FAST - TM Flying Saw - v7-0 - EN

FAST Application Software
Technology
module
Flying Saw ________________________________ Reference Manual EN
Ä.[zWä
13588954
L
Contents
________________________________________________________________
1 About this documentation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 3

1.1 Document history _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 5
1.2 Conventions used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 6
1.3 Definition of the notes used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 7
2 Safety instructions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 8
3 Functional description for the "Flying Saw" _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 10

3.1 Overview of the functions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 12
3.2 Important notes on how to operate the technology module _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 13
3.3 L_TT1P_FlyingSaw[Base/State] function block _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 15
3.3.1 Inputs and outputs _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 16
3.3.2 Inputs _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 16
3.3.3 Outputs _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 19
3.3.4 Parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 21
3.4 State machine _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 24
3.5 Signal flow diagrams _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 26
3.5.1 Structure of the signal flow _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 27
3.5.2 Structure of the access points _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 28
3.6 Manual jog (jogging) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 29
3.7 Homing _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 29
3.8 Setting motion profiles (linear/S-ramps) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 30
3.9 First synchronisation of the saw carriage to the material speed _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 31
3.10 Length-controlled operation (cutting of relative product lengths) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 34
3.11 Mark-controlled operation (cutting to position markers) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 37
3.12 Separation of cut material (execute gap) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 39
3.13 Restoring the target position _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 40
3.14 Deleting the mark stack _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 43
3.15 Moving to the parking position _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 45
3.16 Window for following error monitoring _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 47
3.17 CPU utilisation (example Controller 3231 C) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 49
Index _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 50
Your opinion is important to us _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 51
2 Lenze · Technology module | Flying Saw · Reference Manual · DMS 7.0 EN · 12/2019 · TD06
1 About this documentation
________________________________________________________________

This documentation ...
• contains detailed information on the functionalities of the "Flying Saw" technology module;
• is part of the "Controller-based Automation" manual collection. It consists of the following sets
of documentation:
Documentation type Subject

Product catalogue Controller-based Automation (system overview, sample topologies)
Lenze Controller (product information, technical data)
System manuals Visualisation (system overview/sample topologies)
Communication manuals Bus systems
Online helps • Controller-based Automation EtherCAT®
• Controller-based Automation CANopen®
• Controller-based Automation PROFIBUS®
• Controller-based Automation PROFINET®
Reference manuals Lenze Controllers:
Online helps • Controller 3200 C
• Controller c300
• Controller p300
• Controller p500
Software manuals Lenze Engineering Tools:
Online helps • »PLC Designer« (programming)
• »Engineer« (parameter setting, configuration, diagnostics)
• »VisiWinNET® Smart« (visualisation)
• »Backup & Restore« (data backup, recovery, update)
Lenze · Technology module | Flying Saw · Reference Manual · DMS 7.0 EN · 12/2019 · TD06 3
________________________________________________________________
More technical documentation for Lenze components

Further information on Lenze products which can be used in conjunction with Controller-based
Automation can be found in the following sets of documentation:
Planning / configuration / technical data Symbols:

 Product catalogues  Printed documentation
• Controller-based Automation  PDF file / online help in the Lenze
• Controllers engineering tool
• Inverter Drives/Servo Drives
Mounting and wiring
 Mounting instructions
• Controllers
• Communication cards (MC-xxx)
• I/O system 1000 (EPM-Sxxx)
• Communication modules
 Hardware manuals
Parameter setting / configuration / commissioning
 Online help/reference manuals
• Controllers
• I/O system 1000 (EPM-Sxxx)
 Online help/communication manuals
• Bus systems
• Communication modules
Sample applications and templates
 Online help / software and reference manuals
• i700 application sample
• Application Samples 8400/9400
• FAST Application Template Lenze/PackML
• FAST technology modules
 Tip!
Current documentation and software updates with regard to Lenze products can be found
in the download area at:
www.lenze.com
Target group
This documentation is intended for all persons who plan, program and commission a Lenze
automation system on the basis of the Lenze FAST Application Software.
1.1 Document history
________________________________________________________________
1.1 Document history
Version Description
7.0 12/2019 TD06 Error corrections & supplements
6.0 06/2019 TD29 General revisions
5.1 05/2017 TD17 Content structure has been changed.
General revisions
5.0 03/2016 TD17 New: Deleting the mark stack ( 43)
General revisions
New outputs: xInPosition, xPositioning
New parameter: lrBladeWidth
Chapter Moving to the parking position ( 45) has been revised.
Fig. State machine ( 45) has been revised
3.0 07/2015 TD17 Corrections and additions
Content structure has been changed.
2.0 05/2015 TD17 General editorial revision
Modularisation of the contents for the »PLC Designer« online help
1.0 04/2014 TD00 First edition
1.2 Conventions used
________________________________________________________________
1.2 Conventions used
This documentation uses the following conventions to distinguish between different types of
information:
Type of information Highlighting Examples/notes

Spelling of numbers
Decimal separator Point The decimal point is always used.
For example: 1234.56
Text
Program name »« »PLC Designer« ...
Variable names italics By setting bEnable to TRUE...
Function blocks bold The L_MC1P_AxisBasicControl function block ...
Function libraries The L_TT1P_TechnologyModules function library ...
Source code Font ...
"Courier new" dwNumerator := 1;
dwDenominator := 1;
...
Icons
Page reference ( 6) Reference to further information:
Page number in PDF file.
Variable names
The conventions used by Lenze for the variable names of Lenze system blocks, function blocks, and
functions are based on the "Hungarian Notation". This notation makes it possible to identify the
most important properties (e.g. the data type) of the corresponding variable by means of its name,
e.g. xAxisEnabled.
1.3 Definition of the notes used
________________________________________________________________
1.3 Definition of the notes used
The following signal words and symbols are used in this documentation to indicate dangers and
important information:
Safety instructions
Layout of the safety instructions:
 Pictograph and signal word!

(characterise the type and severity of danger)
Note
(describes the danger and gives information about how to prevent dangerous
situations)
Pictograph Signal word Meaning

Danger! Danger of personal injury through dangerous electrical voltage
 Reference to an imminent danger that may result in death or serious personal injury
if the corresponding measures are not taken.
Danger! Danger of personal injury through a general source of danger
 Reference to an imminent danger that may result in death or serious personal injury
if the corresponding measures are not taken.
Stop! Danger of property damage
 Reference to a possible danger that may result in property damage if the
corresponding measures are not taken.
Application notes
Pictograph Signal word Meaning

Note! Important note to ensure trouble-free operation

Tip! Useful tip for easy handling

Reference to another document

2 Safety instructions
________________________________________________________________
Please observe the safety instructions in this documentation when you want to commission an
automation system or a plant with a Lenze Controller.
 The device documentation contains safety instructions which must be observed!

Read the documentation supplied with the components of the automation system
carefully before you start commissioning the Controller and the connected devices.
 Danger!
High electrical voltage
Injury to persons caused by dangerous electrical voltage
Possible consequences
Death or severe injuries
Protective measures
Switch off the voltage supply before working on the components of the automation
system.
After switching off the voltage supply, do not touch live device parts and power
terminals immediately because capacitors may be charged.
Observe the corresponding information plates on the device.
 Danger!
Injury to persons
Risk of injury is caused by ...
• unpredictable motor movements (e.g. unintended direction of rotation, too high
velocities or jerky movement);
• impermissible operating states during the parameterisation while there is an active
online connection to the device.
Possible consequences
Death or severe injuries
Protective measures
• If required, provide systems with installed inverters with additional monitoring and
protective devices according to the safety regulations valid in each case (e.g. law on
technical equipment, regulations for the prevention of accidents).
• During commissioning, maintain an adequate safety distance to the motor or the
machine parts driven by the motor.
________________________________________________________________
 Stop!
Damage or destruction of machine parts
Damage or destruction of machine parts can be caused by ...
• Short circuit or static discharges (ESD);
• unpredictable motor movements (e.g. unintended direction of rotation, too high
velocities or jerky movement);
• impermissible operating states during the parameterisation while there is an active
online connection to the device.
Protective measures
• Always switch off the voltage supply before working on the components of the
automation system.
• Do not touch electronic components and contacts unless ESD measures were taken
beforehand.
• If required, provide systems with installed inverters with additional monitoring and
protective devices according to the safety regulations valid in each case (e.g. law on
technical equipment, regulations for the prevention of accidents).
3 Functional description for the "Flying Saw"
________________________________________________________________
 Inverter Drive
 Mark sensor (touch probe sensor)
 Feeding rollers
 Material web
 Detection of the master speed
 Negative hardware limit switch
 Saw carriage
 Positive hardware limit switch
 Motor and gearbox
[3-1] Typical mechanics of the technology module
________________________________________________________________
The flying saw provides the application of a machining process (e.g. sawing process, glue
application) to material that is continuously passing through. A typical flying saw process is divided
into the following motion stages:
1. Waiting for the start signal for synchronisation:

The drive is in the home position and is waiting for the start
signal for synchronisation with the material passing
through.
2. Synchronisation with material speed:
The drive is synchronised with the speed of the web at the
acceleration ramp specified. When the acceleration path
has been passed through, the tool slide reaches position
synchronicity with the material. At the machining unit, a
"Synchronicity reached" status signal is set.
3. Synchronous run of the web:
During the synchronous run with the material web, the
product is machined (e.g. sawing process, glue application).
When the machining process has been completed, the
synchronous movement to the material web can be
cancelled.
4. Approaching the new machining position:
Completion of synchronous operation is initiated by an
external "Machining process completed" control signal. The
drive stops the synchronous movement to the material web
and initiates the reversing process to the next machining
position.
The "Flying saw" technology module offers the following functionalities:

• In the "Base" version, the technology module can only operate in a length-controlled manner.
The saw carriage is synchronised to the material speed.
• The "State" version provides an extended function range of the "Base" version:
The State version additionally provides mark-controlled operation, the recovery of the target
position, travelling to a parking position, and following error monitoring.
Overview of the functions ( 12)
3.1 Overview of the functions
________________________________________________________________
3.1 Overview of the functions
In addition to the basic functions for operating the L_MC1P_AxisBasicControl function block, the
stop function and the holding function, the technology module offers the following functionalities
which are assigned to the "Base" and "State" versions:
Functionality Versions
Base State
Manual jog (jogging) ( 29)  
Homing ( 29)  
Setting motion profiles (linear/S-ramps) ( 30)  
First synchronisation of the saw carriage to the material speed ( 31)  
Length-controlled operation (cutting of relative product lengths) ( 34)  
Mark-controlled operation (cutting to position markers) ( 37) 
Restoring the target position ( 40) 
Deleting the mark stack ( 43) 
Moving to the parking position ( 45) 
Window for following error monitoring ( 47) 
 »PLC Designer« Online help

Here you will find detailed information on the L_MC1P_AxisBasicControl function block,
the stop function and the holding function.
3.2 Important notes on how to operate the technology module
________________________________________________________________
For the "Flying Saw" technology module, the axes have to be configured as follows:
• The master axis has to be a rotary axis.
• The slave axis has to be a linear axis.
Go to the »PLC Designer« and set the corresponding machine measuring system for each axis
under the Settings tab:
During the cutting process the master axis must only move in positive direction.
In the application, the mounting direction must also be set so that the master axis only moves
in positive direction.
Setting of the operating mode

The operating mode for the slave axis has to be set to "cyclically synchronous position" (csp) because
the axis is led via the master position value.
________________________________________________________________
Controlled start of the axes

Motion commands that are set in the inhibited axis state (xAxisEnabled = FALSE) after enable
(xRegulatorOn = TRUE) must be activated again by a FALSETRUE edge.
In this way it is prevented that the drive starts in an uncontrolled manner after controller enable.
 Example Manual jog (jogging) ( 29):

1. In the inhibited axis state (xAxisEnabled = FALSE), xJogPos is set to TRUE.
• xRegulatorOn = FALSE (axis is inhibited.)
==> "READY" state (xAxisEnabled = FALSE)
• xJogPos = TRUE (manual jog is to be executed.)
2. Enable axis.
• xRegulatorOn = TRUE
==> "READY" state (xAxisEnabled = TRUE)
3. Execute manual jog.
• xJogPos = FALSETRUE
==> "JOGPOS" state
3.3 L_TT1P_FlyingSaw[Base/State] function block
________________________________________________________________
The figure shows the relation of the inputs and outputs to the "Base" and "State" versions.
The additional inputs and outputs of the "State" version are shaded.
L_TT1P_FlyingSaw[Base/State]
Base
BOOL ⎯ xEnableInternalControl xInternalControlActive ⎯ BOOL
BOOL ⎯ xEnable eTMState ⎯ L_TT1P_States
scCtrl_ABC ⎯ scCtrlABC scStatusABC ⎯ scStatus_ABC
BOOL ⎯ xResetError xError ⎯ BOOL
BOOL ⎯ xRegulatorOn xWarning ⎯ BOOL
BOOL ⎯ xStop eErrorID ⎯ L_IE1P_Error
BOOL ⎯ xHalt scErrorInfo ⎯ L_TT1P_scErrorInfo
L_TT1P_scPar_FlyingSaw [Base/ ⎯ scPar xAxisEnabled ⎯ BOOL
State]
AXIS_REF ⎯ MasterAxis scSignalFlow ⎯ L_TT1P_scSF_FlyingSaw [Base/

State]
AXIS_REF ⎯ SlaveAxis xDone ⎯ BOOL

L_TT1P_scAP_FlyingSaw [Base/ ⎯ scAccessPoints xBusy ⎯ BOOL
State]
BOOL ⎯ xJogPos xIsHomed ⎯ BOOL

BOOL ⎯ xJogNeg xHwLimitSwitchNeg ⎯ BOOL
BOOL ⎯ xHomeExecute xHwLimitSwitchPos ⎯ BOOL
BOOL ⎯ xHomeAbsSwitch xSwLimitEnabled ⎯ BOOL
BOOL ⎯ xEnableHWLimit xSwLimitSwitchActive ⎯ BOOL
BOOL ⎯ xHWLimitPos xSynchronised ⎯ BOOL
BOOL ⎯ xHWLimitNeg xAccDecSync ⎯ BOOL
BOOL ⎯ xStartFlyingSaw xInPosition ⎯ BOOL
BOOL ⎯ xSyncInInstant xPositioning ⎯ BOOL
BOOL ⎯ xExecuteNextCut lrActPos ⎯ LREAL
BOOL ⎯ xExecuteGap lrActVel ⎯ LREAL
LREAL ⎯ lrCuttingLength lrActFollowingError ⎯ LREAL
BOOL ⎯ xSetMaterialCounter lrMaterialCounter ⎯ LREAL
lrTargetPos ⎯ LREAL
lrCutGap ⎯ LREAL
State
BOOL ⎯ xMoveToParkPos byRemainMarkStack ⎯ BYTE
BOOL ⎯ xResumeTargetPos
BOOL ⎯ xResetMarkStack
BOOL ⎯ xMarkReceive
LREAL ⎯ lrActMarkPosIn
________________________________________________________________
3.3.1 Inputs and outputs
Designator Description Available in

Data type version
Base State
MasterAxis Reference to the master axis (master axis)  
AXIS_REF
SlaveAxis Reference to the slave axis  
AXIS_REF
3.3.2 Inputs

Data type version
Base State
xEnableInternalControl TRUE In the visualisation, the internal control of the axis can be  
BOOL selected via the "Internal Control" axis.
xEnable Execution of the function block  
BOOL TRUE The function block is executed.
FALSE The function block is not executed.
scCtrlABC Input structure for the L_MC1P_AxisBasicControl function block  
scCtrl_ABC • scCtrlABC can be used in "Ready" state.
• If there is a request, the state changes to "Service".
• The state change from "Service" back to "Ready" takes place if
there are no more requests.
xResetError TRUE Reset axis error or software error.  
BOOL
xRegulatorOn TRUE Activate controller enable of the axis (via the MC_Power  
BOOL function block).
xStop TRUE Cancel the active movement and brake the axis to a  
BOOL standstill with the deceleration defined via the lrStopDec
parameter.
• The state changes to "Stop".
• The STOP state is exited if (Not xStop AND Not xHalt)
AND eAxisState = StandStill
• The input is also active with "Internal Control".
xHalt TRUE Cancel the active movement and brake the axis to a  
BOOL standstill with the deceleration defined via the lrHaltDec
parameter.
• The state changes to "Stop".
• The technology module remains in the "Stop" state as
long as xStop is set to TRUE (or xHalt = TRUE).
scPar The parameter structure contains the parameters of the technology  
L_TT1P_scPar_FlyingSaw [Base/State] module.
The data type depends on the version used (Base/State).
scAccessPoints Structure of the access points  
L_TT1P_scAP_FlyingSaw [Base/State] The data type depends on the version used (Base/State).
xJogPos TRUE Traverse axis in positive direction (manual jog).  
BOOL If xJogNeg is also TRUE, the traversing direction selected
first remains set.
xJogNeg TRUE Traverse axis in negative direction (manual jog).  
BOOL If xJogPos is also TRUE, the traversing direction selected
first remains set.
________________________________________________________________

Data type version
Base State
xHomeExecute The input is edge-controlled and evaluates the rising edge.  
BOOL FALSE Start homing.
TRUE The function is aborted via the xStop input.
xHomeAbsSwitch TRUE Connection for reference switch:  
BOOL For homing modes with a reference switch, connect this
input to the digital signal which maps the state of the
reference switch.
xEnableHWLimit TRUE The evaluation of the travel range limit switch (hardware  
BOOL limit switch) is activated.
xHWLimitPos Positive hardware limit switch  
BOOL Connect this input to the corresponding digital input that is
connected to the limit switch.
TRUE The positive hardware limit switch has been reached or
approached.
• The xHwLimitSwitchPos output is also set to TRUE.
• The axis is brought to a standstill with the deceleration
in the alrStopDec parameter.
• The state changes to "ERROR" with the error message
’20500’ (HWLimitPos).
xHWLimitNeg Negative hardware limit switch  
BOOL Connect this input to the corresponding digital input that is
connected to the limit switch.
TRUE The negative hardware limit switch has been reached or
approached.
• The xHwLimitSwitchNeg output is also set to TRUE.
• The axis is brought to a standstill with the deceleration
in the alrStopDec parameter.
’20501’ (HWLimitNeg).
xStartFlyingSaw TRUE The "Flying Saw" technology module is activated.  
BOOL • Parameter xSyncFlyingSaw = TRUE:
The saw carriage is synchronised to the material
position.
• Parameter xSyncFlyingSaw = FALSE:
The saw carriage waits for a signal for synchronising to
the material position.
FALSE The saw carriage is disengaged from the material position
and brakes to a standstill.
• If the saw carriage is in waiting position, it is only
disengaged.
• xParkPos parameter = TRUE: the saw carriage is
disengaged first and then travels to its parking position.
xSyncInInstant The input is edge-controlled and evaluates the rising edge.  
BOOL FALSE The saw carriage is synchronised to the material position.
TRUE This can occur in the parking position or during a return.
xExecuteNextCut The input is edge-controlled and evaluates the rising edge.  
BOOL FALSE The saw carriage moves to the next machining position.
TRUE
xExecuteGap The input is edge-controlled and evaluates the rising edge.  
BOOL FALSE The saw carriage moves by the distance set in the lrGap
TRUE parameter. This distance is added to the relative travel way
(lrCuttingLength input).
lrCuttingLength Cutting length (relative positioning) or cutting position (absolute  
LREAL positioning)
• Unit: Units from the master axis (mm)
________________________________________________________________

Data type version
Base State
xSetMaterialCounter The input is edge-controlled and evaluates the rising edge.  
BOOL FALSE Sets the material position (lrMaterialCounter output) to
TRUE the value of the lrSetMaterialPos parameter.
xMoveToParkPos The input ... 
BOOL • is only evaluated if the technology module is in "READY" state;
• is edge-controlled and evaluates the rising edge.
FALSE The saw carriage is driven to the parking position
TRUE (lrParkPosition parameter).
xResumeTargetPos The input is edge-controlled and evaluates the rising edge. 
BOOL FALSE The saw carriage is moved to the position of the lrTargetPos
TRUE output.
xResetMarkStack The input is edge-controlled and evaluates the rising edge. 
BOOL FALSE All marks on the mark stack are removed.
TRUE If this input is confirmed during the clutched-in state, the
axis travels automatically to the waiting position
(lrLowerLimit parameter).
xMarkReceive TRUE A touch probe mark has been detected in the connected 
BOOL touch probe sensor.
lrActMarkPosIn Current position of the touch probe mark with regard to the axis 
LREAL reference used.
• Unit: units
________________________________________________________________
3.3.3 Outputs

Data type version
Base State
xInternalControlActive TRUE The internal control of the axis is activated via the  
BOOL visualisation.
(xEnableInternalControl input = TRUE)
eTMState Current state of the technology module  
L_TT1P_States State machine ( 24)
scStatusABC Structure of the status data of the L_MC1P_AxisBasicControl  
scStatus_ABC function block
xError TRUE There is an error in the technology module.  
BOOL
xWarning TRUE There is a warning in the technology module.  
BOOL
eErrorID ID of the error or warning message if xError = TRUE or  
L_IE1P_Error xWarning = TRUE.
Possible error or warning messages (IDs):
17125: The position of the slave axis exceeds the set
"lrUpperLimit" parameter.
17126: The position of the slave axis falls below the set
"lrLowerLimit" parameter.
17127: The target position to be approached exceeds the set
"lrUpperLimit" parameter.
17128: The position detected by the mark sensor is out of the valid
range.
"FAST technology modules" reference manual:
Here you can find information on further error or warning messages.
scErrorInfo Error information structure for a more detailed analysis of the error  
L_TT1P_scErrorInfo cause
scSignalFlow Structure of the signal flow  
L_TT1P_scSF_FlyingSaw [Base/State] The data type depends on the version used (Base/State).
Signal flow diagrams ( 26)
xAxisEnabled TRUE The axis is enabled.  
BOOL
xDone TRUE The request/action has been completed successfully.  
BOOL
xBusy TRUE The request/action is currently being executed.  
BOOL
xIsHomed TRUE The axis has been referenced (reference known).  
BOOL
xHwLimitSwitchNeg TRUE The negative hardware limit switch has been reached or  
BOOL approached.
• The xHwLimitNeg input has to be connected to the
digital input that is connected to the limit switch.
• The xHWLimitNeg input is also set to TRUE.
• The drive is brought to a standstill with the deceleration
set in the lrStopDec parameter.
’20501’ (HWLimitNeg).
________________________________________________________________

Data type version
Base State
xHwLimitSwitchPos TRUE The positive hardware limit switch has been reached or  
BOOL approached.
• The xHwLimitPos input has to be connected to the
digital input that is connected to the limit switch.
• The xHWLimitPos input is also set to TRUE.
• The drive is brought to a standstill with the deceleration
’20500’ (HWLimitPos).
xSwLimitEnabled TRUE Activate the monitoring of the software limit positions.  
BOOL
xSwLimitSwitchActive TRUE A software limit position has been reached or exceeded.  
BOOL • The drive is brought to a standstill with the deceleration
• The state changes to "ERROR" with error message
'20306' (SWLimitPos) or '20307' (SWLimitNeg).
xSynchronised TRUE The axis is synchronised to the cam.  
BOOL
xAccDecSync TRUE The synchronisation function is active.  
BOOL The axis is synchronised or desynchronised (clutch opens or
closes).
xInPosition TRUE The axis has reached the parking position.  
BOOL
xPositioning TRUE The axis travels to the parking position  
BOOL
lrActPos Current position  
LREAL • Unit: units
lrActVel Current velocity  
LREAL • Unit: units/s
lrActFollowingError Current following error  
LREAL • Unit: units/s2
lrMaterialCounter Continuous material position  
lrTargetPos Target position of the saw carriage  
lrCutGap Distance between two cutting positions  
byRemainMarkStack Display of the positions still available (max. 15) on the mark stack 
BYTE
________________________________________________________________
3.3.4 Parameters
L_TT1P_scPar_FlyingSaw [Base/State]
The L_TT1P_scPar_FlyingSaw[Base/State] structure contains the parameters of the technology
module.

Data type version
Base State
lrStopDec Deceleration for the stop function and when hardware/software  
LREAL limit switches and the following error monitoring function are
triggered
• Unit: units/s2
• Initial value: 10000
lrStopJerk Jerk for the stop function and for the triggering of the hardware limit  
LREAL switches, software limit positions, and the following error
monitoring function
• Unit: units/s3
lrHaltDec Deceleration for the holding function  
LREAL Specification of the maximum speed variation which is to be used for
deceleration to standstill.
• Unit: units/s2
• Only positive values are permissible.
lrJerk Jerk for compensating a clutch or holding function  
lrJogJerk Jerk for manual jog  
lrJogVel Maximum speed to be used for manual jog.  
LREAL • Unit: units/s
lrJogAcc Acceleration for manual jog  
LREAL Specification of the maximum velocity variation which is to be used
for acceleration.
• Unit: units/s2
lrJogDec Deceleration for manual jog  
LREAL Specification of the maximum speed variation which is to be used for
deceleration to standstill.
• Unit: units/s2
lrHomePosition Home position for a reference run (homing)  
xUseHomeExtParameter Selection of the homing parameters to be used  
BOOL • Initial value: FALSE
FALSE The homing parameters defined in the axis data are used.
TRUE The scHomeExtParameter homing parameters from the
application are used.
scHomeExtParameter Homing parameters from the application  
L_MC1P_HomeParameter • Only relevant if xUseHomeExtParameter = TRUE.
________________________________________________________________

Data type version
Base State
scHomeExtTP Transfer of an external touch probe event  
MC_TRIGGER_REF • Only relevant for "external encoder" touch probe configuration.
• For describing the MC_TRIGGER_REF structure, see the
MC_TouchProbe function block.
lrSyncVel Additive velocity of the saw carriage during synchronisation (travel  
LREAL distance, approach target position again)
The set value is added to the velocity of the master axis.
• Unit: units/s
lrSyncAcc Maximum acceleration of the saw carriage when clutching in to the  
LREAL master value of the master axis
• Unit: units/s2
lrSyncDec Maximum deceleration of the saw carriage when declutching from  
LREAL the master value of the master axis
• Unit: units/s2
lrPosVel Maximum velocity of the saw carriage during positioning (travel to  
LREAL the next cutting position, positioning to parking position)
• Unit: units/s
lrPosAcc Maximum acceleration of the saw carriage during positioning (travel  
LREAL to the next cutting position, positioning to parking position)
• Unit: unit/s2
lrPosDec Maximum deceleration of the saw carriage during positioning  
LREAL (travel to the next cutting position, positioning to parking position)
• Unit: units/s2
lrSetMaterialPos Default value for the material counter  
LREAL The value of the material counter results from the value set here plus
the actual position of the saw carriage.
The value is accepted when a rising edge (FALSETRUE) is detected a
the xSetMaterialPos input.
• Unit: units
lrUpperLimit Upper travel range limit of the saw carriage  
lrLowerLimit Lower travel range limit of the saw carriage  
xSyncFlyingSaw Response of the "Flying Saw" technology module after switch-on  
BOOL (xStartFlyingSaw input = TRUE)
• Initial value: FALSE
FALSE The saw carriage is only synchronised with the material
position if the xSynxInInstant input detects a rising edge
(FALSETRUE).
TRUE The saw carriage is synchronised with the material position
immediately if the xStartFlyingSaw input is set to TRUE.
This can take place irrespective of the current saw carriage
position.
________________________________________________________________

Data type version
Base State
lrGap Distance to be travelled after a saw cut  
LREAL With length-controlled operation, the lrGap parameter is added to
the relative travel way (lrCuttingLength input).
The distance is travelled after a rising edge (FALSETRUE) at the
xExecuteGap input.
Length-controlled operation (cutting of relative product lengths)
( 34)
• Unit: units
lrBladeWidth Blade width of the saw blade  
LREAL The value is added to the cutting length in the operating mode
Length-controlled operation (cutting of relative product lengths)
( 34).
• Unit: units
xParkPos The parameter is evaluated by a falling edge at the input xStartFly- 
BOOL ingSaw
• Initial value: FALSE
TRUE The saw carriage is moved to the parking position, which is
defined in parameter lrParkPosition.
FALSE The saw carriage is brought to a standstill immediately.
lrParkPosition Parking position of the saw carriage if the xParkPos parameter is set 
LREAL to TRUE.
• Unit: units
lrMarkSensorPos Position of the touch probe sensor (relating to the measuring system 
LREAL of the saw carriage)
• Unit: units
eModeFlyingSaw Selection of the operating mode 
ENUM • Initial value: 0 (length-controlled operation)
0 Length-controlled operation (cutting of relative product
lengths) ( 34)
1 Mark-controlled operation (cutting to position markers)
( 37)
xPosInWindow Activation of the tolerance window for following error monitoring 
BOOL • Initial value: FALSE
TRUE The tolerance window (following error monitoring) is
activated.
lrPosInWindow Size of the tolerance window for following error monitoring 
lrTimePosInWindow Duration of stay of the following error inside the tolerance window 
LREAL • Unit: ms
3.4 State machine
________________________________________________________________
3.4 State machine
[3-2] State machine of the technology module
 A transition to the ERROR or STOP state is possible.

(*1 In the "Ready" state, xRegulatorOn has to be set to TRUE.
(*2 In the "ERROR" state, xResetError has to be set to TRUE in order to acknowledge and reset the errors.
3.4 State machine
________________________________________________________________
States of the eTMState output (L_TT1P_States)
No. L_TT1P_States Description

1 INIT Initialisation of the technology module active.
2 READY Technology module ready for operation.
3 HOMING Referencing active.
10 JOGGING Manual jog active.
11 JOGPOS Manual jog in positive direction active.
200 SAW_IN_PROCESS Cutting process active.
210 MOVE_TO_PARK_POS Movement to the parking position active.
996 STOP Stop/Halt active.
998 SERVICE The technology module is in service mode. The internal
L_MC1P_AxisBasicControl function block is controlled via the scCtrlABC
input structure. The status of the function block can be viewed via the
scStatusABC output structure.
999 ERROR Error state
1000 SYSTEMFAULT System fault
3.5 Signal flow diagrams
________________________________________________________________
The illustrations show the main signal flow of the functions implemented.
The signal flow of the additional functions such as "manual jog" is not displayed here.
[3-3] Signal flow: Flying Saw
________________________________________________________________
3.5.1 Structure of the signal flow
L_TT1P_scSF_FlyingSaw [Base/State]
The contents of the L_TT1P_scSF_FlyingSaw[Base/State] structure is read-only and offer a practical
diagnostics option within the signal flow (Signal flow diagrams ( 26)).

Data type version
Base State
IP01_xExecuteNextCut The input is edge-controlled and evaluates the rising edge.  
BOOL FALSE The saw carriage moves to the next machining position.
TRUE
IP02_lrCuttinglength Cutting length (relative positioning) or cutting position (absolute  
LREAL positioning)
IP03_lrLowerLimit Lower travel range limit of the saw carriage  
IP04_lrUpperLimit Upper travel range limit of the saw carriage  
IP05_eModeFlyingSaw Selection of the operating mode 
L_TT1P_eModesFlyingSaw • Initial value: 0 (length-controlled operation)
0 Length-controlled operation (cutting of relative product
lengths) ( 34)
1 Mark-controlled operation (cutting to position markers)
( 37)
MP01_lrSetMasterPos Set position of the master axis  
MP02_lrSetSlavePos Set position of the slave axis  
MP03_lrTotalCuttingLength Sum of the cut cutting lengths  
MP04_xPosSynchronised TRUE The setpoints of the master axis and the slave axis are  
BOOL synchronous.
MP05_wMarkInIndex Index of the incoming mark (touch probe) on the mark stack 
WORD
MP06_wMarkOutIndex Index of the mark (touch probe) to be called on the mark stack 
WORD
MP07_alrMarkPositionArray Memory of the detected position markers 
ARRAY [0..15] OF LREAL
MP08_alrTimeStampArray Memory of the time stamps corresponding to the position markers 
ARRAY [0..15] OF LREAL in MP07_alrMarkPositionArray
MP09_xMarkStackEmpty TRUE There is no valid mark on the mark stack anymore. 
BOOL
MP10_xMarkStackFull TRUE The mark stack is completely filled. 
BOOL The next mark detected overwrites the oldest mark entered
on the mark stack.
MP11_lrStackMarkPos Position of the mark currently output by the mark stack. 
OP01_lrMaterialCounter Continuous material position  
OP02_lrTargetPos Target position of the saw carriage  
________________________________________________________________
3.5.2 Structure of the access points
L_TT1P_scAP_FlyingSaw [Base/State]
The access points (AP) can be used to influence signals. In the initial state, the access points do not
have any effect.
Each access point acts as an alternative branch and is activated via an OR operation or a switch.

Data type version
Base State
AP01_xLoadTotalCutting Selection of a value for the sum of all lengths cut  
Length (MP03_lrTotalCuttingLength variable)
BOOL • Initial value: TRUE
TRUE The value in AP01_lrLoadTotalCuttingLength is
preselected.
AP01_lrLoadTotalCutting Value for the sum of all lengths cut (MP03_lrTotalCuttingLength
Length variable)
AP02_xLoadTargetPos Selection of a value for the target position of the saw carriage  
BOOL (lrTargetPos or OP02_lrTargetPos output)
The precondition for this is that the technology module is in the
"READY" state.
• Initial value: TRUE
TRUE The value in lrLoadTargetPos is preselected.
AP02_lrLoadTargetPos Value for the target position of the saw carriage (lrTargetPos or
LREAL OP02_lrTargetPos output)
• Unit: units
AP03_xRangeOfTolerance Activation of the tolerance range set under 
BOOL AP03_lrRangeOfTolerance
TRUE Tolerance range AP03_lrRangeOfTolerance is activated.
AP03_lrRangeOfTolerance Tolerance range which is put around the master value of the master
LREAL axis to ensure the synchronism with the saw carriage.
This is required in case of noisy master value signals.
3.6 Manual jog (jogging)
________________________________________________________________
3.6 Manual jog (jogging)
Precondition
• The technology module is in the "Ready" state.
• The slave axis is enabled (xRegulatorOn = TRUE).
Execution
For manual jog of the axis, the manual jog speed lrJogVel is used.
If the xJogPos input is TRUE, the axis is traversed in positive direction and if the xJogNeg input
is TRUE, the axis is traversed in negative direction. The axis is executed for as long as the input
remains set to TRUE.
The current travel command cannot be replaced by another jog command. Only if both inputs have
been reset, the State machine ( 24) changes to the "Ready" state again.
Parameters to be set
The parameters for the manual jog are located in the L_TT1P_scPar_FlyingSaw [Base/State] ( 21)
parameter structure.
lrJogVel : LREAL := 10; // Velocity [units/s]
lrJogAcc : LREAL := 100; // Acceleration [units/s^2]
lrJogDec : LREAL := 100; // Deceleration [units/s^2]
lrJogJerk : LREAL := 10000; // Jerk [units/s^3]
The parameter values can be changed during operation. They are accepted when the xJogPos or
xJogNeg input is set to TRUE again.
3.7 Homing
Precondition
• The slave axis is enabled (xRegulatorOn = TRUE).
Execution
Homing is started with a rising edge (FALSETRUE) at the xHomeExecute input. The axis will be
travelling until the home position is reached. After successful homing, the State machine ( 24)
changes back again to the "Ready" state.
The homing process is not interrupted if the xHomeExecute input is set to FALSE too early. The
function is aborted via the xStop input.
The parameters for homing are located in the L_TT1P_scPar_FlyingSaw [Base/State] ( 21)
parameter structure.
xUseHomeExtParameter : BOOL := FALSE;
lrHomePosition : LREAL := 0.0;
scHomeExtParameter : L_MC1P_HomeParameter;
scHomeExtTP : MC_TRIGGER_REF;
3.8 Setting motion profiles (linear/S-ramps)
________________________________________________________________
3.8 Setting motion profiles (linear/S-ramps)
The parameters for the motion profile of the saw carriage are located in the
L_TT1P_scPar_FlyingSaw [Base/State] ( 21) parameter structure.
lrJerk : LREAL := 100000; // units/s3;
lrSyncVel : LREAL := 3600; // units/s;
lrSyncAcc : LREAL := 10000; // units/s2;
lrSyncDec : LREAL := 10000; // units/s2;
lrPosVel : LREAL := 3600; // units/s;
lrPosAcc : LREAL := 10000; // units/s2;
lrPosDec : LREAL := 10000; // units/s2;
3.9 First synchronisation of the saw carriage to the material speed
________________________________________________________________
When the "flying saw" has been switched on by the xStartFlyingSaw input = FALSETRUE, there are
several possibilities of synchronising the saw carriage with the material speed:
A. xSyncFlyingSaw parameter = FALSE:
The saw carriage is only synchronised with the material position if the xSynxInInstant input
detects a rising edge (FALSETRUE).
This function can for example be used to carry out an initial top cut.
The initial top cut at the start of length-controlled operation can either be carried out when the
material web is at a standstill or if it is running.
[3-4] Example: Characteristic with xSyncFlyingSaw parameter = FALSE
________________________________________________________________
B. xSyncFlyingSaw parameter = TRUE:

The saw carriage is synchronised with the material position immediately if the
xStartFlyingSaw input is set to TRUE. This can take place irrespective of the current saw carriage
position.
[3-5] Example: Characteristic with xSyncFlyingSaw parameter = TRUE
C. eModeFlyingSaw = 1 parameter (mark-controlled operation):
 Note!
The mark-controlled operation is only possible in the State version of the technology
module.
The saw carriage is only synchronised with the material position if a mark has been detected at
the mark sensor connected (xMarkReceive input = TRUE).
________________________________________________________________
[3-6] Example: Characteristic with eModeFlyingSaw parameter = 1 (mark-controlled operation)
3.10 Length-controlled operation (cutting of relative product lengths)
________________________________________________________________
 Cutting length
[3-7] Cutting length with length-controlled operation
In length-controlled operation, the first machining process (top cut) starts in any position. Then all
subsequent saw cuts have the desired relative distance (cutting length) to the previous cut in each
case.
________________________________________________________________
[3-8] Example: Characteristic of length-controlled operation
In the time diagram in Fig. [3-8] three different saw cuts ΔS1 ... ΔS3 are carried out. After each cut a
specific distance (lrGap parameter) is run.
The movement from one machining position to the next one is carried out via a superimposed
relative positioning process. The positioning distance ΔS1 ... ΔS3 results from the cutting length at
the lrCuttingLength input added by the length of the distance run in the lrGap parameter. The
relative positioning process is initiated by a rising edge (FALSETRUE) at the xExecuteNextCut input.
The lrLowerLimit and lrUpperLimit parameters are used for setting the machining area of the saw
carriage. In the diagram above, the area outside these two limits is highlighted in red. When saw cut
ΔS3 is requested, it can be clearly seen that the target position (lrTargetPos output) is below the
lrLowerLimit limit. In this case, the saw carriage moves to the lower limit specified and waits until
the target position enters the operating range so that synchronisation with the target position can
then take place.
The areas highlighted in turquoise indicate when the saw carriage is synchronous to the material
position. In the example, the saw carriage is only synchronised to the material position when a new
target position is requested with the xExecuteNextCut input = TRUE or if a distance (lrGap
parameter) is travelled after the saw cut with the xExecuteGap input = TRUE.
________________________________________________________________
The parameters for the length-controlled operation are located in the L_TT1P_scPar_FlyingSaw
[Base/State] ( 21) parameter structure.
A new/changed cutting length with a rising edge (FALSETRUE) is accepted at the xExecuteNextCut
input.
For the time diagram in figure [3-8] ( 35), a sequence runs outside the technology module that
successively defines the following product lengths at the lrCuttingLength input:
• 500 [units]
• 250 [units]
• 1000 [units]
Furthermore the following parameter settings have been carried out:
lrLowerLimit : LREAL := 0;
lrUpperLimit : LREAL := 1000;
lrGap : LREAL := 50;
xSyncFlyingSaw : BOOL := TRUE;
3.11 Mark-controlled operation (cutting to position markers)
________________________________________________________________
 Mark sensor (touch probe sensor)

 Cutting mark
 Print image
 Position of the mark sensor (lrMarkSensorPos parameter)
 Lower travel range limit of the saw carriage (lrLowerLimit parameter)
 Cutting length (lrSetMaterialPos parameter)
 Upper travel range limit of the saw carriage (lrUpperLimit parameter)
[3-9] Cutting length for mark-controlled operation
Mark-controlled operation is used if the material already features partitions by position markers,
e.g. in the case of a print image. In this case, the saw cuts must not be placed arbitrarily on the
material, but must be executed in line with the position markers. An additional mark sensor that is
placed in a sufficient distance in front of the operating range of the saw detects the cutting
positions beforehand. These cutting positions are stored in a mark stack.
________________________________________________________________
[3-10] Example: Characteristic of mark-controlled operation
In the time diagram in fig. [3-10] three marks are detected in a row. The first mark starts the process.
During the machining phase (cutting and running the distance) of the first mark detected, two
further marks are detected which are stored on the mark stack. The next valid mark position is
approached with a rising edge (FALSETRUE) at the xExecuteNextCut input = TRUE.
3.12 Separation of cut material (execute gap)
________________________________________________________________
If there is no valid mark on the mark stack anymore, the saw carriage moves to the lower travel
range limit (lrLowerLimit parameter) and waits for the next mark.
The cutting length is the distance between the detected marks. As soon as the technology module
is switched on, the position at the lrActMarkPosIn input is converted to the setpoint position of the
saw carriage for each detected mark at the xReceiveMark input and stored on the mark stack. With
a rising edge (FALSETRUE) at the xExecuteNextCut input, it is possible to change over to the next
mark in the stack.
The parameters for the length-controlled operation are located in the L_TT1P_scPar_FlyingSaw
For the time diagram in figure [3-10] ( 38), the following parameters have been set:
eModeFlyingSaw : ENUM : = 1; // Mark controlled
lrSetMaterialPos : LREAL := 0;
lrLowerLimit : LREAL := 0;
lrUpperLimit : LREAL := 1000;
lrGap : LREAL := 50;
xSyncFlyingSaw : BOOL := FALSE;
3.12 Separation of cut material (execute gap)
This function is suitable for

• cut edge protection for delicate material.
• separating the cut material.
The xExecuteGap input serves to separate the cut material. Using this function, the saw carriage is
briefly moved oversynchronously in relation to the material before the saw blade is pulled out. In
this way, a gap forms between the cut edge and the saw blade which can be set via the lrGap
parameter. The gap serves to prevent marks from the saw blade on the cut edge.
3.13 Restoring the target position
________________________________________________________________
This function can be executed once when the sawing process has been started
(xStartFlyingSaw = TRUE) in order to restore a target position.
In length-controlled operation and in mark-controlled operation, the process for restoring the
target position is different. Furthermore it is checked in both operating modes whether the target
position requested is below the upper travel range limit (lrUpperLimit parameter).
Length-controlled operation
After a rising edge (FALSETRUE) at the xResumeTargetPos input, the target position (lrTargetPos
output) is approached again.
[3-11] Example: Characteristic for "Restoring the target position" in length-controlled operation
________________________________________________________________
Mark-controlled operation
In case of mark-controlled operation, only one valid mark can be restored. Here, the target position
(lrTargetPos output) has to be in front of the travel range limit (lrUpperLimit parameter).
If the target position has already exceeded the upper travel range limit, a rising edge (FALSETRUE)
at the xExecuteNextCut input serves to change over to the next mark in the mark stack. If no valid
mark is available in the stack, no target position is approached.
After a rising edge (FALSETRUE) at the xResumeTargetPos input, the target position is approached
again.
________________________________________________________________
[3-12] Example: Characteristic for "Restoring the target position" in mark-controlled operation
3.14 Deleting the mark stack
________________________________________________________________
With a rising edge (FALSETRUE) at the xResetMarkStack input, all marks stored on the mark stack
are deleted.
The byRemainMarkStack output shows how many marks the mark stack can take.
If the function is executed while the "flying saw" is in the synchronous state, (xStartFlyingSaw
input = TRUE), the saw carriage travels to the waiting position (lrLowerLimit parameter) and will be
synchronised with the next mark.
Both options are shown in the time diagram in figure [3-13] ( 44).
________________________________________________________________
[3-13] Example: "Delete mark stack" history
3.15 Moving to the parking position
________________________________________________________________
There are two options to approach the parking position:

A. "Flying Saw" is not active:
• A rising edge (FALSETRUE) at the xMoveToParkPos input causes a change from "Ready" to
"Move To Park Pos" and the saw carriage travels to the parking position set in the
lrParkPosition parameter.
B. "Flying Saw" is deactivated:
• The parameters lrParkPosition and xParkPos from the L_TT1P_scPar_FlyingSaw [Base/State]
( 21) parameter structure are set to TRUE.
• If then the xStartFlyingSaw input is set from TRUE to FALSE, the saw carriage travels to the
parking position set in the lrParkPosition parameter.
During positioning, the xPositioningoutput is = TRUE.
When the parking position has been reached, the output xInPosition is set = TRUE and the output
xPositioning is set = FALSE.
The parameters for travelling to the parking position are located in the L_TT1P_scPar_FlyingSaw
eModeFlyingSaw : ENUM : = 0; // Length controlled
xParkPos : BOOL := TRUE;
lrParkPosition : LREAL := 150; // units
________________________________________________________________
[3-14] Example: Characteristic for "Moving to parking position"
3.16 Window for following error monitoring
________________________________________________________________
This function checks whether the following error is to be found within a defined window within a
certain period. It is activated with the xPosInWindow parameter set to TRUE.
The window and the time are set via the parameters lrPosInWindow and lrTimePosInWindow from
the L_TT1P_scPar_FlyingSaw [Base/State] ( 21) parameter structure. As soon as the two setpoints
of the master and slave axis are synchronous and the following error is inside the set window, the
xSynchronised output is set = TRUE.
[3-15] Example: Characteristic of the following error monitoring
________________________________________________________________
The parameters for the following error monitoring are located in the L_TT1P_scPar_FlyingSaw
eModeFlyingSaw : ENUM : = 0; // Length controlled
xPosInWindow : BOOL := TRUE;
lrPosInWindow : LREAL := 0.5; // units
lrTimePosInWindow : LREAL := 50; // ms
3.17 CPU utilisation (example Controller 3231 C)
________________________________________________________________
3.17 CPU utilisation (example Controller 3231 C)
The following table shows the CPU utilisation in microseconds using the example of the 3231 C
controller (ATOM™ processor, 1.6 GHz).
Versions Wiring of the technology module CPU utilisation

Average Maximum peak
Base xEnable := TRUE; 40 μs 90 μs
xRegulatorOn := TRUE;
xStartFlyingSaw := TRUE;
xExecuteNextCut := TRUE;
State xEnable := TRUE; 80 μs 120 μs
xRegulatorOn := TRUE;
xStartFlyingSaw := TRUE;
xExecuteNextCut := TRUE;
Index
________________________________________________________________
A N
Access points 28 Notes on how to operate the technology module 13
Application notes 7
Approaching the parking position 45 O
Operating mode 13
C Outputs 19
Controlled start of the axes 14
Conventions used 6 P
CPU utilisation (example Controller 3231 C) 49 Parameter structure L_TT1P_scPar_FlyingSawBase/State 21
Cutting on position markers (mark-controlled operation) 37
Cutting relative product lengths (length-controlled operation) R
34 Recovery of the target position 40
Restoring the target position 40
D
Deleting the mark stack 43 S
Document history 5 Safety instructions 7, 8
Signal flow diagrams 26
E Start of the axes 14
E-mail to Lenze 51 State machine 24
eTMState 25 States 24
States of the eTMState output 25
F Structure of the access points L_TT1P_scAP_FlyingSawBase/
Feedback to Lenze 51 State 28
Flying Saw (functional description) 10 Structure of the signal flow L_TT1P_scSF_FlyingSawBase/State
Following error monitoring 47 27
Functional description for the "Flying Saw" 10 Synchronisation of the saw carriage with the material speed 31
H T
Homing 29 Target group 4
Technology module functions (overview) 12
I
Inputs 16 V
Inputs and outputs 16 Variable names 6
L W
L_TT1P_FlyingSawBase 15 Window for following error monitoring 47
L_TT1P_FlyingSawBase/State function block 15
L_TT1P_FlyingSawState 15
L_TT1P_scAP_FlyingSawBase 28
L_TT1P_scAP_FlyingSawState 28
L_TT1P_scPar_FlyingSawBase 21
L_TT1P_scPar_FlyingSawState 21
L_TT1P_scSF_FlyingSawBase 27
L_TT1P_scSF_FlyingSawState 27
Layout of the safety instructions 7
Length-controlled operation (cutting of relative product
lengths) 34
M
Manual jog (jogging) 29
Mark-controlled operation (cutting to position markers) 37
Motion profiles (linear/S-shaped ramps) 30
Your opinion is important to us
)(('%$&.
These instructions were created to the best of our knowledge and
belief to give you the best possible support for handling our product.
Perhaps we have not succeeded in achieving this objective in every
respect. If you have suggestions for improvement, please e-mail us
to:
[email protected]
Thank you very much for your support.

Your Lenze documentation team
51
Technology module | Flying Saw · Reference Manual · SHGTMFlyingSaw · 13588954 · DMS 7.0 EN · 12/2019 · TD06
Lenze Automation GmbH

Postfach 10 13 52, 31763 Hameln
Hans-Lenze-Straße 1, 31855 Aerzen
Germany
HR Hannover B 205381
+49 5154 82-0
+49 5154 82-2800
[email protected]
www.lenze.com
Service
Lenze Service GmbH
Breslauer Straße 3, 32699 Extertal
Germany
008000 24 46877 (24 h helpline)
+49 5154 82-1112
[email protected]

FAST - TM Flying Saw - v7-0 - EN

Uploaded by

Copyright:

Available Formats

FAST - TM Flying Saw - v7-0 - EN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FAST - TM Flying Saw - v7-0 - EN

Uploaded by

Copyright:

Available Formats

FAST Application Software

1 About this documentation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 3

3 Functional description for the "Flying Saw" _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 10

Your opinion is important to us _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 51

1 About this documentation

Documentation type Subject

More technical documentation for Lenze components

Planning / configuration / technical data Symbols:

1.1 Document history

1.2 Conventions used

Type of information Highlighting Examples/notes

1.3 Definition of the notes used

 Pictograph and signal word!

Pictograph Signal word Meaning

Pictograph Signal word Meaning

 The device documentation contains safety instructions which must be observed!

3 Functional description for the "Flying Saw"

[3-1] Typical mechanics of the technology module

1. Waiting for the start signal for synchronisation:

The "Flying saw" technology module offers the following functionalities:

3.1 Overview of the functions

 »PLC Designer« Online help

3.2 Important notes on how to operate the technology module

Setting of the operating mode

Controlled start of the axes

 Example Manual jog (jogging) ( 29):

3.3 L_TT1P_FlyingSaw[Base/State] function block

AXIS_REF ⎯ MasterAxis scSignalFlow ⎯ L_TT1P_scSF_FlyingSaw [Base/

AXIS_REF ⎯ SlaveAxis xDone ⎯ BOOL

BOOL ⎯ xJogPos xIsHomed ⎯ BOOL

3.3.1 Inputs and outputs

Designator Description Available in

Designator Description Available in

Designator Description Available in

Designator Description Available in

Designator Description Available in

Designator Description Available in

Designator Description Available in

Designator Description Available in

Designator Description Available in

3.4 State machine

[3-2] State machine of the technology module

 A transition to the ERROR or STOP state is possible.

States of the eTMState output (L_TT1P_States)

No. L_TT1P_States Description

3.5 Signal flow diagrams

[3-3] Signal flow: Flying Saw

3.5.1 Structure of the signal flow

Designator Description Available in

3.5.2 Structure of the access points

Designator Description Available in

3.6 Manual jog (jogging)

3.8 Setting motion profiles (linear/S-ramps)

3.9 First synchronisation of the saw carriage to the material speed

[3-4] Example: Characteristic with xSyncFlyingSaw parameter = FALSE

B. xSyncFlyingSaw parameter = TRUE:

[3-5] Example: Characteristic with xSyncFlyingSaw parameter = TRUE

C. eModeFlyingSaw = 1 parameter (mark-controlled operation):

[3-6] Example: Characteristic with eModeFlyingSaw parameter = 1 (mark-controlled operation)