LMCSINA V3 0 en

Library Motion
Control SINAMICS -
LMCSINA
Siemens
SIMATIC S7-1200 / S7-1500 Industry
Online
https://support.industry.siemens.com/cs/ww/en/view/109479491 Support
Legal information
Legal information
Use of application examples
Application examples illustrate the solution of automation tasks through an interaction of several
components in the form of text, graphics and/or software modules. The application examples are
a free service by Siemens AG and/or a subsidiary of Siemens AG (“Siemens”). They are non-
binding and make no claim to completeness or functionality regarding configuration and
equipment. The application examples merely offer help with typical tasks; they do not constitute
customer-specific solutions. You yourself are responsible for the proper and safe operation of the
products in accordance with applicable regulations and must also check the function of the
respective application example and customize it for your system.
Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the
application examples used by technically trained personnel. Any change to the application
examples is your responsibility. Sharing the application examples with third parties or copying the
application examples or excerpts thereof is permitted only in combination with your own products.
The application examples are not required to undergo the customary tests and quality inspections
of a chargeable product; they may have functional and performance defects as well as errors. It is
your responsibility to use them in such a manner that any malfunctions that may occur do not
result in property damage or injury to persons.
Disclaimer of liability
Siemens shall not assume any liability, for any legal reason whatsoever, including, without
limitation, liability for the usability, availability, completeness and freedom from defects of the
application examples as well as for related information, configuration and performance data and
any damage caused thereby. This shall not apply in cases of mandatory liability, for example
under the German Product Liability Act, or in cases of intent, gross negligence, or culpable loss of
life, bodily injury or damage to health, non-compliance with a guarantee, fraudulent
non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for
damages arising from a breach of material contractual obligations shall however be limited to the
 Siemens AG 2018 All rights reserved
foreseeable damage typical of the type of agreement, unless liability arises from intent or gross
negligence or is based on loss of life, bodily injury or damage to health. The foregoing provisions
do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens
against existing or future claims of third parties in this connection except where Siemens is
mandatorily liable.
By using the application examples you acknowledge that Siemens cannot be held liable for any
damage beyond the liability provisions described.
Other information
Siemens reserves the right to make changes to the application examples at any time without
notice. In case of discrepancies between the suggestions in the application examples and other
Siemens publications such as catalogs, the content of the other documentation shall have
precedence.
The Siemens terms of use (https://support.industry.siemens.com) shall also apply.
Security information
Siemens provides products and solutions with industrial security functions that support the secure
operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary
to implement – and continuously maintain – a holistic, state-of-the-art industrial security concept.
Siemens’ products and solutions constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems, machines
and networks. Such systems, machines and components should only be connected to an
enterprise network or the internet if and to the extent such a connection is necessary and only
when appropriate security measures (e.g. firewalls and/or network segmentation) are in place.
For additional information on industrial security measures that may be implemented, please visit
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends that product updates are applied as soon as they are available
and that the latest product versions are used. Use of product versions that are no longer
supported, and failure to apply the latest updates may increase customer’s exposure to cyber
threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed
at: http://www.siemens.com/industrialsecurity.
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018 2
Table of contents
Table of contents
Legal information ......................................................................................................... 2
1 Introduction ........................................................................................................ 5
1.1 General structure of the library ............................................................. 5
1.2 Content of the application folders ......................................................... 6
1.2.1 Synchronism applications..................................................................... 6
1.2.2 Cross Cutter ......................................................................................... 7
1.2.3 Flying Saw ............................................................................................ 8
1.2.4 Line Tension Control ............................................................................ 8
1.2.5 Winder .................................................................................................. 9
1.2.6 Traverser .............................................................................................. 9
2 Configuration in STARTER ............................................................................. 10
2.1 Configuring the drive functionality ...................................................... 10
2.2 Configuring the communication .......................................................... 11
2.2.1 Preparation and telegram selection ................................................... 11
2.2.2 Creating the telegram interconnections ............................................. 14
2.2.3 Setting the user-defined GSDML for the TIA Portal ........................... 19
3 LMCSINA synchronism FBs ........................................................................... 20
3.1 Preparation ......................................................................................... 20
3.2 Commissioning steps ......................................................................... 22
3.3 Interfaces ............................................................................................ 28
3.3.1 Interfaces of LMCSINA_BasicSync FB .............................................. 28

3.3.2 Interface of LMCSINA_BasicVirtualMaster FB................................... 32
3.4 Operation of blocks ............................................................................ 34
3.4.1 Operation of LMCSINA_BasicSync FB .............................................. 34
3.4.2 Operation of LMCSINA_BasicVirtualMaster FB ................................. 37
4 LMCSINA_CrossCutterFB in TIA Portal ........................................................ 38
4.1 Preparation ......................................................................................... 38
4.2 Commissioning TIA Portal .................................................................. 40
4.3 LMCSINA_CrossCutterFB interfaces ................................................. 47
4.3.1 Block inputs ........................................................................................ 47
4.3.2 Block outputs ...................................................................................... 48
4.3.3 Value overview for the output status .................................................. 50
4.4 Operation ............................................................................................ 51
4.4.1 Enabling the block .............................................................................. 51
4.4.2 Reading configuration data ................................................................ 51
5 LMCSINA_FlyingSawFB in TIA Portal ........................................................... 52
5.1 Preparation ......................................................................................... 52
5.2 Commissioning TIA Portal .................................................................. 54
5.3 LMCSINA_FlyingSawFB interfaces ................................................... 61
5.3.1 Block inputs ........................................................................................ 61
5.3.2 Block outputs ...................................................................................... 62
5.3.3 Value overview for the output status .................................................. 64
5.4 Operation ............................................................................................ 65
5.4.1 Enabling the block .............................................................................. 65
5.4.2 Reading configuration data ................................................................ 65
6 LMCSINA_WinderFB in TIA Portal ................................................................. 66
7 LMCSINA_LineTensionControlFB in TIA Portal ........................................... 67
8 LMCSINA_TraversingDriveFB im TIA Portal ................................................. 68
9 Appendix .......................................................................................................... 69
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018 3
Table of contents
9.1 Service and Support ........................................................................... 69

9.2 Application Support ............................................................................ 70
9.3 Links and Literature ............................................................................ 70
9.4 Change documentation ...................................................................... 71
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018 4
1 Introduction
1 Introduction
The SIMATIC library "Library Motion Control SINAMICS" allows the comprehensive
motion control functions in the SINAMICS S120 to be controlled in a user-friendly
and convenient fashion. The applications based on DCC / DCB-Extension for the
SINAMICS S120 are supported. The library can be used with a SIMATIC S7-1500
as well as with a SIMATIC S7-1200. Control is possible via PROFINET or
PROFIBUS-DP.
The following applications are supported:
 BasicGear synchronism (from V5.1)
https://support.industry.siemens.com/cs/ww/en/view/xxx
 BasicCam synchronism (from V5.1)
 ExtendedGear synchronism (from V5.1)
 ExtendedCam synchronism (from V5.1)
 Positioning (from V5.1)
https://support.industry.siemens.com/cs/ww/en/view/72849730
 Linear flying saws with DCB-Extension
 Cross-cutters with DCB-Extension
 DCC Winder
 DCC Line Tension Control
 Traversing with DCB-Extension
https://support.industry.siemens.com/cs/de/de/view/xxx
Note The former versions of LMCSINA library (< V3.0) include the former application
versions for drive based synchronism (synchronism applications <= V4.x).
The LMCSINA library >= V3.0 includes only the control blocks for the innovated
synchronism applications (from synchronism application version >= V5.1) and
the technological applications.
1.1 General structure of the library

The library is separated in the different drive based applications. Each application /
each application type has a separate folder in the master copies of the library.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 5
1 Introduction
Figure 1-1
1.2 Content of the application folders

1.2.1 Synchronism applications
The folder "01_Synchronism Applications" contains all blocks, that are relevant for
the control of the synchronism applications (>= V5.1).
Figure 1-2
The blocks are only used to control the drive based functions. There are no
interlocks and logics implemented inside the blocks. This makes sure to have a
consistent axis state in the drive. The blocks directly send all commands to the
drive. All axis states are handled by the drive itself. The separate blocks realize the
following tasks:
LMCSINA_BasicSync: This FB is used for controlling per one following axis in

synchronism or for a positioning leading axis. For each axis one instance of this
block is needed. The block can handle all axes with the following applications:
Basic Gearing, Basic Cam, Extended Gearing, Extended Cam and Positioning.
Included are functions like axis enable, homing, stopping, jogging, positioning,
leading value switchover, synchronization, etc.
LMCSINA_BasicMeasuringWheel: This FB is optional and therefore not

mandatory to realize the synchronism. It is used to control certain homing functions
on a measuring wheel as leading axis.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 6
1 Introduction
LMCSINA_BasicVirtualMaster: This FB is optional and therefore not mandatory

to realize the synchronism. It is used to control the virtual master (virtual leading
axis), which is calculated on a following axis and should be controlled by the PLC.
The virtual leading axis includes functions like setting, positioning and continuous
motion.
LMCSINA_ExtendedCamFunctions: This FB is optional and therefore not

mandatory to realize the synchronism. It can be called additionally to the
LMCSINA_BasicSync FB. It is only valid for the application "Extended Cam" and
controls additional camming functions.
LMCSINA_ExtendedCoupleFunctions: This FB is optional and therefore not

LMCSINA_BasicSync FB. It is only valid for the application "Extended Gear" and
"Extended Cam" and controls additional coupling functions.
LMCSINA_ExtendedOffsetFunctions: This FB is optional and therefore not

LMCSINA_BasicSync FB. It is only valid for the application "Extended Gear" and
"Extended Cam" and controls additional offset functions.
LMCSINA_SpeedAxis: This FB is optional and therefore not mandatory to realize

the synchronism. It is used to control several homing functions when using a speed
leading axis as leading value. It does not control the speed of the axis.
1.2.2 Cross Cutter
The folder "02_CrossCutter" contains all files that are necessary for the drive
based cross cutter application.
Figure 1-3
The subfolder "Necessary components from LAcycCom" contains some mandatory

variables and datatypes from another library for compiling the block correctly. If the
library "LAcycCom" not used in the project so far, those files always have to be
copied completely to the PLC.
The subfolder "LMCSINA components" contains the necessary datatypes for
compiling and the control function block.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 7
1 Introduction
1.2.3 Flying Saw
The folder "03_FlyingSaw" contains all files that are necessary for the drive based
flying saw application.
Figure 1-4

compiling and the control function block.
1.2.4 Line Tension Control
The folder "04_LineTensionControl" contains all files that are necessary for the
drive based application line tension control.
Figure 1-5

LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 8
1 Introduction
compiling, the control function block and the configuration data block
1.2.5 Winder
The folder "05_Winder" contains all files that are necessary for the drive based
winder application.
Figure 1-6

compiling, the control function block and the configuration data block.
1.2.6 Traverser
The folder "06_Traverser" contains the block for controlling the drive based
application traverser (with DCB Extension).
Figure 1-7
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 9
2 Configuration in STARTER
2.1 Configuring the drive functionality
The drives must be configured and parameterized in Starter, as the motion control
functionality, for the synchronous applications as well as for the other technological
applications, are directly realized in the drive.
Detailed step-by-step instructions are provided in the commissioning chapter of the
application itself. The basic steps are again shown in the following.
Basic configuration steps

1. Install the necessary DCB libraries in STARTER/SCOUT, and load to the drive
device
2. Create the drives as usual or read them by automatic configuration
3. Activate the position controller on the axes (only for position controlled axes)
4. Import the appropriate DCC charts (and save/compile)
5. Parameterize the mechanical system of the axes
6. Parameterize the basic motion control functionality, geometry of the system
etc.
7. If required, configure the communication (see Chapter Fehler! Verweisquelle
konnte nicht gefunden werden.)
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 10
2.2 Configuring the communication

2.2.1 Preparation and telegram selection
Telegrams for position controlled axes

This chapter is valid for the following applications / axes:
 Synchronism axes:
– Basic Gearing
– Basic Camming
– Extended Gearing
– Extended Camming
– Positioning
 Cross cutter
 Flying saw
 Winder
 Traverser
 Line tension control
The configuration of speed-controlled leading axes is different and is described in

the next chapter “Communication for speed-controlled leading axes”.
When selecting the telegram of the axes to be controlled, "[999] Free telegram
configuring with BICO" must be selected. If a standard telegram was active
beforehand, reset the parameters on the axis by setting p10 = 30.
The length of the input data/actual values and output values/setpoints should be
set to the following lengths:
For all synchronism axes: Input data = 28; Output data = 20

Cross cutter: Input data = 20; Output data = 20
Flying saw: Input data = 20; Output data = 20
Winder: Input data = 20; Output data = 20
Line tension control: Input data = 20; Output data = 20
Traverser: Input data = 28; Output data = 20
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 11
Figure 2-1
NOTICE Undesirable axis motion as a result of incorrect telegram settings

If a telegram configuration other than "[999] Free telegram configuring with
BICO" is set, even after running the commissioning script, incorrect BICO
interconnections will continue to exist. Depending on the previous telegram
selection, this can result in incorrect and undesirable axis motion.
Telegram for speed-controlled leading axes

This chapter is valid for the following applications / axes:
 Speed-controlled leading axes for synchronism applications
The general speed control of the drive is done by the user. Therefore there are
function blocks in TIA Portal like the SINA_SPEED function block of the DriveLib.
For this kind of control the user can select any telegram. In order to use the
SINA_SPEED FB for example the standard telegram 1 is used.
Independent of this general drive control there are several position related
functions like homing available for these speed controlled leading axes in
synchronism operation. To control these functions, supplementary data of 1 (word)
in send and receive direction is added. The communication script is adding the
supplementary data automatically to the drive object. There must not be other
supplementary data configured by the user for that drive object. If the user needs
additional data transfer for a standard telegram, this needs to be handled by
telegram extension. The telegram length must not exceed the maximum limit. The
script fails when the limit is exceeded.
Configuration steps:
 First just configure the send and receive data to do the user defined speed
control (e.g. by selecting a standard telegram and optional telegram extension)
 Execute the communication script for the synchronism applications
 When executing the script select the communication for your speed controlled
leading drive
By running the script supplementary data with the length of 1 word in send and
receive direction is added and the technology control and status word is
interconnected to it.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 12
An example configuration could look as follows:
Figure 2-2
In this example the user would use Standard telegram 1 for speed control.
Additionally 4 words in send and receive direction for other user data is added by
the user. The script added the supplementary data automatically.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 13
2.2.2 Creating the telegram interconnections
Executable script files are supplied for the particular applications to create the
telegram interconnection. You will find the script that matches the particular
application in the following table.
Table 2-1
Application used Script file required
Synchronous applications: LMCSINA_Synchronism_CommunicationScript
 Basic Gearing (.txt/.xml)
 Basic Camming
 Extended Gearing
 Extended Camming
 Positioning with DCC / EPOS
 Measuring Wheel (as Leading axis)
 Speed Axis (as Leading axis)
Cross cutter LMCSINA_Technology_CommunicationScript
(.txt/.xml)
Flying saw LMCSINA_Technology_CommunicationScript
(.txt/.xml)
The script files supplied for the applications to establish the appropriate
telegram interconnection can either be incorporated in Starter (from Starter
version V4.4.1.0) or in the project itself. For all of the scripts mentioned above,
the integration and execution is identical. The two versions for possible
integration and execution are described in the following.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 14
Script integrated in Starter

With this version, the script is available in all drive projects with the matching
device versions. However, in this case, the script is not archived with the project.
This version makes sense if you frequently wish to commission similar projects with
an unchanged script.
To do this, proceed as follows:
 Copy the script file provided (*.txt) to the installation directory of Starter in the
following file structure (in this case, with "C:\Program Files" as installation
folder, for example):
"C:\Program Files (x86)\Siemens\Step7\U7umc\data\scripts\
device_configurations\v4.8\SINAMICS_S120"
 The saved scripts can now be selected in the configuration screen form of the
drive via "Configuration scripts":
Fig. 2-3
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 15
 In the dialog that opens, select the appropriate script, and click on "Execute".
Fig. 2-4
 Follow the instructions of the script

LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 16
Using the script integrated in the project
With this version, you must import the script into every project where you wish to
use it. However, the script remains integrated, even when archiving and
transferring the project. This version especially makes sense if you wish to make
your own project-specific modifications to the script.
To do this, proceed as follows:
 Insert a script folder at the project level
Fig. 2-5
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 17
 Import the interconnection script (*.xml)
Fig. 2-6
 "Accept and execute" the script
Figure 2-7
 Follow the instructions of the script

 Please refer to the documentation of the particular application for additional
parameter settings
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 18
2.2.3 Setting the user-defined GSDML for the TIA Portal
If you are using a PROFIBUS drive, then a GSDML file does not have to be
created in STARTER. The standard GSDs for PROFIBUS can be subsequently
used in the TIA Portal.
Proceed as follows if you wish to use a PROFINET drive:
Note When using PROFINET – when integrating into the TIA portal – it is necessary to
create a user-defined GSDML for the TIA Portal. The standard GSDML of the
SINAMICS S120 does not include a 20/20 or 20/28 telegram; however it is
required for creating the user-defined GSDML file.
Create the user-defined GSDML file for your drive device using the following
Starter script (script and detailed description are available at the following link):
When executed, the script automatically creates the user-defined GSDML file,
which can be subsequently installed in the TIA Portal.
Continuing commissioning
The next steps involve commissioning the communication and control in the TIA
Portal. Proceed with the following chapter depending on the application being
used:
Table 2-2
Application used continue with commissioning Chapter
number
Synchronous applications: Chapter xxx
 Basic Gearing
 Basic Camming
 Extended Gearing
 Extended Camming
 Positioning with DCC / EPOS
 Measuring Wheel (as Leading axis)
 Speed Axis (as Leading axis)
Cross cutter Chapter xxx
Flying saw Chapter xxx
Winder Commissioning and description see manual
of winder
Line tension control Commissioning and description see manual
of line tension control
Traverser Commissioning and description see manual
of traverser
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 19
3 LMCSINA synchronism FBs

This chapter includes the description of the following synchronism function blocks:
 LMCSINA_BasicSync
 LMCSINA_BasicVirtualMaster
 LMCSINA_SpeedAxis
 LMCSINA_BasicMeasuringWheel
After you have configured the drive according to chapter 2 , then the
communication to the higher-level control is configured in the TIA Portal.
3.1 Preparation
If you wish to configure a PROFIBUS a device, then you can continue with Chapter
3.2.
If you wish to configure a PROFINET device, then this is done using the user-
defined GSDML file. How you can install this GSDML file is described in the
following, and where you can then find it in the hardware catalog.
Installing the GSDML file generated in the TIA Portal

Install the user-defined GSDML file that you generated in the TIA Portal as follows:
Fig. 3-1
Fig. 3-2
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 20
Finding the GSDML in the hardware catalog

The GSDML file can now be found in the folder structure of the hardware catalog –
as shown in the following diagram.
Fig. 3-3
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 21
3.2 Commissioning steps

Configuring the control
Create a SIMATIC S7-1200/1500 control, and then configure it as usual.
Note A minimum firmware release of 4.0 is required for the SIMATIC S7-1200. This is
necessary to use the blocks from "LAcycCom" for acyclic communication.
The following's steps describe the procedure when creating the drives and the
control blocks.
Integrating the drive
 Integrating the SINAMICS drive into the network view

a. PROFIBUS: Use the existing GSD files
b. PROFINET: Use the user-defined GSDML file that has been installed
 Connect the drive to the control system
Fig. 3-4
Integrating the LMCSINA library
 Dearchive the global LMCSINA library by right clicking in the global libraries.
Fig. 3-5
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 22
 Copy all necessary control blocks from the folder "01_Synchronism

Applications" to the program blocks of the PLC.
 The block LMCSINA_BasicSync is mandatory and controls the following axes.
All other blocks are optional.
Figure 3-6
Calling the block LMCSINA_BasicSync


Call the FB "LMCSINA_BasicSync" with an instance for each synchronous

axes in your user program
 Interconnect all needed inputs and outputs
Note The following inputs are mandatory to interconnect:

– enable
(the block is only calculated if it is TRUE)
– HardwareID of the free telegram 28/20
(can be found under PLC tags -> system constants)
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 23
Figure 3-7
Calling the block LMCSINA_BasicVirtualMaster

 Call the FB "LMCSINA_BasicVirtualMaster" with an instance for each virtual
leading axes in your user program

– enable
– HardwareID of the free telegram 28/20 of the following axis on which the
virtual leading axis is calculated
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 24
Figure 3-8
Calling the block LMCSINA_BasicMeasuringWheel

 Call the FB "LMCSINA_BasicMeasuringWheel" with an instance for each
measuring wheel axes in your user program

– enable
– HardwareID of the free telegram 28/20 of the following axis on which the
measuring wheel is calculated
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 25
Figure 3-9
Calling the block LMCSINA_SpeedAxis

 Call the FB "LMCSINA_SpeedAxis" with an instance for each speed leading
axis in your user program
 Each FB LMCSINA_SpeedAxis is communicating on his own with the
connected drive object. Therefore the inputs HWID_STW and HWID_ZSW
need to be set to the corresponding Hardware-ID of the projected
supplementary data of the length 1/1 (word)
Note The following inputs must (mandatory) be interconnected in order to call the
function block:
– enable
(the block is only calculated for TRUE)
– HWID_STW
Here the hardware ID of the supplementary telegram data in send
direction (from the PLCs point of view) needs to be given
– HWID_ZSW
Here the hardware ID of the supplementary telegram data in receive
direction (from the PLCs point of view) needs to be given
The block itself can now be compiled.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 26
Calling the addon block LMCSINA_ExtendedCamFunctions

 Optionally call the FB "LMCSINA_ExtendedCamFunctions" with an instance for
each following axis in your user program

– enable
Calling the addon block LMCSINA_ExtendedCoupleFunctions

 Optionally call the FB "LMCSINA_ExtendedCoupleFunctions" with an instance
for each following axis in your user program

– enable

Calling the addon block LMCSINA_ExtendedOffsetFunctions

 Optionally call the FB "LMCSINA_ExtendedOffsetFunctions" with an instance
for each following axis in your user program

– enable
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 27
3.3 Interfaces
3.3.1 Interfaces of LMCSINA_BasicSync FB
Table 3-1
Designation Type Data type Description
enable IN BOOL Block enable
TRUE: block is calculated cyclically
FALSE: block is not calculated
ackError IN BOOL Acknowledge drive fault
TRUE: acknowledge drive fault
enableAxis IN BOOL Drive enable
TRUE: axis enable (OFF1 enable oft he drive)
FALSE: deletion of OFF1 command (OFF2, OFF3
keep set)
enablePositionControl IN BOOL Position control(ler) enable
TRUE: enable position control of the axis
FALSE: disable position control
homing IN BOOL Enable homing
TRUE: enable homing (depending on mode)
homingMode IN INT Homing mode
1: Set reference point
2: Start absolute encoder adjustment

3: Enable flying homing
4: Enable and start active homing procedure
referenceCoordinate IN DINT Reference coordinate for homing functions
interruptMethod IN BOOL Selection of Interrupt for active homing
TRUE: Measuring input as interrupt
FALSE: encoder zero mark as interrupt
homingOnlyOnInterrupt IN BOOL Selection of type for active homing
TRUE: active homing only on interrupt, without
proximity switch
FALSE: active homing with proximity switch and
interrupt
homingDirection IN BOOL Selection of active homing direction
TRUE: negative starting direction
FALSE: positive starting direction
homingEdge IN BOOL Selection of edge detection proximity switch for
active homing
TRUE: negative edge detection
FALSE: positive edge detection
stopDrive IN BOOL Stop drive
TRUE: Axis ramps down with given dynamics and
stays in standstill as long as this input is enabled
(level detection)
FALSE: Move axis with next highest mode
jogPositive IN BOOL Jog forward
TRUE: Move axis forward with given jog velocity
as long as the input is enabled (level detection)
jogNegative IN BOOL Jog backward
TRUE: Move axis backward with given jog
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 28

velocity as long as the input is enabled (level
detection)
enableMDI IN BOOL Enable positioning mode
TRUE: Change axis mode to positioning. When
enabling the input the axis ramps down and waits
for the starting command for positioning. As long
as the axis should stay in positioning mode, the
input needs to be enabled (level detection).
startPositioning IN BOOL Starting command for new positioning motion
(edge triggered)
positive edge: Start a new positioning motion
positioningType IN BOOL Selection of positioning type
TRUE: absolute positioning
FALSE: relative positioning
mdiContinuous IN BOOL Enable continuous setpopint change trigger (only
valid for absolute positioning)
TRUE: a new positioning motion is started by just
changing the position setpoint ("positionSetpoint")
There is no need of starting the motion by the
input "startPositioning"
FALSE: Positioning motions always need tob e
started by the input "startPositioning"

positionSetpoint IN DINT Setting of the positioning setpoint for positioning
motions in [LU]
syncAbsolute IN BOOL Absolute synchronization for synchronism mode
- edge triggered behavior:
With positive edge during relative synchronism a
synchronisation motion is started and the axis
changes over to absolute synchronism
- level depending behavior:
TRUE: When leaving a higher priority mode it is
preselected that the axis directly synchronizes
absolutely to the leading valued
FALSE: For each changeover to synchronism
mode the axis synchronizes relatively to the
leading value
selectChannel IN BOOL Selection of leading value channel for
synchronism mode
TRUE: leading value channel 1 is active
FALSE: leading value channel 2 is active
- Change: By changing the input in synchronism
mode the axis synchronizes to the other leading
value channel. This can be done relatively
("syncAbsolute" = 0) or absolutely
("syncAbsolute" = 1)
compensationFwd IN BOOL Enable compensation motions always in forward
direction (only valid for modulo axes)
TRUE: compensation motions always forward
FALSE: compnesation motions backward or on
shortest way (depending on input
"compensationBwd")
Truth table for the inputs compensationFwd (here

Fwd) and compensationBwd (here Bwd):
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 29

Fwd = 0; Bwd = 0: compensation on shortest way
Fwd = 1; Bwd = 0: compensation always forward
Fwd = 1; Bwd = 1: compensation always forward
Fwd = 0; Bwd = 1: compensation always
backward
compensatioBwd IN BOOL Enable compensation motions always in

backward direction (only valid for modulo axes)
Truth table see input "compensationFwd"
autoSyncAfterHoming IN BOOL Enable automatic synchronization of following
axis after homing of leading axis
TRUE: Offset caused by homing of the leading
axis is automatically synchronized
FALSE: Offset caused by homing of the leading
axis keeps stored on following axis -> relative
synchronism
Note:
- is set for example when using print mark
correction or flying homing on leading axis side
- manual synchronization is possible via
"syncAbsolute"
interpolateCam IN BOOL Trigger for recalculating the cam (edge triggered)
positive edge: recalculate cam
Note: only valid for application "Basic Cam"

Attention: Cams should only be recalculated in
case the axis is not in synchronism operation, as
position jumps could occur depending on the cam
itself!
camAbsolute IN BOOL Enable absolute cam output
TRUE: cam output absolute
FALSE: cam output relative
Note: Only valid for application "Basic Cam"

For details see application manual
enablePrintmarkCorrection IN BOOL Enable print mark correction on following axis
TRUE: Print mark correction enabled
FALSE: Print mark correction disabled
velocityOverride IN REAL Velocity override for axis dynamics
valid values: 0..199%
Normalization value for maximum relative velocity:

p21551
For details see application manual -> axis
dynamics
accelerationOverride IN REAL Acceleration override for axis dynamics
Normalization value for maximum relative

acceleration: p21553
dynamics
mdiVelocityOverride IN REAL Velocity override for positioning motions
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 30
Normalization value for positioning velocity:

p22015
freeSendWord20 IN WORD Free communication word for the user to send
additional data to the drive
Note: Destination in drive is parameter r2050[19]
HardwareID IN HW_IO Setting of ID of the free telegram 20/28 to the
following axis
Note: The Hardware ID is automatically assigned
by the PLC when interconnecting the drive to it. A
list of all Hardware IDs can be found under PLC
tags -> system constants. Always use the ID of
the telegram to the drive (not the ID of the drive
itself).
valid OUT BOOL TRUE: Block outputs valid
busy OUT BOOL TRUE: Block is calculated
error OUT BOOL TRUE: Block fault
status OUT WORD Block state
warncode OUT WORD Actual warncode (r2132) of the drive
faultcode OUT WORD Actual faultcode (r2131) of the drive
axisEnabled OUT BOOL TRUE: Axis enabled (OFF1 enabled – axis in
operation)
axisError OUT BOOL TRUE: Axis fault

positionControlActive OUT BOOL TRUE: Position control enabled
axisHomed OUT BOOL TRUE: Axis homed
axisStandstill OUT BOOL TRUE: Axis in standstill (v = 0)
axisStops OUT BOOL TRUE: Axis stops (velocity is ramped down to
standstill)
jogFwdActive OUT BOOL TRUE: Jog forward active
jogBwdActive OUT BOOL TRUE: Jog backward active
homingActive OUT BOOL TRUE: Active homing activated
mdiActive OUT BOOL TRUE: Positioning mode active
followUpActive OUT BOOL TRUE: Follow up mode active (Position control
disabled) – position setpoint is set to actual
position value
encAdjActive OUT BOOL TRUE: Absolute encoder adjustment active
Note: Do not switch on the axis as long as the
adjustment is active
encAdjError OUT BOOL TRUE: Fault in absolute encoder adjustment
(Cause: see parameter r23921)
encAdjDone OUT BOOL TRUE: Absolute encoder adjustment successfully
done
dynamicsNotValid OUT BOOL TRUE: Axis dynamics not valid
Note: Set valid values for velocity and
acceleration and acknowledge the error by the
input "ackError"
dynamics
axisMovesFwd OUT BOOL TRUE: Axis moves forward (v > 0)
axisMovesBwd OUT BOOL TRUE: Axis moves backward (v < 0)
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 31

relativeSync OUT BOOL TRUE: Relative synchronism active
absoluteSync OUT BOOL TRUE: Absolute synchronism active
camNotValid OUT BOOL TRUE: parameterized cam points do not result in
a valid cam
Note: Adjust the cam points and recalculate the
cam by the input "interpolateCam"
actualPosition OUT DINT Actual position of the axis (r2521[0]) in [LU]
actualVelocity OUT DINT Actual velocity of the axis (r2522[0]) in [1000
LU/min]
load OUT Real Actual torque value of the axis (r80)
Note: normalized to p2003
4000hex = 16384dec = 100% of p2003
7FFFhex = 32767dec = 199% of p2003
FFFFhex = -32768dec = -200% of p2003
axisState OUT UDINT Actual state / mode of the axis (r23900)
cyclicReadState OUT DWORD Actual state / fault of the cyclic reading command
(for diagnosis in case of faulty communication ->
see help of block DPRD_DAT in TIA Portal)
Note: in many cases a wrong HardwareID was set
cyclicWriteState OUT DWORD Actual state / fault of the cyclic writing command
(for diagnosis in case of faulty communication ->
see help of block DPRD_DAT in TIA Portal)
Note: in many cases a wrong HardwareID was set

freeReceiveWord25 OUT WORD Word for free usage for the user to read additional
data from the drive
Note: Value needs to be interconnected to
parameter p2051[24] in the drive
data from the drive
data from the drive
data from the drive
3.3.2 Interface of LMCSINA_BasicVirtualMaster FB
Table 3-2
enable IN BOOL Block enable
TRUE: Block is calculated cyclically
FALSE: Block is not calculated
setVirtualAxis IN BOOL Set the output position of the virtual leading axis
TRUE: Set output position to setting value
moveFwdVirtualAxis IN BOOL Move virtual leading axis continuously forward
TRUE: Move continuously forward
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 32

moveBwdVirtualAxis IN BOOL Move virtual leading axis continuously backward
TRUE: Move continuously backward
velocityOvdVirtualAxis IN REAL Velocity override for virtual leading axis
Normalization value for velocity:

p25004
positioningTypeVirtualAxis IN BOOL Selection of positioning type
TRUE: Absolute positioning
FALSE: Relative positioning
positioningFwdVirtualAxis IN BOOL Selection of positioning direction (only valid for
modulo axes and absolute positioning)
TRUE: Positioning only forward
Truth table for the inputs

positioningFwdVirtualAxis (here Fwd) and
positioningBwdVirtualAxis (here Bwd):
Fwd = 0; Bwd = 0: Positioning motions on
shortest way
Fwd = 1; Bwd = 0: Positioning motions always
forward
forward
backward
positioningBwdVirtualAxis IN BOOL Selection of positioning direction (only valid for
modulo axes and absolute positioning)
TRUE: Positioning only bakcward
Truth table see input "positioningFwdVirtualAxis"

startPositioningVirtualAxis IN BOOL Starting command for a new positioning motion
(edge triggered)
positive edge: Starting a new positioning motion
stopPositioningVirtualAxis IN BOOL Stop and reject a positioning motion (edge
triggered)
positive edge: active positioning motion is
stopped and rejected
positionSetpointVirtualAxis IN BOOL Position setpoint for positioning motion in [LU]
HardwareID IN HW_IO Setting of Hardware ID of the free telegram 20/28
to the following axis, on which the virtual axis is
calculated
Note: The Hardware ID is automatically assigned
by the PLC when interconnecting the drive to it. A
list of all Hardware IDs can be found under PLC
tags -> system constants. Always use the ID of
the telegram to the drive (not the ID of the drive
itself).
valid OUT BOOL TRUE: Block outputs valid
busy OUT BOOL TRUE: Block is calculated
error OUT BOOL TRUE: Block error
status OUT WORD Block state
actualPosVirtualAxis OUT DINT Actual position of virtual leading axis in [LU]
actualVelVirtualAxis OUT DINT Actual velocity of virtual leading axis in [1000
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 33

LU/min]
continuousOpVirtualAxis OUT BOOL TRUE: Continuous mode active
positioningActiveVirtualAxis OUT BOOL TRUE: Positioning motion active
positioningDoneVirtualAxis OUT BOOL TRUE: Positioning motion done / not active
3.4 Operation of blocks

3.4.1 Operation of LMCSINA_BasicSync FB
Block enable
The blocks must be enabled with "Enable". Status 7000H means that the block is
not computed. Status 7001H is output at the first call. When it is in cyclic mode the
status changes to 7002h.
Only if the block is enabled there is a cyclic communication to the drive. If the block
enable signal is disabled during operation the OFF1 command of the drive is taken
first before the cyclic communication is stopped.
Axis enable
The axis is enabled by the input "enableAxis". By that the OFF1 command of the
drive is set. The commands for OFF2 and OFF3 are permanently enabled and are
not taken in case the block is enabled. When the axis is automatically switched off
by an axis fault, the fault has to be acknowledged first and then a new rising edge
needs to be created at the "enableAxis" input to switch on the axis again. After that
the input needs to stay enabled as long as the axis should be enabled. So the input
has an edge detection and a level detection. For switching on always a positive
edge is required.
Switch on after fault

After an axis fault, which switched off the axis, the fault first needs to be
acknowledged by "ackError" and then a new rising edge at the input "enableAxis"
needs to be created. So only acknowledging the fault is not sufficient to switch on
the axis again.
The following diagram shows the switching on procedure
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 34
Figure 3-10
Acknowledge error
(I: ackError)
Enable axis
(I: enableAxis)
Axis fault
(Q: axisError)
Axis enabled
(Q: axisEnabled)
Enable position control

When the axis should be moved, the position controller needs to be enabled by the
input "enablePositionControl". Additionally the axis needs to be switched on. The
axis only changes to the wanted mode if it is switched on and the position control is
enabled. The additional need to enable the position control shall avoid to directly
changing the axis to synchronism mode after switching on.
Axis modes
All axis modes are prioritized and are handled by the application on the drive side.
The synchronism mode is automatically active when the axis and the position
control is enabled. So for that mode no explicit control bit is necessary to set. All
other modes (Stop drive, jog, active homing and positioning) have a higher priority
than synchronism mode and need to be enabled explicitly. If the axis should not
directly go to synchronism mode after switching on and position controller enable
another mode needs to be selected (e.g. "stopDrive").
In general more than one mode can be selected at the same time. The application
prioritizes the modes and runs always the mode with the highest priority. The
following modes are prioritized in the following order (first mode = highest priority;
last mode = lowest priority):
1. Follow up mode (Axis disabled / position control disabled)
2. Stop drive
3. Jog forward
4. Jog backward
5. Active homing mode
6. Positioning mode
7. Absolute synchronism
8. Relative synchronism
When the axis is switched on and the position controller is enabled, the mode
"relative synchronism" is automatically active in case no other mode with higher
priority is selected.
The following functions are not prioritized and can in general be executed in
parallel to the other modes:
 Flying homing
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 35
 Set reference point

 Print mark correction (only reasonable in synchronism mode!)
Selecting a mode
Modes need to be selected explicitly. The modes "follow up" and "relative
synchronism" are an exception here.
The follow up mode is getting active when the position controller is disabled or the
axis is switched off.
The relative synchronism mode is always getting active when the axis and the
position controller are enabled and no other mode is selected.
In case more than one mode is selected the axis always executes the mode with
the highest priority.
Deselecting a mode
A mode can be left by deselecting it or by selecting a mode with higher priority.
When the position controller is enabled and no other mode is selected, the axis
changes always to "relative synchronism" mode and follows the leading value's
velocity.
Flying changeover of modes

In general each mode can be switched over with a dynamic motion to another
mode on the fly.
Changing into a mode with higher priority

By selecting a mode with higher priority than the actual one the axis always
changes directly to that new mode - independent whether the old mode keeps
selected or not. By that you could for example switch over on the fly from jogging
backward to jogging forward by first selecting jog backward and then additionally
select jog forward. Of course in the same moment jog backward could be
deselected (but does not need to).
Changing into a mode with lower priority

For a flying changeover to a lower priority mode the old higher priority mode always
needs to be deselected. Either the lower priority mode is then selected exactly at
the same time or it is already preselected. A mode is preselected by selecting the
higher priority mode as well as the lower priority mode. Then the higher priority
mode just needs to be deselected and the axis changes to the lower priority mode.
In the application manual you additionally find a schematic timing diagram for flying
changeovers of modes and the list of all axis states for diagnosis and interpreting
reasons.
Information regarding the different axis functions and modes

Detailed information to all axis functions and their configuration can be found in the
application manual in the operation chapter.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 36
3.4.2 Operation of LMCSINA_BasicVirtualMaster FB
Block enable
The blocks must be enabled with "Enable". Status 7000H means that the block is
not computed. Status 7001H is output at the first call. When it is in cyclic mode the
status changes to 7002h.
Only if the block is enabled there is a cyclic communication to the drive.
Modes
The virtual leading axis in general can be operated in the following modes:
 Continuous mode – a position signal is continuously generated by the given
velocity setpoint.
 Positioning mode – the virtual leading axis by a starting command is moving
absolutely to a defined position or moves on relatively by the defined distance.
 Setting function – the output position of the virtual leading axis is set to a
defined setting position.
This is the priority of the modes:

1. Setting function (highest priority)
2. Continuous motion
3. Positioning (lowest priority)
A changeover of modes works similar to the following axis. Modes with higher
priority always first need to be deselected before the axis changes to a mode with
lower priority. Changes to modes with higher priority are always directly done.
CAUTION Unexpected position jumps on the following axes

If the virtual axis is set while one or more following axes are synchronized
(absolutely or relatively) to it, position jumps on the following axes can occur.
Therefore only set the virtual axis in case the following axes are uncoupled from
synchronism (e.g. by selecting the mode "stop drive" on the following axis).
Detailed information to all functions of the virtual leading axis can be found in the
application manual in chapter functions of the virtual leading axis.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 37
4 LMCSINA_CrossCutterFB in TIA Portal

4.1 Preparation
4.2.

Fig. 4-1
Fig. 4-2
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 38

Fig. 4-3
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 39
4.2 Commissioning TIA Portal

control blocks.
1. Integrating the SINAMICS drive into the network view

2. Connect the drive to the control system
Fig. 4-4
3. Dearchive the global LMCSINA library by right clicking in the global libraries.
Fig. 4-5
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 40
Copy all of the required library elements into the folder of the PLC
Open the folder "02_CrossCutter" under the master copies and copy all necessary
files of the library to the correct folders of your PLC (take care of the step order!)
4. Copy the folder "LAcycCom_Tags” from "Necessary components from

LAcycCom” into the folder PLC tags
5. Copy the folder ”LAcycCom_Types" from "Necessary components from
LAcycCom" into the folder PLC datatypes
6. Copy the folder ”LMCSINA_Types" from "LMCSINA components" into the
folder PLC datatypes
7. Copy the function block "LMCSINA_CrossCutterFB" from "LMCSINA
components"  "LMCSINA_Blocks" to the PLC program blocks
NOTICE Avoid creating an invalid array of structs!

Problem: If a data type/block is transferred into the PLC, and is compiled before
accepting the PLC variables/user constants provided, then an invalid array with
"0" structures is created.
Remedy: The PLC variables must be completely accepted before compiling the
PLC/program. This is necessary, as in the data types/blocks used, array limits
are defined based on constants.
Calling block LMCSINA_CrossCutterFB

 Calling the axixFB "LMCSina_CrossCutterFB" with an instance for each cross-
cutter.
 Interconnecting inputs and outputs.
function block:
– enable
– hardwareID
(can be found under PLC variables – system constants)
– driveObjectNo
(can be found in the properties of the drive object in STARTER)
The block itself can now be simply compiled. Additional steps are required to use
acyclic communication (see the next chapter)
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 41
Figure 4-6
Integrating the acyclic communication
Note The function block can also be used without acyclic communication. The default
values in the FB correspond to the default values in the drive parameters.
1. Opening/dearchiving the global "LAcycCom" library

2. Copy all data types from LAcycCom  00_ Resource Management 
LAcycCom_Types to the PLC data types
3. Copy the PLC variables LAcycCom  00_Resource Management to the PLC
folder
4. Copy function block "LAcycCom_ResourceManager" from LAcycCom 
00_Resource Management to the folder of the control system used to the
program blocks
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 42
5. Copy the global data block "LAcycCom_RequestBuffer" from LAcycCom 

00_Resource Management to the PLC folder
Fig. 4-7
4
5
3
6. Copy function block "LAcycCom_ ReadDriveParams" from LAcycCom  01

Drives  LAcycCom_Blocks  PROFIDrive to the PLC folder
7. Copy all data types except "LAcycCom_typeSilentOperation" from LAcycCom
 01 Drives  LAcycCom_Types to PLC data types
Note Data type "LAcycCom_typeSilentOperation", as a result of the use in the

LMCSINA environment, is also supplied there – and must therefore be integrated
into the project ONCE. When not complied with, the TIA portal changes the
comments of a data type, which can result in problems when compiling.
PLC variables "LAcycCom_Drives" should also exist in the project, and should
therefore not be integrated another time.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 43
Fig. 4-8
8. Call function blocks "LAcycCom_ResourceManager" and

"LAcycCom_ReadDriveParams" in the (same) program block

9. Interconnect LAcycCom_RequestBuffer to input "globalBuffer" of
"LAcycCom_ResourceManager" block
10. Activation of LAcycCom_ResourceManager at input "enable"
11. Interconnect LAcycCom_RequestBuffer at input "globalBuffer" of block
"LAcycCom_ReadDriveParams"
12. Interconnect the data area "statAcyclicData" from the instance DB of the cross-
cutter at input "dataset" of block "LAcycCom_ReadDriveParams"
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 44
Figure 4-9
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 45
Fig. 4-10
Note Block LDPV1_Buffermanager must be released at input "enable".

Block LDPV1_ReadParameters is exclusively controlled here using input
"dataset".
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018 46
4.3 LMCSINA_CrossCutterFB interfaces

4.3.1 Block inputs
Table 4-1
Designation Data Default Description
type value
enable Bool FALSE TRUE: Enable FB functionality
FALSE: FB deactivated
ackError Bool FALSE Rising edge: Acknowledge drive fault
enableAxis Bool FALSE Rising edge: Switch-on axis
Falling edge: Switch-off axis
axisAcceleration Real 200.0 Acceleration, positioning/jogging [°/s²]
jogPositive Bool FALSE TRUE: Jog forward
jogNegative Bool FALSE TRUE: Jog backward
jogVelocity Real 3600.0 Jogging velocity [°/min]
traverseToMaintenance Bool FALSE TRUE: Traverse to start position
maintenancePosition Real 0.0 Maintenance position [°]
positioningVelocity Real 3600.0 Positioning velocity [°/min]
approachDirection USInt 1 Defining the approach direction for the initial
position and wait position:
0: shortest path
1: only positive
2: only negative
homing Bool FALSE TRUE: Activate reference point approach
homingMode UInt 1 Type of reference point approach:

0: no reference point approach/homing
1: Active reference point approach active,
2: Active reference point approach active, without
BERO
3: Active reference point approach, backward
4: Active reference point approach, backward,
without BERO
5: Active reference point approach, falling edge
6: Active reference point approach, falling edge
without BERO
7: Active reference point approach, falling edge,
backward
8: Active reference point approach, rising edge,
backward, without BERO
10: Flying referencing/homing
enableCuttingOperation Bool FALSE TRUE: Enable cutting operation – traverse to
start position
enableCut Bool FALSE TRUE or rising edge: Start cutting
cuttingMode USInt 2 Selecting the cutting mode:
0: no cut
1: continuous cutting, immediately
2: continuous cutting
3: Test cut, immediate
4: No cut
5: Single cut, immediate
6: Single cut
formatLength Real 1000.0 Format length [mm]
enableOscillation Bool FALSE TRUE: Enable oscillation for over-critical format
lengths
enableCuttingCurve Bool FALSE TRUE: Enable cut curve input
enableCuttingTorque Bool FALSE TRUE: Enable cut torque input
printMarkCorrection Bool FALSE TRUE: Enable print mark sensing
compensationVelocity Real 100000.0 Velocity for print mark correction compensation
[mm/min]
compensationAcceleration Real 10000.0 Acceleration to compensate print mark correction
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 47

type value
[mm/s²]
distancePrintMarkCut Real 0.0 Distance, print mark cut [mm]
counterReset Bool FALSE Rising edge: Reset material counter
readWriteConfigData USInt 0 0: no reading or writing;
1: Reading the "configdata" from the drive
hardwareID HW_IO 16#0 Hardware identification
(as example, can be found in the system
constants of the PLC)
driveObjectNo USInt 0 Drive object number
(as example, can be found in the communication
page in Starter)
Values of the "homingMode" input

Table 42
homing Designation select using start disable select
Mode homing negative direction BERO flying
flag BWD homing
p21630 p21634 p21635 p21636 p21643
0 no homing x
1 active homing x
2 active homing, without x x
BERO
3 active homing, BWD x x
4 active homing, BWD, x x x
without BERO
5 active homing, negative x x
flag
6 active homing, negative x x x
flag, without BERO
flag, BWD
8 active homing, negative x x x x
flag, BWD, without BERO
10 flying homing x
Values of the "cuttingMode" input

Table 4-3
cuttingMode Meaning
0 no cut
1 immediate continuous cutting
2 continuous cutting
3 immediate test cut
4 test cut
5 immediate single cut
6 single cut
4.3.2 Block outputs
Table 4-4
type value
busy Bool FALSE TRUE: FB is working and new output values can
be expected
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 48

type value
valid Bool FALSE TRUE: Valid set of outputs available at the FB
error Bool FALSE Rising edge informs that an error occurred during
the execution.
axisError Bool FALSE TRUE: Drive error or application error
axisEnabled Bool FALSE TRUE: Axis is in operation
axisMoveFWD Bool FALSE TRUE: Axis traverses forward
axisMoveBWD Bool FALSE TRUE: Axis traverses backward
targetReached Bool FALSE TRUE: Target position reached
joggingActive Bool FALSE TRUE: Jogging active
posToMaintenanceActive Bool FALSE TRUE: Positioning to maintenance position active
homingActive Bool FALSE TRUE: Homing active
flyingHomingActive Bool FALSE TRUE: Flying referencing/homing active
axisHomed Bool FALSE TRUE: Axis is homed
cuttingEnabled Bool FALSE TRUE: Cutting operation enabled
cutPossible Bool FALSE TRUE: Cut possible
oscillatingDeactivated Bool FALSE TRUE: Oscillating deactivated – format length too
long
actualPosition Real 0.0 Actual position [°]
actualVelocity Real 0.0 Actual velocity [°/min]
actualFormatLength Real 0.0 Actual format length [mm]
numberOfCuts DInt 0 Number of cuts
load Real 0.0 Actual torque in % of nominal torque
actualAlarmCode Word 16#0 Displays the code of the last alarm that occurred.
actualFaultcode Word 16#0 Displays the code of the oldest active fault.
status Word 16#7000 Current status of FB
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 49
4.3.3 Value overview for the output status
Table 4-5
Value Meaning
16#7101 jog velocity at limit
16#7102 positioning velocity at limit
16#7103 compensation velocity at limit
16#7110 positioning acceleration at limit
16#7111 compensation acceleration at limit
16#7200 acyclic command busy
16#7201 acyclic command busy and drive fault active
16#7202 acyclic command done
16#7203 acyclic command done and drive fault active
16#8210 homing mode not valid

16#8213 cutting mode not valid
16#8214 format length not valid
16#8215 approach direction not valid
16#8400 drive alarm active

16#8401 drive fault active
16#8402 DCC group fault active
16#8410 fine resolution not valid
16#8600 DPRD_DAT fault active

16#8610 DPWR_DAT fault active
16#8621 acyclic command error

16#8622 acyclic command error and drive fault active
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 50
4.4 Operation
4.4.1 Enabling the block
The block must be enabled with "enable". Status 7000H means that the block is not
computed. Status 7001H is output at the first call.
4.4.2 Reading configuration data
Input "readWriteConfigData" must be set to 1 to readout configuration data from

the drive. The task is started when the status at the input changes.
The absolute and/or the maximum values of the dynamic data are read out.
The values must be read out if the following parameters are changed in the drive.
Alternatively, the values can be manually adapted in the instance DB.
The following parameters are read out:
Fig. 4-11
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 51
5 LMCSINA_FlyingSawFB in TIA Portal

LMCSINA_FlyingSawFB is commissioned in exactly the same way as
LMCSINA_CrossCutterFB.
This is the reason that in the following screenshots, the LMCSINA_CrossCutter
elements are visible.
5.1 Preparation
5.2.

Fig. 5-1
Fig. 5-2
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 52

Fig. 5-3
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 53
5.2 Commissioning TIA Portal

control blocks.
8. Integrating the SINAMICS drive into the network view

9. Connect the drive to the control system
Fig. 5-4
10. Dearchive the global LMCSINA library by right clicking in the global libraries.
Fig. 5-5
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 54
Copy all of the required library elements into the folder of the PLC
Open the folder "03_FlyingSaw" under the master copies and copy all necessary
files of the library to the correct folders of your PLC (take care of the step order!)
11. Copy the folder "LAcycCom_Tags” from "Necessary components from

LAcycCom” into the folder PLC tags
12. Copy the folder ”LAcycCom_Types" from "Necessary components from
LAcycCom" into the folder PLC datatypes
13. Copy the folder ”LMCSINA_Types" from "LMCSINA components" into the
folder PLC datatypes
14. Copy the function block "LMCSINA_FlyingSawFB" from "LMCSINA
components"  "LMCSINA_Blocks" to the PLC program blocks
NOTICE Avoid creating an invalid array of structs!

Problem: If a data type/block is transferred into the PLC, and is compiled before
accepting the PLC variables/user constants provided, then an invalid array with
"0" structures is created.
Remedy: The PLC variables must be completely accepted before compiling the
PLC/program. This is necessary, as in the data types/blocks used, array limits
are defined based on constants.
Calling block LMCSINA_FlyingSawFB

 Calling the axixFB "LMCSina_FlyingSawFB" with an instance for each flying
saw.
 Interconnecting inputs and outputs.
function block:
– enable
– hardwareID
(can be found under PLC variables – system constants)
– driveObjectNo
(can be found in the properties of the drive object in STARTER)
The block itself can now be simply compiled. Additional steps are required to use
acyclic communication (see the next chapter)
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 55
Figure 5-6
Integrating the acyclic communication
Note The function block can also be used without acyclic communication. The default
values in the FB correspond to the default values in the drive parameters.
1. Opening/dearchiving the global "LAcycCom" library

2. Copy all data types from LAcycCom  00_ Resource Management 
LAcycCom_Types to the PLC data types
3. Copy the PLC variables LAcycCom  00_Resource Management to the PLC
folder
4. Copy function block "LAcycCom_ResourceManager" from LAcycCom 
00_Resource Management to the folder of the control system used to the
program blocks
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 56
5. Copy the global data block "LAcycCom_RequestBuffer" from LAcycCom 

00_Resource Management to the PLC folder
Fig. 5-7
4
5
3
6. Copy function block "LAcycCom_ ReadDriveParams" from LAcycCom  01

Drives  LAcycCom_Blocks  PROFIDrive to the PLC folder
7. Copy all data types except "LAcycCom_typeSilentOperation" from LAcycCom
 01 Drives  LAcycCom_Types to PLC data types
Note Data type "LAcycCom_typeSilentOperation", as a result of the use in the

LMCSINA environment, is also supplied there – and must therefore be integrated
into the project ONCE. When not complied with, the TIA portal changes the
comments of a data type, which can result in problems when compiling.
PLC variables "LAcycCom_Drives" should also exist in the project, and should
therefore not be integrated another time.
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 57
Fig. 5-8
8. Call function blocks "LAcycCom_ResourceManager" and

"LAcycCom_ReadDriveParams" in the (same) program block

9. Interconnect LAcycCom_RequestBuffer to input "globalBuffer" of
"LAcycCom_ResourceManager" block
10. Activation of LAcycCom_ResourceManager at input "enable"
11. Interconnect LAcycCom_RequestBuffer at input "globalBuffer" of block
"LAcycCom_ReadDriveParams"
12. Interconnect the data area "statAcyclicData" from the instance DB of the cross-
cutter at input "dataset" of block "LAcycCom_ReadDriveParams"
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 58
Figure 5-9
LMCSINA
Entry-ID: 109479491, V3.0, 03/2018 59
Fig. 5-10
Note Block LDPV1_Buffermanager must be released at input "enable".

Block LDPV1_ReadParameters is exclusively controlled here using input
"dataset".
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018 60
5.3 LMCSINA_FlyingSawFB interfaces

5.3.1 Block inputs
Table 5-1
type value
enable Bool false TRUE: Enable functionality of FB; 0: Disable
ackError Bool FALSE Rising edge: Acknowledge drive faults
enableAxis Bool FALSE Rising edge: Enable axis; Falling edge: Disable
axis
axisVelocity Real 100000.0 Maximum positioning velocity [mm/min]
axisAcceleration Real 5000.0 Maximum acceleration for Acceleration
positioning/jogging [mm//s²]
jogPositive Bool FALSE TRUE: Jog FWD
jogNegative Bool FALSE TRUE: Jog BWD
jogVelocity Real 1000.0 Jog velocity [mm/min]
traverseToMaintenance Bool false Rising edge: Traverse to maintenance position
maintenancePosition Real 0.0 Maintenance position [mm]
homing Bool FALSE TRUE: enable homing
homingMode UInt 1 Selection of Homing Mode: 0: no homing; 1:
active homing; 2: active homing, without BERO;
3:active homing, BWD; 4: active homing, BWD,
without BERO; 5: active homing, negative flag; 6:
active homing, negative flag, without BERO; 7:
active homing, negative flag, BWD, without

BERO; 8: active homing, negative flag, BWD,
without BERO; 10: flying homing
enableCuttingOperation Bool false TRUE: enable cutting operation – traverse to
starting position
enableCut Bool false TRUE or rising edge: start cut
cuttingMode USInt 2 Selection of cutting mode: 0: no cut; 1: immediate
continuous cutting; 2: continuous cutting; 3:
immediate test cut; 4: immediate test cut; 5:
immediate single cut; 6: single cut
formatLength Real 1000.0 Format length [mm]
knifeAtTop Bool TRUE TRUE: Feedback signal for Knife/saw at the top
inhibitAutoReturn Bool false TRUE: Only return on command
returnPositioning Bool false Rising edge: Return positioning with dynamic
response
actClampFunction Bool false TRUE: Activate clamping function
actGapFunction Bool false TRUE: Enable create gap mode
createGapTrigger Bool false Rising edge: Trigger create gap
enableSWLimit Bool false TRUE: Activate monitoring software limit switch
disableHWLimit Bool false TRUE: Deactivate monitoring hardware limit
switch
ackHWLimit Bool false Rising edge: Acknowledge hardware limit switch
printMarkCorrection Bool false TRUE: Enables printmark sensing
distancePrintMarkCut Real 0.0 Distance, print mark cut variable [mm]
counterReset Bool false Rising edge: Material counter reset
0: no reading or writing; 1: read config data from
readWriteConfigData USInt 0 drive
Hardware identifier (see for example system
hardwareID HW_IO 16#0 constants – PLC)
Drive object number (see for example
driveObjectNo USInt 0 communication overview Starter – DRIVE)
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018
Values of the "homingMode" input

Table 52
homing Designation select using start disable select
Mode homing negative direction BERO flying
flag BWD homing
p21630 p21634 p21635 p21636 p21643
0 no homing x
1 active homing x
2 active homing, without x x
BERO
3 active homing, BWD x x
4 active homing, BWD, x x x
without BERO
5 active homing, negative x x
flag
flag, without BERO
flag, BWD
8 active homing, negative x x x x
flag, BWD, without BERO
10 flying homing x
Values of the "cuttingMode" input

Table 5-3
cuttingMode Meaning
0 no cut
1 immediate continuous cutting
2 continuous cutting
3 immediate test cut
4 test cut
5 immediate single cut
6 single cut
5.3.2 Block outputs
Table 5-4
type value
TRUE: FB is working and new output values can
busy Bool false be expected
valid Bool false TRUE: Valid set of outputs available at the FB
Rising edge informs that an error occurred during
error Bool false the execution.
axisError Bool FALSE TRUE: Drive error or application error
axisEnabled Bool FALSE TRUE: Axis is in operation
axisHomed Bool false TRUE: axis is homed
axisMoveFWD Bool false TRUE: axis traverses forward
axisMoveBWD Bool false TRUE: axis traverses backward
targetReached Bool false TRUE: target position reached
joggingActive Bool false TRUE: jogging active
posToMaintenanceActive Bool false TRUE: positioning to maintenance position active
homingActive Bool false TRUE: homing active
flyingHomingActive Bool false TRUE: flying homing active
cuttingEnabled Bool false TRUE: cutting operation enabled
cutPossible Bool false TRUE: cut possible
axisInSyncMaterial Bool false TRUE: axis synchronized to the material
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018

type value
axisInStartPosition Bool false TRUE: axis is located at the starting position
softwareLimitActive Bool false TRUE: software limit switch actuated
hardwareLimitActive Bool false TRUE: hardware limit switch actuated
actualPosition Real 0.0 Actual position [mm]
actualVelocity Real 0.0 Actual velocity [mm/min]
actualFormatLength Real 0.0 Actual format length [mm]
numberOfCuts DInt 0 Number of cuts
load Real 0.0 Actual torque in % of nominal torque
actualAlarmCode Word 16#0 Displays the code of the last alarm that occurred.
actualFaultcode Word 16#0 Displays the code of the oldest active fault.
#STATU
S_NO_C
status Word ALL Current status of FB
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018
5.3.3 Value overview for the output status
Table 5-5
Value Meaning
16#7101 jog velocity at limit
16#7102 positioning velocity at limit
16#7103 compensation velocity at limit
16#7110 positioning acceleration at limit
16#7111 compensation acceleration at limit
16#7200 acyclic command busy
16#7201 acyclic command busy and drive fault active
16#7202 acyclic command done
16#7203 acyclic command done and drive fault active
16#8210 homing mode not valid

16#8213 cutting mode not valid
16#8214 format length not valid
16#8215 approach direction not valid
16#8400 drive alarm active

16#8401 drive fault active
16#8402 DCC group fault active
16#8410 fine resolution not valid
16#8600 DPRD_DAT fault active

16#8610 DPWR_DAT fault active
16#8621 acyclic command error

16#8622 acyclic command error and drive fault active
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018
5.4 Operation
5.4.1 Enabling the block
The block must be enabled with "enable". Status 7000H means that the block is not
computed. Status 7001H is output at the first call.
5.4.2 Reading configuration data
Input "readWriteConfigData" must be set to 1 to read out configuration data from

the drive. The task is started when the status at the input changes.
The absolute and/or the maximum values of the dynamic data are read out.
The values must be read out if the following parameters are changed in the drive.
Alternatively, the values can be manually adapted in the instance DB.
The following parameters are read out:
Fig. 5-11
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018
6 LMCSINA_WinderFB in TIA Portal
6 LMCSINA_WinderFB in TIA Portal

The description for implementation and use can be found in the DCC winder
application documentation.
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018
7 LMCSINA_LineTensionControlFB in TIA Portal
7 LMCSINA_LineTensionControlFB in TIA
Portal
The description for implementation and use can be found in the DCC line tension
control application documentation.
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018
8 LMCSINA_TraversingDriveFB im TIA Portal
8 LMCSINA_TraversingDriveFB im TIA Portal

The function block LMCSINA_TraversingDriveFB in this version is only available
untested and undocumented. For help please contact the stated Application
Support address.
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018
9 Appendix
9 Appendix
9.1 Service and Support
Industry Online Support
Do you have any questions or need assistance?
Siemens Industry Online Support offers round the clock access to our entire
service and support know-how and portfolio.
The Industry Online Support is the central address for information about our
products, solutions and services.
Product information, manuals, downloads, FAQs, application examples and videos
– all information is accessible with just a few mouse clicks at:
https://support.industry.siemens.com
Technical Support
The Technical Support of Siemens Industry provides you fast and competent
support regarding all technical queries with numerous tailor-made offers
– ranging from basic support to individual support contracts. You send queries to
Technical Support via Web form:
www.siemens.com/industry/supportrequest
SITRAIN – Training for Industry

With our globally available training courses for our products and solutions, we help
you achieve with practical experience, innovative learning methods and a concept
that’s tailored to the customer’s specific needs.
For more information on our offered trainings and courses, as well as their
locations and dates, refer to:
www.siemens.com/sitrain
Service offer
Our range of services includes the following:
 Plant data services
 Spare parts services
 Repair services
 On-site and maintenance services
 Retrofitting and modernization services
 Service programs and contracts
You can find detailed information on our range of services in the service catalog:
https://support.industry.siemens.com/cs/sc
Industry Online Support app

You will receive optimum support wherever you are with the "Siemens Industry
Online Support" app. The app is available for Apple iOS, Android and Windows
Phone:
https://support.industry.siemens.com/cs/ww/en/sc/2067
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018
9 Appendix
9.2 Application Support

Siemens AG
Digital Factory Division
Factory Automation
Production Machines
DF FA PMA APC
Frauenauracher Str. 80
91056 Erlangen, Germany
mailto: tech.team.motioncontrol@siemens.com
9.3 Links and Literature

Table 9-1
No. Topic
\1\ Siemens Industry Online Support
https://support.industry.siemens.com
\2\ Link to this entry page of this application example
\3\
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018
9 Appendix
9.4 Change documentation

Table 9-2
Version Date Modification
V1.0 09/2015 First edition
V2.2 12/2015 Second edition
V2.3 04/2016 Third edition
V2.4 02/2017  Bug fixing regarding comments on Winder FB
 Function blocks for synchronism applications V4.0 are
added (LMCSINA_MeasuringWheel,
LMCSINA_SpeedAxis)
 Bug fixing regarding positioning direction in
LMCSINA_VirtualMaster function block
V2.4.1 06/2017  Bug fixing in the blocks LMCSINA_CrossCutterFB and
LMCSINA_FlyingSawFB:
When disabling the enable input the control signals of
the controlled axis are disabled, too (OFF1 reaction).
To restart the axis it is necessary to set the enable
input first and then create a positive edge at the
enableAxis input.
Previous behavior: The axis stayed in control when
disabling the enable input, but couldn't be controlled by
the block any longer.
V2.5 11/2017  LMCSINA_LineTensionControlFB added

V3.0 03/2018 The blocks for the synchronism applications <= V4.x were
deleted from the library
Instead the reworked Basic and Extended blocks for the
snychronism applications >= V5.1 were included
The block LMCSINA_TraversingDriveFB to control the DCB
traverser was included
Bugfixing at WinderConfigDB (comment for winding type
corrected)
LMCSINA
Beitrags-ID: 109479491, V3.0, 03/2018

LMCSINA V3 0 en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

LMCSINA V3 0 en

Uploaded by

Copyright:

Library Motion

3.3.1 Interfaces of LMCSINA_BasicSync FB .............................................. 28

9.1 Service and Support ........................................................................... 69

1.1 General structure of the library

1.2 Content of the application folders

LMCSINA_BasicSync: This FB is used for controlling per one following axis in

LMCSINA_BasicMeasuringWheel: This FB is optional and therefore not

LMCSINA_BasicVirtualMaster: This FB is optional and therefore not mandatory

LMCSINA_ExtendedCamFunctions: This FB is optional and therefore not

LMCSINA_ExtendedCoupleFunctions: This FB is optional and therefore not

LMCSINA_ExtendedOffsetFunctions: This FB is optional and therefore not

LMCSINA_SpeedAxis: This FB is optional and therefore not mandatory to realize

1.2.2 Cross Cutter

The subfolder "Necessary components from LAcycCom" contains some mandatory

1.2.3 Flying Saw

The subfolder "Necessary components from LAcycCom" contains some mandatory

1.2.4 Line Tension Control

The subfolder "Necessary components from LAcycCom" contains some mandatory

The subfolder "Necessary components from LAcycCom" contains some mandatory

Basic configuration steps

konnte nicht gefunden werden.)

2.2 Configuring the communication

Telegrams for position controlled axes

The configuration of speed-controlled leading axes is different and is described in

the next chapter “Communication for speed-controlled leading axes”.

For all synchronism axes: Input data = 28; Output data = 20

NOTICE Undesirable axis motion as a result of incorrect telegram settings

Telegram for speed-controlled leading axes

An example configuration could look as follows:

2.2.2 Creating the telegram interconnections

Script integrated in Starter

 Follow the instructions of the script

Using the script integrated in the project

 Import the interconnection script (*.xml)

 "Accept and execute" the script

 Follow the instructions of the script

2.2.3 Setting the user-defined GSDML for the TIA Portal

3 LMCSINA synchronism FBs

Installing the GSDML file generated in the TIA Portal

Finding the GSDML in the hardware catalog

3.2 Commissioning steps

Integrating the drive

 Integrating the SINAMICS drive into the network view

Integrating the LMCSINA library

 Copy all necessary control blocks from the folder "01_Synchronism

Calling the block LMCSINA_BasicSync

Call the FB "LMCSINA_BasicSync" with an instance for each synchronous

Note The following inputs are mandatory to interconnect:

Calling the block LMCSINA_BasicVirtualMaster

Note The following inputs are mandatory to interconnect:

Calling the block LMCSINA_BasicMeasuringWheel

Note The following inputs are mandatory to interconnect:

Calling the block LMCSINA_SpeedAxis

Calling the addon block LMCSINA_ExtendedCamFunctions

Note The following inputs are mandatory to interconnect:

Calling the addon block LMCSINA_ExtendedCoupleFunctions

Note The following inputs are mandatory to interconnect:

(the block is only calculated if it is TRUE)

Calling the addon block LMCSINA_ExtendedOffsetFunctions

Note The following inputs are mandatory to interconnect:

2: Start absolute encoder adjustment

Designation Type Data type Description

started by the input "startPositioning"

Truth table for the inputs compensationFwd (here

Designation Type Data type Description