Siemens SINUMERIK 840Di sl Parts list manual

Foreword
Brief description 1
Detailed description 2
Boundary conditions 3
Signal Descriptions 4
Examples 5
Data lists 6
Appendix A
SINUMERIK
SINUMERIK
840D sl/840Di sl/840D/840Di/810D
Synchronized actions
Function Manual
11/2006
6FC5397-5BP10-2BA0
Valid for
Control
SINUMERIK 840D sl/840DE sl
SINUMERIK 840Di sl/840DiE sl
SINUMERIK 840D powerline/840DE powerline
SINUMERIK 840Di powerline/840DiE powerline
SINUMERIK 810D powerline/810DE powerline
Software Version
NCU system software for 840D sl/840DE sl 1.4
NCU system software for 840D sl/DiE sl 1.0
NCU system software for 840D/840DE 7.4
NCU system software for 840Di/840DiE 3.3
NCU system software for 810D/810DE 7.4

Safety Guidelines
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
Danger
indicates that death or severe personal injury will result if proper precautions are not taken.
Warning
indicates that death or severe personal injury may result if proper precautions are not taken.
Caution
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
Caution
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
Notice
indicates that an unintended result or situation can occur if the corresponding information is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning and
operation of a device/system may only be performed by qualified personnel. Within the context of the safety notes
in this documentation qualified persons are defined as persons who are authorized to commission, ground and
label devices, systems and circuits in accordance with established safety practices and standards.
Prescribed Usage
Note the following:
Warning
This device may only be used for the applications described in the catalog or the technical description and only in
connection with devices or components from other manufacturers which have been approved or recommended by
Siemens. Correct, reliable operation of the product requires proper transport, storage, positioning and assembly
as well as careful operation and maintenance.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this
publication may be trademarks whose use by third parties for their own purposes could violate the rights of the
owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Siemens AG
Automation and Drives
Postfach 48 48
90437 NÜRNBERG
GERMANY
Order No.: 6FC5397-5BP10-2BA0
Ⓟ 11/2006
Copyright © Siemens AG 2006.
Technical data subject to change

Synchronized actions
Function Manual, 11/2006, 6FC5397-5BP10-2BA0 3
Foreword
SINUMERIK® Documentation
The SINUMERIK documentation is organized in 3 parts:
•General documentation
•User documentation
•Manufacturer/service documentation
A monthly updated publications overview with respective available languages can be found
in the Internet under:
http://www.siemens.com/motioncontrol
Select the menu items "Support" → "Technical Documentation" → "Overview of
Publications".
The Internet version of DOConCD (DOConWEB) is available under:
http://www.automation.siemens.com/doconweb
Information about training courses and FAQs (Frequently Asked Questions) can be found
in internet under::
http://www.siemens.com/motioncontrol under menu option "Support"
Target group
This publication is intended for:
•Project engineers
•Technologists (from machine manufacturers)
•System startup engineers (Systems/Machines)
•Programmers
Benefits
The function manual describes the functions so that the target group knows them and can
select them. It provides the target group with the information required to implement the
functions.

Foreword
Synchronized actions
4 Function Manual, 11/2006, 6FC5397-5BP10-2BA0
Standard version
This documentation only describes the functionality of the standard version. Extensions or
changes made by the machine tool manufacturer are documented by the machine tool
manufacturer.
Other functions not described in this documentation might be executable in the control. This
does not, however, represent an obligation to supply such functions with a new control or
when servicing.
Further, for the sake of simplicity, this documentation does not contain all detailed
information about all types of the product and cannot cover every conceivable case of
installation, operation or maintenance.
Technical Support
If you have any technical questions, please contact our hotline:
Europe / Africa Asia / Australia America
Phone [phone] [phone] [phone]
Fax [phone] [phone] [phone]
Internet http://www.siemens.com/automation/support-request
E-Mail mailto:[e-mail]
Note
Country specific telephone numbers for technical support are provided under the following
Internet address:
http://www.siemens.com/automation/service&support
Questions about the manual
If you have any queries (suggestions, corrections) in relation to this documentation, please
send a fax or e-mail to the following address:
Fax: [phone] / 98 - 63315
Email: mailto:[email protected]m
A fax form is available at the end of this document.

Foreword
Synchronized actions
Function Manual, 11/2006, 6FC5397-5BP10-2BA0 5
SINUMERIK Internet address
http://www.siemens.com/sinumerik
EC declaration of conformity
The EC Declaration of Conformity for the EMC Directive can be found/obtained
•in the internet:
http://www.ad.siemens.de/csinfo
under product/order no. 15257461
•with the relevant branch office of the A&D MC group of Siemens AG.

Foreword
Synchronized actions
6 Function Manual, 11/2006, 6FC5397-5BP10-2BA0

Synchronized actions
Function Manual, 11/2006, 6FC5397-5BP10-2BA0 7
Table of contents
Foreword ................................................................................................................................................... 3
1 Brief description....................................................................................................................................... 11
2 Detailed description ................................................................................................................................. 13
2.1 Components of synchronized actions..........................................................................................13
2.1.1 Definition of motion-synchronous actions ....................................................................................20
2.1.2 Execution of synchronized actions ..............................................................................................20
2.1.3 List of possible actions.................................................................................................................20
2.2 Real-time evaluations and calculations .......................................................................................22
2.3 Special real-time variables for synchronized actions...................................................................28
2.3.1 Marker/counter variables .............................................................................................................29
2.3.2 Timers ..........................................................................................................................................30
2.3.3 Synchronized action parameters .................................................................................................31
2.3.4 R parameters ...............................................................................................................................32
2.3.5 Machine and setting data.............................................................................................................32
2.3.6 FIFO variables (circulating memory)............................................................................................34
2.3.7 System variables saved in SRAM (SW 6.3 and later) .................................................................36
2.3.8 Determining the path tangent in synchronized actions................................................................37
2.3.9 Determining the current override .................................................................................................38
2.3.10 Capacity evaluation using time requirement for synchronized actions........................................39
2.3.11 List of system variables relevant to synchronized actions...........................................................41
2.4 Actions in synchronized actions...................................................................................................42
2.4.1 Output of M, S and H auxiliary functions to the PLC ...................................................................44
2.4.2 Setting (writing) and reading of real-time variables .....................................................................47
2.4.3 Changing of SW cam positions and times (setting data).............................................................48
2.4.4 FCTDEF.......................................................................................................................................49
2.4.5 Polynomial evaluation SYNFCT...................................................................................................51
2.4.6 Overlaid movements $AA_OFF settable (SW 6 and later) ..........................................................56
2.4.7 Online tool offset FTOC ...............................................................................................................59
2.4.8 Online tool length offset $AA_TOFF[Index] .................................................................................61
2.4.9 RDISABLE ...................................................................................................................................66
2.4.10 STOPREOF .................................................................................................................................66
2.4.11 DELDTG.......................................................................................................................................67
2.4.12 Disabling a programmed axis motion ..........................................................................................68
2.4.13 Starting command axes ...............................................................................................................69
2.4.14 Axial feedrate from synchronized actions ....................................................................................73
2.4.15 Starting/Stopping axes from synchronized actions......................................................................74
2.4.16 Axis replacement from synchronized actions ..............................................................................75
2.4.17 Spindle motions from synchronized actions ................................................................................81
2.4.18 Setting actual values from synchronized actions.........................................................................85
2.4.19 Activating/deactivating coupled motions and couplings ..............................................................86
2.4.20 Measurements from synchronized actions ..................................................................................93
2.4.21 Setting and deleting wait markers for channel synchronization...................................................97
2.4.22 Set alarm/error reactions .............................................................................................................98
2.4.23 Evaluating data for machine maintenance...................................................................................99

Table of contents
Synchronized actions
8 Function Manual, 11/2006, 6FC5397-5BP10-2BA0
2.5 Call of Technology Cycles......................................................................................................... 101
2.5.1 Coordination of synchronized actions, technology cycles, part program (and PLC) ................ 104
2.6 Control and protection of synchronized actions........................................................................ 106
2.6.1 Control via PLC ......................................................................................................................... 106
2.6.2 Protected synchronized actions ................................................................................................ 108
2.7 Control system response for synchronized actions in specific operational states.................... 111
2.7.1 Power On .................................................................................................................................. 111
2.7.2 RESET ...................................................................................................................................... 111
2.7.3 NC STOP .................................................................................................................................. 112
2.7.4 Mode change ............................................................................................................................ 113
2.7.5 End of program ......................................................................................................................... 113
2.7.6 Response of active synchronized actions to end of program and change in operating
mode ......................................................................................................................................... 114
2.7.7 Block search.............................................................................................................................. 114
2.7.8 Program interruption by ASUB.................................................................................................. 115
2.7.9 REPOS...................................................................................................................................... 115
2.7.10 Response to alarms .................................................................................................................. 115
2.8 Configuration............................................................................................................................. 116
2.8.1 Configurability ........................................................................................................................... 116
2.9 Diagnostics (only with HMI Advanced) ..................................................................................... 119
2.9.1 Displaying status of synchronized actions ................................................................................ 120
2.9.2 Displaying main run variables ................................................................................................... 121
2.9.3 Logging main run variables....................................................................................................... 121
3 Boundary conditions .............................................................................................................................. 125
4 Signal Descriptions................................................................................................................................ 129
5 Examples............................................................................................................................................... 131
5.1 Examples of conditions in synchronized actions....................................................................... 131
5.2 Reading and writing of SD/MD from synchronized actions....................................................... 132
5.3 Examples of adaptive control.................................................................................................... 134
5.3.1 Clearance control with variable upper limit ............................................................................... 135
5.3.2 Feedrate control ........................................................................................................................ 136
5.3.3 Control velocity as a function of normalized path ..................................................................... 137
5.4 Monitoring a safety clearance between two axes ..................................................................... 138
5.5 Store execution times in R parameters..................................................................................... 139
5.6 "Centering" with continuous measurement ............................................................................... 139
5.7 Axis couplings via synchronized actions................................................................................... 143
5.7.1 Coupling to leading axis............................................................................................................ 143
5.7.2 Non-circular grinding via master value coupling ....................................................................... 144
5.7.3 On-the-fly parting ...................................................................................................................... 148
5.8 Technology cycles position spindle........................................................................................... 149
5.9 Synchronized actions in the TC/MC area ................................................................................. 151
6 Data lists................................................................................................................................................ 155
6.1 Machine data............................................................................................................................. 155
6.1.1 General machine data............................................................................................................... 155
6.1.2 Channelspecific machine data .................................................................................................. 155
6.1.3 Axis-specific machine data........................................................................................................ 156

Table of contents
Synchronized actions
Function Manual, 11/2006, 6FC5397-5BP10-2BA0 9
6.2 Setting data................................................................................................................................156
6.2.1 Axis/spindle-specific setting data...............................................................................................156
6.3 Signals .......................................................................................................................................157
6.3.1 Signals from channel .................................................................................................................157
A Appendix................................................................................................................................................ 159
A.1 Publication-specific information .................................................................................................159
A.1.1 Correction sheet - fax template..................................................................................................159
A.1.2 Overview ....................................................................................................................................161
Index...................................................................................................................................................... 163

Table of contents
Synchronized actions
10 Function Manual, 11/2006, 6FC5397-5BP10-2BA0

Synchronized actions
Function Manual, 11/2006, 6FC5397-5BP10-2BA0 11
Brief description 1
Definition of synchronized actions
Motion-synchronous actions (or "synchronized actions" for short) are instructions
programmed by the user, which are evaluated in the interpolation cycle of the NCK in
synchronization with the execution of the part program. If the condition programmed in the
synchronized action is fulfilled or if none is specified, then actions assigned to the instruction
are activated in synchronism with the remainder of the part program run.
Applications
The following selection from the wide range of possibilities indicates how actions
programmed in synchronized actions can be usefully employed.
•Output of auxiliary functions to PLC
•Writing and reading of main run variables
•Positioning of axes and spindles
•Activation of synchronous procedures, such as:
– Read-in disable
– Deletion of distance-to-go
– End preprocessing stop
•Activation of technology cycles
•Online calculation of function values
•Online tool offsets
•Activation/deactivation of couplings/coupled motion
•Take measurements
•Enabling/disabling of synchronized actions
All possible applications of this function are described in the "Detailed Description" chapter.

Brief description
Synchronized actions
12 Function Manual, 11/2006, 6FC5397-5BP10-2BA0
,QLWLDWHGDFWLRQV
QRQPRGDO
PRGDO
PRGDOVWDWLF
DFURVVPRGHV
*DWLQJORJLF
(YDOXDWLRQRI
FRQGLWLRQV
5HDOWLPHHYHQWVDQGYDOXHV
'LJLWDOLQSXWVVLJQDOV
9DOXHVRIV\VWHPYDULDEOHV
0HDVXUHGYDOXHV
'ULYHGDWD
,Q1&.LQWHUSRODWLRQF\FOH
Figure 1-1 Schematic diagram of synchronized actions
For details of how to program synchronized actions, please see:
References:
/PGA/Programming Manual Advanced
The following chapters describe:
•functional relationships for synchronized actions in the Chapter "Detailed Description",
•Application examples in the Chapter "Examples".
Note
This description encompasses the functionality of the current software version. The
synchronized actions available in SW version 3 and earlier are described in:
References:
/FB2/ Function Manual, Extended Functions; Synchronized Actions (S5).

Synchronized actions
Function Manual, 11/2006, 6FC5397-5BP10-2BA0 13
Detailed description 2
2.1 Components of synchronized actions
Structure of a synchronized action
Component: Validity,
identification
number
Frequency G code for cond.
and action
Condition Action
code word
(fixed)
G code for
action
Action or
Tech-no-lo-
gy-cy-cle
Example IDS=1 EVERY G70 $AAA_IM[B]
> 15
DO G71 POS[X]=100
The components of the synchronous actions are explained below individually:
•Validity:
– With identification number
– Without identification number
•Frequency
•G code for condition and action (SW 5 and later)
•Condition
•G code for actions (SW 5 and later)
•Action(s)/Technology cycle
Validity ID number
There are three possible ways for defining the scope of validity of a synchronized action:
1. No specification
2. ID
3. IDS

Detailed description
2.1 Components of synchronized actions
Synchronized actions
14 Function Manual, 11/2006, 6FC5397-5BP10-2BA0
No data
Synchronized actions that have no specified validity have a non-modal action, i.e. they apply
only to the next block.
Non-modal synchronized actions are operative only in AUTOMATIC mode.
From SW 6.1 and later, non-modal synchronized actions are active modally for all
preprocessing stop blocks (incl. implicitly generated ones) and for implicitly generated
intermediate blocks.
ID
Synchronized actions with validity identifier ID act modally in the subsequently programmed
blocks. They are operative only in AUTOMATIC mode.
Limitation:
•ID actions remain operative only until another synchronized action with the same
identification number is programmed
•till deletion, CANCEL(i), see Chapter "Coordinations between synchronized actions,
Technology cycles, Part program (and PLC)".
IDS
Statically effective synchronized actions that are programmed with the keyword "IDS", are
active in all operating modes. They are also referred to as static synchronized actions.
Option.
Synchronized actions programmed with ID or IDS are deleted from the part program.
Identification numbers
For modal synchronized actions (ID, IDS) identification numbers between 1 and 255 are
allocated. They are important for the functions of mutual coordination of synchronized
actions. See Chapter "Coordination of synchronized actions, technology cycles, part program
(and PLC)".
Modal/static synchronized actions with identification numbers between 1 and 64 can be
disabled and enabled from the PLC. See Chapter "Control via PLC".
Unique identification numbers must be allocated in the channel.
Applications for static synchronized actions:
•AC-grinding also active in the JOG mode
•Logic operations for Safety Integrated
•Monitoring functions, responses to machine states in all modes
•Ooptimization of the tool change
•Cyclic machines
Examples:
IDS=1 EVERY $A_IN[1]==1 DO POS[X]=100: all modes
ID=2 EVERY $A_IN[1]==0 DO POS[X]=0: AUTOMATIC

Detailed description
2.1 Components of synchronized actions
Synchronized actions
Function Manual, 11/2006, 6FC5397-5BP10-2BA0 15
Note
The following actions are operative only in AUTOMATIC mode when the program is running:
STOPREOF
DELDTG
Frequency
Keywords (see table) are programmed to indicate how often the subsequently specified
condition must be scanned and the associated action executed if the condition is fulfilled.
These keywords are an integral component of the synchronized action condition.
Table 2-1 Effect of frequency keywords
Keyword Scanning frequency
None If no scanning frequency is programmed, then the action is executed cyclically in every interpolation
cycle.
WHENEVER The associated action/technology cycle is executed cyclically in every interpolation cycle provided that
the condition is fulfilled.
FROM If the condition has been fulfilled once, the action/technology cycle is executed cyclically in every
interpolation cycle for as long as the synchronized action remains active.
WHEN As soon as the condition has been fulfilled, the action/technology cycle is executed once. Once the
action has been executed a single time, the condition is no longer checked.
EVERY The action/technology cycle is activated once if the condition is fulfilled. The action/technology cycle is
executed every time the condition changes from the FALSE to the TRUE state.
In contrast to keyword WHEN, checking of the condition continues after execution of the action/cycle
until the synchronized action is deleted or disabled.
Details of technology cycles are given in the Chapter "Call of technology cycles".
Deleting with CANCEL
If an active synchronized action is cancelled (deleted) with CANCELfrom the part program,
then the active action is not affected. Positioning motions are completed as programmed.
With the command CANCEL a modal or a statically active synchronized action can be
deleted.
If a synchronized action is deleted while the positioning axis motion it has initiated is still in
progress, the positioning motion continues until properly executed. A channel stop also
cancels the positioning movement from synchronized actions/technology cycles.
G code for condition and action
Starting from SW-version 5 the G-codes can be programmed in synchronized actions. This
allows defined settings to exist for the evaluation of the condition and the action/technology
cycle to be executed, independent of the current parts program status. It is necessary to
separate the synchronized actions from the program environment, because synchronized
actions are required to execute their actions at any time from a defined initial state as a
result of fulfilled trigger conditions.

Detailed description
2.1 Components of synchronized actions
Synchronized actions
16 Function Manual, 11/2006, 6FC5397-5BP10-2BA0
Applications:
Definition of the measurement systems for condition evaluation and action through G codes
G70, G71, G700, G710.
Note
Only one G-code of the G-code group may be programmed for each part of the condition. A
G-code specified for the condition is valid for the evaluation of the condition and for the
action, if no separate G-code is specified for the action. A G code specified for the condition
is valid for the evaluation of the condition and for the action if no separate G code is
specified for the action.
Conditions
The execution of actions / technology cycles can be made dependent upon a condition
(logical expression).
The condition is checked in the interpolation cycle. If no condition is programmed, the action
is performed once in every IPO cycle.
Possible components include:
•Comparison of main run variables such as digital or analog inputs/outputs
•Boolean gating of comparison results
•Computation of real-time expressions
•Time/distance from beginning of block
•Measured values, measurement results
•Servo values
•Velocities, axis status
In SW version 3 and earlier, two conditions are permitted, i.e. the comparison of a main run
variable with an expression calculated during preprocessing or the comparison of two main
run variables.
Examples:
WHENEVER $AA_IM[X] > 10.5*SIN(45) DO ...
or
WHENEVER $AA_IM[X] > $$AA_IM[X1] DO ...
Additional comparisons using Boolean gating can also be interlinked. Boolean operators of
the NC language may be used for this purpose:
NOT, AND, OR, XOR, B_OR, B_AND, B_XOR, B_NOT.

Detailed description
2.1 Components of synchronized actions
Synchronized actions
Function Manual, 11/2006, 6FC5397-5BP10-2BA0 17
Examples:
WHENEVER ($A_IN[1]==1) OR ($A_IN[3]==0) DO ...
; while input 1 is applied or input 3 is not applied ...
Two or more real-time expressions may be compared with one another within one condition.
Comparisons may be made between variables of the same type or between partial
expressions.
Examples:
Example
WHEN $AA_IM[X2] <= $AA_IM[X1] +.5 DO $AA_OVR[X1]=0
; Stop, when the safety clearance is exceeded.
Further examples of conditions can be found in Chapter 6.1. The calculations of real-time
expressions are described in the Chapter "Evaluations and calculations in real time".
All system variables whose data are read or written by the NC via synchronized actions can
be addressed in conditions. So can all machine data and setting data where the value is
read in the main run:
Machine data, e.g. $$MN_..., $$MC_..., $$MA_...
Setting data, e.g. $$SN_..., $$SC_..., $$SA_...
Note
GUD variables cannot be used
R-parameters are addressed with $R... .
Setting data and machine data, whose value may vary during machining, must be
programmed with $$S._.../$$M._... .
More examples of conditions are given in the Chapter "Examples for conditions in
synchronized actions".
G code for the action
The G code may specify a different G code from the condition for all actions in the block and
technology cycles. If technology cycles are contained in the action part, the G code remains
modally active for all actions until the next G code, even after the technology cycle has been
completed.
Only one G code of the G code group may be programmed for each action part.

Detailed description
2.1 Components of synchronized actions
Synchronized actions
18 Function Manual, 11/2006, 6FC5397-5BP10-2BA0
Actions
Every synchronized action contains one or more programmed actions or one technology
cycle. These are executed when the appropriate condition is fulfilled. If several actions are
programmed in one synchronized action, they are executed within the same interpolation
cycle.
Example
WHEN $AA_IM[Y] >= 35.7 DO M135 $A_OUT[1]=1
If the actual value of the Y axis is greater than or equal to 35.7, then M135 is output at PLC
and at the same time the output 1 is set.
Program/technology cycle
A program (name) can also be specified as an action. This program may contain any of the
actions, which can be programmed individually in synchronized actions. These programs are
also referred to as technology cycles below. A technology cycle is a sequence of actions that
are processed sequentially in the interpolation cycle, see
Chapter 2.5. "Call of Technology Cycles".
Application: Single axis programs, cyclic machines.
Machining process
The blocks of a part program are prepared at the program preprocessing stage, stored and
then executed sequentially at the interpolation level (main run). Variables are accessed
during block preparation. When main-run variables (e.g., actual values) are used, block
preparation is interrupted to allow current real-time values up to the preceding block to be
supplied.
Synchronized actions are transported to the interpolator in preprocessed form together with
the prepared block. The main run variables used are evaluated in the interpolation cycle.
Block preparation is not interrupted.
Part program blocks without traversing motion (zero blocks) are normally eliminated by the
interpreter. However, if synchronous actions are active, this zero block is included and also
executed. Here, an exact stop corresponding to the active function (e.g. G601) is triggered.
This allows the synchronous action to also switch.
Examples of zero blocks:
N1000 G91 X0 Y0 Z0
...
N10 G90 G64 X100 Y100 Z100
N15 Z100
...
Blocks without traversing motion can also be generated using program jumps.

Detailed description
2.1 Components of synchronized actions
Synchronized actions
Function Manual, 11/2006, 6FC5397-5BP10-2BA0 19
0$B$B,'
'HOHWH
$FWLRQVWHFKQRORJ\
F\FOHV
6HWSRLQWV
6HTXHQFHRIV\QFKURQL]HGDFWLRQLQWHUSUHWDWLRQ
6\QFKURQL]HG
DFWLRQ
SURFHVVLQJ
0RYHPHQW
RID[HV
0DLQUXQ
:+(1(9(5
%ORFN
%ORFN
>@
%ORFN
%ORFN

1%ORFN
1
%ORFN
1,' 
1
%ORFN
1
%ORFN

3UHSDUHG
33EORFNV
3URJUDP
SUHSURFHVVLQJ
6HOHFWLQJ
6DYHGSUHSURFHVVHGV\QFKURQL]HGDFWLRQV
0HPRU\VL]H0'0&B00B180B6<1&B(/(0(176
$FWLRQV
7HFKF\FOHV
&RQGLWLRQ)UHTXHQF\9DOLGLW\,','6
Figure 2-1 Schematic diagram illustrating processing of synchronized actions
Processing of synchronized actions
Synchronized actions are checked in the interpolation cycle to determine whether they
contain actions to be activated.
Action(s) are executed in synchronism with path control if the preconditions programmed on
the left of the action(s) are fulfilled.
Order of execution
Within an interpolation cycle, modal synchronized action instructions are processed in order
of their ID number (i.e. block with ID number 1 before block with ID number 2, etc.). Once the
modal synchronized action instructions have been executed, non-modal synchronized action
instructions are processed in the order in which they are programmed.

Detailed description
2.1 Components of synchronized actions
Synchronized actions
20 Function Manual, 11/2006, 6FC5397-5BP10-2BA0
2.1.1 Definition of motion-synchronous actions
Defining programs
Motion-synchronous actions can be defined as follows:
•In the part program
•Static synchronized actions in an asynchronous subprogram activated by the PLC
2.1.2 Execution of synchronized actions
Conditions for execution
The actions programmed in motion-synchronous actions are executed, when:
•the synchronized action exists and has not been deselected with CANCEL(ID).
•the synchronous action is not locked, no LOCK(ID), see Chapter 2.5.1 "Coordination of
synchronized actions, technology cycles, part programs and PLC".
•evaluation of the action is due as a result of the programmed frequency keyword or
•the appropriate condition is fulfilled.
•For further details, please see the following subsections.
2.1.3 List of possible actions
•Output of M, S and H auxiliary functions to the PLC
•Setting (writing) of main run variables enables the following:
– Overlaid movement ($AA_OFF), option.
– Applied tool length offsets ($AA_TOFF), option.
– Feedrate control ($AC_OVR, $AA_OVR), disabling of a programmed axis motion
– Allocate Servo–data–values $V...=
– Reading or writing arithmetic variable $R[n]=
– Writing the SD value in the main run $$SD
•Reading the MD value for the interpretation time $MD...=
•Changing of SW cam positions and times (setting data)
•Modification of coefficients and limits from FCTDEF
•Polynomial evaluation SYNFCT
•Online tool offset FTOC