840Dsl Basic FCT Man 1219 en-US

Preface
Fundamental safety
instructions 1
Mode group, channel,
SINUMERIK program operation, reset 2
response
Axes, coordinate systems,

SINUMERIK 840D sl frames 3
Basic functions
Kinematic chain 4
Continuous-path mode,
Function Manual
exact stop, LookAhead 5
Cross-channel program
coordination and channel-by- 6
channel running-in
Cross-channel axis
interchange 7
Preprocessing 8
Emergency stop 9
Various NC/PLC interface
signals and functions 10
Auxiliary function outputs to
PLC 11
Digital and analog NC I/O 12

Valid for
Distributed systems 13
Control system
SINUMERIK 840D sl / 840DE sl
Memory configuration 14
CNC software version 4.93
12/2019 Appendix A
6FC5397-2GP40-0BA0
Legal information
Warning notice system
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
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
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 product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of 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 Document order number: 6FC5397-2GP40-0BA0 Copyright © Siemens AG 2019.

Digital Industries Ⓟ 12/2019 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Preface
SINUMERIK documentation
The SINUMERIK documentation is organized into the following categories:
● General documentation/catalogs
● User documentation
● Manufacturer/service documentation
Additional information
You can find information on the following topics at the following address (https://
support.industry.siemens.com/cs/de/en/view/108464614):
● Ordering documentation/overview of documentation
● Additional links to download documents
● Using documentation online (find and search in manuals/information)
If you have any questions regarding the technical documentation (e.g. suggestions,
corrections), please send an e-mail to the following address
(mailto:docu.motioncontrol@siemens.com).
mySupport/Documentation
At the following address (https://support.industry.siemens.com/My/ww/en/documentation),
you can find information on how to create your own individual documentation based on
Siemens' content, and adapt it for your own machine documentation.
Training
At the following address (http://www.siemens.com/sitrain), you can find information about
SITRAIN (Siemens training on products, systems and solutions for automation and drives).
FAQs
You can find Frequently Asked Questions in the Service&Support pages under Product
Support (https://support.industry.siemens.com/cs/de/en/ps/faq).
SINUMERIK
You can find information about SINUMERIK at the following address (http://www.siemens.com/
sinumerik).
Basic functions
Function Manual, 12/2019, 6FC5397-2GP40-0BA0 3
Preface
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.
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.
Note regarding the General Data Protection Regulation

Siemens observes standard data protection principles, in particular the principle of privacy by
design. That means that
this product does not process / store any personal data, only technical functional data (e.g. time
stamps). If a user links this data with other data (e.g. a shift schedule) or stores personal data
on the same storage medium (e.g. hard drive) and thus establishes a link to a person or
persons, then the user is responsible for ensuring compliance with the relevant data protection
regulations.
Technical Support
Country-specific telephone numbers for technical support are provided on the Internet at the
following address (https://support.industry.siemens.com/sc/ww/en/sc/2090) in the "Contact"
area.
If you have any technical questions, use the online form in the "Support Request" area.
Basic functions
4 Function Manual, 12/2019, 6FC5397-2GP40-0BA0
Preface
Information on the structure and contents
Structure
This Function Manual is structured as follows:
● Inner title (page 3) with the title of the Function Manual, the SINUMERIK controls as well as
the software and the version for which this version of the Function Manual is applicable and
the overview of the individual functional descriptions.
● Descriptions of functions
● Appendix with:
– List of abbreviations
– Documentation overview
Note
For detailed descriptions of data and alarms see:
● For machine and setting data:
Detailed machine data description
● For NC/PLC interface signals:
NC Variables and Interface Signals List Manual
● For alarms:
Diagnostics Manual
Notation of system data

The following notation is applicable for system data in this documentation:
Signal/Data Notation Example

NC/PLC interface ... NC/PLC interface signal: When the new gear stage is engaged, the following NC/PLC
signals <signal address> (<signal name>) interface signals are set by the PLC program:
DB31, ... DBX16.0-2 (actual gear stage A to C)
DB31, ... DBX16.3 (gear is changed)
Machine data ... machine data: Master spindle is the spindle stored in the machine data:
<Type><Number> <Complete Des‐ MD20090 $MC_SPIND_DEF_MASTER_SPIND (position of de‐
ignator> (<Meaning>) letion of the master spindle in the channel)
Setting data ... setting data: The logical master spindle is contained in the setting data:
<Type><Number> <Complete Des‐ SD42800 $SC_SPIND_ASSIGN_TAB[0] (spindle number con‐
ignator> (<Meaning>) verter)
Basic functions
Preface
Quantity structure
Explanations concerning the NC/PLC interface are based on the absolute maximum number of
the following components:
● Mode groups (DB11)
● Channels (DB21, etc.)
● Axes/spindles (DB31, etc.)
Data types
The control provides the following data types that can be used for programming in part
programs:
Type Meaning Range of values

INT Signed integers -2.147.483.648 ... +2.147.483.647
REAL Numbers with decimal point ≈ ±5.0*10-324 … ≈ ±1.7*10+308
BOOL Boolean values TRUE (≠0) , FALSE (0)
CHAR ASCII characters and bytes 0 ... 255 or -128 ... 127
STRING Character string, null-terminated Maximum of 400 characters + /0
(no special characters)
AXIS Axis names All axis names available in the control
system
FRAME Geometrical parameters for moving, rotating, scaling, and ---
mirroring
Arrays
Arrays can only be formed from similar elementary data types. Up to 3-dimensional arrays are
possible.
Example: DEF INT ARRAY[2, 3, 4]
Number systems
The following number systems are available:
● Decimal: DEF INT number = 1234 or DEF REAL number = 1234.56
● Hexadecimal: DEF INT number = 'H123ABC'
● Binary: DEF INT number = 'B10001010010'
Querying REAL variables

We recommend that querying REAL or DOUBLE variables in NC programs and synchronized
actions is programmed as limit value evaluation.
Example: Querying the actual value of an axis for a specific value
Program code Comment

DEF REAL AXPOS = 123.456
IF ($VA_IM[<axis>] - 1ex-6) <= AXPOS <= ($VA_IM[<axis>] + 1ex-6) ; actual position
... == AXPOS
Basic functions
Preface

ELSE
... <> AXPOS
ENDIF
Basic functions
Preface
Basic functions
Table of contents
Preface .........................................................................................................................................................3
1 Fundamental safety instructions.................................................................................................................25
1.1 General safety instructions.....................................................................................................25
1.2 Warranty and liability for application examples ......................................................................25
1.3 Industrial security ...................................................................................................................26
2 Mode group, channel, program operation, reset response.........................................................................29
2.1 Product brief...........................................................................................................................29
2.2 Mode group ............................................................................................................................31
2.2.1 Mode group stop ....................................................................................................................34
2.2.2 Mode group reset ...................................................................................................................34
2.3 Mode types and mode type change .......................................................................................35
2.3.1 Monitoring functions and interlocks of the individual modes ..................................................40
2.3.2 Mode change .........................................................................................................................40
2.4 Channel..................................................................................................................................41
2.4.1 Properties...............................................................................................................................41
2.4.2 Start inhibit, global and channel-specific................................................................................44
2.5 Program operation .................................................................................................................45
2.5.1 Program operation mode .......................................................................................................45
2.5.2 Initial settings .........................................................................................................................46
2.5.2.1 Machine data..........................................................................................................................46
2.5.2.2 Programming..........................................................................................................................47
2.5.3 Selection and start of an NC program....................................................................................50
2.5.4 Program interruption ..............................................................................................................52
2.5.5 Channel reset.........................................................................................................................53
2.5.6 Program status.......................................................................................................................54
2.5.7 Channel status .......................................................................................................................55
2.5.8 Responses to operator and program actions .........................................................................56
2.5.9 Example of a timing diagram for a program run.....................................................................57
2.5.10 Program jumps.......................................................................................................................58
2.5.10.1 Return jump to the start of the program (GOTOS).................................................................58
2.5.11 Program section repetitions ...................................................................................................60
2.5.11.1 Programming..........................................................................................................................60
2.5.12 Event-driven program call (PROG_EVENT) ..........................................................................66
2.5.12.1 Function .................................................................................................................................66
2.5.12.2 Parameterization ....................................................................................................................70
2.5.12.3 Programming..........................................................................................................................74
2.5.12.4 Boundary conditions...............................................................................................................75
2.5.12.5 Examples ...............................................................................................................................75
2.5.13 Influencing the stop events by stop delay areas ....................................................................77
2.5.13.1 Function .................................................................................................................................77
Basic functions
Table of contents
2.5.13.3 Programming..........................................................................................................................80
2.5.13.4 Supplementary conditions......................................................................................................82
2.5.14 Adapting the size of the interpolation buffer...........................................................................83
2.5.15 Basic block display (only for ShopMill/ShopTurn) ..................................................................85
2.5.15.1 Function .................................................................................................................................85
2.5.15.3 Structure for a DIN block........................................................................................................88
2.6 Program control......................................................................................................................91
2.6.1 Overview ................................................................................................................................91
2.6.2 Program test...........................................................................................................................93
2.6.3 Dry run feedrate .....................................................................................................................96
2.6.4 Reduced rapid traverse..........................................................................................................98
2.6.5 Programmed stop...................................................................................................................99
2.6.6 Handwheel offset .................................................................................................................100
2.6.7 Skipping program blocks......................................................................................................101
2.6.8 Single block..........................................................................................................................103
2.6.8.1 Function ...............................................................................................................................103
2.6.8.2 Selecting and activating .......................................................................................................104
2.6.8.3 Parameterization ..................................................................................................................105
2.6.8.4 Programming........................................................................................................................106
2.6.8.5 Constraints ...........................................................................................................................110
2.6.9 Mode group-specific single block type A / B ........................................................................111
2.6.10 Configured stop....................................................................................................................112
2.6.10.1 Function ...............................................................................................................................112
2.6.10.2 Selecting and activating .......................................................................................................113
2.6.10.3 Parameter assignment .........................................................................................................115
2.6.10.4 Programming........................................................................................................................116
2.6.10.5 Constraints ...........................................................................................................................116
2.6.10.6 Examples .............................................................................................................................117
2.6.11 Status ...................................................................................................................................121
2.7 Block search, types 1, 2, and 4: ...........................................................................................121
2.7.1 Description of the function....................................................................................................123
2.7.2 Block search in connection with other NCK functions..........................................................125
2.7.2.1 ASUB after and during block search ....................................................................................125
2.7.2.2 PLC actions after block search ............................................................................................126
2.7.2.3 Spindle functions after block search ....................................................................................127
2.7.2.4 Reading system variables for a block search.......................................................................128
2.7.3 Automatic start of an ASUB after a block search .................................................................128
2.7.4 Cascaded block search........................................................................................................130
2.7.5 Examples for block search with calculation..........................................................................131
2.7.6 Constraints ...........................................................................................................................134
2.8 Block search Type 5 (SERUPRO) .......................................................................................135
2.8.1 Description of the function....................................................................................................135
2.8.2 Repositioning to the contour (REPOS) ................................................................................138
2.8.2.1 Repositioning with controlled REPOS..................................................................................146
2.8.3 Accelerate block search .......................................................................................................147
2.8.4 SERUPRO ASUB.................................................................................................................149
2.8.5 Selfacting SERUPRO...........................................................................................................152
2.8.6 Locking a program section for "Continue machining at the contour" ...................................153
2.8.7 Behavior during POWER ON, mode change and RESET ...................................................156
2.8.8 Supplementary conditions....................................................................................................157
Basic functions
Table of contents
2.8.8.1 STOPRE in the target block .................................................................................................157

2.8.8.2 SPOS in target block............................................................................................................158
2.8.8.3 Travel to fixed stop (FXS) ....................................................................................................158
2.8.8.4 Travel with limited torque/force (FOC) .................................................................................159
2.8.8.5 Synchronous spindle............................................................................................................159
2.8.8.6 Couplings and master-slave.................................................................................................160
2.8.8.7 Axis functions .......................................................................................................................163
2.8.8.8 Gear stage change...............................................................................................................164
2.8.8.9 Superimposed motion ..........................................................................................................165
2.8.8.10 NC/PLC interface signals .....................................................................................................165
2.8.8.11 Making the initial settings more flexible................................................................................166
2.8.8.12 Compressor functions ..........................................................................................................166
2.8.9 System variable....................................................................................................................167
2.9 Asynchronous subprograms (ASUPs) .................................................................................167
2.9.1 Function ...............................................................................................................................167
2.9.1.1 Execution sequence of an ASUP in program mode.............................................................170
2.9.1.2 ASUP with REPOSA ............................................................................................................171
2.9.1.3 NC response ........................................................................................................................172
2.9.2 Commissioning: Machine data .............................................................................................173
2.9.2.1 NC-spec.: Mode-group-specific NC/PLC interface signals and operating mode
switchover ............................................................................................................................173
2.9.2.2 NC-spec.: ASUP start enable...............................................................................................174
2.9.2.3 NC-spec.: Effectiveness of the parameterized start enables ...............................................174
2.9.2.4 Channel-spec.: Start enable despite non-referenced axes ..................................................175
2.9.2.5 Channel-spec.: Start enable despite read-in disable ...........................................................175
2.9.2.6 Channel-spec.: Continuous execution despite single block .................................................176
2.9.2.7 Channel-spec.: Refreshing the display ................................................................................176
2.9.3 Programming: System variables ..........................................................................................177
2.9.3.1 REPOS option ($P_REPINF) ...............................................................................................177
2.9.3.2 Activation event ($AC_ASUP)..............................................................................................177
2.9.4 Programming (SETINT, PRIO).............................................................................................177
2.9.5 Restrictions ..........................................................................................................................179
2.9.6 Examples .............................................................................................................................180
2.10 User-specific ASUB for RET and REPOS............................................................................181
2.10.1 Function ...............................................................................................................................181
2.10.2 Parameter assignment .........................................................................................................181
2.10.3 Programming........................................................................................................................182
2.11 Perform ASUB start for user alarms.....................................................................................183
2.11.1 Function ...............................................................................................................................183
2.11.2 Activation..............................................................................................................................184
2.11.3 Examples .............................................................................................................................185
2.11.3.1 User ASUB from reset - example 1......................................................................................185
2.11.3.2 User ASUB from reset - example 2......................................................................................186
2.11.3.3 User ASUB with M0 .............................................................................................................187
2.11.3.4 User ASUB with stop............................................................................................................188
2.11.3.5 User ASUB from stopped.....................................................................................................189
2.12 Execution from external .......................................................................................................191
2.13 Executing external subprograms (EXTCALL) ......................................................................192
2.14 Execution from external storage (EES) (option)...................................................................195
Basic functions
Table of contents
2.14.1 Function ...............................................................................................................................195

2.14.2 Commissioning.....................................................................................................................198
2.14.2.1 Configuring the drives ..........................................................................................................198
2.14.2.2 Global part program memory (GDIR)...................................................................................200
2.14.2.3 Settings for file handling in the part program for EES ..........................................................202
2.14.2.4 Memory configuration...........................................................................................................203
2.15 Process Datashare - output to an external device/file..........................................................204
2.15.1 Function ...............................................................................................................................204
2.15.2 Commissioning.....................................................................................................................205
2.15.3 Programming........................................................................................................................208
2.16 System settings for power-up, RESET / part program end and part program start .............212
2.16.1 System settings for power-up, RESET / part program end and part program start .............212
2.16.2 Tool withdrawal after POWER ON with orientation transformation......................................217
2.17 Replacing functions by subprograms ...................................................................................220
2.17.1 Overview ..............................................................................................................................220
2.17.2 Replacement of M, T/TCA and D/DL functions ....................................................................221
2.17.2.1 Replacement of M functions.................................................................................................221
2.17.2.2 Replacing T/TCA and D/DL functions ..................................................................................223
2.17.2.3 System variable....................................................................................................................226
2.17.2.4 Example: Replacement of an M function .............................................................................227
2.17.2.5 Example: Replacement of a T and D function......................................................................230
2.17.2.6 Behavior in the event of a conflict ........................................................................................231
2.17.3 Replacement of spindle functions ........................................................................................232
2.17.3.1 General information..............................................................................................................232
2.17.3.2 Replacement of M40 - M45 (gear stage change).................................................................234
2.17.3.3 Replacement of SPOS, SPOSA, M19 (spindle positioning).................................................234
2.17.3.4 System variable....................................................................................................................235
2.17.3.5 Example: Gear stage change...............................................................................................236
2.17.3.6 Example: Spindle positioning ...............................................................................................238
2.17.4 Properties of the subprograms.............................................................................................241
2.17.5 Restrictions ..........................................................................................................................243
2.18 Renaming/locking NC commands........................................................................................243
2.19 Program runtime / part counter ............................................................................................244
2.19.1 Program runtime ..................................................................................................................245
2.19.1.1 Function ...............................................................................................................................245
2.19.1.2 Commissioning.....................................................................................................................248
2.19.1.3 Supplementary conditions....................................................................................................250
2.19.1.4 Examples .............................................................................................................................250
2.19.2 Workpiece counter ...............................................................................................................251
2.19.2.1 Function ...............................................................................................................................251
2.19.2.2 Commissioning.....................................................................................................................252
2.19.2.4 Examples .............................................................................................................................254
2.20 Workpiece simulation ...........................................................................................................255
2.21 Data lists ..............................................................................................................................256
2.21.1 Function ...............................................................................................................................256
2.21.2 Machine data........................................................................................................................257
Basic functions
Table of contents
2.21.2.1 General machine data..........................................................................................................257

2.21.2.2 Channel-specific machine data ............................................................................................259
2.21.2.3 Axis/spindlespecific machine data .......................................................................................262
2.21.3 Setting data ..........................................................................................................................262
2.21.3.1 Channelspecific setting data ................................................................................................262
3 Axes, coordinate systems, frames............................................................................................................263
3.1 Brief description ...................................................................................................................263
3.1.1 Axes .....................................................................................................................................263
3.1.2 Coordinate systems .............................................................................................................265
3.1.3 Frames .................................................................................................................................266
3.2 Axes .....................................................................................................................................269
3.2.1 Overview ..............................................................................................................................269
3.2.2 Machine axes .......................................................................................................................270
3.2.3 Channel axes .......................................................................................................................271
3.2.4 Geometry axes.....................................................................................................................271
3.2.5 Special axes.........................................................................................................................271
3.2.6 Path axes .............................................................................................................................272
3.2.7 Positioning axes ...................................................................................................................272
3.2.8 Main axes.............................................................................................................................273
3.2.9 Synchronized axes...............................................................................................................274
3.2.10 Axis configuration.................................................................................................................276
3.2.11 Link axes ..............................................................................................................................278
3.3 Zero points and reference points .........................................................................................279
3.3.1 Reference points in working space ......................................................................................279
3.3.2 Position of coordinate systems and reference points...........................................................281
3.4 Coordinate systems .............................................................................................................282
3.4.1 Overview ..............................................................................................................................282
3.4.2 Machine coordinate system (MCS) ......................................................................................284
3.4.2.1 Actual value setting with loss of the referencing status (PRESETON) ................................285
3.4.2.2 Actual value setting without loss of the referencing status (PRESETONS) .........................290
3.4.3 Basic coordinate system (BCS) ...........................................................................................295
3.4.4 Basic zero system (BZS)......................................................................................................297
3.4.5 Settable zero system (SZS) .................................................................................................299
3.4.6 Workpiece coordinate system (WCS) ..................................................................................300
3.4.7 Additive offsets.....................................................................................................................301
3.4.7.1 External work offsets............................................................................................................301
3.4.7.2 DRF offset ............................................................................................................................302
3.4.7.3 Reset behavior .....................................................................................................................302
3.4.8 Axis-specific overlay ($AA_OFF) .........................................................................................303
3.4.8.1 Function ...............................................................................................................................303
3.4.8.2 Commissioning.....................................................................................................................303
3.4.8.3 Programming: Deselecting overlays axis-specifically (CORROF) .......................................304
3.5 Frames .................................................................................................................................307
3.5.1 Frame types .........................................................................................................................307
3.5.2 Frame components ..............................................................................................................308
3.5.2.1 Translation ...........................................................................................................................308
3.5.2.2 Fine offset ............................................................................................................................309
3.5.2.3 Rotation Overview (geometry axes only) .............................................................................310
3.5.2.4 Rotation with a Euler angles: ZY'X" convention (RPY angles).............................................311
Basic functions
Table of contents
3.5.2.5 Rotation with a Euler angles: ZX'Z" convention ...................................................................316

3.5.2.6 Rotation in any plane ...........................................................................................................317
3.5.2.7 Scaling .................................................................................................................................318
3.5.2.8 Mirroring ...............................................................................................................................318
3.5.2.9 Chain operator .....................................................................................................................319
3.5.2.10 Programmable axis name ....................................................................................................319
3.5.2.11 Coordinate transformation....................................................................................................320
3.5.3 Data management frames and active frames ......................................................................320
3.5.3.1 Overview ..............................................................................................................................320
3.5.3.2 Activating data management frames....................................................................................322
3.5.3.3 NCU-global and channel-specific frames.............................................................................323
3.5.4 Frame chain and coordinate systems ..................................................................................324
3.5.4.1 Overview ..............................................................................................................................324
3.5.4.2 Relative coordinate systems ................................................................................................325
3.5.4.3 Selectable SZS ....................................................................................................................327
3.5.4.4 Manual traversing of geometry axes either in the WCS or in the SZS
($AC_JOG_COORD) ...........................................................................................................328
3.5.4.5 Suppression of frames .........................................................................................................329
3.5.5 Frames of the frame chain ...................................................................................................330
3.5.5.1 Overview ..............................................................................................................................330
3.5.5.2 Settable frames ($P_UIFR[<n>])..........................................................................................331
3.5.5.3 Grinding frames $P_GFR[<n>].............................................................................................333
3.5.5.4 Channel-specific basic frames[<n>] .....................................................................................337
3.5.5.5 NCU-global basic frames $P_NCBFR[<n>] .........................................................................338
3.5.5.6 Active complete basic frame $P_ACTBFRAME...................................................................339
3.5.5.7 Programmable frame $P_PFRAME .....................................................................................340
3.5.5.8 Channelspecific system frames ...........................................................................................342
3.5.6 Implicit frame changes .........................................................................................................344
3.5.6.1 Switching geometry axes .....................................................................................................344
3.5.6.2 Selecting and deselecting transformations: General............................................................347
3.5.6.3 Selecting and deselecting transformations: TRANSMIT ......................................................348
3.5.6.4 Selecting and deselecting transformations: TRACYL ..........................................................354
3.5.6.5 Selecting and deselecting transformations: TRAANG .........................................................359
3.5.6.6 Adapting active frames.........................................................................................................365
3.5.6.7 Mapped Frames ...................................................................................................................365
3.5.6.8 Mapped Frames ...................................................................................................................370
3.5.7 Predefined frame functions ..................................................................................................373
3.5.7.1 Inverse frame .......................................................................................................................373
3.5.7.2 Additive frame in frame chain...............................................................................................376
3.5.8 Functions..............................................................................................................................377
3.5.8.1 Setting zeros, workpiece measuring and tool measuring.....................................................377
3.5.8.2 Axis-specific external work offset .........................................................................................377
3.5.8.3 Toolholder ............................................................................................................................378
3.5.9 Subprograms with SAVE attribute (SAVE)...........................................................................388
3.5.10 Data backup .........................................................................................................................389
3.5.11 Positions in the coordinate system.......................................................................................390
3.5.12 Control system response ....................................................................................................390
3.5.12.1 POWER ON .........................................................................................................................390
3.5.12.2 Mode change .......................................................................................................................391
3.5.12.3 Channel reset / part program end ........................................................................................391
3.5.12.4 Part program start ................................................................................................................395
3.5.12.5 Block search.........................................................................................................................395
Basic functions
Table of contents
3.5.12.6 REPOS.................................................................................................................................395
3.6 Workpiece-related actual-value system ...............................................................................396
3.6.1 Overview ..............................................................................................................................396
3.6.2 Use of the workpiece-related actual value system...............................................................396
3.6.3 Special reactions..................................................................................................................398
3.7 Boundary conditions.............................................................................................................400
3.8 Examples .............................................................................................................................400
3.8.1 Axes .....................................................................................................................................400
3.8.2 Coordinate systems .............................................................................................................402
3.8.3 Frames ...............................................................................................................................404
3.9 Data lists ..............................................................................................................................406
3.9.1 Machine data........................................................................................................................406
3.9.1.1 Displaying machine data ......................................................................................................406
3.9.1.2 NC-specific machine data ....................................................................................................406
3.9.2 Setting data ..........................................................................................................................408
3.9.3 System variables..................................................................................................................408
4 Kinematic chain ........................................................................................................................................411
4.1 Function description .............................................................................................................411
4.1.1 Characteristics .....................................................................................................................411
4.2 Commissioning.....................................................................................................................415
4.2.1 General ................................................................................................................................415
4.2.1.1 Overview ..............................................................................................................................415
4.2.1.2 Structure of the system variables.........................................................................................416
4.2.2 Machine data........................................................................................................................417
4.2.2.1 Maximum number of elements.............................................................................................417
4.2.2.2 Root element........................................................................................................................417
4.2.2.3 Maximum number of switches..............................................................................................417
4.2.3.1 Overview ..............................................................................................................................418
4.2.3.2 $NK_NAME ..........................................................................................................................419
4.2.3.3 $NK_NEXT...........................................................................................................................420
4.2.3.4 $NK_PARALLEL ..................................................................................................................421
4.2.3.5 $NK_TYPE ...........................................................................................................................422
4.2.3.6 Type-dependent variables for $NK_TYPE = "AXIS_LIN" .....................................................423
4.2.3.7 Type-dependent variables for $NK_TYPE = "AXIS_ROT" ...................................................426
4.2.3.8 Type-dependent variables for $NK_TYPE = "ROT_CONST"...............................................429
4.2.3.9 Type-dependent variables for $NK_TYPE = "OFFSET" ......................................................431
4.2.3.10 Type-dependent variables for $NK_TYPE = "SWITCH" ......................................................433
4.2.3.11 $NK_SWITCH ......................................................................................................................435
4.3 Programming........................................................................................................................436
4.3.1 Deletion of components (DELOBJ) ......................................................................................436
4.3.2 Index determination by means of names (NAMETOINT).....................................................439
4.4 Example ...............................................................................................................................440
4.4.1 Specifications .......................................................................................................................440
4.4.2 Part program of the machine model.....................................................................................442
Basic functions
Table of contents
4.5 Data lists ..............................................................................................................................445

4.5.1 Machine data........................................................................................................................445
5 Continuous-path mode, exact stop, LookAhead.......................................................................................447
5.1 Brief Description...................................................................................................................447
5.2 Exact stop mode ..................................................................................................................449
5.3 Continuous-path mode.........................................................................................................453
5.3.1 General functionality ............................................................................................................453
5.3.2 Velocity reduction according to overload factor ...................................................................455
5.3.3 Rounding..............................................................................................................................457
5.3.3.1 Rounding according to a path criterion (G641) ....................................................................460
5.3.3.2 Rounding in compliance with defined tolerances (G642/G643) ...........................................462
5.3.3.3 Rounding with maximum possible axial dynamic response (G644).....................................465
5.3.3.4 Rounding of tangential block transitions (G645) ..................................................................467
5.3.3.5 Rounding and repositioning (REPOS) .................................................................................469
5.3.4 LookAhead ...........................................................................................................................470
5.3.4.1 Standard functionality...........................................................................................................470
5.3.4.2 Free-form surface mode: Extension function .......................................................................476
5.4 Dynamic adaptations............................................................................................................480
5.4.1 Smoothing of the path velocity .............................................................................................480
5.4.2 Adaptation of the dynamic path response............................................................................483
5.4.3 Determination of the dynamic response limiting values .......................................................488
5.4.4 Interaction between the "smoothing of the path velocity" and "adaptation of the path
dynamic response" functions ...............................................................................................489
5.4.5 Dynamic response mode for path interpolation....................................................................492
5.4.6 Free-form surface mode: Basic functions ............................................................................494
5.5 Compressor functions ..........................................................................................................498
5.5.1 Compression of linear, circular and rapid traverse blocks ...................................................498
5.5.1.1 Function ...............................................................................................................................498
5.5.1.2 Commissioning.....................................................................................................................500
5.5.1.3 Programming........................................................................................................................502
5.5.2 Compression of short spline blocks .....................................................................................504
5.6 Contour/Orientation tolerance ..............................................................................................506
5.6.1 Commissioning.....................................................................................................................506
5.6.2 Programming........................................................................................................................507
5.6.2.1 Programming contour/orientation tolerance (CTOL, OTOL, ATOL).....................................507
5.6.2.2 Programming contour/orientation tolerance (CTOL, OTOL, ATOL) Additional information....510
5.7 Rapid traverse movements ..................................................................................................511
5.7.1 Function ...............................................................................................................................511
5.7.1.1 Rapid traverse......................................................................................................................511
5.7.1.2 Interpolation response of path axes for rapid traversing movements ..................................512
5.7.1.3 Tolerances for rapid traverse movements............................................................................514
5.7.1.4 Rapid traverse override........................................................................................................514
5.7.2 Commissioning.....................................................................................................................515
Basic functions
Table of contents
5.7.3 Programming........................................................................................................................516
5.7.3.1 Activating rapid traverse (G0) ..............................................................................................516
5.7.3.2 Switch on/off linear interpolation for rapid traverse movements (RTLION, RTLIOF) ...........518
5.7.3.3 Adapt tolerances for rapid traverse motion (STOLF, CTOLG0, OTOLG0) ..........................520
5.8 RESET behavior ..................................................................................................................523
5.9 Supplementary conditions....................................................................................................524
5.9.1 Block change and positioning axes......................................................................................524
5.9.2 Block change delay ..............................................................................................................524
5.10 Data lists ..............................................................................................................................525
5.10.1 Machine data........................................................................................................................525
5.10.1.2 Channelspecific machine data .............................................................................................525
5.10.2 Setting data ..........................................................................................................................527
6 Cross-channel program coordination and channel-by-channel running-in ...............................................529
6.1 Cross-channel program coordination ...................................................................................529
6.1.1 Cross-channel program coordination (INIT, START, WAITM, WAITMC, WAITE, SETM,
CLEARM) .............................................................................................................................529
6.1.2 Conditional wait (WAITMC) in the continuous path mode....................................................534
6.2 Running-in channel-by-channel ...........................................................................................538
6.2.1 Function ...............................................................................................................................538
6.2.2 Sequence .............................................................................................................................539
6.2.3 Single-channel view .............................................................................................................539
6.2.4 Multi-channel view................................................................................................................541
6.2.7 Examples .............................................................................................................................545
6.3.1 MDI mode: Path control mode and WAITMC.......................................................................546
6.3.2 Non-synchronous start of traversing motion after WAIT commands....................................547
7 Cross-channel axis interchange ...............................................................................................................549
7.1 Overview ..............................................................................................................................549
7.2 Commissioning.....................................................................................................................549
7.3 Programming: Releasing an axis (RELEASE) .....................................................................550
7.4 Programming: Fetching an axis (GET, GETD).....................................................................551
7.5 Automatic axis replacement .................................................................................................553
7.6 Axis replacement via PLC ....................................................................................................554
7.7 Axis interchange via axis container rotation.........................................................................557
7.8 Axis replacement with and without preprocessing stop .......................................................557
7.9 Axis exclusively controlled from the PLC .............................................................................559
7.10 Axis permanently assigned to the PLC ................................................................................560
7.11 Geometry axis in rotated frame and axis replacement.........................................................561
Basic functions
Table of contents
7.12 Axis replacement from synchronized actions.......................................................................562

7.13 Axis interchange for leading axes (gantry)...........................................................................564
7.14 State diagram.......................................................................................................................565
7.15.1 Axis replacement by PLC.....................................................................................................566
7.15.2 Block search with calculation ...............................................................................................566
7.16 Example ...............................................................................................................................567
7.17 Data lists ..............................................................................................................................568
7.17.1 Machine data........................................................................................................................568
7.17.2 Setting data ..........................................................................................................................571
8 Preprocessing...........................................................................................................................................573
8.2 Program handling.................................................................................................................575
8.3 Program call .........................................................................................................................577
8.4 Constraints ...........................................................................................................................579
8.5 Examples .............................................................................................................................581
8.5.1 Preprocessing individual files...............................................................................................581
8.5.2 Preprocessing in the dynamic NC memory..........................................................................582
8.6 Data lists ..............................................................................................................................583
8.6.1 Machine data........................................................................................................................583
9 Emergency stop........................................................................................................................................585
9.1 Brief Description...................................................................................................................585
9.2 Relevant standards ..............................................................................................................585
9.3 Emergency stop control elements........................................................................................586
9.4 Emergency stop sequence...................................................................................................587
9.5 Emergency stop acknowledgement .....................................................................................588
9.6 Data lists ..............................................................................................................................590
9.6.1 Machine data........................................................................................................................590
10 Various NC/PLC interface signals and functions......................................................................................591
10.2 Functions..............................................................................................................................591
10.2.1 Screen refresh behavior for overload...................................................................................591
10.2.2 Activate DEFAULT memory .................................................................................................592
10.2.3 Read/write PLC variable ......................................................................................................592
Basic functions
Table of contents
10.2.4 Access protection via password and keyswitch ...................................................................595

10.2.4.1 Password .............................................................................................................................597
10.2.4.2 Keyswitch positions (DB10, DBX56.4 to 7) ..........................................................................599
10.2.4.3 Parameterizable protection levels ........................................................................................600
10.2.5 Switching over motor/drive data sets ...................................................................................600
10.2.5.1 General Information .............................................................................................................600
10.2.5.2 Formatting interfaces ...........................................................................................................601
10.2.5.3 Request interface .................................................................................................................602
10.2.5.4 Display interface...................................................................................................................602
10.2.5.5 Example ...............................................................................................................................602
10.2.5.6 Overview of the interfaces....................................................................................................603
10.3 Examples .............................................................................................................................605
10.3.1 Parameter set changeover...................................................................................................605
10.4 Data lists ..............................................................................................................................607
10.4.1 Machine data........................................................................................................................607
10.4.1.1 Display machine data...........................................................................................................607
11 Auxiliary function outputs to PLC..............................................................................................................611
11.1.1 Function ...............................................................................................................................611
11.1.2 Definition of an auxiliary function .........................................................................................612
11.1.3 Overview of the auxiliary functions.......................................................................................612
11.2 Predefined auxiliary functions ..............................................................................................618
11.2.1 Overview: Predefined auxiliary functions .............................................................................619
11.2.2 Overview: Output behavior...................................................................................................630
11.2.3 Parameterization ..................................................................................................................633
11.2.3.1 Group assignment................................................................................................................633
11.2.3.2 Type, address extension and value .....................................................................................633
11.2.3.3 Output behavior....................................................................................................................635
11.3 Userdefined auxiliary functions ............................................................................................638
11.3.1.1 Maximum number of user-defined auxiliary functions..........................................................640
11.3.1.2 Group assignment................................................................................................................640
11.3.1.3 Type, address extension and value .....................................................................................640
11.3.1.4 Output behavior....................................................................................................................642
11.4 Associated auxiliary functions ..............................................................................................642
11.5 Type-specific output behavior ..............................................................................................644
11.6 Priorities of the output behavior for which parameters have been assigned........................646
11.7 Programming an auxiliary function.......................................................................................647
11.8 Programmable output duration.............................................................................................648
11.9 Auxiliary function output to the PLC .....................................................................................650
11.10 Auxiliary functions without block change delay ....................................................................650
Basic functions
Table of contents
11.11 M function with an implicit preprocessing stop.....................................................................651

11.12 Response to overstore .........................................................................................................652
11.13 Behavior during block search...............................................................................................653
11.13.1 Auxiliary function output during type 1, 2, and 4 block searches .........................................653
11.13.2 Assignment of an auxiliary function to a number of groups .................................................654
11.13.3 Time stamp of the active M auxiliary function ......................................................................656
11.13.4 Determining the output sequence ........................................................................................656
11.13.5 Output suppression of spindle-specific auxiliary functions...................................................658
11.13.6 Auxiliary function output with a type 5 block search (SERUPRO) .......................................661
11.13.7 ASUB at the end of the SERUPRO......................................................................................665
11.14 Implicitly output auxiliary functions.......................................................................................671
11.15 Information options...............................................................................................................672
11.15.1 Group-specific modal M auxiliary function display ...............................................................673
11.15.2 Querying system variables...................................................................................................674
11.16.1 General constraints ..............................................................................................................676
11.16.2 Output behavior....................................................................................................................677
11.17 Examples .............................................................................................................................678
11.17.1 Extension of predefined auxiliary functions..........................................................................678
11.17.2 Defining auxiliary functions ..................................................................................................680
11.18 Data lists ..............................................................................................................................684
11.18.1 Machine data........................................................................................................................684
12 Digital and analog NC I/O.........................................................................................................................687
12.1 Introduction ..........................................................................................................................687
12.2 Indirect I/O access via PLC..................................................................................................688
12.2.1 Brief description ...................................................................................................................688
12.2.4 Comparator inputs................................................................................................................692
12.2.5 Digital NC I/Os .....................................................................................................................692
12.2.5.1 Digital NC inputs ..................................................................................................................692
12.2.5.2 Digital NC outputs ................................................................................................................694
12.2.5.3 Connection and logic operations of fast digital I/Os .............................................................696
12.2.6 Analog NC I/Os ....................................................................................................................698
12.2.6.1 Analog NC inputs .................................................................................................................698
12.2.6.2 Analog NC outputs ...............................................................................................................700
12.2.6.3 Representation of the analog I/O values..............................................................................703
12.2.7 Comparator inputs................................................................................................................705
12.3 Direct I/O access via PLC ....................................................................................................709
12.3.2 Reading/writing: System variables .......................................................................................711
12.3.4 Examples .............................................................................................................................712
12.3.4.1 Writing to PLC-I/Os ..............................................................................................................712
Basic functions
Table of contents
12.3.4.2 Reading from PLC-I/Os........................................................................................................713

12.4 Direct I/O access without PLC .............................................................................................714
12.4.1 Brief description ...................................................................................................................714
12.4.2 Parameter assignment .........................................................................................................716
12.4.3 Reading/writing ....................................................................................................................717
12.4.3.1 System variables..................................................................................................................717
12.4.5 Examples .............................................................................................................................720
12.4.5.1 Writing to the NC I/O ............................................................................................................720
12.4.5.2 Reading from the NC I/O......................................................................................................721
12.4.5.3 Writing of the NC I/O with status query ................................................................................723
12.5 Data lists ..............................................................................................................................724
12.5.1 Machine data........................................................................................................................724
12.5.2 Setting data ..........................................................................................................................725
12.5.2.1 General setting data.............................................................................................................725
12.5.3 System variable....................................................................................................................725
12.5.4 Signals .................................................................................................................................726
12.5.4.1 Signals to NC .......................................................................................................................726
12.5.4.2 Signals from NC ...................................................................................................................727
13 Distributed systems ..................................................................................................................................729
13.1.1 Several operator panels on several NCUs (T:M:N)..............................................................729
13.1.2 NCU link ...............................................................................................................................731
13.1.2.1 Link communication .............................................................................................................731
13.1.2.2 Link variables .......................................................................................................................732
13.1.2.3 Link axes ..............................................................................................................................732
13.1.2.4 Lead link axes ......................................................................................................................733
13.1.2.5 Dependencies ......................................................................................................................733
13.1.2.6 Application example: Rotary indexing machine ...................................................................734
13.2 NCU link ...............................................................................................................................736
13.2.1 Link communication .............................................................................................................736
13.2.1.2 Link module..........................................................................................................................740
13.2.1.3 Parameter assignment: NC system cycles ..........................................................................740
13.2.1.4 Parameter assignment: Link communication .......................................................................743
13.2.1.5 Configuration........................................................................................................................743
13.2.1.6 Wiring the NCUs ..................................................................................................................743
13.2.1.7 Activation..............................................................................................................................744
13.2.2 Link variables .......................................................................................................................744
13.2.2.1 Properties of the link variables memory ...............................................................................745
13.2.2.2 Properties of the link variables .............................................................................................746
13.2.2.3 Write elements .....................................................................................................................747
13.2.2.4 Dynamic response during write............................................................................................747
13.2.2.5 System variable....................................................................................................................747
13.2.2.6 Synchronization of a write request .......................................................................................748
13.2.2.7 Example: Structure of the link variables memory.................................................................748
13.2.2.8 Example: Read drive data....................................................................................................750
13.2.3 Link axes ..............................................................................................................................751
Basic functions
Table of contents

13.2.3.2 Name of a link axis...............................................................................................................753
13.2.3.4 Auxiliary function output for spindles....................................................................................754
13.2.4 Axis container.......................................................................................................................757
13.2.4.3 Programming........................................................................................................................766
13.2.4.4 System variable....................................................................................................................768
13.2.4.5 Machining with axis container (schematic)...........................................................................769
13.2.4.6 Behavior in different operating states...................................................................................769
13.2.4.7 Behavior when withdrawing the release for axis container rotation .....................................770
13.2.5 Lead link axes ......................................................................................................................774
13.2.5.3 System variables to enter a leading value ...........................................................................777
13.2.5.5 Example ...............................................................................................................................777
13.2.6 System of units within a link group.......................................................................................777
13.3 Examples .............................................................................................................................778
13.3.1 Link axis ...............................................................................................................................778
13.3.2 Axis container coordination ..................................................................................................779
13.3.2.1 Axis container rotation without a part program wait .............................................................780
13.3.2.2 Axis container rotation with an implicit part program wait ....................................................780
13.3.2.3 Axis container rotation by one channel only (e.g. during power up) ....................................780
13.3.3 Evaluating axis container system variables .........................................................................780
13.3.3.1 Conditional branch ...............................................................................................................780
13.3.3.2 Static synchronized action with $AN_AXCTSWA ................................................................781
13.3.3.3 Wait for certain completion of axis container rotation ..........................................................781
13.3.4 Configuration of a multi-spindle turning machine .................................................................782
13.3.5 Lead link axis .......................................................................................................................791
13.3.5.1 Configuration........................................................................................................................791
13.3.5.2 Programming........................................................................................................................792
13.4 Data lists ..............................................................................................................................794
13.4.1 Machine data........................................................................................................................794
13.4.2 Setting data ..........................................................................................................................795
13.4.2.1 General setting data.............................................................................................................795
13.4.2.2 Axis/spindle-specific setting data .........................................................................................795
13.4.3 Signals .................................................................................................................................795
13.4.3.1 Signals from NC ...................................................................................................................795
13.4.3.2 Signals from HMI/PLC..........................................................................................................795
13.4.3.3 General online interface .......................................................................................................796
13.4.3.4 Signals from axis/spindle .....................................................................................................797
Basic functions
Table of contents
14 Memory configuration ...............................................................................................................................799

14.1 Introduction ..........................................................................................................................799
14.2 Active and passive file system .............................................................................................799
14.3 Commissioning.....................................................................................................................801
14.3.1 Configuration........................................................................................................................801
14.3.2 Reconfiguration ....................................................................................................................801
14.4 Configuration of the static user memory ..............................................................................802
14.4.1 Division of the static NC memory .........................................................................................802
14.4.2 Commissioning.....................................................................................................................804
14.5 Configuration of the dynamic user memory .........................................................................805
14.5.1 Division of the dynamic NC memory ....................................................................................805
14.5.2 Commissioning.....................................................................................................................807
14.6.1 Depending on the number of channels and tool carriers .....................................................807
14.6.2 Subsequent reduction of the number of channels and/or axes............................................808
14.7 Data lists ..............................................................................................................................808
14.7.1 Machine data........................................................................................................................808
A Appendix...................................................................................................................................................815
A.1 List of abbreviations .............................................................................................................815
A.2 Documentation overview......................................................................................................823
A.3 Available IPCs......................................................................................................................824
Index.........................................................................................................................................................825
Basic functions
Table of contents
Basic functions
Fundamental safety instructions 1
1.1 General safety instructions
WARNING
Danger to life if the safety instructions and residual risks are not observed
If the safety instructions and residual risks in the associated hardware documentation are not
observed, accidents involving severe injuries or death can occur.
● Observe the safety instructions given in the hardware documentation.
● Consider the residual risks for the risk evaluation.
WARNING
Malfunctions of the machine as a result of incorrect or changed parameter settings
As a result of incorrect or changed parameterization, machines can malfunction, which in turn
can lead to injuries or death.
● Protect the parameterization against unauthorized access.
● Handle possible malfunctions by taking suitable measures, e.g. emergency stop or
emergency off.
1.2 Warranty and liability for application examples

Application examples are not binding and do not claim to be complete regarding configuration,
equipment or any eventuality which may arise. Application examples do not represent specific
customer solutions, but are only intended to provide support for typical tasks.
As the user you yourself are responsible for ensuring that the products described are operated
correctly. Application examples do not relieve you of your responsibility for safe handling when
using, installing, operating and maintaining the equipment.
Basic functions
Fundamental safety instructions
1.3 Industrial security
Note
Industrial security
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Products and solutions from Siemens constitute one element of such a
concept.
Customers are responsible for preventing unauthorized access to their plants, systems,
machines and networks. Such systems, machines and components should only be connected
to an enterprise network or the Internet if and to the extent such a connection is necessary and
only when appropriate security measures (e.g. using firewalls and/or network segmentation)
are in place.
For additional information on industrial security measures that can be implemented, please
visit:
Industrial security (https://www.siemens.com/industrialsecurity)
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends that product updates are applied as soon as they become
available, and that only the latest product versions are used. Use of product versions that are
no longer supported, and failure to apply the latest updates may increase customer’s exposure
to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed at:
Industrial security (https://www.siemens.com/industrialsecurity)
Further information is provided on the Internet:

Industrial Security Configuration Manual (https://support.industry.siemens.com/cs/ww/en/
view/108862708)
Basic functions
WARNING
Unsafe operating states resulting from software manipulation
Software manipulations, e.g. viruses, Trojans, or worms, can cause unsafe operating states
in your system that may lead to death, serious injury, and property damage.
● Keep the software up to date.
● Incorporate the automation and drive components into a holistic, state-of-the-art industrial
security concept for the installation or machine.
● Make sure that you include all installed products into the holistic industrial security concept.
● Protect files stored on exchangeable storage media from malicious software by with
suitable protection measures, e.g. virus scanners.
● On completion of commissioning, check all security-related settings.
● Protect the drive against unauthorized changes by activating the "Know-how protection"
converter function.
Basic functions
Basic functions
Mode group, channel, program operation, reset
response 2
2.1 Product brief
Channel
An NC channel represents the smallest unit for manual traversing of axes and automatic
processing of part programs. At any one time, a channel will always be in a particular mode, e.g.
AUTOMATIC, MDI, or JOG. A channel can be regarded as an independent NC.
Mode group
A channel always belongs to a mode group. A mode group can also consist of several channels.
A mode group can be identified by the fact that all channels of the mode group are always in the
same mode at a particular time, e.g. AUTOMATIC, MDI, or JOG. This is ensured through the
NC internal mode logic.
A mode group can be regarded as an independent multi-channel NC.
Channel gaps
When channels are configured, placeholder channels can be provided in order to create as
uniform a configuration as possible over machines in a series. Only the channels that are
actually used are then activated.
Program test
The following options are available for testing or moving in position a new part program.
● Program execution without setpoint outputs
● Program execution in singleblock mode
● Program execution with dry run feedrate
● Skip part program blocks
● Block search with or without calculation.
Block search
The block search function enables the following program simulations for locating specific
program points:
● Type 1 without calculation at contour
● Type 2 with calculation at contour
Basic functions
Mode group, channel, program operation, reset response
2.1 Product brief
● Type 4 with calculation at block end point

● Type 5 automatic start of the selected program point with calculation of all required data
from history
● Automatic start of an ASUP after a block search
● Cascaded block search
● Cross-channel block search in "Program test" mode
Program operation
The execution of part programs or part program blocks in AUTOMATIC or MDI modes is
referred to as program operation. During execution, the program sequence can be controlled
by PLC interface signals and commands.
For each channel, basic settings or channel-specific machine data can be specified. These
basic settings affect, for example, G groups and auxiliary function output.
A part program can be selected only if the relevant channel is in the Reset state.
Furthermore, all further program runs are handled by PLC interface signals and the
corresponding commands.
● Start of part program or part program block
● Part program calculation and program control
● RESET command, program status, and channel status
● Responses to operator and program actions
● Eventdriven program calls
Asynchronous subprograms (ASUPs), interrupt routines

Interrupt inputs allow the NC to interrupt the the current part program execution so that it can
react to more urgent events in interrupt routines or ASUPs.
Single block
With the single-block function, the user can execute a part program block-by-block.
There are 3 types of setting for the single-block function:
● SLB1: = IPO single block
● SLB2: = decode single block
● SLB3: = stop in cycle
Basic block display

A second basic block display can be used with the existing block display to display all blocks
that produce an action on the machine.
The actually approached end positions are shown as an absolute position. The position values
refer either to the workpiece coordinate system (WCS) or the settable zero system (SZS).
Basic functions
2.2 Mode group
Program execution from external source

When complex workpieces are machined, the NC may not have enough memory for the
programs. Using the function "Execution from external source" or "EES (execution from
external storage) enables part programs to be called and executed from an external memory
(e.g. from the hard disk).
Behavior after POWER ON, Reset, ...

The control-system response after:
● Power up (POWER ON)
● Reset/part program end
● Part program start
can be modified for functions, such as G commands, tool length compensation, transformation,
coupled axis groupings, tangential follow-up, programmable synchronous spindle for certain
system settings through machine data.
Subprogram call with M, T and D functions

For certain applications, it may be advantageous to replace M, T or D functions as well as a few
NC language commandsSPOS, SPOSA, by a subprogram call. This can be used, for example,
to call the tool change routine.
Relevant machine data can be used to define and control subprograms having M, T or D
functions. For example, for a gear stage change.
Program runtime/part counter

Information on the program runtime and the part count is provided to assist the machine tool
operator.
The functions defined for this purpose are not identical to the functions of tool management and
are intended primarily for systems without tool management.
2.2 Mode group
Mode group
In a mode group, multiple channels if an NC are grouped together to form one processing unit.
In principle, it is an independent "NC" within an NC.
Basic functions
2.2 Mode group
A mode group is essentially characterized by the fact that all channels assigned to it are any
instant are always in the same mode (AUTOMATIC, JOG, MDI).
Note
This description continues on the assumption that there is one mode group and one channel.
Functions which require multiple channels (e.g. "Axis interchange" function), are described in:
Further information:
Further information can be found at Cross-channel program coordination and channel-by-
channel running-in (Page 529).
Further information can be found under Parameterization

A channel is assigned to a mode group in the machine data:
MD10010 $MN_ASSIGN_CHAN_TO_MODE_GROUP[<channel index>] = mode group
number
All channels with the same mode group number form one mode group.
Note
A NC always comprises one mode group with one channel by default. It is not possible to
parameterize an NC without a channel.
Mode-group-specific NC/PLC interface signals

The mode-group-specific NC/PLC interface signals are in data block DB11.
Basic functions
2.2 Mode group
The mode-group-specific NC/PLC interface essentially comprises the following interface

signals:
● Request signals PLC → NC
– Mode group reset
– Mode group stop axes plus spindle
– Mode group stop
– Mode changeover inhibit
– Mode: JOG, MDI, AUTOM.
– Single block: Type A, Type B
– Machine function REF, REPOS, TEACH IN, INC x
● NC → PLC status signals
– Mode strobe: JOG, MDI, AUTOMATIC
– Machine function strobe: REF, REPOS, TEACH IN
– All channels in the reset state
– Mode group has been reset
– Mode group Ready
– Active mode: JOG, MDI, AUTOMATIC
– Active machine function: REF, REPOS, TEACH, INC x
Activated and non-activated channels, channel gaps
Activated channel
A channel with a mode group number ≠ 0 is an active channel.
Non-activated channel
A channel with a mode group number 0 is a non-activated channel. It does not take up any
memory internally in the control.
Channel gaps
A channel with a mode group number 0 is not only a non-activated channel. It is also a so-called
channel gap in the sequence of the channels.
The advantage of channel gaps is that the configuration data can be kept largely identical in a
series of similar machines. For the specific commissioning, only those channels are activated
Basic functions
2.2 Mode group
that are required for the machine in question. The unoccupied memory can be freely used as
additional user memory.
Table 2-1 Example
Machine data Meaning

MD10010 $MN_AS‐ Channel 1, mode group 1
SIGN_CHAN_TO_MODE_GROUP[0] = 1
MD10010 $MN_AS‐ Channel 3, not used
2.2.1 Mode group stop
Function
The following NC/PLC interface signals are used to stop the traversing motions of the axes or
of the axes and spindles in all mode group channels and to interrupt part program execution:
DB11 DBX0.5 (mode group stop)
DB11 DBX0.6 (mode group stop, axes plus spindles)
2.2.2 Mode group reset
Function
A mode group reset is requested via a mode group-specific NC/PLC interface signal:
DB11 DBX0.7 = 1 (mode group reset)
Effect
Effect on the channels of mode group:
● Part program preparation (preprocessing) is stopped.
● All axes and spindles are decelerated to zero speed according to their acceleration curves
without contour violation.
● Any auxiliary functions not yet output to the PLC are no longer output.
● The preprocessing pointers are set to the interruption point, and the block pointers are set
to the beginning of the appropriate part programs.
Basic functions
2.3 Mode types and mode type change
● All initial settings (e.g. the G commands) are set to the parameterized values.
● All alarms with "Channel reset" criterion are canceled.
If all the channels of the mode group are in reset state, then:
● All alarms with "Mode group reset" cancel criterion are canceled.
● The NC/PLC interface indicates completion of the mode group reset and the mode group's
readiness to operate:
DB11 DBX6.7 (all channels in the reset state)
DB11 DBX6.3 = 1 (mode group ready)
Unique mode
All channels of a mode group are always in the same mode:
● AUTOMATIC
● JOG
● MDI
If individual channels are assigned to different mode groups, a channel switchover activates the
corresponding mode group. This allows mode changes to be initiated via a channel
switchover.
Modes
The following modes are available:
● AUTOMATIC
Automatic execution of part programs:
– Part program test
– All channels of the mode group can be active at the same time.
● JOG in Automatic
JOG in AUTOMATIC is an extension of AUTOMATIC mode intended to simplify use. JOG
can be executed without leaving AUTOMATIC mode if boundary conditions so permit.
Basic functions
● JOG
Manual traversing of axes via traversing keys of the machine control panel or via a
handwheel connected to the machine control panel:
– Channel-specific signals and interlocks are taken into account for motions executed by
means of an ASUP or via static synchronized actions.
– Couplings are taken into account.
– Every channel in the mode group can be active.
● MDI
Manual Data Automatic (the blocks are entered via the user interface)
– Restricted execution of part programs and part program sections.
– Part program test
– A maximum of 1 channel per mode group can be active (applies only to TEACH IN).
– Axes can only be traversed manually in subordinate machine functions such as JOG,
REPOS or TEACH IN.
Applies to all modes
Cross-mode synchronized actions

Modal synchronized actions can be executed by means of IDS in all modes for the following
functions parallel to the channel:
● Command axis functions
● Spindle functions
● Technology cycles
Selection
The user can select the desired mode by means of softkeys on the user interface.
This selection (AUTOMATIC, MDI, or JOG) is forwarded to the PLC on the NC/PLC interface,
but is not activated:
DB11 DBX4.0, 0.1, 0.2 (strobe mode)
Activation and priorities

The mode of the mode group is activated via the NC/PLC interface:
DB11 DBX0.0, 0.1, 0.2 (mode)
If several modes are selected at the same time, the following priority applies:
Priority Mode Mode group signal (NC → PLC)

1st priority, high JOG DB11 DBX0.2
2nd priority, medium MDI DB11 DBX0.1
3rd priority, low AUTOMATIC DB11 DBX0.0
Basic functions
Display
The current mode of the mode group is displayed via the NC/PLC interface:
DB11 DBX6.0, 0.1, 0.2 (active mode)
Mode group signal (NC → PLC) Active operating mode

DB11 DBX6.2 JOG
DB11 DBX6.1 MDI
DB11 DBX6.0 AUTOMATIC
Machine functions
Machine functions can be selected within a mode that also apply within the mode group:
● Machine functions within the JOG mode
– REF (reference point approach)
– REPOS (repositioning)
– JOG retract (retraction motion in the tool direction)
● Machine functions within the MDI mode
– REF (reference point approach)
– REPOS (repositioning)
– TEACHIN (teach-in of axis positions)
NC/PLC interface signals

● DB11 DBX5.0, 0.1, 0.2 (machine function strobe): Requirement
● DB11 DBX1.0, 0.1, 0.2 (machine function): Activation
● DB11 DBX7.0-2 (active machine function): Feedback signal
Channel states
● Channel reset
The machine is in its initial state. This is defined by the machine manufacturer's PLC
program, e.g. after POWER ON or at the end of the program.
● Channel active
A program has been started, and the program is being executed or a reference point
approach is in progress.
● Channel interrupted
The running program or reference point approach has been interrupted.
Functions within modes

Modes are supplemented through user-specific functions. The individual functions are
technology- and machine-independent and can be started and/or executed from the three
channel states "Channel reset", "Channel active" or "Channel interrupted".
Basic functions
Boundary condition for the TEACH IN machine function

TEACH IN is not permissible for leading or following axes of an active axis grouping, e.g. for:
● Gantry-axis grouping or a gantry axis pair
● Coupled-axis grouping of master and slave axis
JOG in Automatic
JOG in AUTOMATIC mode is permitted if the mode group is in "RESET" state and the axis is
jog-capable. "RESET" state for the mode group means:
● All channels are in the "RESET" state
● All programs are canceled
● DRF is not active in any channel
An axis is JOG-capable if it is not in any of the following states:
● PLC axis as concurrent positioning axis (request of the axis from the PLC)
● Command axis (the axis has been programmed by a synchronized action and the motion
has not been completed yet)
● Rotating spindle (spindle rotating despite RESET)
● An asynchronous reciprocating axis
Note: The "jog-capable" property is independent of the "JOG in AUTOMATIC" function.
Activation
The function "JOG in AUTOMATIC" can be activated with the machine data:
MD10735 $MN_JOG_MODE_MASK
● Before POWER ON, the following machine data must be set:
MD10735 $MN_JOG_MODE_MASK, bit 0 = 1
● The user switches to AUTO (PLC user interface DB11 DBX0.0 = 0→1 edge). "JOG in
AUTOMATIC" is then active if the NC previously had channel state "RESET" and program
state "Aborted" in all mode group channels. The axis in question must also be "jog-capable".
DRF must be deactivated (if not already deactivated).
● RESET is initiated or the running program is finished with M30/M2 in all mode group
channels that do not have channel state "Reset" and program state "Aborted".
● The relevant axis is automatically made "JOG-capable" (e.g. axis interchange: PLC → NC).
Note: In most applications, the axes to be traversed are "JOG-capable" and with the switchover
to AUTOMATIC, "JOG in AUTOMATIC" is also active.
Characteristics
● The +/– keys cause a JOG motion, and the mode group is switched internally to JOG. (i.e.
"Internal JOG").
● Moving the handwheels causes a JOG motion, and the mode group is switched internally to
JOG, unless DRF is active.
Basic functions
● An ongoing JOG motion is not complete until the end position of the increment has been
reached (if this has been set) or the motion has been aborted with "Delete distance-to-go".
In this way an increment can be stopped using Stop and then moved to the end using Start.
The NC remains in "Internal JOG" during this time. A partial increment is possible, but it must
not be interrupted using Stop. There is a mode in which releasing the travel key causes
interruption within an increment.
● Without any JOG motion, "JOG in AUTOMATIC" responds in the same way as "Automatic".
In particular, the Start key starts the selected part program and the appropriate HMI softkey
initiates a block search.
● If JOG motion is active, the NC is internally in JOG mode, and, thus, a block search request
is refused and a Start cannot start the part program. Start starts any remaining increment or
has no effect.
● While a mode group axis is being traversed in JOG mode, the mode group remains
internally in JOG mode.
Comment: This phase can begin with the JOG motion of an axis and end with the end of the
JOG motion of another axis.
● Axis interchange is not possible for an axis with active JOG movement (the axis might
change the mode group). The NC blocks any axis interchange attempt.
● The PLC user interface indicates "Automatic" mode:
– DB11 DBX6.0, 6.1, 6.2 = 1
– DB11 DBX7.0, 7.1, 7.2 = 0
● In "JOG in AUTOMATIC", the NC/PLC interface displays whether the mode group is in
"Mode group RESET".
– DB11 DBX6.4 (mode group has been reset, mode group 1)
● In "JOG in AUTOMATIC", the NC/PLC interface displays whether the NC has automatically
switched to "Internal JOG".
– DB11 DBX6.5 (NC internal JOG active, mode group 1)
Boundary conditions
"JOG in AUTOMATIC" can only switch internally to JOG if the mode group is in the "mode group
reset" status, i.e. it is not possible to jog immediately in the middle of a stopped program. The
user can jog in this situation by pressing the JOG key or the Reset key in all channels of the
mode group.
Selecting AUTOMATIC disables the INC keys and the user can/must press the INC keys again
to select the desired increment. If the NC switches to "Internal JOG", the selected increment is
retained.
If the user attempts to jog the geometry or orientation axes, the NC switches to "Internal JOG"
and the movement executed. Several axes can be physically moved in this way; they must all
be "JOG-capable".
Basic functions
Following the JOG motion, the NC deactivates "Internal JOG" again and selects AUTO mode
again. The internal mode change is delayed until the movement is complete. This avoids
unnecessary multiple switching operations, e.g. when using the handwheel. The PLC can only
rely on the "Internal JOG active" PLC signal.
The NC will then switch to "Internal JOG" even if the axis is not enabled.
2.3.1 Monitoring functions and interlocks of the individual modes
Channel status determines monitoring functions
Monitoring functions in operating modes

Different monitoring functions are active in individual operating modes. These monitoring
functions are not related to any particular technology or machine.
In a particular mode only some of the monitoring functions are active depending on the
operating status. The channel status determines which monitoring functions are active in which
mode and and in which operating state.
Interlocking functions in operating modes

Different interlocks can be active in the different operating modes. These interlocking functions
are not related to any particular technology or machine.
Almost all the interlocks can be activated in every mode, depending on the operating status.
2.3.2 Mode change
Introduction
A mode change is requested and activated via the mode group interface (DB11). A mode group
will either be in AUTOMATIC, JOG, or MDI mode, i.e. it is not possible for several channels of
a mode group to take on different modes at the same time.
What mode transitions are possible and how these are executed can be configured in the PLC
program on a machine-specific basis.
Note
The mode is not changed internally until the signal "Channel status active" is no longer pending.
For error-free mode change however, all channels must assume a permissible operating mode.
Basic functions
2.4 Channel
Possible mode changes

The following table shows possible mode changes for a channel:
AUTOMATIC JOG MDI

AUTO MDI Manual traversing AUTO
Reset Inter‐ Reset Inter‐ Inter‐ Reset Inter‐ Active Inter‐
rupted rupted rupted rupted rupted
AUTOMATIC X X X
JOG X X X X X
MDI X X X X
Possible mode changes are indicated by an "X".
Special cases
● Error during mode change
If a mode change request is rejected by the system, the error message "Operating mode
cannot be changed until after NC Stop" is output. This error message can be cleared without
changing the channel status.
● Mode change disable
A mode change can be prevented by means of interface signal:
DB11, DBX0.4 (mode change disable).
This suppresses the mode change request.

The user must configure a message to the operator indicating that mode change is disabled.
No signal is issued for this by the system.
● Mode change from MDI to JOG
If all channels of the mode group are in Reset state after a mode change from MDI to JOG,
the NC switches from JOG to AUTO. In this state, part program commands START or INIT
can be executed.
If a channel of the mode group is no longer in Reset state after a mode change, the part
program command START is rejected and Alarm 16952 is issued.
2.4 Channel
2.4.1 Properties
In a channel of the NC, the part programs defined by the user are executed.
The following properties characterize a channel:
● A channel is always assigned to a mode group.
● A channel can only execute one part program at any point in time.
● Machine, geometry, and special axes and spindles are assigned to a channel. Only these
can be traversed via the part program executed in the channel.
Basic functions
2.4 Channel
● A channel consists of the internal units

– Preprocessing (program decoding and block preparation)
– Main run (path and axis interpolation).
● A channel has an interface with the PLC. Via this NC/PLC interface, the PLC user program
can read various channel-specific status data and write requests to the channel.
● In a channel, channel-specific ones are active (see Function Manual Tools under Tool
offset).
● Channel-specific coordinate systems are active in a channel.
● Each channel has a unique channel name by default. The defined channel name can be
changed in machine data:
MD20000 $MC_CHAN_NAME = "<channel name>"
Multiple channels can be combined to form a mode group. The channels of a mode group are
always in the same mode (AUTOMATIC, JOG, MDI).
Channel configuration
Channels can be filled with their own channel name via the following machine data:
MD20000 $MC_CHAN_NAME (channel name)
The various axes are then assigned to the available channels via machine data. There can be
only one setpoint-issuing channel at a time for an axis/spindle. The axis/spindle actual value
can be read by several channels at the same time. The axis/spindle must be registered with the
relevant channel.
The following channel-specific settings can also be made using machine data:
● Position of deletions or the basic program settings of G groups via the machine data:
MD20150 $MC_GCODE_RESET_VALUES (reset setting of the G groups)
● Auxiliary function groups regarding the combination and the output time
● Transformation conditions between machine axes and geometry axes
● Other settings for the execution of a part program
Change in the channel assignment

An online change in the channel configuration cannot be programmed in a part program or PLC
user program. Changes in the configuration must be made via the machine data. The changes
become effective only after a new POWER ON.
Container axes and link axes

An axis container combines a group of axes in a container. These axes are referred to as
container axes. This involves assigning a pointer to a container slot (ring buffer location within
the relevant container) to a channel axis. One of the axes in the container is located temporarily
in this slot.
Each machine axis in the axis container must be assigned at all times to exactly one channel
axis.
Basic functions
2.4 Channel
Link axes can be assigned permanently to one channel or dynamically (by means of an axis
container switch) to several channels of the local NCU or the other NCU. A link axis is a non-
local axis from the perspective of one of the channels belonging to the NCU to which the axis
is not physically connected.
The assignment between the link axes and a channel is implemented as follows:
● For permanent assignment using machine data:
Allow the direct logic machine axis image to show link axes.
● For dynamic assignment:
Allow the axis container slot machine data to show link axes.
You can find further information about link and container axes in:
Further Information:
"Basic Functions" Function Manual
Interface signals
The signals of the 1st channel are located in the NC/PLC interface in DB21, the signals from
channel 2 are located in DB22. The channel or channels can be monitored and controlled from
the PLC or NC.
Channel-specific technology specification

The technology used can be specified for each channel:
MD27800 $MC_TECHNOLOGY_MODE
In the delivery state, machine data is active for milling as standard.
Spindle functions using a PLC

In addition to function block FC18, spindle functions can also be started and stopped via the
axial NC/PLC interface signals in parallel to part programs that are running.
Requirements:
● Channel status: "Interrupted" or "RESET"
● Program status: "Interrupted" or "canceled"
The following functions can be controlled from the PLC via interface signals:
● Stop (corresponds to M5)
● Start with clockwise direction of rotation (corresponds to M3)
● Start with counter-clockwise direction of rotation (corresponds to M4)
● Select gear stage
● Positioning (corresponds to M19)
For several channels, the spindle started by the PLC is active in the channel to which it is
assigned at the start.
For more information about the special spindle interface, see Function Manual Axes and
Spindles under Spindles.
Basic functions
2.4 Channel
PLC-controlled single-axis operations

An axis can also be controlled from the PLC instead of from a channel. For this purpose, the
PLC requests the axis from the NC via the NC/PLC interface:
DB31, ... DBX28.7 = 1 (PLC controls axis)
The following functions can be controlled from the PLC:
● Cancel axis/spindle sequence (equivalent to delete distance-to-go)
● Stop or interrupt axis/spindle
● Resume axis/spindle operation (continue the motion sequence)
● Reset axis/spindle to the initial state
For more information on the channel-specific signal exchange (PLC → NC), see Function
Manual PLC and Basic Program under Basic PLC program.
The exact functionality of independent single-axis operations is described in:
Further information
Function Manual Axes and Spindles; Positioning axes
2.4.2 Start inhibit, global and channel-specific
Function
In ShopMill/ShopTurn, a program can only be started by default in the Machine area. The start
in the other areas, e.g. tools, is locked via a start lock (PI service).
The automated start lock sequences can be deactivated using an NC/PLC interface signal.
Deactivate start lock

An active start lock is deactivated with the interface signal:
DB21, ... DBX7.5 (deactivate start lock)
Machine data
The machine data is used to set an alarm if a start is requested with the start lock set:
MD11411 $MN_ENABLE_ALARM_MASK, bit 6
Basic functions
2.5 Program operation
OPI variables
Variable Description
startLockState Status of the global start lock
chanStartLockState Status of the channel-specific start lock
startRejectCounter Start counter for a global start lock
startLockCounter Start counter for a channel-specific start lock
PI services
Setting the start lock (_N_STRTLK)

The start lock can be set either globally or channel-specifically using the PI service
_N_STRTLK.
● Global start lock
If the global start lock is set, then the start of an NC program is locked in all channels. An
already running NC program is not affected. Only the next start of an NC program is locked.
● Channel-specific start lock
As a result of the channel-specific start lock, the start of an NC program is only locked in the
AUTOMATIC mode and in the "Reset" channel status.
Reset of the global or channel-specific start lock (_N_STRTUL)

With the PI service _N_STRTUL, the global or channel-specific start lock can be reset.
2.5.1 Program operation mode
Definition
Program mode is present when in the AUTOMATIC or MDI operating modes, NC programs or
PC program blocks are processed.

The program mode can be influenced by the PLC user program via mode group- and channel-
specific NC/PLC interface signals or returns the appropriate feedbacks to the PLC user
program.
Further information
An overview of the NC/PLC interface signals can be obtained in the Function Manual PLC;
Interface signals
Basic functions
2.5.2 Initial settings
Basic settings can be programmed in channel-specific machine data for each channel. These
basic settings affect, for example, G groups and auxiliary function output.
Auxiliary function output

The timing for output of auxiliary functions can be predefined via machine data
AUXFU_x_SYNC_TYPE (MD22200, 22210, 22220, 22230, 22240, 22250, 22260), (output
timing for M, S, T, H, F, D, E functions). For more detailed explanations, see Section "Auxiliary
function outputs to PLC (Page 611)".
G groups
An initial programming setting can be specified for each of the available G groups using
MD20150 $MC_GCODE_RESET_VALUES (reset state of G groups). This basic setting is
automatically active during program start or in Reset until it is deselected by a G command from
the same G group.
Via MD22510 $MC_GCODE_GROUPS_TO_PLC (G commands which are output to interface
NC-PLC after block change / RESET), the output of the G commands to the PLC interface can
be activated.
Further information
A list of G groups with the associated G commands can be found in the "NC Programming"
Programming Manual.
Basic configuration of the NC language scope

Certain basic configurations of the NC language scope can be generated (configurable) via
machine data. The options and functions of the NC language scope is specially tailored
(configured) to the needs of the user.
2.5.2.1 Machine data
NC language scope
The way that non-active options and functions should be handled with language commands
can be set with the following machine data:
MD10711 $MN_NC_LANGUAGE_CONFIGURATION = <value>
Value Meaning
0 All language commands are available. Whether or not the needed function is activated can only be recognized
upon execution.
1 All language commands are available.
Language commands for non-enabled options are recognized during the program interpretation ⇒ Alarm 12553
"Option/function is not active".
2 Only the language commands of the enabled options are available.
Language commands for non-enabled options are recognized during the program interpretation ⇒ Alarm 12550
"Name not defined or option/function available".
Basic functions
Value Meaning
3 All language commands are available.
Language commands of not activated functions are recognized during the program interpretation ⇒ Alarm 12553
"Option/function is not active".
Example:
1. Option set for the cylinder surface transformation.
2. The cylinder surface transformation in the machine data MD24100 $MC_TRAOF_TYPE_1 is not activated
3. Alarm 12553 is issued already when programming the TRACYL command.
4 Only the language commands of the active functions are available.
Language commands of non-active functions are not recognized ⇒ Alarm 12550 "Name not defined or option/
function not available".
Note
Whether the associated language commands are generally unavailable in the Siemens language or whether this
is true only on the corresponding system cannot be distinguished in this scenario.
2.5.2.2 Programming
The function "STRINGIS(...)" checks whether the specified character string is available as
element of the NC programming language in the actual language scope.
The following elements of the NC programming language can be checked:
● G commands of all existing G groups
● DIN or NC addresses
● Functions
● Procedures
● Keywords
● System data, such as machine data $M... , setting data $S... or option data $O...
● System variables $A... , $V... , $P...
● Arithmetic parameters R...
● Cycle names of activated cycles
● GUD and LUD variables
● Macro names
● Label names
Definition
INT STRINGIS(STRING <name>)
Syntax
<return value> = STRINGIS(<name>)
Basic functions
Meaning
STRINGIS(): Test function with return value

<name>: Character string to be tested
<return The return value is coded in the first three decimal places yxx
value>: 000 The specified string is not an element of the current language scope 1).
100 The specified string is an element of the NC programming language, but
currently cannot be programmed (option/function is inactive).
2xx The specified string is a programmable element of the current language
scope (option/function is active).
Detailed information is contained in the first and second decimal places:
xx Meaning
01 DIN address or NC address2)
02 G command (e.g. G04, INVCW)
03 Function with return value
04 Function without return value
05 Keyword, e.g. DEFINE
06 Machine ($M...), setting ($S...) or option data ($O...)
07 System parameter, e.g. system variable ($...) or arithmetic param‐
eter (R...)
08 Cycle (the cycle must be loaded to the NC and the cycle program
must be active 3) )
09 GUD variable (the GUD variable must be defined in the GUD defi‐
nition files and the GUD variables activated)
10 Macro name (the macro must be defined in the macro definition files
and macros activated) 4)
11 LUD variable of the actual part program
12 ISO G command (ISO language mode must be active)
400 The specified string is an NC address that was not identified as DIN ad‐
dress or NC address (xx==01) or macro name (xx==10), and is not G or
R 2)
y00 No specific assignment possible
1) Depending on the control, under certain circumstances, only a subset of the Siemens NC language
commands are known, e.g. SINUMERIK 802D sl. For these controls, for strings that are principally
Siemens NC language commands, a value of 0 is returned. This behavior can be changed using
MD10711 $MN_NC_LANGUAGE_CONFIGURATION. If MD10711 = 1, then a value of 100 is always
returned for Siemens NC language commands.
2) NC addresses are the following letters: A, B, C, E, I, J, K, Q, U, V, W, X, Y, Z. These NC addresses
can also be programmed with an address extension. The address extension can be specified when
checking with STRINGIS. Example: 201 == STRINGIS("A1").
The letters: D, F, H, L, M, N, O, P, S, T are NC addresses or auxiliary functions that are defined by the
user. A value of 400 is always returned for these. Example: 400 == STRINGIS("D"). These NC ad‐
dresses cannot be specified with address extension when checking with STRINGIS.
Example: 000 == STRINGIS("M02"), but 400 == STRINGIS("M").
3) Names for cycle parameters cannot be checked with STRINGIS.
4) Address defined as macro, e.g. G, H, M, L, is identified as macro.
Basic functions
Examples
In the following examples it is assumed that the specified NC language element, unless noted
otherwise, can in principle be programmed in the control.
1. String "T" is defined as auxiliary function:
400 == STRINGIS("T")
000 == STRINGIS ("T3")
2. String "X" is defined as axis:
201 == STRINGIS("X")
201 == STRINGIS("X1")
3. String "A2" is defined as NC address with extension:
201 == STRINGIS("A")
201 == STRINGIS("A2")
4. String "INVCW" is defined as named G command:
202 == STRINGIS("INVCW")
5. String "$MC_GCODE_RESET_VALUES" is defined as machine data:
206 == STRINGIS("$MC_GCODE_RESET_VALUES")
6. String "GETMDACT" is an NC language function:
203 == STRINGIS("GETMDACT ")
7. String "DEFINE" is a keyword:
205 == STRINGIS("DEFINE")
8. String "$TC_DP3" is a system parameter (tool length component):
207 == STRINGIS("$TC_DP3")
9. String "$TC_TP4" is a system parameter (tool size):
207 == STRINGIS("$TC_TP4")
10.String "$TC_MPP4" is a system parameter (magazine location status):
– Tool magazine management is active: 207 == STRINGIS("$TC_MPP4") ;
– Tool magazine management is not active: 000 == STRINGIS("$TC_MPP4")
See also the paragraph below: Tool magazine management.
11.String "MACHINERY_NAME" is defined as GUD variable:
209 == STRINGIS("MACHINERY_NAME")
12.String "LONGMACRO" is defined as macro:
210 == STRINGIS("LONGMACRO")
13.String "MYVAR" is defined as LUD variable:
211 == STRINGIS("MYVAR")
14.String "XYZ" is a command that is not known in the NC, GUD variable, macro or cycle name:
000 == STRINGIS("XYZ")
Basic functions
Supplementary conditions
Tool magazine management

If the tool magazine management function is not active, STRINGIS() supplies the system
parameters of the tool magazine management, independent of the machine data
● MD10711 $MN_NC_LANGUAGE_CONFIGURATION
always a value of 000.
ISO Mode
If the "ISO Mode" function is active:
STRINGIS() checks the specified string initially as SINUMERIK G command:
● MD18800 $MN_MM_EXTERN_LANGUAGE (activation of external NC languages)
● MD10880 $MN_ MM_EXTERN_CNC_SYSTEM (control system to be adapted)
For active "ISO Mode", STRINGIS() checks the specified character string first whether it
belongs to the SINUMERIK G command.
If the string is not a SINUMERIK G command, it is subsequently checked whether it is an ISO
G command.
Programmed switchover of the ISO Mode

Programmed switchovers with the G290 (SINUMERIK mode) and G291 (ISO Mode)
commands have no effect on STRINGIS().
2.5.3 Selection and start of an NC program
Selection
An NC program can be selected only if the relevant channel is in the reset status.
● DB21, ... DBX35.7 == 1 (reset)
Start
An NC program is started by two different events:
1. DB21, ... DBX7.1 = 1 (NC start), the signal is normally initiated by pressing the "NC start" key
on the machine control panel.
2. START command in an NC program of another active channel. The channel must be in the
AUTOMATIC or MDI mode and in the "reset" or "interrupted" status.
– DB21, ... DBX35.7 == 1 (reset)
– DB21, ... DBX35.6 == 1 (interrupted)
Basic functions
Initial conditions
An NC program can be started only when the following initial conditions are satisfied.
● DB11 DBX4.4 == 1 (mode group ready)
● DB11 DBX0.7 == 0 (mode group reset)
● DB21, ... DBX1.7 == 0 (activate program test)
● DB21, ... DBX7.0 == 0 (NC start lock)
● DB21, ... DBX7.2 == 0 (NC stop at block limit)
● DB21, ... DBX7.3 == 0 (NC stop)
● DB21, ... DBX7.4 == 0 (NC stop, axes plus spindles)
● DB21, ... DBX7. 7 == 0 (reset)
● DB10 DBX56.1 == 0 (emergency stop)
● No axis or NC-specific alarm may be pending
Execution of command
The part program or the part program block is automatically executed and the following
interface signals are set:
● DB21, ... DBX35.5 (channel status reset)
● DB21, ... DBX35.0 (program status running)
The program is processed until the end of the program has been reached or the channel is
interrupted or aborted by a STOP or RESET command.
Further information
A detailed description of the interface signals can be found in the Function Manual PLC.
A detailed description of the NC variables is provided in the List Manual NC Variables
Alarms
Under certain conditions the START command will have no effect and one of the following
alarms will be triggered:
● 10200 "No NC Start permitted with active alarm"
● 10202 "No NC Start permitted with active command"
● 10203 "No NC Start permitted for non-referenced axes"
Further information
Diagnostics Manual Alarms
Basic functions
2.5.4 Program interruption
Prerequisites
A program interruption is performed only when the channel and the NC program are active:
● DB21, ... D35.5 == 1 (channel: active)
● DB21, ... D35.0 == 1 (program: running)
Program interruption
The program processing can be interrupted by the following events:
● DB21, ... DBX7.2 == 1 (NC stop at block limit)
● DB21, ... DBX7.3 == 1 (NC stop)
● DB21, ... DBX7.4 == 1 (NC stop, axes plus spindles)
● DB21, ... DBX2.0 == 1 (single block)
● Programmed M00 or M01 command in the processed NC program
The channel and the NC program are then in the "interrupted" status:
● DB21, ... D35.6 == 1 (channel interrupted)
● DB21, ... D35.3 == 1 (program interrupted)
Further information
A detailed description of the interface signals can be found in the Function Manual PLC
Sequence
The following actions are performed when a program interruption is detected:
● Interrupt the program processing:
– At the next block limit for the following events: "NC stop at block limit", M00, M01 or single
block
– Immediately: All other events
● The traversing axes of the channel are stopped via a braking ramp. The braking of the axes
can extend over several blocks.
● The block indicator shows the current block at the point of interruption.
● The auxiliary functions that have not been output before the point of interruption are no
longer output.
Basic functions
Possible actions in the interrupt state

Various functions can be performed in the channel during a part program interruption, for
example:
● Overstore
● Block search
Further information can be found at Block search, types 1, 2, and 4: (Page 121).
● Repositioning (REPOS)
Further information can be obtained at User-specific ASUB for RET and REPOS
(Page 181).
● Oriented tool retraction
Further information
– "NC Programming" Programming Manual
– "Tools" Function Manual
● ASUB (see Section "Asynchronous subprograms (ASUPs) (Page 167)")
● DRF function, shifting the workpiece zero point
Further information
"Axes and Spindles" Function Manual; Manual traversing
● Continue the interrupted NC program
– START command from another channel
Further information
"NC Programming" Programming Manual
– NC/PLC interface:
DB21, ... DBX7.1 = 1 (NC start)
See also
Block search Type 5 (SERUPRO) (Page 135)
2.5.5 Channel reset
Function
A channel reset causes an NC program being processed in automatic mode or program block
being processed in the MDI mode to be terminated.
The NC program or the program block cannot be continued at the point of interruption. After
completion of the channel reset, all axes and spindles of the channel are in the "exact stop"
status (exception: follow-up mode).
Basic functions
Sequence
The NC reset causes the following actions to be performed in the channel:
● The program preparation is stopped immediately.
● Axes and spindles are braked via their parameterized braking ramps to standstill.
● Any auxiliary functions of the current block not yet output are no longer output to the PLC.
● The block indicator is reset to the start of the selected NC program.
● All reset alarms of the channel are cleared from the display.
Rules
● A channel reset is performed in any channel state.
● A channel reset is not aborted by any other command.
Request: Channel reset

A channel reset is requested via the following NC/PLC interface signals:
● DB21, … DBX7.7 = 1 (reset)
Request: Mode group reset

A mode group reset initiates a channel reset in all channels of a mode group.
A mode group reset is requested via the following NC/PLC interface signals:
● DB11, ... DBX0.7 = 1 (mode group reset)
Feedback: Channel reset completed

● DB21, … DBX35.7 == 1 (channel state reset)
Feedback: Mode group reset completed

● DB11, ... DBX6.5 == 1 (mode group reset)
Further information
2.5.6 Program status

The status of the selected NC program is displayed in the interface for each channel.
All program states can occur in the AUTOMATIC and MDI modes. In all other modes or
machine functions, the program status is aborted or interrupted.
Basic functions

The following program states are displayed at the NC/PLC interface (DB21, ... ):
● DB21, ... DBX35.4 ("aborted")
● DB21, ... DBX35.3 ("interrupted")
● DB21, ... DBX35.2 ("stopped")
● DB21, ... DBX35.1 ("waiting")
● DB21, ... DBX35.0 ("running")
A detailed description of the interface signals can be found in the NC Variables and Interface
Signals List Manual.
Status changes
The program status is influenced by commands, NC/PLC interface and alarms. Starting at the
"running" program status, the table shows the following status based on the associated event.
Initial status of the program: "running"

Event Following status of the program
Abor‐ Inter‐ Stop‐ Wait‐ Run‐
ted rupted ped ing ning
DB21, ... DBX7.7 (reset) x
DB21, ... DBX7.3 (NC stop) x
DB21, ... DBX7.2 (NC stop at the block limit) x
DB21, ... DBX7.4 (NC stop, axes and spindles) x
DB21, ... DBX6.1 (read-in disable) x
DB21, ... DBX6.0 (feedrate stop) x
DB21, ... DBX12.3 / 16.3 / 20.3 (feedrate stop, geo axis x
1 / 2 / 3)
DB21, ... DBB4; feedrate override = 0% x
DB31, ... DBX4.3 (feed/spindle stop) x
DB21, ... DBX194.2 / DBX197.6 (M02 / M30 in the block) x
DB21, ... DBX194.0 / DBX194.1 (M00 / M01 in the block) x
DB21, ... DBX0.4 (single block) x
DB21, ... DBX6.2 (delete distance-to-go) x
Auxiliary functions output to PLC but not yet acknowl‐ x
edged
WAIT command in the program x
Alarm with "NOREADY" system response x
2.5.7 Channel status

The channel status for each channel is displayed in all operating modes at the NC/PLC
interface (DB21, ...).
Basic functions

The channel states are indicated by the following signals in the NC/PLC interface:
● DB21, ... DBX35.7 ("reset")
● DB21, ... DBX35.6 ("interrupted")
● DB21, ... DBX35.5 ("active")
A detailed description of the interface signals can be found in the NC Variables and Interface
Signals List Manual.
Status changes
The channel status is influenced by commands and NC/PLC interface signals. Starting at the
"active" channel status, the table shows the following status based on the associated event.
Initial status of the channel: "active"

Event Following status of the channel
"Reset" "Interrupted" "Active"
DB21, ... DBX7.7 (reset) x
DB21, ... DBX7.3 (NC stop) x
DB21, ... DBX7.2 (NC stop at the block limit) x
DB21, ... DBX7.4 (NC stop, axes and spindles) x
DB21, ... DBX6.1 (read-in disable) x
DB21, ... DBX6.0 (feedrate stop) x
DB21, ... DBX12/16/20.3 (feedrate stop, geometry axis x
1/2/3)
DB21, ... DBB4; feedrate override = 0% x
DB31, ... DBX4.3 (feed/spindle stop) x
DB21, ... DBX194.2/DBX197.6 (M02/M30 in the block) x
DB21, ... DBX194.0/DBX194.1 (M00/M01 in the block) x
DB21, ... DBX0.4 (single block) x
DB21, ... DBX6.2 (delete distance-to-go) x
Auxiliary functions output to PLC but not yet acknowl‐ x
edged
WAIT command in the program x
The "active" channel status is achieved when an NC program or NC program block is being
executed or when axes are traversed in JOG mode.
2.5.8 Responses to operator and program actions
Status transitions
The following table shows the channel and program states that result after certain operator and
program actions.
Basic functions
The left-hand part of the table lists the various states of the channel and of the program selected
in the channel, and the active operating mode.
The right-hand part of the table lists the operating/program actions and the following status.
Status Channel sta‐ Program status Operating Operating or program action => following status
tus mode
R U A R U S W A A M J
1 x x x RESET ⇒ 4
2 x x x RESET ⇒ 5
3 x x x RESET ⇒ 6
4 x x x NC start ⇒ 13; mode change ⇒ 5 or 6
6 x x x Direction key ⇒ 15; mode change ⇒ 4 or 5
7 x x x NC start ⇒ 14
8 x x x NC start ⇒ 15
11 x x x Direction key ⇒ 17; mode change ⇒ 9 or 10
13 x x x NC stop ⇒ 12
14 x x x NC stop ⇒ 7; for block end ⇒ 5
15 x x x NC stop ⇒ 8; for JOG end ⇒ 6
16 x x x NC stop ⇒ 10; for block end ⇒ 10
17 x x x NC stop ⇒ 11; for JOG end ⇒ 11
18 x x x Reset ⇒ 4; wait for other channel ⇒ 18
Channel status Program status Modes

R → aborted R → aborted A → automatic
U → interrupted U → interrupted M → MDI
A → running S → stopped J → JOG
W → waiting
A → running
2.5.9 Example of a timing diagram for a program run
Program code
N10 G01 G90 X100 M3 S1000 F1000 M170
N20 M0
Basic functions
1&VWDUWIURP3/&+0,XVHUODQJXDJH
1&VWRSIURP3/&+0,XVHUODQJXDJH
'%'%;1&VWDUWGLVDEOH
'%'%;UHDGLQGLVDEOH
3/&!1&
'%'%;FRQWUROOHUHQDEOH;D[LV
'%'%;IHHGUDWHVWRS
'%'%;FRQWUROOHUHQDEOHVSLQGOH
'%'%;VSLQGOHVWRS
'%'%;SURJUDPVWDWHUXQQLQJ
'%'%;SURJUDPVWDWHLQWHUUXSWHG
'%'%;SURJUDPVWDWHVWRSSHG
1&!3/&
'%'%;SURJUDPVWDWHFDQFHOHG
'%'%%WUDYHOFRPPDQG;D[LV
'%'%;H[DFWVWRSILQH
'%'%;VSLQGOHVWDWLRQDU\
'%'%;VSLQGOHLQVHWSRLQWUDQJH
6SLQGOH $[LV;WUDYHUVHV
SRZHUXS
1 1
Figure 2-1 Signal characteristics during the program
2.5.10 Program jumps
2.5.10.1 Return jump to the start of the program (GOTOS)
Function
With the function "Jump back to start of the program" the control jumps back from a part
program to the beginning of the program. The program is then processed again.
As compared to the function "Program jumps to jump marks", with which a repeated processing
of the program can also be implemented, the function "Jump back to the start of the program"
offers the following advantages:
● The programming of a jump mark at the start of the program is not necessary.
● The program restart can be controlled through the NC/PLC interface signal:
DB21, ... DBX384.0 (control program branching)
Basic functions
● The timer for the program runtime can be reset to "0" at the restart of the program.
● The timer for workpiece counting can be incremented by "1" at program restart.
Application example
The function is used, if the processing of subsequent workpieces is to be done through an
automatic program restart, e.g. in case of turning machine with bar loader/changer.

The jump back takes place only when the following NC/PLC interface signal is set:
DB21, ... DBX384.0 (control program branching) = 1
Parameterization
Program runtime
The runtime of the selected NC program is stored in the system variable $AC_CYCLE_TIME.
When starting a new program, the system variable is automatically reset to "0" (see Section
" Program runtime (Page 245) ")
Via the following machine data it can be set that the system variable $AC_CYCLE_TIME is
reset to "0" even in case of a program restart through the function "jump back to start of
program":
MD27860 $MC_PROCESSTIMER_MODE.Bit 8 = <value> (activate the program runtime
measurement)
Bit Value Meaning

8 0 $AC_CYCLE_TIME is not reset to "0" by the function "jump back to start of pro‐
gram".
1 $AC_CYCLE_TIME is reset to "0" by the function "jump back to start of program".
Note
In order that the setting of bit 8 can become effective, the measurement of the current program
runtime must be active (MD27860 bit 1 = 1).
Workpiece count
After the part program end (M02 / M30) has been attained, the activated workpiece counters
($AC_TOTAL_PARTS / $AC_ACTUAL_PARTS / $AC_SPECIAL_PARTS) are incremented by
"1" (see Section "Workpiece Counter (Page 256)").
Via the following machine data it can be set that the activated workpiece counter is incremented
even in case of a program restart through the function "jump back to start of program":
MD27880 $MC_PART_COUNTER.Bit <n> = <value> (activating the workpiece counter)
Bit Value Meaning: In case of a program restart through the function "jump back to start of
program", the workpiece counter:
7 0 $AC_TOTAL_PARTS is not incremented.
1 $AC_TOTAL_PARTS is incremented.
Basic functions
Bit Value Meaning: In case of a program restart through the function "jump back to start of
program", the workpiece counter:
11 0 $AC_ACT_PARTS is not incremented.
1 $AC_ACT_PARTS is incremented.
15 0 $AC_SPECIAL_PARTS is not incremented.
1 $AC_SPECIAL_PARTS is incremented.
Programming
Syntax
GOTOS
Meaning
GOTOS: Return to the start of the current program

Preprocessing Yes
stop:
Effective: Non-modal
Example:
Programming Comment
N10 ... ; Start of the program
...
IF ...
N100 GOTOS Return to the program start (N10)
ENDIF
...
RET
2.5.11 Program section repetitions
2.5.11.1 Programming
The program section repetition permits the repetition of program sections within an NC
program.
Basic functions
The program lines or program sections to be repeated are identified by jump markers (labels).
Note
Jump markers (labels)
Jump markers are always located at the beginning of a block. If a program number exists, the
jump marker is located immediately after the block number.
The following rules apply when naming jump markers:
● Number of characters:
– Minimum 2
– Maximum 32
● Permissible characters are:
– Letters
– Digits
– Underscores
● The first two characters must be letters or underscores.
● The name of the jump marker is followed by a colon (":").
Syntax
1. REPEATB: Repeat single program line
<jump marker>: ...

...
REPEATB <jump marker> P=<n>
2. REPEAT + jump marker: Repeat program section between jump marker and REPEAT
statement
<jump marker>: ...

...
REPEAT <jump marker> P=<n>
3. REPEAT + jump marker_1 + jump marker_2: Repeat section between two jump markers
<start jump marker>: ...

...
<end jump marker>: ...
...
REPEAT <start jump marker> <end jump marker> P=<n>
Basic functions
Note
It is not possible to nest the REPEAT statement with the two jump markers in parentheses. If
the <start jump marker> appears before the REPEAT statement and the <end jump
marker> is not reached before the REPEAT statement, the section between the <start
jump marker> and the REPEAT statement will be repeated.
4. REPEAT + jump marker + ENDLABEL: Repeat section between jump marker and
ENDLABEL:
<jump marker>: ...

...
ENDLABEL: ...
...
REPEAT <jump marker> P=<n>
Note
It is not possible to nest the REPEAT statement with the <jump marker> and the ENDLABEL in
parentheses. If the <jump marker> appears before the REPEAT statement and
the ENDLABEL is not reached before the REPEAT statement, the section between the <jump
marker> and the REPEAT statement will be repeated.
Meaning
REPEATB: Command for repeating a program line

REPEAT: Command for repeating a program section
<jump marker>: The <jump marker> identifies:
● REPEATB: The program line to be repeated
● REPEAT: The start of the program section to be repeated
The program line identified by the <jump marker> can appear before or after
the REPEAT/REPEATB statement. The search initially commences towards the
start of the program. If the jump marker is not found in this direction, the search
continues in the direction towards the end of the program.
Exception:
If the program section between the jump marker and the REPEAT statement
needs to be repeated (see 2. under Syntax), the program line identified by
the <jump marker> has to appear before the REPEAT statement, since in
this case the search runs only towards the beginning of the program.
If the line with the <jump marker> contains further statements, they are
executed again on each repetition.
ENDLABEL: Keyword that marks the end of a program section to be repeated.
If the line with the ENDLABEL contains further statements, they are executed
again on each repetition.
ENDLABEL can be used more than once in the program.
Basic functions
P: Address for specifying the number of repetitions

Note:
If no number is specified for P=<n>, the program section is repeated just once.
<n>: Number of repetitions
Type: INT
The program section to be repeated is repeated <n> times. After the last
repetition, the program is resumed at the program line following the REPEAT/
REPEATB command.
Examples
Example 1: Repeat individual program line

N10 POSITION1: X10 Y20
N20 POSITION2: CYCLE(0,,9,8) ;Position cycle
N30 ...
N40 REPEATB POSITION1 P=5 ; Execute block N10 five times.
N50 REPEATB POSITION2 ; Execute block N20 once.
N60 ...
N70 M30
Example 2: Repeat program section between jump marker and REPEAT statement:

N5 R10=15
N10 Begin: R10=R10+1 ; Start of the program section
N20 Z=10-R10
N30 G1 X=R10 F200
N40 Y=R10
N50 X=-R10
N60 Y=-R10
N70 Z=10+R10
N80 REPEAT BEGIN P=4 ; Execute section from N10 to N70 four times.
N90 Z10
N100 M30
Example 3: Repeat section between two jump markers

N5 R10=15
N10 Begin: R10=R10+1 ; Start of the program section
N20 Z=10-R10
N30 G1 X=R10 F200
N40 Y=R10
N50 X=-R10
N60 Y=-R10
Basic functions

N70 END: Z=10 ; End of the program section
N80 Z10
N90 CYCLE(10,20,30)
N100 REPEAT BEGIN END P=3 ; Execute section from N10 to N70 three times.
N110 Z10
N120 M30
Example 4: Repeat section between jump marker and ENDLABEL

N10 G1 F300 Z-10
N20 BEGIN1: ; Start program section 1
N30 X10
N40 Y10
N50 BEGIN2: ; Start program section 2
N60 X20
N70 Y30
N80 ENDLABEL: Z10
N90 X0 Y0 Z0
N100 Z-10
N110 BEGIN3: X20 ; Start program section 3
N120 Y30
N130 REPEAT BEGIN3 P=3 ; Execute section from N110 to N120 three times.
N140 REPEAT BEGIN2 P=2 ; Execute section from N50 to N80 twice.
N150 M100
N160 REPEAT BEGIN1 P=2 ; Execute section from N20 to N80 twice.
N170 Z10
N180 X0 Y0
N190 M30
Example 5: Milling, drilling position with different technologies

N10 CENTER DRILL() ; Load centering drill.
N20 POS_1: ; Start program section 1; drilling position 1
N30 X1 Y1
N40 X2
N50 Y2
N60 X3 Y3
N70 ENDLABEL:
N80 POS_2: ; Start program section 2; drilling position 2
N90 X10 Y5
N100 X9 Y-5
N110 X3 Y3
N120 ENDLABEL: ; End program sections 1 and 2
Basic functions

N130 DRILL() ; Drilling cycle
N140 THREAD(6) ; Threading cycle
N150 REPEAT POS_1 ; Repeat program section once from POS_1 up to ENDLABEL.
N160 DRILL() ; Drilling cycle
N170 THREAD(8) ; Threading cycle
N180 REPEAT POS_2 ; Repeat program section once from POS_2 up to ENDLABEL.
N190 M30
Further information
● Program section repetitions can be nested. Each call uses a subprogram level.
● If M17 or RET is programmed while processing a program section repetition, the program
section repetition is canceled. The program is resumed at the block following the REPEAT
line.
● In the actual program display, the program section repetition is displayed as a separate
subprogram level.
● If the level is canceled during the program section processing, the program resumes at the
point after the program section repetition call.
Example:

N5 R10=15
N10 BEGIN: R10=R10+1 ;Width
N20 Z=10-R10
N30 G1 X=R10 F200
N40 Y=R10 ; Interrupt level
N50 X=-R10
N60 Y=-R10
N70 END: Z10
N80 Z10
N90 CYCLE(10,20,30)
N100 REPEAT BEGIN END P=3
N120 Z10 ; Resume program execution.
N130 M30
● Check structures and program section repetitions can be used in combination. There should
be no overlap between the two, however. A program section repetition should appear within
a check structure branch or a check structure should appear within a program section
repetition.
● If jumps and program section repetitions are mixed, the blocks are executed purely
sequentially. For example, if a jump is performed from a program section repetition,
processing continues until the programmed end of the program section is found.
Example:
Basic functions
Program code
N10 G1 F300 Z-10
N20 BEGIN1:
N30 X=10
N40 Y=10
N50 GOTOF BEGIN2
N60 ENDLABEL:
N70 BEGIN2:
N80 X20
N90 Y30
N100 ENDLABEL: Z10
N110 X0 Y0 Z0
N120 Z-10
N130 REPEAT BEGIN1 P=2
N140 Z10
N150 X0 Y0
N160 M30
Note
The REPEAT statement should appear after the traversing block.
2.5.12 Event-driven program call (PROG_EVENT)
2.5.12.1 Function
Function
The "Event-driven program call" (PROG_EVENT) function starts, for the occurrence of a
selected event in the NC, a user-specific NC program (PROG_EVENT-program).
Application examples
Initial setting for functions or initialization of system or user variables.
Events
The triggering events are selected with the machine data MD20108
$MC_PROG_EVENT_MASK (see Section "Parameterization (Page 70)").
PROG_EVENT program
The name of the PROG_EVENT program is set with the machine data
MD11620 $MN_PROG_EVENT_NAME up (see Section "Parameterization (Page 70)").
The PROG_EVENT program is executed in the channel in which the event occurred.
Basic functions
The PROG_EVENT program is executed with the lowest priority and so can be interrupted by
a user ASUP.
Processing sequences
Processing sequence when activated by an event: Program start

Initial state:
Channel: Reset status

Mode: AUTOMATIC (optional: Overstore (active)
MDI
TEACH IN
1. A program starts in the channel
2. Initialization sequence with evaluation of:
– MD20112 $MC_START_MODE_MASK
3. Implicit call of the PROG_EVENT program as a subprogram
4. Processing of the data part of the main program
5. Processing of the program part of the main program
Processing sequence when activated by an event: Program end

Initial state
Channel: Active
Mode: AUTOMATIC (optional: Overstore (active)
MDI
TEACH IN
1. In the channel, the end of program block is exchanged in the executed program.
2. End of program is executed, evaluation of the following machine data:
– MD20110 $MC_RESET_MODE_MASK
– MD20150 $MC_GCODE_RESET_VALUES
– MD20152 $MC_GCODE_RESET_MODE
3. Implicit call of the PROG_EVENT program as ASUP
4. A reset is executed in the channel, evaluation of the following machine data:
Basic functions
Sequence when activated by an event: Channel reset

Initial state:
Channel: Any
Mode: Any
1. Control activates reset-sequence with evaluation of machine data:
Sequence when activated by an event: Power-up of the NC

1. Control activates after power-up reset-sequence with evaluation of machine data:
NC/PLC interface signals Change of "program status" and "channel status"

The following diagrams show the changes of the various NC/PLC interface signals for "program
status" and "channel status" during the event-driven program call sequence.
Basic functions
Signal sequence when activated by program start and program end

'%'%;
3URJUDPVWDWXVUXQQLQJ
'%'%;
3URJUDPVWDWXVVWRSSHG
'%'%;
3URJUDPVWDWXVFDQFHOHG
'%'%;
&KDQQHOVWDWXVDFWLYH
'%'%;
&KDQQHOVWDWXVLQWHUUXSWHG
'%'%;
&KDQQHOVWDWXVUHVHW
Signal sequence when activated by a channel reset

'%'%;
3URJUDPVWDWXVUXQQLQJ
'%'%;
3URJUDPVWDWXVVWRSSHG
'%'%;
3URJUDPVWDWXVFDQFHOHG
'%'%;
&KDQQHOVWDWXVDFWLYH
'%'%;
'%'%;
&KDQQHOVWDWXVUHVHW
NC/PLC interface signals: DB21, ... DBX35.4 (program status aborted) and DB21, ... DBX35.7 (channel
status reset)
● The interface signals are set only when the PROG_EVENT program has completed again.
● The interface signals are not set between:
– Program end and PROG_EVENT program start
– Channel reset and PROG_EVENT program start
Basic functions
NC/PLC interface signals DB21, ... DBX376.0 ... 4 (triggering events)

The initiating event is displayed using interface signals DB21, ... DBX376.0 ... 4:
Bit Value Event

0 1 Program start from channel state "Reset"
1 1 End of program
2 1 Channel reset
3 1 Powering-up of the NC
4 1 1. Program start after block search (see "Automatic start of an ASUP after block
search (Page 128)")
If the PROG_EVENT program has completed or been canceled with a channel reset, the
interface signals are cleared again.
The interface signals are available for at least the duration of a PLC cycle.
2.5.12.2 Parameterization
Event selection
The events that start the PROG_EVENT program are set channel-specific using the machine
data:
MD20108 $MC_PROG_EVENT_MASK.Bit <n> = 1
Bit <value> Meaning: Event

0 1 Part program start
1 1 Part program end
2 1 Channel reset
3 1 Run-up
Note
MD20108 $MC_PROG_EVENT_MASK is not evaluated in the simulation.
PROG_EVENT program
The PROG_EVENT program (default: _N_PROG_EVENT_SPF) must be loaded and enabled.
Default setting
As default setting, when an event occurs, user program _N_CMA_DIR/
_N_PROG_EVENT_SPF is executed.
The PROG_EVENT program must be loaded and enabled.
User-specific setting
If, for an event, a different PROG_EVENT program than the default setting is to be executed,
the NC program name must be entered into the following machine data:
Basic functions
MD11620 $MN_PROG_EVENT_NAME = <program name>
Search path
The PROG_EVENT program must be located in one of the following cycle directories. The
following search path is passed through when the parameterized event occurs:
1. /_N_CUS_DIR/ (user cycles)
2. /_N_CMA_DIR/ (manufacturer cycles)
3. /_N_CST_DIR/ (standard cycles)
The first program found with the name specified in MD11620 $MN_PROG_EVENT_NAME is
executed.
Note
● The specified program name is checked syntactically as in case of a subprogram name, i.e.
the first two characters must be letters or underscores (no digits). Prefix (_N_) and suffix
(_SPF) of the program names are added automatically, if not specified.
● The same protection mechanisms that can be activated for cycles (protection levels for
writing, reading, etc.) are activated.
Behavior when starting a user ASUB

The behavior of the function "event-driven program call" upon start of a user ASUB from the
reset channel status can be set channel-specific with the machine data:
MD20109 $MC_PROG_EVENT_MASK_PROPERTIES.Bit 0 = <value>
Bit Value Meaning

0 0 The PROG_EVENT program is started when one of the events parameterized with
MD20108 occurs.
1 The PROG_EVENT program is not started when one of the events parameterized
with MD20108 occurs.
Behavior when the single-block processing is set

The behavior of the "event-driven program call" function for set single-block processing can be
set channel-specific with the following machine data:
MD20106 $MC_PROG_EVENT_IGN_SINGLEBLOCK.Bit <n> = <value>
Bit Value Meaning: In the PROG_EVENT program, the single-block processing for event:
0 0 Part program start: acts
1 Part program start: is suppressed
1 0 Part program end: acts
1 Part program end: is suppressed
2 0 Channel reset: acts
1 Channel reset: is suppressed
Basic functions
Bit Value Meaning: In the PROG_EVENT program, the single-block processing for event:
3 0 Run-up: acts
1 Run-up: is suppressed
If the single-block processing is suppressed, the PROG_EVENT program is processed without

interruption.
Note
● MD20106 $MC_PROG_EVENT_IGN_SINGLEBLOCK affects all single-block processing
types.
● The single-block processing in the PROG_EVENT program can be disabled with the
following setting:
MD10702 $MN_IGNORE_SINGLEBLOCK_MASK, bit 0 = 1 (prevent single-block stop)
The settings in MD20106 $MC_PROG_EVENT_IGN_SINGLEBLOCK then do not act.
Behavior when the read-in disable is set

The behavior of the "event-driven program call" function in case of set read-in disable
(DB21, ... DBX6.1 = 1) can be set channel-specific for each initiating event with the following
machine data:
MD20107 $MC_PROG_EVENT_IGN_INHIBIT.Bit <n> = <value>
Bit Value Meaning: In the PROG_EVENT program, the read-in disable for event:
0 0 Part program start: acts
If the PROG_EVENT program is terminated with the RET command, no executable
block is created
1 Part program start: is suppressed
If the PROG_EVENT program is terminated with the RET command, an executable
block analog to M17 is created.
1 0 Part program end: acts
1 Part program end: is suppressed
2 0 Channel reset: acts
1 Channel reset: is suppressed
3 0 Run-up: acts
1 Run-up: is suppressed
Suppress updating of the display of the program and channel statuses

To prevent flickering when displaying the program and channel statuses on the HMI user
interface, the display refresh can be suppressed for the execution of the normally very brief
PROG_EVENT program. The program and the channel status before activation of the
PROG_EVENT program then remain visible in the display.
Basic functions
MD20192 $MC_PROG_EVENT_IGN_PROG_STATE.Bit <n> = <value>
Bit Value Meaning: While processing the PROG_EVENT program, the refresh of the display of
the program and channel statuses for event:
1 0 Part program end: Not suppressed
1 Part program end: Suppressed
2 0 Channel reset: Not suppressed
1 Channel reset: Suppressed
3 0 Run-up: Not suppressed
1 Run-up: Suppressed
Note
The system variables $AC_STAT and $AC_PROG are not affected by this function, i.e. in the
running event-driven user program, $AC_STAT is set to "active" and $AC_PROG to "running".
NC/PLC interface signals DB21, ... DBX35.0-7 ("Program status ..." and "Channel status ...")
also remain unaffected.
Response for DB21, ... DBX7.2 / 3 / 4 (NC stop ...)

The response of the "event-driven program call" function for "NC stop", "NC stop at block limit"
and "NC stop axes plus spindle" can be set channel-specific for the part program end, channel
reset and ramp up events with the following machine data:
MD20193 $MC_PROG_EVENT_IGN_STOP.Bit <n> = <value>
Bit Value Meaning: The PROG_EVENT-program for NC stop and event

1 0 Part program end: is stopped/prevented
1 Part program end: is processed completely
2 0 Channel reset: is stopped/prevented
1 Channel reset: is processed completely
3 0 Run-up: is stopped/prevented
1 Run-up: is processed completely
Application example
An edge change of the interface signal DB21, ... DBX7.3 (NC stop) initiated by the operator by
pressing the NC Stop key during a channel reset or power-up is ignored during the execution
of the PROG_EVENT program and so an undesired stop behavior at the machine is prevented.
Note
Programming DELAYFSTON/DELAYFSTOF in the PROG_EVENT program cannot replace the
behavior set with MD20193. NC stop before executing the DELAYFSTON command can still
cause an interruption.
Basic functions
PROG_EVENT program
End of program
The following must be kept in mind, if the user program is to be activated through the part
program start.
● The user program must be ended with M17 or RET.
● A return jump with the REPOS command is not permissible.
Block display
The display can be suppressed in the current block display using the DISPLOF attribute in the
PROC statement.
Communication to the PLC user program

User M functions programmed in the PROG_EVENT program can inform the PLC user
program, e.g. about the processing status of the PROG_EVENT program.
System variable
Query for triggering event

The initiating event can be queried in the PROG_EVENT program with the following system
variables:
<value> = $P_PROG_EVENT (event-driven program call active)
Value Meaning: Activation by

1 Part program start
2 Part program end
3 Channel reset
4 Power-up
5 After output of the last action block after Block search (see "Automatic Start of an ASUP after
block search (Page 128)")
Query of the current channel

The channel in which the PROG_EVENT program is processed can be determined with the
following system variables:
<value> = $P_CHANNO (query the current channel number)
Note
The PROG_EVENT program is processed in the channel in which the initiating event occurred.
Power-up is an event that takes place concurrently in all channels.
Basic functions
2.5.12.4 Boundary conditions
Emergency stop / alarm

If an emergency stop or a mode group / NC-specific alarm is present for a channel reset or after
power-up, the PROG_EVENT program is processed only after the emergency stop or the error
has been acknowledged in all channels.
Note
The "power-up" event occurs in all channels concurrently.
2.5.12.5 Examples
Example 1: Call the PROG_EVENT program for all events
Parameterization
MD20108 $MC_PROG_EVENT_MASK = 'H0F' Call of _N_PROG_EVENT_SPF for:

● Part program end
● Channel reset
● Power-up
Programming

PROC PROG_EVENT DISPLOF
; Processing for part program start
IF ($P_PROG_EVENT==1)
MY_GUD_VAR=0 ; Initialize GUD variable
RET
ENDIF
; Processing for part program end and channel reset
IF ($P_PROG_EVENT==2) OR
($P_PROG_EVENT==3)
DRFOF ; Deactivate DRF offsets
IF $MC_CHAN_NAME=="CHAN1"
CANCEL(2) ; Clear modal synchronized action 2
ENDIF
RET
ENDIF
; Sequence for power-up
IF ($P_PROG_EVENT==4)
IF $MC_CHAN_NAME=="CHAN1"
Basic functions

IDS=1 EVERY $A_INA[1]>5.0 DO
$A_OUT[1]=1
ENDIF
RET
ENDIF
RET
Example 2: ; Call the PROG_EVENT program for channel reset
Parameterization
MD20108 $MC_PROG_EVENT_MASK = 'H04' Call of _N_PROG_EVENT_SPF for:

● Operator panel reset
Programming

PROC PROG_EVENT DISPLOF
N10 DRFOF ; Deactivate DRF offsets
N20 M17
Example 3: Initialization of the function
Parameterization
Machine data assignment, extract from the commissioning file (_N_INITIAL_INI)

...
CHANDATA(3) ; Initialization for channel 3
$MC_PROG_EVENT_IGN_INHIBIT='H01F'
$MC_PROG_EVENT_MASK='H04' ; Event: Channel reset
...
Meaning
The PROG_EVENT program _N_CMA_DIR/_N_PROG_EVENT_SPF is started for channel
reset in the 3rd channel and processed until program end, irrespective of whether or not the
read-in disable is activated or deactivated.
Basic functions
2.5.13 Influencing the stop events by stop delay areas
2.5.13.1 Function
Stop delay area

The response to a stop event can be influenced by the conditioned interruptible area in the NC
program. Such a program area is called a stop delay area.
Within the stop delay areas there should be no stop and the feedrate should not be changed.
Stops do not take effect until the program section has been completed.
This has the following advantages:
● A program section is processed without a drop in velocity.
● If the user aborts the program after a stop with reset, the aborted program block is after the
protected section. This program block is a suitable search target for a subsequent block
search.
● The following main run axes are not stopped as long as a stop delay area is in progress:
– Command axes
– Positioning axes that travel with POSA
Application
Example: Machining a thread.
Definition
The definition of a stop delay area is made in the part program with the predefined
DELAYFSTON and DELAYFSTOF procedures (see "Programming (Page 80)").
Stop events
Overview of the events that cause a stop:
Event Reaction
DB21, ... DBX7.7 (reset) or DB11 DBX20.7 (mode group reset) Immediate
NC program: M30 Alarm 16954
User interrupt to start an ASUP: Delayed
FC 9 or DB10 DBB1 (setting the digital NC inputs for the PLC)
DB21, ... DBX6.2 / DB31, ... DBX2.2 (clear distance-to-go) channel/axis-spe‐ Immediate
cific
DB21, ... DBX6.3 (clear the number of subprogram repetitions) Delayed
DB21, ... DBX6.4 (program level abort) Delayed
Basic functions
Event Reaction
Stop because of single block Delayed
● In the stop delay area:
The NC stops at the end of the 1st block outside the stop delay area.
● Single block is active before the stop delay area:
NC stops at each block limit, i.e. also in the stop delay area:
DB21, ... DBX7.2 (NC stop at the block limit)
This deselects the stop delay area!
DB11 DBX21.7 (activate single-block type A) Delayed
DB11 DBX21.6 (activate single-block type B) Delayed
DB21, ... DBX7.4 (NC stop) and DB11 DBX0.6 (mode group stop, axes plus Immediate
spindles)
DB21, ... DBX7.3 (NC stop at block limit) and DB11 DBX0.5 (mode group Delayed
stop)
NC program: Stop because of empty overstore buffer Alarm 16954
NC program: Programmed or implicit STOPRE Alarm 16954
NC program: M0 or M1 Alarm 16954
DB21, ... DBX7.2 (NC stop at the block limit) Delayed
Subprogram end should always deselect the stop delay area. System error
NC program: WAITM Alarm 16954
NC program: WAITE Alarm 16954
NC program: INIT with parameter "S" Alarm 16954
NC program: MMC (STRING, CHAR) Alarm 16954
DB21, ... DBB26 (activate/deactivate skip block) Delayed
DB21, ... DBB26 (deactivate skip block) Delayed
DB21, ... DBX0.6 (activate DryRun) Delayed
DB21, ... DBX0.6 (deactivate DryRun) Delayed
DB21, ... DBX6.1 (read-in disable) Delayed
Alarm: Alarm configuration STOPATENDBYALARM Immediate
Alarm: Alarm configuration STOPBYALARM Immediate
Internal: Stop after alarm for empty IPO buffer Immediate
Internal: Stop after alarm for empty IPO buffer Immediate
NC program: Alarm 16954 for LFON Alarm 16954
NC program: WAITMC Alarm 16954
NC program: NEWCONF Alarm 16954
NC program: NEWCONF Alarm 16954
OPI: PI "_N_SETUDT" Delayed
Extended stop and retract Delayed
DB31, ... DBX3.0 (accept external work offset) Delayed
OPI: PI "_N_FINDST" STOPRUN Alarm 16955
Alarms with NOREADY response Immediate
DB21, ... DBX7.2 == 1 (NC stop at block limit) Delayed
DB21, ... DBX7.3 == 1 (NC stop)
DB21, ... DBX7.4 == 1 (NC stop, axes plus spindles)
DB21, ... DBX6.1 == 1 (read-in disable) Delayed
Basic functions
Event Reaction
DB21, ... DBX2.0 == 1 (single block) Delayed
Reaction
● Immediate
Stops immediately, even in the stop delay area. Designated as a "hard stop event".
● Delayed
Does not stop (even short-term) until after the stop delay area. Is known as a "soft stop event".
● Alarm 16954
Program is aborted because illegal program commands have been used in the stop delay area.
● Alarm 16955
Program is continued, an illegal action occurred in the stop delay area.
● Alarm 16957
The program area (stop delay area) enclosed by DELAYFSTON and DELAYFSTOF could not be
activated. As a result, every stop will take effect immediately and is not subject to a delay! This will
always occur when the deceleration begins before the stop delay area but ends within the stop delay
area. Likewise, if the stop delay area is entered with an override of 0, the stop delay area also cannot
be activated. (Example: A G4 before the stop delay area allows the user to reduce the override to 0.
The next block in the stop delay area then begins with override 0 and the described alarm situation
occurs.)
Note
MD11411 $MN_ENABLE_ALARM_MASK (activation of warnings) Bit 7 activates this alarm.
Note
Some NC events are stopped for only a short time, in order to perform a switching operation,
and restart immediately. This includes, e.g. an interrupt that stops the NC program briefly in
order to start the associated ASUP. These events are also allowed in the stop delay area,
however they are pushed back to its end and are thus considered "soft stop events".
Note
If a "hard" stop event coincides with the "stop delay area", the entire "stop delay area" is
deselected! Thus, if any other stop occurs in this program section, it will be stopped
immediately. A new program setting (new DELAYFSTON) must be made in order to start a new
stop delay area.
Machine data
Stop response for G331/G332

For tapping without compensating chuck (G331, G332), the stop response can be set as
follows:
Basic functions
MD11550 $MN_STOP_MODE_MASK
Bit Value Meaning

0 0 (default) Results in an implicit stop delay range if G331/G332 is active - and path
motion or a dwell time (G4) was also programmed.
1 A stop while G331/G332 is active is possible in the following situations:
● The continuous path mode is interrupted (G64).
● A dwell time (G4) is programmed between the G33x blocks.
NC commands DELAYFSTON and DELAYFSTOF must be used to define a
stop delay range.
Defining a stop delay range (DELAYFSTON, DELAYFSTOF)

The predefined DELAYFSTON and DELAYFSTOF procedures are used to define a
conditionally interruptible range in the part program (stop delay range).
Note
DELAYFSTON and DELAYFSTOF are not permitted in synchronized actions!
Syntax
DELAYFSTON
...
DELAYFSTOF
Meaning
DELAYFSTON: Defining the start of a stop delay range

Alone in the block: Yes
DELAYFSTOF: Define the end of the stop delay area
Programming example
The following program block is repeated in a loop:
Program code
...
N99 MY_LOOP:
N100 G0 Z200
N200 G0 X0 Z200
Basic functions
Program code
N300 DELAYFSTON
N400 G33 Z5 K2 M3 S1000
N500 G33 Z0 X5 K3
N600 G0 X100
N700 DELAYFSTOF
N800 GOTOB MY_LOOP
...
In the following diagram it can be seen that the user pressed "Stop" in the stop delay range, and
the NC started braking outside the stop delay range, i.e. in block N100. That causes the NC to
stop at the beginning of N100.
1&VWRSSW 1*=
1*; 1*;=
1*=;.
1*=.
;
6WRSEXWWRQ
6WRSEXWWRQGXULQJD*
= PDFKLQLQJ
Additional information
End of subprogram
DELAYFSTOF is activated implicitly at the end of the subprogram in which DELAYFSTON is
called.
Nesting
If subprogram 1 calls subprogram 2 in a stop delay area, the whole of subprogram 2 is a stop
delay area. In particular, DELAYFSTOF in subprogram 2 has no effect.
Example:

N10010 DELAYFSTON ; Blocks with N10xxx program level 1.
N10020 R1 = R1 + 1
N10030 G4 F1 ; Stop delay area starts.
...
N10040 subprogram2
...
... ; Interpretation of subprogram 2.
Basic functions

N20010 DELAYFSTON ; Ineffective, repeated start, 2nd level.
...
N20020 DELAYFSTOF ; Ineffective, end at another level.
N20030 RET
N10050 DELAYFSTOF ; Stop delay end of range at the same level.
...
N10060 R2 = R2 + 2
N10070 G4 F1 ; Stop delay area ends. From now, stops act immediately.
System variables
The following system variables can be queried to determine whether part program processing
is currently in a stop delay area:
● in the part program with $P_DELAYFST
● in synchronized actions with $AC_DELAYFST
Value Meaning
0 Delay stop range not active
1 Delay stop area active
2.5.13.4 Supplementary conditions
Overlap
If two stop delay areas overlap, one from DELAYFSTON/DELAYFSTOF and the other from
MD11550 $MN_STOP_MODE_MASK, the largest possible stop delay area will be generated.
Dwell time (G4)

G4 is permitted in the stop delay area. Other part program commands that cause a stop in the
meantime (e.g. WAITM) are not permitted and trigger the alarm 16954.
Override
If the override is changed before a stop delay area, the override takes effect in the stop delay
area.
If the override is changed in the stop delay area, the change takes effect after the stop delay
area.
Note
Override = 0
If the override is reduced to 0 before a stop delay area, the stop delay area cannot be activated.
Feed disable
DB21, ... DBX6.0 The feed disable has no effect in the stop delay area; the program does not
stop until after the stop delay area.
Basic functions
Single block
If the single block is activated in the stop delay area, the NC stops at the end of the first block
outside the stop delay area.
If the single block is already selected before the stop delay area, the NC stops at each block
limit, i.e. also in the stop delay area! This deselects the stop delay area.
2.5.14 Adapting the size of the interpolation buffer
MD28060
The channel-specific interpolator executes prepared blocks from the interpolation buffer during
the part program run. The maximum number of blocks requiring space in the interpolation buffer
at any given point in time is defined by the memory configuring MD28060
$MM_IPO_BUFFER_SIZE (number of NC blocks in the IPO buffer (DRAM)). For some
applications it may be meaningful not to use the full buffer capacity in order to minimize the
"interval" between preparation and interpolation.
SD42990
The number of blocks in the interpolation buffer can be restricted dynamically to a smaller value
than in MD28060 $MC_MM_IPO_BUFFER_SIZE (number of NC blocks in the IPO buffer
(DRAM)), minimum 2 blocks, with the setting data SD42990
$SC_MAX_BLOCKS_IN_IPOBUFFER (max. number of blocks in the IPO buffer).
Values of setting data SD42990 $SC_MAX_BLOCKS_IN_IPOBUFFER:
Value Effect
<0 No interpolation buffer limit active.
The max. possible IPO buffer as set in MD 28060: MM_IPO_BUFFER_SIZE is
activated.
or 1 The minimum permissible IPO buffer with two blocks is activated.
< MM_IPO_BUFFER_SIZE The IPO buffer is activated with no more than the maximum specified number of
blocks.
>= MM_IPO_BUFFER_SIZE The IPO buffer is activated with the number of blocks specified in MD 28060:
MM_IPO_BUFFER_SIZE.
Basic functions
Note
If SD42990 $SC_MAX_BLOCKS_IN_IPOBUFFER is set in the part program, the interpolation
buffer limitation takes effect immediately if the block with the SD is being preprocessed by the
interpreter.
This means that the limitation of the IPO buffer may take effect a few blocks before the intended
limitation (see also MD 28070 $MC_MM_NUM_BLOCKS_IN_PREP).
To avoid premature activation and to make the limitation of the IPO buffer take effect in
synchronism with the block, a STOPRE (preprocessing stop) must be programmed before the
SD is set in the part program.
Validity
SD42990 $SC_MAX_BLOCK_IN_IPOBUFFER has global, channel-specific validity and can
also be modified in a part program. This modified value is retained at the end of the program.
If this setting data is to be reset again on defined events, a so-called event-driven program must
be created to do this. For example, this setting data could always be set to a predefined value
on RESET.
Application
The IPO buffer limitation can be used whenever the number of blocks between block
preparation and interpolation must be minimized, e.g. when actual positions in the part program
must be read and processed for other purposes.
Example
N10 ...
N20 ...
..........
N100 $SC_MAX_BLOCKS_IN_IPOBUFFER = 5 ; Limitation of the IPO buffer to
five NC blocks
N110 ...
N120 ...
............
N200 $SC_MAX_BLOCKS_IN_IPOBUFFER = -1 ; Cancellation of the IPO buffer
limitation
N210 ...
............
Basic functions
2.5.15 Basic block display (only for ShopMill/ShopTurn)
2.5.15.1 Function
In ShopMill/ShopTurn, a so-called basic block display can be used in addition to the existing
block display to show all blocks that produce an action on the machine.
The end positions actually approached are shown as an absolute position. The position values
refer either to the workpiece coordinate system (WCS) or the settable zero system (SZS).
The number of LookAhead display blocks stored in the display buffer depends on the number
of prepared blocks in the relevant processing state in the preprocessing buffer of the control. If
a preprocessing stop is processed, the number of display blocks is reduced to zero and
increases again after the stop is acknowledged. In the case of REORG events (e.g. mode
change, ASUB start), the display blocks stored for LookAhead are deleted and preprocessed
again afterwards.
Values processed in the basic block display coincide with the:
● Selected tools
● Feedrate and spindle speed
● Position values actually approached
Exceptions:
With active tool radius compensation, deviations can occur.
For modulo axes, the programmed value is displayed in the basic block display. This value
can also lie outside the modulo range.
Activating/deactivating basic block display

The basic block display can be activated/deactivated in the following setting data:
SD42750 $SC_ABSBLOCK_ENABLE (enabling the basic block display)
Configure basic block display

The basic block display can be configured via the following machine data:
NC machine data for basic block display Meaning:

MD28400 $MC_MM_ABSBLOCK Activate basic block display
MD28402 $MC_MM_ABSBLOCK_BUF‐ Size of the display buffer
FER_CONF[2]
Machine data display Position values to be set:
MD9004 $MM_DISPLAY_RESOLUTION for metric dimensional notation
MD9011 $MM_DISPLAY_RESOLUTION_INCH for imperial dimensional notation
MD9010 $MM_SPIND_DISPLAY_RESOLUTION Coordinate system to be set for spindles dis‐
play resolution
MD9424 $MM_MA_COORDINATE_SYSTEM for WCS or SZS actual value display
Basic functions
This display machine data is copied to NC machine data

MD17200 $MN_GMMC_INFO_UNIT[0] (global HMI information) to MD17200
$MN_GMMC_INFO_UNIT[3]. This permits access from the NC to this display machine data.
Activation
The basic block display is activated by MD 28400 $MC_MM_ABSBLOCK (activate block
display with absolute values) by means of Power On. If MD28400 $MC_MM_ABSBLOCK is set
to 1, a channel-specific display buffer (FIFO) is created during power-up.
Size of display buffer (FIFO) = (MD28060 $MC_MM_IPO_BUFFER_SIZE (number of NC
blocks in the IPO buffer) + MD28070 $MC_MM_NUM_BLOCKS_IN_PREP (number of blocks
for the block preparation)) multiplied by 128 bytes. For the standard machine data setting, this
represents a size of 6 KB.
Optimize the size of display buffer:
The memory requirement can be optimized by entering a value between 128 and 512. The
display blocks prepared in the display buffer are transferred to the HMI via a configurable
upload buffer.
The maximum size of the upload buffer is obtained by multiplying (MD28402
$MC_MM_ABSBLOCK_BUFFER_CONF[0] +
MD28402 $MC_MM_ABSBLOCK_BUFFER_CONF[1] + 1) by the block length configured in
MD28400 $MC_MM_ABSBLOCK.
The number of blocks before the current block is configured in
MD28402 $MC_MM_ABSBLOCK_BUFFER_CONF[0] and the number of blocks after the
current block is configured in MD28402 $MC_MM_ABSBLOCK_BUFFER_CONF[1].
If the length of a display block configured in MD28400 $MC_MM_ABSBLOCK is exceeded, this
display block is truncated accordingly. To represent this, the "..." string is appended to the block
end.
For preprocessed cycles
(MD10700 $MN_PREPROCESSING_LEVEL > 1 (program preprocessing level)), the display
block contains only axis positions.
Additional supplementary conditions for the basic block display:
● Modal synchronized action blocks with absolute values are
not taken into account.
● The basic block display is deactivated during block search with or without calculation.
● Polar coordinate programming is not shown in Cartesian system.
Basic functions
Radius/diameter values
Diameter values shown in the basic block display and position display may be needed as a
radius for internal calculation. These values for measurements in radius/diameter according to
G group 29 can be manipulated using the following options:
● G command DIAMCYCOF (extension of channel-specific diameter programming)
This G command deactivates the channel-specific diameter programming during the cycle
execution. In this way, calculations in the cycle can always be made in the radius. The
position display and the basic block display are continued according to the state of the
diameter programming before DIAMCYCOF.
In the basic block display, the last displayed value is retained.
● G command DIACYCOFA[AX] (axis-specific diameter programming)
This G command deactivates the axis-specific diameter programming during the cycle
execution. In this way, calculations in the cycle can always be made in the radius. In the
position display and in the basic block display, this continues according to the state of the
diameter programming before DIACYCOFA[AX] indicator.
In the basic block display, the last displayed value is retained.
● MD27100 $MC_ABSBLOCK_FUNCTION_MASK (parameterize the block display with
absolute values)
Bit0 = 1 Setpoints of the transverse axis are always displayed as diameter values
in the basic block display.
Behavior for active compressor

Two display blocks are generated for active compressor with G group 30 not equal to COM. The
● first contains the G command of the active compressor, the
● second contains the string "..." as character for missing display blocks
Example:
G0 X10 Y10 Z10 ; block still prepared for the basic block display
COMPCAD ; compressor for optimized surface quality (CAD program)
... ; String as sign that the display blocks are missing
To prevent bottlenecks of the NC performance, the basic block display is disabled

automatically. As a sign that the display blocks are missing, a display block with the string "..."
is generated.
All display blocks are always generated in the single block.
Basic functions
2.5.15.3 Structure for a DIN block
Structure of display block for a DIN block

Basic structure of display block for a DIN block
● Block number/label
● G command of the first G group
(only if changed as compared to the last machine function block).
● Axis position
(sequence corresponding to MD20070 $MC_AXCONF_MACHAX_USED (machine axis
number valid in the channel)).
● Further modal G commands
(only if changed as compared to the last machine function block).
● Other addresses as programmed.
The display block for the basic block display is directly derived from the programmed part
program blocks according to the following rules:
● Macros are expanded.
● Skip identifiers and comments are omitted.
● Block number and labels are transferred from the original block, but omitted if DISPLOF is
active.
● The number of decimal places is defined in display machine data MD 9004, MD 9010 and
MD 9011 via the HMI.
HMI display machine data Access in the NC machine data

MD9004 $MM_DISPLAY_RESOLUTION MD17200 $MN_GMMC_INFO_NO_UNIT[0]
MD9011 $MM_DISPLAY_RESOLUTION_INCH MD17200 $MN_GMMC_INFO_NO_UNIT[1]
MD9010 $MM_SPIND_DISPLAY_RESOLU‐ MD17200 $MN_GMMC_INFO_NO_UNIT[2]
TION
MD9424 $MM_MA_COORDINATE_SYSTEM MD17200 $MN_GMMC_INFO_NO_UNIT[3]
● Programmed axis positions are represented as absolute positions in the coordinate system
(WCS / SZS) specified in MD9424 $MM_MA_COORDINATE_SYSTEM (coordinate system
for actual value display)
Note
The modulo correction is omitted for modulo axes, which means that positions outside the
modulo range can be displayed. It also means that the basic block display differs from the
position display in which values are always modulo-converted.
Basic functions
Examples
Comparisons between display block (original block) and basic block display:
● Programmed positions are displayed as absolute.
The addresses AP/RP are displayed with their programmed values.
Original block: Display block:

N10 G90 X10.123 N10 X10.123
N20 G91 X1 N20 X11.123
● Address assignments (non-DIN addresses) are displayed in the form <address> =

<constant>.

N110 R1 = -67.5 R2 = 7.5
N130 Z = R1 RND = R2 N130 Z-67.5 RND = 7.5
● Address indices (address extensions) are displayed as constants <address> [ <constant> ]

= <constant>.

N220 DEF AXIS AXIS_VAR = X
N240 FA[ AXIS_VAR] = R2 N240 FA[X] = 1000
● DIN addresses without address extension are displayed in the form

<din_address> <constant>.

N410 DEF REAL FEED = 1.5
N420 F = FEED N420 F1.5
Basic functions
The following applies for H functions: Each programmed value is display irrespective of the
output type to the PLC.
(MD22110 $MC_AUXFU_H_TYPE_INT (type of H auxiliary function is integer)).
● For Tool selection by tool command
Display information is generated in the form T<value> or T=<string>. If an address
extension has been programmed, this is displayed as well.
If several spindles have been configured or the "Tool change via master toolholder" function
(MD20124 $MC_TOOL_MANAGEMENT_TOOLHOLDER (toolholder number)) is active,
the T number is always output with address extension.
If no address extension has been programmed, the number of the master spindle or the
master toolholder is used instead (T<spindle_number/tool_holder>= ).
● For the Spindle programming via S, M3, M4, M5, M19, M40 - M45 and M70 (or MD 20094
$MC_SPIND_RIGID_TAPPING_M_NR (M function for switching over in the controlled axis
operation)) the following regulation applies regarding the address extension:
If an address extension has been programmed, then this is also resolved.
If several spindles have been configured, then the address extension is also output.
If no address extension has been programmed, the number of the master spindle is used
(S<spindle_number>=).
● Indirect G command programming in form G[ <group> ] = <expression> is substituted by the
corresponding G command.

N510 R1=2
N520 G[8]= R1 N520 G54
● Modal G commands that do not generate an executable block are collected and output with
the display block of the next executable block if permitted by the syntax (DIN block). If this
is not the case (e.g. predefined subprogram call TRANSMIT), a separate display block
containing the modified G commands is placed in front of the next executable block.

N610 G64 G64
N620 TRANSMIT N620 TRANSMIT
● A display block is always generated for part program lines in which the addresses F and FA
appear (including for MD22240 $MC_AUXFU_F_SYNC_TYPE = 3 (output time of the F
functions)).

N630 F1000 N630 F1000
N640 X100 N640 X100
● The display blocks generated for the block display are derived directly from the programmed
part program blocks. If intermediate blocks (e.g. tool radius compensation G41/G42, radius/
chamfer RNDM, RND, CHF, CHR) are generated in the course of contour preprocessing,
these are assigned the display information from the part program block on which the motion
is based.
Basic functions
2.6 Program control

N710 Y157.5 G42 N710 Y157.5 G42
N720 Z-67.5 RND=7.5 N720 Z-67.5 RND=7.5
● With the EXECTAB command (processing a table of contour elements), the block
generated by EXECTAB is shown in the display block.

N810 EXECTAB (KTAB[5]) N810 G01 X46.147 Z-25.38
● With the EXECSTRING command, the block generated via EXECSTRING is displayed in
the display block.
Original block:
N910 DEF STRING[40] PROGSTRING = "N905 M3 S1000 G94 Z100 F1000 G55"
N920 EXECSTRING(PROGSTRING)
Original block:
N905 Z100 G55 G94 M3 S1000 F1000
2.6 Program control
2.6.1 Overview
The control system provides various functions for controlling the execution of an NC program.
These functions are predominantly used for testing and running-in a new part program. Using
these functions significantly reduces the danger to the machine and time required during the
test phase.
Several program control functions can be activated at the same time to achieve a better result.
Functions
The following program control functions are available:
● Program test (Page 93)
● Dry run feedrate (Page 96)
● Reduced rapid traverse (Page 98)
● Programmed stop (Page 99)
● Handwheel offset (Page 100)
● Skipping program blocks (Page 101)
Basic functions
2.6 Program control
● Single block (Page 103)

● Configured stop (Page 112)
Selecting and activating
Via the user interface

A program control function is selected for the active channel via the user interface, e.g.
SINUMERIK Operate:
1. Softkey: Operating area "Machine" > "Program control"
2. "Program control" menu: select the function checkbox.
The PLC then transfers the selection signal to the corresponding activation signal of the NC/
PLC interface.
Directly via the PLC user program

The function may also be directly activated via the PLC user program by setting the
corresponding activation signal in the NC/PLC interface.
Note
Selection activation via the user interface
The HMI request signals are only transferred from the basic PLC program to the PLC request
signals if FB1 parameter MMCToIF is set to TRUE:
● MMCTolf == "TRUE" ; ⇒ Transfer (default setting)
● MMCTolf == "FALSE" ; ⇒ No transfer
If the parameters are not set, the PLC request signals must be set by the PLC user program.
Note
Activation via the PLC user program
The FB1 parameter MMCToIf must be set to "FALSE", otherwise the NC/PLC interface would
be overwritten with the values of the HMI/PLC interface.
Basic functions
2.6 Program control
2.6.2 Program test
Function
In the "Program test" state, a part program can be executed without actually traversing any of
the machine axes. The user can use this to check the programmed axis positions and auxiliary
function outputs of a part program. This program simulation can also be used as an extended
syntax check.
Note
Spindle traversing motion
Contrary to the machine axes - in the "Program test" state - traversing motion of the spindles
of the channel is enabled as default setting (see Section "Basic setting").
If, in the "Program test" state, spindles are not to be traversed, then they must be explicitly
inhibited/locked via the PLC user program:
Basic settings
The following settings apply as default setting for channels in the "Program test" state:
● Setpoints identical to normal operation are generated for the axes; however they are not
output to the machine axes.
● For the spindles, setpoints are output to the machine axes.
● The displayed actual values of the inhibited axes/spindles are internally generated from
setpoints.
● The commands for channel synchronization are processed normally.
● The NC/PLC interface signals are processed normally.
● The processing time of the program is the same as in normal operation.
Temporarily when required, the "Program test" state can be exited on an axis-for-axis basis.
The setpoints are then output again on the machine axes so that they actually traverse at the
machine.
Selecting and activating
Via the user interface

"Program test" for the channel displayed in the "Machine" basic display is selected via the user
interface, e.g. SINUMERIK Operate:
2. "Program control" menu: Select check box "Program test (PRT)".
PLC interface.
Basic functions
2.6 Program control
Directly via the PLC user program


After selecting program test (PRT), the following NC/PLC interface signals are set (see below
note "Automatic transfer of interface signals"):
● Channels
– DB21, ... DBX25.7 (from the HMI: program test selected) == 1
– DB21, ... DBX1.7 (from the PLC: activate program test) == 1
– DB21, ... DBX33.7 (from the NC: program test active) == 1
● Axes
– DB31, ... DBX128.0 (from the HMI: suppress program test) == 0
– DB31, ... DBX128.1 (activate program test from the HMI) == 0
– DB31, ... DBX14.0 (from the PLC: suppress program test) == 0
● Spindles
– DB31, ... DBX128.0 (from the HMI: suppress program test) == 1
– DB31, ... DBX128.1 (from the HMI: activate program test) == 0
– DB31, ... DBX14.0 (from the PLC: suppress program test) == 1
Note
Default state of traversing motion
The default state regarding traversing motion after selecting "Program test" in the channel is:
● Axes: Inhibited
● Spindles: Enabled
Inhibiting spindle traversing motion

If, during "Program test" spindles are not to be traversed, then they must be explicitly inhibited/
locked via the PLC user program:
● DB31, ... DBX128.0 (suppress program test) == 0
● DB31, ... DBX128.1 (activate program test) == 1
● DB31, ... DBX14.0 (from the PLC: suppress program test) == 0
● DB31, ... DBX14.1 (from the PLC: activate program test) == 1
Basic functions
2.6 Program control
Enable axis traversing motion

If, during "Program test" channel axes are to be traversed, then they must be explicitly enabled
via the PLC user program:
● DB31, ... DBX14.0 (from the PLC: suppress program test) == 1
● DB31, ... DBX14.1 (from the PLC: activate program test) == 0
Permissible switching instants

● Channel
Interface signals to deactivate/activate the channel-specific "Program test" state (DB21, ...
DBX25.7 or DBX1.7), may only be switched in the "Reset" or "Interrupted" channel state.
● Axes/spindles
Interface signals to activate/deactivate the axis-specific "Program test" state (DB31, ...
DBX128.0 / .1 or DBX14.0 / .1) may always be switched.
Program start and program run

When the program test function is active, the part program can be started and executed via the
following NC/PLC interface signals (incl. auxiliary function outputs, wait times, G command
outputs, etc.):
DB21, ... DBX7.1 (NC Start)
The safety functions such as software limit switches, working area limits continue to be valid.
The programmed velocities remain unchanged. This means that the position and velocity
information on the operator interface is exactly the same as that output during normal part
program execution. The position control is not interrupted, so the axes do not have to be
referenced when the function is switched off.
Note
The signals for exact stop DB31, ... DBX60.6/60.7 (exact stop coarse/fine) mirror the actual
status on the machine.
They are only canceled during program testing if the axis is pushed out of its set position (the
set position remains constant during program testing).
With signal DB21, ... DBX33.7 (program test active) both the PLC program and the part
program can use variable $P_ISTEST to decide how to react or branch in response to these
signals during testing.
Note
Dry run feedrate
Program execution in the "program test" state can also be activated using the "Dry run feedrate"
function. With this function, part program sections with a small programmed feedrate can be
processed in a shorter time.
Basic functions
2.6 Program control
Note
Tool management
Because of the axis disable, the assignment of a tool magazine is not changed during program
testing. A PLC application must be used to ensure that the consistency between the data in the
tool management system and the magazine is not corrupted.
2.6.3 Dry run feedrate
Function
To reduce the processing time during the program test, traversing motion can be executed
faster by activating the drive run feedrate. For example, for G01, G02, G03, G33, G34, G35,
G95, the test feedrate applies instead of the programmed feedrate.
NOTICE
Destroyed tool or workpiece as a result of excessively high cutting velocities
When a workpiece is machined with the dry run feedrate function active, the resulting cutting
velocities may lie outside the permissible range and lead to destruction of the tool and / or
workpiece.
As a consequence, the dry run feedrate should only be used for the program test.
Activation
The dry run feedrate is selected at the user interface in the AUTOMATIC and MDI modes, and
can be activated when automatic operation is interrupted or at the end of the block.
Selection
The "Dry run feedrate" function is selected for the channel displayed in the "Machine" basic
display via the user interface, e.g. SINUMERIK Operate:
2. "Program control" menu: select checkbox "Dry run feedrate (DRY)".
The following signal is set in the HMI/PLC interface to request that the PLC user program
activates the function:
DB21, ... DBX24.6 (dry run feedrate selected) == 1
Basic functions
2.6 Program control
PLC interface.
Note
Activation
To request that the NC activates the function, the PLC user program must set the following NC/
PLC interface signal:
DB21, ... DBX0.6 (activate dry run feedrate) == 1
Feedback signal
The following NC/PLC interface signal is set as feedback signal to the PLC user program that
the function is active in the NC:
DB21, ... DBX318.6 (dry run feedrate active) == 1
Parameterization
Dry run feedrate

The dry run feedrate effective in the channel is set using:
SD42100 $SC_DRY_RUN_FEED = <dry run feedrate>
Note
Revolutional feedrate
The dry run feedrate also replaces the programmed revolutional feedrate in program blocks
with G95.
Dry run feedrate mode

The dry run feedrate mode is set with:
SD42101 $SC_DRY_RUN_FEED_MODE = <value>
<Val‐ Meaning
ue>
0 The maximum from SD42100 and the programmed feedrate are effective as dry run feedrate.
1 The minimum from SD42100 and the programmed feedrate are effective as dry run feedrate.
2 SD42100 is effective as dry run feedrate.
10 The same as for a value of 0, except for thread cutting (G33, G34, G35) and tapping (G331,
G332, G63). For these functions, the programmed feedrate applies.
Basic functions
2.6 Program control
Further information
For additional information on influencing the feedrate, see Function Manual Axes and Spindles.
2.6.4 Reduced rapid traverse
Function
In the reduced rapid traverse mode (RG0), the traversing velocity of the axes is reduced to the
percentage value currently set for RG0.
Setting the RG0 value

The RG0 value is set via the user interface, e.g. SINUMERIK Operate:
1. Softkey: Operating area "Machine" > "Settings"
2. Window "Settings for automatic operation": Enter the percentage value in "Reduced rapid
traverse RG0".
Activation
Selection
The "Reduced rapid traverse" function is selected for the channel displayed in the "Machine"
basic display via the user interface, e.g. SINUMERIK Operate:
2. "Program control" menu: Select checkbox "Reduced rapid traverse (RG0)".
DB21, ... DBX25.3 (feedrate override selected for rapid traverse) == 1
Note
Activation
DB21, ... DBX6.6 (path rapid traverse override active) == 1
Basic functions
2.6 Program control
2.6.5 Programmed stop
Function
If function "Programmed stop 1" is active, then program execution stops at all blocks in which
supplementary function M01 is programmed. This means that while machining a workpiece,
users have the option of checking the results of individual machining steps.
Activation
Selection
The "Programmed stop 1" function is selected for the channel displayed in the "Machine" basic
2. "Program control" menu: Select checkbox "Reduced rapid traverse (RG0)".
DB21, ... DBX24.5 (M01 requested) == 1
Note
Activation
DB21, ... DBX0.5 (activate M01) == 1
Feedback signal
DB21, ... DBX32.5 (M01 active) == 1
If the NC program is stopped at the end of a block due to the function, the following NC/PLC
interface signal is set:
DB21, ... DBX35.2 (program status stopped) == 1
Basic functions
2.6 Program control
2.6.6 Handwheel offset
Function
The "Handwheel offset (DRF)" function can be used to set an additive incremental zero offset
for geometry and auxiliary axes in the basic coordinate system in the AUTOMATIC mode via
an electronic handwheel.
Typical applications:
● Compensating (correcting) tool wear within an NC block
Where NC blocks have very long processing times, it becomes necessary to offset tool wear
manually within the NC block (e.g. for milling machines that machine large surfaces).
● High precision compensation (correction) when grinding
● Simple temperature compensation
Activation
Selection
The "Handwheel offset" function is selected for the channel displayed in the "Machine" basic
2. "Program control" menu: select checkbox "Handwheel offset (DRF)".
DB21, ... DBX24.3 (handwheel offset requested) == 1
Note
Activation
DB21, ... DBX0.3 (activate handwheel offset) == 1
Feedback signal
DB21, ... DBX33.3 (handwheel offset active) == 1
Basic functions
2.6 Program control
Further information
Detailed information about the DRF offset function is provided in Function Manual Axes and
Spindles.
2.6.7 Skipping program blocks
NC blocks, which are not to be executed every time the program runs, can be skipped and not
processed. This function is used when testing and/or running-in new programs, for example.
Skip blocks
Blocks to be skipped are indicated in the part program by the character "/" before the block
number. Several consecutive blocks can also be skipped. The instructions in the skipped
blocks are not executed and the program resumes with the next block that is not skipped.
Example:
1
1
1
1
1
1
1
1
1
1
1
1

N10 … ; Is executed
/N20 … ; Skipped
/N40 … ; Skipped
/N50 … ; Skipped
/N60 … ; Skipped
...
Basic functions
2.6 Program control
Skip levels
Blocks can be assigned to skip levels (max. 10), which can be activated via the user interface
or the PLC user program.
The assignment is made in the NC program using a forward slash, followed by the number of
the skip level. Only one skip level can be specified for each block.
Example:

/ ... ; Block is skipped (1st skip level)
/0 ... ; Block is skipped (1st skip level)
/1 N010... ; Block is skipped (2nd skip level)
/2 N020... ; Block is skipped (3rd skip level)
...
/7 N100... ; Block is skipped (8th skip level)
Note
The levels to be skipped can only be changed when the control system is in the STOP/reset
state.
Note
The number of skip levels that can be used depends on a display machine data.
Note
Skipping blocks also remains active during block searches.
Note
System and user variables can also be used in conditional jumps in order to control program
execution.
Selection
Skip levels for the channel displayed in the "Machine" basic display are selected via the user
interface, e.g. SINUMERIK Operate:
2. "Program control" menu: Select checkbox "Skip level... (SKP)".
The associated signal is set in the HMI/PLC interface to request that the PLC user program
activates the selected skip level:
DB21, ... DBX26.0 (skip blocks of the 1st skip level) == 1
DB21, ... DBX26.1 (skip blocks of the 2nd skip level) == 1
...
Basic functions
2.6 Program control
DB21, ... DBX26.7 (skip blocks of the 8th skip level) == 1

Note
Activation
To request that the NC activates the skip level, the PLC user program must set the appropriate
NC/PLC interface signal:
DB21, ... DBX2.0 (skip blocks of the 1st skip level) == 1
DB21, ... DBX2.1 (skip blocks of the 2nd skip level) == 1
...
Parameterization
Number of skip levels

The number of skip levels is defined using machine data:
MD51029 $MM_MAX_SKP_LEVEL (max. number of skip levels in the NC program)
2.6.8 Single block
2.6.8.1 Function
For single block execution, part program execution stops after every program block. If tool
radius compensation is selected, processing stops after every intermediate block inserted by
the control system. The program status switches to "Program status stopped". The channel
status remains active. The next part program block is processed on NC Start.
Application
With this function, users have the option of executing a part program block for block - and
checking the individual machining steps. The next block can be executed once the user decides
that an executed part program block is functioning correctly.
Basic functions
2.6 Program control
Single block types

The following single block types are available:
● "SB1: Single block coarse" (stop after each block with a machine function = main run block)
After each completely executed block with a machine function, the NC program and/or
processing is stopped.
● "SB2: Calculation block" (stop after each block, including calculation blocks and comment
blocks)
After each block, the NC program or processing is stopped.
● "SB3: Single block fine" (stop after every block with machine function, even in a cycle)
As for SB1, but stops after every block with a machine function in cycles, too.
See also
Constraints (Page 110)
2.6.8.2 Selecting and activating
Selection
Single block processing can be selected:
● Via the machine control panel (key "Single Block")
● Via the user interface, e.g. SINUMERIK Operate:
1. Operating area "Machine" > "Program control"
2. Menu: "Program control": In the single block type selection list, select "SB1", "SB2" or
"SB3".
Further information: Operating Manual
Activation
The PLC basic program activates the function for the selected channel via the NC/PLC
interface signal:
DB21, ... DBX0.4 (activate single block) == 1
Feedback signal
Once the program has executed a part program block in single block mode, the following NC/
PLC interface signals are set:
DB21, ... DBX39.4 (stop at block end due to single block) == 1
Basic functions
2.6 Program control
Machine data
Deactivate single-block execution

In the following machine data, it is possible to select for certain machining situations and
program types that a stop will not be performed although the single block function is active:
MD10702 $MN_IGNORE_SINGLEBLOCK_MASK
Note
By programming (Page 106) SBLON/SBLOF within an ASUB or subprogram, single block
machining can be explicitly activated/deactivated.
Note
For single block type "SB2: Calculation block", the machine data only active for system ASUBs,
user ASUBs and subprograms with attribute DISPLOF.
Behavior of event-controlled program calls

The behavior of event-driven program calls (program events) with respect to a single block is
set using:
MD20106 $MC_PROG_EVENT_IGN_SINGLEBLOCK
The behavior of interrupt programs (ASUB)

The behavior of interrupt programs (ASUB) with respect to a single block is set using:
MD20117 $MC_IGNORE_SINGLEBLOCK_ASUB
If an ASUB is activated during the single block, execution of the ASUB is completed. The single
block does not act until after the ASUB or in the first main run block in which single-block
suppression is not activated. On the transition from ASUB to the NC program, if the path
velocity is too large so that it is not possible to brake to standstill in the following block, e.g. when
continuous-path mode G64 is active, the deceleration may extend over several following
blocks.
Note
By programming (Page 106) SBLON within an ASUB, in this case single block
processing cannot be reactivated.
Setting data
Debug mode for single block "SB2: calculation block" (SD42200)

Because the blocks are decoded in advance, the connection between the current block display
referring to the main run and the displayed variable values at the user interface can be lost. In
that case, the variable values displayed may not be plausible.
Basic functions
2.6 Program control
With the following channel-specific setting data, it is possible to set that, when single block
"SB2: calculation block" is active, a preprocessing stop will be performed for each block. This
suppresses the advance processing of part program blocks and maintains the connection
between the current block display and the display of variable values.
SD42200 $SC_SINGLEBLOCK2_STOPRE (activate debug mode for SB2)
Note
Contour deviation
When executing traversing blocks with single block type "SB2: Calculation block" in the debug
mode, contour deviations can occur.
2.6.8.4 Programming
Even with active single block machining, the user can completely or partly process an NC
program without interruption. Single block machining is suppressed via the SBLOF command,
and reactivated via the SBLON command.
Suppressing single block machining for the complete NC program

If the deactivation of single block machining (SBLOF) is programmed in the first line (PROC ...)
of a main program, this remains valid until the end of the NC program or until the NC program
is canceled. The NC program is then executed without stopping when in the single block mode.
If deactivating single block machining (SBLOF) is programmed in the first line (PROC ...) of a
subprogram, this remains valid until the end of the NC program or until the NC program is
canceled. With the programmed return command, the decision is made whether to stop at the
end of the subprogram:
● Return with M17: Stop at the end of the subprogram
● Return with RET: No stop at end of subprogram
Suppressing single block machining within the NC program

If the deactivation of single block machining (SBLOF) is programmed in a block within an NC
program, then single block machining is deactivated from this block onward up to the next
programmed activation of single block machining (SBLON) - or at the end of the active
subprogram level.
Syntax
Suppressing single block machining for the complete NC program:
PROC ... SBLOF

...
Suppressing single block machining within the NC program:
...
SBLOF
...
Basic functions
2.6 Program control
SBLON
...
Meaning
PROC: First operation in a program

SBLOF: Predefined procedure to deactivate single block machining
Alone in the block: Yes, possible in the PROC block
Effectiveness: Modal
SBLON: Predefined procedure to activate single block machining
Alone in the block: yes
Special aspects
● Block display with suppressed single block machining
The current block display can be suppressed in subprograms using DISPLOF. If DISPLOF
is programmed together with SBLOF, for single block stops within the subprogram, the
subprogram call is displayed.
● Suppression of single block machining with asynchronous subprograms (ASUB)
In order to execute an ASUB with active single block machining in one step, a PROC
statement must be programmed in the ASUB with SBLOF. This also applies to the function
"Editable system ASUB" (MD11610 $MN_ASUP_EDITABLE).
If the single block stop in the system or user ASUB is suppressed by programming SBLOF
in the PROC line or using the settings in machine data
MD10702 $MN_IGNORE_SINGLEBLOCK_MASK (bit0 = 1 or bit1 = 1), then the single
block stop can be reactivated by programming SBLON in the ASUB.
If the single block stop in the user ASUB is suppressed using the setting in machine data
MD20117 $MC_IGNORE_SINGLEBLOCK_ASUP, the single block stop cannot be
reactivated by programming SBLON in the ASUB.
● Special features for various single block machining types
– "SB2: Arithmetic block" AND MD10702 $MN_IGNORE_SINGLEBLOCK_MASK,
Bit 12 = 1:
→ The program is not stopped in the SBLON block.
– "SB3: single block fine":
→ The SBLOF command is suppressed.
● Suppression of single block machining in nested programs
If SBLOF was programmed in the PROC statement in a subprogram, then execution is
stopped at the subprogram return with M17. That prevents the next block in the calling
program from already running. If, in a subprogram with SBLOF, without SBLOF in the PROC
statement, a suppression of single block machining is activated, execution is only stopped
after the next machine function block of the calling program. If that is not wanted, SBLON
must be programmed in the subprogram before the return (M17). Execution does not stop
for a return to a higher-level program with RET.
Basic functions
2.6 Program control
Examples
Example 1: Suppressing single block machining within the NC program

Initial situation: Single block machining is active.

N10 G1 X100 F1000
N20 SBLOF ; Switch off single block machining
N30 Y20
N40 M100
N50 R10=90
N60 SBLON ; Reactivate single block machining
N70 M110
N80 ...
The area between N20 and N60 is executed as one step in single block mode.
Example 2: A cycle is to act like a command for a user

Initial situation: Single block machining is active.
Main program:
Program code
...
N100 G1 X10 G90 F200
N120 X-4 Y6
N130 CYCLE1
N140 G1 X0
N150 M30
Cycle CYCLE1:

N100 PROC CYCLE1 DISPLOF SBLOF ; Suppress single block machining for the com-
plete program.
N110 R10=3*SIN(R20)+5
N120 IF (R11 <= 0)
N130 SETAL(61000)
N140 ENDIF
N150 G1 G91 Z=R10 F=R11
N160 M17
The cycle CYCLE1 is processed with active single block machining. CYCLE1 is processed for
active single block machining, i.e. the Start key must be pressed once to process CYCLE1.
Basic functions
2.6 Program control
Example 3: An ASUB, which is started by the PLC in order to activate a modified zero offset and
tool offsets, is to be executed invisibly

N100 PROC NV SBLOF DISPLOF ; Suppress single block machining and block
display.
N110 CASE $P_UIFRNUM OF
0 GOTOF _G500
1 GOTOF _G54
2 GOTOF _G55
3 GOTOF _G56
4 GOTOF _G57
DEFAULT GOTOF END
N120 _G54: G54 D=$P_TOOL T=$P_TOOLNO
N130 RET
N150 RET
N170 RET
N190 RET
N200 END: D=$P_TOOL T=$P_TOOLNO
N210 RET
Example 4: Specific stopping in the subprogram

Initial situation:
● Single block machining is active.
● MD10702 $MN_IGNORE_SINGLEBLOCK_MASK, Bit12 = 1
Main program:

N10 G0 X0 ; single block stop
N20 X10 ; single block stop
N30 CYCLE ; Traversing block generated by the cycle.
N50 G90 X20 ; single block stop
M30
Cycle CYCLE:

PROC CYCLE SBLOF ; Suppress single block machining
N100 R0=1
N110 SBLON ; No single block stop due to MD10702 bit12 = 1
N140 SBLOF
N150 R0=2
Basic functions
2.6 Program control

RET
Example 5: Suppression of single block machining with program nesting

Initial situation:
● Single block machining type 2 is active.
● The program execution shall not be interrupted in the SBLON block
(MD10702 $MN_IGNORE_SINGLEBLOCK_MASK, Bit12 = 1)

N10 X0 F1000 ; single block stop
N20 UP1(0)
PROC UP1(INT _NR) SBLOF ; Deactivate single block machining for
UP1
N100 X10
N110 UP2(0)
PROC UP2(INT _NR)
N200 X20
N210 SBLON ; Activate single block machining
N230 UP3(0)
PROC UP3(INT _NR)
N305 X30
N310 SBLON ; Activate single block machining
N340 X34
N350 M17 ; single block stop (M17)
N240 X24 ; single block stop (N210)
N120 X12
N40 M30 ; single block stop
2.6.8.5 Constraints
Behavior when synchronized actions are used

For single block type "SB2: Calculation block" for a block-related synchronized action, the next
stop is only executed after the next main run block (block with a machine function). No stop is
performed during preprocessing blocks between the synchronized action and the next main run
block.
Basic functions
2.6 Program control
Behavior for G33/G34/G35

For a series of G33/G34/G35 blocks, single block SB1 or SB3 is only active if "Dry run feedrate"
is selected. SB2 has no effect for G33/G34/G35. Calculation blocks are not processed in single-
step mode (only if single decoding block is active).
Alarm 16922
Initial situation: In a channel, an NC program is stopped by an M0 programmed in it, and in the
channel a single block is active (DB21, ... DBX0.4 == 1)
If, in this situation the single block type is toggled between SB1 or SB3 and SB2 at the user
interface several times, then alarm 16922 "Maximum nesting depth exceeded" is displayed.
2.6.9 Mode group-specific single block type A / B

For a mode group-specific single block, in a channel (control channel) the NC program is
executed in single blocks. In the control channel, single block must be activated using the NC/
PLC interface signal DB21 ... DBX0.4.
In the remaining channels of the mode group ("dependent channels"), the respective NC
program is executed block-by-block in accordance with the single block type A or B, which was
selected mode group-specifically via NC/PLC interface signal DB11 DBX1.6/7. In the
dependent channels, it is not permissible that the NC/PLC interface signal DB21 ... DBX0.4 is
set.
Single block type A / B

Single block type A: If the control channel stops, then also the dependent channels immediately
stop, comparable with NC stop.
Single block type B: If the control channel stops, then also the dependent channels stop at the
particular end of block, comparable with NC stop at the block limit.
Interface signals
Control channel
● DB21, ... DBX0.4 (activate single block)
All channels of the mode group

● DB21, ... DBX7.1 (NC Start)
Mode group
● DB11 DBX1.6 (single block, type B)
● DB11 DBX1.7 (single block, type A)
Basic functions
2.6 Program control
Schematic execution sequence for single block type A

Prerequisite: All mode group channels are in the "Reset" or "Interrupted" state.
1. PLC user program: Select single block in the control channel, DB21 ... DBX0.4 = 1
2. PLC user program: Select single block type A for the mode group, DB11 DBX1.7 = 1
3. PLC user program: All channels of the mode group start, DB21 ... DBX0.4 = 1
4. The control channel stops at the end of the block.
5. All dependent channels receive an internal signal to immediately stop machining.
6. All mode group channels are in the "Interrupted" state once all of the dependent channels
have reached the particular end of the braking phase.
Schematic execution sequence for single block type B

Prerequisite: All mode group channels are in the "Reset" or "Interrupted" state.
1. PLC user program: Select single block in the control channel, DB21 ... DBX0.4 = 1
2. PLC user program: Select single block type B for the mode group, DB11 DBX1.6 = 1
3. PLC user program: All channels of the mode group start, DB21 ... DBX0.4 = 1
4. The control channel stops at the end of the block.
5. All dependent channels receive an internal signal to stop machining at the end of the block.
6. All mode group channels are in the "Interrupted" state once all of the dependent channels
have reached the particular end of the block.
2.6.10 Configured stop
2.6.10.1 Function
Unlike with the "Single block" function, in which the NC program is stopped after each block, the
"Configured stop" function gives the machine operator the capability of stopping only at critical
program locations. Before the program is started, the operator must select the stop situations
that are relevant for this from a selection defined by the machine manufacturer.
Definition of stop situations

The following NC function calls or NC function transitions can be specified as stop situations:
● M/H/T/D function calls
● Calls of subprograms (and user ASUBs)
● G function transitions:
– G0 → Not-G0
– Not-G0 → G0
– G0 → G0
Basic functions
2.6 Program control
The stop situations for the configured stop are defined during commissioning by means of
setting data (Page 115). The machine operator selects and activates (Page 113) this via the
user interface or directly through the PLC user program.
Program flow
If the controller during program interpretation detects a function/subprogram call or G function
transition that is defined as a stop situation, the NC program is stopped at the end of the block
before the block with the function/subprogram call or G function transition. The program status
switches to "Program status stopped". The channel status remains active. The program
execution can be continued up to the next stop situation with NC start.
Applications
Tool and mold making

Part programs in tool and mold making can be made up of a large number of short G1 blocks,
which delineate a single path on the workpiece. To ensure that the program is not stopped after
each of these short G1 blocks when single block processing is active, the machine operator can
use the "Configured stop" function instead of single block processing and specify, for example,
that stops are only to take place before the G0 feed motion to the next path of the workpiece
(stop situation "Transition Not G0 → G0"). For the long G0 blocks that are more critical to the
execution and are traversed at maximum speed, a stop should be made after each G0 block
(stop situation "Transition G0 → G0").
Positioning a workpiece
In machine tools, many machine functions are implemented with auxiliary functions (M/H
functions) or cycles (subprograms) (e.g. tool change, traverse steady rest to the workpiece,
etc.). When positioning a workpiece, the machine operator usually wants to execute such
machine functions somewhat more slowly to ensure that no collisions occur. With the aid of the
"Configured stop" function, the operator can stop the program before the start of the cycle or
before the auxiliary function is started and then set the override switch down to 0%. Then the
operator continues program execution with NC start. The block with the cycle or auxiliary
function is loaded and traversing is started by turning on the override switch.
Note
The override value can also be set to 0% via the PLC user program.
Another critical situation when positioning a workpiece is the start of motions involving large
masses or bodies. The "Configured stop" function can also be used to make stops before such
motions if a suitable stop situation has been defined prior to the program start.
2.6.10.2 Selecting and activating
Selection
It is possible to select the "Configured stop" function for the channel displayed in the root screen
"Machine" in all modes via the operator interface.
Basic functions
2.6 Program control
E.g. SINUMERIK Operate:

1. Operating area "Machine" > "Program control"
2. "Program control" window: select "CST configured stop"
The relevant stop situations are selected via the corresponding selection box in the "Program
control" window. All of the stop situations that were defined during commissioning are listed
there.
To select the function and the relevant stop situations, the channel must be in the "Reset" or
"Interrupted" state:
DB21, … DBX35.7 == 1 (channel status "reset")
DB21, ... DBX35.6 == 1 (channel state "interrupted")
DB21, ... DBX24.1 (activate configured stop) == 1
Note
Activation
DB21, ... DBX7.6 (activate configured stop) == 1
Feedback signal
DB21, ... DBX39.6 (configured stop is activated) == 1
If the NC program is stopped at the end of a block due to the function, the following NC/PLC
interface signals are set:
DB21, ... DBX39.7 (stop at block end due to configured stop) == 1
Deselection
It is possible to deselect the "Configured stop" function in all program and channel states.
Basic functions
2.6 Program control
2.6.10.3 Parameter assignment
Machine data
Preventing a configured stop

You can use the following machine data to prevent stopping in certain machining situations
despite the "Configured stop" function being active:
MD10703 $MN_IGNORE_CFG_STOP_MASK
Setting data
Definition of stop situations

The stop situations for the configured stop are defined by the following setting data:
Setting data Meaning

SD42220 $SC_CFG_STOP_ARRAY[<n>] = "<Name>" NC functions and subprograms before which stops are to be made
<Name>: Name of the NC function/subprogram
Data type: STRING
The following are permitted:
● M/H/T/D function calls
The following syntax rules must be observed:
– No address extensions are supported for D.
– The value of the auxiliary function is always a
positive INTEGER value, including 0.
– Negative INTEGER values for the address ex‐
tension are permitted for M functions.
Example: "M[-5]=3"
– An asterisk (*) is permitted as a wildcard.
Example: "M[*]=87" / "M*=87"
● Subprogram names
Valid nomenclature: "_N_..."
<n>: Array index
Data type: INT
Range of values: 0 ... 19
Examples:
● $SC_CFG_STOP_ARRAY[0] = "M=87"
● $SC_CFG_STOP_ARRAY[1] = "_N_CS_TOOL"
● $SC_CFG_STOP_ARRAY[3] = "_N_MY_TOOL_CHANGE"
SD42222 $SC_CFG_STOP_MASK G function transitions at which a stop should be made
Bit 0 G0 → G0
Bit 1 G0 → Not-G0
Bit 2 Not-G0 → G0
Basic functions
2.6 Program control

SD42224 $SC_CFG_STOP_ARRAY_MASK Release of SD42220 $SC_CFG_STOP_ARRAY[<n>]
Bit 0 Release of SD42220 $SC_CFG_STOP_ARRAY[0]
... ...
Note
The valid nomenclature and syntax rules must be observed when specifying the NC function or
subprogram name.
In the event of an error, alarm 16968 "Machine data $SC_CFG_STOP_ARRAY contains invalid
syntax" is displayed.
Example
$SC_CFG_STOP_MASK = 6 Stop before the selection and deselection

of G0
$SC_CFG_STOP_ARRAY[0]="_N_MY_UP_0" Stop before the call of subprogram
MY_UP_0
SC_CFG_STOP_ARRAY[1]="M=3" Stop before the execution of M3
$SC_CFG_STOP_ARRAY_MASK='H0FFF' Release of SD42220
$SC_CFG_STOP_ARRAY bit 0 ... 11
Just as with single block processing, the configured stop also permits switching off the function
in the NC program via the pre-defined SBLOF procedure and switching it on again via the
predefined SBLON procedure.
For further information, see Chapter "Single block (Page 103)".
2.6.10.5 Constraints
Configured stop during simultaneous single block execution

If the "Single block" and "Configured stop" functions are active at the same time, the configured
stop is additive. This means that additional stops by means of the configured stop are retained
and become effective, for example, when the single block stop is prevented by MD10702
$MN_IGNORE_SINGLEBLOCK_MASK.
Stop only in executable NC blocks

Stops by means of the "Configured stop" function can only take effect in executable blocks.
They have no effect in NC blocks which are deleted by the internal block execution.
Basic functions
2.6 Program control
Stop-preventing situations
Stops are ignored by the configured stop in the following situations:
● Tapping G331/G63 without spindle stop being active.
● Thread cutting G33 is active.
● Retraction motion of the tool is active.
● During an ASUB in the startup.
● During a Safety ASUB.
● Upon occurrence in a conditionally interruptible program area (stop-delay area).
Synchronized actions
The action part of a synchronized action is not evaluated for the configured stop! An auxiliary
function specified as a stop situation therefore does not result in a program stop upon
occurrence in a synchronized action.
2.6.10.6 Examples
Stop situation: Transition G0 → G0
Parameter assignment
$SC_CFG_STOP_MASK = 1 Stop when transitioning from G0 to G0
Programming example
Program code
N10 G0 X10
N20 G0 X20
N30 G1 X30 F1000
N40 G1 X40
N50 G0 X50
N60 G0 X70
N70 M30
Program flow
NC start → The program starts, then stops after reaching position X10 in block N10.
NC start → The program is continued, then stopped after position X50 in block N50 is
reached.
NC start → The program is continued without further stops until the end of the program.
Basic functions
2.6 Program control
Stop situation: M function
$SC_CFG_STOP_ARRAY[3]="M=88" Stop before execution of auxiliary function M88

$SC_CFG_STOP_ARRAY_MASK='H8' Release of SD42220 $SC_CFG_STOP_ARRAY
bit 3
Program example 1
Program code
N10 G0 X10
N20 G0 X20
N30 G1 X30 F1000
N35 M88
N40 G1 X40
N50 G0 X50
N60 M30
Program execution 1
NC start → The program starts. Stops at the end of block N30 at position X = 30.
NC start → Output of the M function, the program is continued without further stops
until the end of the program.
Program example 2
Program code
N10 G0 X10
N20 G0 X20
N30 G1 X30 M88 F1000
N40 G1 X40
N50 G0 X50
N60 M30
Program execution 2
NC start → The program starts. Stops at the end of block N20 at position X = 20.
NC start → The output of the M function takes place in block N30, the program is
continued without further stops until the end of the program.
Program example 3
Program code
N10 G0 X10
N20 G0 X20
N30 G1 X30 F1000
N35 WHEN TRUE DO M88
N40 G1 X40
Basic functions
2.6 Program control
Program code
N50 G0 X50
N60 M30
Program execution 3
NC start → The program starts and is executed until the end of the program. The aux‐
iliary function call in the action part of the synchronized action does not
result in a program stop.
Stop situation: Subprogram
$SC_CFG_STOP_AR‐ Stop before execution of the CS_TOOL subpro‐

RAY[0]="_N_CS_TOOL" gram
$SC_CFG_STOP_ARRAY_MASK='H1' Release of SD42220 $SC_CFG_STOP_ARRAY
bit 0
Programming example
Program code
N10 G0 X10
N20 G0 X20
N30 G1 X30 F1000
N35 CS_TOOL
N40 G1 X40
N50 G0 X50
N60 G0 X70
N70 M30
Program flow
NC start → The program starts, then stops after reaching position X30 in block N30.
NC start → The program is continued without further stops until the end of the program.
Stop situation: Tool change with T function

In the following example, the "Configured stop" function is to be used to only stop before
specific tool changes on a turning machine with a tool turret and inactive tool management
system.
$MN_MM_TOOL_MANAGE‐ No memory reserving for tool management

MENT_MASK = 0
$MC_TOOL_MANAGEMENT_MASK = 0 Tool management inactive
$MC_TOOL_CHANGE_MODE = 0 Tool change with T number
Basic functions
2.6 Program control
$SC_CFG_STOP_ARRAY[0] = 'T=1' Stop before switching in tool T=1

$SC_CFG_STOP_ARRAY[1] = 'T=3' Stop before switching in tool T=3
$SC_CFG_STOP_ARRAY_MASK = 3 Release of SD42220 $SC_CFG_STOP_ARRAY
bit 0 and 1
Programming example

...
N50 G0 Z0
N100 G0 Z10 X20 ; Stop at Z10 X20
N200 T1 ; NC start required to continue the program and for tool
change
N250 G1 X9
N300 G1 Z100
N350 G1 X20
N400 G1 Z10 ; No stop because T2 not in $SC_CFG_STOP_ARRAY
N500 T2
N550 G1 X9
N600 G1 Z100
N650 G1 X20
N700 G1 Z10 ; Stop at Z10 X20
N800 T3 ; NC start required to continue the program and for tool
change
N850 G1 X8
N900 G1 Z100
N950 G1 X20
N1000 G1 Z10
N2000 M30 ; Stop due to end of program
Note
Without tool management, the T functions are treated like any other auxiliary functions. This
allows a selective stop before a specific tool change (as shown in the example).
This is not possible with tool management. Here stops can only be made before each tool
change (with the stop situation "T[*]=*").
Basic functions
2.7 Block search, types 1, 2, and 4:
2.6.11 Status
The currently selected settings for program control can be read through system variables:
● In the part program via preprocessing variables:
System variable Type Meaning

$P_ISTEST BOOL Program test active
$P_DRYRUN BOOL Dry run feedrate active
$P_ISRG0 BOOL Reduced rapid traverse active
$P_ISPROGSTOP BOOL Programmed stop 1 (M01) active
$P_ISDRF BOOL Handwheel offset active
$P_ISSKIP BOOL Skip block active
● In the part program and in synchronized actions via the main run variable:

$AC_PROGINF INT Active program control
The value is bit-coded. These individual bits have the following mean‐
ing:
Bits 0 ... 9 Skip level 0 ... 9 active
Bit 10 Dry run feedrate active
Bit 11 Programmed stop 1 (M01) active
Bit 12 Handwheel offset active
Bit 13 Single block active
Bit 14 Reduced rapid traverse active
Bit 15 Feed stop active
Bit 16 Program test active
Bit 17 Associated help function (M-1) active
Bit 18 Configured stop active
Further information: List Manual System Variables
Function
Block search offers the possibility of starting part program execution from almost any part
program block.
This involves the NC rapidly performing an internal run through the part program (without
traversing motions) to the selected target block during block search. Here, every effort is made
to achieve the exact same control status as would result at the target block during normal part
program execution (e.g. with respect to axis positions, spindle speeds, loaded tools, NC/PLC
interface signals, variable values) in order to be able to resume automatic part program
execution from the target block with minimum manual intervention.
Basic functions
Block search types

● Type 1: Block search without calculation
Block search without calculation is used to find a part program block in the quickest possible
way. No calculation of any type is performed. The control status at the target block remains
unchanged compared to the status before the start of the block search.
● Type 2: Block search with calculation at contour
Block search with calculation at contour is used to enable the programmed contour to be
approached in any situation. On NC Start, the start position of the target block or the end
position of the block before the target block is approached. This is traversed up to the end
position. Processing is true to contour.
● Type 4: Block search with calculation at block end point
Block search with calculation at block end point is used to enable a target position (e.g. tool
change position) to be approached in any situation. The end position of the target block or
the next programmed position is approached using the type of interpolation valid in the
target block. This is not true to contour.
Only the axes programmed in the target block are moved. If necessary, a collision-free initial
situation must be created manually on the machine in "JOG REPOS" mode before the start
of further automatic part program execution.
● Type 5: Block search with calculation in "Program test" (SERUPRO) mode
SERUPRO (search run by programtest) is a cross-channel block search with calculation.
Here, the NC starts the selected part program in "Program test" mode. On reaching the
target block, the program test is automatically deselected. This type of block search also
enables interactions between the channel in which the block search is being performed and
synchronized actions as well as with other NC channels.
See Section "Block search Type 5 (SERUPRO) (Page 135)".
Note
For further explanations regarding the block search, see Section "Behavior during block search
(Page 653)."
Subsequent actions
After completion of a block search, the following subsequent actions may occur:
● Type 1 - Type 5: Automatic Start of an ASUP
When the last action block is activated, a user program can be started as an ASUP.
● Type 1 - Type 4: Cascaded block search
A further block search with a different target specification can be started from "Search target
found".
Basic functions
2.7.1 Description of the function
Basic sequence for type 2 or type 4

1. User: Activation of the block search type 2 or type 4 (block search with calculation to ...) via
the user interface
2. Search for the target block with collection of auxiliary functions
3. Stop after "Search target found ⇒ display of alarm 10208 "Continue program with NC start"
4. User: NC start to execute the action blocks ⇒ DB21, ... DBX7.1 = 1 (NC start)
5. Execution of the action blocks
6. Last action block is activated ⇒ Automatic start of /_N_CMA_DIR/_N_PROG_EVENT_SPF
(default) as an ASUB
7. Last ASUB block (REPOSA) is activated ⇒ DB21, ... DBX32.6 = 1 (last action block active)
8. Optional: Execution of user-specific requirements via PLC user program
9. Display of the alarm 10208 "Continue program with NC start"
10.User: Continue program with NC start ⇒ DB21, ... DBX7.1 = 1 (NC start)
Search target not found

If the search target is not found, alarm 15370 "Search target not found during block search" is
displayed and the block search is canceled.
Basic functions
Time sequence

%ORFNVHDUFKDFWLYH
'%'%;
$FWLRQEORFNDFWLYH
'%'%;
/DVWDFWLRQEORFNDFWLYH
'%'%;
&KDQQHOVWDWXVUHVHW
'%'%;
'%'%;
① Start block search

② Search target 1 found
③ Start block search
④ Search target 2 found
⑤ NC start - output action blocks
⑥ Last action block
Action blocks
During a block search type 2 or type 4 (block search with calculation to ...), actions such as tool
(T, D), spindle (S), feedrate programming or M function outputs are collected. With NC start to
execute the action blocks, the collected actions are output to the PLC.
Note
With NC start for the action blocks, the spindle programming collected during block search type
2 or type 4 (block search with calculation to ...) (S value, M3 / M4 / M5 / M19, SPOS) becomes
active.
The user has to ensure in the PLC user program that the tool can be operated or the spindle
programming is reset or not output:
DB31, ... DBX2.2 = 1 (spindle reset).
Constraints
Continuation mode after block search type 4

If initial programming of an axis is performed incrementally to a block search type 4 (block
search with calculation to block end point), the programmed incremental value can be added
Basic functions
to the position value collected up to the search target or to the current actual value of the axis.
The setting is realized via:
SD42444 $SC_TARGET_BLOCK_INCR_PROG
The setting data is evaluated with NC start for outputting the action blocks.
Single block
If you do not wish to stop after each action block after the search target during block search type
2 or type 4 (block search with calculation to ...) is found and while function "Single block"
(DB21, ... DBX0.4 == 1 (activate single block)) is active, this behavior can be deactivated in
machine data:
MD10702 $MN_IGNORE_SINGLEBLOCK_MASK, Bit 3 = 1 (ignore signal block for action
blocks)
Interface signal "start block active"

The interface signal is only set during block search type 2 (block search with calculation to
contour):
● DB21, ... DBX32.4 = 1 (approach block active)
For block search type 4 (block search with calculation to block end point), the interface signal
is not set because no approach block is generated here (approach block equal to target block).
Type of interpolation of the target block

For a block search type 4 (block search with calculation to block end point), the start movement
is performed in the interpolation type valid in the target block. For interpolation types other than
linear interpolation (G0 or G1), the start movement can be canceled with an alarm (e.g. circle
end point error in circular interpolation G2 or G3).
2.7.2 Block search in connection with other NCK functions
2.7.2.1 ASUB after and during block search
Block search type 2 and type 4: Synchronization of the channel axes

If an ASUP is started after a block search type 2 or type 4 (block search with calculation to ...)",
the actual positions of all channel axes are synchronized.
Effect
If the following system variables are read in the ASUP, they contain the following values:
● $P_EP: Current actual position of the channel axis in the WCS
● $AC_RETPOINT: Collected block search position of the channel axis in the WCS
Basic functions
Block search type 2: ASUP completion

For block search type 2 (block search with calculation at contour), the following
command REPOSA (reapproach to the contour; linear; all channel axes) must be programmed
by completion of the ASUP.
Effect
● All channel axes are moved to their search position that was collected during the block
search.
● $P_EP == "collected block search position of the channel axis (WCS)"
Block search type 4: REPOS behavior

After block search type 4 (block search with calculation to block end point), no automatic
repositioning is triggered during the period described by the beginning and end by the REPOS
command:
● Begin: NC/PLC interface signals DB21, ... DBX32.6 == 1 (last action block active)
● End: Continuing program execution with NC start.
The start point of the approach movement are the current positions of the channel axes at the
time of the NC start command. The end point results from the other transversing movements
programmed in the part program.
For block search type 4, no approach movement is generated by the NC.
Effect:
● After exiting the ASUP, the system variable $P_EP (programmed end position) contains the
actual position, at which the channel axes were positioned by the ASUP or manually (mode:
JOG).
$P_EP == "current actual position of the channel axis in the WCS
2.7.2.2 PLC actions after block search

If all action blocks have been executed by the NC and actions by the PLC, e.g. starting an ASUP
to perform a tool change, or of the operator, e.g. restore, are possible, the following channel-
specific NC/PLC interface signal is set:
● DB21, ... DB32.6 = 1 (last action block active)
Parameterizing the time of alarm output

To inform the operator that NC start is required in the channel to continue program execution,
alarm 10208 "Continue program with NC start" is displayed.
Basic functions
When the alarm is displayed can be set via machine data:

MD11450 $MN_SEARCH_RUN_MODE, Bit 0 = <value>
<value> Meaning
0 With the change of the last action block after a block search, the following takes place:
● Execution of the part program is stopped
● DB21, ... DBB32.6 = 1 (last action block active)
● Display alarm 10208
1 With the change of the last action block after a block search, the following takes place:
● Execution of the part program is stopped
● DB21, ... DBB32.6 = 1 (last action block active)
● Only display alarm 10208 if DB21, ... DBX1.6 == 1 (PLC action ended)
In combination with the alarm, the following interface signals are set:
● DB21, ... DBX36.7 = 1 (NC alarm with machining standstill is pending)
● DB21, ... DBX36.6 = 1 (NC alarm channel-specific is pending)
2.7.2.3 Spindle functions after block search
Control system response and output

Whether the spindle-specific auxiliary functions collected during block search are automatically
output to the PLC in the action block or user-specifically at a later time can be set in
MD11450 $MN_SEARCH_RUN_MODE, Bit 2 = <value>
<value> Meaning
0 Output of spindle-specific auxiliary functions collected during block search (M3, M4, M5, M19,
M70) in action blocks.
1 The spindle-specific auxiliary functions collected during block search are not output in the
action block.
They can be output at a later time, for example, in an ASUP. The spindle-specific auxiliary
functions collected are stored in system variables:
System variables
The spindle-specific auxiliary functions collected during block search are stored in the following
system variables:
System variable Description

$P_SEARCH_S [ <n> ] The spindle speed or cutting speed last programmed
$P_SEARCH_SDIR [ <n> ] Spindle direction last programmed
$P_SEARCH_SGEAR [ <n> ] Gear stages last programmed M function
$P_SEARCH_SMODE [ <n> ] Spindle mode last programmed
$P_SEARCH_SPOS [ <n> ] Spindle position or traverse path last programmed by means
of M19, SPOS or SPOSA
Basic functions

$P_SEARCH_SPOSMODE [ <n> ] Position approach mode last programmed by means of M19,
SPOS, or SPOSA
<n>: Spindle number
For later output of the spindle-specific auxiliary functions, the system variables can be read, for
example, in an ASUB, and output after output of the action blocks:
DB21, ... DBX32.6 == 1 (last action block active)
Note
The contents of the system variables $P_S, $P_DIR and $P_SGEAR may be lost after block
search due to synchronization operations.
For more detailed information on ASUB, block search and action blocks, see Sections "Output
suppression of spindle-specific auxiliary functions (Page 658)" and "Program test (Page 93)."
2.7.2.4 Reading system variables for a block search

In part programs, values can be read from the areas processing, main run, or servo/drive via
system variables:
$P_... Preprocessing-related system variables contain programmed values

$A_... Main-run-related system variables contain current values
$V_... Servo/drive-related system variables contain current values
Because no blocks enter the main run during a block search of type 2 and type 4 (block search
with calculation to ...), main run and servo/drive-related system variables are not changed
during the block search. Where necessary, for these system variables, the block search must
specially handled in the NC program by querying whether a block search is active $P_SEARCH
(block search active).
Preprocessing-related system variables provide correct values in all search types.
2.7.3 Automatic start of an ASUB after a block search
Making the function effective

The automatic ASUB start after a block search is activated by the following MD setting:
MD11450 $MN_SEARCH_RUN_MODE, bit 1 = 1
Program to be activated
In the default setting, the program _N_PROG_EVENT_SPF is activated from the directory
_N_CMA_DIR as ASUB after the block search by changing the last action block. If another
program is to be activated, then the name of this user program must be entered in the following
machine data:
Basic functions
MD11620 $MN_PROG_EVENT_NAME

The following channel-specific machine data are used to set whether the activated ASUP will
be processed without interruption although single-block processing is set or whether single-
block processing will be activated:
MD20106 $MC_PROG_EVENT_IGN_SINGLEBLOCK, bit 4 = <value>
<value> Meaning
0 Single-block processing is active.
1 Single-block processing is suppressed.
Behavior when the read-in disable is set

The channel-specific machine data is used to set whether the ASUP will be processed without
interruption although read-in disable (DB21, ... DBX6.1 = 1) is set, or whether the read-in
disable will be effective:
MD20107 $MC_PROG_EVENT_IGN_INHIBIT, Bit 4 = <value>
<value> Meaning
0 Read-in disable is active.
1 Read-in disable is suppressed.
Note
For more information on parameterizing MD11620, MD20108, and MD20107, see Section
"Parameterization (Page 70)."
Programming
The event by which the ASUP has been started is stored in the system variable
$P_PROG_EVENT. On automatic activation after a block search, $P_PROG_EVENT returns
the value "5."
Sequence
Sequence of automatic start of an ASUB after a block search
1. User: Activation of the block search type 2 or type 4 (block search with calculation to ...) via
the operator interface
2. Search for the target block with collection of auxiliary functions
3. Stop after "Search target found ⇒ display of alarm 10208 "Continue program with NC start"
4. User: NC start to execute the action block s⇒ DB21, ... DBX7.1 = 1 (NC start)
5. Execution of the action blocks
6. Last action block is activated ⇒ Automatic start of /_N_CMA_DIR/_N_PROG_EVENT_SPF
(default) as an ASUB.
Basic functions
7. Last ASUP block (REPOSA) is activated ⇒ DB21, ... DBX32.6 = 1 (last action block active)
8. Optional: Execution of user-specific requirements via PLC user program
9. Display of the alarm 10208 "Continue program with NC start"?
Note
With MD11450 $MN_SEARCH_RUN_MODE, Bit 0 == 1, alarm 10208 will only be output
after enabling by the PLC user program (DB21, ... DBX1.6 = 1 (PLC action ended)).
10.User: Continue program with NC start ⇒ DB21, ... DBX7.1 = 1 (NC start)
2.7.4 Cascaded block search
Functionality
The "Cascaded block search" function can be used to start another block search from the status
"Search target found". The cascading can be continued after each located search target as
often as you want and is applicable to the following block search functions:
● Type 1 block search without calculation
● Type 2 block search with calculation at contour
● Type 3 block search with calculation at block end point
Note
Another "cascaded block search" can be started from the stopped program execution only
if the search target has been found.
Activation
The "cascaded block search" is configured in the existing machine data:
MD11450 $MN_SEARCH_RUN_MODE
● The cascaded block search is enabled (i.e. several search targets can be specified)
with Bit 3 = 0 (FALSE).
● For compatibility reasons, the cascaded block search can be disabled with Bit 3 = 1 (TRUE).
By default, the cascaded block search is set with Bit 3 = 0.
Execution behavior
Search target found, restart block search

When the search target is reached, the program execution is stopped and the search target
displayed as current block. After each located search target, a new block search can be
repeated as often as you want.
Changing the search target specifications
Basic functions
You can change the search target specifications and block search function before every block
search start.
Example: Execution sequence with cascaded block search

● RESET
● Block search up to search target 1
● Block search up to search target 2 → "Cascaded block search"
● NC Start for output of the action blocks → Alarm 10208
● NC Start → Continue program execution

%ORFNVHDUFKDFWLYH
'%'%;
$FWLRQEORFNDFWLYH
'%'%;
/DVWDFWLRQEORFNDFWLYH
'%'%;
&KDQQHOVWDWXVUHVHW
'%'%;
'%'%;
Figure 2-2 Chronological order of interface signals
2.7.5 Examples for block search with calculation
Selection
From the following examples, select the type of block search that corresponds to your task.
Type 4 block search with calculation at block end point

Example with automatic tool change after block search with active tool management:
1. Set machine data:
MD11450 $MN_ SEARCH_RUN_MODE to 1
MD11602 $MN_ASUP_START_MASK Bit 0 = 1 (ASUP Start from stopped state)
2. Select ASUP "BLOCK_SEARCH_END" from the PLC via FB4 (see also Function Manual
"PLC and Basic Program", Section "Basic PLC program").
3. Load and select part program "WORKPIECE_1".
Basic functions
4. Block search to block end point, block number N220.

5. HMI signals "Search target found".
6. NC Start for output of action blocks.
7. With the PLC signal:
DB21... DB32.6 (last action block active)
the PLC starts ASUB "BLOCK_SEARCH_END" via FC9 (see also Function Manual "PLC
and Basic Program", Section "Basic PLC program").
8. After the end of the ASUP (can be evaluated, e.g. via M function M90 to be defined, see
example for block N1110), the PLC sets signal
DB21, ... DBX1.6 (PLC action complete).
Alternatively, NC/PLC interface signal:
DB21-DB30 DBB318 bit 0 (ASUP is stopped)
can be scanned.
As a result, Alarm 10208 is displayed, i.e. other actions can now be performed by the
operator.
9. Manual operator actions (JOG, JOG-REPOS, overstoring)
10.Continue part program with NC Start.
\

$SSURDFKPRYHPHQW 7RROFKDQJHSRLQW
7DUJHWEORFN1

$SSURDFKSRLQW

[
Figure 2-3 Approach motion for block search to block end point (target block N220)
Note
"Block search at contour" with target block N220 would generate an approach motion to the
tool change point (start point of the target block).
Type 2 block search with calculation at contour

Example with automatic tool change after block search with active tool management:
1. to 3. Same as example for Type 4 block search

4. Block search at contour, block number N260
5. to 10. Same as example for Type 4 block search
Basic functions

$SSURDFKPRYHPHQW 7RROFKDQJHSRLQW

$SSURDFKSRLQW

[
Figure 2-4 Approach motion for block search at contour (target block N260)
Note
"Block search to block end point" with target block N260 would result in Alarm 14040 (circle end
point error).
Part programs for Type 4 and Type 2

PROC WORKPIECE_1

; Main program
...
;Machine contour section 1 with "CUTTER_1"tool
...
N100 G0 G40 X200 Y200 ; Deselect radius compensation
N110 Z100 D0 ; Deselect length correction
;End of contour section 1
;
;Machine contour section 2 with "CUTTER_2"tool
N200 T="CUTTER_2" ; Preselect tool
N210 WZW ; Call tool change routine
N220 G0 X170 Y30 Z10 S3000 M3 D1 ; Approach block for contour section 2
N230 Z-5 ; Infeed
N240 G1 G64 G42 F500 X150 Y50 ; Start point of contour
N250 Y150
N260 G2 J50 X100 Y200
N270 G1 X50
N280 Y50
N290 X150
N300 G0 G40 G60 X170 Y30 ; Deselect radius compensation
N310 Z100 D0 ; Deselect length correction
End of contour section 2
...
M30
Basic functions

PROC WZW
;Tool change routine
N500 DEF INT TNR_AKTIV ; Variable for active T number
N510 DEF INT TNR_VORWAHL ; Variable for preselected T number
N520 TNR_AKTIV = $TC_MPP6[9998,1] ; Read T number of active tool
N530 GETSELT(TNR_VORWAHL) ; Read T number of preselected tool
;
;Execute tool change only if tool is not yet active
N540 IF TNR_AKTIV == TNR_VORWAHL GOTOF ENDE
N550 G0 G40 G60 G90 SUPA X450 Y300 Z300 D0 ; Approach tool change point
N560 M6 ; Execute tool change
;
END: M17
PROC BLOCK_SEARCH_END SAVE
;ASUP for calling the tool change routine after block search
N1000 DEF INT TNR_AKTIV ; Variable for active T number
N1020 DEF INT TNR_SUCHLAUF ; Variable for T number determined in
; block search
N1030 TNR_AKTIV = $TC_MPP6[9998,1] ; Read T number of active tool
N1040 TNR_SUCHLAUF = $P_TOOLNO ; Read T number determined by block
search
N1060 IF TNR_AKTIV ==TNR_SUCHLAUF GOTOF ASUP_ENDE
N1070 T = $TC_TP2[TNR_SUCHLAUF] ; T selection by tool name
N1080 WZW ; Call tool change routine
N1090 IF TNR_VORWAHL == TNR_SUCHLAUF GOTOF ASUP_ENDE
N1100 T = $TC_TP2[TNR_VORWAHL] ; Restore T preselection by tool name
ASUP_END:
N1110 M90 ; Feedback to PLC
N1120 REPOSA ; ASUP end
2.7.6 Constraints
Behavior with compressor function active

If the target block for block search type 2 or type 4 (block search with calculation to ...) is in a
program section in which a compressor function (COMP...) is active, positions are approached
on the path calculated by the compressor on repositioning. These positions must precisely
match the positions on the path programmed in the part program.
If programmed blocks are eliminated from the part program during compression, these blocks
will not be found as the target block in the block search. Alarm 15370 "Search target for block
search not found" is output.
Basic functions
2.8 Block search Type 5 (SERUPRO)
2.8.1 Description of the function

Block search type 5, block search with calculation in the "Program test" mode
(SERUPRO, "Search-Run by Program test") enables a cross-channel block search with
calculation at a selectable interruption point. Taking into account existing program coordination
commands, all the status data required to continue the program in the interrupted channels is
determined during SERUPRO and then the NC and PLC set to a state permitting the program
continuation.
Before repositioning with subsequent continuation of the program execution, all the output
states that may still be required can be automatically generated via a user-specific ASUP.
Channels
In combination with the HMI, SERUPRO is provided for the following channels:
● For the current SERUPRO channel only (1)
● For all channels with the same workpiece name as the SERUPRO channel (2)
● For all channels with the same mode group as the SERUPRO channel (3)
● For all channels of the NCU (4)
The scope of channels for SERUPRO is selected by means of configuration file maschine.ini,
in Section [BlockSearch]:
Section [BlockSearch] Enable block search function for HMI and select block search configuration
SeruproEnabled=1 ;SERUPRO softkey available for HMI. Default value is (1)
SeruproConfig=1 ;Number (1) to (4) of above indicated channel grouping. Default value is (1)
All other channels started with SERUPRO are operated in "Self-Acting SERUPRO" mode. Only
the channel in which a target block has been selected can be started with a block search in
SERUPRO mode.
Activation
SERUPRO is activated via the HMI. SERUPRO is operated using the "Prog.Test Contour"
softkey.
SERUPRO uses REPOS to approach the target block.
Basic functions
Chronological sequence of SERUPRO

1. Via HMI, softkey "Pog. test contour" and the search target are operated.
2. The NC now automatically starts the selected program in "Program test" mode.
– In this mode, axes are not traversed.
– Auxiliary functions $A_OUT and the direct PLC IO are output.
– The auxiliary functions of the target block are not output.
3. The NC stops at the beginning of the target block, deselects the program test internally, and
displays the stop condition "Wait: Search target found".
4. If the user-specific ASUP "PROG_EVENT.SPF" is available, it is started automatically.
5. Repositioning is performed with the next NC start (REPOS).
The REPOS operation is performed via a system ASUP and can be extended using the
"Editable ASUP" function.
Boundary conditions for block search SERUPRO

The SERUPRO function may only be activated in "AUTOMATIC" mode and may only be
aborted in program state (channel state RESET).
If in normal mode only the PLC starts commonly several channels, then this can be simulated
by SERUPRO in each channel.
With machine data setting:
MD10708 $MN_SERUPRO_MASK, bit 1 = 0,
alarm 16942: "Channel %1 Start program command action %2<ALNX> not possible"
aborts the simulation if part program command START is used.
Machine data:
MD10707 $MN_PROG_TEST_MASK
allows shutdown in the stopped state and has no effect on the SERUPRO operation. The
default setting allows program testing to be deactivated only in the RESET state.
Note
After program testing has been deactivated, a REPOS operation is initiated that is subject to the
same restrictions as a SERUPRO approach operation. Any adverse effects can be inhibited
using an ASUP.
Controlling SERUPRO behavior

For the functions listed below as an example, the SERUPRO behavior can be set specifically
for the NC:
● Programmed stop (M0)
● Program coordination command START
● Group SERUPRO
Basic functions
● Cross-channel exiting of SERUPRO

● Override
MD10708 $MN_SERUPRO_MASK = <behavior with SERUPRO>
Channel-specific basic settings for SERUPRO

The channel-specific basic settings are normally specified with the following machine data after
a part program start:
MD20112 $MC_START_MODE_MASK= basic settings>
You can specify your own basic settings for SERUPRO which replace the basic settings from
MD20112:
MD22620 $MN_START_MODE_MASK_PRT = <SERUPRO basic settings>
The SERUPRO basic settings must be explicitly released via:
MD22621 $MC_ENABLE_START_MODE_MASK_PRT = 1
NC/PLC interface signal "Block search via program test is active"

The block search via program test is displayed using the NC/PLC interface signal:
DB21, ... DBX318.1 == 1
The interface signal is set from the start of the block search until the target block is inserted into
the main run.
For user-defined ASUP after the SERUPRO operation

Note
If the machine manufacturer decides to start an ASUP after the SERUPRO operation as
described in point 7, the following must be observed:
Stopped status acc. to point 6:

Machine data:
MD11602 $MN_ASUP_START_MASK
and
MD11604 $MN_ASUP_START_PRIO_LEVEL
allow the NC to start the ASUP from the stopped status automatically via the FC9 block.
Acknowledgment of FC9 only after completion of REPOS block:

The ASUP can only be signaled as complete from the FC9 block with "ASUP Done" if the
REPOS block has also been completed.
Deselection of assigned REPOS operation after point 8:

The start of the ASUP deselects the assigned REPOS operation!
Therefore, the ASUP should be ended with REPOSA in order to retain the REPOS operation.
Basic functions
Deleting an unwanted REPOS operation:

The unwanted REPOS operation is deleted by completing the ASUP with M17 or RET.
Special handling of ASUP:

As a basic rule, an ASUP that ends with REPOS and is started from stopped state receives
special treatment.
The ASUP stops automatically before the REPOS block and indicates this via:
DB21, ... DBX318.0 (ASUP is stopped)
Automatic ASUP start

The ASUP in path:
/_N_CMA_DIR/_N_PROG_EVENT_SPF
is started automatically in SERUPRO approach with machine data:
MD11450 $MN_SEARCH_RUN_MODE, bit 1 = 1
according to the following sequence:
1. The SERUPRO operation has been performed completely.
2. The user presses "NC start".
3. The ASUP is started.
4. The NC stops automatically before the REPOS part program command and the
message "Press NC start to continue the program" appears.
5. The user presses "NC start" again.
6. The NC executes the repositioning motion and continues the part program at the target
block.
Note
The automatic ASUP start with MD11450 requires Starts to continue the program.
The procedure is in this respect similar to other block search types.
2.8.2 Repositioning to the contour (REPOS)
The "Reposition to the contour" (REPOS) function can be used to continue an interrupted
machining at the interrupted location. Unlike REPOS, SERUPRO permits the "refetching" or
"repetition" of a program section. For this purpose, once SERUPRO has found the target block,
the contour is positioned at the location selected with REPOS mode and the machining
continued.
Basic functions
SERUPRO: Set REPOS response

The REPOS behavior, i.e. the behavior in the repositioning block, is set with the following
machine data:
MD11470 $MN_REPOS_MODE_MASK = <REPOS mode>
<REPOS mode>
Bit Value Meaning
0 0 An interrupted delay time is repeated
1 An interrupted delay time is continued
1 - Reserved
2 0 DB31, ... DBX10.0 (REPOS delay) not considered in the repositioning deceleration
block.
1 DB31, ... DBX10.0 (REPOS delay) considered in the repositioning deceleration
block.
3 0 SERUPRO: Only path axes traverse in the repositioning block
1 SERUPRO: Path and positioning axes traverse concurrently in the repositioning
block
4 0 REPOS: Only path axes traverse in the repositioning block
1 REPOS: Path and positioning axes traverse concurrently in the repositioning block
5 0 During the interruption, changed feedrates and spindle speeds act only after the
first part program block following the interruption location
1 Modified feedrates and spindle speeds during the interruption are valid immedi‐
ately from the interruption point onward, i.e. they are already valid in the residual
block and are given priority. This behavior relates to every REPOS operation.
6 0 SERUPRO: In the repositioning block, neutral axes and positioning spindles tra‐
verse as path axes.
1 SERUPRO: In the repositioning block, neutral axes and positioning spindles tra‐
verse as command axes.
Neutral axes and positioning spindles are repositioned after SERUPRO.
For neutral axes, where it is not permissible to reposition them, the REPOS delay
must be set: DB31, ... DBX10.0 = 1 (REPOS delay)
7 0 The REPOS delay is not enabled.
1 The REPOS delay is enabled.
Axes with active REPOS delay (DB31, ... DBX10.0 == 1), which are neither ge‐
ometry nor orientation axes, are not traversed when repositioning.
CAUTION
Risk of collision
MD11470 $MN_REPOS_MODE_MASK, Bit 3 or Bit 4 = 1
The user alone is responsible for ensuring that the concurrent traversal of the axes in the
repositioning block does not cause any collision on the machine.
Repositioning with controlled REPOS

The REPOS mode can be specified for the path axes via the NC/PLC interface:
Basic functions
DB21, ... DBX31.0 - 2 (REPOS mode)

The REPOS mode is programmed in the NC program, and defines the approach behavior (see
Section "Repositioning with controlled REPOS (Page 146)").
The REPOS behavior of individual axes can also be controlled via NC/PLC interface signals,
and must be enabled using machine data:
MD11470 $MN_REPOS_MODE_MASK BIT 2=1.
Path axes cannot be influenced individually. For all other axes that are not geometry axes,
REPOS of individual axes can be prevented temporarily and also delayed. NC/PLC interface
signals can be used to subsequently re-enable or to continue blocking individual channel axes
that REPOS would like to traverse.
DANGER
Risk of collision
Signal DB31, ... DBX2.2 (delete distance-to-go) produces the following dangerous behavior
when function "Prevent repositioning of individual axes" is selected:
MD11470 $MN_REPOS_MODE_MASK.bit 2 == 1
As long as an axis is programmed incrementally after the interruption, the NC approaches
different positions than those approached with no interruption.
See the example below: Axis is programmed incrementally
Basic functions
Example: Rotary axis A is programmed incrementally

Rotary axis A is the fourth machine axis.
● Rotary axis A is positioned at 11° before the REPOS operation.
In the interruption block, i.e. in the target block of SERUPRO, rotary axis A should be moved
to 27°.
Any number of blocks later, rotary axis A is moved incrementally through 5°:
N1010 POS[A]=IC(5) FA[A]=1000
When interface signal DB34 DBX10.0 = 1 is set (REPOS delay), rotary axis A is not moved
in the REPOS operation, and is moved with N1010 to 32°. The user may have to consciously
acknowledge the movement from 11° to 27°.
DANGER
Risk of collision
As, after the interruption, the axis is incrementally programmed, it moves to 16° instead of
32°.
● Starting axes individually

The REPOS behavior for SERUPRO approach with several axes is selected with:
MD11470 $MN_REPOS_MODE_MASK.BIT 3 = 1
The NC commences SERUPRO approach with a block that moves all positioning axes to
the programmed end and the path axis to the target block.
The user starts the individual axes by selecting the appropriate feedrate enables. The target
block is then executed.
● Repositioning positioning axes in the repositioning block
Positioning axes are not repositioned in the residual block but rather in the repositioning
block, and their effect is not limited to the block search via program test on SERUPRO
approach.
MD11470 $MN_REPOS_MODE_MASK.bit 3 = 1: for block search via program test
(SERUPRO)
MD11470 $MN_REPOS_MODE_MASK.bit 4 = 1: for each REPOS
Note
If neither bit 3 nor bit 4 is set, in that this phase non-path axes are repositioned in the residual
block.
Delayed approach of axis with REPOS offset

If the axis-specific interface signal DB31, ... DBX10.0 (REPOS delay) is set with the positive
edge of DB21, ... DBX31.4 (REPOS mode change), the REPOS offset for this axis is only
traversed through when programmed the next time.
Basic functions
Whether this axis is currently subject to a REPOS offset can be read via synchronized actions
with $AA_REPOS_DELAY.
CAUTION
Risk of collision
DB31, ... DBX10.0 (REPOS delay) have no effect on machine axes, which form a path.
Whether an axis is a path axis can be determined using DB31, ... DBX76.4 (path axis).
Acceptance timing of REPOS SIGNALS

With the positive edge of DB21, ... DBX31.4 (REPOS mode change), the following REPOS
signals are transferred into the NC:
● Channel-specific: DB21, ... DBX31.0 - 2 (REPOS mode)
● Axis-specific: DB31, ... DBX10.0 (REPOS delay)
The level of the REPOS signals refers to the actual main run block. There are two different
cases:
1. One repositioning block of a currently active REPOS operation is contained in the main run.
The active REPOS operation is canceled, restarted and the REPOS offsets are influenced
by the REPOS signals mentioned above:
2. No repositioning block of a currently active REPOS operation is contained in the main run.
Each future REPOS operation wanting to reapproach the current main program block is
influenced by the REPOS signals mentioned above.
Note
In a running ASUP, DB21, ... DBX31.4 (REPOS mode change) does not act on the final
REPOS, unless the signal is inadvertently set at the instant in time that the REPOS blocks are
being executed.
In the 1st case, the signal is allowed only in the stopped state.
Response to RESET:
● The NC has already acknowledged the PLC signal:
DB21, ... DBX31.4 == 1 (REPOS mode change) AND
DB21, ... DBX319.0 == 1 (REPOS mode change acknowledgment)
If, in this situation, a channel reset occurs, then the active REPOS mode is cleared:
DB21, ... DBX319.1 - 3 = 0 (active REPOS mode)
● The NC has still not acknowledged the PLC signal:
DB21, ... DBX31.4 == 1 (REPOS mode change) AND
DB21, ... DBX319.0 == 0 (REPOS mode change acknowledgment)
If, in this situation, a channel reset occurs, then acknowledgment of the REPOS mode
change and the active REPOS mode are cleared:
DB21, ... DBX319.0 = 0 (REPOS mode change acknowledgment)
DB21, ... DBX319.1 - 3 = 0 (active REPOS mode)
Basic functions
Controlling SERUPRO approach with NC/PLC interface signals

The SERUPRO approach can be used with:DB21, ... DBX31.4 (REPOS mode change) and the
associated signals in the following phases:
● From "Search target found" to "Start SERUPRO ASUP"
● From "SERUPO-ASUP stops automatically before REPOS" to "Target block is executed"
While the SERUPRO ASUP is being executed, e.g. in the program section before the REPOS
operation, the interface signal does not affect the SERUPRO positioning
REPOS operations with NC/PLC interface signals

Control REPOS mit NC/PLC interface signals
REPOS offsets can be influenced with the following NC/PLC interface signals:
● DB21, ... DBX31.0 - 2 (REPOS mode)
● DB21, ... DBX31.4 (REPOS mode change)
● DB31, ... DBX10.0 (REPOS delay)
REPOS acknowledgment signals

The following NC/PLC interface signals can be used to acknowledge from the NC, functions
that control the REPOS response via PLC:
● DB21, ... DBX319.0 (REPOS mode change acknowledgment)
● DB21, ... DBX319.1 - 3 (active REPOS mode)
● DB21, ... DBX319.5 (REPOS acknowledgment delay)
● DB31, ... DBX70.0 (REPOS offset)
● DB31, ... DBX70.1 (REPOS offset valid)
● DB31, ... DBX70.2 (REPOS delay acknowledgment)
● DB31, ... DBX76.4 (path axis)
For further information, see "REPOS offset in the interface"
REPOS acknowledgment operations

If the NC recognizes a REPOS mode change (DB21, ... DBX31.4 == 1), then this is
acknowledged by the PLC with DB21, ... DBX319.0 = 1.
Note
If the NC has not yet acknowledged interface signal DB21, ... DBX31.4 (REPOS MODE
CHANGE) with interface signal DB21, ... DBX319.0 (REPOS mode change acknowledgment)
, then a channel reset in this situation causes the program to be canceled, and the REPOS,
which is to be used to control the REPOS mode, is not executed.
Basic functions
A REPOS mode issued from the PLC is acknowledged by the NC using the following interface
signals:
● DB21, ... DBX319.1 - 3 (active REPOS mode)
● DB31, ... DBX70.2 (REPOS delay acknowledgment)
Example
● Instant in time ②: An NC program in block N20 is stopped with an NC stop. All axes are
braked along their parameterized braking ramps to standstill.
● Instant in time ③: After the PLC user program has set the "REPOS mode", the NC accepts
the REPOS mode with the 0/1 edge of "REPOS mode change".
● Instant in time ④: "REPOS mode change acknowledgment" remains set until the ASUP is
initiated.
● Instant in time ⑤: The REPOS operation begins in the ASUP.
● Instant in time ⑥: The residual block of the ASUP is reloaded.
&RPPDQGZLWK$683LVEHJXQ
5HDSSURDFKPRYHPHQWRI
5(326LVHQGHG
7KHUHPDLQGHUVHWEHJLQV
1
1 ,QLWLDWH$683 1
3UHVHOHFW501%/
6WRSRIWKHSDUWSURJUDP
6WRSRIWKHSDUWSURJUDP 7KHUHPDLQGHUVHWHQGV
5(3263$7+02'(

5(32602'(('*(
5(32602'(('*($&.1
5HSRV3DWK0RGH4XLWW

W
Figure 2-5 REPOS sequence in part program with timed acknowledgment signals from NC
NC sets acknowledgment again

Phase with REPOSPATHMODE still active (residual block of the program stopped at → Time
(2) is not yet completely executed).
Basic functions
As soon as the REPOS repositioning motion of the ASUP is executed, the NC sets the "Repos
Path Mode Ackn" again (→ Time (5)). If no REPOSPATHMODE has been preselected via an
NC/PLC interface signal, the programmed REPOS mode is displayed.
"Repos Path Mode Ackn" is canceled when the residual block is activated (→ Time (6)).
The part program block N30 following the block at → Time (2) is resumed.
Interface signal:
DB31, ... DBX70.2 (REPOS delay acknowledgment) is analogously defined.
DB31, ... DBX70.1 (REPOS offset valid) = 1, if:
DB21, ... DBX319.1-319.3 (active REPOS mode) = 4 (RMNBL).
Valid REPOS offset

At the end of the SERUPRO operation, the user can read out the REPOS offset via the axis/
spindle NC/PLC interface signal (NC→PLC):
DB31, ... DBX70.0 (REPOS offset).
The effects of this signal on the relevant axis are as follows:
Value 0: No REPOS offset is applied.

Value 1: REPOS offset is applied.
Range of validity
Interface signal:
DB31, ... DBX70.0 (REPOS offset)
is supplied at the end of the SERUPRO operation.
The REPOS offset is invalidated at the start of a SERUPRO ASUP or the automatic ASUP start.
Updating the REPOS offset in the range of validity

Between the SERUPRO end and SERUPRO start, the axis can be moved in JOG mode with
a mode change.
In JOG mode, the user manually moves the axis over the REPOS offset path in order to set
interface signal:
DB31, ... DBX70.0 (REPOS offset) to the value 0.
Within the range of validity, the axis can also be traversed using FC18, whereby the interface
signal
DB31, ... DBX70.0 (REPOS offset) is continuously updated.
Displaying the range of validity

The range of validity of the REPOS offset is indicated with interface signal:
DB31, ... DBX70.1 (REPOS offset valid)
Basic functions
It is indicated whether the REPOS offset calculation was valid or invalid:
Value 0: The REPOS offset of this axis is calculated correctly.

Value 1: The REPOS offset of this axis cannot be calculated, as the REPOS has not yet
occurred, e.g. it is at the end of the ASUP, or no REPOS is active.
REPOS offset after an axis interchange

The group signal:DB21, ... DBX319.5 (REPOS delay) can be used to determine whether a valid
REPOS offset has taken place:
Value 0: All axes currently controlled by this channel have either no REPOS offset or their
REPOS offsets are invalid.
Value 1: Miscellaneous.
REPOS offset with synchronized synchronous spindle coupling

When repositioning with SERUPRO, processing continues at the point of interruption. If a
synchronous spindle coupling was already synchronized, there is no REPOS offset of the
following spindle and no synchronization path is present. The synchronization signals remain
set.
Search target found on block change

The axis-specific NC/PLC interface signal DB31, ... DBX76.4 (path axis) is 1 if the axis is part
of the path grouping.
This signal shows the status of the current block to be executed during block change.
Subsequent status changes are ignored.
If the SERUPRO operation is ended with "Search target found", DB31, ... DBX76.4 (path axis)
refers to the target block.
2.8.2.1 Repositioning with controlled REPOS

Once SERUPRO has been used to find the target block, prior to continuing the interrupted
program, a REPOS operation for repositioning the contour is performed. The REPOS mode
"Reposition at the block start point of the target block" (RMBBL) is active by default. The
REPOS mode can be defined user-specific via the NC/PLC interface:
DB21, ... DBX31.0 - .2 (REPOS mode)
Further information
REPOS mode: Repositioning to the next point on the path (RMNBL)

in the RMNBL REPOS mode, positioning is made for the REPOS start position from the next
nearest contour point.
Basic functions
Example
The program is interrupted at any point in the block N110. The axes were then traversed to
position (A), e.g. manually. Once SERUPRO has found target block N110, the REPOS
operation with REPOS mode RMNBL is performed. With regard to the REPOS start position (A),
point (B) is the next nearest point of the contour. The REPOS operation is completed when
point (B) is reached. The programmed contour of the interrupted program is traversed again
starting at point (B).
,QWHUUXSWLRQSRLQW1
%
1 1
Specifying the REPOS mode via the NC/PLC interface

The REPOS mode can be specified via the following NC/PLC interface signal:
DB21, ... DBX31.0 - .2 (REPOS mode)
Note
RMNBL is a general REPOS extension and it is not restricted to SERUPRO.
RMIBL and RMBBL behavior identically for SERUPRO.
DB21, ... DBX31.0 - .2 (REPOS mode) affects only the traversing motion of the path axes.
The behavior of the other axis can be changed individually using interface signal DB31, ...
DBX10.0 (REPOSDELAY). The REPOS offset is not applied immediately, but only when it is
next programmed.
For further information on the programming of the repositioning point, see:
Further information
2.8.3 Accelerate block search
Machine data settings

The speed of execution of the SERUPRO operation can be influenced via the following
machine data.
Basic functions
MD22600 $MC_SERUPRO_SPEED_MODE = <value>
<Value> Meaning
0 Program test with block search velocity / dry run feedrate:
● Axes: MD22601 $MC_SERUPRO_SPEED_FACTOR * dry run feedrate
● Spindles: MD22601 $MC_SERUPRO_SPEED_FACTOR * programmed speed
Dynamic limitations of axes / spindles are not considered.
1 Program test with programmed velocity:
● Axes: Dry run feedrate
● Spindles: Programmed speed
Dynamic limitations of axes / spindles are considered.
2 Program test with dry run feedrate
Under program test, traversing is performed with the programmed velocity / speed.
Dynamic limitations of axes / spindles are considered.
3 Program test with block search velocity
Under program test, traversing is performed with the following velocity:
● Axes: MD22601 $MC_SERUPRO_SPEED_FACTOR * programmed feedrate
● Spindles: MD22601 $MC_SERUPRO_SPEED_FACTOR * programmed speed.
Dynamic limitations of axes / spindles are not considered.
Note
When revolutional feedrate is active (e.g. G95), the programmed feedrate is not multiplied by
MD22601 $MC_SERUPRO_SPEED_FACTOR but only the programmed spindle speed.
This results, here too, in an increase in the effective path velocity by MD22601 $MC_SER‐
UPRO_SPEED_FACTOR.
Main axes
MD22600 $MC_SERUPRO_SPEED_MODE acts on the following main run axes with
SERUPRO:
● PLC axes
● Command axes
● Positioning axes
● Reciprocating axes
Basic functions
NOTICE
Actions of synchronized action may not be executed with SERUPRO
Because during SERUPRO other actual values (e.g. axis positions) are generated internally
that are different from those in normal program execution, with SERUPRO, conditions of
synchronized actions that check the actual values (e.g. axis positions) are no longer
recognized as true (TRUE) and that the action part of the synchronized action is therefore not
executed.
Revolutional feedrate
Effects of MD22601 $MC_SERUPRO_SPEED_FACTOR during DryRun:
● Switchover of G95/G96/G961/G97/G971 to G94
● Tapping and thread cutting: Normal dry run velocity.
Tapping without compensating chuck

● With "tapping without compensating chuck" (G331/G332), the spindle is interpolated under
position control in a path grouping. The drilling depth (linear axis), the thread pitch, and
speed (spindle) are defined.
During dry run, the velocity of the linear axis is specified, the speed remains constant, and
the pitch is adjusted.
After SERUPRO, a position for the spindle results that is deviates from normal mode
because the spindle has revolved fewer times in SERUPRO.
2.8.4 SERUPRO ASUB
SERUPRO ASUP special points

Special points should be noted for SERUPRO ASUP with regard to:
● Reference point approach: Referencing via part program G74
● Tool management: Tool change and magazine data
● Spindle ramp-up: On starting a SERUPRO ASUP
G74 reference point approach

If command G74 (reference point approach) is programmed between the program start and the
search target, this will be ignored by the NC.
SERUPRO approach does not take this G74 command into account!
Tool management
If tool management is active, the following setting is recommended:
Basic functions
MD20310 $MC_TOOL_MANAGEMENT_MASK Bit 20 = 0

The tool management command generated during the SERUPRO operation is thus not output
to the PLC!
The tool management command has the following effect:
● The NC acknowledges the commands automatically.
● No magazine data is changed.
● Tool data is not changed.
Exception:
The tool enabled during the test mode can assume 'active' state. In this way, the wrong tool
may be on the spindle after the SERUPRO operation.
Remedy:
The user starts a SERUPRO ASUP that is actually traversed. Prior to the start, the user can
start an ASUP that loads the correct tool.
SERUPRO operation: Functionality: In sequence steps 2. to 6.
SERUPRO ASUP: Functionality: The sequence of step 7.
In addition, machine data setting MD20310 $MC_TOOL_MANAGEMENT_MASK Bit 11 = 1 is
required because the ASUP may have to repeat a T selection.
Systems with tool management and auxiliary spindle are not supported by SERUPRO!
Example
Tool change subprogram

PROC L6 ; Tool change routine
N500 DEF INT TNR_AKTUELL ; Variable for active T number
; Determine current tool

N520 STOPRE ; In program testing
N530 IF $P_ISTEST ; From the program context
N540 TNR_AKTUELL = $P_TOOLNO ; The "current" tool is read
N550 ELSE ; Otherwise, the tool of the spindle is read out.
N560 TNR_AKTUELL = $TC_MPP6[9998,1] ; Read tool T number on the spindle
N570 ENDIF
N580 GETSELT(TNR_VORWAHL) ; Read T number of the preselected tool of the master spindle
; Execute tool change only if tool is not yet current
N590 IF TNR_AKTUELL <> TNR_VORWAHL ; Approach tool change point
N600 G0 G40 G60 G90 SUPA X450 Y300
Z300 D0
N620 ENDIF
N630 M17
Basic functions
ASUP for calling the tool change routine after type 5 block search

PROC ASUPWZV2
N1000 DEF INT TNR_SPINDEL ; Variable for active T number
N1020 DEF INT TNR_SUCHLAUF ; Variable for T number determined in block search
N1030 TNR_SPINDEL = $TC_MPP6[9998,1] ; Read tool T number on the spindle
N1040 TNR_SUCHLAUF = $P_TOOLNO ; Read T number determined by block search,
i.e. this tool determines the
current tool offset
N1060 IF TNR_SPINDEL ==TNR_SUCHLAUF GOTOF AS-
UP_ENDE1
N1070 T = $TC_TP2[TNR_SUCHLAUF] ; T selection by tool name
N1080 L6 ; Call tool change routine
N1085 ASUP_ENDE1:
N1090 IF TNR_VORWAHL == TNR_SUCHLAUF GOTOF AS-
UP_ENDE
N1100 T = $TC_TP2[TNR_VORWAHL] ; Restore T preselection by tool name
N1110 ASUP_ENDE:
N1110 M90 ; Feedback to PLC
N1120 REPOSA ; ASUP end
In both of the programs PROC L6 and PROC ASUPWZV2, the tool change is programmed with
M206 instead of M6.
ASUP "ASUPWZV2" uses different system variables to detect the progress of the program
($P_TOOLNO) and represent the current status of the machine ($TC_MPP6[9998,1] ).
Spindle ramp-up
When the SERUPRO ASUP is started, the spindle is not accelerated to the speed specified in
the program because the SERUPRO ASUP is intended to move the new tool into the correct
position at the workpiece after the tool change.
A spindle ramp-up is performed with SERUPRO ASUP as follows:
● SERUPRO operation has finished completely.
● The user starts the SERUPRO ASUP via function block FC 9
in order to ramp up the spindle.
● The start after M0 in the ASUP does not change the spindle status.
● SERUPRO ASUP automatically stops before the REPOS part program block.
Basic functions
● The user presses START.

● The spindle accelerates to the target block state if the spindle was not programmed
differently in the ASUP.
Note
Modifications for REPOS of spindles:
The transitions of speed control mode and positioning mode must be taken into
consideration in the event of modifications in SERUPRO approach and spindle functionality.
For further information on the operating mode switchover of spindles, see Section "Mode
types and mode type change (Page 35)".
2.8.5 Selfacting SERUPRO
Self-acting SERUPRO
The channel-specific function "Self-acting SERUPRO" allows a SERUPRO sequence without
having to previously define a search target in a program of the associated SERUPRO channels.
A special channel, the "serurpoMasterChan", can also be defined for each "Self-acting
SERUPRO". A search target can be defined in this channel.
The "Self-acting SERUPRO" function supports the SERUPRO cross-channel block search.
Function
The "Self-acting SERUPRO" operation cannot be used to find a search target. If the search
target is not reached, then no channel is stopped. However, in certain situations the channel is
temporarily stopped. Generally, the channel waits for another channel. Examples are: Wait
marks, couplings or axis interchange.
The wait phase occurs:

During this wait phase, the NC checks the "seruproMasterChan" channel whether it has
reached a search target. The wait phase is exited when a search target is not reached.
If the search target is reached,
the SERUPRO operation is also ended in the channel. The "seruproMasterChan" channel must
have been started in normal SERUPRO mode.
No wait phase occurs:

"Self-acting SERUPRO" is ended by M30 of the part program.
The channel is now in the Reset state again.
There is no SERUPRO approach.
Basic functions
Starting a group of channels

If a group of channels is only started with "Self-acting SERUPRO", then all channels are ended
with "RESET".
Exception:
A channel waits for a partner channel that has not been started at all.
A cross-channel block search can be carried out as follows:
● Via the HMI, the user selects the channels that must work together (channel group).
● The user selects a particularly important channel from the channel group for which a search
target is to be explicitly selected (target channel).
● The HMI will then start SERUPRO on the target channel and "Self-acting SERUPRO" in the
remaining channels of the channel group.
The operation is complete when every relevant channel has deleted "seruproActive".
"Self-acting SERUPRO" accepts no master channel on another NCU.
Activation
"Self-acting SERUPRO" is activated via the HMI as a block search start for the Type 5 block
search for target channel "seruproMasterChan".
A search target is not specified for the dependent channels started from the target channel.
2.8.6 Locking a program section for "Continue machining at the contour"
Programmed interrupt pointer

If because of manufacturing and/or process-related reasons, "Continue machining at the
contour" may not be possible within a certain program section at a program abort, this program
section can be locked for the target block of a block search.
If after a program abort there is a block search for the interruption point within the locked
program section for "Continue machining at the contour", the last executable block (main run
block) before the start of the locked section is used by the control as target block (hold block).
Programming
Syntax
IPTRLOCK()
Functionality
Marks the beginning of the program section as of which "Continue machining at the contour" is
locked. The next executable block (main run block) in which IPTRLOCK becomes active is now
used as target block for a block search with "Continue machining at the interruption point", until
the release with IPTRUNLOCK. This block is referred to as the hold block in the following.
Basic functions
Syntax
IPTRUNLOCK()
Marks the end of the program section locked for "Continue machining at the contour". As of the
next executable block (main run block) in which IPTRLOCK becomes active, the current block
is used again as target block for a block search with "Continue machining at the interruption
point". This block is referred to as the release block in the following.
Example

...
N010 IPTRLOCK() ; Locked area: Start
N020 R1=R1+1
N030 G4 F1 ; Hold block
... ; Locked area
N200 IPTRUNLOCK() ; Locked area: End
N220 R1=R1+1
N230 G4 F1 ; Release block
...
● IPTRLOCK acts within a program (*.MPF, *.SPF) at the most up to the end of the program
(M30, M17, RET). IPTRUNLOCK implicitly becomes active at the end of the program.
● Multiple programming of IPTRLOCK within a program does not have a cumulative effect.
With the first programming of IPTRUNLOCK within the program or when the end of the
program is reached, all previous IPTRLOCK calls are terminated.
● If there is a subprogram call within a locked area, "Continue machining at the contour" is also
locked for this and all following subprogram levels. The lock also cannot be cancelled within
the called subprogram through explicit programming of IPTRUNLOCK.
Example: Nesting of locked program sections in two program levels

With the activation of the "Continue machining at the contour" lock in PROG_1, "Continue
machining at the contour" is also locked for PROG_2 and all following program levels.

PROC PROG_1 ; Program 1
...
N010 IPTRLOCK()
N020 R1=R1+1
... ; Locked area: Start
N040 PROG_2 ; Locked area
... ; Locked area: End
N050 IPTRUNLOCK()
Basic functions

N060 R2=R2+2
...

N210 IPTRLOCK() ; Ineffective due to program 1
...
N250 IPTRUNLOCK() ; Ineffective due to program 1
...
N280 RET ; Ineffective due to program 1
Example 3: Multiple programming of IPTRLOCK

...
N010 IPTRLOCK()
N020 R1=R1+1
... ; Locked area: Start
N150 IPTRLOCK() ; Locked area
... ; Locked area
N250 IPTRLOCK() ; Locked area
... ; Locked area: End
N360 IPTRUNLOCK()
N370 R2=R2+2
...
System variable
The status of the current block can be determined via the system variable $P_IPTRLOCK:
$P_IPTRLOCK Meaning
FALSE The current block is not within a program section locked for "Continue machining
at the contour"
TRUE The current block is within a program section locked for "Continue machining at the
contour"
Automatic function-specific "Continue machining at the contour" lock

For various couplings, the activation/deactivation of the "Continue machining at the contour"
lock can be performed automatically channel-specifically with the activation/deactivation of the
coupling:
Basic functions
MD22680 $MC_AUTO_IPTR_LOCK, bit x
Bit Val‐ Meaning

ue
0 Electronic gear ( EGON / EGOF)
1 Automatic "Continue machining at the contour" lock is active
0 Automatic "Continue machining at the contour" lock is not active
1 Axial master value coupling (LEADON / LEADOF)
1 Automatic "Continue machining at the contour" lock is active
0 Automatic "Continue machining at the contour" lock is not active
This program section begins with the last executable block before the activation and ends with
the deactivation.
The automatic interrupt pointer is not active for couplings that were activated or deactivated via
synchronized actions.
Example: Automatically declaring axial master value coupling as search-suppressed:

N100 G0 X100
N200 EGON(Y,"NOC",X,1,1) ; Search-suppressed program section starts.
N300 LEADON(A,B,1)
...
N400 EGOFS(Y)
...
N500 LEADOF(A,B) ; Search-suppressed program section ends.
N600 G0 X200
A program abort within search-suppressed program section (N200 - N500) always provides the
interrupt pointer with N100.
NOTICE
Unwanted state caused by function overlappings
If there is an overlap of the "Programmable interrupt pointer" and "Automatic interrupt pointer"
functions via machine data, the NC selects the largest possible search-suppressed area.
A program may need a coupling for almost all of the runtime. In this case, the automatic
interrupt pointer would always point to the start of the program and the SERUPRO function
would in fact be useless.
2.8.7 Behavior during POWER ON, mode change and RESET
SERUPRO is inactive at Power On. The operating mode change is permitted during
SERUPRO. RESET aborts SERUPRO, the internally selected program test is deselected
again. SERUPRO cannot be combined with other block search types.
Basic functions
2.8.8 Supplementary conditions
2.8.8.1 STOPRE in the target block

The STOPRE block receives all modal settings from the preceding block and can, therefore,
apply conditions in advance in relation to the following actions:
● Synchronize program line currently processing with the main run.
● Derive modal settings for SERUPRO in order, for example, to influence this REPOS motion
on approach of SERUPRO.
Example: Position a Z axis by specifying an X axis setpoint.

When block "G1 F100 Z=$AA_IM[X]" is interpreted, the preceding STOPRE block ensures
synchronization with the main run. The correct setpoint of the X axis is thus read via $AA_IM to
move the Z axis to the same position.
Example: Read and correctly calculate external work offset.
N10 G1 X1000 F100

N20 G1 X1000 F500
N30 G1 X1000 F1000
N40 G1 X1000 F5000
N50 SUPA G1 F100 X200 ; move external work offset to 200
N60 G0 X1000
N70 ...
Via an implicit STOPRE before N50, the NC can read and correctly calculate the current work
offset.
For a SERUPRO operation on the N50 search target, repositioning is on the implicit STOPRE
in the SERUPRO approach and the velocity is determined from N40 with F5000.
Basic functions
Implicit preprocessing stop

Situations in which an implicit preprocessing stop is issued:
1. In all blocks in which one of the following variable access operations occurs:
– Programming of a system variable beginning with $A...
– Programming of a system variable beginning with attribute SYNR/SYNRW
2. For the following commands:
– Part program MEACALC, MEASURE commands
– Programming of SUPA (suppress frame and online corrections)
– Programming of CTABDEF (start of the curve table definition)
– Part program WRITE/DELETE command (write/delete file)
– Before the first WRITE/DELETE command of a sequence of such commands
– Part program EXTCALL command
– Part program GETSELT, GETEXET commands
– For tool and active FTOCON tool fine correction
3. For the following command processing:
– End processing of a type 1 block search ("block search without calculation")
– End processing of a type 2 block search with calculation ("block search at contour end
point")
2.8.8.2 SPOS in target block

If a spindle is programmed with M3/M4 and a switch made to SPOS in the target block, the
spindle is switched to SPOS at the end of the SERUPRO operation ("Search target found"
status).
DB31, ... DBX84.5 = TRUE (active spindle mode: positioning mode)
2.8.8.3 Travel to fixed stop (FXS)

During repositioning (REPOS), the "Travel to fixed stop" function (FXS) is repeated
automatically. Every axis is taken into account. The torque programmed last before the search
target is used as torque.
System variable
The system variables for "Travel to fixed stop" have the following meaning with SERUPRO:
● $AA_FXS: Progress of the program simulation
● $VA_FXS: Real machine state
The two system variables always have the same values outside the SERUPRO function.
ASUP
A user-specific ASUP can be activated for SERUPRO.
Basic functions
Further information
Detailed information regarding the SERUPRO block search can be obtained in the Function
Manual Axes and Spindles; Travel to fixed stop.
2.8.8.4 Travel with limited torque/force (FOC)

During repositioning (REPOS), the "Travel with limited torque/force" function (FOC) is repeated
automatically. Every axis is taken into account. The torque programmed last before the search
target is used as torque.
System variable
The system variables for "Travel with limited torque/force" have the following meaning with
SERUPRO:
● $AA_FOC: Progress of the program simulation
● $VA_FOC: Real machine state
Boundary condition
A changing torque characteristic cannot be implemented during repositioning.
Example
A program traverses axis X from 0 to 100 and switches "Travel with limited torque/force" (FOC)
on every 20 increments for 10 increments. This torque characteristic is usually generated with
non-modal FOC and cannot be performed during repositioning (REPOS). Instead, axis X is
traversed from 0 to 100 with or without limited torque/force in accordance with the last
programming.
Further information
Detailed information regarding the SERUPRO block search can be obtained in the Function
Manual Axes and Spindles; Travel to fixed stop.
2.8.8.5 Synchronous spindle
The synchronous spindle can be simulated.

The synchronous spindle operation with main spindle and any number of following spindles can
be simulated in all existing channels with SERUPRO.
Further information
Further information regarding synchronous spindles can be obtained in the Function Manual
Extended Functions; Synchronous spindle
Basic functions
2.8.8.6 Couplings and master-slave
Setpoint and actual value couplings

The SERUPRO operation is a program simulation in Program Test mode with which setpoint
and actual value couplings can be simulated.
Specifications for EG simulation

For simulation of EG, the following definitions apply:
1. Simulation always takes place with setpoint coupling.
2. If not all leading axes are under SERUPRO, the simulation is aborted with Alarm 16952
"Reset Clear/No Start". This can occur with cross-channel couplings.
3. Axes that have only one encoder from the NC point of view and are moved externally,
cannot be simulated correctly. These axes must not be integrated in couplings.
CAUTION
Incorrect simulation
In order to be able to simulate couplings correctly, they must have been switched off
previously.
This can be performed with machine data MD10708 $MA_SERUPRO_MASK.
Specifications for coupled axes

The SERUPRO operation simulates coupled axes always assuming that they are setpoint
couplings. In this way, the end points are calculated for all axes that are used as target points
for SERUPRO approach. The coupling is also active with "Search target found". The path from
the current point to the end point is carried out for SERUPRO approach with the active coupling.
LEADON
The following specifications apply for the simulation of axial master value couplings:
1. Simulation always takes place with setpoint coupling.
2. SERUPRO approach takes place with active coupling and an overlaid motion of the
following axis in order to reach the simulated target point.
The following axis that is moved solely by the coupling cannot always reach the target point. In
SERUPRO approach, an overlaid linear motion is calculated for the following axis to approach
the simulated point!
Basic functions
Reaching simulated target point for LEAD with JOG

At the time of "Search target found", the coupling is already active, especially for the JOG
motions. If the target point is not reached, SERUPRO approach can be used to traverse the
following axis with active coupling and an overlaid motion to the target point.
Note
For further information on the repositioning of axis couplings, see Section "Repositioning to the
contour (REPOS) (Page 138)".
Master-slave
A system ASUP can be started automatically after the block search has finished. In this ASUP,
the user can control the coupling state and the associated axis positions subsequently. The
required information is provided via the following system variables:

$P_SEARCH_MASLD[<slave axis>] Position offset between slave and master axis when the
link is closed.
$AA_MASL_STAT[<slave axis>] Current state of a master/slave coupling
$P_SEARCH_MASLC[<slave axis>] Status: The state of the coupling was changed during
the block search
The system variables are deleted when the coupling is switched on with MASLON.
Note
The coupled axes must be in the same channel when the block search is executed.
Further information
Further information regarding the master-slave coupling can be obtained in the Function
Manual Technologies; Speed/torque coupling, master-slave"
Basic functions
Example
● System ASUP
– Path and name: /_N_CMA_DIR/PROGEVENT.SPF
– Master axis: X
– Slave axis: Y
Program code
PROG PROGEVENT
N10 IF(($S_SEARCH_MASLC[Y]< >0) AND ($AA_MASL_STAT[Y]< >0))
N20 MASLOF(Y)
N30 SUPA Y = $AA_IM[X] - $P_SEARCH_MASLD[Y]
N40 MASLON(Y)
N50 ENDIF
N60 REPOSA
...
RET
● Machine data
To ensure that the ASUP starts automatically, the following machine data must be set:
– NC-specific machine data:
- MD11604 $MN_ASUP_START_PRIO_LEVEL = 100
- MD11450 $MN_SEARCH_RUN_MODE = 'H02'
– Channel-specifically for the channel in which the ASUP is started or generally for all
channels:
- MD20105 $MC_PROG_EVENT_IGN_REFP_LOCK, bit<n> = TRUE
n: For all required event-driven program calls (prog events)
- MD20115 $MC_IGNORE_REFP_LOCK_ASUP, bit<n> = TRUE
n: For all required user interrupts
NOTICE
System interrupts
MD20115 $MC_IGNORE_REFP_LOCK_ASUP, bits 8 to 31 enable the system
interrupts.
Bit 8 / interrupt 9 starts an ASUP that contains traversing motions.
Basic functions
Axis couplings
● Acceleration of the processing speed and leading axis and following axes in different
channels
For a leading axis whose following axes are assigned to a different channel than that of the
leading axis, the setting for acceleration of the execution speed has no effect (MD22601
(Page 147)$MC_SERUPRO_SPEED_FACTOR):
● Coupled motion
The coupled motion function (TRAILON) is supported by SERUPRO.
Further information
For further information on coupled motion with TRAILON and TRAILOF, see:
– Function Manual Axes and Spindles; Axis couplings
– Programming Manual Advanced; Axis couplings
● Gantry axes
The gantry axis function is supported by SERUPRO.
Further information
Further information regarding the functionality of gantry axes can be obtained in the
Function Manual Axes and Spindles; Gantry axes
● Tangential control
The tangential follow-up of individual axes function is supported by SERUPRO.
Further information
Further information on the tangential control can be found in the Function Manual Special
Functions; Tangential control
2.8.8.7 Axis functions
SERUPRO conditions
The special conditions for SERUPRO must be observed with axis enable, autonomous axis
operations, and axis replacement.
Axis enable
The axial interface DB31, ... DBX3.7 ("Program test axis/spindle enable") controls the axis
enables if no closed-loop controller enable is to (or can) be issued at the machine and is active
only during the program test or when SERUPRO is active.
It is possible to issue this enable via interface signal PLC → NC
DB31, ... DBX3.7 (program test axis/spindle enable). If the real servo enable is missing during
program test or SERUPRO, the effect on the axes/spindles is as follows:
● As soon as the simulated program run intends to move an axis/spindle, the message
"Waiting for axis enable" or "Waiting for spindle enable" is displayed and the simulation is
stopped.
● If during a simulated motion, NC/PLC interface signal DB31, ... DBX3.7 (program test axis/
spindle enable) is then canceled, alarm 21612: "Channel %1 axis %2 NC/PLC interface
signal 'controller enable' reset during motion" is activated.
Basic functions
Autonomous axis operations

Autonomous single-axis operations are axes controlled by the PLC that can also be simulated
on SERUPRO. During SERUPRO operation, as in normal operation, the PLC can take over or
give up control of an axis. If required, this axis can also be traversed using FC18. The PLC takes
over control of the axis before the approach block and is responsible for positioning this axis.
This is valid for all block search types.
Further information
Further information regarding autonomous single-axis operations can be obtained in the
Function Manual Axe and Spindles; Positioning axes
Axis replacement
Problem: A program moves an axis and gives up control before the target block with WAITP(X).
X is thus not subject to REPOS and the axis is not taken into account in SERUPRO approach.
Via the machine data MD11470 $MN_REPOS_MODE_MASK, the following behavior can be
achieved for SERUPRO-REPOS:
The neutral axes are moved as "command axes" in the SERUPRO-REPOS. The axis
interpolates without a path context even if it was last programmed as a path axis. In this
scenario, the velocity results from MD32060 $MA_POS_AX_VELO. After SERUPRO
approach, this axis is again neutral.
Neutral axes that are however not allowed to be repositioned must receive the axial NC/PLC
interface signal "REPOSDELAY". This deletes the REPOS movement.
Example:
After SERUPRO, one axis is deliberately moved in the synchronized action via technology
cycles. The command axes are always moved in the approach block, never in the target block.
The target block can only be changed if all command axes have been moved to the end.
CAUTION
The PLC-controlled axis is not repositioned
Axes enabled by RELEASE(X) before the target block are not repositioned.
2.8.8.8 Gear stage change
Operational sequences
The gear stage change (GSC) requires physical motions from the NC in order to be able to
engage a new gear.
In the SERUPRO operation, no gear stage change is required and is carried out as follows:
Some gears can only be changed when controlled by the NC, since either the axis must
oscillate or a certain position must be approached beforehand.
The gear stage change can be suppressed selectively for DryRun, program test, and
SERUPRO using bits 0 to 2 in MD35035 $MA_SPIND_FUNCTION_MASK.
Basic functions
The gear stage change must then be performed in REPOS; this will work even if the axis
involved is to be in "speed control mode" at the target block. In other cases, the automatic gear
stage change is denied with an alarm if, for example, the axis was involved in a transformation
or coupling between the gear stage change and the target block.
Note
For further information regarding gear stage change with DryRun, program test and
SERUPRO, see Function Manual Axes and Spindles under Spindles.
2.8.8.9 Superimposed motion
Only SERUPRO
If "overlaid movements" are used, only the block search via program test (SERUPRO) can be
used, since the overlaid movements are interpolated accordingly in the main run. This applies
in particular to $AA_OFF.
Velocity profile instead of maximum axis velocity

During Program test, a velocity profile must be used, which allows "superimposed movements"
to be interpolated during the main run. It is thus not possible to interpolate at the maximum axis
velocity.
The axis velocity is set in "Dry run feedrate" mode using
SD42100 $SC_DRY_RUN_FEED.
The velocity of the SERUPRO operation is selected using
MD22600 $MC_SERUPRO_SPEED_MODE.
2.8.8.10 NC/PLC interface signals
REPOS offset available

If a REPOS offset has resulted for an axis during SERUPRO, this is displayed via the axial NC/
PLC interface at the end of the SERUPRO operation:
DB31, ...DBX70.0 == 1 (REPOS offset available)
Validity of the REPOS offset

The REPOS offset becomes invalid at the start of a SERUPRO ASUB or NC start to resume the
machining:
DB31, ... DBX70.1 == 1 (REPOS offset invalid)
The axis can be traversed manually in JOG mode or via the PLC user program using FC 18
between the end of the SERUPRO operation and NC start to resume the machining. If the
REPOS offset is traversed completely, the interface signal is reset.
Basic functions
2.8.8.11 Making the initial settings more flexible
Basic setting / basic SERUPRO setting

Machine data MD20112 $MC_START_MODE_MASK defines the basic setting of the control
for part program start with respect to the G codes (especially the current plane and settable zero
offset), tool length compensation, transformation, and axis couplings. The special option exists
for the SERUPRO operation of using MD22620 $MC_ENABLE_START_MODE_MASK_PRT
to select a basic setting that differs from the normal part program start. The new setting must
therefore be stored in the machine data:
MD22620 $MC_START_MODE_MASK_PRT
The meaning of the bits of MD22620 is identical to those of MD20112
$MC_START_MODE_MASK.
Example:
The synchronous spindle coupling at the beginning of the SERUPRO operation is retained for
the part program start.
; Synchronous spindle cou-

pling not configured
$MC_START_MODE_MASK = 'H400' ; will be switched off
$MC_START_MODE_MASK_PRT = 'H00' ; remains active
$MC_ENABLE_START_MODE_MASK_PRT = 'H01' ; $MC_START_MODE_MASK_PRT is
evaluated in SERUPRO instead
of $MC_START_MODE_MASK
2.8.8.12 Compressor functions

If, during a block search type 5 the target block is located in a program section in which a
compressor function (COMP...) is active, positions are approached on the path calculated by
the compressor when repositioning. These positions must precisely match the positions on the
path programmed in the part program.
If programmed blocks are eliminated from the part program during compression, these blocks
will not be found as the target block in the block search. Alarm 15370 "Search target for block
search not found" is output.
Basic functions
2.9 Asynchronous subprograms (ASUPs)
2.8.9 System variable

Overview of the system variables relevant for SERUPRO:
System variable Meaning

$AC_ASUP, bit 20 ASUP activation reason:
$AC_ASUP, Bit 20 == 1 ⇒ system ASUP active, reason: SERUPRO search goal
reached
$AC_SERUPRO SERUPRO status:
$AC_SERUPRO == 1 ⇒ SERUPRO is active
$P_ISTEST Program test status:
SERUPRO active ⇒ $P_ISTEST == 1
$P_SEARCHL Most recently active block-search type:
$P_SEARCHL == 5 from the start of SERUPRO to reset or end of program
$AC_REPOS_PATH_MODE REPOS mode for repositioning the contour after a SERUPRO
2.9.1 Function
Note
The terms "asynchronous subprogram", "ASUB" and "interrupt routine" used interchangeably
in the description below refer to the same functionality.
Basic functions
General
Asynchronous subprograms (ASUB) are NC programs that are started in an NC channel as
response to asynchronous events (interrupt input signals, process and machine states). The
activation of an ASUB interrupts an NC program currently executing. The NC program can be
continued at the interrupt position when the ASUB ends.
0DLQSURJUDPVXESURJUDP ,QWHUUXSWURXWLQH

16(7,17 $VVLJQDURXWLQHWRDQHYHQW
DQGVZLWFKWRUHDG\
1
%ORFNLQ 1 $%+(%B=

([HFXWLRQ
1
(YHQW 15
1 LQSXWVZLWFKHG
1;<
1
1
1 0
1
1
1 5HWXUQSRVVLEOH
10
The NC program being executed in the channel can be protected from being interrupted by an
ASUB either completely or only in sections. See Section "Programming (SETINT, PRIO)
(Page 177)" "Flexible programming".
Definition
To create an ASUB (interrupt routine) from an NC program, an interrupt signal must be
assigned to the NC program via the SETINT command (see Section "Programming (SETINT,
PRIO) (Page 177)") or via the PI service "ASUB" (see "PLC" Function Manual) in the block
descriptions.
Interrupt signals
● A total of eight I/O inputs are available as interrupt signals.
● The I/O input signals can be influenced via the PLC user program.
● The first four I/O inputs are the four fast inputs of the NCU module. The signal states can be
read via the NC/PLC interface in the DB10 data block. The input signals can also be locked
via the NC/PLC interface in the DB10 data block.
Basic functions
Further information
● You will find more information under Digital and analog NC I/O (Page 687).
● Further information regarding PLC control of the fast NC inputs (interrupt signals) can be
obtained in the Function Manual PLC.
Call
During program mode

During program mode, i.e. in AUTOMATIC or MDI mode, an ASUB can always be called.
Outside the program mode

Outside the program mode, an ASUB can be called in the following modes, machine functions
and states:
● JOG, JOG REF
● MDI Teach In, MDI Teach In REF, MDI Teach In JOG, MDI REF, MDI JOG
● AUTOMATIC, program statuses "stopped", "ready"
● Axis state "Not referenced"
If an ASUB is started during JOG or JOG REF, the current traversing is aborted.
Activation
An ASUB is activated via:
● 0/1 edge of the interrupt signal, triggered by a 0/1 edge at the associated fast NC input
● Calling of the "Function Call ASUB" (see also Function Manual "PLC and Basic Program",
Section "Basic PLC program").
● Setting an output via synchronized action which is parameterized on an interrupt via short-
circuit (see "Examples (Page 180)")
Further information
Function Manual Synchronized Actions
Display
The activation of an ASUB is shown channel-specifically with the following NC/PLC interface
signal:
DB21, … DBX378.0 == 1 (ASUB active)
Basic functions
2.9.1.1 Execution sequence of an ASUP in program mode

1. Decelerating the axes
Upon activation of the ASUP, all machine axes are decelerated to a standstill according to
the deceleration ramp (MD32300 $MA_MAX_AX_ACCEL), and the axis positions are
saved.
2. Reorganization
In addition to decelerating the axes, the previously decoded calculation blocks are
calculated back to the interruption block, i.e. all the variables, frames and G commands are
assigned the value that they would have at the point of interruption if the part program had
not been previously decoded. These values are also buffered so they remain available after
the end of the ASUP.
Exceptions where no reorganization is possible:
– In thread cutting blocks
– With complex geometries (e.g. spline or radius compensation)
3. Processing the ASUP
The ASUP is started automatically on completion of the reorganization.
The ASUP is processed as a normal subprogram (nesting depth, etc.).
4. End of the ASUP
After the end identifier (M02, M30, M17) of the ASUP has been processed, the axis traverses
by default to the end position programmed in the part program block following the
interruption block.
A REPOS statement must have been programmed at the end of the ASUP if return
positioning to the point of interruption is required, e.g. N104 REPOSL M17
3DUWSURJUDP $68%
352*B1$0( ,17(5B1$0(
1 1
1< $68%WUDYHOSDWK (QGSRLQWRIWKH 1
1; $68% 1
1 1 15(326/0

10 &RQWLQXH*

1
ZLWKRXW5(326
1
6 WK

1
L
5( LRQZ
1
1
32
LW
SRV
&RQWLQXH*
5H
ZLWKRXW5(326
1

1
&RQWLQXHDIWHU
5(326 1

,QWHUUXSWLRQSRLQW
1
Basic functions
2.9.1.2 ASUP with REPOSA

If an NC program is stopped by an NC stop or alarm, and an ASUP with REPOSA is
subsequently initiated from the PLC user program using FC9, then typically, the following
sequence is obtained:
● The ASUP and/or the traversing motion programmed in it are executed:
– Program status: "Stopped"
– DB21, ... DBX318.0 (ASUP is stopped) = 1
● A new stop is executed before repositioning to the contour (REPOS).
● The operator initiates an NC start to reposition to the contour (REPOS):
– DB21, ... DBX318.0 (ASUP is stopped) = 0
– The reapproach movement is executed.
● At the end of the reapproach motion, the FC9 acknowledge signal "ASUP done" is set and
the path of the interrupted NC program is continued.
Note
The NC/PLC interface signal DB21, ... DBX318.0 (ASUP is stopped) is set only in the
following case:
Interrupt in the program mode and in the "interrupted" channel state.
Note
For ASUPs without REPOS, the FC9 acknowledge signal "ASUP done" and the reset of the
NC/PLC interface signal DB21, ... DBX318.0 = 0 (ASUP is stopped) coincide from a timing
perspective.
3DWKPRWLRQRIDQ &RQWUROLVVWRSSHG
$68%ZLWK5(326$ $68%ZLWK5(326$ DXWRPDWLFDOO\
(YHQWWKDWSXWVWKHFRQWURO
LQWRWKHVWRSSHGVWDWXV ,6$68%VWRSSHGLV
RFFXUV VHW
([DPSOH6WRSNH\
)&EORFNVLJQDOV$68%'RQH
&RQWUROKDVVWRSSHGDIWHU
ZKLFKWKH$683LVVWDUWHG
E\WKH)& 3DWKRIWKHSDUWSURJUDP
Figure 2-6 Schematic sequence: ASUP with REPOSA
Basic functions
2.9.1.3 NC response
The different responses in the various states for channel, mode group or NC on an activated
ASUP are listed in the following table:
State ASUP start Control system response

Program is active Interrupt, (PLC) 1. Fast retraction or stop axes
2. Interrupt the program for the duration of the ASUP
3. Approach of the interruption point, if REPOS in ASUP
4. Continuation of the part program
Reset Interrupt, (PLC) The ASUP is executed like a main program. Reset (without M30) is exe‐
cuted at the end of the ASUP. The next control system status depends on
the following machine data:
MD20110 $MC_RESET_MODE_MASK
MD20112 $MC_START_MODE_MASK
Further information
Workpiece-related actual-value system (Page 396)
Program mode (AUTO‐ Interrupt, (PLC) ASUP is executed. At the end of the ASUP the STOP state is reapplied.
MATC or MDI) If REPOS in the ASUP:
+ channel stopped
● The ASUP processing is stopped before the approach block.
● The approach movement can be initiated with the Start key.
Start key Once the ASUP has been executed, processing of the interrupted pro‐
gram is resumed.
Manual mode Interrupt, (PLC) Control system assumes the status "internal program execution mode" for
+ channel stopped the addressed channel (not evident externally) and then activates the AS‐
UP. The selected operating mode remains valid. The original status is
resumed after execution of the ASUP (M17).
JOG Interrupt, (PLC) Stop processing, evaluate:
AUTO Teach-In MD11602 $MN_ASUP_START_MASK
AUTO Teach reference
MD11604 $MN_ASUP_START_PRIO_LEVEL
point.
Internal switchover to "internal program execution mode" if appropriate,
MDI JOG, Interrupt, (PLC)
activate ASUP, restore status prior to ASUP start.
MDI Teach-In,
MDI Teach reference point. Any LIFTFAST defined with SETINT is not activated in JOG mode.
Manual mode Interrupt, (PLC) The current active motion is stopped. The distance-to-go is deleted. The
+ channel running remaining sequence of operations is the same as for "Manual mode,
channel stopped".
User alarm 65500 - 65999, Interrupt, (PLC) When the following machine data is set, the user ASUP is processed
channel in reset despite the "NC Start disable" alarm response:
MD20194 $MC_IGNORE_NONCSTART_ASUP
Basic functions
State ASUP start Control system response

Processing of INITIAL.INI Not possible The signal "Interrupt request not possible" is generated.
Block search
Alarm that cannot be re‐
moved by NC Start.
Digitalizing active
Channel in fault condition
User alarm other Not possible The "request was canceled because of an alarm" signal is generated.
than 65500 - 65999,
channel in reset,
MD20194 not active
2.9.2 Commissioning: Machine data
2.9.2.1 NC-spec.: Mode-group-specific NC/PLC interface signals and operating mode switchover
The machine data specifies the effectiveness of the mode-group-specific NC/PLC interface
signals of DB11 and the channels in which an operating mode switchover is performed:
MD11600 $MN_BAG_MASK = <Value>
Val‐ Meaning
ue
0 The mode-group-specific NC/PLC interface signals of DB11 are effective.
An internal operating mode switchover is performed in all channels of the mode group.
1 The mode-group-specific NC/PLC interface signals of DB11 are not effective.
An internal operating mode switchover is performed only in the channel in which an ASUP is
active.
2 The mode-group-specific NC/PLC interface signals of DB11 are effective.
active.
3 The mode-group-specific NC/PLC interface signals of DB11 are not effective.
active.
Note
Multi-channel systems
If the "Manual traversing during an ASUP interruption in JOG mode" function is to be possible
in multi-channel systems (see below), MD11600 $MN_BAG_MASK must be set to "2" or "3".
See also
Programming (SETINT, PRIO) (Page 177)
Basic functions
2.9.2.2 NC-spec.: ASUP start enable

With the machine data, you can specify which stop reasons are to be ignored for an ASUP start:
MD11602 $MN_ASUP_START_MASK, <Bit> = <Value>
Bit Val‐ Meaning

ue
0 0 The ASUP is not started when a stop is present from the Stop key, M0 or M01.
1 The ASUP is started even when a stop is present from the Stop key, M0 or M01.
2 0 When an ASUP is started, the channel-specific machine data is effective when there is
a read-in disable in the channel:
● MD20107 $MC_PROG_EVENT_IGN_INHIBIT
● MD20116 $MC_IGNORE_INHIBIT_ASUP
1 The start of a user or system ASUP is enabled in all channels of the NC even when there
is a read-in disable in the relevant channel.
The settings in the channel-specific machine data are not effective:
● MD20107 $MC_PROG_EVENT_IGN_INHIBIT
● MD20116 $MC_IGNORE_INHIBIT_ASUP
Notice
The start enable is active in all channels of the NC despite a read-in disable. Not only for
the user, but also for the system ASUPs. It is therefore strongly recommended that
the channel-specific enables are used instead of the NC-specific enable.
3 0 If an ASUP was started in JOG mode and interrupted by an NC stop, axes cannot be
traversed manually in this state.
1 If an ASUP was started in JOG mode and interrupted by an NC stop, axes can be
traversed manually in this state.
The ASUP can be continued with NC start. A REPOS operation is then performed auto‐
matically.
Note
If more than one channel is parameterized in the control, the following machine data must
also be set:
MD11600 $MN_BAG_MASK, bit 1 = 1
Manual start enable

If an ASUP is not started automatically due to the parameterized start enables, the ASUP can
still be started via NC/PLC interface signal (DB21, ... DBX7.1) from the PLC user program or by
manual actuation of NC start.
Note
The ASUP for "fast retraction from the contour" (LIFTFAST) is started in every case.
2.9.2.3 NC-spec.: Effectiveness of the parameterized start enables

With the machine data, you set up to which ASUP priority (Page 177), starting from the highest
priority, the settings in MD11602 $MN_ASUP_START_MASK are effective:
MD11604 $MN_ASUP_START_PRIO_LEVEL = <ASUP priority>
Basic functions
Example
MD11604 $MN_ASUP_START_PRIO_LEVEL = 5
The settings in MD11602 $MN_ASUP_START_MASK are effective for ASUPs of priorities 1 →
5.
2.9.2.4 Channel-spec.: Start enable despite non-referenced axes

With the machine data, you can set for which interrupts the associated ASUP is started despite
the parameterized "NC start disable without reference point" function (MD20700
$MC_REFP_NC_START_LOCK):
MD20115 $MC_IGNORE_REFP_LOCK_ASUP, bit (1 - <Interrupt>) = TRUE
NOTICE
System interrupts
With MD20115 $MC_IGNORE_REFP_LOCK_ASUP, bits 8 - 31, the ASUPs assigned to the
system interrupts are enabled.
NC-specific ASUP start enable
If MD11602 $MN_ASUP_START_MASK, bit 2 == TRUE, the ASUP start enable is set for all
channels of the NC despite the parameterized channel-specific "NC start disable without
reference point" function (MD20700 $MC_REFP_NC_START_LOCK). It is therefore strongly
recommended that the channel-specific enable is used instead of the NC-specific enable.
2.9.2.5 Channel-spec.: Start enable despite read-in disable

With the machine data, you can set for which interrupts the associated ASUP is started despite
the read-in disable present in the channel (DB21, ... DBX6.1):
MD20116 $MC_IGNORE_INHIBIT_ASUP, bit (1 - <Interrupt>) = TRUE
NOTICE
System interrupts
With MD20116 $MC_IGNORE_INHIBIT_ASUP, bits 8 - 31, the ASUPs assigned to the
system interrupts are enabled.
If MD11602 $MN_ASUP_START_MASK, bit 2 == TRUE, the channel-specific settings in
MD20116 $MC_IGNORE_INHIBIT_ASUP are ignored in all channels of the NC. It is
therefore strongly recommended that the channel-specific enable is used instead of the NC-
specific enable.
Basic functions
2.9.2.6 Channel-spec.: Continuous execution despite single block

With the machine data, you can set for which interrupts the associated ASUP is
executed continuously, i.e. without block-by-block interruption, despite active single block
processing in the channel (DB21, ... DBX0.4):
MD20117 $MC_IGNORE_SINGLEBLOCK_ASUP, bit (1 - <Interrupt>) = TRUE
The settings in MD20117 $MC_IGNORE_SINGLEBLOCK_ASUP are only active for a single
block SBL1 (main run single block).
NOTICE
System interrupts
With MD20117 $MC_IGNORE_SINGLEBLOCK_ASUP, bits 8 - 31, the ASUPs assigned to
the system interrupts are enabled.
If MD10702 $MN_IGNORE_SINGLEBLOCK_MASK, bit 1 == TRUE, the channel-specific
settings in MD20117 $MC_IGNORE_SINGLEBLOCK_ASUP are ignored in all channels of
the NC. It is therefore strongly recommended that the channel-specific enable is used instead
of the NC-specific enable.
2.9.2.7 Channel-spec.: Refreshing the display

With the machine data, you can set that the display is not refreshed while the ASUP is being
executed to avoid a flickering of the display of the program and the channel states on the user
interface when executing a very short ASUP:
MD20191 $MC_IGN_PROG_STATE_ASUP, bit (1 - <Interrupt>) = TRUE
Note
NC/PLC interface signal
The following NC/PLC interface signal is set when executing an ASUP with suppressed display:
DB21, … DBX378.1 = 1 ("silent" ASUP active)
System variables and NC/PLC interface signals

The system variables and NC/PLC interface signals for the program state and the channel state
are not affected by the suppression of the display during the execution of an ASUP:
● $AC_STAT (channel state)
● $AC_PROG (program state)
● DB21, ... DBX35.5 - 7 (channel state)
● DB21, ... DBX35.0 - 4 (program state)
Basic functions
2.9.3 Programming: System variables
2.9.3.1 REPOS option ($P_REPINF)

In conjunction with ASUPs, program execution sequences can be generated for which there is
no unambiguous return to a repositioning point on the contour (REPOS).
The system variable can be used to read in the ASUP whether a REPOS is possible.
<value> = $P_REPINF
Value Meaning
0 Repositioning with REPOS not possible because:
● Not called in the ASUP
● ASUP ran from reset state
● ASUP ran from JOG
1 Repositioning with REPOS possible in ASUP
2.9.3.2 Activation event ($AC_ASUP)

The following information with regard to the event that caused the activation of the ASUP can
be read via the $AC_ASUP system variable:
● The reason why the ASUP was activated, e.g. Bit 0: User interrupt "ASUP with Blsync"
● How the ASUP was activated, e.g. Bit 0: NC/PLC interface signal, digital-analog interface
● How is it possible to continue, e.g. Bit 0: Freely selectable REORG or RET
2.9.4 Programming (SETINT, PRIO)
Assignment: Interrupt to the NC program

The SETI command assigns an NC program to an interrupt. This makes the NC program into
an ASUB.
Syntax
SETINT(<n>) <NC program>
Meaning
SETINT: Assignment of an NC program to an interrupt signal

<n>: Number of the interrupt signal
Range of values: 0, 1, 2, ... 8
<NC program>: Program name
Basic functions
Example

N20 SETINT(3) LIFT_Z ; IF input 3 == 1
; THEN start ASUB "LIFT_Z"
Together with SETINT additionally the following statements can be programmed:

● LIFTFAST
When the interrupt signal arrives, a "Fast retraction of the tool from the contour" is performed
before the ASUB starts. The motion direction for the fast retraction is specified by the
program instruction ALF.
● BLSYNC
Upon receiving the interrupt signal, the current program block is processed and only then is
the ASUB started.
Note
The assignment interrupt signal ↔ part program is cleared when the following happens:
● Channel in Reset state
● CLRINT statement in the part program
Priorities
If several interrupts are activated by SETINT in an NC program, the assigned NC programs or
ASUBs must be assigned different priorities.
Syntax
PRIO=<value>
Meaning
PRIO: Keyword for defining the priority of the interrupt

<Value>: Priority: 1, 2, 3 ... 128. Whereby 1 is the highest priority.
Example

N20 SETINT(3) PRIO=2 LIFT_Z ; IF input 3 == 1
; THEN start ASUB "LIFT_Z"
N30 SETINT(2) PRIO=3 LIFT_X ; IF INPUT 2 == 1
; THEN start ASUB "LIFT_X"
The ASUBs are executed in the sequence of the priority values if the inputs 2 and 3 have
switched simultaneously:
1. "LIFT_Z"
2. "LIFT_X"
Basic functions
Additional interrupt-specific commands
Command Meaning
SAVE If the SAVE command is used in an ASUB, the G commands, frames and
transformations active in the interrupted NC program before the interrup‐
tion take effect again at the end of the ASUB.
DISABLE The DISABLE ENABLE command pair can be set to protect program sec‐
ENABLE tions from being interrupted by ASUBs.
The assignment of an interrupt signal to an NC program made with SETINT
is retained.
The ASUB is then started with the next 0/1 edge of the interrupt signal
after ENABLE.
CLRINT(<n>) Delete the assignment of interrupt signals n to the NC program assigned
with SETI.
Further information
See also
Programming (Page 182)
2.9.5 Restrictions
Cross-mode ASUP start
Settings to be checked
● MD11600 $MN_BAG_MASK
● MD11604 $MN_ASUP_START_PRIO_LEVEL
● Interrupt assignment priority
Recommended settings
NC-specific machine data:
● MD11600 $MN_BAG_MASK = 'H3'
Note
Note with this setting, that the mode-group-specific NC/PLC interface signals of DB11 no
longer affect the channel in which the ASUP is executed. If this behavior is not desired,
alternatively the setting MD11600 $MN_BAG_MASK = 'H2' can be used (see
"Commissioning: Machine data (Page 173)").
MD11602 $MN_ASUP_START_MASK = 'H5'
● MD11604 $MN_ASUP_START_PRIO_LEVEL = 7
Basic functions
Channel-specific machine data for the channel in which the ASUP is started or generally for all
channels:
● MD20105 $MC_PROG_EVENT_IGN_REFP_LOCK, bit <n> = TRUE
<n>: For all required event-driven program calls (prog events)
● MD20115 $MC_IGNORE_REFP_LOCK_ASUP, bit <n> = TRUE
<n>: For all required user interrupts
NOTICE
System interrupts
With MD20115 $MC_IGNORE_REFP_LOCK_ASUP, bits 8 - 31, the system interrupts are
enabled.
2.9.6 Examples
Activation of an ASUP by an interrupt from a synchronized action

1. Parameterize two active digital I/O bytes:
– MD10350 $MN_FASTIO_DIG_NUM_INPUTS = 2
– MD10360 $MN_FASTIO_DIG_NUM_OUTPUTS = 2
2. Parameterize a short-circuit with OR operation from output 9 to input 9:
– Input 1, input byte 2 = (output 1, output byte 2) OR (HW input signal 1, input byte 2):
MD10361 $MN_FASTIO_DIG_SHORT_CIRCUIT[0] = 'H0102B102'
3. Assign the HW input byte to the SETINT interrupt programming:
– Input byte 2:
MD21210 $MC_SETINT_ASSIGN_FASTIN = 2
4. Define input as ASUP trigger:
– Input 1 in the second input byte, i.e. absolute input 9, starts the SYNCASUP program
SETINT(1) PRIO=1 SYNCASUP
5. Define a synchronized action to set the output:
– Synchronized action with ID 1 always sets output 9 to 1 when the value of the
standardized path parameter becomes >= 0.5:
IDS=1 EVERY $$AC_PATHN >= 0.5 DO $A_OUT[9]=1
The short-circuit of output 9 to input 9 causes interrupt 1 and the "SYNC" NC program to
be started as ASUP.
Basic functions
2.10 User-specific ASUB for RET and REPOS
2.10.1 Function
Function
The control software includes a Siemens-specific ASUP to implement the NC program end
(RET) and repositioning on the contour (REPOS) functions. The machine tool manufacturer
can replace the system ASUP with a user-specific ASUP.
DANGER
Programming fault
The machine manufacturer has sole responsibility for ensuring the correct operation of the
user-specific ASUP that replaces the Siemens-specific ASUP ("ASUP.SYF").
2.10.2 Parameter assignment
Installation
ASUP name
The user-specific ASUP must be given the following name:
● _N_ASUP_SPF
ASUP directories
The user-specific ASUP "_N_ASUP_SPF" must be stored in one of the two directories:
● _N_CMA_DIR (manufacturer directory)
● _N_CUS_DIR (user directory)
Activation and search path

Bits 0 and 1 of the following machine data specify the event for which the user-specific ASUP
"_N_ASUP_SPF" is activated.
Bit 2 specifies the search start for activation of the user-specific ASUP "_N_ASUP_SPF".
Basic functions
MD11610 $MN_ASUP_EDITABLE, bit 0, 1, 2 = <value>
Bit Value Meaning

0 and 1 0 The user-specific ASUP is activated neither for program end (RET) nor for repo‐
sitioning on the contour (REPOS).
1 The user-specific ASUP is activated for RET.
The system-specific ASUP is activated for REPOS.
2 The system-specific ASUP is activated for RET.
The user-specific ASUP is activated for REPOS.
3 The user-specific ASUP is activated for RET and REPOS.
2 0 The user-specific ASUP is searched for first in the user directory _N_CUS_DIR.
1 The user-specific ASUP is searched for first in the manufacturer
directory _N_CMA_DIR.
Defining a level of protection

If a user-specific ASUP is to be used for RET and/or REPOS (MD11610
$MN_ASUP_EDITABLE ≠ 0), a protection level can be defined for the user-specific routine
"_N_ASUP_SPF". The level of protection can have values in the range 0 - 7. The setting is made
via the following machine data:
MD11612 $MN_ASUP_EDIT_PROTECTION_LEVEL <protection level of the user-specific
ASUP>
Details regarding the protection levels can be obtained in:
Further information
Commissioning Manual; Protection level concept

The following machine data specifies that the system-specific ASUP and the user-specific
ASUP "_N_ASUP_SPF" should be processed without interruption, despite active single-block
processing:
MD10702 $MN_IGNORE_SINGLEBLOCK_MASK, bit 0 = <value>
Bit Value Meaning

0 0 For active single-block mode, a stop is made in every ASUP.
1 For active single-block mode, the ASUP is processed without interruption.
2.10.3 Programming
Determining the cause of the ASUB activation

The cause of the activation of the ASUB can be read bit-coded via the system variable
$AC_ASUP.
Basic functions
2.11 Perform ASUB start for user alarms
Continuation
When using the system ASUB, the behavior for the continuation after execution of the actions
is permanently specified within the ASUB:
● System ASUB 1 → continuation with RET (subprogram return)
● System ASUB 2 → continuation with REPOS (repositioning)
The description of the system variables specifies the behavior with regard to the system ASUB
for each cause at "Continued for".
Note
Continued for user-specific ASUB
It is recommended for user-specific ASUBs that the appropriate continuation of the system
ASUB be retained.
Cause: Change of operating mode ($AC_ASUP, bit 9 == 1)
At a change of operating mode, the continuation depends on the machine data:
MD20114 $MC_MODESWITCH_MASK (interruption of MDA through mode change)
● Bit 0 == 0: System ASUB 1 → continuation with RET
● Bit 0 == 1: System ASUB 2 → continuation with REPOS
Further information
A detailed description regarding the system variable can be obtained in the List Manual System
Variables
2.11.1 Function
Description
An ASUB can be initiated in various situations, either by the user, the system or event-
controlled. A user alarm with the "NC Start disable" alarm response prevents the ASUB start in
some situations. For a pending alarm response, a user ASUB from reset acknowledges with the
alarm 16906.
Basic functions
With the appropriate setting of a channel-specific machine data it is possible to start and
perform an ASUB although a user alarm with the alarm response "NC Start disable" is active.
The alarm response is overridden for the ASUB start and permits its execution.
Note
NC alarms with the "NC Start disable" alarm response are not affected by the override. A user
ASUB from reset is still not possible and will be rejected with the alarm 16906.
User alarms that can be overridden

The number range for the user alarms that can be overridden is classified as follows:
Number range Effect Delete

65000 - 65499 Display, NC Start disable Reset
65500 - 65999 Display, NC Start disable (not for ASUBs for set MD20194) Reset
66000 - 66999 Display, NC Start disable, motion standstill after executing Reset
the pre-decoded blocks
67000 - 67999 Display Cancel
68000 - 68999 Display, NC Start disable, immediate interpolator stop Reset
69000 - 69999 Display, NC Start disable, stop at next block end Reset
Note
Although it is possible to override the "NC Start disable" alarm response for the following alarm
number ranges, the other responses of the associated alarms ensure for the stop conditions.
The stop conditions cannot be overridden with the function described in this section:
● 66000 - 66999
● 68000 - 68999
● 69000 - 69999
2.11.2 Activation
Setting
Each ASUP channel can be set separately with the following channel-specific machine data:
MD20194 $MC_IGNORE_NONCSTART_ASUP (ASUP start permitted despite pending alarm
response "NC Start disable" for certain user alarms)
A change of the MD setting acts only with the NEWCONF part program command or from the user
interface per softkey.
Basic functions
Sequence
The normal sequence for the ASUP start has the following form:
● Set machine data appropriate with MD20194 $MC_IGNORE_NONCSTART_ASUP and
activate with NEWCONF.
● Start the part program.
A user alarm from the number ranges that can be overridden appears, e.g. alarm 65500.
This can occur from a synchronized action or with a part program command.
● Despite alarm, the part program is processed to the program end M02, M30 or M17.
The Reset channel state is active.
● A started user ASUP from reset is now performed.
Note
An ASUP start from a running or stopped part program is also permitted for a pending "NC Start
disable" alarm response. It is irrelevant whether a user alarm or an NC alarm with the "NC Start
disable" alarm response is involved.
Note
If the part program is stopped during the processing of the user ASUP, the ASUP can no longer
be continued with the NC Start key, e.g. for M0 in the ASUP or for user stop. The "NC Start
disable" alarm response is rejected with the alarm 16906. The previously generated user alarm
can be acknowledged only with reset.
2.11.3 Examples
2.11.3.1 User ASUB from reset - example 1

MD20194 is not set in the application
Main program
Program code
N10 G90 G0 Z10
N20 SETAL(65500)
N30 X100
N40 Z0
N50 M30
User ASUB
Program code
N110 G91 G0 X-10 Z5
Basic functions
Program code
N120 X20
N130 REPOSA
Sequence
1
$ODUP
1 5(326$
1
1 8VHU$68%IURPDFWLYH 1

SURJUDP
8VHU$68%IURPUHVHW 0
$ODUP

The block N10 is processed. The alarm 65500 appears that contains the "Display" and "NC
Start disable" alarm responses. The part program does not stop as result. The block N30 is
loaded and processed. If the user ASUB is used in the block middle, it is performed despite
pending "NC Start disable" alarm response. The REPOSA resumes at the program interruption
and processes the part program to the program end M30. If the user ASUB is now used, it will
be rejected with alarm 16906. The NC state is reset.
2.11.3.2 User ASUB from reset - example 2

The application is the normal case, MD20194 is set.
Main program
Program code
N4 $MC_IGNORE_NONCSTART_ASUP=1
N6 NEWCONF
N10 G90 G0 Z10
N20 SETAL(65500)
N30 X100
N40 Z0
N50 M30
Basic functions
User ASUB
Program code
N110 G91 G0 X-10 Z5
N120 X20
N130 REPOSA
Sequence
1
$ODUP
1 5(326$
1
1
8VHU$68%IURPDFWLYH
1 SURJUDP 1
1 5(326$
8VHU$68%IURPUHVHW 0
The machine data MD20194 $MC_IGNORE_NONCSTART_ASUP is set for ASUB channel 1

and activated with NEWCONF. The block N10 is processed. The alarm 65500 appears that
contains the "Display" and "NC Start disable" alarm responses. The part program does not stop
as result. The block N30 is loaded and processed. If the user ASUB is used in the block middle,
it is performed despite pending "NC Start disable" alarm response. The REPOSA resumes at the
program interruption and processes the part program to the program end M30. If the user ASUB
is now used, it is repeated because of the set machine data MD20194.
2.11.3.3 User ASUB with M0

MD20194 is set in the application.
Main program
Program code
N6 NEWCONF
N10 G90 G0 Z10
N20 SETAL(65500)
N30 X100
N40 Z0
N50 M30
Basic functions
User ASUB
Program code
N110 G91 G0 X-10 Z5
N120 X10
N122 M0
N124 X10
N130 REPOSA
Sequence
1 0 $ODUP

$ODUP
1&VWDUWDIWHUVWDQGVWLOO
1
1
8VHU$68%IURPDFWLYH
1 SURJUDP

it is performed despite pending "NC Start disable" alarm response. The part program stops at
block N122 because of M0. The ASUB can no longer be continued when the NC Start key is
pressed. The "NC Start disable" alarm response is rejected with the alarm 16906. The
previously generated 65500 alarm can be acknowledged only with reset.
2.11.3.4 User ASUB with stop

MD20194 is set in the application.
Main program
Program code
N6 NEWCONF
N10 G90 G0 Z10
N20 SETAL(65500)
N30 X100
N40 Z0
Basic functions
Program code
N50 M30
User ASUB
Program code
N110 G91 G0 X-10 Z5
N120 X20
N130 REPOSA
Sequence
1&VWRS
1 $ODUP

$ODUP
1
1
8VHU$68%IURPDFWLYH
1 SURJUDP

it is performed despite pending "NC Start disable" alarm response. If the NC Stop key is
pressed for N120 in the block middle, the ASUB stops. The ASUB can no longer be continued
when the NC Start key is pressed. The "NC Start disable" alarm response is rejected with the
alarm 16906. The previously generated 65500 alarm can be acknowledged only with reset.
2.11.3.5 User ASUB from stopped

MD20194 is or not set in the application.
Main program
Program code
N10 G90 G0 Z10
N20 SETAL(65500)
N30 X50
N35 M0
N38 X100
Basic functions
Program code
N40 Z0
N50 M30
User ASUB
Program code
N110 G91 G0 X-10 Z5
N120 X20
N130 REPOSA
Sequence
1 $ODUP

$ODUP
1
1 0
8VHU$68%IURPVWRSSHG
1
The block N10 is processed. The alarm 65500 appears that contains the "Display" and "NC
Start disable" alarm responses. The part program does not stop as result. The block N30 is
loaded and processed. The part program stops at block N35 because of M0. The NC state is
stopped. If the user ASUB is now used, it is performed despite the stopped NC state and
pending "NC Start disable" alarm response. It does not matter whether or not the machine data
MD20194 $MC_IGNORE_NONCSTART_ASUP is set. After block N120, the ASUB remains
stationary before REPOSA. Repositioning is possible only at the next NC Start. The NC Start,
however, is rejected with the alarm 16906 because of the "NC Start disable" alarm response.
The previously generated 65500 alarm can be acknowledged only with reset.
Basic functions
2.12 Execution from external
2.12 Execution from external
Function
The "execution from external source" function can be used to execute programs from an
external program memory that cannot be saved in the NC memory due to their size.
Note
Protected cycles (_CPF files) can not be executed from an external program memory.
External program memory

External program memory can be found on the following data carriers:
● Local drive
● Network drive
● USB drive
Note
Only the USB interfaces on the operator panel front or the TCU can be used as interface for
the processing of an external program on a USB drive.
NOTICE
Tool/workpiece damage caused by the USB flash drive
It is recommended that a USB flash drive is not used for the execution of an external
subprogram. A communication interruption to the USB flash drive during the execution of
the subprogram due to contact problems, failure, abort through trigger or unintentional
unplugging, results in an immediate machining stop. The tool and/or workpiece could be
damaged.
Applications
● Direct execution from external programs
In principle, any program that is accessible via the directory structure of the interface in the
"Execution from external" HMI mode can be selected and executed.
● Execution of external subprograms from the part program
The "external" subprogram is called with the part program command EXTCALL by specifying
a call path (optional) and the name of the part subprogram (→ see "Execution of external
subprograms (EXTCALL) (Page 192)").
Parameterization
A reloading memory (FIFO buffer) must be reserved in the dynamic NC memory for executing
a program in "execution from external source" mode.
Basic functions
2.13 Executing external subprograms (EXTCALL)
Size of FIFO buffer

The size of the FIFO buffer is set in the machine data:
MD18360 $MN_MM_EXT_PROG_BUFFER_SIZE (FIFO buffer size for processing from
external)
Note
Programs with jump commands
For external programs that contain jump commands (GOTOF, GOTOB, CASE, FOR, LOOP,
WHILE, REPEAT, IF, ELSE, ENDIF etc.) the jump destinations must lie within the post loading
memory.
Note
ShopMill/ShopTurn programs
The contour descriptions added at the file end mean the ShopMill and ShopTurn programs
must be stored completely in the read-only memory.
Number of FIFO buffers

One FIFO buffer must be provided for each one of the programs that are executed
simultaneously in "execution from external source" mode.
The number of FIFO buffers is set in the machine data:
MD18362 $MN_MM_EXT_PROG_NUM (number of externally executed program levels
executable simultaneously)
Behavior on reset, power-on

External program calls are aborted using reset and power-on and the particular FIFO buffers
are erased.
A main program selected from an external program memory is selected again automatically
after a power-on if the same program memory is still available and execution of EXTCALL calls
has been activated in MD9106 $MM_SERVER_EXTCALL_PROGRAMS.
Function
Individual machining steps for producing complex workpieces may involve program sequences
that require so much memory that they cannot be stored in the NC memory.
In such cases, the user has the option of executing the program sequences as subprograms
from an external program memory in the "Execution from external source" mode with the help
of the EXTCALL part program command.
Basic functions
Prerequisites
The following preconditions are applicable to the execution from external subprograms:
● The subprograms must be accessible via the directory structure of the operator interface.
● A reloading memory (FIFO buffer) must be reserved for each subprogram in the dynamic
NC memory.
Note
Subprograms with jump commands
For external subprograms that contain jump commands (GOTOF, GOTOB, CASE, FOR, LOOP,
WHILE, REPEAT, IF, ELSE, ENDIF etc.) the jump destinations must lie within the post loading
memory.
The size of the post loading memory is set via:
MD18360 MM_EXT_PROG_BUFFER_SIZE
ShopMill/ShopTurn programs
The contour descriptions added at the file end mean the ShopMill and ShopTurn programs
must be stored completely in the read-only memory.
The path for the external subprogram directory can be preset using setting data:
SD42700 $SC_EXT_PROG_PATH (program path for the EXTCALL external subprogram call)
The entire path of the program to be called along with the subprogram path or name specified
during programming is derived therefrom.
Note
If the program path is only specified using the appropriate programming, then SD42700 must
be empty!
Programming
An external subprogram is called by means of parts program command EXTCALL.
Syntax: EXTCALL("<path/><program name>")
Parameter:
<path>: Absolute or relative path data (optional)

Type: STRING
Basic functions
<program name>: The program name is specified without prefix "_N_".

The file extension ("MPF", "SPF") can be attached to program names
using the "_" or "." character (optional).
Type: STRING
Note
Path specification: Short designations
The following short designations can be used to specify the path:
● LOCAL_DRIVE: for local drive
● CF_CARD: for memory card
● USB: for USB front connection
CF_CARD: and LOCAL_DRIVE: can be alternatively used.
EXTCALL call with absolute path name

If the subprogram exists at the specified path, it will be executed following the EXTCALL call. If
it does not exist, program execution is canceled.
EXTCALL call with relative path name / without path name
In the event of an EXTCALL call with a relative path name or without a path name, the available
program memories are searched as follows:
● If a path name is preset in SD42700 $SC_EXT_PROG_PATH, the data specified in
the EXTCALL call (program name or with relative path name) is searched for first, starting
from this path. The absolute path is obtained from linking the following characters:
– The path name preset in SD42700
– The "/" character as a separator
– The subprogram path or name programmed in EXTCALL
● If the called subprogram is not found at the preset path, the data specified in the EXTCALL
call is then searched for in the user-memory directories.
● The search ends when the subprogram is found for the first time. If the search does not
produce any hits, the program is canceled.
Example
Execute from local drive
Main program:
Program code
N010 PROC MAIN
N020 ...
N030 EXTCALL ("ROUGHING")
N040 ...
N050 M30
Basic functions
2.14 Execution from external storage (EES) (option)
External subprogram:
Program code
N010 PROC ROUGHING
N020 G1 F1000
N030 X= ... Y= ... Z= ...
N040 ...
...
...
N999999 M17
The "MAIN.MPF" main program is stored in NC memory and is selected for execution.
The "SCHRUPPEN.SPF" or "SCHRUPPEN.MPF" subprogram to be subsequently loaded is
on the local drive in the directory "/user/sinumerik/data/prog/WKS.DIR/WST1.WPD".
The subprogram path is preset in SD42700:
SD42700 $SC_EXT_PROG_PATH = "LOCAL_DRIVE:WKS.DIR/WST1.WPD"
Note
Without the path being specified in the SD42700, the EXTCALL operation for this example
would have to be programmed as follows:
EXTCALL("LOCAL_DRIVE:WKS.DIR/WST1.WPD/SCHRUPPEN")
2.14.1 Function
Note
To use the function, the "Expanded CNC user storage" or "Execute from external storage
(EES)" licensed option is required!
Function
Using the EES (Execution from External Storage) function, users have the option of having the
NCK execute programs directly from an external program storage.
Basic functions
The following drives are available as external memory:
Drive Symbolic name 1) SINUMERIK 840D sl

NC Extend CF_CARD CF card of NCU
(previously "Lo‐ LOCAL_DRIVE or
cal drive") SYS_DRIVE Local hard disk of a PCU
USER CF CF_CARD -
LOCAL_DRIVE
Network drive
Statically managed USB drive
1)
For SINUMERIK 840D sl, the symbolic names LOCAL_DRIVE, CF_CARD, and SYS_DRIVE are
permanently assigned to the drive NC Extend (⇒ NC Extend can be addressed via LOCAL_DRIVE,
CF_CARD, and SYS_DRIVE).
NOTICE
Tool/workpiece damage caused by the USB flash drive
A USB flash drive cannot be recommended when executing an external program. A
communication abort to the USB flash drive during the execution of the program due to contact
problems, failure, abort through trigger or unintentional unplugging, results in an uncontrolled
stop of the machining. The tool and/or workpiece could be damaged.
Requirements
The following prerequisites apply when using EES:
● The "Expanded CNC user storage" or "Execute from external storage (EES)" licensed
option must be set.
● The drives, which are used at the control as external memory, must be configured as a
logical drives (see "Commissioning (Page 198)").
● A list of available IPCs is available under Available IPCs (Page 824).
Basic functions
Operating mode
Depending on the option available and the drive configuration, various EES operating modes
are possible. The active operating mode of a control is displayed using machine data MD18045
$MN_EES_MODE_INFO.
MD18045 Operating mode Option External memory

SINUMERIK 840D sl
=0 EES not active - -
=1 Local EES active 6FC5800-0AP77-0YB0 The use of EES on an NCU is limited to the expanded user
CNC user memory expan‐ memory (100 MB) of the CF card.
ded If EES is used on a PCU, the entire free memory can be
used by NC Extend.
EES via network or USB is not possible.
6FC5800-0AP12-0YB0 If EES is used on an NCU, with the additional option, the
additional HMI user memo‐ local user memory can be expanded up to 6 GB (depending
ry on CF card of NCU. on MD9111).
If EES is used on a PCU, the additional option is not re‐
quired.
=2 Global EES active 6FC5800-0AP75-0YB0 EES can be used for all available external storage.
Execution from external
storage (EES)
6FC5800-0AP12-0YB0 If EES is used on an NCU, with the additional option, the

additional HMI user memo‐ local user memory can be expanded up to 6 GB (depending
ry on CF card of NCU. on MD9111).
If EES is used on a PCU, the additional option is not re‐
quired.
=5 Local EES active The same as MD18045 = 1, only that on the expanded user memory a global part
+ program memory (Page 200) is set up.
Global part program
memory
=6 Global EES active The same as MD18045 = 2, only that on an external user memory a global part program
+ memory (Page 200) is set up.
Global part program
memory
Properties
The EES function can replace the "Execution from external (Page 191)" and "Executing
external subprograms (EXTCALL) (Page 192)" functions.
The EES function has the following advantages:
● Standard program handling throughout the system
● No restrictions regarding the commands that can be used
The restrictions on "execution from external source" and "execution of external
subprograms (EXTCALL)", e.g. no backward jumps, limitation of the jump distance of jump
commands by the size of the reload memory, are eliminated with EES.
Basic functions
● Programs can be moved between different program storages (NC, GDIR, external drive)
significantly easier.
● There are practically no restrictions regarding the part program size and the number of
programs (this is only limited by the capacity of the external data memory).
● Uniform syntax for the subprogram call, independent of the storage location of the
subprogram (an EXTCALL call is not required).
● Network drives can be used jointly by more than one station (PCU/NCU). Prerequisite is a
uniform drive configuration for these stations. This results in a uniform view of the programs
for all stations.
● Because of the uniform view of the external program storage for all stations, changes to the
programs stored there consistently apply to all stations.
2.14.2 Commissioning
2.14.2.1 Configuring the drives

To use the EES function, the drives used with the control system must be declared.
Further information
● Commissioning Manual, base software and operating software
● Operating Manual SINUMERIK Operate
After activating the new drive configuration, the programs can be freely distributed among the
available drives.
Note
All the previous drives may no longer be available in the newly created drive configuration.
Access to the programs on these drive is then no longer possible.
Remedy: First copy the programs stored on these drives to a drive that can still be accessed.
Note
Because protected cycles (_CPF files) are only executed from the NC part program memory for
system reasons, they cannot be stored for execution on an external program memory.
Basic functions
The previous NC part program memory with the MPF.DIR, SPF.DIR and WKS.DIR directories
is not absolutely necessary when using EES. A system can also be configured without using
the NC part program memory.
NOTICE
Executing programs that are not visible
Even if the NC part program memory was removed from the drive configuration, it is always
still available in the system itself. This especially means that when executing the program it is
possible that programs that still exist there are inadvertently executed from the SPF.DIR.
Remedy: If the system is configured without NC part program memory in the drive
configuration, any programs still stored there should be deleted manually.
If the NC part program memory is still to be used, then it should not be completely removed from
the system, only assigned an appropriate protection level when required.
Drives can be used jointly by multiple stations (PCU/IPC/NCU). A standard drive configuration
for these stations means that there is a standard program view that is independent of the
particular station.
Note
The memory card of an NCU/PPU cannot be used by several stations.
Example:
Several NCUs jointly use a program memory on the local hard disk of the PCU
(LOCAL_DRIVE).
3&8,3&
/ 2 &$ / B ' 5 , 9 (
1& 1& 1&
1&8 1&8 1&8
Basic functions
Note
If external program memories are used together at different stations in the EES mode, then the
following rules must be observed:
● A program cannot be simultaneously edited from several stations.
● Programs, which are being executed, can no longer be changed.
For operation with an external HMI, the drives must be configured on the external HMI! The
drive configuration (logdrive.ini) must be loaded into the corresponding NCU from the external
HMI. A softkey is available for the transfer on the dialog for the drive configuration.
In systems in which multiple NCs work together, the drive configuration must be identical for all
NCs. This is achieved by distributing the logdrive.ini file to all of the NCUs listed in the mmc.ini
file. The configurations existing there are therefore overwritten.
Further information
A list of PCU-Basesoftware can be obtained at:
● Commissioning Manual SINUMERIK 840D sl PCU-Basesoftware
● A list of available IPCs is available under Available IPCs (Page 824).
2.14.2.2 Global part program memory (GDIR)

When declaring the drives, one of the drives can be designated the global part program
memory (GDIR).
Further information
Operating Manual Universal/Turning/Milling/Grinding; Managing programs > Setting up drives
The system automatically creates the MPF.DIR, SPF.DIR and WKS.DIR directories on the
drive that acts as the GDIR. These three directories form the GDIR.
The GDIR only plays a role for the EES function. Depending on the drive configuration, the
GDIR replaces or extends the NC part program memory. However, it is not mandatory to set up
a GDIR for the EES operation.
The directories and files of the GDIR can be addressed in the part program in the same way as
in the passive file system. Therefore, a compatible relocation of an NC program with path
specification is possible for the passive file system to the GDIR.
The GDIR extends the search path for subprograms, which are called without specifying an
absolute path.
GDIR replaces the NC part program memory

If the NC part program memory is completely empty in the MPF.DIR, SPF.DIR and WKS.DIR
directories, then the GDIR replaces the NC part program memory. The previous NC search
path is emulated 1:1 by the GDIR.
Basic functions
Selecting the main program on an external archive/data storage medium

Search sequence for the subprograms:
1. Actual directory on an external archive/data storage medium
2. SPF.DIR in the GDIR memory
3. The drive referenced using CALLPATH
4. Cycles
GDIR extends the NC part program memory

When the NC part program memory is not empty in the MPF.DIR, SPF.DIR and WKS.DIR
directories, then the search sequence for the subprograms depends on where the main
program is archived (active directory).
Selecting the main program in the NC part program memory (MPF.DIR or xxx.WPD in
WKS.DIR)
1. Actual directory in the NC part program memory
2. SPF.DIR in the NC part program memory
4. Cycles
Selecting the main program on an external archive/data storage medium released for EES
1. Actual directory on an external archive/data storage medium
2. SPF.DIR in the NC part program memory
3. SPF.DIR in GDIR
5. Cycles
Note
To define the search sequence, also see MD11625 $MN_FILE_ONLY_WITH_EXTENSION
and MD11626 $MN_CYCLES_ONLY_IN_CYCDIR!
Note
An external drive can also be referenced using the CALLPATH statement.
Basic functions
2.14.2.3 Settings for file handling in the part program for EES
Program names unique throughout the system

If external program memories are used together at different stations in EES mode, file
operations performed simultaneously on different stations (WRITE, DELETE, …) result in
access conflicts. To avoid such access conflicts, we recommend setting up a name space for
file names on each station that is unique throughout the system.
Name space unique throughout the system

A name space for file names that is unique throughout the system is achieved, for example, by
associating the file names with the EES-specific name of the NC parameterized in the machine
data and the channel number of the channel in which the program is executed. For example,
when the program is executed, the following code generates the file name (MYFILE
_NC1_1.SPF), which is unique throughout the system, by appending the EES-specific name of
the NC (NC1) and the channel number (channel 1) to the program name.
$MN_EES_NC_NAME="NC1"
N10 DEF STRING[31] FILENAME
N20 FILENAME="MYFILE_" << $MN_EES_NC_NAME << "_" << $P_CHANNO <<
".SPF"
The EES-specific name of the NC is set in the NC-specific machine data:
MD10125 $MN_EES_NC_NAME = <NC name>
Note
Name of the NC unique throughout the system
To avoid access conflicts, the EES-specific name of the NC must be unique throughout the
system. The responsibility for this resides exclusively with the user/machine manufacturer.
When calling the program, only search for files with file ID
In order to speed up the program search for subprogram calls during EES operation, we
recommend that you limit the search to files with file ID (e.g. SPF, MPF, etc.):
MD11625 $MN_FILE_ONLY_WITH_EXTENSION = 1
Note
MD11625 has no effect on the program search when processing external subprograms with
EXTCALL.
Further information
For further information describing the search path to call the subprogram, see "NC
Programming" Programming Manual.
Basic functions
Only search for programs with interface in the cycle directories

In order to speed up the program search for subprogram calls during EES operation, we
recommend the search for subprograms which have created an interface description (by
means of PROC statement), and whose interface description was generated from the one of
the cycle directories (CUS, CMA, CST) be limited to the cycle directories:
MD11626 $MN_CYCLES_ONLY_IN_CYCDIR = 1
Note
MD11626 has no effect on subprograms whose interface was created using an EXTERNAL
declaration. A search is made in all program directories.
NOTICE
No search success for cycles outside the cycle directories
Cycles in the current directory and global subprogram directory are no longer found with the
setting MD11626 = 1!
Remedy: Always store cycles in the cycle directories.
2.14.2.4 Memory configuration
Reducing the end user program memory in the passive file system
With active EES, the end user program memory in the passive file system can be reduced:
MD18352 $MN_MM_U_FILE_MEM_SIZE (end user memory for part programs / cycles / files)
The released memory can then be used, for example, for tool data or manufacturer cycles
(MD18353 $MN_MM_M_FILE_MEM_SIZE).
Further information
For detailed information regarding memory configuration, see Memory configuration
(Page 799).
Releasing reload memory

The EES function can replace the "Execution from external source" and "Execution of external
subprograms (EXTCALL)" functions.
In order to execute subprograms from part programs with EXTCALL calls with EES instead of
the "Execution of external subprograms (EXTCALL)" function, the EXTCALL calls must be
changed to CALL calls, and the path specifications adapted if required.
After a complete changeover, the reload memory (FIFO buffer) required for the "Execution from
external source" and "Execution of external subprograms (EXTCALL)" can be released:
MD18362 $MN_MM_EXT_PROG_NUM (number of externally executed program levels
executable simultaneously) = 0
Basic functions
2.15 Process Datashare - output to an external device/file
Teach in
In the EES mode, it is not possible to use the "Teach In" function in the AUTOMATIC operating
mode.
2.15.1 Function
With the "Process Datashare" function, it is possible to write data from a part program to an
external device or to an external file; for instance, to log production data or to control additional
equipment at a control system.
Availability
The function is available:
● Only in the real NC (not in the SNC and VNC simulation software).
● Only in part programs (not in synchronized actions).
● Parallel in all machining channels of the NC for all available (configured) output devices.
External devices/files
External devices/files can be:
● Files on the local memory card
The local memory card represents the memory which is referenced by HMI with the
symbolic identifier LOCAL_DRIVE.
Note
For SINUMERIK 840D sl, the option "Additional xxx MB HMI user memory on memory card
of the NCU" is required for output to the LOCAL_DRIVE device.
● Files on a network drive

● RS-232-C
Note
For SINUMERIK 840D sl, the NCU option module RS 232 interface is required for output at
the RS-232-C.
Basic functions
Maximum number of opened external devices

More than one external device/file can also be assigned in a part program / channel. A
maximum of ten output devices can be simultaneously opened across all NC channels. In
addition, there are two entries reserved for Siemens cycles.
A maximum of five jobs may be active simultaneously to the output devices.
Usage mode
For each output device, when opening the device, it can be specified as to whether the device
is to be exclusively used by just one channel or whether several channels can output to the
device ("shared" mode).
Behavior for part program end / channel reset

With part program end and channel reset, all of the external devices/files that have been
opened in the channel are closed.
Use of the function for data transfer to the control
NOTICE
Data security
If the Process Datashare function is used to send data from an external device via the Ethernet
interface X130 to the control, there is the possibility that the data on the control could be
falsified by a third-party and is no longer consistent. When using the function, ensure that the
network is protected against access by third-parties.
The external devices to be used are configured in the /oem/sinumerik/nck/extdev.ini or /user/
sinumerik/nck/extdev.ini file. If both files are available, then the entries in the user area have
priority. The file can be updated in the operating area COMMISSIONING under
SYSTEMDATEN/CF card.
Note
It is not necessary to configure in the extdev.ini file when using LOCAL_DRIVE and
CYC_DRIVE. The two devices are always available as soon as the corresponding option is set
or the user CompactFlash card is available.
The external devices to be used are defined/listed in the section [ExternalDevices] of the
extdev.ini file. A serial device (/dev/v24) and up to nine files or directories (/dev/ext/1…9) can
be specified as device. The Linux notation is used when specifying devices. Lines, which start
with ";", are comments and are overread.
Basic functions
With the exception of /dev/v24, the devices can be declared as directory path - terminated with
an attached "/" – or as file path – i.e. with attached fully qualified path, ending with a file name
(without a terminating "/"). When used in a part program, a file name (path) must also be
specified for a device with directory path.
Except for /dev/v24, a device is defined using the three items separated by a comma for
"Server", "Path" and the optional "Write mode".
For the files or directories (this then applies to all files in the directory), it can be specified as to
whether the file should be overwritten after it has been opened ("O" = Overwrite) or whether the
outputs should be attached to the file ("A" = Append). The default value is "A". A file/directory
that does not exist is newly created when opening.
For the device V.24 interface, only the settings for baud rate, data bits, stop bits, parity, protocol
and possibly end are specified in this sequence.
For files that are generated/saved on the LOCAL_DRIVE, LOCAL_DRIVE_MAX_FILESIZE
data can be used to set a maximum file size in bytes - this is then valid as standard for all files.
The file size is checked when executing an EXTOPEN command in Append mode. Optionally,
the write mode ("O" = Overwrite, "A" = Append) can be defined using the
LOCAL_DRIVE_FILE_MODE data. The default value is "A".
Note
A copy template for the extdev.ini configuration file is available in the /siemens/sinumerik/nck
directory.
Note
Changes to the extdev.ini file only become effective after an NC restart/boot.
Note
USB devices
For SINUMERIK 840D sl, only statically connected USB interfaces of a TCU can be configured
as USB devices. The configuration is realized using the SERVER:/PATH type as specification
for "Server" in the sense above, whereby SERVER is the TCU name and /PATH designates the
USB interface. The USB interfaces of a TCU are addressed using "dev0-0", "dev0-1", "dev1-0".
The path data always starts with "/Partition", whereby the partition can be specified using a two-
digit partition number or its partition name – and where required, is extended with a file path up
to the required target, e.g.:
/dev/ext/8 = "TCU4:/dev0-0, /01/, A"
/dev/ext/8 = "TCU4:/dev0-0, /01/mydir.dir/"
/dev/ext/8 = "TCU4:/dev0-0, /myfirstpartition/Mydir.dir/myfile.txt, O"
Example
[ExternalDevices]
; Comment line
; example for V24
Basic functions
; /dev/v24 = "9600, 8, 1, none, rts [, etx]"

; examples for network drives
; /dev/ext/1 = "//[USERNAME[/DOMAIN][%PASSWORD]@]SERVER/SHARE/, /, A"
; /dev/ext/2 = "//[USERNAME[/DOMAIN][%PASSWORD]@]SERVER/SHARE, /myfile.txt, O"
; /dev/ext/3 = "//[USERNAME[/DOMAIN][%PASSWORD]@]SERVER/SHARE, /mydir/, A"
; /dev/ext/4 = "SERVER:/dev0-0, /01/, A"
;…
; SIEMENS only
; /dev/cyc/1= "//[USERNAME[/DOMAIN][%PASSWORD]@]SERVER/SHARE, /mydir/, A"
; /dev/cyc/2= "//[USERNAME[/DOMAIN][%PASSWORD]@]SERVER/SHARE/mydir, /, A"
LOCAL_DRIVE_MAX_FILESIZE = 50000
LOCAL_DRIVE_FILE_MODE = "O"
Effectiveness of the EXTOPEN parameter <WriteMode>

By specifying the write mode, when configuring in the extdev.ini file as well as for an EXTOPEN
call, authorization conflicts can occur, which are then acknowledged with EXTOPEN - possibly
with error:
Value from extdev.ini Value of the EXTOPEN parameter

"OVR" "APP" -
"O" O Error O
"A" Error A A
- O A A
Explanation:
O: "Overwrite" mode is active.
A: "Append" mode is active.
Error: EXTOPEN call is acknowledged with error.
LOCAL_DRIVE: File attribute

The files created with EXTOPEN on LOCAL_DRIVE are allocated the following file attributes:
● Owner: "user" Read/write rights set

● Group: "operator" Read/write rights set
Basic functions
2.15.3 Programming
The writing of data from a part program to an external device/file is performed in three steps:
1. Open the external device/file
The external device/file is opened for the channel for writing using the EXTOPEN command.
2. Writing data
The output data can be processed using the string functions of the NC language, e.g.
SPRINT. The WRITE command is used for writing.
3. Close the external device/file
The external device/file assigned in the channel is released again using the EXTCLOSE
command, when the end of the program is reached (M30) or for a channel reset.
Syntax
DEF INT <Result>
DEF STRING[<n>] <Output>
…
EXTOPEN(<Result>,<ExtDev>,<SyncMode>,<AccessMode>,<WriteMode>)
…
<Output>="data output"
WRITE(<Result>,<ExtDev>,<Output>)
…
EXTCLOSE(<Result>,<ExtDev>)
Basic functions
Meaning
EXTOPEN: Pre-defined procedure to open an external device/file

<Result>: Parameter 1: Result variable
By using the result variable value, it can be evaluated in the program as to wheth‐
er the operation was successful and processing is then appropriately continued.
Type: INT
Values: 0 No error
1 External device cannot be opened
2 External device is not configured
3 External device with invalid path configured
4 No access rights for external device
5 Usage mode: External device already "exclusively" occupied
6 Usage mode: External device already being "shared"
7 File length longer than LOCAL_DRIVE_MAX_FILESIZE
8 Maximum number of external devices has been exceeded
9 Option for LOCAL_DRIVE not set
11 Reserved
12 Write mode: Data contradicts extdev.ini
16 Invalid external path has been programmed
22 External device not mounted
Basic functions
<ExtDev>: Parameter 2: Symbolic identifier for the external device/file to be opened

Type: STRING
The symbolic identifier comprises:
1. the logical device name
2. where relevant, followed by a file path (attached using "/").
The following logical device names have been defined:
"LOCAL_DRIVE": Local CF card (pre-defined)
"CYC_DRIVE": Reserved drive name for use in SIEMENS cycles (pre-
defined)
"/dev/ext/1", ... Available network drives
"/dev/ext/9": Note:
It is necessary to configure in the extdev.ini file!
"/dev/cyc/1", Reserved drive names for use in SIEMENS cycles
"/dev/cyc/2": Note:
It is necessary to configure in the extdev.ini file!
File path:
● A file path must be specified for "LOCAL_DRIVE" and "CYC_DRIVE" e.g.
"LOCAL_DRIVE/my_dir/my_file.txt"
● The logical device names "/dev/ext/1...9" and "/dev/cyc/1...2" can be config‐
ured:
– To already refer to a file, in which case only the logical device names may
be specified, e.g.:
"/dev/ext/4"
– Or to a directory, in which case a file path must be specified, e.g.:
"/dev/ext/5/my_dir/my_file.txt"
Note:
For the logical device names "/dev/ext/1...9", "/dev/v24" and "/dev/cyc/1...2" up‐
percase/lowercase is ignored; uppercase/lowercase is significant for specifying a
path to a file. Only uppercase letters are permissible for "LOCAL_DRIVE" and
"CYC_DRIVE".
<SyncMode>: Parameter 3: Processing mode for the WRITE commands to this device/file
Type: STRING
Values: "SYN": Synchronous writing
Program execution is stopped until the write operation
has been completed.
Successfully completing the synchronous write opera‐
tion can be checked by evaluating the error variables of
the WRITE command.
"ASYN": Asynchronous writing
Program execution is not interrupted by the WRITE
command.
Note.
In this mode, the result variable of the WRITE command
does not provide any information and always has the
value 0 (no error). In this particular mode, there is no
certainty that the WRITE command was successful.
Basic functions
<AccessMode>: Parameter 4: Usage mode for this device/file

Type: STRING
Values: "SHARED": Device/file is requested in the "shared" mode. Other
channels can also use the device, i.e. also open in this
mode.
"EXCL": Device/file is exclusively used in the channel; no other
channel can use the device.
<WriteMode>: Parameter 5: Write mode for the WRITE commands to this file/device (optional)
Type: STRING
Values: "APP": Attaching
The file is always kept regarding its contents; write calls
are attached at the end.
"OVR": Overwrite
The contents of the file are deleted and re-generated
using the subsequent write calls.
Note:
Using this parameter, the write mode configured in the extdev.ini file cannot be
overwritten. In the case of a conflict, then the EXTOPEN call is acknowledged
with error.
WRITE: Pre-defined procedure to write output data
EXTCLOSE: Pre-defined procedure to close an external device/file that has been opened
<Result>: Parameter 1: Result variable
Type: INT
Values: 0 No error
16 Invalid external path has been programmed
21 Error when closing the external device
<ExtDev>: Parameter 2: Symbolic identifier for the external device/file description to be
closed, see EXTOPEN!
Note:
The identifier must be identical to the identifier specified in the EXTOPEN call!
Example
Program code
N10 DEF INT RESULT
N20 DEF BOOL EXTDEVICE
N30 DEF STRING[80] OUTPUT
N40 DEF INT PHASE
N50 EXTOPEN(RESULT,"LOCAL_DRIVE/my_file.txt","SYN","SHARED")
N60 IF RESULT > 0
N70 MSG("Error for EXTOPEN:" << RESULT)
N80 ELSE
N90 EXTDEVICE=TRUE
Basic functions
2.16 System settings for power-up, RESET / part program end and part program start
Program code
N100 ENDIF
…
N200 PHASE=4
N210 IF EXTDEVICE
N220 OUTPUT=SPRINT("End phase: %D",PHASE)
N230 WRITE(RESULT,"LOCAL_DRIVE/my_file.txt",OUTPUT)
N240 ENDIF
…
Effect on continuous path mode

The EXTOPEN, WRITE and EXTCLOSE commands trigger a preprocessing stop and
therefore interrupt the continuous path mode.
Behavior during block search

During "block search with calculation" with WRITE, no output is made. However, the EXTOPEN
and EXTCLOSE commands are collected and set active with NC start after the search target
was reached. The following WRITE commands therefore find the same environment as for the
normal program processing.
For a block search with calculation in the (SERUPRO) "Program test" mode, EXTOPEN,
WRITE and EXTCLOSE are executed just the same as for normal program processing.
2.16 System settings for power-up, RESET / part program end and part
program start
2.16.1 System settings for power-up, RESET / part program end and part program start
Concept
The behavior of the control can be set via the machine data for the following events:
● Run-up (power-on)
● Reset / part program end
Basic functions
The control-system response after: Can be set with:

Run-up (power on) *)
MD20144 $MC_TRAFO_MODE_MASK
MD20150 $MC_GCODE_RESET_VALUES
RESET / part program end MD20110 $MC_RESET_MODE_MASK
MD20150 $MC_GCODE_RESET_VALUES
MD20152 $MC_GCODE_RESET_MODE
Part program start MD20112 $MC_START_MODE_MASK
*)
see also POWER ON (Page 390)
Basic functions
System settings after run-up

MD20110 $MC_RESET_MODE_MASK, bit 0 = 0 or 1
%RRWLQJ
32:(521
%LW 7UDQVIRUPDWLRQDFWLYH
0' DFFWR0'0'%LW0'%LW
5(6(7B02'(B0$6. *HRD[LVLQWHUFKDQJHDFWLYH
%LW 'HIDXOW DFFWR0'ZLWK0'
VHWWLQJ
%LW
%LW
%LW
7KHWRROOHQJWK
0'
%LWDQGELW FRPSHQVDWLRQ
VHOHFWHGEHIRUH32:(521
UHPDLQVDFWLYH
%LW
7RROOHQJWKFRPSHQVDWLRQDFWLYH
DFFWR0'0'
0'
7UDQVIRUPDWLRQRII
*FRGHVDFFWR0'0&B*&2'(B5(6(7B9$/8(6
&RXSOHGPRWLRQJURXSVLVWULJJHUHG
7DQJHQWLDOIROORZXSLVQRWDFWLYH
6\QFKURQL]HGVSLQGOHFRXSOLQJLVQRWDFWLYH
$[LDOUHYROXWLRQDOIHHGUDWHRIISDWKDQGV\QFKURQL]HGD[HVEDFNWRPDVWHUVSLQGOH
*HRPHWU\D[LVDVVLJQPHQWDFFWR0'0&B$;&21)B*(2$;B$66,*1B7$%
0DVWHUYDOXHFRXSOLQJLVQRWDFWLYH
%DVLFIUDPHLVGHVHOHFWHG
(OHFWURQLFJHDUER[LVQRWDFWLYH
0DVWHUVSLQGOHEDVLFSRVLWLRQDFFWR0'0&B63,1'B'()B0$67(5B63,1'
0DVWHUWRROKROGHUEDVLFSRVLWLRQDFFWR0'0&B722/B0$1*(0(17B722/+2/'(5
5HIHUHQFHD[LVDFFWR0'0&B',$0(7(5B$;B'()
5(6(7SDUWSURJUDPHQG
Figure 2-7 System settings after run-up (power-on)
Basic functions
System settings after reset / part program end and part program start
MD20110 $MC_RESET_MODE_MASK, bit 0 = 0 or 1
5(6(7SDUWSURJUDPHQG
%LW *FRGHVDFFWR0'DQG0'
0'ELWDUHHYDOXDWHGLH
0'
WKHIXQFWLRQDVVLJQHGWRWKHUHOHYDQWELWV
5(6(7B02'(B0$6.
HLWKHUUHWXUQVWRLWVUHVHWSRVLWLRQRU
%LW
'HIDXOW VWD\VLQLWVFXUUHQWSRVLWLRQVHHWDEOHV
VHWWLQJ EHORZ
%LW
7KHFXUUHQWVHWWLQJVDUHUHWDLQHG
3DUWSURJUDPVWDUW
*FRGHVDFFWR0'
7UDQVIRUPDWLRQRII
&RXSOHGPRWLRQRII
7DQJHQWLDOIROORZXSRII 7KHVHWWLQJVDFWLYDWHGE\5(6(7
6\QFKURQL]HGVSLQGOHRII EHFRPHYDOLG
*HRPHWU\D[LVDVVLJQPHQWDFFWR0'
0DVWHUYDOXHRII
$[LDOUHYROXWLRQDOIHHGUDWHRII
5HVHUYHGEDVLFIUDPHRII
0DVWHUVSLQGOHDFFWR0'
0DVWHUWRROKROGHURII
5HIHUHQFHD[LVDFFWR0'
%LW
%LW
0' )XQFWLRQWDNHVDFFRXQWRI5(6(7SRVLWLRQ
67$57B02'(B0$6.
%LW
%LW
5HIHUHQFHD[LVLVUHWDLQHG
%LW GHIDXOWVHWWLQJ
%LW7KHFXUUHQWVHWWLQJVDUHUHWDLQHG
%LW)XQFWLRQWDNHVDFFRXQWRI5(6(7SRVLWLRQ
,QWHUSUHWDWLRQRIVWSDUWSURJUDPEORFN
Figure 2-8 System settings after reset / part program end and part program start
Basic functions
G command effective after run-up and reset / part program end

The G code that is effective in every G group after run-up (power-on) and reset / part program
end is set in the following machine data:
MD20150 $MC_GCODE_RESET_VALUES[<G group>] = <default-G code>
MD20152 $MC_GCODE_RESET_MODE[<G group>] = <value>
Value Description: Per G group

0 The default G command from MD20150 $MC_GCODE_RESET_VALUES takes effect.
1 The last active/current G command takes effect
Control basic setting after run-up, reset / part program end and part program start
The control basic setting after run-up (power-on), reset / part program end and part program
start is defined in the following machine data:
● MD20110 $MC_RESET_MODE_MASK (definition of the control basic setting after run-up
and reset / part program end)
● MD20112 $MC_START_MODE_MASK (definition of the control basic setting after part
program start)
Further information
Detailed machine data description
Relevant machine data

MD20120 $MC_TOOL_RESET_VALUE Tool length compensation during run-up, reset / part program
end
MD20121 $MC_TOOL_PRESEL_RESET_VALUE Preselect tool on Reset
MD20130 $MC_CUTTING_EDGE_RESET_VALUE Tool cutting-edge length compensation on run-up
MD20140 $MC_TRAFO_RESET_VALUE Run-up transformation data block
MD20144 $MC_TRAFO_MODE_MASK Selection of the kinematic transformation function
MD20150 $MC_GCODE_RESET_VALUES Basic setting of the G groups
MD20152 $MC_GCODE_RESET_MODE Reset behavior of the G groups
MD21330 $MC_COUPLE_RESET_MODE_1 Coupling cancellation response
MD20050 $MC_AXCONF_GEOAX_ASSIGN_TAB Assignment of geometry axis to channel axis
MD20118 $MC_GEOAX_CHANGE_RESET Allow automatic geometry axis change
Example
Activate reset setting on reset:

● MD20110, bit 0 = 1
● MD20112 = 0
Basic functions
Transformation remains with reset / part program start:

● MD20110, bit 0 = 1
● MD20110, bit 7 = 1
● MD20112 = 0
Tool length compensation is retained after reset / part program start:

● MD20110, bit 4 = 1
● MD20110, bit 6 = 1
● MD20112 = 0
Active level (bit 4) and settable frame (bit 5) remain active after reset and are reset on part
program start:
● MD20110, bit 4 = 1
● MD20110, bit 5 = 1
● MD20112, bit 4 = 1
● MD20112, bit 5 = 1
Note
MD20110/MD20112, bit 5 and bit 6
If MD20110/MD20112 are parameterized so that tool length compensation or a frame is
active on a part program start in the automatic or MDI mode, the first programming of the
axes must use absolute measurements (because of the traversing of the offset).
Exception: With MD42442/MD42440 the offsetting process for G91 is suppressed.
2.16.2 Tool withdrawal after POWER ON with orientation transformation
Function
If a part program with a machining operation with tool orientation is aborted due to a power
failure or reset, it is possible to select the previously active transformation and generate a frame
in the direction of the tool axis after the control has run up (power on). The tool can then be
retracted in JOG mode by means of a retraction movement towards the tool axis.
Requirement
The active measuring systems must have a machine reference for all the machine axes
involved in the transformation. See Function Manual "Axes and Spindles", Section "Automatic
restoration of the machine reference".
Basic functions
Parameterization
The following machine data must be set so that the last active transformation is retained after
POWER ON:
● MD20144 $MC_TRAFO_MODE_MASK, bit 1 = 1
● MD20110 $MC_RESET_MODE_MASK, bit 0 = 1
● MD20110 $MC_RESET_MODE_MASK, bit 7 = 1
See also Section "System settings for power-up, RESET / part program end and part program
start (Page 212)".
Programming
Wait for machine reference WAITENC

With the command WAITENC, the system waits channel-specific in a program until there is a
valid machine reference for all the active measuring systems of the parameterized axes. See
the "Requirement" section above. The parameter assignment of the axes is performed via:
MD34800 $MA_WAIT_ENC_VALID = 1
Application
In the user program (…/_N_CMA_DIR/_N_PROG_EVENT_SPF) to be called event-controlled
when running up (requirement: MD20108 bit 3 = 1), the system must wait using the command
WAITENC until the valid axis positions are available.
A frame that positions the tool axis in the direction of the X, Y or Z axis can then be generated
using the NC language command TOROTX/TOROTY/TOROTZ.
Example
Orientation transformation and orientation axes with incremental encoders.
Configuration: Meaning:
MD10720 $MN_OPERATING_MODE_DEFAULT [ 0 ] = 6 Run-up in JOG mode.
MD30240 $MA_ENC_TYPE [ 0, <axis>] = 1 Incremental measuring system.
MD34210 $MA_ENC_REFP_STATE [ 0, <axis>] = 3 Enable the restoration of axis positions for incre‐
mental encoders.
MD20108 $MC_PROG_EVENT_MASK = ’H9’ Activate event-controlled using program
PROG_EVENT during run-up and at the start of
the part program.
MD20152 $MC_GCODE_RESET_MODE [ 52 ] = 1 Obtain TOFRAME via reset.
MD20110 $MC_RESET_MODE_MASK = ’HC1’ Obtain transformation and tool offset via reset.
MD20144 $MC_TRAFO_MODE_MASK = ’H02’ Obtain transformation via POWER OFF.
Basic functions
Event-driven user program (…/_N_CMA_DIR/_N_PROG_EVENT_SPF):
; Example with activation of the frame, which aligns the WCS in the tool direction,
; when running up and resetting with part program start.
IF $P_PROG_EVENT == 4 ; Run-up.
IF $P_TRAFO <> 0 ; Transformation was selected.
WAITENC ; Wait for valid axis positions of the orientation axes.
TOROTZ ; Rotate the Z axis of the WCS towards the tool axis.
ENDIF
M17
ENDIF
IF $P_PROG_EVENT == 1 ; Part program start.
TOROTOF ; Reset tool frame.
RET
ENDIF
The WAITENC command essentially corresponds to the following program sequence (example
for 5-axis machine with AB kinematics):
WHILE TRUE ; Waiting for measuring system.

IF (($AA_ENC_ACTIVE[X]==TRUE) AND ($AA_ENC_ACTIVE[Y]
==TRUE) AND ($AA_ENC_ACTIVE[Z]==TRUE) AND ($AA_ENC_ACTIVE[A]
==TRUE) AND ($AA_ENC_ACTIVE[B]==TRUE)) GOTOF GET_LABEL
ENDIF
G4 F0.5 ; Wait time 0.5 s
ENDWHILE
:Position synchronization
GET_LABEL: GET(X,Y,Z,A,B,)
Continuing machining
AUTOMATIC mode
For automatic execution of programs in the AUTOMATIC mode, all the machine axes, whose
actual position of the active measuring system has been restored, must be referenced.
MDI mode and overstore

In the MDI mode and for the overstore function, machining can also be performed, without
referencing the axes, with restored positions. To do this, NC start with restored positions must
be enabled explicitly for a specific channel:
MD20700 $MC_REFP_NC_START_LOCK = 2
Boundary condition
Axes with incremental encoders and without actual value buffering

It is to be assumed that axes with incremental encoders and without actual value buffering are
clamped with sufficient speed in the event of a power failure to prevent them drifting from their
last position setpoint.
Basic functions
2.17 Replacing functions by subprograms
2.17.1 Overview
Function
User-specific auxiliary functions (e.g. M101) do not trigger any system functions. They are only
output to the NC/PLC interface. The functionality of the auxiliary function must be implemented
by the user / machine manufacturer in the PLC user program. A description will be provided as
to how a user-specific subprogram call can be configured (replacement subprogram) instead
of the output to NC/PLC interface, which is the default setting.
Function M101 is then still programmed in the part program. However, when executing the part
program, the substitute subprogram is called. Therefore, the NC replaces the function by a
subprogram call. This results in the following advantages:
● When adapting to the production process, an existing, tested and proven part program can
still be used, unchanged. The changes required are then shifted into the user-specific
subprograms.
● The functionality can be implemented within the substitute subprogram with the full
functional scope of the NC language.
● The communication overhead between NC and PLC is not required.
Functions that can be replaced

The following functions can be replaced by subprograms:
Auxiliary functions
M Switching functions
T Tool selection
TCA Tool selection independent of the tool status
D Tool offset
DL Additive tool offset
Spindle-related functions during active synchronous spindle coupling

M40 Automatic gear stage change
M41 - M45 Gear stage selection 1 ... 5
SPOS Spindle positioning
SPOSA Spindle positioning
M19 Spindle positioning
Basic functions
2.17.2 Replacement of M, T/TCA and D/DL functions
2.17.2.1 Replacement of M functions
General Information
The following conditions are applicable for replacing the M functions:
● Per block only one M function is replaced.
● A block in which an M function is to be replaced, must not contain the following elements:
– M98
– Modal subprogram call
– Subprogram return
– Part program end
● M functions that trigger system functions must not be replaced by a subprogram (see
Section "Non-replaceable M functions").
Parameterization
M function and subprogram

M functions and the replacement subprograms are parameterized in the following machine
data:
● MD10715 $MC_M_NO_FCT_CYCLE[<Index>] = <M function number>
● MD10716 $MC_M_NO_FCT_CYCLE_NAME[<Index>] = "<subprogram name>"
The M function and the corresponding replacement subprogram are connected through the
same index.
Example: M function M101 is replaced by subprogram SUB_M101 and M function M102 by
SUB_M102:
MD10715 $MC_M_NO_FCT_CYCLE[ 0 ] = 101

MD10716 $MC_M_NO_FCT_CYCLE_NAME[ 0 ] = "SUB_M101"
MD10715 $MC_M_NO_FCT_CYCLE[ 1 ] = 102

MD10716 $MC_M_NO_FCT_CYCLE_NAME[ 1 ] = "SUB_M102"
System variable for transferring information

For a freely selectable M function, information regarding the M function that has been replaced
and additional functions (T, TCA, D, DL) for evaluation in the replacement subprogram are
made available via the system variable (see Section "System variable (Page 226)"). The data
contained in the system variables refers to the block in which the M function to be replaced is
programmed.
Basic functions
The M function is selected with the index of machine data MD10715

$MC_M_NO_FCT_CYCLE[<Index>] in which the M function to be replaced has been
parameterized:
MD10718 $MC_M_NO_FCT_CYCLE_PAR = <Index>
Note
For an M function replacement with transfer of information via system variable, the address
extension and function value of the M function must be programmed as constant values.
Permissible programming:
● M<function value>
● M=<function value>
● M[<address extension>]=<function value>
Illegal programming:
● M=<variable1>
● M[<variable2>]=<variable1>
Programming
Rules for replacing M functions:
● The replacement subprogram is called at the block end
● Within the replacement subprogram, no M functions are replaced
● In an ASUB, the M function is also replaced if the ASUB was started within the replacement
subprogram.
M functions that cannot be replaced

The following M functions trigger system functions as pre-defined auxiliary functions and
must not be replaced by a subprogram:
● M0 ... M5
● M17, M30,
● M19
● M40 ... M45
● M98, M99 (only for MD18800 $MN_MM_EXTERN_LANGUAGE ≠ 0)
User-specific M functions parameterized via machine data must also not be replaced by a
subprogram as they also trigger system functions.

MD10714 $MN_M_NO_FCT_EOP M function for spindle active after RE‐
SET
MD10804 $MN_EXTERN_CHAN_M_NO_SET_INT M function for ASUB activation (exter‐
nal mode)
Basic functions

MD10806 $MN_EXTERN_CHAN_M_NO_DISABLE_INT M function for ASUB deactivation (ex‐
ternal mode)
MD10814 $MN_EXTERN_M_NO_MAC_CYCLE Macro call via M function
MD20094 $MC_SPIND_RIGID_TAPPING_M_NR M function for switchover to controlled
axis mode
MD20095 $MC_EXTERN_RIGID_TAPPING_M_NR M function for switchover to controlled
axis mode (external mode)
MD22254 $MC_AUXFU_ASSOC_M0_VALUE Additional M function for program stop
MD22256 $MC_AUXFU_ASSOC_M1_VALUE Additional M function for conditional
stop
MD26008 $MC_NIBBLE_PUNCH_CODE Definition of M functions (for nibble-spe‐
cific)
MD26012 $MC_PUNCHNIB_ACTIVATION Activation of punching and nibbling
functions
Note
Exception
The M function parameterized with MD22560 $MC_TOOL_CHANGE_M_CODE (tool change
with M function) must not be replaced with a subprogram.
2.17.2.2 Replacing T/TCA and D/DL functions
For replacing functions T, TCA, D and DL, the following supplementary conditions apply:
● A maximum of one function replacement is active per block.
● A block with the function replacement must not contain the following elements:
– M98
– Modal subprogram call
– Subprogram return
– Part program end
● If the multitool slot number is programmed with address MTL for the multitool select with
T = slot number, the T replacement also replaces the MTL address. The programmed
values can be queried in the replacement subprogram using the $C_MTL_PROG and
$C_MTL system variables.
Basic functions
Parameterization: Replacement subprogram

The replacement subprogram is specified function-specific in the machine data:
Function Machine data

T MD10717 $MN_T_NO_FCT_CYCLE_NAME
TCA MD15710 $MN_TCA_CYCLE_NAME
D/DL MD11717 $MN_D_NO_FCT_CYCLE_NAME
Note
It is recommended that the same subprogram is used to replace T, TCA and D/DL functions.
Parameterization: Behavior regarding D or DL function with simultaneous T function

When D or DL and T functions are simultaneously programmed in a block, the D or DL number
is either transferred as parameter to the replacement subprogram or the D or DL function is
executed before calling the replacement subprogram. The behavior is configurable via:
MD10719 $MN_T_NO_FCT_CYCLE_MODE (parameterization of the T function replacement)
Bit Value Meaning

0 0 The D or DL number is available in the subprogram in the form of a system variable
(initial state).
1 The D or DL number is calculated directly in the block.
Note:
This function is only active if the tool change was configured with M function:
MD22550 $MC_TOOL_CHANGE_MODE = 1
otherwise the D or DL values are always transferred.

The replacement subprogram is provided with all of the information relevant to the functions
programmed in the block via system variables (see Section "System variable (Page 226)").
The data contained in the system variables refers to the block in which the function to be
replaced was programmed.
Parameterization: Time that the replacement subprogram is called

The call time of the replacement subprogram is set via:
Basic functions
MD10719 $MN_T_NO_FCT_CYCLE_MODE, bit 1 and bit 2
Bit 2 Bit 1 Time that the replacement subprogram is called

0 0 At the end of the block
After the replacement subprogram has been executed, the interpretation is resumed
with the program line following the line that triggered the replacement operation.
0 1 At block start
After the replacement subprogram has been executed, the program line, which re‐
sulted in the replacement subprogram being called, is interpreted. The T address and
the D or DL address and the M function for the tool change are no longer processed.
1 - At block start and block end
The replacement program is called twice.
System variable for the call time

System variable $P_SUB_STAT can be used to read whether the substitution is active, and if
so, when the replacement subprogram – referred to the block – was called up:
Value Meaning
0 Replacement not active
1 Replacement active, subprogram call is made at the block start
2 Replacement active, subprogram call is made at the block end
Example: Replacement of the T function
Parameterization Meaning
MD22550 $MC_TOOL_CHANGE_MODE = 0 Tool change with T function
MD10717 $MN_T_NO_FCT_CYCLE_NAME = "MY_T_CYCLE" Name of the subprogram to re‐
place the T function
MD10719 $MN_T_NO_FCT_CYCLE_MODE = 0 Call time: End of block
Programming Comment
N110 D1 ; D1
N120 G90 G0 X100 Y100 Z50 ; D1 is active.
N130 D2 X110 Z0 T5 ; D1 remains active. The T function is replaced
at the block end with the MY_T_CYCLE subprogram
call. D2 provides MY_T_CYCLE in a system varia-
ble.
A detailed example for replacement of the T function can be found in Section: "Examples of M/
T function replacement at a tool change (Page 227)".
Basic functions
2.17.2.3 System variable
General Information
The replacement subprogram is provided with all of the information relevant to the functions
programmed in the block (T or TCA, D or DL, M) via system variables.
Exception
D or DL number is not transferred if:
● MD10719 $MN_T_NO_FCT_CYCLE_MODE, bit 0 = 1
● MD22550 $MC_TOOL_CHANGE_MODE = 1
AND
● D or DL are programmed together with the T or M function in a block.
CAUTION
Values do not act
The values provided for the replacement subprogram in the system variables are not yet
effective. It is the sole responsibility of the user / machine manufacturer to resolve this by
using the appropriate programming in the replacement subprogram.
System variable

$C_M_PROG TRUE, if the M function has been programmed
$C_M For $C_M_PROG == TRUE, contains the value of address M
We must differentiate between two cases here:
● $C_M supplies the value if, for the tool change with M function,
a subprogram is configured with parameter transfer:
MD10715 MN_M_NO_FCT_CYCLE
● If only one subprogram is configured for the addresses T and/
or D/DL and if in the program the M function for the tool change
is programmed together with one of the addresses to be re‐
placed, then $C_M supplies the value: MD22560
$MC_TOOL_CHANGE_M_CODE
$C_AUX_VALUE[0] Value of the replaced M function
$C_ME For $C_M_PROG == TRUE, contains the value of the address
extension of the M function
$C_AUX_EXT[0] Address extension of the M function (identical to $C_ME)
$C_AUX_IS_QUICK[0] TRUE, if the M function was programmed with quick output to the
PLC
$C_T_PROG TRUE, if the T function was programmed
$C_T For $C_T_PROG == TRUE, contains the value of the T function
Basic functions

$C_TE Contains for:
● $C_T_PROG == TRUE
● $C_TS_PROG == TRUE
the value of the address extension of the T function
$C_TS_PROG TRUE, if for the T or TCA replacement, a tool name has been
programmed.
$C_TS For $C_TS_PROG == TRUE, contains the tool name program‐
med for the T or TCA replacement
$C_TCA TRUE, if the TCA replacement is active
$C_DUPLO_PROG TRUE, if the duplo number of the TCA replacement has been
programmed
$C_DUPLO For $C_DUPLO_PROG == TRUE, contains the value of the pro‐
grammed duplo number
$C_THNO_PROG TRUE, if the toolholder/spindle number of the TCA replacement
has been programmed
$C_THNO For $C_THNO_PROG == TRUE, contains the value of the pro‐
grammed toolholder/spindle number
$C_D_PROG TRUE, if the D function has been programmed
$C_D For $C_D_PROG == TRUE, contains the value of the D function
$C_DL_PROG TRUE, if the DL function was programmed
$C_DL For $C_DL_PROG == TRUE, contains the value of the DL function
$P_SUB_STAT Block-related time when the replacement subprogram is called
$C_MTL_PROG TRUE if address MTL has been programmed
$C_MTL For $C_MTL_PROG == TRUE, contains the value of address MTL
2.17.2.4 Example: Replacement of an M function
Example 1
The function M6 is replaced by calling the subprogram "SUB_M6".
The information relevant for a tool change should be transferred using system variables.
Parameterization

MD10715 $MN_M_NO_FCT_CYCLE[2] = 6 Tool change with M6
MD10716 $MN_M_NO_FCT_CYCLE_NAME[2] = "SUB_M6" Replacement subpro‐
gram for M6
MD10718 $MN_M_NO_FCT_CYCLE_PAR = 2 Information transfer
using system varia‐
bles
Basic functions
Main program
Programming Comment
PROC MAIN
... ;
N10 T1 D1 M6 ; M6 is replaced by subprogram "SUB_M6"
;
... ;
N90 M30
Subprogram "SUB_M6"
Programming Comment
PROC SUB_M6
N110 IF $C_T_PROG==TRUE ; IF address T is programmed
N120 T[$C_TE]=$C_T ; Execute T selection
N130 ENDIF ; ENDIF
N140 M[$C_ME]=6 ; Execute tool change.
N150 IF $C_D_PROG==TRUE ; IF address D is programmed
N160 D=$C_D ; Execute D selection
N170 ENDIF ; ENDIF
N190 M17
Example 2
The new tool is prepared for changing with the T function. The tool change is only realized with
function M6. The T function is replaced by calling the subprogram "MY_T_CYCLE". The D / DL
number is transferred to the subprogram.
Parameterization
MD22550 $MC_TOOL_CHANGE_MODE = 1 Tool change prepared with T
function
MD10717 $MN_T_NO_FCT_CYCLE_NAME = "MY_T_CYCLE" Replacement subprogram
MD10719 $MN_T_NO_FCT_CYCLE_MODE = 0 Transfer of the D/DL number
Main program

N210 D1 ;
N230 D2 X110 Z0 T5 ; D1 remains active, programmed D2 is transferred
; to the subprogram as variable
Basic functions
Example 3
The new tool is prepared for changing with the T function. The tool change is only realized with
function M6. The T function is replaced by calling the subprogram "MY_T_CYCLE". The D / DL
number is not transferred to the subprogram.
Parameterization
MD22550 $MC_TOOL_CHANGE_MODE = 1 Tool change prepared with T
function
MD10717 $MN_T_NO_FCT_CYCLE_NAME = "MY_T_CYCLE" Replacement subprogram
MD10719 $MN_T_NO_FCT_CYCLE_MODE = 1 No transfer of the D/DL number
Main program

N310 D1
N330 D2 X110 Z0 T5 ; D2 is active and is not transferred as variable
to
; the replacement subprogram.
N340 M6 ; Execute tool change.
Example 4
The functions T and M6 are replaced by the subprogram "MY_T_CYCLE".
The parameters are transferred to the subprogram when replacing M6.
If M6 is programmed together with D or DL in the block, the D or the DL number is also
transferred as parameter to the subprogram if no transfer of the D/DL number has been
parameterized:
MD10719 $MN_T_NO_FCT_CYCLE_MODE = 1
Parameterization
Configuration Meaning
MD22550 $MC_TOOL_CHANGE_MODE = 1 Tool change with M function
MD22560 $MC_TOOL_CHANGE_M_CODE = 6 M code for tool change
MD10715 $MC_M_NO_FCT_CYCLE[3] = 6 M function to be replaced
MD10716 $MC_M_NO_FCT_CYCLE_NAME[3] = "MY_T_CYCLE" Replacement subprogram for
the M function
MD10717 $MN_T_NO_FCT_CYCLE_NAME = "MY_T_CYCLE" Replacement subprogram for
the T function
MD10718 $MN_M_NO_FCT_CYCLE_PAR = 3 Parameter transfer to the
replacement subprogram for M6
MD10719 $MN_T_NO_FCT_CYCLE_MODE = 1 No transfer of the D/DL number
Basic functions
Main program

N410 D1
N330 D2 X110 Z0 T5 M6 ; D1 remains active, D2 and T5 are transferred to
the M6 replacement subprogram as variable.
2.17.2.5 Example: Replacement of a T and D function

The functions T and D are replaced by calling the subprogram "D_T_SUB_PROG". The
following should also be true for the example:
● The tool change is realized with address T.
● The subprogram is called at the start of the block.
● The tool management is not active.
● Axis B is an indexing axis with Hirth gearing.
Parameterization

MD11717 $MN_D_NO_FCT_CYCLE_NAME = "D_T_SUB_PROG" Replacement subpro‐
gram
for D function
MD10717 $MN_T_NO_FCT_CYCLE_NAME = "D_T_SUB_PROG" Replacement subpro‐
gram
for M function
MD10719 $MN_T_NO_FCT_CYCLE_MODE = 'H2' Call at block start
MD22550 $MC_TOOL_CHANGE_MODE = 0 Tool change with T
function
Main program
Programming Comment
PROC MAIN
... ;
N10 G01 F1000 X10 T1=5 D1 ; T and D function replaced by calling
; "D_T_SUB_PROG" at start of block
... ;
N90 M30
Subprogram "D_T_SUB_PROG"
Programming Comment
N1000 PROC D_T_SUB_PROG DISPLOF SBLOF
Basic functions
Programming Comment
N4100 IF $C_T_PROG==TRUE ; IF address T is programmed

N4120 POS[B]=CAC($C_T) ; Approach indexing position
N4130 T[$C_TE]=$C_T ; Select tool (T selection)
N4140 ENDIF ; ENDIF
N4300 IF $C_T_PROG==TRUE ; IF address D is programmed

N4320 D=$C_D ; Select offset (D selection)
N4330 ENDIF ; ENDIF
N4400 IF $C_DL_PROG==TRUE ; IF address DL is programmed

N4420 D=$C_DL ; Select insert offset
N4430 ENDIF ; ENDIF
N9999 RET
2.17.2.6 Behavior in the event of a conflict
Conflict case
A conflict is present if several functions are programmed in one block and the functions should
be replaced with different subprograms:
● Addresses D and DL replaced with subprogram:
MD11717 $MN_FCT_CYCLE_NAME = "D_SUB_PROG"
● Address T replaced with subprogram:
MD10717 $MN_FCT_CYCLE_NAME = "T_SUB_PROG"
● M function M6 replaced with subprogram:
MD10715 $MN_M_NO_FCT_CYCLE[0] = 6
MD10716 $MN_M_NO_FCT_CYCLE_NAME[0] = "M6_SUB_PROG"
MD10718 $MN_M_NO_FCT_CYCLE_PAR = 0
MD22550 $MC_TOOL_CHANGE_MODE = 1
MD22560 $MC_TOOL_CHANGE_M_CODE = 6
Resolution
A conflict is resolved corresponding to the following table:
The following are programmed in one program line: Called subprogram:

D and/or DL T or TCA M6
– – x M6_SUB_PROG
– x – T_SUB_PROG
– x x M6_SUB_PROG
x – – D_SUB_PROG
x – x M6_SUB_PROG
Basic functions
The following are programmed in one program line: Called subprogram:

D and/or DL T or TCA M6
x x – T_SUB_PROG
x x x M6_SUB_PROG
2.17.3 Replacement of spindle functions
2.17.3.1 General information
Function
When a coupling is active the following spindle functions can be replaced for leading spindles:
● M40: Automatic gear stage change
● M41 ... M45 Programmed gear stage change
● SPOS, SPOSA and M19: Spindle positioning
Boundary conditions
● To replace a spindle function, the following conditions must be met:
– The programmed spindle must be the leading spindle of an active coupling.
– Leading and following spindle are located in the same channel. This is only detected if
the leading spindle is located in the channel in which the coupling was closed. If the
leading spindle is changed to another channel, a gear stage change or positioning of this
spindle does not call the replacement subprogram.
– A programmed gear stage change must result in a real gear stage change. For this
purpose, the programmed and active gear stage must differ.
● In a block, only one spindle function can be replaced. Multiple replacements lead to the
termination of the program processing. The spindle functions, which are to be replaced,
must then be distributed over several blocks.
Parameterization
Spindle function
The spindle functions to be replaced by the subprogram are selected in the machine data:
Basic functions
MD30465 $MA_AXIS_LANG_SUB_MASK
Bit Meaning
0 Gear-stage change automatic (M40) and directly (M41-M45)
Val‐ Meaning
ue
0 No replacement
1 Replacement through the subprogram set in MD15700 and MD15702
1 Spindle positioning with SPOS / SPOSA / M19
Val‐ Meaning
ue
0 No replacement
1 Replacement through the subprogram set in MD15700 and MD15702
Subprogram: Name
The name of the replacement subprogram is entered in the machine data:
MD15700 $MN_LANG_SUB_NAME = "<subprogram name>"
Subprogram: Path
The path of the replacement subprogram is set in the machine data:
MD15702 $MN_LANG_SUB_PATH = <value>
Value Meaning
0 Manufacturer cycle folder: /_N_CMA_DIR
1 User cycle folder: /_N_CUS_DIR
2 Siemens cycle folder: /_N_CST_DIR
System variable: Time that the replacement subprogram is called

The time that the replacement subprogram is called can be read using the system variable
$P_SUB_STAT:
Value Meaning
0 Replacement not active
1 Replacement active, subprogram call is made at the block start
2 Replacement active, subprogram call is made at the block end
Block processing
If the replacement subprogram is called at the block start, after processing the replacement
subprogram, the block that initiated the call is processed. The replaced commands are no
longer processed.
If the replacement subprogram is called at the block end, the block that initiated calling the
replacement subprogram is first processed without the commands to be replaced. The
replacement subprogram is then subsequently called.
Basic functions
2.17.3.2 Replacement of M40 - M45 (gear stage change)
Function
When a coupling is active, the commands for gear stage change (M40, M41 ... M45) of the
leading spindle are replaced by calling a user-specific subprogram.
Parameterization
Activation
● MD30465 $MA_AXIS_LANG_SUB_MASK, bit 0 = 1
Time that the subprogram is called

● M40
The time of the call cannot be set. The replacement subprogram is always called at the block
start.
● M41 ... M45
The call time depends on the configured output behavior of the auxiliary function to the PLC
(see below MD22080):
– Output before or during motion: Subprogram call at the start of the block.
– Output after motion: Subprogram call at the end of the block
MD22080 $MC_AUXFU_PREDEF_SPEC[12 ... 16] (output behavior for M41 ... M45)
Bit Value Meaning

5 1 Output of the auxiliary function before the motion
6 1 Output of the auxiliary function during the motion
7 1 Output of the auxiliary function after the motion
System variable to transfer information

The replacement subroutine is provided with all of the information relevant to the functions
programmed in the block via system variables (see Chapter "System variable (Page 235)").
The data refer exclusively to the block, in which the function to be replaced has been
programmed.
2.17.3.3 Replacement of SPOS, SPOSA, M19 (spindle positioning)
Function
When a coupling is active, the positioning commands (SPOS, SPOSA or M19) of a leading
spindle are replaced by calling a user-specific subprogram (replacement subprogram).
Basic functions
Application example
When machining workpieces in parallel on a double-spindle machine, the spindles are coupled
through a coupling factor not equal to 1. When changing the tool, they must be brought to the
same position. The replacement subprogram opens the coupling, separately positions the
spindles at the tool change position and then recloses the coupling.
Parameterization
Activation
● MD30465 $MA_AXIS_LANG_SUB_MASK, bit 1 = 1
Time that the replacement subprogram is called

● SPOS, SPOSA
The time of the call cannot be set. The replacement subprogram is always called at the block
start.
● M19
The call time depends on the configured output behavior of the auxiliary function to the PLC
(see below MD22080):
– Output before or during motion: Subprogram call at the start of the block.
– Output after motion: Subprogram call at the end of the block
MD22080 $MC_AUXFU_PREDEF_SPEC[9]
Bit Value Meaning
5 1 Output of the auxiliary function before the motion
6 1 Output of the auxiliary function during the motion
7 1 Output of the auxiliary function after the motion

The replacement subroutine is provided with all of the information relevant to the functions
programmed in the block via system variables (see Chapter "System variable (Page 235)").
The data refer exclusively to the block, in which the function to be replaced has been
programmed.

$P_SUB_AXFCT TRUE, if M40, M41 ... M45 replacement is active
$P_SUB_GEAR Programmed or calculated gear stage
Outside the replacement subprogram: Gear stage of the master spindle
$P_SUB_AUTOGEAR TRUE, if M40 was active in the block that had initiated the replacement
operation.
Outside the replacement subprogram: Actual setting in the interpreter
Basic functions

$P_SUB_LA Contains the axis name of the leading spindle of the active coupling, which
had triggered the replacement operation.
Note
If the variable is used outside the replacement subprogram, program pro‐
cessing is cancelled with an alarm.
$P_SUB_CA Contains the axis name of the following spindle of the active coupling, which
had triggered the replacement operation.
Note
If the variable is called outside the replacement subprogram, program pro‐
$P_SUB_AXFCT Contains the active replacement types corresponding to MD30465
$MA_AXIS_LANG_SUB_MASK
$P_SUB_SPOS TRUE, if the SPOS replacement is active
$P_SUB_SPOSA TRUE, if the SPOSA replacement is active
$P_SUB_M19 TRUE, if the M19 replacement is active
$P_SUB_SPOSIT Contains the programmed spindle position
Note
$P_SUB_SPOSMODE Contains the position approach mode for the programmed spindle position:
Value Meaning
0 No change of the position approach mode
1 AC
2 IC
3 DC
4 ACP
5 ACN
6 OC
7 PC
Note:
$P_SUB_STAT Block-related time when the replacement subprogram is called
2.17.3.5 Example: Gear stage change

In the subprogram, all commands to change the gear stage M40, M41 ... M45 are replaced.
Parameterization

MD15700 $MN_LANG_SUB_NAME = "LANG_SUB" Subprogram
MD15702 $MN_LANG_SUB_PATH = 0 Manufacturer's folder
MD22080 $MC_AUXFU_PREDEF_SPEC[12] = 'H21' M41: Output prior to motion
Basic functions

MD30465 $MA_AXIS_LANG_SUB_MASK[AX5] = Replace gear change commands
'H0001'
Main program
Programming Comment
PROC MAIN
N110 COUPON(S2,S1) ; Close the synchronous spindle coupling
N120 G01 F100 X100 S5000 M3 M43 ; Subprogram call due to M43
N130 M40 ; Switch on automatic gear stage change
N140 M3 S1000 ; Subprogram call due to S1000
; and as a result an initiated automatic
; gear stage change
N9999 M30
Replacement subprogram "LANG_SUB", version 1

Optimized for simplicity and velocity by directly addressing the spindles (S1: Leading spindle,
S2: Following spindle).
Programming Comment
N1000 PROC LANG_SUB DISPLOF SBLOF
N1100 IF($P_SUB_AXFCT ==1) ; Replacement due to gear stage change
N1140 DELAYFSTON ; Start of stop delay area
N1150 COUPOF(S2,S1) ; Open synchronous spindle coupling
N1160 ;gear stage change separately for leading and following spindles
N1170 M1=$P_SUB_GEAR M2=$P_SUB_GEAR
N1180 DELAYFSTON ; End of stop delay area
N1190 COUPON(S2,S1) ; Close the synchronous spindle coupling
N1200 ENDIF
...
N9999 RET

Flexibility through indirect addressing using the system variable (leading spindle: $P_SUB_LA,
Folgespindel: $P_SUB_CA).
Programming Comment
N1010 DEF AXIS _LA ; Bit memory for leading axis / leading spindle
N1020 DEF AXIS _CA ; Bit memory for following axis / following
spindle
Basic functions
Programming Comment
N1030 DEF INT _GEAR ; Bit memory for gear stage
N1100 IF($P_SUB_AXFCT==1) ; Replacement due to gear stage change

N1110 _GEAR=$P_SUB_GEAR ; Gear stage to be activated
N1120 _LA=$P_SUB_LA ; Axis name of the leading spindle
N1130 _CA=$P_SUB_CA ; Axis name of the following spindle
N1150 COUPOF(_CA,_LA) ; Open synchronous spindle coupling
N1160 ;gear stage change for leading and following spindles
N1170 M[AXTOSPI(_LA)]=_GEAR M[AXTOSPI(_CA)]=_GEAR
N1180 DELAYFSTOF ; End of stop delay area
N1190 COUPON(_CA,_LA) ; Close the synchronous spindle coupling
N1200 ENDIF
...
N9999 RET
2.17.3.6 Example: Spindle positioning

In the subprogram, only the replacement of commands SPOS and SPOSA is explicitly executed.
Additional replacements should be supplemented in essentially the same fashion.
Parameterization

MD30465 $MA_AXIS_LANG_SUB_MASK[AX5] = Replace positioning commands
'H0002'
MD22080 $MC_AUXFU_PREDEF_SPEC[9] = 'H0021' Output of M19 to the PLC before mo‐
tion

SD43240 $SA_M19_SPOS[AX5] = 260 Spindle position for M19 = 260
SD43250 $SA_M19_SPOSMODE[AX5] = 4 Position approach mode for M19:
"Approach in the positive direction
(ACP)"
Main program
Programming Comment
PROC MAIN
...
N210 COUPON(S2,S1) ; Activate synchronous spindle coupling
N220 SPOS[1]=100 ; Position leading spindle with SPOS
...
Basic functions
Programming Comment
N310 G01 F1000 X100 M19 ; Position leading spindle with M19

Optimized for simplicity and velocity by directly addressing the spindles (S1: Leading spindle,
S2: Following spindle).
Programming Comment
N2100 IF($P_SUB_AXFCT==2)
N2110 ;Replacement of SPOS/SPOSA/M19 for active synchronous spindle coupling
N2190 COUPOF(S2,S1) ; Open synchronous spindle coupling
N2200 ; Position leading and following spindles
N2210 IF($P_SUB_SPOS==TRUE) OR ($P_SUB_SPOSA==TRUE)
N2220 ;SPOS and SPOSA are mapped to SPOS
N2230 CASE $P_SUB_SPOSMODE OF \
0 GOTOF LABEL1_DC \
1 GOTOF LABEL1_IC \
2 GOTOF LABEL1_AC \
3 GOTOF LABEL1_DC \
4 GOTOF LABEL1_ACP \
5 GOTOF LABEL1_ACN \
DEFAULT GOTOF LABEL_ERR
LABEL1_DC: SPOS[1]=DC($P_SUB_SPOSIT) SPOS[2]=DC($P_SUB_SPOSIT)
GOTOF LABEL1_CONT
LABEL1_IC: DELAYFSTOF
SPOS[1]=IC($P_SUB_SPOSIT) SPOS[2]=IC($P_SUB_SPOSIT)
DELAYFSTON
GOTOF LABEL1_CONT
LABEL1_AC: SPOS[1]=AC($P_SUB_SPOSIT) SPOS[2]=AC($P_SUB_SPOSIT)
GOTOF LABEL1_CONT
LABEL1_ACP: SPOS[1]=ACP($P_SUB_SPOSIT) SPOS[2]=ACP($P_SUB_SPOSIT)
GOTOF LABEL1_CONT
LABEL1_ACN: SPOS[1]=ACN($P_SUB_SPOSIT) SPOS[2]=ACN($P_SUB_SPOSIT)
LABEL1_CONT:
N2250 ELSE ; Position the spindle with M19
N2270 M1=19 M2=19 ; Leading and following spindles
N2280 ENDIF ; End replacement SPOS, SPOSA
N2290 COUPON(S2,S1) ; Activate synchronous spindle coupling
N2410 ELSE
N2420 ;from here processing further replacements
...
Basic functions
Programming Comment
N3300 ENDIF ; End replacements
...
N9999 RET ; Normal end of program
LABEL_ERR: SETAL(61000) ; Error has occurred

Flexibility through indirect addressing using the system variable (leading spindle: $P_SUB_LA,
Folgespindel: $P_SUB_CA).
Programming Comment
N1010 DEF AXIS _LA ; Leading axis/spindle
N1020 DEF AXIS _CA ; Following axis/spindle
N1030 DEF INT _LSPI ; Leading spindle number (programmed
; spindle)
N1040 DEF INT _CSPI ; Following spindle number
...
N2100 IF($P_SUB_AXFCT==2)
N2110 ; Replacement of SPOS/SPOSA/M19 for active ; synchronous spindle coupling
N2120 _LA=$P_SUB_LA ; Axis name of the leading spindle
N2130 _CA=$P_SUB_CA ; Axis name of the following spindle
N2140 _LSPI=AXTOSPI(_LA) ; Number of the leading spindle
N2180 _CSPI=AXTOSPI(_LA) ; Number of the following spindle
N2190 COUPOF(_CA,_LA) ; Deactivate synchronous spindle coupling
N2200 ; Position leading and following spindles:
N2210 IF($P_SUB_SPOS==TRUE) OR ($P_SUB_SPOSA==TRUE)
N2220 ;SPOS and SPOSA are mapped to SPOS
N2230 CASE $P_SUB_SPOSMODE OF
0 GOTOF LABEL1_DC \
1 GOTOF LABEL1_IC \
2 GOTOF LABEL1_AC \
3 GOTOF LABEL1_DC \
4 GOTOF LABEL1_ACP \
5 GOTOF LABEL1_ACN \
DEFAULT GOTOF LABEL_ERR
LABEL1_DC: SPOS[_LSPI]=DC($P_SUB_SPOSIT) SPOS[_CSPI]=DC($P_SUB_SPOSIT)
GOTOF LABEL1_CONT
LABEL1_IC: DELAYFSTOF
SPOS[_LSPI]=IC($P_SUB_SPOSIT) SPOS[_CSPI]=IC($P_SUB_SPOSIT)
DELAYFSTON
GOTOF LABEL1_CONT
Basic functions
Programming Comment
LABEL1_AC: SPOS[_LSPI]=AC($P_SUB_SPOSIT) SPOS[_CSPI]=AC($P_SUB_SPOSIT)
GOTOF LABEL1_CONT
LABEL1_ACP: SPOS[_LSPI]=ACP($P_SUB_SPOSIT) POS[_CSPI]=ACP($P_SUB_SPOSIT)
GOTOF LABEL1_CONT
LABEL1_ACN: SPOS[_LSPI]=ACN($P_SUB_SPOSIT) POS[_CSPI]=ACN($P_SUB_SPOSIT)
LABEL1_CONT:
N2250 ELSE ; Position spindles with M19
N2270 M[_LSPI]=19 M[_CSPI]=19
N2280 ENDIF
N2290 COUPON(_CA,_LA) ; Activate synchronous spindle coupling
N2410 ELSE
N2420 ;from here processing further replacements
...
N3300 ENDIF
...
N9999 RET ; Normal end of program
LABEL_ERR: SETAL(61000) ; Error has occurred
2.17.4 Properties of the subprograms
General rules
● The subprogram called when making the replacement can contain the command PROC and
the attribute SBLOF and DISPLOF.
● The replacement is also made in the ISO language mode. However, the replacement
subprograms are exclusively processed in the standard language mode (Siemens). There
is an implicit switchover into the standard language mode. The original language mode is
reselected with the return jump from the replacement subprogram.
● System variables are exclusively used to transfer information to the replacement
subprogram. Transfer parameters are not possible.
● The behavior for a single block and attribute SBLOF depends on the setting in:
MD10702 IGNORE_SINGLEBLOCK_MASK, bit 14 (prevent single-block stop)
Basic functions
Value Meaning
0 The replacement subprogram behaves like a "normal" subprogram:
● Return jump with M17: Stop at the end of the subprogram
Note
The output of the M function at the PLC depends on:
MD20800 $MC_SPF_END_TO_VDI, bit 0 (subprogram end to PLC)
- Bit 0 = 0: No output
- Bit 0 = 1: M17 is output to the PLC.
● Return jump with RET: No stop at the end of the replacement subprogram
1 In the block, in which the replacement subprogram is called, only one stop is made. Regardless
of whether:
● The subprogram was called at the block start and/or at the block end
● Other subprograms are called in the subprogram
● The subprogram is exited with M17 or RET
The single-block stop takes place for the replacement of M functions at the end of the replace‐
ment subprogram.
For the replacement of T and D/DL functions, the time of the single-block stop depends on
when the subprogram is called:
● Call at block start: Single-block stop at the end of the block
● Call at the block end: Single-block stop at the end of the replacement subprogram
● For replacement subprograms with the attribute DISPLOF in the block display, the program
line is displayed as actual block, which resulted in the subprogram being called.
● In the replacement subprogram, areas or the complete replacement subprogram can be
protected against interruptions, such as NC stop, read-in inhibit etc., using the DELAYFSTON
and DELAYFSTOF commands.
● Replacements do not occur recursively, i.e. the function that has led to the replacement
subprogram call is no longer replaced if it is programmed again in the replacement
subprogram.
Output of auxiliary functions to PLC

When replacing auxiliary functions, calling the replacement subprogram does not initiate that
the auxiliary function is output to the PLC. The auxiliary function is only output if the auxiliary
function is reprogrammed in the replacement subprogram.
Behavior during block search

The replacement subprogram is also called in the block search modes "Block search with
calculation" and "Block search with calculation in the program test mode" (SERUPRO). Any
special features must be implemented in the replacement subprogram using the system
variable: $P_SEARCH, $AC_SERUPRO.
Regarding collecting actions for "block search with calculation", replacement subprograms
behave just like "normal" subprograms.
Basic functions
2.18 Renaming/locking NC commands
2.17.5 Restrictions
● Function replacements are not permitted in:
– Synchronized actions
– Technology cycles
● There must be no blockwise synchronized actions in front of a block that contains functions
at the beginning to be replaced. See the paragraph below "Example for: Non-modal
synchronized actions".
● Only the actions required for the respective replacements can be performed in the
replacement subprogram.
● In a block, in which the replacement subprogram is called at the block end, the following
should be observed:
– No modal subprogram call should be active
– No subprogram return jump should be programmed
– No program end should be programmed
Note
The controller does not monitor whether the function to be replaced has been realized in
the replacement subprogram.
Example of: Non-modal synchronized actions

MD30465 $MA_AXIS_LANG_SUB_MASK, bit 0 = 1 (gear stage change)
Program code
...
N1000 WHENEVER $AA_IM[X2] <= $AA_IM[X1] + 0.5 DO $AA_OVR[X1]=0
N1010 G1 X100 M43
...
If, in block N1010, the function M43 initiates that a replacement subprogram is called,
machining is interrupted and an alarm is output.
2.18 Renaming/locking NC commands
Function
The machine manufacturer or end user can change the names of existing NC commands with
the "Rename/lock NC commands" function.
Basic functions
2.19 Program runtime / part counter
Application
The function can be used for the following purposes:
● Improve the readability of part programs
● Lock NC commands
● User-specific extension of NC functions
Parameterization
The renaming/locking of NC commands is made via the machine data:
MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[<n>] (list of reconfigured NC codes)
An even index [<n>] contains the original name of the command. The following uneven index
contains the new name of the command.
An empty string ("") as new name means that there is no new name for the command.
Consequently, the command is locked and can no longer be programmed.
Changes of MD10712 become effective during the control system startup.
Example
Rename command G00 and deactivate G01

MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[0] = "G00"
MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[1] = "RAPIDTRAVERSE"
MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[2] = "G01"
MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[3] = ""
After activation with Power On, rapid traverse can no longer be programmed with the G00
command, but only with the RAPIDTRAVERSE command. G01 can no longer be programmed.

Information on the program runtime and workpiece counter is provided to support the machine
tool operator.
This information can be processed as system variables in the NC and/or PLC program. This
information is also available to be displayed on the operator interface.
Basic functions
2.19.1 Program runtime
2.19.1.1 Function
The "Program runtime" function provides various timers to monitor technological processes,
which can be read into the part program and into synchronized actions via system variables.
There are two types of timers:
1. Standard timers
Standard timers are always active
2. Timers that can be activated
Timers that can be activated must be activated via machine data.
Standard timers
Time since the last control power-up

$AN_SETUP_TIME Time since the last control power-up with default values in minutes.
Is automatically reset to "0" in each control power-up with default values.
$AN_POWERON_TIME Time since the last normal control power-up ("warm restart") in minutes.
Is automatically reset to "0" in each normal control power-up.
Basic functions
Program runtime
The timers to measure the program runtimes are only available in AUTOMATIC mode.
System variable (channel-specific) Description

$AC_ACT_PROG_NET_TIME Actual net runtime of the current program in seconds
Net runtime means that the time, in which the program was stopped, has been
deducted.
If, in the AUTOMATIC operating mode, a part program is restarted from the
RESET channel state, then $AC_ACT_PROG_NET_TIME is automatically reset
to "0".
Additional properties:
● The reset button does not reset $AC_ACT_PROG_NET_TIME back to "0",
but rather only stops the timer.
● When starting an ASUB, $AC_ACT_PROG_NET_TIME is set to "0" and also
counts the runtime of the ASUB. At the end of an ASUB, it behaves just the
same as for the RESET button: The timer is only held, but is not set to "0".
● $AC_ACT_PROG_NET_TIME is not reset when starting an event-controlled
program (PROG_EVENT).
The program runtime is only counted further if it involves a start, M30 or a
search PROG_EVENT.
● The behavior of $AC_ACT_PROG_NET_TIME for GOTOS and override =
0% can be parameterized using MD27850 (refer to Section "Parameteriza‐
tion")
Tip:
With $AC_PROG_NET_TIME_TRIGGER, $AC_ACT_PROG_NET_TIME can
be manipulated further.
$AC_OLD_PROG_NET_TIME Net runtime in seconds of the program that has just been correctly ended
"Correctly ended" means that the program was not interrupted with RESET, but
instead ended properly with M30.
If a new program is started, $AC_OLD_PROG_NET_TIME remains unscanned,
till M30 is reached again.
Additional properties:
● $AC_OLD_PROG_NET_TIME is set to "0" if the currently selected program
is edited.
● $AC_OLD_PROG_NET_TIME is not changed at the end of an ASUB or an
event-controlled program (PROG_EVENT).
Tip:
The implied copying process of $AC_ACT_PROG_NET_TIME after
$AC_OLD_PROG_NET_TIME takes place only when
$AC_PROG_NET_TIME_TRIGGER is not written.
Basic functions
System variable (channel-specific) Description

$AC_OLD_PROG_NET_TIME_COUNT Changes to $AC_OLD_PROG_NET_TIME
After POWER ON, $AC_OLD_PROG_NET_TIME_COUNT is at "0".
$AC_OLD_PROG_NET_TIME_COUNT is always increased if the control has
newly written to $AC_OLD_PROG_NET_TIME.
If the user terminates the running program with RESET,
$AC_OLD_PROG_NET_TIME and $AC_OLD_PROG_NET_TIME_COUNT re‐
main unchanged.
With $AC_OLD_PROG_NET_TIME_COUNT it can thus be ascertained, wheth‐
er $AC_OLD_PROG_NET_TIME was written.
Example:
If two programs running consecutively have the same runtime and were ended
correctly, then the user can identify this via the changed value in
$AC_OLD_PROG_NET_TIME_COUNT.
$AC_PROG_NET_TIME_TRIGGER Trigger for the selective measurement of program sections.
The function is triggered by the writing of the value to the variable:
Val‐ Function
ue
0 Not active
1 Terminates the measurement
● $AC_OLD_PROG_NET_TIME = $AC_ACT_PROG_NET_TIME
● $AC_ACT_PROG_NET_TIME = 0 and then continues to run
2 Starts the measurement
● $AC_ACT_PROG_NET_TIME = 0
● $AC_OLD_PROG_NET_TIME is not changed
3 Stops the measurement
● $AC_ACT_PROG_NET_TIME is not changed
4 Continues the stopped measurement
● $AC_ACT_PROG_NET_TIME continues to run
All system variables are reset to 0 as a result of POWER ON!
Note
Residual time for a workpiece
If the same workpieces are machined one after the other then using the following timer values
the remaining residual time for a workpiece can be determined.
● Processing time for the last workpiece produced (see $AC_OLD_PROG_NET_TIME)
● Current processing time (see $AC_ACT_PROG_NET_TIME)
The residual time is displayed on the user interface in addition to the current processing time.
Basic functions
Note
Using STOPRE
The system variables $AC_OLD_PROG_NET_TIME and
$AC_OLD_PROG_NET_TIME_COUNT do not generate any implicit preprocessing stop. This
is uncritical when used in the part program if the value of the system variables comes from the
previous program run. However, if the trigger for the runtime measurement
($AC_PROG_NET_TIME_TRIGGER) is written very frequently and as a result
$AC_OLD_PROG_NET_TIME changes very frequently, then an explicit STOPRE should be
used in the part program.
Timers that can be activated
Program runtime
The timers to measure the program runtimes are only available in AUTOMATIC mode.
System variable (channel-spe‐ Description

cific)
$AC_OPERATING_TIME Total runtime of NC programs in Automatic mode (in s)
In the automatic mode, the runtimes of all programs between NC start and end of pro‐
gram / reset are summed up.
The default is not to count in NC stop and override = 0%. Continued counting can be acti‐
vated at an override of 0% via MD27860.
The value is automatically reset to "0" every time the control powers up.
$AC_CYCLE_TIME Runtime of the selected NC program (in seconds)
The runtime between NC Start and end of program / NC reset is measured in the selected
NC program.
The default is not to count in NC stop and override = 0%. Continued counting can be acti‐
vated at an override of 0% via MD27860.
The value is automatically reset to "0" every time a new NC program starts up. MD27860 can
be set to ensure that this value will be deleted even if there is a jump to the beginning of the
program with GOTOS or in the event of ASUBs and PROG_EVENTs starting.
$AC_CUTTING_TIME Processing time in seconds
The runtime of the path axes (at least one is active) is measured in all NC programs between
NC Start and end of program / NC reset without rapid traverse active. MD27860 can be used
to set whether measuring should only be conducted when the tool is active or independent
of the tool state.
The measurement is interrupted when a dwell time is active.
The value is automatically reset to "0" every time the control powers up with default values.
2.19.1.2 Commissioning
Activation/deactivation
The timer that can be activated is switched-in/switched-out using machine data:
Basic functions
MD27860 $MC_PROCESSTIMER_MODE, bit 0 - 2 = <value>
Bit Value Meaning

0 0 Timer for $AC_OPERATING_TIME not active.
1 Timer for $AC_OPERATING_TIME active.
1 0 Timer for $AC_CYCLE_TIME not active.
1 Timer for $AC_CYCLE_TIME active.
2 0 Timer for $AC_CUTTING_TIME not active.
1 Timer for $AC_CUTTING_TIME active.
Parameterization
Behavior of the timer that is always active

The behavior of the timer that is always active for GOTOS and override = 0% is set using
machine data:
MD27850 $MC_PROG_NET_TIMER_MODE
Bit Value Meaning

0 0 $AC_ACT_PROG_NET_TIME is not reset to "0" in case of a jump with GOTOS to the
program start (initial setting).
1 With a jump with GOTOS to the start of the program, $AC_ACT_PROG_NET_TIME is
reset to "0", the value is first saved in $AC_OLD_PROG_NET_TIME and the program
counter $AC_OLD_PROG_NET_TIME_COUNT is incremented.
1 0 $AC_ACT_PROG_NET_TIME is not increased for override = 0%. This means that the
program runtime is measured without the time for which the override was set to "0"
(basic setting).
1 $AC_ACT_PROG_NET_TIME is also increased for override = 0%. This means that the
program runtime is measured with the time for which the override was set to "0".
Behavior of the timer that can be activated

The behavior of the timer that can be activated for certain functions (e.g. test run feedrate,
program test) is set using machine data:
MD27860 $MC_PROCESSTIMER_MODE
Bit Value Meaning

4 0 No measurement during active dry run feedrate.
1 Measurement during active dry run feedrate.
5 0 No measurement during program test.
1 Measurement during program test.
6 Only for bit 1 = 1 (timer for $AC_CYCLE_TIME is active)
0 $AC_CYCLE_TIME is reset to "0" also in case of Start through ASUB and
PROG_EVENTs.
1 $AC_CYCLE_TIME is not reset to "0" in case of Start through ASUB and
PROG_EVENTs.
Basic functions
Bit Value Meaning

7 Only for bit 2 = 1 (timer for $AC_CUTTING_TIME is active)
0 Timer for $AC_CUTTING_TIME counts only for the active tool.
1 Timer for $AC_CUTTING_TIME counts independent of the tool.
8 Only for bit 1 = 1 (timer for $AC_CYCLE_TIME is active)
0 $AC_CYCLE_TIME is not reset to "0" in case of a jump with GOTOS to the program start.
1 $AC_CYCLE_TIME is reset to "0" in case of a jump with GOTOS to the program start.
9 Only for bit 0, 1 = 1 (timer for $AC_OPERATING_TIME and $AC_CYCLE_TIME are active)
0 Counting of the program runtime is not continued at an override of 0%.
1 Counting of the program runtime continues at an override of 0%.
Block search
No program runtimes are determined through block searches.
REPOS
The duration of a REPOS process is added to the current processing time
($AC_ACT_PROG_NET_TIME).
2.19.1.4 Examples
Example 1: Parameterization of the runtime measurement via MD27860

Activating the runtime measurement for the active NC program and hence no measurement in
case of active dry run feedrate and program test:
MD27860 $MC_PROCESSTIMER_MODE = 'H2'
Activating the measurement for the tool action time and measurement also with active dry run
feedrate and program test.
Activating the measurement for the total runtime and the processing time with an active tool,
including measurement with a program test:
Activating the measurement for the total runtime and the machining time (independent of the
tool), including measurement with a program test:
MD27860 $MC_PROCESSTIMER_MODE = 'Ha5'
Activating the measurement for the processing time with an active tool, including
measurements at an override = 0%, but not with a trial run feed active:
Basic functions
Example 2: Measuring the duration of "mySubProgrammA"
Program code
...
N50 DO $AC_PROG_NET_TIME_TRIGGER=2
N60 FOR ii= 0 TO 300
N70 mySubProgrammA
N95 ENDFOR
N97 mySubProgrammB
N98 M30
After the program has processed line N80, the net runtime of "mySubProgrammA" is located in
$AC_OLD_PROG_NET_TIME.
The value from $AC_OLD_PROG_NET_TIME:
● Is kept beyond M30.
● Is updated each time the loop is run through.
Example 3: Measuring the duration of "mySubProgrammA" and "mySubProgrammC"
Program code
N20 mySubProgrammA
N40 mySubProgrammB
N60 mySubProgrammC
N80 mySubProgrammD
N90 M30
2.19.2 Workpiece counter
2.19.2.1 Function
Various counters with a range of values from 0 to 999,999,999 are available with the
"Workpiece counter" function in the form of channel-specific system variables. Read and write
access to the system variables is possible.
The following channel-specific machine data can be used to control counter activation, counter
reset timing and the counting algorithm.
Basic functions
System variables for workpiece counting

$AC_REQUIRED_PARTS Number of workpieces to be produced (setpoint number of workpieces)
In this counter the number of workpieces at which the actual workpiece
count ($AC_ACTUAL_PARTS) will be reset to "0" can be defined.
MD27880 can be used to activate the generation of the display alarm:
"Channel %1 workpiece target = %2 reached"
and of the channel-specific NC/PLC interface signal:
DB21, DBX317.1 (workpiece target reached)
.
$AC_TOTAL_PARTS Total number of completed workpieces (actual workpiece total)
This counter specifies the total number of workpieces produced since
the start time. The value is only automatically reset to "0" when the
control runs up with default values.
$AC_ACTUAL_PARTS Number of completed workpieces (actual workpiece total)
This counter registers the total number of workpieces produced since
the start time. On condition that $AC_REQUIRED_PARTS > 0, the
counter is automatically reset to "0" when the required number of work‐
pieces ($AC_REQUIRED_PARTS) is reached.
$AC_SPECIAL_PARTS Number of workpieces selected by the user
This counter supports user-specific workpiece counts. An alarm can be
defined to be output when the setpoint number of workpieces is reached
($AC_REQUIRED_PARTS). Users must reset the counter themselves.
Note
All workpiece counters are set to "0" when the control runs up with default values and can be
read and written independent of their activation.
Activation
The workpiece counter is activated with the machine data:
MD27880 $MC_PART_COUNTER (activation of workpiece counters)
Bit Value Meaning

0 1 $AC_REQUIRED_PARTS is active
1 0 Alarm/signal output for: $AC_ACTUAL_PARTS = $AC_REQUIRED_PARTS
1 Alarm/signal output for: $AC_SPECIAL_PARTS = $AC_REQUIRED_PARTS
4 1 $AC_TOTAL_PARTS is active.
5 0 $AC_TOTAL_PARTS is incremented by the value "1" through M02/M30.
1 $AC_TOTAL_PARTS is incremented by the value "1" through the M command defined
with MD27882[0].
6 0 $AC_TOTAL_PARTS is also active for program test / block search.
7 1 $AC_TOTAL_PARTS is incremented by the value "1" upon a jump back with GOTOS.
Basic functions
Bit Value Meaning

8 1 $AC_ACTUAL_PARTS is active
9 0 $AC_ACTUAL_PARTS is incremented by the value "1" through M02/M30.
1 $AC_ACTUAL_PARTS is incremented by the value "1" through the M command de‐
fined with MD27882[1].
10 0 $AC_ACTUAL_PARTS is also active for program test / block search.
11 1 $AC_ACTUAL_PARTS is incremented by the value "1" upon a jump back with GOTOS.
12 1 $AC_SPECIAL_PARTS is active.
13 0 $AC_SPECIAL_PARTS is incremented by the value "1" through M02/M30.
1 $AC_SPECIAL_PARTS is incremented by the value 1 through the M command defined
with MD27882[2].
14 0 $AC_SPECIAL_PARTS is also active for program test / block search.
15 1 $AC_SPECIAL_PARTS is incremented by the value "1" upon a jump back with GOTOS.
Workpiece counting with user-defined M command

If the corresponding bit is set in MD27880, then the count pulse can be triggered via a user-
defined M command parameterized via the following machine data instead of via the end of
program M2/M30.
MD27882 $MC_PART_COUNTER_MCODE[<n>] (workpiece counting with user-defined M
command)
<n> Meaning
0 MD27882[0] defines the M command in which $AC_TOTAL_PARTS is incremented.
1 MD27882[1] defines the M command in which $AC_ACTUAL_PARTS is incremented.
2 MD27882[2] defines the M command in which $AC_SPECIAL_PARTS is incremented.
The respective workpiece counter is incremented by "1", when a user-defined M command is

called.
Protection level for workpiece counting

Using the following machine data, the protection level for activating/deactivating the workpiece
counting at the user interface is set.
MD51074 $MN_ACCESS_WRITE_WPC_COUNTER = <protection level>
Mode change / NC RESET

The counters are not affected by a mode change or NC RESET.
Basic functions
$AC_REQUIRED_PARTS ≤ 0
Where $AC_REQUIRED_PARTS ≤ 0 and MD27880 $MC_PART_COUNTER, bit 0 = 1, the
counting procedure and the identity comparison set with MD27880 are not conducted for all the
active counters.
2.19.2.4 Examples
Activation of the workpiece counter $AC_REQUIRED_PARTS:

● MD27880 $MC_PART_COUNTER = 'H3'
$AC_REQUIRED_PARTS is active
Display alarm for: $AC_REQUIRED_PARTS == $AC_SPECIAL_PARTS
Activation of the workpiece counter $AC_TOTAL_PARTS:

● MD27882 $MC_PART_COUNTER_MCODE[0] = 80
$AC_TOTAL_PARTS is active; the counter is incremented by the value 1 with each M02.
$MC_PART_COUNTER_MCODE[0] has no significance.
Activation of the workpiece counter $AC_ACTUAL_PARTS:

$AC_TOTAL_PARTS is active; the counter is incremented by a value of "1" with each M17.
Activation of the workpiece counter $AC_SPECIAL_PARTS:

$AC_SPECIAL_PARTS is active.
With each M77 the following is realized: $AC_SPECIAL_PARTS + 1
Deactivation of the workpiece counter $AC_ACTUAL_PARTS:

$AC_ACTUAL_PARTS is inactive
Activation of all counters:

$AC_REQUIRED_PARTS is active
Basic functions
2.20 Workpiece simulation
Display alarm for: $AC_REQUIRED_PARTS == $AC_SPECIAL_PARTS

$AC_TOTAL_PARTS is active; the counter is incremented by the value 1 with each M02.
$MC_PART_COUNTER_MCODE[0] has no significance.
$AC_ACTUAL_PARTS is active; the counter is incremented by a value of "1" with each M17.
$AC_SPECIAL_PARTS is active; the counter is incremented by a value of "1" with each M77.
Workpiece counter $AC_ACTUAL_PARTS is not processed during the program test / block
search:
$AC_ACTUAL_PARTS is active; the counter is incremented by a value of "1" with each M75,
apart from during the program test and search.
Cancellation of the count modes in the MD27880 $MC_PART_COUNTER with bit 0 = 1:


...
N100 $AC_REQUIRED_PARTS=-10 ; value <0: Set counting.
N200 M41 M43 ; no counting.
N300 M42
...
N500 $AC_REQUIRED_PARTS=52 ; value > 0: Counting in accordance with MD27880
activated.
N501 M43 ; counting.
N502 M42 M41 ; counting.
...
2.20 Workpiece simulation
Function
The actual part program is completely calculated in the tool simulation and the result is
graphically displayed in the user interface. The result of programming is verified without
traversing the machine axes. Incorrectly programmed machining steps are detected at an early
stage and incorrect machining on the workpiece prevented.
Basic functions
2.21 Data lists
Simulation NC
The simulation uses its own NC instance (simulation NC). Therefore, before a simulation is
started, the real NC must be aligned to the simulation NC. With this alignment, all active
machine data is read out of the NC and read into the simulation NC. The NC and cycle machine
data is included in the active machine data.
Compile cycles in simulation mode

Up to SW 4.4, no compile cycles are supported, as of SW 4.4 and higher only selected compile
cycles (CC) are supported for the workpiece simulation. The machine data of the supported
compile cycles is aligned once after the control has powered-up. An alignment with "simulation
start" does not take place!
Note
In part programs, CC-specific language commands and machine data of unsupported
CCs cannot be used (see also paragraph "CC-commands in the part program").
Special motion of supported CCs (OEM transformations) are - under certain circumstances -
incorrectly displayed.
CC-commands in the part program

Language commands in the part program of compile cycles that are not supported
(OMA1 ... OMA5, OEMIPO1/2, G810 ... G829, own procedures and functions) therefore result in
an alarm message and cancellation of the simulation without any individual handling.
Solution: Individually handle the missing CC-specific language elements in the part program
($P_SIM query). Example:

N1 G01 X200 F500
IF (1==$P_SIM)
N5 X300 ; CC not active for simulation.
ELSE
N5 X300 OMA1=10
ENDIF
2.21 Data lists
2.21.1 Function
Various counters with a range of values from 0 to 999,999,999 are available with the
"Workpiece counter" function in the form of channel-specific system variables. Read and write
access to the system variables is possible.
The following channel-specific machine data can be used to control counter activation, counter
reset timing and the counting algorithm.
Basic functions
2.21 Data lists
System variables for workpiece counting

$AC_REQUIRED_PARTS Number of workpieces to be produced (setpoint number of workpieces)
In this counter the number of workpieces at which the actual workpiece
count ($AC_ACTUAL_PARTS) will be reset to "0" can be defined.
MD27880 can be used to activate the generation of the display alarm:
"Channel %1 workpiece target = %2 reached"
and of the channel-specific NC/PLC interface signal:
DB21, DBX317.1 (workpiece target reached)
.
$AC_TOTAL_PARTS Total number of completed workpieces (actual workpiece total)
This counter specifies the total number of workpieces produced since
the start time. The value is only automatically reset to "0" when the
control runs up with default values.
$AC_ACTUAL_PARTS Number of completed workpieces (actual workpiece total)
This counter registers the total number of workpieces produced since
the start time. On condition that $AC_REQUIRED_PARTS > 0, the
counter is automatically reset to "0" when the required number of work‐
pieces ($AC_REQUIRED_PARTS) is reached.
$AC_SPECIAL_PARTS Number of workpieces selected by the user
This counter supports user-specific workpiece counts. An alarm can be
defined to be output when the setpoint number of workpieces is reached
($AC_REQUIRED_PARTS). Users must reset the counter themselves.
Note
All workpiece counters are set to "0" when the control runs up with default values and can be
read and written independent of their activation.
2.21.2 Machine data
2.21.2.1 General machine data
Displaying machine data
Number Identifier: $MM_ Description

SINUMERIK Operate
9421 MA_AXES_SHOW_GEO_FIRST Display geo axes of channel first
9422 MA_PRESET_MODE PRESET / basic offset in JOG.
9423 MA_MAX_SKP_LEVEL Maximum number of skip levels
Basic functions
2.21 Data lists
NC-specific machine data
Number Identifier: $MN_ Description

10010 ASSIGN_CHAN_TO_MODE_GROUP Channel valid in mode group
10125 EES_NC_NAME NCU name for the generation of unique NC program
names in the EES mode
10280 PROG_FUNCTION_MASK Comparison commands ">" and "<"
10700 PREPROCESSING_LEVEL Program preprocessing level
10702 IGNORE_SINGLEBLOCK_MASK Prevent single block stop
10707 PROG_TEST_MASK Program test modes
10708 SERUPRO_MASK Block change modes
10710 PROG_SD_RESET_SAVE_TAB Setting data to be updated
10711 NC_LANGUAGE_CONFIGURATION Manner of handling the languages, whose related op‐
tion or function is not activated.
10713 M_NO_FCT_STOPRE M function with preprocessing stop
10715 M_NO_FCT_CYCLE M function to be replaced by subprogram
10716 M_NO_FCT_CYCLE_NAME Subroutine name for M function replacement
10717 T_NO_FCT_CYCLE_NAME Name of the tool change cycle for T function replace‐
ment
10718 M_NO_FCT_CYCLE_PAR M function replacement with parameters
10719 T_NO_FCT_CYCLE_MODE Parameter assignment for T function replacement
11450 SEARCH_RUN_MODE Block search parameter settings
11470 REPOS_MODE_MASK Repositioning properties
11600 BAG_MASK Mode group response to ASUB
11602 ASUP_START_MASK Ignore stop conditions for ASUB
11604 ASUP_START_PRIO_LEVEL Priorities, starting from which $MN_AS‐
UP_START_MASK is effective
11610 ASUP_EDITABLE Activating a user-specific ASUB program
11612 ASUP_EDIT_PROTECTION_LEVEL Protection level of user-specific ASUB program
11620 PROG_EVENT_NAME Program name for PROG_EVENT
11625 FILE_ONLY_WITH_EXTENSION When calling the program, only search for files with a
file ID
11626 CYCLES_ONLY_IN_CYCDIR Only search for programs with interface in the cycle
directories
11717 D_NO_FCT_CYCLE_NAME Subroutine name for D function replacement
15700 LANG_SUB_NAME Name for replacement subprogram
15702 LANG_SUB_PATH Call path for replacement subprogram
17200 GMMC_INFO_NO_UNIT Global HMI info (without physical unit)
17201 GMMC_INFO_NO_UNIT_STATUS Global HMI status info (without physical unit)
18045 EES_MODE_INFO Mode in which the EES function operates
18360 MM_EXT_PROG_BUFFER_SIZE FIFO buffer size for execution from external source
(DRAM)
18362 MM_EXT_PROG_NUM Number of program levels that can be processed si‐
multaneously from external
Basic functions
2.21 Data lists
2.21.2.2 Channel-specific machine data
Basic machine data
Number Identifier: $MC_ Description

20000 CHAN_NAME Channel name
20050 AXCONF_GEOAX_ASSIGN_TAB Assignment of geometry axis to channel axis
20060 AXCONF_GEOAX_NAME_TAB Channel axis name in the channel
20070 AXCONF_MACHAX_USED Machine axis number valid in channel
20080 AXCONF_CHANAX_NAME_TAB Channel axis name in channel [channel axis no.]: 0...7
20090 SPIND_DEF_MASTER_SPIND Basic setting of master spindle in channel
20100 DIAMETER_AX_DEF Geometry axis with transverse axis function
20106 PROG_EVENT_IGN_SINGLEBLOCK Prog events ignore the single block
20107 PROG_EVENT_IGN_INHIBIT Prog events ignore the read-in disable
20108 PROG_EVENT_MASK Event-driven program calls
20109 PROG_EVENT_MASK_PROPERTIES Prog events properties
20114 MODESWITCH_MASK Setting for REPOS
20116 IGNORE_INHIBIT_ASUP Execute user ASUPs completely in spite of read-in dis‐
able
20117 IGNORE_SINGLEBLOCK_ASUP Process user ASUPs completely in spite of single-block
processing
20160 CUBIC_SPLINE_BLOCKS Number of blocks for C spline
20170 COMPRESS_BLOCK_PATH_LIMIT Maximum traversing length of NC block for compres‐
sion
20191 IGN_PROG_STATE_ASUP Do not display the execution of the interrupt routine on
the operator panel
20192 PROG_EVENT_IGN_PROG_STATE Do not display the execution of the program events on
the operator panel
20193 PROG_EVENT_IGN_STOP Prog events ignore the Stop key
20194 IGNORE_NONCSTART_ASUP ASUP start permitted despite pending alarm response
"NC Start disable" for certain user alarms
20210 CUTCOM_CORNER_LIMIT Max. angle for intersection calculation with tool radius
compensation
20220 CUTCOM_MAX_DISC Maximum value for DISC
20230 CUTCOM_CURVE_INSERT_LIMIT Maximum angle for intersection calculation with tool ra‐
dius compensation
20240 CUTCOM_MAXNUM_CHECK_BLOCKS Blocks for predictive contour calculation with tool radius
compensation
20250 CUTCOM_MAXNUM_DUMMY_BLOCKS Maximum number of blocks without traversing motion
for TRC
20270 CUTTING_EDGE_DEFAULT Basic setting of tool cutting edge without programming
20400 LOOKAH_USE_VELO_NEXT_BLOCK Look Ahead to programmed following block velocity
20430 LOOKAH_NUM_OVR_POINTS Number of override points for Look Ahead
20440 LOOKAH_OVR_POINTS Override switch points for LookAhead
20500 CONST_VELO_MIN_TIME Minimum time with constant velocity
Basic functions
2.21 Data lists

20600 MAX_PATH_JERK Pathrelated maximum jerk
20610 ADD_MOVE_ACCEL_RESERVE Acceleration reserve for overlaid motions
20700 REFP_NC_START_LOCK NC start disable without reference point
20750 ALLOW_GO_IN_G96 G0 logic for G96, G961
20800 SPF_END_TO_VDI Subprogram end to PLC
21000 CIRCLE_ERROR_CONST Circle end point monitoring constant
21010 CIRCLE_ERROR_FACTOR Circle end point monitoring factor
21100 ORIENTATION_IS_EULER Angle definition for orientation programming
21110 X_AXIS_IN_OLD_X_Z_PLANE Coordinate system for automatic Frame definition
21200 LIFTFAST_DIST Traversing path for fast retraction from the contour
21210 SETINT_ASSIGN_FASTIN HW assignment of the ext. NC input byte for NC pro‐
gram interrupt:
21202 LIFTFAST_WITH_MIRROR Lift fast with mirror
Block search

20128 COLLECT_TOOL_CHANGE Tool change commands to the PLC after block search
22600 SERUPRO_SPEED_MODE Velocity for block search type 5
22601 SERUPRO_SPEED_FACTOR Velocity factor for block search type 5
22621 ENABLE_START_MODE_MASK_PRT Switches MD22620: START_MODE_MASK_ PRT free
for SERUPRO block search run
22622 DISABLE_PLC_START Allow part program start via PLC
22680 AUTO_IPTR_LOCK Disable interrupt pointer
Reset response

20110 RESET_MODE_MASK Initial setting after RESET / parts program end
20112 START_MODE_MASK Basic setting for NC start after part program start
20118 GEOAX_CHANGE_RESET Allow automatic geometry axis change
20120 TOOL_RESET_VALUE Tool length compensation when powering-up (RE‐
SET / part program end)
20121 TOOL_PRESEL_RESET_VALUE Preselected tool on RESET
20130 CUTTING_EDGE_RESET_VALUE Tool cutting edge length compensation when powering-
up (RESET / part program end)
20140 TRAFO_RESET_VALUE Transformation data set when powering-up (RE‐
SET / part program end)
20150 GCODE_RESET_VALUES Initial setting of the G groups
20152 GCODE_RESET_MODE Reset behavior of G groups
Basic functions
2.21 Data lists

20156 MAXNUM_GCODES_EXT Reset behavior of the external G groups
22620 START_MODE_MASK_PRT Initial setting at special NC Start after power-up and at
RESET
Auxiliary function settings

22000 AUXFU_ASSIGN_GROUP Auxiliary function group
22010 AUXFU_ASSIGN_TYPE Auxiliary function type
22020 AUXFU_ASSIGN_EXTENSION Auxiliary function extension
22030 AUXFU_ASSIGN_VALUE Auxiliary function value
22200 AUXFU_M_SYNC_TYPE Output timing of M functions
22210 AUXFU_S_SYNC_TYPE Output timing of S functions
22220 AUXFU_T_SYNC_TYPE Output timing of T functions
22230 AUXFU_H_SYNC_TYPE Output timing of H functions
22240 AUXFU_F_SYNC_TYPE Output timing of F functions
22250 AUXFU_D_SYNC_TYPE Output timing of D functions
22400 S_VALUES_ACTIVE_AFTER_RESET S function active after RESET
22410 F_VALUES_ACTIVE_AFTER_RESET F function active after RESET
22510 GCODE_GROUPS_TO_PLC G commands that are output to the NC/PLC interface
on block change / RESET
22550 TOOL_CHANGE_MODE New tool offset for M function
22560 TOOL_CHANGE_M_CODE M function for tool change
Memory settings

27900 REORG_LOG_LIMIT Percentage of IPO buffer for log file enable
28000 MM_REORG_LOG_FILE_MEM Memory size for REORG (DRAM)
28010 MM_NUM_REORG_LUD_MODULES Number of blocks for local user variables for REORG
28020 MM_NUM_LUD_NAMES_TOTAL Number of local user variables (DRAM)
28040 MM_LUD_VALUES_MEM Memory size for local user variables (DRAM)
28050 MM_NUM_R_PARAM Number of channelspecific R parameters (SRAM)
28060 MM_IPO_BUFFER_SIZE Number of NC blocks in IPO buffer (DRAM)
28070 MM_NUM_BLOCKS_IN_PREP Number of blocks for block preparation (DRAM)
28080 MM_NUM_USER_FRAMES Number of settable Frames (SRAM)
28090 MM_NUM_CC_BLOCK_ELEMENTS Number of block elements for compile cycles (DRAM)
28100 MM_NUM_CC_BLOCK_USER_MEM Size of block memory for compile cycles (DRAM)
28400 MM_ABSBLOCK Activating basis blocks with absolute values
28402 MM_ABSBLOCK_BUFFER_CONF Dimension size of upload buffer
28500 MM_PREP_TASK_STACK_SIZE Stack size of preparation task (DRAM)
Basic functions
2.21 Data lists
Program runtime and workpiece counter

27860 PROCESSTIMER_MODE Activate the runtime measurement
27880 PART_COUNTER Activate the workpiece counter
27882 PART_COUNTER_MCODE[ ] Workpiece counting via M command
2.21.2.3 Axis/spindlespecific machine data
Number Identifier: $MA_ Description

30465 AXIS_LANG_SUB_MASK Substitution of NC language commands
30550 AXCONF_ASSIGN_MASTER_CHAN Reset position of channel for axis change
30600 FIX_POINT_POS Fixed value positions of axes with G75
33100 COMPRESS_POS_TOL Maximum deviation with compensation
2.21.3 Setting data
2.21.3.1 Channelspecific setting data
Number Identifier $SC_ Description

42000 THREAD_START_ANGLE Start angle for thread
42010 THREAD_RAMP_DISP Acceleration behavior of axis when thread cutting
42100 DRY_RUN_FEED Dry run feedrate
42200 SINGLEBLOCK2_STOPRE Activate debug mode for SBL2
42220 CFG_STOP_ARRAY Configured stop: NC functions and subprograms be‐
fore which stops are to be made
42222 CFG_STOP_MASK Configured stop: G function transitions at which a stop
should be made
42224 CFG_STOP_ARRAY_MASK Configured stop: Release of SD42220
$SC_CFG_STOP_ARRAY
42444 TARGET_BLOCK_INCR_PROG Continuation mode after block search with calculation
42700 EXT_PROG_PATH Program path for external subroutine call EXTCALL
42750 ABSBLOCK_ENABLE Enable basic block display
42990 MAX_BLOCKS_IN_IPOBUFFER Maximum number of blocks in the interpolation buffer
Basic functions
Axes, coordinate systems, frames 3
3.1 Brief description
3.1.1 Axes
Machine axes
Machine axes are the axes that actually exist on a machine tool.
Channel axes
Every geometry axis and every special axis is assigned to a channel and, therefore, a channel
axis. Geometry axes and additional axes are always traversed in "their" channel.
Geometry axes
The three geometry axes always make up a fictitious rectangular coordinate system, the basic
coordinate system (BCS).
By using FRAMES (offset, rotation, scaling, mirroring), it is possible to image geometry axes of
the workpiece coordinate system (WCS) on the BCS.
Special axes
In contrast to geometry axes, no geometrical relationship is defined between the special axes.
Path axes
Path axes are interpolated together (all the path axes of a channel have a common path
interpolator).
All the path axes of one channel have the same acceleration phase, constant travel phase and
delay phase.
Positioning axes
Positioning axes are interpolated separately (each positioning axis has its own axis
interpolator). Each positioning axis has its own feedrate and acceleration characteristic.
Synchronized axes
Synchronous axes are interpolated together with path axes (all path axes and synchronous
axes of one channel have a common path interpolator).
Basic functions
Axes, coordinate systems, frames
All path axes and all synchronous axes of a channel have the same acceleration phase,
constant travel phase and deceleration phase.
Axis configuration
The machine data below are used to assign the geometry axes, special axes, channel axes and
machine axes as well as the names of the individual axis types:
MD20050 $MC_AXCONF_GEOAX_ASIGN_TAB (assignment of geometry axis to channel
axis)
MD20060 $MC_AXCONF_GEOAX_NAME_TAB (name of the geometry axis in the channel)
MD20070 $MC_AXCONF_MACHAX_USED (machine axis number valid in channel)
MD20080 $MC_AXCONF_CHANAX_NAME_TAB (name of the channel axis in the channel)
MD10000 $MN_AXCONF_MACHAX_NAME_TAB (machine axis name)
MD35000 $MA_SPIND_ASSIGN_TO_MACHAX (assignment of spindle to machine axis)
Replaceable geometry axes

The "Replaceable geometry axes" function allows the geometry axes in a grouping to be
replaced by other channel axes.
Axes that are initially configured as synchronous special axes in a channel can replace any
selected geometry axis in response to a program command.
Link axis
Link axes are axes, which are physically connected to another NCU and whose position is
controlled from this NCU. Link axes can be assigned dynamically to channels of another NCU.
Link axes are not local axes from the perspective of a particular NCU.
The axis container concept is used for the dynamic modification of the assignment to an NCU.
Axis replacement with GET and RELEASE from the part program is not available for link axes
across NCU boundaries.
Further information
The link axes are described under Distributed systems (Page 729).
Axis container
An axis container is a circular buffer data structure, in which local axes and/or link axes are
assigned to channels. The entries in the circular buffer can be shifted cyclically.
In addition to the direct reference to local axes or link axes, the link axis configuration in the
logical machine axis image also allows references to axis containers.
This type of reference consists of:
● Axis container number
● A slot (circular buffer location within the corresponding container)
Basic functions
The entry in a circular buffer location contains:

● A local axis
or
● A link axis
Further information
The axis containers are described under Distributed systems (Page 729).
3.1.2 Coordinate systems
MCS
The machine coordinate system (MCS) has the following properties:
● It is defined by the machine axes.
● The machine axes can be perpendicular to each other to form Cartesian system or arranged
in any other way.
● The names of the machine axes can be defined.
● The machine axes can be linear or rotary axes.
BCS
The basic coordinates system (BCS) has the following properties:
● The geometry axes form a perpendicular Cartesian coordinate system.
● The BCS is derived from a kinematic transformation of the MCS.
BZS
The basic zero system (BZS) is the basic coordinate system with a basic offset.
SZS
The settable zero system (SZS) is the workpiece coordinate system with a programmable
frame from the viewpoint of the WCS. The workpiece zero is defined by the settable frames G54
to G599.
WCS
The workpiece coordinate system (WCS) has the following properties:
● In the workpiece coordinate system all the axes coordinates are programmed (parts
program).
● It is made up of geometry axes and special axes.
● Geometry axes always form a perpendicular Cartesian coordinate system
Basic functions
● Special axes form a coordinate system without any geometrical relation between the special
axes.
● The names of the geometry axes and special axes can be defined.
● The workpiece coordinate system can be translated, rotated, scaled or mirrored with
FRAMES (TRANS, ROT, SCALE, MIRROR).
Multiple translations, rotational movements, etc., are also possible.
External work offset

The zero offset external has the following properties:
● At a time defined in the PLC, a predefined additional zero offset between the basic and the
workpiece coordinate systems is activated.
● The magnitudes of the offsets can be set by the following for each of the axes involved:
– PLC
– Operator panel
– Part program
● Activated offsets take effect at the instant the first motion block of the relevant axes is
processed after offset activation. The offsets are superimposed on the programmed path
(no interpolation).
The velocity, at which the zero offset external is applied, is as follows:
Programmed F value + 1/2 JOG velocity
The zero offset external is traversed at the end of G0 blocks.
● The activated offsets are retained after RESET and end of program.
● After POWER ON, the last active offset is still stored in the control but must be reactivated
by the PLC.
3.1.3 Frames
A frame is a closed calculation rule (algorithm) that translates one Cartesian coordinate system
into another.
Frame components
A frame consists of the following components:
Frame components Programmable with:

Offset Coarse offset TRANS
ATRANS (additive translation component)
CTRANS (work offset for multiple axes)
G58 (axial work offset)
Fine offset CFINE
G59 (axial work offset)
Basic functions
Frame components Programmable with:

Rotation ROT / ROTS
AROT / AROTS
CROTS
Scaling SCALE
ASCALE
Mirroring MIRROR
AMIRROR
6FDOLQJ
0LUURULQJ
5RWDWLRQ
)LQHRIIVHW
&RDUVHRIIVHW
Figure 3-1 Frame components
Coarse and fine offsets

As the assignment of machine axes to channel axes and, in particular, to geometry axes, can
be different in all channels, there is consequently no unique cross-channel geometric
relationship between the channel axes. Therefore, only offset, scaling and mirroring is possible
for NCU-global frames. Rotations are not possible.
G58: Absolute axis-specific programmable work offset (coarse offset)

The absolute component of the translatory offset (coarse offset) is programmed axis-
specifically with G58. The additive component of the translatory offset (fine offset) is retained.
G59: Additive axis-specific programmable work offset (fine offset)

The additive component of the translatory offset (fine offset) is programmed axis-specifically
with G59. The absolute component of the translatory offset (coarse offset) is retained.
G59 can only be used when the fine offset has been released:
● MD18600 $MN_MM_FRAME_FINE_TRANS = TRUE
● MD24000 $MC_FRAME_ADD_COMPONENTS = TRUE
Basic functions
Rotation
Orientations in space are defined via frame rotations as follows:
● Rotation with ROT defines the individual rotations for all geometry axes.
● Solid angles with ROTS, AROTS, CROTS define the orientation of a plane in space.
● Frame rotation with TOFRAME defines a frame with a Z axis pointing in the tool direction.
Scaling
SCALE is used to program the programmable scale factors for all geometry axes and special
axes.
If a new scaling is to be based on a previous scaling, rotation, translation or mirroring, then
ASCALE must be programmed.
Mirroring
The following machine data is used to set how the mirroring is to be performed:
MD10610 $MN_MIRROR_REF_AX
Concatenation
Frames and frame components can be combined using the concatenation operator ":". The
channel-specific active frame $P_ACTFRAME results, for example, from the chaining of all
active frames of the channel:
$P_ACTFRAME = $P_PARTFRAME : $P_SETFRAME : $P_EXTFRAME :

$P_ISO1FRAME : $P_ISO2FRAME : $P_ISO3FRAME :
$P_ACTBFRAME : $P_IFRAME : $P_GFRAME :
$P_TOOLFRAME : $P_WPFRAME : $P_TRAFRAME:
$P_PFRAME : $P_ISO4FRAME : $P_CYCFRAME
Incremental dimensioning G91

Incremental programming with G91 is defined such that the offset value is traversed additively
to the incrementally programmed value when a work offset is selected.
The behavior depends on the setting in the setting data:
SD42440 $SC_FRAME_OFFSET_INCR_PROG (work offsets in frames)
Value Meaning
1 Work offset is applied on FRAME and incremental programming of an axis (= default setting).
0 Only the programmed path is traversed.
Basic functions
3.2 Axes
Consistency
When writing, reading and activating frames, e.g. using channel coordination, the user is solely
responsible for achieving consistent behavior within the channels. Cross-channel activation of
frames is not supported.
3.2 Axes
3.2.1 Overview
*HRPHWU\D[HV $GGLWLRQDOD[HV
&KDQQHOD[HV
3DWKD[HV 3RVLWLRQLQJD[HV 6SLQGOHD[HV

&RPPDQGD[HV *DQWU\D[HV
)HHGUDWHGHWHUPL 6\QFKUR 5HFLSURFDWLQJD[HV &RXSOHGD[HV
QLQJSDWKD[HV QRXV 3/&D[HV *XLGHYDOXHFRXSOLQJ
)*5283 D[HV D[HV
.LQHPDWLFV
WUDQVIRUPDWLRQ
/LQHDUD[HV
5RWDU\D[HV
2ULHQWDWLRQD[HV
0DFKLQHD[HV
Figure 3-2 Relationship between geometry axes, special axes and machine axes
0DFKLQHD[HV
/RFDOPDFKLQHD[LV /LQND[LVYLD1&8OLQN
Basic functions
3.2 Axes
Figure 3-3 Local and external machine axes (link axes)
3.2.2 Machine axes
Meaning
Machine axes are the axes that actually exist on a machine tool.
:=0
<
6&
%
Figure 3-4 Machine axes X, Y, Z, B, S on a Cartesian machine
Application
The following can be machine axes:
● Geometry axes X, Y, Z
● Orientation axes A, B, C
● Loader axes
● Tool turrets
● Axes for tool magazine
● Axes for automatic tool changer
● Spindle sleeves
Basic functions
3.2 Axes
● Axes for pallet changers

● Etc.
3.2.3 Channel axes
Meaning
Each geometry axis and each special axis is assigned to a channel. Geometry axes and
additional axes are always traversed in "their" channel.
3.2.4 Geometry axes
Meaning
The three geometry axes always make up a fictitious rectangular coordinate system.
By using FRAMES (offset, rotation, scaling, mirroring), it is possible to image geometry axes of
the workpiece coordinate system (WCS) on the BCS.
Application
Geometry axes are used to program the workpiece geometry (the contour).
Plane selection G17, G18 and G19 (DIN 66217) always refers to the three geometry axes. That
is why it is advantageous to name the three geometry axes X, Y and Z.
3.2.5 Special axes
Significance
In contrast to geometry axes, no geometrical relationship is defined between the special axes.
Note
Geometry axes have an exactly defined relationship in the form of a rightangled coordinate
system.
Special axes are part of the basic coordinate system (BCS). With FRAMES (translation,
scaling, mirroring), special axes of the workpiece coordinate system can be mapped on the
basic coordinate system.
Basic functions
3.2 Axes
Application
Typical special axes are:
● Rotary axes
● Machine tool axes
● Tool revolver axes
● Loader axes
3.2.6 Path axes
Meaning
Path axes are interpolated together (all the path axes of a channel have a common path
interpolator).
All the path axes of one channel have the same acceleration phase, constant travel phase and
delay phase.
The feedrate programmed under address F (path feedrate) applies to all the path axes
programmed in a block, with the following exceptions:
● An axis has been programmed that has been defined as having no control over the path
velocity with instruction FGROUP.
● Axes programmed with instructions POS or POSA have an individual feedrate setting (axis
interpolator).
Application
Path axes are used to machine the workpiece with the programmed contour.
3.2.7 Positioning axes
Meaning
Positioning axes are interpolated separately (each positioning axis has its own axis
interpolator). Each positioning axis has its own feedrate and acceleration characteristic.
Positioning axes can be programmed in addition to path axes (even in the same block). Path
axis interpolation (path interpolator) is not affected by the positioning axes. Path axes and the
individual positioning axes do not necessarily reach their block end points at the same time.
Basic functions
3.2 Axes
Instructions POS and POSA are used to program positioning axes and define block change
criteria:
● POS
Block change takes place when the path axes and positioning axes have reached their block
end points.
● POSA
Block change takes place when the path axes have reached their end of block position.
Positioning axes continue to traverse beyond block limits to their block end point.
Concurrent positioning axes differ from positioning axes in that they:
● Only receive their block end points from the PLC
● Can be started at any time (not at block limits)
● Do not affect the execution of current part programs.
Application
Typical positioning axes are:
● Loaders for moving workpieces away from machine
● Tool magazine/turret
Further information
● Function Manual Axes and Spindles
● Function Manual Synchronized Actions
● Function Manual PLC and Basic Program
3.2.8 Main axes
Meaning
A main axis is an axis that is interpolated by the main run.
This interpolation can be started as follows:
● From synchronized actions
(as command axes due to an event via block-related, modal or static synchronized actions)
● From the PLC via special function blocks in the basic PLC program
(named as a concurrent positioning axis or a PLC axis)
● Via the setting data or from the part program
(as an asynchronous or block-synchronous oscillating axis)
Basic functions
3.2 Axes
Channel control
An axis interpolated by the main axis reacts in terms of:
● NC stop
● Alarm handling
● Program control
● End of program
● RESET
Note
The response at the end of the program varies. The axis movement need not always be
completed and, therefore, may carry on beyond the end of the program.
Application
Certain axes in the main run can be decoupled at the channel response triggered by the NC
program sequence and controlled from the PLC. These axes are also interpolated in the main
run and respond independently for the channel and program sequence.
A PLC-controlled axis can then be controlled independently by the NC. This concerns the
following actions:
● The sequence for canceling the axis (equivalent to delete distancetogo)
● Stopping or interrupting the axis
● Continuing the axis (continue sequence of motion)
● Resetting the axis to its basic status
3.2.9 Synchronized axes
Meaning
Synchronous axes are components of the path axes, which are not referenced in order to
calculate the tool path velocity. They are interpolated together with path axes (all path axes and
synchronous axes of one channel have a common path interpolator).
All path axes and all synchronous axes of a channel have the same acceleration phase,
constant travel phase and deceleration phase.
The feedrate (path feedrate) programmed under address F applies to all the path axes
programmed in a block but not to the synchronous axes.
Synchronous axes take the same time to cover the programmed path as the path axes.
FGROUP command
The command FGROUP specifies whether the axis is a feed-defining path axis (used to calculate
the path velocity) or a synchronous axis (not used to calculate the path velocity).
Basic functions
3.2 Axes
Example
N05 G00 G94 G90 M3 S1000 X0 Y0 Z0 ;
N10 FGROUP(X,Y) ; Axes X and Y are path axes,
Z is a synchronous axis
N20 G01 X100 Y100 F1000 ; Progr. feedrate 1000 mm/min.
Feedrate of axis X = 707 mm/min.
Feedrate of axis Y = 707 mm/min.
N30 FGROUP (X) ; Axis X is a path axis,
axis Y is a synchronous axis
N20 X200 Y150 ; Progr. Feedrate 1000 mm/min
Feedrate of Axis X = 1000 mm/min
Feedrate of Axis Y is set to 500 mm/min,
because only half the distance is to be
traversed.
Note
The channel axis name must be used for the FGROUP command.
This is defined by the machine data:
Application
In the case of helical interpolation FGROUP can be programmed to determine whether:
● The programmed feedrate should be valid on the path
(all three programmed axes are path axes)
● The programmed feedrate should be valid on the circle
(two axes are path axes and the infeed axis is a synchronous axis)
Basic functions
3.2 Axes
3.2.10 Axis configuration
Assigning geometry, special, channel and machine axes and drives
1&8 *HRPHWU\D[LVQDPHV &KDQQHOD[HVXVHG

0'0&B$;&21)B*(2$;B1$0(B7$%>N@>Q@ 0'0&B$;&21)B*(2$;B$66,*1B7$%>N@>Q@
&KDQQHON &KDQQHON
&KDQQHO &KDQQHO
VWJHRPHWU\D[LV >@ ; VWJHRPHWU\D[LV >@
QGJHRPHWU\D[LV >@ < QGJHRPHWU\D[LV >@
UGJHRPHWU\D[LV >@ = UGJHRPHWU\D[LV >@
&KDQQHOD[LVQDPHV 0DFKLQHD[HVXVHG
0'0&B$;&21)B&+$1$;B1$0(B7$%>N@>Q@ 0'0&B$;&21)B0$&+$;B86('>N@>Q@
&KDQQHON &KDQQHON
&KDQQHO &KDQQHO
VWFKDQQHOD[LV >@ ; VWFKDQQHOD[LV >@
QGFKDQQHOD[LV >@ < QGFKDQQHOD[LV >@
UGFKDQQHOD[LV >@ = UGFKDQQHOD[LV >@
WKFKDQQHOD[LV >@ $ WKFKDQQHOD[LV >@
WKFKDQQHOD[LV >@ % WKFKDQQHOD[LV >@
WKFKDQQHOD[LV >@ 8 WKFKDQQHOD[LV >@
WKFKDQQHOD[LV >@ WKFKDQQHOD[LV >@

/RJLFDOPDFKLQHD[LVLPDJH
0'01B$;&21)B/2*,&B0$&+$;B7$%>Q@
>@ >@ >@ >@ >@ >@ >@ >@
1&B$;
&7B6/
$;
$;
$;
$;
$;
$;

$[LVFRQWDLQHUQDPHV
0'
01B$;&7B1$0(B7$%>Q@
/RFDOPDFKLQHD[HV
0' $[LVFRQWDLQHU&7 >@ &7
01B$;&21)B0$&+$;B1$0(B7$%>Q@ 0'01B$;&7B$;&21)B$66,*1B7$% >@ &7
VWPDFKLQHD[LV >@ $; 6ORW 6ORW >@ &7
QGPDFKLQHD[LV >@ $; >@ &7
UGPDFKLQHD[LV >@ $;

$;

$;
WKPDFKLQHD[LV >@ $;

B
B
&
WKPDFKLQHD[LV >@ $; &RQWDLQHUOLQND[LV

&
1
1
WKPDFKLQHD[LV >@ $; 0DFKLQHD[LV$;PRQ1&8QZLWK

1
WKPDFKLQHD[LV >@

&
Qำ
1
B
&
WKPDFKLQHD[LV >@

B
$

;
$;

6ORW 6ORW

/LQND[LV0DFKLQHD[LV$;RQ1&8
Figure 3-5 Axis assignment
Basic functions
3.2 Axes
1&8 6HWSRLQWFKDQQHORIWKHPDFKLQHD[LV
0'
0$B&75/287B02'8/(B15>$FKVH!@>Q@
VWPDFKLQHD[LV >@
QGPDFKLQHD[LV >@
UGPDFKLQHD[LV >@ /RJLFDOGULYHDGGUHVVHV
WKPDFKLQHD[LV >@ 0'
01B'5,9(B/2*,&B$''5(66
VWGULYH >@
QGGULYH >@
UGGULYH >@
$FWXDOYDOXHFKDQQHORIWKHPDFKLQHD[LV WKGULYH >@
0' >@
0$B(1&B02'8/(B15>$FKVH!@>Q@ >@

VWPDFKLQHD[LV >@
QGPDFKLQHD[LV >@
UGPDFKLQHD[LV >@
WKPDFKLQHD[LV >@

Figure 3-6 Drive assignment
Boundary conditions
● Leading zeros for user-defined axis names are ignored:
MD10000 `$MN_AXCONF_MACHAX_NAME_TAB[0] = X01 corresponds to X1
● The geometry axes must be assigned to the channel axes in ascending order without any
gaps.
● All channel axes that are not geometry axes are special axes.
Channel axis gaps

Normally, each channel axis defined in machine data MD20080
$MC_AXCONF_CHANAX_NAME_TAB must be assigned a machine axis via MD20070
$MC_AXCONF_MACHAX_USED.
In order to simplify commissioning series of machines with a different number of machine axes,
channel axes may also be defined, which are not assigned to any machine axis. As a result,
gaps can occur in the numbering sequence of the channel axes.
Any channel axis gaps must be explicitly enabled:
MD11640 $MN_ENABLE_CHAN_AX_GAP = 1
Without being enabled, a value of 0 in machine data MD20070
$MC_AXCONF_MACHAX_USED stops the assignment of further channel axes to machine
axes.
Example
Channel axis B is not assigned to a machine axis.
Basic functions
3.2 Axes
1&8
&KDQQHOD[LVQDPHV 0DFKLQHD[HVXVHG
0'0&B$;&21)B&+$1$;B1$0(B7$%>Q@>P@ 0'0&B$;&21)B0$&+$;B86('>Q@>P@
&KDQQHOQ &KDQQHOQ
&KDQQHO &KDQQHO
VWFKDQQHOD[LV >@ ; VWFKDQQHOD[LV >@
QGFKDQQHOD[LV >@ < QGFKDQQHOD[LV >@
UGFKDQQHOD[LV >@ = UGFKDQQHOD[LV >@
WKFKDQQHOD[LV >@ $ WKFKDQQHOD[LV >@
WKFKDQQHOD[LV >@ % &KDQQHOD[LVJDS WKFKDQQHOD[LV >@
WKFKDQQHOD[LV >@ WKFKDQQHOD[LV >@

Figure 3-7 Axis configuration with channel axis gap (excerpt)
Boundary conditions
● Channel axes without assigned machine axes (channel axis gaps) are, regarding the
number and indexing of the channel axes, treated just like normal channel axes with
associated machine axes.
● If a channel axis without assigned machine axis (channel axis gap) is defined as geometry
axis, then this is rejected without an alarm.
3.2.11 Link axes
Meaning
A link axis is a machine axis that is not on the NCU from which it is traversed. The name of a
local machine axis is not entered in the machine data for the logical machine axis image of the
traversing NCU, but the NCU and machine axis name of the NCU to which it is physically
connected.
As an example, machine axis AX1 of NCU2 should be traversed from NCU1:
● NCU1: MD10002 $MN_AXCONF_LOGIC_MACHAX_TAB[n] = NC2_AX1
Requirement
The NCUs involved must be connected using link communication as a requirement for using
link axes. The link axes and link communication functions are described in detail in Distributed
systems (Page 729).
Basic functions
3.3 Zero points and reference points
3.3.1 Reference points in working space
Zeros and reference points

The neutral position of the machine is obtained from the coordinate axes and the constructive
characteristics of the machine. The zero of the coordinate system is obtained by defining a
suitable reference point on the machine in its neutral position.
The position of the coordinate systems (MCS, BCS, BZS, SZS, WCS) is determined by means
of zeros.
Zero points Reference points

M = Machine zero R = Reference point
W = Workpiece zero T = Toolholder reference point
Machine zero M
The machine zero M defines the machine coordinate system MCS. All other reference points
refer to the machine zero.
Workpiece zero W
The workpiece zero W defines the workpiece coordinate system in relation to the machine zero
M. The programmed part-program blocks are executed in the workpiece coordinate system
WCS.
Reference point R
The position of the reference point R is defined by cam switches. Reference point R calibrates
the position measuring system.
With incremental encoders, the reference point must be approached every time the control
power is switched on. The control can only then work with the measuring system and transfer
all position values to the coordinate systems.
Toolholder reference point T

The toolholder reference point T is located on the toolholder locator. By entering the tool
lengths, the control calculates the distance between the tool tip (TCP Tool Center Position) and
the toolholder reference point.
Basic functions
Example: Zeros and reference points on a turning machine
0 :
7
Basic functions
3.3.2 Position of coordinate systems and reference points
Switching on the control

For incremental measuring encoders, the reference point must be approached after each
switch-on of the controller to ensure the controller can transfer all of the position values to the
coordinate system.
;

0DFKLQH]HUR :RUNSLHFH]HUR
:RUNSLHFHOHQJWK
==
0 :

6SLQGOH
① Machine coordinate system (MCS)

② Workpiece coordinate system (WCS)
Figure 3-8 Position of the coordinate systems through machine zero point M and workpiece zero point
W
;
=
5HIHUHQFHSRLQW
7 5
7RROKROGHU
0DFKLQH]HUR
7RROFDUULHU
/
UHIHUHQFHSRLQW
;
/
=
0
Figure 3-9 Position of the reference point to the machine zero point
Basic functions
3.4 Coordinate systems
3.4.1 Overview
Definitions
DIN 66217 stipulates that when programming machine tools, right-angled, rectangular
(Cartesian) coordinate systems must be used. The positive directions of the coordinate axes
can be determined using the "right-hand rule".
<
;
=
Figure 3-10 Right_hand_rule
The coordinate system used when programming is referred to the workpiece. Programming is
realized independent of whether the tool or the workpiece is moved. When programming, it is
always assumed that the tool traverses relative to the coordinate system of the workpiece,
which is intended to be stationary.
Positive (clockwise) rotation of rotary axes can also be defined using the "right-hand rule". If the
thumb of the right hand points towards the positive direction of a coordinate axis (linear axis),
then the fingers point in the positive direction of rotation of the associated rotary axis.
=
&
r r

$ %
r
; <
Basic functions
Figure 3-11 Clockwise, rectangular Cartesian coordinate system
Coordinate systems
The following coordinate systems are defined for machine tools:
Coordinate system Abbreviation Remark

Workpiece Coordinate System WCS Programming the traversing motion of the geome‐
try axes for machining the workpiece is written in
the WCS.
Settable Zero System SZS Coordinate transformation using frames:
WCS ⇒ SZS
Basic Zero System BZS Coordinate transformation using frames:
SZS ⇒ BZS:
Basic Coordinate System BCS Coordinate transformation using frames:
BZS ⇒ BCS:
Machine Coordinate System MCS Coordinate transformation using frames and kine‐
matic transformation:
BCS ⇒ MCS:
The programmed traversing motion of the geome‐
try axes in WCS is mapped to the machine axes of
MCS using frames and kinematic transformations.
A kinematic transformation is used to derive the
BCS from the MCS. In this way, functions such as
manual traverse, for example, are effective not in
the MCS but in the BCS.
:&6
3B75$)5$0(3B3)5$0(
3B,62)5$0(3B&<&)5$0(
6=6
3B722/)5$0(3B:3)5$0(
LQD
3B,)5$0(3B*)5$0(
FK
H
%=6
DP
)U
3B$&7%)5$0(
3B3$57)5$0(3B6(7)5$0(3B(;7)5$0(
3B,62)5$0(3B,62)5$0(3B,62)5$0(
%&6
+DQGZKHHO'5)RIIVHWRYHUODLGPRYHPHQWH[WHUQDOZRUNRIIVHWNLQHPDWLF
WUDQVIRUPDWLRQ
0&6
5HIHUHQFHSRLQWRIIVHW
Figure 3-12 Coordinate systems, frames, and kinematic transformations
Basic functions
3.4.2 Machine coordinate system (MCS)
Machine coordinate system (MCS)

The machine coordinate system (MCS) is made up of all physically available machine axes.
&
<
Figure 3-13 MCS with machine axes X, Y, Z, B, C (5-axis milling machine)
;
=
0
Figure 3-14 MCS with machine axes X, Z (turning machine)
Basic functions
Axial preset offset

The reference point of the control in the machine coordinate system (machine zero) can be
reset via the "Preset offset (PRESETON)" function.
CAUTION
Loss of the encoder adjustment
After a preset offset, the appropriate machine axis is in the "Not referenced" state! This means
that when using absolute encoders, the encoder adjustment is lost and must be performed
again (e.g. by calibration with a laser interferometer ). The use of PRESETON in combination
with absolute encoders is therefore not recommended.
Note
We recommend that the function is only used for machine axes that do not require a reference
point.
In order to restore the original machine coordinate system, the machine axis must be re-
referenced, e.g. with G74 (reference point approach).
The machine axes are not moved with the preset offset.
Further information
● "NC Programming" Programming Manual, supplemental commands
● "NC Programming" Programming Manual, coordinate transformations (FRAMES)
3.4.2.1 Actual value setting with loss of the referencing status (PRESETON)
Function
The PRESETON() procedure sets a new actual value for one or more axes in the machine
coordinate system (MCS). This corresponds to work offset of the axis MCS. The axis is not
traversed.
A preprocessing stop with synchronization is triggered by PRESETON. The actual position is not
assigned until the axis is at standstill.
If the axis is not assigned to the channel for PRESETON, the next steps depend on the
replacement behavior parameterized in the following machine data:
MD30552 $MA_AUTO_GET_TYPE
Referencing status
By setting a new actual value in the machine coordinate system, the referencing status of the
machine axis is reset.
DB31, ... DBX60.4/.5 = 0 (referenced/synchronized measuring system 1/2)
It is recommended that PRESETON only be used for axes that do not require a reference point.
Basic functions
To restore the original machine coordinate system, the measuring system of the machine axis
must be referenced again, e.g. through active referencing from the part program (G74).
CAUTION
Loss of the referencing status
By setting a new actual value in the machine coordinate system with PRESETON, the
referencing status of the machine axis is reset to "not referenced/synchronized".
Programming
Syntax
PRESETON(<axis_1>, <value_1> [, <axis_2>, <value_2>, ... <axis_8>,
<value_8>])
Meaning
PRESETON: Actual value setting with loss of the referencing status

Preprocessing Yes
stop:
<axis_x>: Machine axis name
Type: AXIS
Value range: Machine axis names defined in the channel
<value_x>: New actual value of the machine axis in the machine coordinate system
(MCS)
The input is made in the current valid system of units (inch/metric)
An active diameter programming (DIAMON) is taken into account
Type: REAL
System variable
$AC_PRESET
The axis-specific system variable $AC_PRESET provides the vector from the zero point of the
currently offset MCS' to the zero point of the original MCS0 after the referencing of the machine
axis.
$AC_PRESET<axis> = $AC_PRESET<axis> + "current actual position of the axis in the MCS"
- "PRESETON actual position"
The work offset can be undone with the system variables:
PRESETON(<axis>, $VA_IM + $AC_PRESET[<axis>]) ; "current actual
position of the axis in the MCS'" + "offsets"
Basic functions
Example
Program code
N10 G1 X10 F5000
N20 PRESETON(X, $AA_IM[X]+70) ; actual value = 10 + 70 = 80 =>
; $AC_PRESET = $AC_PRESET - 70
Boundary conditions
Axes for which PRESETON must not be used

● Traversing path axes
● Traversing positioning axes
● Traversing command axes in spindle mode
● Traversing concurrent positioning axes (FC18)
● Axes involved in a transformation
● Axes on which one or more of the following safety Safety Integrated functions are active:
– Enable "Safe software limit switch"
MD36901 $MA_SAFE_FUNCTION_ENABLE[<SafeAxis>], bit 1 = 1
– Enable "Safe software cams", pair 1 ... 4, cam +/-
MD36901 $MA_SAFE_FUNCTION_ENABLE[<SafeAxis>], bits 8 ... 15 = 1
or
Enable "Safe cam track", cam 1 ... 30
MD36903 $MA_SAFE_CAM_ENABLE[<SafeAxis>], bit 0 ... 29 = 1
● Hirth axes
● Synchronized axes of a gantry grouping
● Axes for which the reference point approach from the part program (G74) is active
● Slave axis of a speed/torque coupling (master-slave)
Basic functions
Geometry axes
● PRESETON can be used on a stationary geometry axis when a further geometry axis is not
being traversed in the channel at the same time.
● PRESETON can be used on a stationary geometry axis even when a further geometry axis
is being traversed in the channel at the same time, but this axis is in the "neutral axis" state
or traversing as a command axis.

N10 G0 X0 Y0 ; X, Y: Geometry axes
N15 RELEASE(Y) ; Neutral axis
N20 PRESETON(Y,20) ; Actual position Y in the MCS =
20
N30 G0 X40 ; Geometry axis X traverses
N40 M30
Example: A further geometry (X) is traversing at the same time in the "neutral axis" state

N20 POS[X]=40 FA[X]=1000 ; X command axis
N30 DO PRESETON(Y,20) ; Actual position Y in the MCS =
20
N40 M30
Example: Geometry axis (X) traverses simultaneously as command axis
PLC-controlled axes
PRESETON can be used on PLC-controlled axes according to their current type.
Spindle states
The following table shows the reactions that occur when PRESETON is used on a spindle in a
synchronized action:
PRESETON in the NC program

Spindle mode Traversing sta‐ Assigned to the NC Main axis
tus program
Speed control mode In motion Alarm 22324 Alarm 22324
Stationary +/- +/-
Positioning mode SPOS In motion - +/-
Stationary +/- +/-
Positioning across block bounda‐ In motion Alarm 10610 -
ries SPOSA
Axis mode In motion - +/-
Stationary +/- +/-
+: Possible
-: Not possible
Basic functions
Axis couplings
● Leading axes: The sudden change of the leading axis position caused by PRESETON is not
traversed in the following axes. The coupling is not changed.
● Following axes: Only the overlaid position component of the following axis is affected
by PRESETON.
Gantry grouping
If PRESETON is used on the guide axis of a gantry grouping, the work offset is also performed
in all synchronized axes of the gantry grouping.
Indexing axes
PRESETON can be used on indexing axes.
Software limit switches, operating range limit, protection areas

If the axis position is outside the specified limits after a work offset by PRESETON, an alarm is
not displayed until an attempt is made to traverse the axis.
Block search with calculation

PRESETON commands are collected during the block search and executed with the NC start to
continue the NC program.
Position-dependent NC/PLC interface signals

The status of the position-dependent NC/PLC interface signals is redetermined based on the
new actual position.
Example: Fixed point positions
● Parameterized fixed point positions: MD30600 $MA_FIX_POINT_POS[0...3] = <fixed point
position 1...4>
● NC/PLC interface signals DB31, ... DBX75.3 ... 5 (JOG approach fixed point: reached)
If the axis is at a fixed point position with the exact stop tolerance, the associated NC/PLC
interface signal is set. The NC/PLC interface signal is reset when the actual value is set by
PRESETON to a different value outside the exact stop tolerance around the fixed point position.
DRF offset
A DRF offset of the axis is deleted by PRESETON.
Overlaid movement $AA_OFF

An overlaid movement from a synchronized action with $AA_OFF is not affected by
PRESETON.
Online tool offset FTOC

An active online tool offset from a synchronized action with FTOC remains active even after
PRESETON.
Axis-specific compensations
Axis-specific compensations remain active after PRESETON.
Basic functions
JOG mode
PRESETON must only be used on a stationary axis.
JOG mode, REF machine function

PRESETON must not be used.
3.4.2.2 Actual value setting without loss of the referencing status (PRESETONS)
Function
The PRESETONS() procedure sets a new actual value for one or more axes in the machine
coordinate system (MCS). This corresponds to work offset of the axis MCS. The axis is not
traversed.
A preprocessing stop with synchronization is triggered by PRESETONS. The actual position is
not assigned until the axis is at standstill.
If the axis for PRESETONS is not assigned to the channel, the next steps depend on the axis-
specific configuring of the axis replacement behavior:
MD30552 $MA_AUTO_GET_TYPE
Referencing status
By setting a new actual value in the machine coordinate system (MCS) with PRESETONS, the
referencing status of the machine axis is not changed.
Prerequisites
● Encoder type
PRESETONS is only possible with the following encoder types of the active measuring
system:
– MD30240 $MA_ENC_TYPE[<measuring system>] = 0 (simulated encoder)
– MD30240 $MA_ENC_TYPE[<measuring system>] = 1 (raw signal encoder)
● Referencing mode
PRESETONS is only possible with the following referencing modes of the active measuring
system:
– MD34200 $MA_ENC_REFP_MODE[<measuring system>] = 0 (reference point
approach not possible)
– MD34200 $MA_ENC_REFP_MODE[<measuring system>] = 1 (referencing of
incremental, rotary or linear measuring systems: zero pulse on the encoder track)
Commissioning
Axis-specific machine data

Actual value setting without loss of the referencing status (PRESETONS) must be set axis-
specifically:
Basic functions
MD30455 $MA_MISC_FUNCTION_MASK, bit 9 = 1
Note
PRESETON deactivated
Activation of the "Actual value setting without loss of the referencing status PRESETONS"
function deactivates the "Actual value setting with loss of the referencing status PRESETON"
function. The options mutually exclude each other.
Programming
Syntax
PRESETONS(<axis_1>, <value_1> [, <axis_2>, <value_2>, ... <axis_8>,
<value_8>])
Meaning
PRESETONS: Actual value setting with loss of the referencing status

Preprocessing Yes
stop:
<axis_x>: Machine axis name
Type: AXIS
Value range: Machine axis names defined in the channel
<value_x>: New current actual value of the machine axis in the machine coordinate
system (MCS)
The value refers to the active system of units (inch / metric)
An active diameter programming (DIAMON) is taken into account
Type: REAL
System variable
$AC_PRESET
The axis-specific system variable $AC_PRESET provides the vector from the zero point of the
currently offset MCS' to the zero point of the original MCS0 after the referencing of the machine
axis.
$AC_PRESET<axis> = $AC_PRESET<axis> + "current actual position of the axis in the MCS"
- "PRESETONS actual position"
The work offset can be undone with the system variables:
PRESETONS(<axis>, $VA_IM + $AC_PRESET[<axis>]) ; "current actual
position of the axis in the MCS'" + "offsets"
Example
Work offset of the X axis MCS by 70 units.
Basic functions
The programmed end position of the X axis (command axis) is transformed to the new MCS
with PRESETONS.
Program code
N10 G1 X10 F5000
N20 PRESETONS(X, $AA_IM[X]+70) ; actual value = 10 + 70 = 80 =>
; $AC_PRESET = $AC_PRESET - 70
Boundary conditions
Axes for which PRESETONS must not be used

● Traversing positioning axes
● Traversing command axes in spindle mode
● Traversing concurrent positioning axes (FC18)
● Axes involved in a transformation
● Traversing path axes
● Axes on which one or more of the following safety Safety Integrated functions are active:
– Enable "Safe software limit switch"
MD36901 $MA_SAFE_FUNCTION_ENABLE[<SafeAxis>], bit 1 = 1
– Enable "Safe software cams", pair 1 ... 4, cam +/-
MD36901 $MA_SAFE_FUNCTION_ENABLE[<SafeAxis>], bits 8 ... 15 = 1
or
Enable "Safe cam track", cam 1 ... 30
MD36903 $MA_SAFE_CAM_ENABLE[<SafeAxis>], bit 0 ... 29 = 1
● Hirth axes
● Synchronized axes of a gantry grouping
● Axes for which the reference point approach from the part program (G74) is active
● Slave axis of a speed/torque coupling (master-slave)
Basic functions
Geometry axes
● PRESETONS can be used on a stationary geometry axis when a further geometry axis is not
being traversed in the channel at the same time.
● PRESETONS can be used on a stationary geometry axis even when a further geometry axis
is being traversed in the channel at the same time, but this axis is in the "neutral axis" state
or traversing as a command axis.
Example: A further geometry (X) is traversing at the same time in the "neutral axis" state

1)
N15 RELEASE(Y) ; Neutral axis
N20 PRESETONS(Y,20) ; Actual position Y in the MCS =
20
N30 G0 X40 ; Geometry axis X traverses
N40 M30
1) Note
The release of an axis in the action part of a synchronized action does not ensure that the release
is on time.
N20 ID=1 WHEN 20.0 < $AA_IM[X] DO RELEASE(Y) PRESETONS(Y,20) ; NOT
recommended!
Example: Another geometry axis (X) is traversing at the same time as command axis

N20 POS[X]=40 FA[X]=1000 ; X command axis
N30 PRESETONS(Y,20) ; Actual position Y in the MCS =
20
N40 M30
PLC-controlled axes
PRESETONS can be used on PLC-controlled axes according to their current type.
Spindle states
The following table shows the reactions that occur when PRESETONS is used on a spindle in a
synchronized action:
PRESETONS in the NC program

tus program
Speed control mode In motion Alarm 22324 Alarm 22324
Stationary +/- +/-
Positioning mode SPOS In motion - +/-
Stationary +/- +/-
Positioning across block bounda‐ In motion Alarm 10610 -
ries SPOSA
Basic functions
PRESETONS in the NC program

tus program
Axis mode In motion - +/-
Stationary +/- +/-
+: Possible
-: Not possible
Axis couplings
● Leading axes: The sudden change of the leading axis position caused by PRESETONS is not
traversed in the following axes. The coupling is not changed.
● Following axes: Only the overlaid position component of the following axis is affected
by PRESETONS.
Gantry grouping
If PRESETONS is used on the guide axis of a gantry grouping, the work offset is also performed
in all synchronized axes of the gantry grouping.
Indexing axes
PRESETONS can be used on indexing axes.
Software limit switches, operating range limit, protection areas

If the axis position is outside the specified limits after a work offset by PRESETONS, an alarm is
not displayed until an attempt is made to traverse the axis.

PRESETONS commands are collected during the block search and executed with the NC start
to continue the NC program.
Position-dependent NC/PLC interface signals

The status of the position-dependent NC/PLC interface signals is redetermined based on the
new actual position.
Example: Fixed point positions
● Parameterized fixed point positions: MD30600 $MA_FIX_POINT_POS[0...3] = <fixed point
position 1...4>
● NC/PLC interface signals DB31, ... DBX75.3 ... 5 (JOG approach fixed point: reached)
If the axis is at a fixed point position with the exact stop tolerance, the associated NC/PLC
interface signal is set. The NC/PLC interface signal is reset when the actual value is set by
PRESETONS to a different value outside the exact stop tolerance around the fixed point position.
DRF offset
A DRF offset of the axis is deleted by PRESETONS.
Overlaid movement $AA_OFF

An overlaid movement from a synchronized action with $AA_OFF is not affected by
PRESETONS.
Basic functions
Online tool offset FTOC

An active online tool offset from a synchronized action with FTOC remains active even after
PRESETONS.
Axis-specific compensations
Axis-specific compensations remain active after PRESETONS.
JOG mode
PRESETONS must only be used on a stationary axis.
JOG mode, REF machine function

PRESETONS must not be used.
In a synchronized action for an axis, if several PRESETONS instructions are included, then only
the last instruction in the sequence from left to right is actually executed.
Example:
Program code
N10 ID=1 WHEN TRUE DO PRESETONS(X,40) PRESETONS(X,39) PRESETONS(X,38)
; This is equivalent to:
N10 ID=1 WHEN TRUE DO PRESETONS(X,38)
3.4.3 Basic coordinate system (BCS)
Basic coordinate system (BCS)

The basic coordinate system (BCS) consists of three mutually perpendicular axes (geometry
axes) as well as other special axes, which are not interrelated geometrically.
Machine tools without kinematic transformation

BCS and MCS always coincide when the BCS can be mapped onto the MCS without kinematic
transformation (e.g. TRANSMIT / face transformation, 5-axis transformation and up to three
machine axes).
On such machines, machine axes and geometry axes can have the same names.
Basic functions
<
0&6 %&6
;
=
0DFKLQH]HUR
Figure 3-15 MCS=BCS without kinematic transformation
Machine tools with kinematic transformation

The BCS and MCS do not coincide when the BCS is mapped onto the MCS with kinematic
transformation (e.g. TRANSMIT / face transformation, 5-axis transformation or more than three
axes).
On such machines the machine axes and geometry axes must have different names.
<%.6
\0.6 .LQHPDWLF
WUDQVIRUPDWLRQ
;%.6
=%.6
;0.6 %DVLFFRRUGLQDWHV\VWHP%&6
=0.6
0DFKLQHFRRUGLQDWH
V\VWHP0&6
Figure 3-16 Kinematic transformation between the MCS and BCS
Machine kinematics
The workpiece is always programmed in a two- or three-dimensional, right-angled coordinate
system (WCS). However, such workpieces are being programmed ever more frequently on
machine tools with rotary axes or linear axes not perpendicular to one another. Kinematic
transformation is used to represent coordinates programmed in the workpiece coordinate
system (rectangular) in real machine movements.
Basic functions
Further information
Function Manual Transformations, Multi-axis transformations
3.4.4 Basic zero system (BZS)
Basic zero system (BZS)

The basic zero system (BZS) is the basic coordinate system with a basic offset.
<
<
%DVLFRIIVHW
;
=
;
%DVLF]HURV\VWHP%=6
=
%DVLFFRRUGLQDWHV\VWHP
%&6
Figure 3-17 Basic offset between BCS and BZS
Basic offset
The basic offset describes the coordinate transformation between BCS and BZS. It can be
used, for example, to define the palette zero.
The basic offset comprises:
● External work offset
● DRF offset
● Superimposed motion
Basic functions
● Chained system frames

● Chained basic frames

=

<
0

;
① A kinematic transformation is not active. This means that the machine coordinate system and
the basic coordinate system coincide.
② The basic zero system (BZS) with the pallet zero are obtained from the basic offset.
③ The settable work offset G54 or G55 specifies the "settable zero system" (SZS) for work‐
piece 1 or workpiece 2 respectively.
④ The workpiece coordinate system (WCS) results from the programmable coordinate trans‐
formation.
Figure 3-18 Example for coordinate systems on machine tool
The following applies:

● The user can change the basic offset from the part program, by means of an operator action
and from the PLC.
● If the basic offset is to take effect immediately, an ASUB can be started via the PLC
using FC9 in order to execute the appropriate G command.
Note
Recommendation to the machine manufacturer
Use the 3rd basic offset onwards for your own applications.
The 1st and 2nd basic offset are reserved for "PRESET" and the "Zero offset external".
Basic functions
3.4.5 Settable zero system (SZS)
Settable zero system (SZS)

The "settable zero system" (SZS) is the workpiece coordinate system WCS with a
programmable frame (viewed from the perspective of the WCS). The workpiece zero is defined
by the settable FRAMES G54 to G599.
<
<
*ಹ*
;
=
;
6HWWDEOH]HURV\VWHP6=6
=
%DVLF]HURV\VWHP
%=6
Figure 3-19 Settable FRAME G54 ... G599 between BZS and SZS
Programmable offsets act on the "settable zero system". All programmable offsets refer to the
"settable zero system".
WCS actual-value display in WCS or SZS

The actual values of the axes in the machine coordinate system (MCS) or the WCS can be
displayed on the HMI operator interface. For displays in WCS, the actual values can also be
displayed in relation to the SZS. The corresponding parameterization takes place through the
machine data:
MD9424 $MM_MA_COORDINATE_SYSTEM (coordinate system for actual value display)
Value Meaning
0 Actual value display in relation to the WCS
1 Actual value display in relation to the SZS
Note
Display of the current coordinate system
When "Actual-value display in relation to the SZS" is active, the WCS is still displayed on the
HMI operator interface as the coordinate system to which the actual-value display relates.
Basic functions
Example
Actual value display in relation to the WCS or SZS
Code (excerpt) Actual value display: Actual value display:

Axis X (WCS) Axis X (SZS)
N10 X100 100 100
N20 X0 0 0
N30 $P_PFRAME = CTRANS(X,10) 0 10
N40 X100 100 110
3.4.6 Workpiece coordinate system (WCS)
Workpiece coordinate system (WCS)

The workpiece coordinate system (WCS) is the programming basis.
<
<
3URJUDPPDEOH)5$0(ZLWK
3B3)5$0(
;
=
;
:RUNSLHFHFRRUGLQDWHV\VWHP
:&6
=
6HWWDEOH]HURV\VWHP
6=6
Figure 3-20 Programmable FRAME between SZS and WCS
Basic functions
3.4.7 Additive offsets
3.4.7.1 External work offsets

The external work offset is a linear offset between the basic coordinate system (BCS) and the
basic zero system (BZS).
]%16
]%.6
[%16
$$B(75$163B(;7)5$0(
[%.6
The external work offset $AA_ETRANS is effective in two ways depending on the machine data
parameterization:
1. The $AA_ETRANS system variable has a direct effect as offset value after activation by the
NC/PLC interface signal.
2. The value of the $AA_ETRANS system variable is taken into the system frame
$P:EXTFRAME and the data management frame $P_EXTFR after activation by the NC/
PLC interface signal. The active complete frame $P_ACTFRAME is then recalculated.
Machine data
In conjunction with the $AA_ETRANS system variable, a distinction is made between two
procedures which are selected via the following machine data:
MD28082 $MC_MM_SYSTEM_FRAME_MASK, bit1 = <value>
<Value> Meaning
0 Function: Direct writing of $AA_ETRANS[<axis>] by the PLC, HMI or NC program.
Enable to traverse the work offset of $AA_ETRANS[<axis>] in the next possible traversing block: DB31, ...
DBX3.0
1 Function: Activation of the active system frame $P:EXTFRAME and the data management frame $P_EXTFR
Enable to traverse the work offset of $AA_ETRANS[<axis>] through: DB31, ... DBX3.0. The following is per‐
formed in the channel:
● Stop of all traversing movements in the channel (except command and PLC axes)
● Preprocessing stop with subsequent reorganization (STOPRE)
● Coarse offset of the active frame $P_EXTFRAME[<axis>] = $AA_ETRANS[<axis>]
● Coarse offset of the data management frame $P_EXTFR[<axis>] = $AA_ETRANS[<axis>]
● Recalculation of the active complete frame $P_ACTFRAME
● Traversing of the offset in the programmed axes.
● Continuation of the interrupted traversing movement or the NC program
Basic functions
Programming
Syntax
$AA_ETRANS[<axis>] = <value>
Meaning
$AA_ETRANS: System variable to buffer the external work offset

<axis>: Channel axis
<value>: Offset value
NC/PLC interface signal

Activation of the external work offset:
DB31, ... DBX3.0 = 0 → 1 ⇒ $P_EXTFRAME[<axis>] = $P_EXTFR[<axis>] =
$AA_ETRANS[<axis>]
Suppression: External work offset

● The SUPA command suppresses the external work offset while the block is being processed.
● Active external work offsets are suppressed for the duration of the reference point approach
through the G74 command (reference point approach) and the equivalent operator actions
in the reference point approach mode.
● With G74, i.e. "Automatic" or "MDI" mode, the previously active external work offset
automatically becomes active again with the next traversing movement in the block.
● After a mode change from the reference point approach mode, the NC/PLC interface signal
for the referenced axes must be set for reactivation.
3.4.7.2 DRF offset

The DRF offset enables the adjustment of an additive incremental work offset for geometry and
additional axes in the basic coordinate system through handwheel.
System variable
The DRF offset can be read from the axis-specific system variable:
$AC_DRF[<Axis>]
Further information
Function Manual Axes and Spindles; Manual traversing
3.4.7.3 Reset behavior

The reset and Power On behavior of the $P_EXTFRAME active frame and of the $P_EXTFR
data management frame can be set with machine data:
Basic functions
Machine data
● The reset behavior for the system frame active of the $P_EXTFRAME external work offset
in the channel is set with the following machine data:
● MD24006 $MC_CHSFRAME_RESET_MASK, bit 1 = <value>
Value Meaning
The active system frame of the external work offset after channel/program end reset is:
0 Not active
1 Active
● The Power On behavior of the channel-specific system frame of the $P_EXTFR external
work offset of the data management is set with the following machine data:
MD24008 $MC_CHSFRAME_POWERON_MASK, bit 1 = <value>
Value Meaning
The $P_EXTFR system frame of the external work offset for Power On
0 Not deleted
1 Deleted
3.4.8 Axis-specific overlay ($AA_OFF)
3.4.8.1 Function
Axis-specific system variable $AA_OFF[<axis>] can specify an absolute position or an
incremental distance of the specified axis in a synchronous action, for example. The resulting
traversing motion is then executed in parallel with the traversing motions of the channel of the
axis.
$AA_OFF[<axis>] = <value>
Machine data
Parameterization of the overlaid motion

The following settings for the overlaid movement are made in the axis-specific machine data:
36750 $MA_AA_OFF_MODE, bit<n> = <value>
Bit Value Meaning

0 0 Interpretation of the value of $AA_OFF as the absolute position
1 Interpretation of the value of $AA_OFF as the incremental path
1 0 The overlaid movement is deselected for channel reset.
1 The overlaid movement maintained beyond channel reset.
Basic functions
Bit Value Meaning

2 0 In JOG mode, an overlaid movement is not retracted.
1 In JOG mode, an overlaid movement is retracted.
3 0 A superimposed motion is interrupted for NC stop.
1 A superimposed motion is not interrupted for NC stop.
System variable
Integrated path of the axis overlay

The integrated value of the overlaid movement can be read from the axis-specific system
variable.
<value> = $AA_OFF_VAL[<axis>]
3.4.8.3 Programming: Deselecting overlays axis-specifically (CORROF)

The following axis-specific overlays (overrides) are deleted with the CORROF procedure:
● Additive work offsets (DRF offsets) set via handwheel traversal
● Position offsets programmed via the $AA_OFF system variable
A preprocessing stop is initiated through the deletion of an overlay (override) value and the
position component of the deselected overlaid movement is transferred to the position in the
basic coordinate system. Whereby, no axis is traversed.
The position value that can be read via the $AA_IM system variable (current MCS setpoint of
the axis) does not change in the machine coordinate system.
The position value that can be read via the $AA_IW system variable (current WCS setpoint of
the axis) changes in the workpiece coordinate system because it now contains the deselected
component of the overlaid movement.
Note
CORROF can be programmed in an NC program.
CORROF must not be programmed in a synchronized action.
Syntax
CORROF(<Axis>,"<String>"[,<Axis>,"<String>"])
Meaning
CORROF: Procedure for the deselection of the following offsets and overlays of an axis:
● DRF offset
● Position offsets ($AA_OFF)
Effective‐ Modal
ness:
Basic functions
<Axis>: Axis identifier (channel, geometry or machine axis identifier)

Data type: AXIS
<String>: Character string for the definition of the overlay type
Data type: BOOL
Value Meaning
DRF DRF offset
AA_OFF Position offset ($AA_OFF)
Examples
Example 1: Axis-specific deselection of a DRF offset (1)

A DRF offset is generated in the X axis by DRF handwheel traversal. No DRF offsets are
operative for any other axes in the channel.

N10 CORROF(X,"DRF") ; CORROF has the same effect as DRFOF here.
...
Example 2: Axis-specific deselection of a DRF offset (2)

A DRF offset is generated in the X and Y axes by DRF handwheel traversal. No DRF offsets are

; Only the DRF offset of the X axis is deselected; the DRF offset of the Y axis is
retained.
; With DRFOF, both offsets would have been deselected.
N10 CORROF(X,"DRF")
...
Example 3: Axis-specific deselection of a $AA_OFF position offset

; A position offset == 10 is interpolated for the X axis.
N10 WHEN TRUE DO $AA_OFF[X]=10 G4 F5
...
; The position offset of the X axis is deselected: $AA_OFF[X]=0
; The X axis is not traversed.
; The position offset is added to the current position of the X axis.
N80 CORROF(X,"AA_OFF")
...
Basic functions
Example 4: Axis-specific deselection of a DRF offset and a $AA_OFF position offset (1)
A DRF offset is generated in the X axis by DRF handwheel traversal. No DRF offsets are

; A position offset of 10 is interpolated for the X axis.
...
; Only the DRF offset and the position offset of the X axis are deselected.
; The DRF offset of the Y axis is retained.
N70 CORROF(X,"DRF",X,"AA_OFF")
...
Example 5: Axis-specific deselection of a DRF offset and a $AA_OFF position offset (2)
A DRF offset is generated in the X and Y axes by DRF handwheel traversal. No DRF offsets are

; A position offset == 10 is interpolated for the X axis.
...
; The DRF offset of the Y axis and the position offset of the X axis are deselected.
; The DRF offset of the X axis is retained.
N70 CORROF(Y,"DRF",X,"AA_OFF")
...
Further information
$AA_OFF_VAL
Once the position offset has been deselected by means of $AA_OFF, system variable
$AA_OFF_VAL (integrated distance of axis overlay) for the corresponding axis will equal zero.
$AA_OFF in JOG mode

Also in JOG mode, if $AA_OFF changes, the position offset will be interpolated as an overlaid
movement if this function has been enabled via machine data MD 36750
$MA_AA_OFF_MODE.
$AA_OFF in synchronized action

If a synchronized action which immediately resets $AA_OFF
(DO $AA_OFF[<axis>]=<value>) is active when the position offset is deselected using the
CORROF(<axis>,"AA_OFF"), then $AA_OFF will be deselected and not reset, and alarm
21660 will be displayed. However, if the synchronized action becomes active later, e.g. in the
block after CORROF, $AA_OFF will remain set and a position offset will be interpolated.
Basic functions
3.5 Frames
Automatic channel axis exchange

If an axis that is active in another channel has been programmed for a CORROF, it will be fetched
into the channel with an axis exchange (requirement: MD30552 $MA_AUTO_GET_TYPE > 0)
and the position offset and/or the DRF offset deselected.
3.5 Frames
3.5.1 Frame types

A frame is a data structure that contains values for offset (TRANS), fine offset (FINE), rotation
(ROT), mirroring (MIRROR) and scaling (SCALE) for axes.
When activating the frame, using the frame values, a static coordinate transformation for the
axes contained in the frame is performed using a defined algorithm.
Axis-specific frame
An axis-specific frame contains the frame values of an axis.
Example data structure of an axis-specific frame for geometry axis X:
Axis TRANS FINE ROT MIRROR SCALE

X 10.0 0.1 0.0 0 1
Channel-specific frame
A channel-specific frame contains frame values for all channel axes (geometry, special and
machine axes).
Rotations (ROT) are only included in the calculation for geometry axes.
A channel-specific frame is only active in the channel in which the frame is defined.
Example of the data structure of a channel-specific frame:
● Geometry axes: X, Y, Z
● Special axes: A
● Machine axes: AX1

X 10.0 0.1 0.0 0 1
Y 0.0 0.0 0.0 1 1
Z 0.0 0.0 45.0 0 1
A 2.0 0.1 0.0 0 2
AX1 0.0 0.0 0.0 0 0
Basic functions
3.5 Frames
Global frame
A global frame contains the frame values for all machine axes.
A global frame is active in all channels of the NC.
Example data structure of global frame:
● Machine axes: AX1, ... AX5

AX1 10.0 0.1 - 0 1
AX2 0.0 0.0 - 1 1
AX3 0.0 0.0 - 0 1
AX4 2.0 0.1 - 0 2
AX5 0.0 0.0 - 1 1
3.5.2 Frame components
3.5.2.1 Translation
Programming
The programming of the translation or coarse offset can be performed via the following
commands:
● Example of data management frames $P_UIFR
– Complete frame: $P_UIFR[<n>] = CTRANS(<K1>,<V1>[,<K2>,<V2>]
[,<K3>,<V3>])
with Km = coordinate x, y or z and Vm = offset m
– Frame component: $P_UIFR[<n>,<k>,TR] = <V>
with K = coordinate x, y or z and V = offset
● Example of programmable frame
– TRANS <K1> <V1> [<K2> <V2>][<K3> <V3>]
Programs examples:
Program code Remark

$P_UIFR[1] = CTRANS(X,10,Y,10) Complete frame
$P_UIFR[1,X,TR] = 10 Frame components
TRANS X=10 Y=10 Programmable frame
Basic functions
3.5 Frames
7UDQVODWLRQILQH
GLVSODFHPHQW
\
Figure 3-21 Offset in the Z direction
3.5.2.2 Fine offset
Parameterization
The fine offset is enabled via the machine data:
MD18600 $MN_MM_FRAME_FINE_TRANS = <value>
Value Meaning
0 The fine offset cannot be entered or programmed.
1 Fine offset is possible for settable frames, basic frames and the programmable frame via
command or program.
Programming
The programming of the translation or coarse offset can be performed via the following
commands:
● Example of data management frames $P_UIFR
– Complete frame: $P_UIFR[<n>] = CFINE(<K1>,<V1>[,<K2>,<V2>]
[,<K3>,<V3>])
– Frame component: $P_UIFR[<n>,<K>,FI] = <V>
with K = coordinate x, y or z and V = offset
● Example of programmable frame
– TRANS <K1> <V1> [<K2> <V2>][<K3> <V3>]
Programming examples:
Program code Remark

$P_UIFR[1] = CTRANS(X,10,Y,10) Complete frame
$P_UIFR[1,X,TR] = 10 Frame components
TRANS X=10 Y=10 Programmable frame
Basic functions
3.5 Frames
3.5.2.3 Rotation Overview (geometry axes only)
Function
The direction of rotation around the coordinate axes is determined by means of a right-hand,
rectangular coordinate system with axes x, y and z. If the rotary motion is in a clockwise
direction when looking in the positive direction of the coordinate axis, the direction of rotation
is positive. A, B and C designate rotations whose axes are parallel to the coordinate axes.
<
[
<
]
]
The following figure shows the new position of the coordinate system x', y' and z' after the
rotation around z with γ = -45°
$ [
&
Parameterization of the rotation sequence

The following machine data is used to set around which coordinate axes and in which order the
rotations are performed when more than one angle of rotation is programmed:
Basic functions
3.5 Frames
MD10600 $MN_FRAME_ANGLE_INPUT_MODE = <value>
Value Meaning
1 Euler angles in zy'x'' convention (RPY angles)
2 Euler angles in zx'z" convention
Note
For historical reasons, Euler angles in zx'z" convention can be used. However, it is strongly
recommended that only Euler angles in zy'x" convention (RPY angles) be used (see
Section Rotation with a Euler angles: ZY'X" convention (RPY angles) (Page 311)).
3.5.2.4 Rotation with a Euler angles: ZY'X" convention (RPY angles)

Euler angles in the ZY'X" convention are also called RPY angles. RPY is derived from rolling,
pitching and yawing:
<DZ
= 3LWFK
<
5ROO
For the ZY'X'' convention, the rotations are carried out in the following sequence:
\ೀ \ು \ೀ
] ]ಿ ]ಿ
\ಿ \ಿ
[ು
]ೀ ]ೀ ]ು
\
[ಿ [ಿ [ೀ [ೀ
Basic functions
3.5 Frames
Value range
With RPY angles, programmed values can only be unambiguously calculated back within the
following value ranges:
-180 ≤ x ≤ 180
-90 < y < 90
-180 ≤ z ≤ 180
Programming: Writing all rotation components

When programming the rotating components of a frame usingCROT, ROT or AROT, all rotating
components are always written to. Rotating components not explicitly programmed are
assigned a value of 0°.
Syntax
<frame> = CROT([<1st GAx>,<angle>,][<2nd GAx>,<angle>,][<3rd
GAx>,<angle>])
ROT [<1st GAx> <Angle>] [<2. GAx> <Angle>] [<3. GAx> <Angle>]
AROT [<1st GAx> <Angle>] [<2. GAx> <Angle>] [<3. GAx> <Angle>]
Meaning
CROT: Absolute rotation

<Frame>: Arbitrary active or data management frame
ROT: Absolute rotation
Reference frame: Programmable frame $P_PFRAME,
reference point: Zero point of the current workpiece coordinate system set
with G54 ... G57, G505 ... G599
AROT: Additive rotation
Reference frame: Programmable frame $P_PFRAME,
reference point: Zero point of the current workpiece coordinate system set
with G54 ... G57, G505 ... G599
<nth GAx>: Name of the nth geometry axis around which rotation is to be performed with
the specified angle. The value 0° is implicitly set as angle of rotation for a
geometry axis that has not been programmed.
Assignment of geometry axis to rotary axis:
Geometry axis Rotary axis
1st geometry axis x''
2nd geometry axis y'
3rd geometry axis z
<angle>: Angle specification in degrees.
[...]: The data in square brackets are optional.
Programming: Writing to a rotation component

When explicitly programming a rotation component of a frame, only the programmed rotation
component is written. Rotation components that have not been programmed remain
unchanged.
Basic functions
3.5 Frames
Syntax
<frame>[<index>,<GAx>,RT] = <angle>
Meaning
<Frame>: Arbitrary active frame or data management frame

<Index>: Array index of the frame, e.g. $P_UIFR[0 ... n]
<GAx>: Name of the geometry axis around which rotation is to be performed with the
specified angle.
RT: Keyword for rotation "RoTation"
<Angle> Angle specification in degrees.
Reading back the rotation components

In general, the same values are obtained when reading back the rotation components of a
frame as those that were programmed:
Programmed Values when reading back

x, RT y, RT z, RT
<Frame> = CROT(X,45,Y,30,Z,-20) 45 30 -20
Values outside the value range

Programmed values outside a value range are mapped on the range limits:

x, RT y, RT z, RT
<Frame> = CROT(X,190,Y,0,Z,-200) -170 0 160
Note
It is recommended that when writing the rotation components of the frame, the specified value
ranges are observed so that the same values are obtained when reading back the rotation
components.
Gimbal lock
Gimbal lock designates a geometric problem in which the rotation components can no longer
be unambiguously calculated back from the position vector. Gimbal lock occurs in RPY angles
with an angular position of the rotation component y = 90°. In this case, the rotation components
are converted by the control system after being written so that the following applies:
● Rotation component z = rotation component z - rotation component x
● Rotation component x = 0°
● Rotation component y = 90°
Basic functions
3.5 Frames

x, RT y, RT z, RT
<Frame> = CROT(X,30,Y,90,Z,40) 0 90 40 - 30 = 10
CAUTION
Different values for reading back the rotation component z
Because of the different conversion times after writing the complete frame or the writing
of individual rotation components of a data management frame and the writing of individual
rotation components of an active frame, different values can be read back for rotation
component z.
Differences when writing the complete frame and frame components

Two cases must be distinguished when writing the rotation components of a frame:
1. Writing the complete frame: <Frame> = CROT(X,a,Y,b,Z,c)
When writing the complete frame, the conversion is immediately at the time of writing.
2. Writing individual rotation components, e.g. rotation around X: <Frame>[0,X,RT]= <a>
When writing individual rotation components, the conversion depends on the storage
location of the frame:
– Data management frames
With data management frames, the conversion is at the time of activation of the frame
based on the rotation components written by this time. With regard to the conversion of
a data management frame, a data management frame therefore behaves in the same
way after writing individual rotation components as when writing the complete frame.
– Active frames
In the case of active frames, the conversion is immediately at the time of writing of the
rotation component.
Basic functions
3.5 Frames
Example
● Writing the complete frame
The conversion is made in each block after the complete frame has been written.

x, RT y, RT z, RT
N10 <Frame> = CROT(X,0,Y,90,Z,90) 0 90 90
N20 <Frame> = CROT(X,90,Y,90) 0 90 -90 1)
N30 <Frame> = CROT(X,90,Y,90,Z,90) 0 90 0 1)
1) Different values compared to the writing of individual rotation components of an active frame
● Writing individual rotation components of a data management frame

The conversion is performed on the activation of the data management frame. In the
example, at any time after N30.

x, RT y, RT z, RT
N10 <Data management frame>[0,X,RT] = 0 0 90 90
N20 <Data management frame>[0,Y,RT] = 90
N30 <Data management frame>[0,Z,RT] = 90
N10 <Data management frame>[0,X,RT] = 90 0 90 -90 1)
N10 <Data management frame>[0,X,RT] = 90 0 90 0 1)
1) Different values compared to the writing of individual rotation components of an active frame
● Writing individual rotation components of an active frame

Any required conversion is performed immediately on writing the rotation component.
The stored initial values of the active frame are: x = 0, y = 0, z = 0.

x, RT y, RT z, RT
N10 <Active frame>[0,X,RT] = 0 0 90 90
N20 <Active frame>[0,Y,RT] = 90
N10 <Active frame>[0,X,RT] = 90 0 90 0 1)
N10 <Active frame>[0,X,RT] = 90 0 90 90 1)
1) Different values compared to the writing of the complete frame or the writing of individual rotation
components of a data management frame
Basic functions
3.5 Frames
3.5.2.5 Rotation with a Euler angles: ZX'Z" convention

With Euler angles, the rotations are in the order z, x', z".
Note
Recommended use
For historical reasons, Euler angles in zx'z" convention can be used. However, it is strongly
recommended that only Euler angles in zy'x" convention (RPY angles) be used (see
Section Rotation with a Euler angles: ZY'X" convention (RPY angles) (Page 311)).

] ]ಿ ]ಿ \ು
]ೀ ]ೀ
[ೀ [ೀ [ು
\ಿ \ಿ \ೀ \ೀ
]ು
[ಿ [ಿ
Assignment of rotary axis to geometry axis
Rotary axis Geometry axis in channel

z 3rd geometry axis
x' 1st geometry axis
z'' 3rd geometry axis
Value range
Data from Euler angles can only be unambiguously calculated back within the following value
ranges:
0 <= x < 180

-180 <= y <= 180
-180 <= z <= 180
For data outside the specified value ranges, a modulo conversion is made referred to the value
of the particular range limit.
Note
It is recommended that when writing the rotation components of the frame, the specified value
ranges are observed so that the same values are obtained when reading back the rotation
components.
Basic functions
3.5 Frames
3.5.2.6 Rotation in any plane
CRPL - Constant Rotation Plane

The predefined function "Constant Rotation Plane" enables a rotation to be programmed for a
frame in an arbitrary plane (G17, G18, G19) without specifying the name of a geometry axis.
This enables rotations to be programmed in the third plane when only two geometry axes are
present in the channel due to the specific machine constellation.
Syntax
CRPL(<rotary axis>,<angle of rotation>)
Meaning
CRPL: Rotation in any plane

<rotary Axis around which the rotation is performed
axis>:
Type: INT
Value Meaning
0 Rotation in the active plane
1 Rotation around Z
2 Rotation around Y
3 Rotation around X
<angle of Angle in degrees through which the rotation is performed
rotation>:
Type: REAL
It is strongly recommended to observe the specified angular ranges. If the
limits are not observed, then an unambiguous reverse calculation is not
possible. Angles outside the limits are not rejected.
RPY angle: X -180 <= <angle of rotation> <= 180
Y -90 <= <angle of rotation> <= 90
Z -180 <= <angle of rotation> <= 180
ZX'Z" convention: X -180 <= <angle of rotation> <= 180
Y 0 <= <angle of rotation> <= 180
Z -180 <= <angle of rotation> <= 180
Chaining with frames

CRPL() can be chained with frames and known frame functions such as CTRANS(), CROT(),
CMIRROR(), CSCALE(), CFINE() etc.
Examples:
$P_PFRAME = $P_PFRAME : CRPL(0,30.0)
$P_PFRAME = CTRANS(X,10) : CRPL(1,30.0)
$P_PFRAME = CROT(X,10) : CRPL(2,30.0)
$P_PFRAME = CRPL(3,30.0) : CMIRROR(Y)
Basic functions
3.5 Frames
3.5.2.7 Scaling
6FDOLQJ
Programming
The program commands below are used to program the scaling:
$P_UIFR[1] = CSCALE(x,1,y,1)
SCALE x = 1y = 1
$P_UIFR[1,x,sc] = 1
3.5.2.8 Mirroring
0LUURULQJ
Programming
The program commands below are used to program a mirroring:
$P_UIFR[1] = CMIRROR(x,1,y,1)
MIRROR x = 1y = 1
$P_UIFR[1,x,mi] = 1
Basic functions
3.5 Frames
3.5.2.9 Chain operator

Frame components or complete frames can be combined into a complete frame using the chain
operator ( : ).
3.5.2.10 Programmable axis name

Geometry, channel and machine axis names can be used in the frame commands. The
programmed axis must be known to the channel-specific frames in the channel.
SPI
When programming frame commands, the SPI(<spindle number>) axis function can be
used in place of an axis name.
SPI(<spindle number>) forms the reference of the spindle to the channel axis.
→ refer to MD35000 $MA_SPIND_ASSIGN_TO_MACHAX[ ] (assignment of spindle to machine
axis)
The following frame commands can be programmed with SPI(spino):
CTRANS()
CFINE()
CMIRROR()
CSCALE()
A spindle can only be assigned to one rotary axis at a time. The CROT(..) function can
therefore not be programmed withSPI(), as only geometry axes are permitted forCROT().
The channel axis name or machine axis name of the axis belonging to the spindle is always
output when decompiling frames, even when axis names have been programmed in the part
program with SPI(..).
If the spindle is assigned e.g., to the Channel Axis A then the programming:
N10 $P_UIFR[1] =
CTRANS(SPI(1),33.33,X,1):CSCALE(SPI(1),33.33):CMIRROR(SPI(1))
during recompilation:
$P_UIFR[1]=CTRANS(X,1,A,33.33):CSCALE(A,33.33):CMIRROR(A)
If a spindle and an assigned axis are programmed in a frame command, then Alarm 16420
"Axis % multiply programmed" is output.
Example:
$P_UIFR[1] = CTRANS(SPI(1),33.33,X,1,A,44)
(The spindle is assigned to Axis A.)
Programming examples
$P_PFRAME[SPI(1),TR]=22.22
$P_PFRAME=CTRANS(X, axis value,Y,axis value,SPI(1),axis value)
Basic functions
3.5 Frames
$P_PFRAME=CSCALE(X,Scale,Y,scale,SPI(2),scale)
$P_PFRAME=CMIRROR(S1,Y,Z)
$P_UBFR=CTRANS(A,10):CFINE(SPI(1),0.1)
3.5.2.11 Coordinate transformation
6FDOLQJ
0LUURULQJ
5RWDWLRQ
)LQHRIIVHW
&RDUVHRIIVHW
The formulae below are used to discover the coordinate transformation for geometry axes:
:&6᪸%&6 Y 5 6 0 Y

W
%&6᪸:&6 Y
LQY0 LQY6 LQY5YW
V: Position vector in BCS

V': Position vector in WCS
3.5.3 Data management frames and active frames
3.5.3.1 Overview
Frame types
The following frame types are available:
● System frames ($P_PARTFR, ... see figure)
● Basic frames ($P_NCBFR[<n>], $P_CHBFR[<n>])
Basic functions
3.5 Frames
● Grinding frames ($P_GFR[<n>])

● Settable frames ($P_UIFR[<n>])
● Programmable frame ($P_PFRAME)
For all frame types except the programmable frame, one or more frames exist in the data
management (data management frames) in addition to the frame active in the channel. For the
programmable frame, only the frame active in the channel exists.
$UFKLYLQJ 3DUWSURJUDP 8VHULQWHUIDFH
*ULQGLQJIUDPHV
1&8RGHU&+$1
3B*)5>Q@
6\VWHPIUDPHV
&+$1 3B*)5>@
3B5(/)5 3B&<&)5
3B,62)5 3B75$)5
3B,62)5 3B:3)5 %DVLFIUDPHV 6HWWDEOHIUDPHV

3B722/)5 1&8 &+$1 1&8RGHU&+$1
3B,62)5
3B,62)5 3B(;7)5 3B1&%)5>Q@ 3B&+%)5>Q@ 3B8,)5>Q@
3B6(7)5
3B3$57)5 3B1&%)5>@ 3B&+%)5>@ 3B8,)5>@
***3,B6(78'7
$FWLYDWLRQRIGDWDVWRUDJHIUDPHVWKURXJK *)5$0(*)5$0(5HVHW
7UDQVIRUPDWLRQVZHFKVHO*(2$;
&KDQQHO $FWLYHIUDPHV
3B$&7)5$0( 3B3$57)5$0(3B6(7)5$0(3B(;7)5$0(
DFWLYHFRPSOHWHIUDPHWKURXJKFKDLQLQJ 3B,62)5$0(3B,62)5$0(3B,62)5$0(
RIDOODFWLYHIUDPHVLQWKHVSHFLILHGRUGHU 3B$&7%)5$0(3B,)5$0(3B*)5$0(
3B722/)5$0(3B:3)5$0(3B75$)5$0(
3B3)5$0(3B,62)5$0(3B&<&)5$0(
3DUWSURJUDP
Basic functions
3.5 Frames
Writing frames
Data management frames and active frames can be written from the part program. Only data
management frames can be written via the user interface.
Archiving frames
Only data management frames can be archived.
3.5.3.2 Activating data management frames

Data management frames become active frames as a result of the following actions:
● "Settable frames" G group: G54 ... G57, G500, G505 ... G599
● "Grinding frames" G group: GFRAME0 ... GFRAME100
● RESET and MD20110 $MC_RESET_MODE_MASK, bit14 == 1 (the current setting of the
basic frame is retained)
● Transformation changeover
● Changing the geometry axis assignment GEOAX
● From the HMI with PI service "_N_SETUDT"
Activation from the HMI

The activation of a data management frame from the HMI with PI service "_N_SETUDT" only
becomes active in the channel after a hot restart for the current part program.
The activation is effective in the reset state if the following machine data is set:
MD9440 $MM_ACTIVATE_SEL_USER_DATA (set active offset immediately)
Activating system frames

System frames are activated by:
● Programming the corresponding system function in the part program
● Operator control at SINUMERIK Operate
Note
Modifying system frames of the data management
In principle, system frames of the data management can be modified by the cycle
programmer and activated using a G500, G54...G599 command. However, this option
should only be used with reservation.
Activating data management frames

The behavior when activating data management frames is set using the following machine data:
Basic functions
3.5 Frames
MD24050 $MC_FRAME_SAA_MODE (save and activate data management frames)
Bit Val‐ Meaning

ue
0 0 @@@
1 ● Data management frames are only activated by programming the system variables
$P_CHBFRMASK, $P_NCBFRMASK and $P_CHSFRMASK.
● G500...G599 activates the appropriate settable frame.
1 0 Data management frames are implicitly described by functions, such as TOROT, PAROT,
external work offset and transformations.
1 Data management frames are not implicitly described by functions, such as TOROT,
PAROT, external work offset and transformations.
Activation of system frames via system variable $P_CHSFRMASK

The system frames of the data management can be activated using system variable
$P_CHSFRMASK. The value of the variables is specified as bit coded according to the
machine data:
MD28082 $MC_MM_SYSTEM_FRAME_MASK (system frames of the data management)
The corresponding system frame of the data management in the channel is activated by setting
a bit of system variable $P_CHSFRMASK to 1. For a value of 0, the currently active system
frame in the channel remains active.
Activating system frames after RESET

After RESET, the system frames in the channel are activated whose bits are set in the following
machine data:
MD24006 $MC_CHSFRAME_RESET_MASK (active system frames after Reset)
Activating system frames for TCARR, PAROT and TOROT, TOFRAME
The system frames for TCARR, PAROT and TOROT, TOFRAME are activated according to the
setting in the following machine data:
MD20150 $MC_GCODE_RESET_VALUES (reset setting of the G groups)
When changing over geometry axes using transformation selection/deselection or the GEOAX
command, the actual total frame $P_ACTFRAME is either deleted or is re-calculated using the
new geometry axis constellation and activated. The system frames and all other frames are
conditioned again in relation to the geometry axes.
3.5.3.3 NCU-global and channel-specific frames

● Settable frames and grinding frames can only be configured as NCU-global or channel-
specific frames.
● Basic frames can be configured as NCU-global and channel-specific frames.
● An NCU-global frame has the same effect in all channels of the NCU.
Basic functions
3.5 Frames
● All channels of an NCU can read and write NCU-global frames equally.
● As the assignment of machine axes to channel axes and, in particular, to geometry axes,
can be different in all channels, there is consequently no unique cross-channel geometric
relationship between the channel axes. Therefore, only offset, scaling and mirroring is
possible for NCU-global frames. Rotations are not possible.
Note
Program coordination
The coordination of channel-specific accesses to NCU-global frames is the sole responsibility
of the user. It is recommended that the commands for the program coordination be used.
Further information
3.5.4 Frame chain and coordinate systems
3.5.4.1 Overview
The figure below shows the frame chain for the current complete frame. The frame chain is
located between the basic coordinate system (BCS) and the workpiece coordinate system
(WCS).
The settable zero system (SZS) corresponds to the WCS transformed by the programmable
frame. The basic zero system (BZS) still includes the current settable frame. The system frame
for the external work offset exists only if it has been configured. Otherwise, the external work
offset is traversed as overlaid movement of the axis.
Basic functions
3.5 Frames
:&6
3B75$)5$0(3B3)5$0(
3B,62)5$0(3B&<&)5$0(
6=6
3B722/)5$0(3B:3)5$0(
Q
DL
3B,)5$0(3B*)5$0(
FK
H
%=6
D P
)U
3B$&7%)5$0(
3B3$57)5$0(3B6(7)5$0(3B(;7)5$0(
3B,62)5$0(3B,62)5$0(3B,62)5$0(
%&6
+DQGZKHHO'5)RIIVHWRYHUODLGPRYHPHQWH[WHUQDOZRUNRIIVHWNLQHPDWLF
WUDQVIRUPDWLRQ
0&6
WCS: Workpiece Coordinate System

SZS: Settable Zero System
BZS: Basic Zero System
BCS: Basic Coordinate System
MCS: Machine Coordinate System
Complete frame
The current complete frame $P_ACTFRAME results from the chaining of all active frames of the
frame chain:
$P_ACTFRAME = $P_PARTFRAME : $P_SETFRAME : $P_EXTFRAME :

$P_ACTBFRAME : $P_IFRAME : $P_GFRAME :
$P_TOOLFRAME :$P_WPFRAME : $P_TRAFRAME :
$P_PFRAME :$P_ISO4FRAME : $P_CYCFRAME
3.5.4.2 Relative coordinate systems

Relative coordinate systems display the current setpoint positions of the axes which lie relative
to a specified reference point in the active displayed coordinate system. No programming can
be done regarding the relative coordinate systems. Only the axis positions in these systems
can be read via the system variables.
The new display coordinate systems lie relative to WCS and SZS coordinate system and result
through transformation of the WCS or SZS axis positions with the active system frame
$P_RELFRAME. The relative coordinate systems can not only be displaced linearly, but also
rotated, mirrored, compressed or expanded.
Basic functions
3.5 Frames
The position indicator for axis setpoints is done in WCS or in SZS. The configuring is done via
HMI machine data. Always only one display-coordinate system is active in the channel. For this
reason only one relative frame is provided which generates both relative coordinate systems in
the same ratio. The HMI displays the relative coordinates according to the configuration.
6 5( /
:&
6 5(/
6=
(
$0
)5
(
(/
$0
B5
)5
3
(/
:&6
B5
3
6=6
Figure 3-22 Relative coordinate systems
The "Relative coordinate systems" function is activated with MD51036

$MNS_ENABLE_COORDINATE_REL=1.
The data maintenance frame $P_RELFR can be written in the part program and via BTSS. All
the frame components can be modified.
The active system frame $P_RELFRAME can be written in the part program and via BTSS.
The configuring of the system frame $P_RELFR is done via the following machine data:
Machine data Bit Meaning

MD28082 $MC_MM_SYSTEM_FRAME_MASK 11 Creation of $P_RELFR; with this, relative coordi‐
nate systems become existent.
MD28083 $MC_MM_SYSTEM_DATAFRAME_MASK 11 Data maintenance frame $P_RELFR
MD24006 $MC_CHSFRAME_RESET_MASK. 11 $P_RELFR becomes active at Reset
MD24007 $MC_CHSFRAME_RESET_CLEAR_MASK 11 $P_RELFR is deleted at Reset
MD24008 $MC_CHSFRAME_POWERON_MASK 11 $P_RELFR is deleted at PowerOn
The axis position in the relative coordinate system WCSRel can be read via the variable
$AA_PCS_REL[ax]. The variable can be read in part program, BTSS and via synchronized
actions.
The axis position in the relative coordinate system SZSRel can be read via the variable
$AA_ACS_REL[ax]. The variable can be read in part program, BTSS and via synchronized
actions.
Basic functions
3.5 Frames
The setting of a relative reference point via the operator panel is done via the general command
interface for the workpiece and tool measuring. The system frame $P_RELFR for relative
coordinate systems is calculated and activated as follows:
● $AC_MEAS_TYPE = 14
● PI-services _N_SETUDT(6, 7)
An example of setting the relative axis positions can be found in:
Further information
Function Manual Technologies; Measurement (M5)
3.5.4.3 Selectable SZS

Within a cycle, machining is performed in a cycle-specific workpiece coordinate system (WCS).
The cycle-specific WCS results from SZS transformed by the programmable frame
$P_PFRAME and/or cycle frame $P_CYCFRAME programmed for the cycle.
If a cycle is interrupted by a machine operator, e.g. through an NC stop, traversing should then
be performed in the original coordinate system (SZS) valid before the activation of the cycle.
Machine data
The specification how the SZS is to be calculated from the cycle-specific WCS is set via the
following machine data.
MD24030 $MC_FRAME_ACS_SET = <value>
<value> Meaning
0 SZS = WCS transformed with $P_TRAFRAME, $P_PFRAME, $P_ISO4FRAME and $P_CY‐
CFRAME
1 SZS = WCS transformed only with $P_CYCFRAME

0'0&B)5$0(B$&6B6(7 0'0&B)5$0(B$&6B6(7
< :&6 < :&6

; :&6 ; :&6
6 <6=6 6
:& :&
3B&<&)5$0(
3B75$)5$0(3B3)5$0( 6=6 ;6=6

<6=6 3B,62)5$0(3B&<&)5$0(
3B75$)5$0(3B3)5$0(
3B,62)5$0(
6=6 ;6=6
① SZS = WCS transformed with $P_TRAFRAME, $P_PFRAME, $P_ISO4FRAME and $P_CY‐

CFRAME
② SZS = WCS transformed only with $P_CYCFRAME
Basic functions
3.5 Frames
Effects
The reconfiguration of the SZS has an effect on:
● SZS-related actual values: Actual-value displays, system variables, e.g. $AA_IEN, etc.
● Manual traversing (JOG) of geometry axes in the SZS
3.5.4.4 Manual traversing of geometry axes either in the WCS or in the SZS ($AC_JOG_COORD)
Previously, geometry axes have been traversed manually in JOG mode in the WCS. In
addition, there is also the option to carry out this manual traversing in the SZS coordinate
system. The $AC_JOG_COORD variable enables the user to switch between manual
traversing in the WCS and SZS. The user can now select if he wants to traverse in the SZS or
the WCS.
During manual traversing in the JOG mode, the geometry axes can be traversed either in the
workpiece coordinate system (WCS) or in the settable zero system (SZS).
System variables
During manual traversing in the JOG mode, the geometry axes can be traversed either in the
workpiece coordinate system (WCS) or in the settable zero system (SZS). The selection is
made via the system variable $AC_JOG_COORD:
$AC_JOG_COORD = <value>
<Value> Meaning
0 Workpiece coordinate system (WCS)
1 Settable zero system (SZS)
Basic functions
3.5 Frames
3.5.4.5 Suppression of frames

Suppression of frames is performed channel-specifically via the commands G53, G135
and SUPA described in the following. Activation of the frame suppression results in jumps in the
position display (HMI) as well as in the position values in system variables that refer to the
WCS, SZS or BZS. The behavior can be set via machine data.
3$
68

:.6
3B75$)5$0(3B3)5$0(
*

3B,62)5$0(3B&<&)5$0(
* (16
3B722/)5$0(3B:3)5$0(
3B,)5$0(3B*)5$0(
%16
3B$&7%)5$0(
3B3$57)5$0(3B6(7)5$0(3B(;7)5$0(
3B,62)5$0(3B,62)5$0(3B,62)5$0(
%.6
+DQGZKHHO'5)PRYHPHQWRYHUODLGPRYHPHQW
([WHUQDOZRUNRIIVHW
.LQHPDWLFVWUDQVIRUPDWLRQ
0.6
Machine data
The behavior of position displays (HMI) and position values in system variables is specified via
the following machine data:
MD24020 $MC_FRAME_SUPPRESS_MODE, bit<n> = <value> (positions during frame
suppression)
Bit Val‐ Meaning

ue
0 0 Position values (OPI) with frame suppression 1)
1 Position values (OPI) without frame suppression 2)
Basic functions
3.5 Frames
Bit Val‐ Meaning

ue
1 0 Position values in system variables with frame suppression 1)
1 Position values in system variables without frame suppression 2)
1) Jump of the position value
2) No jump of the position value
Programming
Com‐ Meaning
mand
G53: Nonmodal suppression of the following frames:
$P_TRAFRAME : $P_PFRAME : $P_ISO4FRAME : $P_CYCFRAME
$P_IFRAME : $P_GFRAME : $P_TOOLFRAME : $P_WPFRAME :
G153: Non-modal suppression of the frames as for G53 plus following frames:
$P_PARTFRAME : $P_SETFRAME : $P_EXTFRAME : $P_ACTBFRAME
SUPA: Implicit preprocessing stop and non-modal suppression of the frames as for G53 and G135
plus following frames:
● Handwheel offsets (DRF)
● Overlaid movement
● External work offset
G500: Modal activation of the G500 frame. The G500 frame should normally be a zero frame.
DRFOF: Deactivation (deletion) of the handwheel offsets (DRF)
3.5.5 Frames of the frame chain
3.5.5.1 Overview
The following frames are available:
● Settable frames (G500, G54 ... G57, G505 ... G599)
● Grinding frames (GFRAME0 ... GFRAME100)
● Basic frames
● Programmable frame
● System frames
Basic functions
3.5 Frames
3.5.5.2 Settable frames ($P_UIFR[<n>])
Machine data
Channel-specific settable frames

The number of channel-specific settable frames is set with the following machine data:
MD28080 $MC_MM_NUM_USER_FRAMES = <number>
System variable index n = 0, 1, 2, ... <number> - 1
NCU-global settable frames

The number of NCU-global settable frames is set with the following machine data:
MD18601 $MN_MM_NUM_GLOBAL_USER_FRAMES = <number>
If the machine data has a value > 0, there are no channel-specific settable frames. The machine
data to set the channel-specific settable frames is then not evaluated.
Reset position of the G group of the settable frames

The reset position or which of the G commands of the settable frame-specific 8th G group take
effect after channel reset or Power On is set in:
MD20150 $MC_GCODE_RESET_VALUES[7] = <value>
Value G command
1 G500
2 G54
3 G55
4 G56
5 G57
6 G505
... ...
100 G599
Reset behavior of the grinding-specific G group

The reset behavior of the settable frame-specific 8th G group is set in:
MD20152 $MC_GCODE_RESET_MODE[7] = <value>
Value Meaning
After channel reset or part program end:
0 The settable frame-specific G command in accordance with MD20150 is active.
1 The currently active settable frame-specific G command remains active.
Basic functions
3.5 Frames
Note
The MD20152 $MC_GCODE_RESET_MODE machine data is evaluated only for:
MD20110 $MC_RESET_MODE_MASK, bit 0 == 1
System variables
$P_UIFR[<n>] (settable frames of the data management)

System variable $P_UIFR[<n>] can be used to read and write the settable frames of the data
management. The new values are not immediately active in the channel when writing a settable
frame of the data management. The activation in the channel only takes effect with the
programming of a work offset G500, G54...G599.
For NCU-global frames, the changed settable frame of the data management is active in each
channel of the NCU which executes a G500, G54..G599 command.
The settable frames in the data management are also stored during a data backup.
$P_IFRAME (active settable frame)

System variable $P_IFRAME can be used to read and write the settable frame active in the
channel. The new values are immediately active in the channel when writing the settable frame.
In the case of NCU-global settable frames, the changed active frame acts only in the channel
in which the new values were programmed. If the changed NCU-global settable frame is to be
active in all channels of the NCU, the settable frame active in the channel and the
corresponding settable frame of the data management must be written together:
$P_UIFR[<n>] = $P_IFRAME = <new value>
● $P_UIFR[<n>] (settable frame in the data management)
● $P_IFRAME (settable frame active in the channel)
For the changed settable frame to take effect in another channel, it must be activated in this
channel with the appropriate command, e.g. G54.
$P_UIFRNUM (number of active settable frame)

System variable $P_UIFRNUM can be used to read the index <n> of the settable frame of the
data management active in the channel:
Settable frame active in the channel $P_IFRAME == $P_UIFR[ $P_UIFRNUM ]
$P_UIFRNUM $P_IFRAME == $P_UIFR[<n>], where n =

0 0
1 1
2 2
... ...
99 99
Basic functions
3.5 Frames
Programming
Commands for activating a settable frame in the channel

The programming of a G500, G54...G599 command activates the settable frame of the
$P_UIFR[<n>] data management in the channel or the active $P_IFRAME settable frame set
identical to the settable frame of the $P_UIFR[<n>] data management:
G<x> ⇒ $P_IFRAME = $P_UIFR[<n>]
Command Active settable frame $P_IFRAME

G500 $P_UIFR[0]
G54 $P_UIFR[1]
G55 $P_UIFR[2]
G56 $P_UIFR[3]
G57 $P_UIFR[4]
G505 $P_UIFR[5]
... ...
G599 $P_UIFR[99]
Writing of settable frames through HMI/PLC

Only the settable frames of the data management can be written from the HMI or the PLC user
program.
3.5.5.3 Grinding frames $P_GFR[<n>]
Grinding frames are additional work offsets or "fit-dependent corrections" available particularly
for the grinding technology. They are added to the work offset of the adjustable frames
(Page 331).
3B*)5>@ 3B*)5>@
3B,)5$0(
(16 (16* (16*
%16
5$0(
&7%)
3B$
%.6ิ0.6
Figure 3-23 Grinding frames
Basic functions
3.5 Frames
Based on the base zero system (BZS), the settable zero system (SZS) results from the chaining
of the frames active in the channel:
$P_IFRAME: $P_GFRAME : $P_TOOLFRAME :$P_WPFRAME
Machine data
Number of channel-specific grinding frames

The number of channel-specific grinding frames is set in:
MD28079 $MN_MM_NUM_G_FRAMES = <number>
with <number> = 0, 1, 2, ... maximum number
Number of NCU-global grinding frames

The number of NCU-global grinding frames is set in:
MD18603 $MN_MM_NUM_GLOBAL_G_FRAMES = <number>
with <number> = 0, 1, 2, ... maximum number
If the machine data has a value > 0, there are no channel-specific grinding frames. The machine
data to set the channel-specific grinding frames is then not evaluated.
Reset position of the grinding-specific G group (64)

The reset position or which of the G commands of the grinding-specific 64th G group take effect
after channel reset or Power On is set in:
MD20150 $MC_GCODE_RESET_VALUES[63] = <value>
Value G command
1 GFRAME0 (zero frame)
2 GFRAME1
3 GFRAME2
... ...
101 GFRAME100
Reset behavior of the grinding-specific G group

The reset behavior of the grinding-specific 64th G group is set in:
MD20152 $MC_GCODE_RESET_MODE[63] = <value>
Value Meaning
After channel reset or part program end:
0 The grinding-specific G command in accordance with MD20150 is active.
1 The currently active grinding-specific G command remains active.
Basic functions
3.5 Frames
Note
The MD20152 $MC_GCODE_RESET_MODE machine data is evaluated only for:
MD20110 $MC_RESET_MODE_MASK, bit 0 == 1
System variables
$P_GFR[<n>] (grinding frames of the data management)

System variable $P_GFR[n] can be used to read and write the grinding frames of the data
management. The new values are not immediately active in the channel when writing a grinding
frame. The activation in the channel only takes effect with the programming of the appropriate
command GFRAME0...GFRAME100. For NCU-global frames, the changed frame only becomes
active in those channels of the NCU, which execute a GFRAME0 ... GFRAME100 command.
The grinding frames in the data management are also stored during a data backup.
Note
Display (SINUMERIK Operate)
The grinding frames of the data management are displayed in a separate window of the
SINUMERIK Operate user interface.
● Further information
Operating Manual Grinding; Section "Setting up the machine" > "Work offsets" > "Displaying
and editing seat-related fine offset"
Delete (SINUMERIK Operate)
The grinding frames of the data management can be deleted individually or, for example, after
a workpiece change, all together via the SINUMERIK Operate user interface.
● Further information
Operating Manual Grinding; Section "Setting up the machine" > "Work offsets" > "Displaying
and editing seat-related fine offset"
$P_GFRAME (active grinding frame)

The grinding frame active in the channel can be read from and written to the $P_GFRAME
system variable. The new values are immediately active in the channel when writing the active
grinding frame.
In the case of NCU-global grinding frames, the changed frame acts only in the channel in which
the new frame values were programmed.
If the changed NCU-global grinding frame is to be active in all channels of the NCU starting from
one channel, the $P_GFRAME grinding frame active in the grinding frame and the grinding
frame in the $P_GFR[<n>] data management must be written together:
$P_GFRAME = $P_GFR[<n>] = <new value>
For the changed grinding frame in the $P_GFR[<n>] data management to take effect in another
channel, it must be activated in this channel with the appropriate command GFRAME<n>.
Basic functions
3.5 Frames
$P_GFRNUM (number of the active grinding frame)

System variable $P_GFRNUM can be used to read the index <n> of the grinding frame of the
data management active in the channel:
Grinding frame active in the channel $P_GFRAME == $P_GFR[ $P_GFRNUM ]
$P_GFRAME grinding frame activated with the G $P_GFRNUM

command GFRAME<n>:
GFRAME0 0
GFRAME1 1
GFRAME2 2
... ...
GFRAME100 100
Programming
Command for activating a grinding frame in the channel

The programming of the GFRAME<n> command makes the associated grinding frame of the
$P_GFR[<n>] data management active in the channel. This sets the active $P_GFRAME
grinding frame identical to the $P_GFR[<n>] grinding frame of the data management:
GFRAME<n> ⇒ $P_GFRAME = $P_GFR[<n>]
Command Grinding frame activated in the channel

GFRAME0 $P_GFR[0] (null frame)
GFRAME1 $P_GFR[1]
... ...
GFRAME100 $P_GFR[100]
Syntax
GFRAME<n>
Meaning
GFRAME<n>: Activation of the grinding frame <n> of the data management

G group: 64
Basic position: MD20150 $MC_GCODE_RESET_VALUES[63]
<n>: Number of the grinding frame
Range of values: 0, 1, 2, ... 100
Writing of grinding frames through HMI/PLC

Only the grinding frames of the data management can be written from the HMI or the PLC user
program.
Basic functions
3.5 Frames
3.5.5.4 Channel-specific basic frames[<n>]
Machine data
Number of channel-specific basic frames

The number of channel-specific basic frames is set with the following machine data:
MD28081 $MC_MM_NUM_BASE_FRAMES = <number>
System variables
$P_CHBFR[<n>] (channel-specific basic frames of the data management)

System variable $P_CHBFR[<n>] can be used to read and write the channel-specific basic
frames of the data management. The new values are not immediately active in the channel
when writing a channel-specific basic frame. The activation in the channel only takes effect with
the programming of the appropriate command G500, G54...G599.
The channel-specific basic frames in the data management are also stored during a data
backup.
$P_CHBFRAME[<n>] (active channel-specific basic frames)

System variable $P_CHBFRAME[<n>] can be used to read and write the active channel-
specific basic frames. When writing an active channel-specific basic frame, the new values take
effect immediately through the recalculation of the active complete basic frame
$P_ACTBFRAME.
System variables for compatibility reasons
$P_UBFR (first channel-specific basic frame of the data management)

The system variable is retained for reasons of compatibility, although it is redundant for the
$P_CHBFR[0] variables.
The basic frame with array index 0 is not activated simultaneously when writing to the
predefined $P_UBFR variable, but rather activation only takes place on execution of a G500,
G54,.G599 statement. For NCU-global frames, the changed frame only becomes active in
those channels of the NCU, which execute a G500, G54..G599 command. The variable is
used primarily for storing write operations to the basic frame on HMI or PLC. The variable can
also be read and written in the program.
$P_UBFR is identical to $P_CHBFR[0]. One basic frame always exists in the channel by
default, so that the system variable is compatible with older versions. If there is no channel-
specific basic frame, an alarm: "Frame: Statement not permitted" is output on a read or write
access.
$P_BFRAME (first active channel-specific basic frame)

The system variable is retained for reasons of compatibility, although it is redundant for the
$P_CHBFRAME[0] variables.
Basic functions
3.5 Frames
The predefined frame variable $P_BFRAME can be used to read and write the current basic
frame with the array index 0, which is valid in the channel, in the part program. The written basic
frame is immediately included in the calculation. In the case of NCU-global settable frames, the
modified frame acts only in the channel in which the frame was programmed. If the frame is to
be modified for all channels of an NCU, $P_UBFR and $P_BFRAME must be written
simultaneously. The other channels must then activate the corresponding frame, e.g. with G54.
$P_BFRAME is identical to $P_CHBFRAME[0]. The system variable always has a valid default
value. If there is no channel-specific basic frame, an alarm: "Frame: Statement not permitted"
is output on a read or write access.
Writing of basic frames from HMI/PLC

Only the basic frames of the data management can be written from the HMI or the PLC user
program.
3.5.5.5 NCU-global basic frames $P_NCBFR[<n>]
Machine data
Number of NCU-global basic frames

The number of NCU-global basic frames is set with the following machine data:
MD18602 $MN_MM_NUM_GLOBAL_BASE_FRAMES = <number>
System variables
$P_NCBFR[<n>] (NCU-global basic frames of the data management)

System variable $P_NCBFR[<n>] can be used to read and write the NCU-global basic frames
of the data management. The new values are not immediately active in the channel when
writing an NCU-global basic frame. The activation in the channel only takes effect with the
programming of the appropriate command G500, G54...G599.
The NCU-global basic frames in the data management are also stored during a data backup.
$P_NCBFRAME[<n>] (current NCU-global basic frames)

System variable $P_NCBFRAME[<n>] can be used to read and write the active NCU-global
basic frames. When writing an active NCU-global basic frame, the new values take effect
immediately through the recalculation of the active complete basic frame $P_ACTBFRAME.
If the changed NCU-global basic frame is to be active in all channels of the NCU starting from
one channel, the NCU-global basic frame active in the channel and the NCU-global frame in the
data management must be written together:
Basic functions
3.5 Frames
$P_NCBFR[<n>] = $P_NCBFRAME = <new value>

● $P_NCBFR[<n>] (NCU-global basic frame of the data management)
● $P_NCBFRAME (NCU-global basic frame active in the channel)
For the changed NCU-global frame to take effect in another channel, it must be activated in this
channel with the appropriate command G500, G54..G599.
Programming
A channel-specific settable frame of the data management $P_UIFR[<n>] becomes the
settable frame $P_IFRAME active in the channel through the appropriate command
(G54 ... G57, G505 ... G599 and G500).
Command Activation of the NCU-global and channel-specific

basic frames of the data management
G500 $P_CHBFR[ 0 ] : $P_NCBFR[0]
... ...
G599 $P_CHBFR[ 99 ] : $P_NCBFR[99]
3.5.5.6 Active complete basic frame $P_ACTBFRAME
Function
All active NCU-global and channel-specific basic frames are combined into the complete basic
frame $P_ACTBFRAME:
$P_ACTBFRAME = $P_NCBFRAME[0] : ... : $P_NCBFRAME[<n>] :
$P_CHBFRAME[0] : ... : $P_CHBFRAME[<n>]
%16
(
3B&+%)5$0(>Q!@
$0
)5
7%
3B&+%)5$0(>@
&
B$
3
3B1&%)5$0(>Q!@
3B1&%)5$0(>@
%.6
Basic functions
3.5 Frames
Figure 3-24 Complete basic frame
Machine data
Reset response
Which basic frames are active after a reset (channel reset, end of program reset or Power On)
is set via the machine data:
MD20110 $MC_RESET_MODE_MASK, bit0 = 1 and bit14 = 1
● Bit 1 = 0: Default value ⇒ reset behavior corresponding to the setting of the further bits
● Bit14 = 0: The basic frames are completely deselected with reset.
● Bit14 = 1: With reset, the machine data settings are taken over in the system variables and
the basic frames selected therein become active:
– $P_NCBFRMASK = MD10613 $MN_NCBFRAME_RESET_MASK
– $P_CHBFRMASK = MD24002 $MC_CHBFRAME_RESET_MASK
Example
Machine data setting Active basic frames

$P_NCBFRMASK = MD10613 $MN_NCBFRAME_RE‐ $P_NCBFRAME[0] :
SET_MASK = 'H81' $P_NCBFRAME[7]
Programming
Basic frame masks

The basic frames that are linked to form the complete basic frame are selected via the basic
frame masks $P_NCBFRMASK and $P_CHBFRMASK.
The appropriate basic frame is selected by setting a bit in the basic frame mask:
● $P_NCBFRMASK, bit 0, 1, 2, ... n ⇒ $P_NCBFRAME[0, 1, 2, ... n]
● $P_CHBFRMASK, bit 0, 1, 2, ... n ⇒ $P_NCHFRAME[0, 1, 2, ... n]
The basic frame masks $P_NCBFRMASK and $P_CHBFRMASK can only be read/written in the
NC program. The basic frame masks can be read via the OPI.
After writing a basic frame mask, the active complete basic frame $P_ACTBFRAME and
complete frame $P_ACTFRAME are recalculated.
Example

$P_NCBFRMASK = 'H81' ; Active NCU-global basic frames: $P_NCBFRAME[0] :
$P_NCBFRAME[7]
3.5.5.7 Programmable frame $P_PFRAME

Programmable frames are available only as active frames.
This frame is reserved for the programmer.
Basic functions
3.5 Frames
The programmable frame remains at RESET, if:

MD24010 $MC_PFRAME_RESET_MODE (reset mode for programmable frame) = 1
This functionality is especially important after a RESET if one still wants to retract out of an
oblique hole.
MIRROR
Mirrorings of a geometry axis were previously (up to SW-P4) related to a defined reference axis
only using the machine data:
MD10610 $MN_MIRROR_REF_AX
(reference axis for the mirroring).
From the user's point of view, this definition is difficult to understand. When mirroring the z axis,
the display showed that the x axis was mirrored and the y axis had been rotated through 180
degrees. When mirroring two axes this became even more complex and it was no longer easy
to understand, which axes had been mirrored and, which had not.
As of SW P5, there is the option to clearly display the mirroring of an axis. Mirroring is then not
mapped to mirroring of a reference axis and rotations of other axes.
This setting can be configured using:
MD10610 $MN_MIRROR_REF_AX = 0
MIRROR and AMIRROR are used to expand the programming of the programmable frame.
Previously, the specified value of the coordinate axis, e.g. the value 0 for MIRROR X0 was not
evaluated, but rather the AMIRROR had a toggle function, i.e. MIRROR X0 activates mirroring
and an additional AMIRROR X0 deactivates it. MIRROR always has an absolute effect and
AMIRROR an additive effect.
The
MD10612 $MN_MIRROR_TOGGLE = 0 ("Mirror Toggle")
machine data setting can be used to define that the programmed values are evaluated.
A value of 0, as inAMIRROR X0, deactivates the mirroring of the axis, and values not equal to
0 cause the axis to be mirrored if it is not already mirrored.
Reading or writing mirroring component-by-component is independent of the machine data:
MD10612 $MN_MIRROR_TOGGLE
A value = 0 means that the axis is not mirrored and a value = 1 means that the axis will always
be mirrored, irrespective of whether it has already been mirrored or not.
$P_NCBFR[0,x,mi]=1 ; x axis is always mirrored.

$P_NCBFR[0,x,mi]=0 ; x axis mirroring is OFF.
Axis-specific replacement G58, G59

The translation component of the programmable frame is split into an absolute component and
a component for the total of all additively programmed translations. The absolute component
can be changed using TRANS, CTRANS or by writing the translation components, in which the
additive component is set to zero. G58 changes only the absolute translation component for the
specified axis; the total of additively programmed translations is retained.
G58 X... Y... Z... A... ...
Basic functions
3.5 Frames
G59 is used for axis-specific overwriting of the additively programmed translations for the
specified axes which were programmed with ATRANS.
G59 X... Y... Z... A... ...
Example
TRANS X10 Y10 Z10

ATRANS X5 Y5 ; Total translations X15 Y15 Z10
G58 X20 ; Total translations X25 Y15 Z10
G59 X10 Y10 ; Total translations X30 Y20 Z10
G58 and G59 can only be used if:

MD24000 $MC_FRAME_ADD_COMPONENTS (frame components for G58 / G59) == TRUE
The table below shows the effect of various program commands on the absolute and additive
translation.
Coarse or absolute offset Fine or additive offset

TRANS X10 10 0
ATRANS X10 Unchanged alt_fine + 10
CTRANS(X,10) 10 0
CTRANS() 0 0
CFINE(X,10) 0 10
$P_PFRAME[X,TR] = 10 10 Unchanged
$P_PFRAME[X,FI] = 10 Unchanged 10
G58 X10 10 Unchanged
G59 X10 Unchanged 10
3.5.5.8 Channelspecific system frames

Channel-specific system frames are only written by system functions, such as actual value
setting, scratching, external work offset and inclined machining.
Machine data
Parameterization of the channel-specific system frames

Only channel-specific system frames whose system functions are actually used should be
configured for memory space reasons.
Per channel, each system frame occupies approx. 1 KB static and approx. 6 KB dynamic
memory.
The channel-specific system frames are parameterized in the following machine data:
MD28082 $MC_MM_SYSTEM_FRAME_MASK, bit<n>
Bit Value System frame available:

0 1 $P_SETFR: Actual value setting and scratching
1 1 $P_EXTFR: External work offset via system frames
Basic functions
3.5 Frames
Bit Value System frame available:

2 1 $P_PARTFR: TCARR and PAROT with an orientable toolholder
3 1 $P_TOOLFR: TOROT and TOFRAME
4 1 $P_WPFR: Frame for workpiece reference points
5 1 $P_CYCFR: Frame for cycles
6 1 $P_TRAFR: Frame for selection and deselection of transformations
7 1 $P_ISO1FRAME : Frame for G51.1 mirroring (ISO)
8 1 $P_ISO2FRAME : Frame for G68 2DROT (ISO)
9 1 $P_ISO3FRAME : Frame for G68 3DROT (ISO)
10 1 $P_ISO4FRAME: Frame for G51 scale (ISO)
11 1 $P_RELFR: Frame for relative coordinate systems
Parameterization of the SZS (ACS) coordinate system

The following machine data is used to specify which system frames form the SZS (ACS)
coordinate system
MD24030 $MC_FRAME_ACS_SET = <value>
<value> Meaning: The SZS (ACS) coordinate system comprises

0 $P_PARTFRAME : $P_SETFRAME : $P_EXTFRAME :$P_ISO1FRAME : $P_ISO2FRAME :
$P_ISO3FRAME :$P_ACTBFRAME : $P_IFRAME : $P_GFRAME : $P_TOOLFRAME :
$P_WPFRAME
1 $P_PARTFRAME : $P_SETFRAME : $P_EXTFRAME :$P_ISO1FRAME : $P_ISO2FRAME :
$P_ISO3FRAME :$P_ACTBFRAME : $P_IFRAME : $P_GFRAME : $P_TOOLFRAME :
$P_WPFRAME : $P_TRAFRAME :$P_PFRAME : $P_ISO4FRAME
System variables
Channel-specific system frames of the data management

The channel-specific system frames of the data management can be read and written via the
following frame variables:
System variable Meaning: System frame of the data management for

$P_SETFR Actual value setting and scratching (Set Frame)
$P_EXTFR External work offset (Ext Frame)
$P_PARTFR TCARR and PAROT for orientable toolholder (Part Frame)
$P_TOOLFR TOROT and TOFRAME (Tool Frame)
$P_WPFR Workpiece reference points (WorkPiece Frame)
$P_CYCFR Cycles (Cycle Frame)
$P_TRAFRAME Transformations (Transformation Frame)
$P_ISO1FR G51.1 mirroring (ISO)
$P_ISO2FR G68 2DROT (ISO)
$P_ISO3FR G68 3DROT (ISO)
$P_ISO4FR G51 scale (ISO)
$P_RELFR Relative coordinate systems
Basic functions
3.5 Frames
Note
Cycle programming
The frame variables of the system frames are only for the cycle programming. Therefore, in NC
programs the system frames should not be written directly by the user, but rather only via
system functions such as TOROT, PAROT, etc.
Channelspecific active system frames

System variables of the active channel-specific system frames:
System variable Meaning: Active system frame for

$P_SETFRAME Actual value setting and scratching (Set Frame)
$P_EXTFRAME External work offset (Ext Frame)
$P_PARTFRAME TCARR and PAROT for orientable toolholder (Part Frame)
$P_TOOLFRAME TOROT and TOFRAME (Tool Frame)
$P_WPFRAME Workpiece reference points (WorkPiece Frame)
$P_CYCFRAME Cycles (Cycle Frame)
$P_TRAFRAME Transformations (Transformation Frame)
$P_ISO1FRAME G51.1 mirroring (ISO)
$P_ISO2FRAME G68 2DROT (ISO)
$P_ISO3FRAME G68 3DROT (ISO)
$P_ISO4FRAME G51 scale (ISO)
$P_RELFRAME Relative coordinate systems
If a channel-specific system frame of the data management is not parameterized, the following
applies for the corresponding active system frame: $P_<system frame> == null frame.
Channel-specific active SZS (ACS) complete frame

The system variable $P_ACSFRAME is used to read which system frames form the SZS (ACS)
coordinate system. The specification is made via the MD24030 $MC_FRAME_ACS_SET
machine data described above. See Subsection "Machine data" > "Parameterization of the
SZS (ACS) coordinate system"
System variable Meaning: Active system frame for

$P_ACSFRAME System frames that form the SZS (ACS) coordinate system in accordance with
the parameterization in MD24030 $MC_FRAME_ACS_SET
3.5.6 Implicit frame changes
3.5.6.1 Switching geometry axes

Which channel axes are the geometry axis of the channel can change by activating/
deactivating a transformation and with the GEOAX() command.
Basic functions
3.5 Frames
Four different settings for handling the current $P_ACTFRAME complete frame can be made
with the following machine data:
MD10602 $MN_FRAME_GEOAX_CHANGE_MODE = <value>
<value> Meaning
0 Delete
The current complete frame is deleted when geometry axes are switched over, when trans‐
formations are selected and deselected, and on GEOAX().
The modified geometry axis configuration is not used until a new frame is activated.
1 New calculation on receipt of the rotations
The current complete frame is calculated again when the geometry axes are switched over,
whereby the frame components of the new geometry axes are effective. The rotations of the
geometry axes which were programmed before the switchover remain effective for the new
geometry axes.
For TRANSMIT, TRACYL and TRAANG, see Section "Selecting and deselecting transforma‐
tions: General (Page 347)".
2 New calculation only when no rotations were active
The current complete frame is calculated again when the geometry axes are switched over,
whereby the frame components of the new geometry axes are effective. If rotations are active
in the current basic frames, the current settable frame or the programmable frame before the
switchover, it is aborted with the alarm "Frame: Geometry axis switchover not allowed".
For TRANSMIT, TRACYL and TRAANG, see Section "Selecting and deselecting transforma‐
tions: General (Page 347)".
3 Transformation: Reset / GEOAX(): New calculation on receipt of the rotations
● Transformation: The current frame is deleted when selecting and deselecting transfor‐
mations.
● GEOAX(): With GEOAX(), the current complete frame is calculated again and the trans‐
lations, scalings and mirrorings of the new geometry axes come into effect. The rotations
of the geometry axes which were programmed before the switchover remain effective for
the new geometry axes.
The workpiece geometry is described by a coordinate system that is formed by the geometry
axes. A channel axis is assigned to each geometry axis and a machine axis is assigned to each
channel axis. An axis-specific frame exists for each machine axis (system frame, basic frame,
settable frame, programmable frame). If a different machine axis is assigned to a geometry
axis, the machine axis provides its own axis-specific frame components. The new geometry in
the channel is then generated by the new contour frames resulting from the new geometry axes
(up to three).
The current valid frames are calculated again on the geometry axis switchover and a resulting
complete frame is generated. The data management frames are not included unless they are
activated.
Example:
The channel axis A is to become a geometry axis X through geo axis substitution. The
substitution is to give the programmable frame a translation component of 10 in the X axis. The
current settable frame is to be retained.
MD10602 $MN_FRAME_GEOAX_CHANGE_MODE = 1

$P_UIFR[1] = CROT(X,10,Y,20,Z,30) ; Frame is retained after geo axis substitution.
Basic functions
3.5 Frames

G54 ; Settable frame becomes active.
TRANS A10 ; Axial offset of A is also substituted.
GEOAX(1, A) ; A becomes the X axis
; $P_ACTFRAME = CROT(X,10,Y,20,Z,30) :
CTRANS(X10)
Several channel axes can become geometry axes on a transformation change.
Example:
Channel axes 4, 5 and 6 become the geometry axes of a 5axis transformation. The geometry
axes are thus all substituted before the transformation. The current frames are changed when
the transformation is activated. The axial frame components of the channel axes which become
geometry axes are taken into account when calculating the new WCS. Rotations programmed
before the transformation are retained. The old WCS is restored when the transformation is
deactivated. The most common application is probably that the geometry axes do not change
before and after the transformation and that the frames are to stay as they were before the
transformation.
Machine data
Program code
$MC_AXCONF_CHANAX_NAME_TAB[0] = "CAX"
$MC_AXCONF_CHANAX_NAME_TAB[1] = "CAY"
$MC_AXCONF_CHANAX_NAME_TAB[2] = "CAZ"
$MC_AXCONF_CHANAX_NAME_TAB[3] = "A"
$MC_AXCONF_CHANAX_NAME_TAB[4] = "B"
$MC_AXCONF_CHANAX_NAME_TAB[5] = "C"
$MC_AXCONF_GEOAX_ASSIGN_TAB[0] = 1
$MC_AXCONF_GEOAX_NAME_TAB[0] = "X"
$MC_AXCONF_GEOAX_NAME_TAB[1]="Y"
$MC_AXCONF_GEOAX_NAME_TAB[2] = "Z"
$MC_TRAFO_GEOAX_ASSIGN_TAB_1[0]=4
$MC_TRAFO_AXES_IN_1[0] = 4
Basic functions
3.5 Frames
Program:
Program code
$P_NCBFRAME[0] = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6)
$P_CHBFRAME[0] = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6)
$P_IFRAME = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6):CROT(Z,45)
$P_PFRAME = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6):CROT(X,10,Y,20,Z,30)

TRAORI ; Transformation sets GEOAX(4,5,6)
; $P_NCBFRAME[0] = CTRANS(X,4,Y,5,Z,6,CAX,1,CAY,2,CAZ,3)
; $P_ACTBFRAME =CTRANS(X,8,Y,10,Z,12,CAX,2,CAY,4,CAZ,6)
; $P_PFRAME =
CTRANS(X,4,Y,5,Z,6,CAX,1,CAY,2,CAZ,3):CROT(X,10,Y,20,Z,30)
; $P_IFRAME = CTRANS(X,4,Y,5,Z,6,CAX,1,CAY,2,CAZ,3):CROT(Z,45)
TRAFOOF ; Deactivation of the transformation sets GEOAX(1,2,3)
; $P_NCBFRAME[0] = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6)
; $P_CHBFRAME[0] = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6)
; $P_IFRAME = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6):CROT(Z,45)
; $P_PFRAME =
CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6):CROT(X,10,Y,20,Z,30)
3.5.6.2 Selecting and deselecting transformations: General

As a rule, the assignment of geometry axes to the channel axes changes when selecting and
deselecting transformations. It is not possible to uniquely assign axis-specific frame
components to geometric contour frame components when carrying out transformations, in
which rotary axes become linear axes and vice versa. The contour frame must be conditioned
using special treatment for such non-linear transformations.
The mode, set with MD10602 $MN_FRAME_GEOAX_CHANGE_MODE = 1 and 2, is
expanded in such a way as to take the above transformations into account.
When selecting transformations, the contour frame is connected to the axis-specific frames.
The virtual geometry axis of the TRANSMIT, TRACYL and TRAANG transformations is subject
to special treatment.
Note
Transformations with virtual axes
When selecting TRANSMIT or TRACYL, offsets, scaling and mirroring of the real Y axis are not
accepted in the virtual Y axis. Offsets, scaling and mirroring of the virtual Y axis are deleted for
TRAFOOF.
Basic functions
3.5 Frames
3.5.6.3 Selecting and deselecting transformations: TRANSMIT
Transmit expansions
The machine data below can be used to take the axis-specific complete frame of the
TRANSMIT rotary axis, i.e. translation, mirroring and scaling, into account in the transformation:
● MD24905 $MC_TRANSMIT_ROT_AX_FRAME_1 = 1
A rotary axis offset can, for example, be entered by compensating the oblique position of a
workpiece in a frame within a frame chain. As a rule, this offset can also be included in the
transformation as an offset in the rotary axis. A C axis offset, as in the figure above, then leads
to corresponding X and Y values.
With this setting, the axis-specific offset of the rotary axis is taken account of in the
transformation up to the SZS. The axis-specific offsets of the rotary axis included in the SZS
frames are entered into the transformation frame as rotation. This setting is only effective if the
transformation frame has been configured.
Frame expansions:
The expansions described below are only valid for the following machine data settings:
● MD10602 $MN_FRAME_GEOAX_CHANGE_MODE = 1
Basic functions
3.5 Frames
The selection of transformation TRANSMIT produces a virtual geometry axis, coupled by way
of the rotary axis, which is merely included in the contour frame but does not have a reference
to an axis-specific frame. The geometric value results from the rotation of a rotary axis. All other
geometry axes accept their axis-specific components when the transformation is selected.
Components:
● Translations
When selecting TRANSMIT, translations of the virtual axis are deleted. Translations of the
rotary axis can be taken into account in the transformation.
● Rotations
Rotations before the transformation are accepted.
● Mirrorings
Mirroring of the virtual axis is deleted. Mirroring of the rotary axis can be taken into account
in the transformation.
● Scalings
Scaling of the virtual axis is deleted. Scaling of the rotary axis can be taken into account in
the transformation.
Example: Machine data
; FRAME configurations
$MC_MM_SYSTEM_FRAME_MASK='H41' ; TRAFRAME, SETFRAME

$MC_CHSFRAME_RESET_MASK='H41' ; Frames are active after Reset.
$MC_CHSFRAME_POWERON_MASK='H41' ; Frames are deleted for Power On.
$MN_FRAME_GEOAX_CHANGE_MODE=1 ; Frames are calculated after switchover

of the geo axis.
$MC_RESET_MODE_MASK='H4041' ; Basic frame is not deselected after Re-
set.
;$MC_RESET_MODE_MASK='H41' ; Basic frame is deselected after Reset.
;$MC_GCODE_RESET_VALUES[7]=2 ; G54 is the default setting.

$MC_GCODE_RESET_VALUES[7]=1 ; G500 is the default setting.
$MN_MM_NUM_GLOBAL_USER_FRAMES=0
$MN_MM_NUM_GLOBAL_BASE_FRAMES=3
$MC_MM_NUM_USER_FRAMES=10 ; From 5 to 100

$MC_MM_NUM_BASE_FRAMES=3 ; From 0 to 8
$MN_NCBFRAME_RESET_MASK='HFF'
$MC_CHBFRAME_RESET_MASK='HFF'
$MN_MIRROR_REF_AX=0 ; No scaling when mirroring.

$MN_MIRROR_TOGGLE=0
$MN_MM_FRAME_FINE_TRANS=1 ; Fine offset
Basic functions
3.5 Frames
$MC_FRAME_ADD_COMPONENTS=TRUE ; G58, G59 is possible.
; TRANSMIT is the 1st transformation

$MC_TRAFO_TYPE_1=256
$MC_TRAFO_AXES_IN_1[0]=1
$MA_ROT_IS_MODULO[AX6]=TRUE;
$MC_TRANSMIT_BASE_TOOL_1[0]=0.0
$MC_TRANSMIT_ROT_AX_OFFSET_1=0.0
$MC_TRANSMIT_ROT_SIGN_IS_PLUS_1=TRUE
$MC_TRANSMIT_ROT_AX_FRAME_1=1
; TRANSMIT is the 2nd transformation

$MC_TRAFO_TYPE_2=256
$MC_TRANSMIT_ROT_AX_OFFSET_2=19.0
Basic functions
3.5 Frames
$MC_TRANSMIT_ROT_SIGN_IS_PLUS_2=TRUE
$MC_TRANSMIT_ROT_AX_FRAME_2=1
Example: Part program
; Frame settings
N820 $P_UIFR[1] = ctrans(x,1,y,2,z,3,c,4)
N830 $P_UIFR[1] = $P_UIFR[1] : crot(x,10,y,20,z,30)
N840 $P_UIFR[1] = $P_UIFR[1] : cmirror(x,c)
N850
N860 $P_CHBFR[0] = ctrans(x,10,y,20,z,30,c,15)
N870
; Tool selection, clamping compensation, plane selection

N890 T2 D1 G54 G17 G90 F5000 G64 SOFT
N900
; Approach start position

N920 G0 X20 Z10
N930
N940 if $P_BFRAME <> CTRANS(X,10,Y,20,Z,30,C,15)
N950 setal(61000)
N960 endif
N970 if $P_BFRAME <> $P_CHBFR[0]
N980 setal(61000)
N990 endif
N1000 if $P_IFRAME <>
CTRANS(X,1,Y,2,Z,3,C,4):CROT(X,10,Y,20,Z,30):CMIRROR(X,C)
N1010 setal(61000)
N1020 endif
N1030 if $P_IFRAME <> $P_UIFR[1]
N1040 setal(61000)
N1050 endif
N1060 if $P_ACTFRAME <>
CTRANS(X,11,Y,22,Z,33,C,19):CROT(X,10,Y,20,Z,30):CMIRROR(X,C)
N1070 setal(61000)
N1080 endif
N1090
N1100 TRANSMIT(2)
N1110
N1120 if $P_BFRAME <> CTRANS(X,10,Y,0,Z,20,CAZ,30,C,15)
N1130 setal(61000)
N1140 endif
Basic functions
3.5 Frames
CTRANS(X,1,Y,0,Z,2,CAZ,3,C,4):CROT(X,10,Y,20,Z,30):CMIRROR(X,C)
N1190 setal(61000)
N1200 endif
CTRANS(X,11,Y,0,Z,22,CAZ,33,C,19):CROT(X,10,Y,20,Z,30):CMIRROR(X,C)
N1250 setal(61001)
N1260 endif
N1270
N1280
N1290 $P_UIFR[1,x,tr] = 11
N1300 $P_UIFR[1,y,tr] = 14
N1310
N1320 g54
N1330
; Set frame
N1350 ROT RPL=-45
N1360 ATRANS X-2 Y10
N1370
; Four-edge roughing
N1390 G1 X10 Y-10 G41 OFFN=1; allowance 1 mm
N1400 X-10
N1410 Y10
N1420 X10
N1430 Y-10
N1440
; Tool change
N1460 G0 Z20 G40 OFFN=0
N1470 T3 D1 X15 Y-15
N1480 Z10 G41
N1490
; Four-edge finishing
N1510 G1 X10 Y-10
N1520 X-10
N1530 Y10
N1540 X10
N1550 Y-10
N1560
Basic functions
3.5 Frames
; Deselect frame
N2950 m30 N1580 Z20 G40
N1590 TRANS
N1600
N1610 if $P_BFRAME <> CTRANS(X,10,Y,0,Z,20,CAZ,30,C,15)
N1620 setal(61000)
N1630 endif
N1650 setal(61000)
N1660 endif
TRANS(X,11,Y,0,Z,2,CAZ,3,C,4):CROT(X,10,Y,20,Z,30):CMIRROR(X,C)
N1680 setal(61000)
N1690 endif
TRANS(X,21,Y,0,Z,22,CAZ,33,C,19):CROT(X,10,Y,20,Z,30):CMIRROR(X,C)
N1740 setal(61001)
N1750 endif
N1760
N1770 TRAFOOF
N1780
N1790 if $P_BFRAME <> CTRANS(X,10,Y,20,Z,30,C,15)
N1800 setal(61000)
N1810 endif
N1830 setal(61000)
N1840 endif
TRANS(X,11,Y,2,Z,3,C,4):CROT(X,10,Y,20,Z,30):CMIRROR(X,C)
N1860 setal(61000)
N1870 endif
N1890 setal(61000)
N1900 endif
TRANS(X,21,Y,22,Z,33,C,19):CROT(X,10,Y,20,Z,30):CMIRROR(X,C)
N1920 setal(61002)
N1930 endif
N1940
N2010 $P_UIFR[1] = ctrans()
N2011 $P_CHBFR[0] = ctrans()
N2020 $P_UIFR[1] = ctrans(x,1,y,2,z,3,c,0)
N2021 G54
N2021 G0 X20 Y0 Z10 C0
Basic functions
3.5 Frames
N2030 TRANSMIT(1)
N2040 TRANS x10 y20 z30
N2041 ATRANS y200
N2050 G0 X20 Y0 Z10
N2051 if $P_IFRAME <> CTRANS(X,1,Y,0,Z,3,CAY,2)
N2052 setal(61000)
N2053 endif
N2054 if $P_ACTFRAME <> CTRANS(X,11,Y,20,Z,33,CAY,2):CFINE(Y,200)
N2055 setal(61002)
N2056 endif
N2060 TRAFOOF
N2062 setal(61000)
N2063 endif
N2064 if $P_ACTFRAME <> CTRANS(X,11,Y,2,Z,33):CFINE(Y,0)
N2065 setal(61002)
N2066 endif
3.5.6.4 Selecting and deselecting transformations: TRACYL
[
'LDPHWHUG
TRACYL expansions:
The machine data below can be used to take the axis-specific complete frame of the TRACYL
rotary axis, i.e. the translation, fine offset, mirroring and scaling, into account in the
transformation:
● MD24805 $MC_TRACYL_ROT_AX_FRAME_1 = 1
Basic functions
3.5 Frames
A rotary axis offset can, for example, be entered by compensating the oblique position of a
workpiece in a frame within a frame chain. As a rule, this offset can also be included in the
transformation as an offset in the rotary axis or as a y offset. A C axis offset, as in the figure
above, then leads to corresponding X and Y values.
With this setting, the axis-specific offset of the rotary axis is taken account of in the
transformation up to the SZS. The axial offsets of the rotary axis included in the SZS frames are
entered into the transformation frame as offsets on the peripheral surface. This setting is only
effective if the transformation frame has been configured.
Frame expansions:
The selection of transformation TRACYL produces a virtual geometry axis on the peripheral
surface, coupled via the rotary axis, which is only taken into account in the contour frame but
does not have a reference to an axis-specific frame. All components of the virtual geometry axis
are deleted. All other geometry axes accept their axis-specific components when the
transformation is selected.
Components:
● Translations
When selecting TRACYL, translations of the virtual axis are deleted. Translations of the
rotary axis can be taken into account in the transformation.
● Rotations
● Mirrorings
Mirroring of the virtual axis is deleted. Mirroring of the rotary axis can be taken into account
in the transformation.
● Scalings
Scaling of the virtual axis is deleted. Scaling of the rotary axis can be taken into account in
the transformation.
$MC_MM_SYSTEM_FRAME_MASK = 'H41' ; TRAFRAME, SETFRAME

$MC_CHSFRAME_RESET_MASK = 'H41' ; Frames are active after Reset.
$MC_CHSFRAME_POWERON_MASK = 'H41' ; Frames are deleted for Power On.
$MN_FRAME_GEOAX_CHANGE_MODE = 1 ; Frames are calculated after switchover

of the geo axis.
Basic functions
3.5 Frames
$MC_RESET_MODE_MASK = 'H4041' ; Basic frame is not deselected after Re-

set.
;$MC_RESET_MODE_MASK = 'H41' ; Basic frame is deselected after Reset.
;$MC_GCODE_RESET_VALUES[7] = 2 ; G54 is the default setting.

$MC_GCODE_RESET_VALUES[7] = 1 ; G500 is the default setting.
$MN_MM_NUM_GLOBAL_USER_FRAMES = 0
$MN_MM_NUM_GLOBAL_BASE_FRAMES = 3
$MC_MM_NUM_USER_FRAMES = 10 ; from 5 to 100

$MC_MM_NUM_BASE_FRAMES = 3 ; from 0 to 8
$MN_NCBFRAME_RESET_MASK = 'HFF'
$MC_CHBFRAME_RESET_MASK = 'HFF'
$MN_MIRROR_REF_AX = 0 ; No scaling when mirroring.

$MN_MIRROR_TOGGLE = 0
$MN_MM_FRAME_FINE_TRANS = 1 ; Fine offset
$MC_FRAME_ADD_COMPONENTS = TRUE ; G58, G59 is possible
; TRACYL with groove wall offset is the 3rd transformation
$MC_TRAFO_TYPE_3 = 513; TRACYL
$MC_TRAFO_GEOAX_ASSIGN_TAB_3[0] = 1
$MC_TRACYL_BASE_TOOL_1[0] = 0.0
$MC_TRACYL_ROT_AX_OFFSET_1 = 0.0
$MC_TRACYL_ROT_SIGN_IS_PLUS_1 = TRUE
$MC_TRACYL_ROT_AX_FRAME_1 = 1
Basic functions
3.5 Frames
;Simple traversing test with groove side offset

N450 G603
N460
; Frame settings
N500 $P_UIFR[1] = CTRANS(x,1,y,2,z,3,b,4)
N510 $P_UIFR[1] = $P_UIFR[1] : CROT(x,10,y,20,z,30)
N520 $P_UIFR[1] = $P_UIFR[1] : CMIRROR(x,b)
N530
N540 $P_CHBFR[0] = CTRANS(x,10,y,20,z,30,b,15)
N550
N560 G54
N570
; Continuous-path mode with selected smoothing

N590 G0 x0 y0 z-10 b0 G90 F50000 T1 D1 G19 G641 ADIS=1 ADISPOS=5
N600
N610 if $P_BFRAME <> CTRANS(X,10,Y,20,Z,30,B,15)
N620 setal(61000)
N630 endif
N650 setal(61000)
N660 endif
TRANS(X,1,Y,2,Z,3,B,4):CROT(X,10,Y,20,Z,30):CMIRROR(X,B)
N680 setal(61000)
N690 endif
N710 setal(61000)
N720 endif
N740 setal(61000)
N750 endif
N760
; Transformation ON
N780 TRACYL(40.)
N790
N800 if $P_BFRAME <> CTRANS(X,10,Y,0,Z,30,CAY,20,B,15)
N810 setal(61000)
N820 endif
Basic functions
3.5 Frames
N830 if $P_CHBFR[0] <> CTRANS(X,10,Y,0,Z,30,CAY,20,B,15)

N840 setal(61000)
N850 endif
TRANS(X,1,Y,0,Z,3,CAY,2,B,4):CROT(X,10,Y,20,Z,30):CMIRROR(X,B)
N870 setal(61000)
N880 endif
N890 if $P_UIFR[1] <>
N900 setal(61000)
N910 endif
N930 setal(61001)
N940 endif
N950
N960 $P_UIFR[1,x,tr] = 11
N970 $P_UIFR[1,y,tr] = 14
N980
N990 g54
N1000
N1010 if $P_BFRAME <> CTRANS(X,10,Y,0,Z,30,CAY,20,B,15)
N1020 setal(61000)
N1030 endif
N1050 setal(61000)
N1060 endif
N1080 setal(61000)
N1090 endif
N1110 setal(61000)
N1120 endif
N1140 setal(61001)
N1150 endif
N1160
; Transformation off
N1180 TRAFOOF
N1190
N1200 if $P_BFRAME <> CTRANS(X,10,Y,20,Z,30,B,15)
N1210 setal(61000)
Basic functions
3.5 Frames
N1220 endif
N1240 setal(61000)
N1250 endif
N1270 setal(61000)
N1280 endif
N1300 setal(61000)
N1310 endif
N1330 setal(61002)
N1340 endif
N1350
N1360 G00 x0 y0 z0 G90
N1370
N1380 m30
3.5.6.5 Selecting and deselecting transformations: TRAANG
=
0 :
Frame expansions:
Basic functions
3.5 Frames
Components:
● Translations
When selecting TRAANG, translations of the virtual axis are deleted.
● Rotations
● Mirrorings
Mirrorings of the virtual axis are taken over.
● Scalings
Scalings of the virtual axis are taken over.
$MC_MM_SYSTEM_FRAME_MASK = 'H1' ; SETFRAME

$MC_CHSFRAME_RESET_MASK = 'H41' ; Frames are active after RESET.
$MC_CHSFRAME_POWERON_MASK = 'H41' ; Frames are deleted for "Power On".
$MN_FRAME_GEOAX_CHANGE_MODE = 1 ; Frames are calculated after switchover

of the geo axis.
$MC_RESET_MODE_MASK = 'H4041' ; Basic frame is not deselected after RE-

SET.
;$MC_RESET_MODE_MASK = 'H41' ; Basic frame is deselected after RESET.
;$MC_GCODE_RESET_VALUES[7] = 2 ; G54 is the default setting.

$MC_GCODE_RESET_VALUES[7] = 1 ; G500 is the default setting.
$MN_MM_NUM_GLOBAL_USER_FRAMES = 0
$MN_MM_NUM_GLOBAL_BASE_FRAMES = 3
$MC_MM_NUM_USER_FRAMES = 10 ; from 5 to 100

$MC_MM_NUM_BASE_FRAMES = 3 ; from 0 to 8
$MN_NCBFRAME_RESET_MASK = 'HFF'
$MC_CHBFRAME_RESET_MASK = 'HFF'
$MN_MIRROR_REF_AX = 0 ; No scaling when mirroring.

$MN_MIRROR_TOGGLE = 0
$MN_MM_FRAME_FINE_TRANS = 1 ; Fine offset
$MC_FRAME_ADD_COMPONENTS = TRUE ; G58, G59 is possible.
; TRAANG is the 1st transformation
$MC_TRAFO_TYPE_1 = 1024
Basic functions
3.5 Frames
$MC_TRAFO_AXES_IN_1[0] = 4 ; Inclined axis

$MC_TRAFO_AXES_IN_1[1] = 3 ; Axis is parallel to z
$MC_TRAANG_ANGLE_1 = 85.
$MC_TRAANG_PARALLEL_VELO_RES_1 = 0.
$MC_TRAANG_PARALLEL_ACCEL_RES_1 = 0.
$MC_TRAANG_BASE_TOOL_1[0] = 0.0
; TRAANG is the 2nd transformation
$MC_TRAFO_TYPE_2 = 1024
$MC_TRAANG_ANGLE_2 = -85.
$MC_TRAANG_PARALLEL_VELO_RES_2 = 0.2
$MC_TRAANG_PARALLEL_ACCEL_RES_2 = 0.2
; Frame settings
N820 $P_UIFR[1] = ctrans(x,1,y,2,z,3,b,4,c,5)
Basic functions
3.5 Frames
N830 $P_UIFR[1] = $P_UIFR[1] : crot(x,10,y,20,z,30)

N840 $P_UIFR[1] = $P_UIFR[1] : cmirror(x,c)
N850
N860 $P_CHBFR[0] = ctrans(x,10,y,20,z,30,b,40,c,15)
N870
; Tool selection, clamping compensation, plane selection

N890 T2 D1 G54 G17 G90 F5000 G64 SOFT
N900
; Approach start position

N920 G0 X20 Z10
N930
N940 if $P_BFRAME <> CTRANS(X,10,Y,20,Z,30,B,40,C,15)
N950 setal(61000)
N960 endif
N980 setal(61000)
N990 endif
TRANS(X,1,Y,2,Z,3,B,4,C,5):CROT(X,10,Y,20,Z,30):CMIRROR(X,C)
N1010 setal(61000)
N1020 endif
N1040 setal(61000)
N1050 endif
N1070 setal(61000)
N1080 endif
N1090
N1100 TRAANG(,1)
N1110
N1120 if $P_BFRAME <> CTRANS(X,10,Y,20,Z,30,CAX,10,B,40,C,15)
N1130 setal(61000)
N1140 endif
N1160 setal(61000)
N1170 endif
CTRANS(X,1,Y,2,Z,3,CAX,1,B,4,C,5):CROT(X,10,Y,20,Z,30):CMIRROR(X,CAX,C)
N1190 setal(61000)
N1200 endif
Basic functions
3.5 Frames
N1220 setal(61000)
N1230 endif
TRANS(X,11,Y,22,Z,33,CAX,11,B,44,C,20):CROT(X,10,Y,20,Z,30):CMIRROR(X,CAX,
C)
N1250 setal(61001)
N1260 endif
N1270
N1280
N1290 $P_UIFR[1,x,tr] = 11
N1300 $P_UIFR[1,y,tr] = 14
N1310
N1320 g54
N1330
; Set frame
N1350 ROT RPL=-45
N1360 ATRANS X-2 Y10
N1370
; Four-edge roughing
N1390 G1 X10 Y-10 G41 OFFN=1; allowance 1 mm
N1400 X-10
N1410 Y10
N1420 X10
N1430 Y-10
N1440
; Tool change
N1460 G0 Z20 G40 OFFN=0
N1470 T3 D1 X15 Y-15
N1480 Z10 G41
N1490
; Four-edge finishing
N1510 G1 X10 Y-10
N1520 X-10
N1530 Y10
N1540 X10
N1550 Y-10
N1560
Basic functions
3.5 Frames
; Deselect frame
N1580 Z20 G40
N1590 TRANS
N1600
N1610 if $P_BFRAME <> CTRANS(X,10,Y,20,Z,30,CAX,10,B,40,C,15)
N1620 setal(61000)
N1630 endif
N1650 setal(61000)
N1660 endif
TRANS(X,11,Y,14,Z,3,CAX,1,B,4,C,5):CROT(X,10,Y,20,Z,30):CMIRROR(X,CAX,C)
N1680 setal(61000)
N1690 endif
N1710 setal(61000)
N1720 endif
TRANS(X,21,Y,34,Z,33,CAX,11,B,44,C,20):CROT(X,10,Y,20,Z,30):CMIRROR(X,CAX,
C)
N1740 setal(61001)
N1750 endif
N1760
N1770 TRAFOOF
N1780
N1790 if $P_BFRAME <> CTRANS(X,10,Y,20,Z,30,B,40,C,15)
N1800 setal(61000)
N1810 endif
N1830 setal(61000)
N1840 endif
N1860 setal(61000)
N1870 endif
N1890 setal(61000)
N1900 endif
N1920 setal(61002)
N1930 endif
N1940
N1950 m30
Basic functions
3.5 Frames
3.5.6.6 Adapting active frames

The geometry axis constellation can change during the program processing or for RESET. The
number of existent geometry axes varies between zero to three. For non-existent geometry
axes, components in the active frames (e.g. rotations) can cause the active frames for these
axis constellations to become invalid. This is indicated with the "Channel %1 block %2 rotation
programmed for non-existent geometry axis" alarm. The alarm remains pending until the
frames have been changed appropriately.
The automatic adaptation of active frames can be activated with the following machine data:
MD24040 $MC_FRAME_ADAPT_MODE, bit<n> = <value>
Bit <value> Meaning

0 1 Rotations in active frames that rotate coordinate axes for which there are no ge‐
ometry axes, are deleted from the active frames.
1 1 Shearing angles in active frames are made orthogonal.
2 1 Scaling factors of all geometry axes in the active frames are set to 1.
All rotations in the active frames that could cause coordinate axis motions for non-existent
geometry axes are deleted with the following machine data:
MD24040 $MC_FRAME_ADAPT_MODE = 1
The data management frames are not changed in the process. Only the possible rotations are
accepted for the activation of data management frames.
Example:
No Y axis exists:
● MD20050 $MC_AXCONF_GEOAX_ASSIGN_TAB[0] = 1
● $P_UIFR[1] = CROT(X,45,Y,45,Z,45)
Program code ; Comment

N390 G54 G0 X10 Z10 F10000
IF $P_IFRAME <> CROT(Y,45) ; Only the rotation around Y is transfer-
red
SETAL(61000)
ENDIF
3.5.6.7 Mapped Frames
Overview
The "mapped frames" function supports the cross-channel consistent change of axis-specific
frames inside channel-specific or global data management frames. Using axis-specific
machine data, it is defined between which axes mapping is realized.
Basic functions
3.5 Frames
If frame mapping is, e.g. active for machine axes AX1 and AX4, and the axis-specific frame of
axis AX1 is changed in a channel-specific data management frame (e.g. basic frame
$P_CHBFR[x]) (translation, fine translation, scaling, mirroring), then this frame data for AX1
and AX4 is transferred to all channel-specific data management frames (e.g. basic frame
$P_CHBFR[x]) in all channels in which they are parameterized as channel axes.
Frame mapping is not realized when changing the axis-specific frame data for the rotation.
Requirements
The following requirements must be fulfilled for frame mapping:
● The data management frames used for mapping must be configured:
MD28083 $MC_MM_SYSTEM_DATAFRAME_MASK (system frames)
● Channel-specific data management frames must be explicitly enabled for mapping:
MD10616 $MN_MAPPED_FRAME_MASK (enable frame mapping)
Note
For global data management frames, mapping is always carried out. An enable is not
required.
Parameterization
The parameterization of the mapping relationships is realized in the axis-specific machine data:
MD32075 $MA_MAPPED_FRAME[<AXn>] = "AXm"
AXn, AXm: Machine axis name with n, m = 1, 2, ... max. number of machine axes
Mapping rules
The following rules apply for frame mapping:
● The mapping is bidirectional.
An axis-specific frame can be written for axis AXn or AXm. The frame data is always
accepted and taken for the other axis.
● All parameterized mapping relationships are always evaluated.
When writing an axis-specific frame of axes AXn, all mapping relationships are evaluated
and the frame data accepted for all directly and indirectly involved axes.
● The mapping is global across all channels.
When writing an axis-specific frame of axis AXn or AXm for a channel-specific frame, the
frame data is accepted for all channels in which AXn or AXm are parameterized as channel
axes.
Basic functions
3.5 Frames
● When writing an axis-specific frame using geometry or special axis name, the mapping
relationships are evaluated via the machine axes currently assigned to the geometry or
special axis.
● Mapping is frame-specific.
When writing an axis-specific frame, the frame data is only mapped within the same channel-
specific or global data management frame.
Note
Data consistency
The user / machine manufacturer is solely responsible for ensuring that after a frame is
written, consistent frame data is available in all channels, e.g. by using channel
synchronization.
Basic functions
3.5 Frames
&KDQQHO &KDQQHO &KDQQHO &KDQQHO

&KDQQHOD[HV
*HRPHWU\
DGGLWLRQDOD[HV
0DFKLQHD[LV
; $; ; $;

; $; ; $; ; $;

; $; ; $; ; $;
; $; ; $; ; $; ; $;

; $; ; $;
([SOLFLWPDSSLQJ
< $; < $;
,PSOLFLWPDSSLQJ
Description Parameterization: $MA_

① Simple mapping relationship: MAPPED_FRAME[<AX1>] = "AX4"
AX1(K1) ↔ AX4(K2)
② Chained mapping relationships: MAPPED_FRAME[<AX1>] = "AX4"
AX1(K1) ↔ AX4(K2) ↔ AX7(K3) MAPPED_FRAME[<AX4>] = "AX7"
③ Mapping relationship to itself, with AX1 as chan‐ MAPPED_FRAME[<AX1>] = "AX1"
nel axis of channels 1, 2 and 3:
AX1(K1+K2+K3)
④ Mapping relationship between two axes, the MAPPED_FRAME[<AX1>] = "AX4"
channel axes in two channels are:
AX1(K1+K2) ↔ AX4(K3+K4)
⑤ Chained mapping relationships where multiple MAPPED_FRAME[<AX4>] = "AX7"
channel axes can be written in the same channel: MAPPED_FRAME[<AX7>] = "AX8"
AX4(K1) ↔ AX7(K2) ↔ AX8(K2) ↔ AX5(K1) MAPPED_FRAME[<AX8>] = "AX5"
Figure 3-25 Mapping examples
Basic functions
3.5 Frames
Activating the data management frame

Data management frames can be written in the part program and via the user interface of
SINUMERIK Operate. The following should be noted when activating the data management
frames in the channels written directly and via frame mapping:
● Writing in the part program
The data management frames must be explicitly activated in each channel (G500, G54 ...
G599)
● Writing via user interface
Data management frames are written via the user interface, e.g. by entering new work
offsets. A modified data management frame is immediately active in all of the involved
channels if none of these channels is in the "Channel active" state. The data management
frame is not active in any channel if one of the channels involved is in the "Channel active"
state. The activation must then be explicitly programmed in each channel in the part
program (G500, G54 ... G599). Or, the next time that the channel state changes, it becomes
active after "Channel reset".
Example
The following channels and channel axes are parameterized at a control:
● Channel 1
– Z: Geometry axis
– AX1: Machine axis of geometry axis Z
● Channel 2
The zero point of the Z axis should always be the same in both channels:
● Mapping relationship: $MA_MAPPED_FRAME[AX1] = "AX4"
Part programs in channel 1 and 2
Channel 1 Channel 2
... ...
N100 WAIT (10,1,2) N200 WAIT (10,1,2)
N110 $P_UIFR[1] = CTRANS(Z, 10)
N120 WAIT (20,1,2) N220 WAIT (20,1,2)
N130 G54 N230 G54
N140 IF ($P_IFRAME[0, Z, TR] <> 10) N230 IF ($P_IFRAME[0, Z, TR] <> 10)
N150 SETAL(61000) N250 SETAL(61000)
N160 ENDIF N260 ENDIF
... ...
Description:
N100 / N200 Channel synchronization for consistent writing and mapping of frame data
Basic functions
3.5 Frames
N110 Writing of the settable data management frame $P_UIFR[1]:

Moving the zero point of the Z axis to 10 mm
Mapping the axis-specific frame data:
Channel1: Z ≙ AX1 ⇔ channel 2: Z ≙ AX4
N120 / N220 Channel synchronization for consistent activation of new frame data
N130 / N230 Activating the new frame data
N140 / N240 Checking the zero point of the Z axis for: 10 mm
3.5.6.8 Mapped Frames
Overview
The "mapped frames" function supports the cross-channel consistent change of axis-specific
frames inside channel-specific or global data management frames. Using axis-specific
machine data, it is defined between which axes mapping is realized.
If frame mapping is, e.g. active for machine axes AX1 and AX4, and the axis-specific frame of
axis AX1 is changed in a channel-specific data management frame (e.g. basic frame
$P_CHBFR[x]) (translation, fine translation, scaling, mirroring), then this frame data for AX1
and AX4 is transferred to all channel-specific data management frames (e.g. basic frame
$P_CHBFR[x]) in all channels in which they are parameterized as channel axes.
Frame mapping is not realized when changing the axis-specific frame data for the rotation.
Requirements
The following requirements must be fulfilled for frame mapping:
● The data management frames used for mapping must be configured:
MD28083 $MC_MM_SYSTEM_DATAFRAME_MASK (system frames)
● Channel-specific data management frames must be explicitly enabled for mapping:
MD10616 $MN_MAPPED_FRAME_MASK (enable frame mapping)
Note
For global data management frames, mapping is always carried out. An enable is not
required.
Parameterization
The parameterization of the mapping relationships is realized in the axis-specific machine data:
MD32075 $MA_MAPPED_FRAME[<AXn>] = "AXm"
AXn, AXm: Machine axis name with n, m = 1, 2, ... max. number of machine axes
Basic functions
3.5 Frames
Mapping rules
The following rules apply for frame mapping:
● The mapping is bidirectional.
An axis-specific frame can be written for axis AXn or AXm. The frame data is always
accepted and taken for the other axis.
● All parameterized mapping relationships are always evaluated.
When writing an axis-specific frame of axes AXn, all mapping relationships are evaluated
and the frame data accepted for all directly and indirectly involved axes.
● The mapping is global across all channels.
When writing an axis-specific frame of axis AXn or AXm for a channel-specific frame, the
frame data is accepted for all channels in which AXn or AXm are parameterized as channel
axes.
● When writing an axis-specific frame using geometry or special axis name, the mapping
relationships are evaluated via the machine axes currently assigned to the geometry or
special axis.
● Mapping is frame-specific.
When writing an axis-specific frame, the frame data is only mapped within the same channel-
specific or global data management frame.
Note
Data consistency
The user / machine manufacturer is solely responsible for ensuring that after a frame is
written, consistent frame data is available in all channels, e.g. by using channel
synchronization.
Basic functions
3.5 Frames
&KDQQHO &KDQQHO &KDQQHO &KDQQHO

&KDQQHOD[HV
*HRPHWU\
DGGLWLRQDOD[HV
0DFKLQHD[LV
; $; ; $;

; $; ; $; ; $;

; $; ; $; ; $;
; $; ; $; ; $; ; $;

; $; ; $;
([SOLFLWPDSSLQJ
< $; < $;
,PSOLFLWPDSSLQJ
Description Parameterization: $MA_

① Simple mapping relationship: MAPPED_FRAME[<AX1>] = "AX4"
AX1(K1) ↔ AX4(K2)
② Chained mapping relationships: MAPPED_FRAME[<AX1>] = "AX4"
AX1(K1) ↔ AX4(K2) ↔ AX7(K3) MAPPED_FRAME[<AX4>] = "AX7"
③ Mapping relationship to itself, with AX1 as chan‐ MAPPED_FRAME[<AX1>] = "AX1"
nel axis of channels 1, 2 and 3:
AX1(K1+K2+K3)
④ Mapping relationship between two axes, the MAPPED_FRAME[<AX1>] = "AX4"
channel axes in two channels are:
AX1(K1+K2) ↔ AX4(K3+K4)
⑤ Chained mapping relationships where multiple MAPPED_FRAME[<AX4>] = "AX7"
channel axes can be written in the same channel: MAPPED_FRAME[<AX7>] = "AX8"
AX4(K1) ↔ AX7(K2) ↔ AX8(K2) ↔ AX5(K1) MAPPED_FRAME[<AX8>] = "AX5"
Figure 3-26 Mapping examples
Activating the data management frame

Data management frames can be written in the part program. The following should be noted
when activating the data management frames in the channels written directly and via frame
mapping:
● Writing in the part program
The data management frames must be explicitly activated in each channel (G500, G54 ...
G599)
Basic functions
3.5 Frames
Example
The following channels and channel axes are parameterized at a control:
● Channel 1
● Channel 2
The zero point of the Z axis should always be the same in both channels:
● Mapping relationship: $MA_MAPPED_FRAME[AX1] = "AX4"
Part programs in channel 1 and 2
Channel 1 Channel 2
... ...
N100 WAIT (10,1,2) N200 WAIT (10,1,2)
N110 $P_UIFR[1] = CTRANS(Z, 10)
N120 WAIT (20,1,2) N220 WAIT (20,1,2)
N130 G54 N230 G54
N140 IF ($P_IFRAME[0, Z, TR] <> 10) N230 IF ($P_IFRAME[0, Z, TR] <> 10)
N150 SETAL(61000) N250 SETAL(61000)
N160 ENDIF N260 ENDIF
... ...
Description:
N100 / N200 Channel synchronization for consistent writing and mapping of frame data
N110 Writing of the settable data management frame $P_UIFR[1]:
Moving the zero point of the Z axis to 10 mm
Mapping the axis-specific frame data:
Channel1: Z ≙ AX1 ⇔ channel 2: Z ≙ AX4
N120 / N220 Channel synchronization for consistent activation of new frame data
N130 / N230 Activating the new frame data
N140 / N240 Checking the zero point of the Z axis for: 10 mm
3.5.7 Predefined frame functions
3.5.7.1 Inverse frame

The INVFRAME() function calculates the appropriate inverse frame from a frame.
Basic functions
3.5 Frames
Function description
The chaining between a frame and its inverse frame always produces a zero frame.
FRAME: INVFRAME(FRAME) ⇒ null frame
Frame inversion is an aid for coordinate transformations. Measuring frames are usually
calculated in the WCS. If you wish to transform this calculated frame into another coordinate
system, i.e. the calculated frame should be entered into any arbitrary frame within the frame
chain, then the calculations below should be used.
The new complete frame is a chain of the old complete frame and the calculated frame:
$P_ACTFRAME = $P_ACTFRAME: $AC_MEAS_FRAME
The new frame in the frame chain is therefore:
● Target frame is $P_SETFRAME:
$P_SETFRAME = $P_ACTFRAME: $AC_MEAS_FRAME: INVFRAME($P_ACTFRAME):
$P_SETFRAME
● The target frame is the nth channel basic frame $P_CHBFRAME[<n>]:
k = $MN_MM_NUM_GLOBAL_BASE_FRAMES
– For n = 0, TMP is resolved as:
TMP = $P_PARTFRAME : $P_SETFRAME : $P_EXTFRAME :
$P_NCBFRAME[<0...k>]
– For n ≠ 0, TMP is resolved as:
TMP = $P_PARTFRAME : $P_SETFRAME : $P_EXTFRAME :
$P_NCBFRAME[<0..k>] : $P_CHBFRAME[<0...n> - 1]
$P_CHBFRAME[<n>] = INVFRAME(TMP) : $P_ACTFRAME : $AC_MEAS_FRAME :
INVFRAME($P_ACTFRAME) : TMP : $P_CHBFRAME[<n>]
● The target frame is $P_IFRAME:
TMP = $P_PARTFRAME: $P_SETFRAME: $P_EXTFRAME: $P_BFRAME
$P_IFRAME = INVFRAME(TMP): $P_ACTFRAME: $AC_MEAS_FRAME:
INVFRAME($P_ACTFRAME) : TMP : $P_IFRAME
Example
A frame calculated, for example, using a measuring function, must be entered in the
actual SETFRAME such that the new complete frame is a chain of the old complete frame and
the measurement frame. The SETFRAME is calculated accordingly by means of frame
inversions.

DEF INT RETVAL
DEF FRAME TMP
$TC_DP1[1,1]=120 ; Type
$TC_DP2[1,1]=20. ; 0
$TC_DP3[1,1]= 10. ; (z) length correction vector
$TC_DP4[1,1]= 0. ; (y)
$TC_DP5[1,1]= 0. ; (x)
$TC_DP6[1,1]= 2. ; Radius
T1 D1
Basic functions
3.5 Frames

g0 x0 y0 z0 f10000
G54
$P_CHBFRAME[0] = CROT(Z,45)
$P_IFRAME[X,TR] = -SIN(45)
$P_IFRAME[Y,TR] = -SIN(45)
$P_PFRAME[Z,TR] = -45
$AC_MEAS_VALID = 0 ; Measure corner with four measuring
points
G1 X-1 Y-3 ; 1st Approach measuring point
$AC_MEAS_LATCH[0] = 1 ; 1st Store measuring point
G1 X5 Y-3 ; 2nd Approach measuring point
$AC_MEAS_LATCH[1] = 1 ; 2nd Store measuring point
G1 X-4 Y4 ; 3rd Approach measuring point
$AC_MEAS_LATCH[2] = 1 ; 3rd Store measuring point
G1 X-4 Y1 ; 4th Approach measuring point
$AC_MEAS_LATCH[3] = 1 ; 4th Store measuring point
$AA_MEAS_SETPOINT[X] = 0 ; Set position setpoint of the corner
$AA_MEAS_SETPOINT[Y] = 0
$AA_MEAS_SETPOINT[Z] = 0
$AC_MEAS_CORNER_SETANGLE = 90 ; Define setpoint angle of intersection
$AC_MEAS_WP_SETANGLE = 30
$AC_MEAS_ACT_PLANE = 0 ; Measuring plane is G17
$AC_MEAS_T_NUMBER = 1 ; Select tool
$AC_MEAS_D_NUMBER = 1
$AC_MEAS_TYPE = 4 ; Set measuring type on corner 1
RETVAL = MEASURE() ; Start measuring process
IF RETVAL <> 0
SETAL(61043, << RETVAL)
ENDIF
IF $AC_MEAS_WP_ANGLE <> 30
SETAL(61043, << $AC_MEAS_WP_ANGLE)
ENDIF
IF $AC_MEAS_CORNER_ANGLE <> 90
SETAL(61043, << $AC_MEAS_CORNER_ANGLE)
ENDIF
; Transform measured frame and write to $P_SETFRAME so that a complete frame is cre-
ated,
; which linked from the old total frame results in the measurement frame.
$P_SETFRAME = $P_ACTFRAME: $AC_MEAS_FRAME: INVFRAME($P_ACTFRAME): $P_SETFRAME
$P_SETFR = $P_SETFRAME ; Describe system frames in data manage-
ment
G1 X0 Y0 ; Approach the corner
G1 X10 ; Retract the rectangle rotated about 30
degrees
Y10
Basic functions
3.5 Frames

X0
Y0
M30
3.5.7.2 Additive frame in frame chain

Measurements on the workpiece or calculations in the part program or cycle often produce a
frame that is applied additively to the active complete frame. This causes, for example, the
WCS and thus the programming zero point to be displaced and/or possibly rotated. The
measured frame so exists in a frame variable and has not yet been included in the frame chain
calculation.
Function description
The ADDFRAME() function calculates from the temporary frame the specified target frame
specified by the <STRING> parameter so that the new active $P_ACTFRAME complete frame
from the chaining of the old active complete frame with the temporary frame gives:
ERG = ADDFRAME(TMPFRAME,"$P_SETFRAME") ⇒ $P_SETFRAMEnew = $P_SETFRAMEold
ADD TMPFRAME and $P_ACTFRAMEnew = $P_ACTFRAMEold : TMPFRAME
If an active frame has been specified as a target frame, the new complete frame becomes
active at the preprocessing stage.
If the target frame is a data management frame, the frame becomes active only when it is
activated explicitly in the channel, e.g. part program or cycle.
The function returns a return value for which a user-specific response is possible, e.g. in a user
cycle.
Programming
Syntax
INT ADDFRAME(<FRAME>,<STRING>)
Meaning
<FRAME>: Frame variable with the values to be included additively in the calculation
Type FRAME
Basic functions
3.5 Frames
<STRING>: The name of an active or data management frame:

● Active frames
"$P_CYCFRAME", "$P_ISO4FRAME", "$P_PFRAME",
"$P_WPFRAME", "$P_TOOLFRAME", "$P_IFRAME", "$P_GFRAME",
"$P_CHBFRAME[<n>]", "$P_NCBFRAME[<n>]", "$P_ISO1FRAME",
"$P_ISO2FRAME", "$P_ISO3FRAME", "$P_EXTFRAME", "$P_SET‐
FRAME", "$P_PARTFRAME"
● Data management frames
"$P_CYCFR", "$P_ISO4FR, "$P_TRAFR", "$P_WPFR", "$P_TOOLFR",
"$P_UIFR[<n>]", "$P_GFR", "$P_CHBFR[<n>]", "$P_NCBFR[<n>]",
"$P_ISO1FR, "$P_ISO2FR, "$P_ISO3FR, "$P_EXTFR", "$P_SETFR",
"$P_PARTFR"
Type STRING
Return value: Possible return values:
● 0: OK
● 1: Specified target (string) is wrong
● 2: Target frame is not configured
● 3: Rotation in frame is not permitted
Type INT
3.5.8 Functions
3.5.8.1 Setting zeros, workpiece measuring and tool measuring

Set actual value is initiated by means of an HMI operator action or via measuring cycles. The
calculated frame can be written to system frame SETFRAME. The position setpoint of an axis in
the WCS can be altered during set actual value.
The term "scratching" refers to both the workpiece and tool measurement. The position of the
workpiece can be measured in relation to an edge, a corner or a hole. To determine the zero
position of the workpiece or the hole, position setpoints can be added to the measured positions
in the WCS. The resulting offsets can be entered in a selected frame. In the tool measurement,
the length or radius of a tool can be measured using a measured reference part.
The measurements can be initiated by means of an operator action or via measuring cycles.
Communication with the NC takes place via predefined system variables. The calculation is
performed in the NC when a PI service is activated by means of an HMI operator action or via
a part program command from the measuring cycles. A tool and a plane can be selected as a
basis for the calculation. The calculated frame is entered in the result frame.
3.5.8.2 Axis-specific external work offset
Machine data
The external work offset or the $P_EXTFRAME system frame is activated with the following
machine data:
MD28082 $MC_MM_SYSTEM_FRAME_MASK, bit 1 = TRUE
Basic functions
3.5 Frames
The magnitude for the external work offset can be specified manually via the HMI user
interface, and the PLC user program via OPI or programmed in the part program via the axial
system variable $AA_ETRANS[<axis>].
Activation
The external work offset is activated with the interface signal:
DB31, ... DBX3.0 (accept external work offset)
Behavior
Upon activation of the external work offset, the traversing movements of all axes, except
command and PLC axes, are stopped immediately and the advance is reorganized. The rough
offset of the current system frame and of the system frame in data management is set to the
value of the axial system variable $AA_ETRANS[<axis>]. Thereafter, the offset is traversed
first and then the interrupted movement is continued.
Behavior for incremental dimension
In case of active incremental dimension G91 and machine data:
MD42440 $MC_FRAME_OFFSET_INCR_PROG (work offset in frames) = 0
traversing the offset is done in the scope of the external work offset via system frame, despite
opposite configuring of the machine data, with the approach block, although it is specified by a
frame.
Note
The external work offset always acts absolutely.
3.5.8.3 Toolholder
Translations
With kinematics of type "P" and "M", the selection of a toolholder activates an additive frame
(table offset of the orientable toolholder) which takes into account the work offset as a result of
the rotation of the table. The work offset is entered in the system frame $P_PARTFR. In this case
the translatory component of this frame is overwritten. The other frame components are
retained.
The system frame $P_PARTFR must be enabled via the following machine data:
MD28082 $MC_MM_SYSTEM_FRAME_MASK, bit 2 = 1 (system frame for TCARR and
PAROT)
Note
Alternatively, the offset can also parameterized via machine data to record the table offset:
MD20184 $MC_TOCARR_BASE_FRAME_NUMBER = <number of the basic frame>
This option is only for compatibility reasons to older software versions. You are strongly
recommended not to use this procedure any longer.
Basic functions
3.5 Frames
A frame offset as a result of a toolholder change becomes effective immediately on selection of

TCARR=.... A change in the tool length, on the other hand, only becomes effective
immediately if a tool is active.
A frame rotation is not executed with the activation, or a rotation which is already active is not
changed. As in case T (only the tool can be rotated), the position of the rotary axes used for the
calculation is dependent on the command TCOFR/TCOABS and determined from the rotation
component of an active frame or from the $TC_CARR entries. Activation of a frame changes
the position in the workpiece coordinate system accordingly, without compensating motion by
the machine itself.
The ratios are shown in the figure below:
2ULJLQDOSRVLWLRQRIWKHFRRUGLQDWHV\VWHP
&RRUGLQDWHV\VWHPSRVLWLRQDIWHU
7&$55
&RRUGLQDWHV\VWHPSRVLWLRQDIWHU
2ULJLQDO 3$527
SRVLWLRQRI
WDEOH
3RVLWLRQRIWKHWDEOH
DIWHUURWDWLRQ
Figure 3-27 Frame on activation of a rotary table with TCARR
With kinematics of type M (tool and table are each rotary around one axis), the activation of a
toolholder with TCARR simultaneously produces a corresponding change in the effective tool
length (if a tool is active) and the work offset.
Rotations
Depending on the machining task, it is necessary to take into account not only a work offset
(whether as frame or as tool length) when using a rotary toolholder or table, but also a rotation.
However, the activation of an orientable toolholder never leads directly to a rotation of the
coordinate system.
If only the tool can be rotated, a frame can be defined for it using TOFRAME or TOROT.
With rotary tables (kinematics types P and M), activation with TCARR similarly does not lead to
an immediate rotation of the coordinate system, i.e. even though the zero point of the
coordinate system is offset relative to the machine, while remaining fixed relative to the zero
point of the workpiece, the orientation remains unchanged in space.
If the coordinate system needs to be fixed relative to the workpiece, i.e. not only offset relative
to the original position but also rotated according to the rotation of the table, then PAROT can be
used to activate such a rotation in a similar manner to the situation with a rotary tool.
With PAROT, the translations, scalings and mirroring in the active frame are retained, but the
rotation component is rotated by the rotation component of an orientable toolholder
corresponding to the table. The entire programmable frame including its rotation component
remains unchanged.
Basic functions
3.5 Frames
The rotation component that describes the rotation of the table is then either entered in the
system frame $PARTFR or in the basic frame parameterized with MD20184
$MC_TOCARR_BASE_FRAME_NUMBER:
$MC_MM_SYSTEM_FRAME_MASK, bit 2 = <value>
Value Meaning
1 Rotation component → $PARTFR
0 Rotation component → MD20184 $MC_TOCARR_BASE_FRAME_NUMBER
As with the note made in the description of the table offset, the second alternative here is not
recommended for use with new systems.
The rotation component of the part frame can be deleted with PAROTOF, irrespective of whether
this frame is in a basic or a system frame.
The translation component is deleted when a toolholder which does not produce an offset is
activated or a possibly active orientable toolholder is deselected with TCARR=0.
PAROT or TOROT take into account the overall orientation change in cases where the table or
the tool are oriented with two rotary axes. With mixed kinematics, only the corresponding
component caused by a rotary axis is considered. It is thus possible, for example, when using
TOROT, to rotate a workpiece such that an inclined plane lies parallel to the XY plane fixed in
space, whereby rotation of the tool must be taken into account in machining where any holes
to be drilled, for example, are not perpendicular to this plane.
Example
On a machine, the rotary axis of the table points in the positive Y direction. The table is rotated
by +45 degrees. PAROT defines a frame which similarly describes a rotation of 45 degrees
around the Y axis. The coordinate system is not rotated relative to the actual environment
(marked in the figure with "Position of the coordinate system after TCARR"), but is rotated by
-45 degrees relative to the defined coordinate system (position after PAROT). If this coordinate
system is defined with ROT Y-45, for example, and if the toolholder is then selected with active
TCOFR, an angle of +45 degrees will be determined for the rotary axis of the toolholder.
Language command PAROT is not rejected if no orientable toolholder is active. However, such
a call then produces no frame changes.
Machining in direction of tool orientation

Particularly on machines with tools that can be oriented, traversing should take place in the tool
direction (typically, when drilling) without activating a frame (e.g. using TOFRAME or TOROT), on
which one of the axes points in the direction of the tool. This is also a problem if, when carrying
out inclined machining operations, a frame defining the inclined plane is active, but the tool
cannot be set exactly perpendicularly because an indexed toolholder (Hirth tooth system)
prevents free setting of the tool orientation. In these cases it is then necessary - contrary to the
motion actually requested perpendicular to the plane - to drill in the tool direction, as the drill
would otherwise not be guided in the direction of its longitudinal axis (tool breaks).
Incremental traversing
The end point for incremental traversing motion in the tool direction is programmed using MOVT
= <Value> or MOVT=IC(<Value>).
Basic functions
3.5 Frames
The positive traversing direction is defined from the tool tip to the tool adapter. Corresponding
to paraxial machining, e.g. with G91 Z ....
Absolute traversing
The end point for absolute incremental traversing motion in the tool direction is programmed
using MOVT=AC(<Value>).
In this case a plane is defined, which runs through the current zero point, and whose surface
normal vector is parallel to the tool orientation. MOVT then gives the position relative to this
plane (see figure). The reference plane is only used to calculate the end position. Active frames
are not affected by this internal calculation.
=

02
9 7
$&
ಹ
Programming with MOVT is independent of the existence of a toolholder that can be oriented.
The direction of the motion is dependent on the active plane.
It runs in the directions of the vertical axes, i.e. with G17 in Z direction, with G18 in Y direction
and with G19 in X direction. This applies when no orientable toolholder is active and for the case
of an orientable toolholder without rotary tool or with a rotary tool in its basic setting.
MOVT acts similarly for active orientation transformation (3-, 4-, 5-axis transformation).
If in a block with MOVT the tool orientation is changed simultaneously (e.g. active 5-axis
transformation by means of simultaneous interpolation of the rotary axes), the orientation at the
start of the block is decisive for the direction of motion of MOVT.
With an active 5-axis transformation, the path of the tool center point (TCP) is not affected by
the change of orientation, i.e. the path remains a straight line and its direction is determined by
the tool orientation at the start of the block.
If MOVT is programmed, linear or spline interpolation must be active (G0,G1, ASPLINE,
BSPLINE, CSPLINE). Otherwise, an alarm is produced.
If a spline interpolation is active, the resultant path is generally not a straight line, since the end
point calculated by MOVT is treated as if it had been programmed explicitly with X, Y, Z.
It is not permissible to program geometry axes in a block with MOVT.
Definition of frame rotations with solid angles

Where a frame is to be defined to describe a rotation around more than one axis, this is
achieved through chaining individual rotations. The subsequent rotation is realized in the newly
rotated coordinate system.
Basic functions
3.5 Frames
This applies both to programing in one block - and when configuring a frame in several
consecutive blocks:
● One block: N10 ROT X... Y... Z...
● Several consecutive blocks:
N10 ROT Y...
N20 AROT X...
N30 AROT Z...
Solid angle
Often, solid angles are specified in workpiece drawings to define inclined surfaces. Solid angles
are angles which the intersection lines of the inclined plane form with the main planes (X-Y, Y-
Z, Z-X planes) of the workpiece coordinate system (see diagram). The orientation of a plane in
space is defined unambiguously by specifying two solid angles. The third solid angle is derived
from the first two.
Rotations can be directly defined as solid angle using ROTS, AROTS and CROTS commands.
It is permissible to specify a single solid angle. The rotation which is performed with ROTS or
AROTS in this case is identical to that for ROT and AROT.
The two axes programmed in the command define a plane. The non-programmed axis defines
the associated third axis of a coordinate system. This also means that for the two programmed
axes, it is uniquely defined which is the first axis and which is the second axis. The definition
corresponds to the definition of a plane for G17/G18/G19.
The angle programmed with the axis letter of an axis of the plane then specifies the axis, around
which the other axis of the plane must be rotated in order to move this into the line of
intersection, which the rotated plane forms with the plane surrounded by the other and the third
axis. This definition ensures that, in the case that one of the two programmed angles is towards
zero, the defined plane enters the plane, which is created if only one axis is programmed (e.g.
with ROT or AROT).
Basic functions
3.5 Frames
= =
<ಿ
=ಿ
3 3
< <

6
3 3 ෥˞ 3
෥˟ =ಿ ෥˟
;ಿ
6
˞
3
<ಿ
; ;
;ಿ
= =
<ಿ <ಿ
3 3
< <
=ಿ
෥˞
3
6
;ಿ
6
=ಿ
˟ ˟
˞
3 3 3
; ;
;ಿ
I, ..., Quadrants 1 to 4
IV
① Inclined plane as specification for the new G17 plane
α, β Solid angle of the inclined plane
Figure 3-28 Rotation around the solid angle
In the diagram, the solid angles are shown for an example of a plane in quadrants I to IV. The
inclined plane defines the alignment of the G17 plane after rotating the workpiece coordinate
Basic functions
3.5 Frames
system WCS. The sign of the solid angle specifies the direction around which the coordinate
system is rotated around the relevant axis.
1. Rotation around y:
Rotation of the workpiece coordinate system WCS around the y axis around the signed
angle α ⇒
The x' axis is aligned parallel (colinear) to the intersection lines of the xz plane with the
inclined plane
2. Rotation around x':
Rotation of the new workpiece coordinate system WCS around the x' axis around the signed
angle β ⇒
– The y' axis is aligned in parallel (colinear) to the intersection lines of the zy plane with the
inclined plane
– The z' axis is perpendicular to the inclined plane
– G17' lies in parallel to the inclined plane
The programming to align the G17 plane of the workpiece coordinate system WCS to the
inclined plane is, for each quadrant:
● Quadrant I: ROTS X<+α> Y<-β>
● Quadrant II: ROTS X<-α> Y<-β>
● Quadrant III: ROTS X<-α> Y<+β>
● Quadrant IV: ROTS X<+α> Y<+β>
Orientation
The specification of the solid angle does not define the orientation of the two-dimensional
coordinate system within the plane (i.e. the angle of rotation around the surface normal vector).
The position of the coordinate system is thus determined so that the rotated first axis lies in the
plane which is formed by the first and third axes of the non-rotated coordinate system.
This means that
● When programming X and Y, the new X axis lies in the original Z-X plane.
● When programming Z and X, the new Z axis lies in the original Y-Z plane.
● When programming Y and Z, the new Y axis lies in the original X-Y plane.
If the required coordinate system does not correspond to this basic setting, then an additional
rotation must be performed with AROT....
Parameterization: zy'x'' (RPY angle) or zx'z'' convention

The programmed solid angles are converted to the equivalent Euler angles according to the the
zy'x" convention (RPY angle) or zx'z" convention when entering depending on the following
machine data:
MD10600 $MN_FRAME_ANGLE_INPUT_MODE
Basic functions
3.5 Frames
Frame rotation in tool direction

With the language command TOFRAME, which also existed in older software versions, it is
possible to define a frame whose Z axis points in the tool direction.
An already programmed frame is then overwritten by a frame which describes a pure rotation.
Any work offsets, mirrorings or scalings existing in the previously active frame are deleted.
This response is sometimes interfering. It is often particularly practical to retain a work offset,
with which the reference point in the workpiece is defined.
The language command TOROT is then also used. This command overwrites only the rotation
component in the programmed frame and leaves the remaining components unchanged. The
rotation defined with TOROT is the same as that defined with TOFRAME.
TOROT is, like TOFRAME, independent of the availability of an orientable toolholder. This
language command is also especially useful for 5-axis transformations.
The new language command TOROT ensures consistent programming with active orientable
toolholders for each kinematics type.
TOFRAME or TOROT defines frames whose Z direction points in the tool direction. This definition
is suitable for milling, where G17 is usually active. However, particularly with turning or, more
generally, when G18 or G19 is active, it is desirable that frames which will be aligned on the X
or Y axis, can be defined. For this purpose, the following commands are available in G group
53:
● TOFRAMEX, TOFRAMEY, TOFRAMEZ
● TOROTX, TOROTY, TOROTZ
The appropriate frames can be defined with these commands. The functions of TOFRAME and
TOFRAMEZ or of TOROT and TOROTZ are identical to one another.
The frames resulting from TOROT or TOFRAME can be written in a separate system frame
($P_TOOLFR). The programmable frame is then retained unchanged.
● Requirement: MD28082 $MC_MM_SYSTEM_FRAME_MASK, bit 3 = 1
When programming TOROT or TOFRAME, etc. response is identical, with or without a system
frame. Differences occur when the programmable frame is processed further elsewhere.
Note
In new systems, it is recommended that only the intended system frame is used for frames
produced by the commands of G group 53.
Example
TRANS is programmed after TOROT. TRANS without specified parameters deletes the
programmable frame. In the variant without a system frame, this also deletes the frame
component of the programmable frame produced by TOROT, but if the TOROT component is in
the system frame, it is retained.
TOROT or TOFRAME, etc. are disabled with language command TOROTOF. TOROTOF deletes the
entire system frame $P_TOOLFR. If the programmable frame (old variant) and not the system
frame is described by commands TOFRAME, etc. TOROT only deletes the rotation component
and leaves the remaining frame components unchanged.
If a rotating frame is already active before language command TOFRAME or TOROT is activated,
a request is often made that the newly defined frame should deviate as little as possible from
Basic functions
3.5 Frames
the old frame. This is the case, for example, if a frame definition needs to be modified slightly
because the tool orientation cannot be set freely on account of Hirth-toothed rotary axes. The
language commands uniquely define the Z direction of the new frame.
Parameterization: Frame definition for TOFRAME, TOROT and PAROT (SD42980)

With the following setting data, the direction of the geometry axes of the actual machining plane
(G17: X and Y axis) for the frame definition is defined using TOFRAME, TOROT
(TOROTY, TOROTX) or PAROT.
For a frame calculation, the tool direction is defined, so that the tool direction and applicate
(G17: Z axis) of the frame are parallel and perpendicular to the machining plane.
Initially, rotation around the tool axis is arbitrary. Using the setting data, this free rotation can be
defined so that the newly defined frame deviates as little as possible from a previously active
frame.
In all cases where the setting data is not equal to zero, an active frame remains unchanged if
the tool direction of the old and the new frame match one another.
SD42980 $SC_TOFRAME_MODE
TCARR (request toolholder) and PAROT (align workpiece coordinate system on the workpiece)
TCARR uses the basic frame identified by following machine data:
MD20184 $MC_TOCARR_BASE_FRAME_NUMBER.
A system frame can be created for TCARR and PAROT alone, in order to avoid conflicts with
systems, which already use all the basic frames.
PAROT, TOROT and TOFRAME have previously changed the rotation component of the
programmable frames. In this case, it is not possible to shut down PAROT or TOROT separately.
On RESET, the programmable frame is deleted, which means that after changing the operating
mode to JOG, the rotation component of PAROT and TOROT is no longer available. The user
must also have unrestricted access to the programmable frame. Frames produced by PAROT
and TOROT must be able to be archived and reloaded via data backup.
The system frame for TCARR and PAROT is configured with:
MD28082 $MC_MM_SYSTEM_FRAME_MASK, bit 2 = 1
The following machine data is then no longer evaluated:
MD20184 $MC_TOCARR_BASE_FRAME_NUMBER
If the system frame for TCARR is configured, TCARR and PAROT describe that corresponding
system frame; otherwise the basic frame identified by machine data MD20184 is described.
With kinematics systems of the types P and M, TCARR will enter the table offset of the orientable
toolholder (work offset resulting from the rotation of the table) as a translation into the system
frame. PAROT converts the system frame so that a workpiece-related WCS results.
The system frames are stored retentively and therefore retained after a reset. The system
frames also remain active in the case of a mode change.
For the display, the commands PAROT and TOROT, TOFRAME are each assigned to a separate
G group.
Basic functions
3.5 Frames
PAROTOF
PAROTOF is the switch off command for PAROT. This command deletes the rotations in the
system frame for PAROT. In so doing, the rotations in the current $P_PARTFRAME and in the
data management frame $P_PARTFR are deleted. The position of the coordinate system is
then recreated according to TCARR. PAROTOF is in the same G group as PAROT and appears
therefore in the G command display.
TOROT (align Z axis of the WCS by rotating the frame parallel to the tool orientation) and TOFRAME
(ditto.)
The system frame for TOROT and TOFRAME is activated via the following machine data:
MD28082 $MC_MM_SYSTEM_FRAME_MASK, bit 3 = 1
This system frame is located before the programmable frame in the frame chain.
The SZS coordinate system is located before the programmable frame.
TOROTOF
TOROTOF is the switch off command for TOROT and TOFRAME. This command deletes the
corresponding system frame. The current $P_TOOLFRAME and the data management frame
$P_TOOLFR are also deleted. TOROTOF is in the same G group as TOROT and TOFRAME and
appears therefore in the G command display.
Example
Use of an orientable toolholder with resolved kinematics.
N10 $TC_DP1[1,1]=120
N20 $TC_DP3[1,1]= 13 ; Tool length 13 mm
; Definition of toolholder 1:
N30 $TC_CARR1[1] = 0 ; X component of the 1st offset vector
N40 $TC_CARR2[1] = 0 ; Y component of the 1st offset vector
N50 $TC_CARR3[1] = 0 ; Z component of the 1st offset vector
N60 $TC_CARR4[1] = 0 ; X component of the 2nd offset vector
N70 $TC_CARR5[1] = 0 ; Y component of the 2nd offset vector
N80 $TC_CARR6[1] = -15 ; Z component of the 2nd offset vector
N90 $TC_CARR7[1] = 1 ; X component of the 1st axis
N100 $TC_CARR8[1] = 0 ; Y component of the 1st axis
N110 $TC_CARR9[1] = 0 ; Z component of the 1st axis
N120 $TC_CARR10[1] = 0 ; X component of the 2nd axis
N130 $TC_CARR11[1] = 1 ; Y component of the 2nd axis
N140 $TC_CARR12[1] = 0 ; Z component of the 2nd axis
N150 $TC_CARR13[1] = 30 ; Angle of rotation of 1st axis
N160 $TC_CARR14[1] = -30 ; Angle of rotation of 2nd axis
N170 $TC_CARR15[1] = 0 ; X component of the 3rd offset vector
N180 $TC_CARR16[1] = 0 ; Y component of the 3rd offset vector
N190 $TC_CARR17[1] = 0 ; Z component of the 3rd offset vector
N200 $TC_CARR18[1] = 0 ; X component of the 4th offset vector
Basic functions
3.5 Frames
N210 $TC_CARR19[1] = 0 ; Y component of the 4th offset vector

N220 $TC_CARR20[1] = 15 ; Z component of the 4th offset vector
N230 $TC_CARR21[1] = A ; Reference for 1st axis
N240 $TC_CARR22[1] = B ; Reference for 2nd axis
N250 $TC_CARR23[1] = "M" ; Toolholder type
N260 X0 Y0 Z0 A0 B45 F2000
N270 TCARR=1 X0 Y10 Z0 T1 TCOABS ; Selection of orientable tool holder
N280 PAROT ; Rotation of table
N290 TOROT ; Rotation of z axis in tool orient.
N290 X0 Y0 Z0
N300 G18 MOVT=AC(20) ; Processing in G18 plane
N310 G17 X10 Y0 Z0 ; Processing in G17 plane
N320 MOVT=-10
N330 PAROTOF ; Deactivate rotation of table
N340 TOROTOF ; No longer align WCS with tool
N400 M30
3.5.9 Subprograms with SAVE attribute (SAVE)

For various frames, the behavior regarding subprograms can be set using the SAVE attribute.
Settable frames G54 to G599

The behavior of the adjustable frames can be set using MD10617
$MN_FRAME_SAVE_MASK.BIT0 :
● BIT0 = 0
If using the subprogram, only the values of the active adjustable frame are changed using
the system variable $P_IFRAME, but the G command is kept, then the change is also kept
after the end of the subprogram.
● BIT0 = 1
With the end of the subprogram, the adjustable frame, G command and values, active
before the subprogram call, are reactivated.
Basic frames $P_CHBFR[ ] and $P_NCBFR[ ]

The behavior of the basic frame can be set using MD10617 $MN_FRAME_SAVE_MASK.BIT1:
● BIT1 = 0
If the active basic frame is changed by the subprogram, the change remains effective even
after the end of the subprogram.
● BIT1 = 1
With the end of the subprogram the basic frame which is active before the subprogram call
is reactivated.
Basic functions
3.5 Frames
Programmable frame
With the end of the subprogram the programmable frame active before the subprogram call is
reactivated.
System frames
If the system frames are changed by the subprogram, the change remains effective even after
the end of the subprogram.
3.5.10 Data backup

Data blocks
The data backup of the frames is performed in the following data blocks:
● Channel-specific frames ⇒ _N_CHAN<x>_UFR data blocks
● Global frames ⇒ _N_NC_UFR data block
Note
● It is strongly recommended that the following machine data is not changed between the
backup and restoration of the saved system frames. Otherwise, it is possible that the saved
system frames cannot be loaded.
MD28082 $MC_MM_SYSTEM_FRAME_MASK (configuration of channel-specific system
frames that are included in the channel calculation)
● The data backup is always performed in accordance with geometry axis assignments
currently valid in the channel rather than in accordance with the axis constellations originally
set in the machine data.
Data backup of system frames

Only the system frames created in the data management are considered for the data backup
of the system frames. These system frames were selected during the commissioning of the
control with the following machine data:
MD28083 $MC_MM_SYSTEM_DATAFRAME_MASK
Frames not created in the data management are not backed up.
Data backup of NC-global frames

A data backup of NC-global frames is performed only when at least one NC-global frame has
been parameterized in one of the following machine data items:
● MD18601 $MN_MM_NUM_GLOBAL_USER_FRAMES
● MD18602 $MN_MM_NUM_GLOBAL_BASE_FRAMES
● MD18603 $MN_MM_NUM_GLOBAL_G_FRAMES
Basic functions
3.5 Frames
3.5.11 Positions in the coordinate system

The current setpoint positions in the coordinate systems can be read via the following system
variables: The actual values can be displayed in the WCS, SZS, BZS or MCS via the PLC.
There is an Actual value display softkey in the MCS/WCS. The machine manufacturer can
specify on the PLC which coordinate system corresponds to the workpiece coordinate system
on a machine. The HMI requests the corresponding actual values form the NC.
$AA_IM[axis]
The setpoints in the machine coordinate system can be read for each axis with the
$AA_IM[axis] variable.
$AA_IEN[axis]
The setpoints in the settable zero system (SZS) can be read for each axis with the
$AA_IEN[axis] variable.
$AA_IBN[axis]
The setpoints in the basic zero system (BZS) can be read with the $AA_IBN[axis] variable.
$AA_IW[axis]
The setpoints in the workpiece coordinate system (WCS) can be read with the $AA_IW[axis]
variable.
3.5.12 Control system response
3.5.12.1 POWER ON
Frame Frame conditions after POWER ON

$P_PFRAME programmable frame Deleted.
$P_IFRAME settable frame Is retained, depending on:
● MD24080 $MC_USER_FRAME_POWERON_MASK, bit 0
● MD20152 $MC_GCODE_RESET_MODE[7]
$P_GFRAME grinding frame Is retained, depending on:
● MD24080 $MC_USER_FRAME_POWERON_MASK, bit 0
$P_ACTBFRAME complete basic Is retained, depending on:
frame ● MD20110 $MC_RESET_MODE_MASK bit 0 and bit 14
Basic frames can be deleted via machine data:
● MD10615 $MN_NCBFRAME_POWERON_MASK
● MD24004 $MC_CHBFRAME_POWERON_MASK
Basic functions
3.5 Frames
Frame Frame conditions after POWER ON

System frames: Retained
$P_PARTFRAME, $P_SET‐ Individual system frames can be deleted via machine data:
FRAME, $P_ISO1FRAME, ● MD24008 $MC_CHSFRAME_POWERON_MASK
$P_ISO2FRAME,
$P_ISO3FRAME, $P_TOOL‐ Deletion of system frames is executed in the data management on
FRAME, $P_WPFRAME, $P_TRA‐ first priority.
FRAME, $P_ISO4FRAME, $P_RE‐
LFRAME, $P_CACFRAME
$P_EXTFRAME external work off‐ Is retained, but has to be activated again.
set
DRF offset Deleted.
3.5.12.2 Mode change
System frames
The system frames are retained and remain active.
JOG mode
In JOG mode, the frame components of the current frame are only taken into account for the
geometry axes if a rotation is active. No other axis-specific frames are taken into account.
PLC and command axes

The response for PLC and command axes can be set via machine data:
MD32074 $MA_FRAME_OR_CORRPOS_NOTALLOWED (frame or HL correction is not
permissible)
3.5.12.3 Channel reset / part program end
Reset behavior of the basic frames

The reset behavior of the basic frames is set via the machine data:
MD20110 $MC_RESET_MODE_MASK (definition of initial control settings after channel reset /
part program end)
Reset behavior of system frames

The system frames are retained in the data management after a channel reset / part program
end.
The machine data below can be used to configure the activation of individual system frames:
Basic functions
3.5 Frames
MD24006 $MC_CHSFRAME_RESET_MASK, bit<n> = <VALUE> (active system frames after

channel-reset / part program end)
Bit Value Meaning

0 1 System frame for actual value setting and scratching is active after channel reset /
part program end.
1 1 System frame for external work offset is active after channel reset / part program
end.
2 --- Is not evaluated.
3 --- Is not evaluated.
4 1 System frame for workpiece reference points is active after channel reset / part
program end.
5 1 System frame for cycles is active after channel reset / part program end.
6 --- Reserved, RESET response depends on MD20110 $MC_RESET_MODE_MASK.
7 1 System frame $P_ISO1FR is active after channel reset / part program end.
11 1 System frame $P_RELFR is active after channel reset / part program end.
For bit<n> = 0, the associated system frame is not active.
Reset behavior of the system frames for TCARR, PAROT, TOROT and TOFRAME
The reset behavior of the system frames for TCARR, PAROT, TOROT and TOFRAME after channel
reset / part program end depends on the reset setting of the G commands.
Basic functions
3.5 Frames
The setting is made with machine data:

● MD20110 $MC_RESET_MODE_MASK, bit<n> = <value>
Bit Value Meaning

0 0 The current system frame for TCARR and PAROT is retained.
0 1 Additional relevant machine data settings Effect
MD20152 $MC_GCODE_RESET_MODE[51] = 0 and PAROTOF
MD20150 $MC_GCODE_RESET_VALUES[51] = 1
MD20152 $MC_GCODE_RESET_MODE[51] = 0 and PAROT
MD20152 $MC_GCODE_RESET_MODE[51] = 1 TCARR
and PAROT are re‐
tained.
MD20152 $MC_GCODE_RESET_MODE[52] = 0 and TOROTOF
MD20152 $MC_GCODE_RESET_MODE[52] = 0 and TOROT
MD20152 $MC_GCODE_RESET_MODE[52] = 0 and TOFRAME
MD20152 $MC_GCODE_RESET_MODE[52] = 1 TOROT
and TOFRAME are
retained
Description of the further bits for bit 0 == 1
14 0 Chained complete basic frame is deleted.
1 The complete basic frame results from the following additional machine data:
MD24002 $MC_CHBFRAME_RESET_MASK, bit<n> = 1
n: The nth channel-specific basic frame is calculated into the chained complete
basic frame.
MD10613 $MN_NCBFRAME_RESET_MASK, bit<n> = 1
n: The nth NCU-global basic frame is calculated into the chained complete basic
frame.
TCARR and PAROT are two independent functions, which describe the same frame.
With PAROTOF, the component of TCARR is not activated for channel reset / part program
end.
● MD20152 $MC_GCODE_RESET_MODE[ ] (RESET response of G groups)
● MD20150 $MC_GCODE_RESET_VALUES (RESET position of G groups)
Frame states after channel reset / part program end
Frame Status after channel reset / part program end

$P_IFRAME settable frame Is retained, depending on:
● MD20110 $MC_RESET_MODE_MASK
Basic functions
3.5 Frames
Frame Status after channel reset / part program end

$P_GFRAME grinding frame Is retained, depending on:
● MD20110 $MC_RESET_MODE_MASK
$P_ACTBFRAME complete basic Is retained, depending on:
frame ● MD20110 $MC_RESET_MODE_MASK bit 0 and bit 14
● MD10613 $MN_NCBFRAME_RESET_MASK
● MD24002 $MC_CHBFRAME_RESET_MASK
System frames: Are retained, depending on:
$P_PARTFRAME, $P_SETFRAME, ● MD24006 $MC_CHSFRAME_RESET_MASK
$P_ISO1FRAME, $P_ISO2FRAME, ● MD20150 $MC_GCODE_RESET_VALUES[<n>]
$P_ISO3FRAME, $P_TOOLFRAME,
$P_WPFRAME, $P_TRAFRAME,
$P_ISO4FRAME, $P_RELFRAME,
$P_CACFRAME
$P_EXTFRAME external work offset Retained
DRF offset Retained
Deletion of system frames

The system frames in the data management can be deleted for channel reset / part program
end with the following machine data:
MD24007 $MC_CHSFRAME_RESET_CLEAR_MASK, bit<n> = <value>
Bit Value Meaning

0 1 System frame for actual value setting and scratching is deleted for channel reset /
part program end.
1 1 System frame for external work offset is deleted for channel reset / part program
end.
2 --- Reserved, for TCARR and PAROT see MD20150 $MC_GCODE_RESET_VAL‐
UES[ ].
3 --- Reserved, for TOROT and TOFRAME see MD20150 $MC_GCODE_RESET_VAL‐
UES[ ].
4 1 System frame for workpiece reference points is deleted for channel reset / part
program end.
5 1 System frame for cycles is deleted for channel reset / part program end.
6 --- Reserved, RESET response depends on MD20110 $MC_RESET_MODE_MASK.
7 1 System frame $P_ISO1FR is deleted for channel reset / part program end.
11 1 System frame $P_RELFR is deleted for channel reset / part program end.
For bit<n> = 0, the associated system frame is not deleted.
Basic functions
3.5 Frames
3.5.12.4 Part program start
Frame conditions after part program start
Frame Condition after part program start

$P_IFRAME settable frame Is retained depending on:
$P_GFRAME grinding frame Is retained depending on:
$P_ACTBFRAME complete basic frame Retained
System frames: Retained
$P_PARTFRAME, $P_SETFRAME,
$P_ISO1FRAME, $P_ISO2FRAME,
$P_ISO3FRAME, $P_TOOLFRAME,
$P_WPFRAME, $P_TRAFRAME,
$P_ISO4FRAME, $P_RELFRAME,
$P_CACFRAME
$P_EXTFRAME external work offset Retained
DRF offset Retained
3.5.12.5 Block search

Data management frames are also modified when carrying out a block search with calculation.
Cancellation of block search

If a block search is aborted with channel reset, then the following machine data can be used to
set that all data management frames are reset to the value they had before the block search:
MD28560 $MC_MM_SEARCH_RUN_RESTORE_MODE, bit<n>
Bit Value Meaning

0 1 All frames in the data management are restored.
In case of cascaded block searches, the frames are set to the status of the previous block
search.
SERUPRO
The "SERUPRO" function is not supported.
3.5.12.6 REPOS
There is no special treatment for frames. If a frame is modified in an ASUB, it is retained in the
program. On repositioning with REPOS, a modified frame is included, provided the modification
was activated in the ASUB.
Basic functions
3.6 Workpiece-related actual-value system
3.6.1 Overview
Definition
The term "workpiece-related actual-value system" designates a series of functions that permit
the user:
● To use a workpiece coordinate system defined in machine data after powerup.
Features:
– No additional operations are necessary.
– Effective in JOG and AUTOMATIC modes
● To retain the valid settings for the following after end of program for the next part program:
– Active plane
– Settable frame (G54-G57)
– Kinematic transformation
– Active tool offset
● To change between work coordinate system and machine coordinate system via the user
interface.
● To change the work coordinate system by operator action (e.g., changing the settable frame
or the tool offset).
3.6.2 Use of the workpiece-related actual value system
Requirements, basic settings

The settings described in the previous Section have been made for the system.
The predefined setting after power-up of the HMI software is MCS.
Switchover to WCS
The change to the WCS via the user interface causes the axis positions relative to the origin of
the WCS to be displayed.
Switchover to MCS
The change to the MCS via the user interface causes the axis positions relative to the origin of
the MCS to be displayed.
Basic functions
Interrelationships between coordinate systems

The figure below shows the interrelationships between the machine coordinate system (MCS)
and the workpiece coordinate system (WCS).
)UDPHFKDLQ
:&6
)UDPHIRUF\FOHVSURJUDPPDEOH
IUDPHWUDQVIRUPDWLRQV
6=6
6\VWHPIUDPHIRU72527
72)5$0(ZRUNSLHFHV
**VHWWDEOHIUDPH
FKDQQHOVSHFRU1&8JOREDO
%=6
&KDLQHGILHOGRIEDVLFIUDPHV
FKDQQHOVSHFDQGRU1&8JOREDO
&KDLQHGV\VWHPIUDPHVIRU3$527VHWDFWXDO
YDOXHVFUDWFKLQJH[WZRUNRIIVHW
+DQGZKHHO'5)PRYHPHQWRYHUODLGPRYHPHQW

H[WHUQDOZRUNRIIVHW %&6
.LQHPDWLFVWUDQVIRUPDWLRQ
0&6
0&6 PDFKLQHFRRUGLQDWHV\VWHP
%&6 EDVLFFRRUGLQDWHV\VWHP
:&6 ZRUNSLHFHFRRUGLQDWHV\VWHP
%=6 EDVLF]HURV\VWHP
6=6 VHWWDEOH]HURV\VWHP
Figure 3-29 Interrelationship between coordinate systems
For further information, see "Auxiliary function outputs to PLC (Page 611)" and Function
Manual Tools under Tool offset.
Further information
● NC Programming Programming Manual
● Function Manual Transformations, Kinematics transformation
Basic functions
● Function Manual Axes and Spindles; Axis couplings

● Function Manual Technologies; Tangential control
3.6.3 Special reactions
Overstore
Overstoring in RESET state of:
● Frames (zero offsets)
● Active plane
● Activated transformation
● Tool offset
immediately affects the actual-value display of all axes in the channel.
Entry via operator panel front

If operations on the operator panel are used to change the values for
"Active frame" (zero offsets, "Parameters" operating area)
and
"Active tool length compensation" ("Parameters" operating area)
, one of the following actions is used to activate these changes in the display:
● Press the RESET key.
● Reselect:
– Zero offset by the part program
– Tool offset by the part program
● Reset:
– Zero offset by overstoring
– Tool offset by overstoring
MD9440
If the HMI machine data
MD9440 ACTIVATE_SEL_USER_DATA
for the operator panel front is set, the entered values become active immediately in RESET
state.
When values are entered in the part-program execution stop state, they become effective when
program execution continues.
Basic functions
Actual-value reading
If the actual value of $AA_IW is read in the WCS after activation of a frame (zero offset) or a tool
offset, the activated changes are already contained in the result read even if the axes have not
yet been traversed with the activated changes.
The actual values in the settable zero system (SZS) can be read from the part program for each
axis using the variable $AA_IEN[axis].
The actual values in the basic zero system (BZS) can be read from the part program for each
axis using the variable $AA_IBN[axis].
Actual-value display
The programmed contour is always displayed in the WCS.
The following offsets are added to the MCS:
● Kinematic transformation
● DRF offset/zero offset external
● Active frame
● Active tool offset of the current tool
Switchover by PLC
The actual values can be displayed in the WCS, SZS, BZS or MCS via the PLC. The PLC can
define, which coordinate system corresponds to the workpiece coordinate system on a
machine.
On MMC power-up the MCS is preset.
With the signal DB19 DBB0.7 "MCS/WCS switchover", it is also possible to switch from the PLC
to the WCS.
Transfer to PLC
Depending on machine data
MD20110 / MD20112, bit 1
, the auxiliary functions (D, T, M) are output to the PLC (or not) on selection of the tool length
compensation.
Note
If the WCS is selected from the PLC, an operator action can still be used to switch between the
WCS and MCS for the relevant mode.
However, when the mode and or area is changed, the WCS selected by the PLC is evaluated
and activated (see Section "Mode group, channel, program operation, reset response
(Page 29)").
Basic functions
3.8 Examples
3.7 Boundary conditions

There are no supplementary conditions to note.
3.8 Examples
3.8.1 Axes
Axis configuration for a 3axis milling machine with rotary table
1. Machine axis: X1 Linear axis

2. Machine axis: Y1 Linear axis
3. Machine axis: Z1 Linear axis
4. Machine axis: B1 Rotary table (for turning for multiface machining)
5. Machine axis: W1 Rotary axis for tool magazine (tool revolver)
6. Machine axis: C1 (Spindle)
1. Geometry axis: X (1. channel)

2. Geometry axis: Y (1. channel)
3. Geometry axis: Z (1. channel)
1. Special axis: B (1. channel)
2. Special axis: WZM (1. channel)
1. spindle: S1/C (1. channel)
Basic functions
3.8 Examples
:=0
<
6&
%
Parameterization of the machine data
Machine data Value

MD10000 AXCONF_MACHAX_NAME_TAB[0] = X1
MD10000 AXCONF_MACHAX_NAME_TAB[1] = Y1
MD10000 AXCONF_MACHAX_NAME_TAB[2] = Z1
MD10000 AXCONF_MACHAX_NAME_TAB[3] = B1
MD10000 AXCONF_MACHAX_NAME_TAB[4] = W1
MD10000 AXCONF_MACHAX_NAME_TAB[5] = C1
MD20050 AXCONF_GEOAX_ASSIGN_TAB[0] =1
MD20060 AXCONF_GEOAX_NAME_TAB[0] =X
MD20060 AXCONF_GEOAX_NAME_TAB[1] =Y
MD20060 AXCONF_GEOAX_NAME_TAB[2] =Z
MD20070 AXCONF_MACHAX_USED[0] =1
Basic functions
3.8 Examples
Machine data Value

MD20080 AXCONF_CHANAX_NAME_TAB[0] =X
MD20080 AXCONF_CHANAX_NAME_TAB[1] =Y
MD20080 AXCONF_CHANAX_NAME_TAB[2] =Z
MD20080 AXCONF_CHANAX_NAME_TAB[3] =B
MD20080 AXCONF_CHANAX_NAME_TAB[4] = WZM
MD20080 AXCONF_CHANAX_NAME_TAB[5] = S1
MD30300 IS_ROT_AX[3] =1
MD30300 IS_ROT_AX[4] =1
MD30300 IS_ROT_AX[5] =1
MD30310 ROT_IS_MODULO[3] =1
MD30320 DISPLAY_IS_MODULO[3] =1
MD30320 DISPLAY_IS_MODULO[4] =1
MD20090 SPIND_DEF_MASTER_SPIND =1
MD35000 SPIND_ASSIGN_TO_MACHAX[AX1] =0
3.8.2 Coordinate systems
Configuration of a global basic frame

An NC with two channels is required. The following applies:
● Both channels can then write the global basic frame.
● The other channel recognizes the change when the global basic frame is activated again.
● Both channels can read the global basic frame.
● Both channels can activate the global basic frame independently.
Basic functions
3.8 Examples
Machine data
Machine data Value

MD10000 $MN_AXCONF_MACHAX_NAME_TAB[0] = X1
MD18602 $MN_MM_NUM_GLOBAL_BASE_FRAMES =1
MD28081 $MC_MM_NUM_BASE_FRAMES =1
Machine data for channel 1 Value Machine data for channel 1 Value
$MC_AXCONF_CHANAX_NAME_TAB[0] =X $MC_AXCONF_CHANAX_NAME_TAB[0] =X
$MC_AXCONF_CHANAX_NAME_TAB[1] =Y $MC_AXCONF_CHANAX_NAME_TAB[1] =Y
$MC_AXCONF_CHANAX_NAME_TAB[2] =Z $MC_AXCONF_CHANAX_NAME_TAB[2] =Z
$MC_AXCONF_MACHAX_USED[0] =1 $MC_AXCONF_MACHAX_USED[0] =4
$MC_AXCONF_GEOAX_NAME_TAB[0] =X $MC_AXCONF_GEOAX_NAME_TAB[0] =X
$MC_AXCONF_GEOAX_NAME_TAB[1] =Y $MC_AXCONF_GEOAX_NAME_TAB[1] =Y
$MC_AXCONF_GEOAX_NAME_TAB[2] =Z $MC_AXCONF_GEOAX_NAME_TAB[2] =Z
$MC_AXCONF_GEOAX_ASSIGN_TAB[0] =1 $MC_AXCONF_GEOAX_ASSIGN_TAB[0] =4
Part program in the 1st channel

Code (excerpt) ; Comment
. . .
N100 $P_NCBFR[0] = CTRANS( x, 10 ) ; Activation of the NC-global basic frame
. . .
N130 $P_NCBFRAME[0] = CROT(X, 45) ; Activation of the NC-global basic frame with rotation =>
; Alarm 18310, because rotations are not permitted for
; NC-global frames
. . .
Part program in the 2nd channel

. . .
N100 $P_NCBFR[0] = CTRANS( x, 10 ) ; The NC-global basic frame is also effective in the 2nd
channel
. . .
Basic functions
3.8 Examples

N510 G500 X10 ; Activate basic frame
N520 $P_CHBFRAME[0] = CTRANS( x, 10 ) ; Current frame of the 2nd channel is activated with an off-
set
. . .
3.8.3 Frames
Example 1
The channel axis is to be switched to a geometry axis by means of a geometry axis interchange.
The intention of the interchange is to give the programmable frame a translation component of
10 in the X axis.
The current settable frame is to be retained:
FRAME_GEOAX_CHANGE_MODE = 1

$P_UIFR[1] = CROT(X,10,Y,20,Z,30) ; Frame is retained after geometry axis interchange.
G54 ; Settable frame becomes active.
TRANS A10 ; Axis-specific offset of A is also interchanged.
GEOAX(1,A) ; A becomes the X axis
; $P_ACTFRAME = CROT(X,10,Y,20,Z,30) : CTRANS(X10)
Multiple channel axes can become geometry axes at the same time on a transformation
change.
Example 2
Channel axes 4, 5 and 6 become the geometry axes of a 5axis orientation transformation. The
geometry axes are thus all substituted before the transformation.
The current frames are changed when the transformation is activated.
The axis-specific frame components of the channel axes that become geometry axes are used
in the calculation of the new WCS. Rotations programmed before the transformation are
retained. The old WCS is restored when the transformation is deactivated.
The most common application is probably that the geometry axes do not change before and
after the transformation and that the frames are to stay as they were before the transformation.
Machine data:
$MN_FRAME_GEOAX_CHANGE_MODE = 1
$MC_AXCONF_CHANAX_NAME_TAB [0] = "CAX"

$MC_AXCONF_CHANAX_NAME_TAB [1] = "CAY"
$MC_AXCONF_CHANAX_NAME_TAB [2] = "CAZ"
Basic functions
3.8 Examples
$MC_AXCONF_CHANAX_NAME_TAB [3] = "A"

$MC_AXCONF_CHANAX_NAME_TAB [4] = "B"
$MC_AXCONF_CHANAX_NAME_TAB [5] = "C"
$MC_AXCONF_GEOAX_ASSIGN_TAB [0] = 1
$MC_AXCONF_GEOAX_NAME_TAB [0] = "X"

$MC_AXCONF_GEOAX_NAME_TAB [1] = "Y"
$MC_AXCONF_GEOAX_NAME_TAB [2] = "Z"
$MC_TRAFO_GEOAX_ASSIGN_TAB_1 [0] = 4
$MC_TRAFO_AXES_IN_1 [0] = 4
Program:

$P_NCBFRAME[0] = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6)
$P_CHBFRAME[0] = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6)
$P_IFRAME = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6) : CROT(Z,45)
$P_PFRAME = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6) : CROT(X,10,Y,20,Z,30)
TRAORI ; Transformation sets GEOAX(4,5,6)
; $P_NCBFRAME[0] = CTRANS(X,4,Y,5,Z,6,CAX,1,CAY,2,CAZ,3)
; $P_ACTBFRAME = CTRANS(X,8,Y,10,Z,12,CAX,2,CAY,4,CAZ,6)
; $P_PFRAME = CTRANS(X,4,Y,5,Z,6,CAX,1,CAY,2,CAZ,3) : CROT(X,10,Y,20,Z,30)
; $P_IFRAME = CTRANS(X,4,Y,5,Z,6,CAX,1,CAY,2,CAZ,3) : CROT(Z,45)
TRAFOOF ; Deactivating transformation sets GEOAX (1,2,3)
; $P_NCBFRAME[0] = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6)
; $P_CHBFRAME[0] = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6)
; $P_IFRAME = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6) : CROT(Z,45)
; $P_PFRAME = CTRANS(X,1,Y,2,Z,3,A,4,B,5,C,6) : CROT(X,10,Y,20,Z,30)
Basic functions
3.9 Data lists
3.9 Data lists
3.9.1 Machine data
3.9.1.1 Displaying machine data

SINUMERIK Operate
9242 MA_STAT_DISPLAY_BASE Numerical basis for display of moving
joint STAT
9243 MA_TU_DISPLAY_BASE Numerical basis for display of rotary
axis position TU
9244 MA_ORIAXES_EULER_ANGLE_NAME Display of orientation axes as Euler an‐
gle
9245 MA_PRESET_FRAMEIDX Value storage scratching and PRESET
9247 USER_CLASS_BASE_ZERO_OFF_PA Availability of basic offset in "Parame‐
ters" operating area
9248 USER_CLASS_BASE_ZERO_OFF_MA Availability of basic offset in Machine
operating area
9424 MA_COORDINATE_SYSTEM Coordinate system for actualvalue dis‐
play
9440 ACTIVE_SEL_USER_DATA Active data (frames) are immediately
operative after editing
9449 WRITE_TOA_LIMIT_MASK Applicability of MD9203 to edge data
and locationdependent offsets
9450 MM_WRITE_TOA_FINE_LIMIT Limit value for wear fine
9451 MM_WRITE_ZOA_FINE_LIMIT Limit value for offset fine
3.9.1.2 NC-specific machine data

10000 AXCONF_MACHAX_NAME_TAB Machine axis name
10600 FRAME_ANGLE_INPUT_MODE Sequence of rotation in the frame
10602 FRAME_GEOAX_CHANGE_MODE Frames and switchover of geometry axes
10610 MIRROR_REF_AX Reference axis for mirroring
10612 MIRROR_TOGGLE Change over mirror
10613 NCBFRAME_RESET_MASK ActiveNCU-global basic frame after reset
10615 NCBFRAME_POWERON_MASK Reset global basic frames after Power On
10617 FRAME_SAVE_MASK Behavior of frames for SAVE subprograms
10650 IPO_PARAM_NAME_TAB Name of interpolation parameters
10660 INTERMEDIATE_POINT_NAME_TAB Name of intermediate point coordinates for G2/G3
Basic functions
3.9 Data lists

11640 ENABLE_CHAN_AX_GAP Channel axis gaps are allowed
18600 MM_FRAME_FINE_TRANS Fine offset for FRAME (SRAM)
18601 MM_NUM_GLOBAL_USER_FRAMES Number of globally predefined user frames (SRAM)
18602 MM_NUM_GLOBAL_BASE_FRAMES Number of global basic frames (SRAM)

20050 AXCONF_GEOAX_ASSIGN_TAB Assignment geometry axis to channel axis
20060 AXCONF_GEOAX_NAME_TAB Geometry axis name in channel
20080 AXCONF_CHANAX_NAME_TAB Channel axis name in the channel
20110 RESET_MODE_MASK Definition of basic control settings after RESET / TP end
20118 GEOAX_CHANGE_RESET Allow automatic geometry axis change
20126 TOOL_CARRIER_RESET_VALUE Active toolholder on RESET
20140 TRAFO_RESET_VALUE Transformation record on power-up (RESET / TP-End)
20150 GCODE_RESET_VALUES Initial setting of the G groups
20152 GCODE_RESET_MODE RESET response of the G groups
20184 TOCARR_BASE_FRAME_NUMBER Number of the basic frame for pickup of the table offset
21015 INVOLUTE_RADIUS_DELTA End point monitoring for evolvents (involutes)
22532 GEOAX_CHANGE_M_CODE M code for replacement of geometry axes
22534 TRAFO_CHANGE_M_CODE M code for transformation change
24000 FRAME_ADD_COMPONENTS Frame components for G58 and G59
24002 CHBFRAME_RESET_MASK RESET response of channel-specific basic frames
24004 CHBFRAME_POWERON_MASK Reset channel-specific basic frames after Power On
24006 CHSFRAME_RESET_MASK Active system frames after reset
24007 CHSFRAME_RESET_CLEAR_MASK Clear system frames on RESET
24008 CHSFRAME_POWERON_MASK Reset system frames after POWER ON
24010 PFRAME_RESET_MODE RESET mode for programmable frame
24020 FRAME_SUPPRESS_MODE Positions for frame suppression
24030 FRAME_ACT_SET SZS coordinate system setting
24040 FRAME_ADAPT_MODE Adapting active frames
24050 FRAME_SAA_MODE Saving and activating data management frames
24805 TRACYL_ROT_AX_FRAME_1 Rotary axis offset TRACYL 1
24855 TRACYL_ROT_AX_FRAME_2 Rotary axis offset TRACYL 2
24905 TRANSMIT_ROT_AX_FRAME_1 Rotary axis offset TRANSMIT1
24955 TRANSMIT_ROT_AX_FRAME_2 Rotary axis offset TRANSMIT2
28081 MM_NUM_BASE_FRAMES Number of basic frames
Basic functions
3.9 Data lists

28082 MM_SYSTEM_FRAME_FRAMES System frames (SRAM)
28560 MM_SEARCH_RUN_RESTORE_MODE Restore data after a simulation

32074 FRAME_OR_CORRPOS_NOTALLOWED FRAME or HL offset is not permitted
35000 SPIND_ASSIGN_TO_MACHAX Assignment spindle to machine axis
3.9.2 Setting data
Number Identifier: $SC_ Description

42440 FRAME_OFFSET_INCR_PROG Work offsets in frames
42980 TOFRAME_MODE Frame definition for TOFRAME, TOROT and PAROT
3.9.3 System variables
Identifier Description
$AA_ETRANS[axis] External work offset
$AA_IBN[axis] Actual value in basic zero coordinate system (BZS)
$AA_IEN[axis] Actual value in settable zero point coordinate system (SZS)
$AA_OFF[axis] Overlaid motion for programmed axis
$AC_DRF[axis] Handwheel override of an axis
$AC_JOG_COORD Coordinate system for manual traversing
$P_ACSFRAME Active frame between BCS and SZS
$P_ACTBFRAME Active complete basic frame
$P_ACTFRAME Active complete frame
$P_BFRAME 1st active basic frame. Corresponds to $P_CHBFRAME[0]
$P_CHBFR[<n>] Data management frame: Basic frame can be activated via G500, G54...G599
$P_CHBFRAME[<n>] Active basic frame
$P_CHBFRMASK Basic frame mask in the channel
$P_CHSFRMASK System frame mask
$P_CYCFR Data management frame: System frame for cycles
Basic functions
3.9 Data lists
$P_CYCFRAME Active system frame for cycles
$P_EXTFR Data management frame: System frame for work offset external
$P_EXTFRAME Active system frame for external work offset
$P_IFRAME Active settable frame
$P_ISO1FR Data management frame: System frame for ISO G51.1 mirroring
$P_ISO2FR Data management frame: System frame for ISO G68 2DROT
$P_ISO3FR Data management frame: System frame for ISO G68 3DROT
$P_ISO4FR Data management frame: System frame for ISO G51 Scale
$P_ISO1FRAME Active system frame for ISO G51.1 Mirroring
$P_ISO2FRAME Active system frame for ISO G68 2DROT
$P_ISO3FRAME Active system frame for ISO G68 3DROT
$P_ISO4FRAME Active system frame for ISO G51 Scale
$P_NCBFR[n] Data management frame: NCU-global basic frame in the data management,
can be activated via G500, G54...G599
$P_NCBFRAME[n] Active NCU-global basic frame
$P_NCBFRMASK Global basic frame mask
$P_PARTFR Data management frame: System frame for TCARR and PAROT
$P_PARTFRAME Active system frame for TCARR and PAROT with orientable toolholder
$P_PFRAME Active programmable frame
$P_SETFR Data management frame: System frame for actual value setting
$P_SETFRAME Active system frame for actual value setting
$P_TOOLFR Data management frame: System frame for TOROT and TOFRAME
$P_TOOLFRAME Active system frame for TOROT and TOFRAME
$P_TRAFRAME Data management frame: System frame for transformations
$P_TRAFRAME Active system frame for transformations
$P_UBFR 1st basic frame in the channel in the data management that is activated af‐
ter G500, G54...G599. Corresponds to $P_CHBFR[0].
$P_UIFR[n] Data management frame: Settable frame, can be activated via G500, G54
to G599
$P_UIFRNUM Number of active settable frame
$P_WPFR Data management frame: System frame for the workpiece
$P_WPFRAME Active system frame for the workpiece
Basic functions
3.9 Data lists
Basic functions
Kinematic chain 4
4.1 Function description
4.1.1 Characteristics
This section describes how the kinematic structure of a machine can be mapped using a
kinematic chain and parameterized in the control using system variables for NC functions such
as "collision avoidance" or "kinematic transformation".
The system variables are retentively saved in the NC and can be archived and/or read as "NC
data" via SINUMERIK Operate using the commissioning archive.
For functions such as "collision avoidance", which also require a description of the machine
geometry, see Function Manual Monitoring and Compensating, Section Geometric machine
modeling.
Note
Graphical editor
As an alternative to writing the system variables in a part program, the machine can be modeled
from the SINUMERIK Operate user interface:
Operating area: "Commissioning" > "NC" > "Machine model"
Changes to the machine model
The direct changes to the machine model at the system variables only become visible at the
user interface after explicitly requesting that the machine model is recalculated by calling the
PROTA() or PROTS() function.
Changes to the machine model made at the user interface are immediately accepted in the
system variables of the NC. The changes only become active after explicitly requesting that the
machine model is recalculated by calling the PROTA() or PROTS() function.
Kinematic structure
The kinematic structure of a machine comprises the following:
● Number and type of the machine axes: Linear or rotary axes
● Arrangement of the machine axes: Position and orientation
● Dependencies of the machine axes to one another: Which machine axis traverses with
which other machine axis.
Basic functions
Kinematic chain
Kinematic chain
A kinematic structure of a machine is described using a kinematic chain with the following
properties:
● A kinematic chain consists of an arbitrary number of interconnected elements.
● Parallel subchains can branch off from a kinematic chain.
● Only one active kinematic chain is available in the control.
● The active kinematic chain starts with the root element.
● Parameterized elements or subchains that are not connected to the root element or whose
connection points toward the root element, are not part of the currently active kinematic
chain.
● A kinematic chain is defined in the spatially fixed coordinates of the world coordinate system.
3DUDOOHOH7HLONHWWH
3DUDOOHOH7HLONHWWH
5RRW(OHPHQW
$QIDQJGHUZLUNVDPHQNLQHPDWLVFKHQ.HWWH
Figure 4-1 Example of a kinematic chain
Element
An element of a kinematic chain basically describes the transformation with which the local
coordinate system of the previous element is mapped in the local coordinate system of the
current element:
Kn-1 ⇒ Tn ⇒ Kn
(OHPHQW (OHPHQW
H Q HQ
< Q <Q

7Q .[/RFDOHOHPHQWFRRUGLQDWHV\VWHPV
. Q; Q .Q ; Q
7UDQVIRUPDWLRQV
< Q
7Q 7Q&RQVWDQWRIIVHWLQWKH;<GLUHFWLRQ
7Q&KDQJHDEOHRIIVHWLQWKH;GLUHFWLRQWKURXJKOLQHDUD[LV
. Q ; Q
Figure 4-2 Local element coordinate systems
The following constant transformations are possible:

● Offset (type: OFFSET (Page 431))
● Rotation (type: ROT_CONST (Page 429))
Basic functions
Kinematic chain
The following changing transformations, based on the current position values of the machine
axis assigned to the element (linear axis / rotary axis), are possible:
● Offset (type: AXIS_LIN (Page 423))
● Rotation (type: AXIS_ROT (Page 426))
A position or orientation change in an element, e.g. through a position change of the associated
machine axis, affects all the following elements of the chain or parallel subchains.
The maximum number of possible elements can be parameterized using machine data
(Page 417).
Parallel subchains
If a parallel subchain branches off from an element en, then for the kinematics, the branch is
always before the element. For this reason, a change in element en, e.g. a position change of
the associated machine axis, does not affect the subchain branch.
HO H O
HN H N
H Q HQ H Q H Q
HP HP
Figure 4-3 Parallel subchains branching off from elements en and en+2
Switch
A switch is a special element that is not kinematically active (type: SWITCH (Page 433)) in a
kinematic chain, which can assume the CLOSED and OPEN states.
In the OPEN state, the connection from the previous to the following element is interrupted.
HN
1.B3$5$//(/
V[
1.B1(;7
H Q HQ
[\
Figure 4-4 OPEN state
In the CLOSED state, the previous element is connected to the following element.
Basic functions
Kinematic chain
HN
1.B3$5$//(/
V[
1.B1(;7
H Q HQ
[\
Figure 4-5 CLOSED state
The switch does not influence the connection to a parallel element.

The maximum number of possible switches can be parameterized usingmachine data
(Page 417).
Note
Local coordinate system
The local coordinate system of a switch is not rotated with respect to the world coordinate
system.
World coordinate system

In order to uniquely describe the kinematic stricture of a machine, all elements of the kinematic
chain - as well as the orientation and offset vectors of the machine axes and the constant
rotation/offsets - are referred to the world coordinate system.
Elements with linear axes do not change the orientation of the following elements. The
orientation and offset vectors of the following elements can therefore refer to the world
coordinate system without further supplementary conditions.
(OHPHQW (OHPHQW (OHPHQW
H H H
<
.
;
.:RUOGFRRUGLQDWHV\VWHP
7 ./RFDOHOHPHQWFRRUGLQDWHV\VWHPV
< <
. 7 .
7UDQVIRUPDWLRQV
; ; 7&RQVWDQWRIIVHWLQWKH;<GLUHFWLRQ
7
7&KDQJHDEOHRIIVHWLQWKH;GLUHFWLRQWKURXJKOLQHDUD[LV
< 7&KDQJHDEOHRIIVHWLQWKH<GLUHFWLRQWKURXJKOLQHDUD[LV
. ;
Elements with rotary axes change the orientation of the following elements. This is the reason
that the orientation and offset vectors of the following elements, for a defined initial position of
the previous orientation changing elements, must be referred to the world coordinate system.
Basic functions
Kinematic chain
4.2 Commissioning
(OHPHQW (OHPHQW (OHPHQW (OHPHQW
H H H H
<
.
;
.:RUOGFRRUGLQDWHV\VWHP
.ORFDOHOHPHQWFRRUGLQDWHV\VWHPV
7
<
< . 7UDQVIRUPDWLRQV
. 7 7FRQVWDQWRIIVHWLQWKH;<GLUHFWLRQ
; 7FKDQJLQJRIIVHWLQWKH;GLUHFWLRQZLWKDOLQHDUD[LV
;
7 7FKDQJLQJURWDWLRQDURXQGWKH=ZLWKDURWDU\D[LV
< 7 7FKDQJLQJRIIVHWLQWKH<GLUHFWLRQZLWKDOLQHDUD[LV
,QLWLDOSRVLWLRQ7URWDU\D[LVGHJUHH
. ;
The origin and orientation of the world coordinate system can be freely selected in chain
elements that are defined before the root element. For the active coordinate system after the
root element, the following conditions must be met:
● Origin of the world coordinate system at the machine zero point
● Orientation of the world coordinate system so that the coordinate axes are arranged in the
positive traversing direction of the machine linear main axes
Direction vectors
Within a kinematic chain, the direction vectors, which are used to specify the alignment of the
machine axes, are always specified in absolute terms, i.e. referred to the world coordinate
system.
See also
Machine data (Page 417)
4.2 Commissioning
4.2.1 General
4.2.1.1 Overview
The commissioning of the "Kinematic chain" function is performed using:
● Machine data
– Specification of the quantity structure
– Specification of the first element in the kinematic chain
● System variables
– Specification of the kinematic properties of an element
– Connection of the element to the kinematic chain
Basic functions
Kinematic chain
4.2 Commissioning
4.2.1.2 Structure of the system variables

The system variables are structured according to the following scheme:
● $NK_<Name>[<Index_1>]
● $NK_<Name>[<Index_1>, <Index_2>]
General
The system variables to describe the elements of kinematic chains have the following
properties:
● The prefix for all system variables of the kinematic chain is $NK_, (N for NC, K for kinematic).
● The system variables can be read and written via NC programs.
● The system variables can be stored in archives and loaded to the NC again.
Data type
STRING
All system variables of the STRING data type have the following properties:
● Maximum string length: 31 characters
● No distinction is made between upper and lower case
Example: "Axis1" is identical to "AXIS1"
● Spaces and special characters are permitted
Example: "Axis1" is not identical to "Axis 1"
● Names that start with two underscores "__" are reserved for system purposes and must not
be used for user-defined names.
Note
Leading space
Since spaces are valid and distinct characters, names that start with a space followed by two
underscores "__" can, in principle, be used for user-defined names. However, because they
can be easily mistaken for system names, this procedure is not recommended.
Index_1
The individual elements are addressed via index_1. Index 0 → 1. Element, index 1 → 2.
Element, ... n → (n+1) element, with n = ($MN_MM_MAXNUM_KIN_CHAIN_ELEM - 1)
All system variables of an element have the same index.
Basic functions
Kinematic chain
4.2 Commissioning
Index_2
For system variables that contain a vector, the coordinates of the vector are addressed via
index_2.
● 0 → X axis
● 1 → Y axis
● 2 → Z axis
4.2.2 Machine data
4.2.2.1 Maximum number of elements

The maximum number of elements for kinematic chains is set using machine data.
MD18880 $MN_MM_MAXNUM_KIN_CHAIN_ELEM = <number>
4.2.2.2 Root element

The following machine data is used to specify the root element, i.e. the first element of the
currently active kinematic chain.
MD16800 $MN_ROOT_KIN_ELEM_NAME = "<element_name>"
All parameterized elements and subchains that are connected to the root element in such a way
that the connection starts at the root element, are part of the currently active kinematic chain.
Parameterized elements or subchains that are not connected to the root element or whose
connection points towards the root element, are not part of the currently active kinematic chain.
3DUDPHWHUL]HGHOHPHQWVDQGVXEFKDLQVWKDWDUHQRW (OHPHQWVDQGVXEFKDLQVRIWKHDFWLYHNLQHPDWLF
SDUWRIWKHDFWLYHNLQHPDWLFFKDLQ FKDLQ
0'01B5227B.,1B(/(0B1$0(
4.2.2.3 Maximum number of switches

The maximum number of switches for kinematic chains is set with the machine data
MD18882 $MN_MM_MAXNUM_KIN_SWITCHES = <number>
Basic functions
Kinematic chain
4.2 Commissioning
4.2.3.1 Overview
System variables independent of any element

$NK_SWITCH Switch variable to open and close the switch
Element-specific system variables

Element-specific system variables are subdivided into variables that are independent of the
type and dependent on the type:
● Variables independent of the type

$NK_NAME Name of the current element en
$NK_NEXT Name of the next element en+1
$NK_PARALLEL Name of a branching parallel element ep before the current element
en
$NK_TYPE Type of the element
● Variables dependent on the type

$NK_OFF_DIR Offset or direction vector
$NK_AXIS Machine axis or object name
$NK_A_OFF Work offset for linear axis or rotary axis
$NK_SWITCH_INDEX Switch index
$NK_SWITCH_POS Switch position "CLOSED"
For the following types, variables dependent on the type are evaluated:
System variable Type

OFFSET AXIS_LIN AXIS_ROT ROT_CON SWITCH
ST
$NK_OFF_DIR x x x x -
$NK_AXIS - x x - -
$NK_A_OFF - x x x -
$NK_SWITCH_INDEX - - - - x
$NK_SWITCH_POS - - - - x
Basic functions
Kinematic chain
4.2 Commissioning
The system variables are described in detail in the following sections.
Note
Establish a defined initial state
It is recommended that a defined initial state be generated before parameterizing the kinematic
chain. To do this, the system variables of the kinematic chain should be set to their default value
using function DELOBJ().
Change system variable values
If the value of one of the system variables listed above is changed, then the change becomes
immediately visible on the user interface, e.g. SINUMERIK Operate. The machine model of the
NC is only updated after explicitly requesting that the machine model is recalculated by calling
the PROTA() or PROTS() function.
See also
Deletion of components (DELOBJ) (Page 436)
4.2.3.2 $NK_NAME
Function
Enter the NC-wide unique element name in the system variable. The element is referenced via
this name, e.g. within kinematic chains. The name is also displayed in the graphical editor of
SINUMERIK Operate.
Syntax
$NK_NAME[<n>] = "<name>"
Meaning
$NK_NAME: Name of the element

Data type: STRING
Default value: "" (empty string)
<n>: System variable or element index
Data type: INT
Range of values: 0, 1, 2, ... ($MN_MM_MAXNUM_KIN_CHAIN_ELEM - 1)
<name>: Element name, max. string length: 31 characters
Data type: STRING
Basic functions
Kinematic chain
4.2 Commissioning
Example
The 9th kinematic element is assigned the name "B axis":

N100 $NK_NAME[8] = "B axis" ; 9th kin. element,
; name = "B axis"
4.2.3.3 $NK_NEXT
Function
If the element is part of a kinematic chain, the name of the following element should be entered
in the system variable.
Syntax
$NK_NEXT[<n>] = "<name>"
Meaning
NK_NEXT: Name of the following element

Data type: STRING
Range of values: All names contained in $NK_NAME (Page 419)
Default value: "" "" (empty string)
Data type: INT
Data type: STRING
Example
The 9th kinematic element does not have a following element:

N100 $NK_NEXT[8] = "" ; 9. kin. element,
; following element = ""
Basic functions
Kinematic chain
4.2 Commissioning
4.2.3.4 $NK_PARALLEL
Function
The name of the element that branches off before the current element should be entered in the
system variable. The branching element is parallel to the current element. Changes to the
current element, e.g. position changes of the assigned machine axis, have no effect on the
parallel element.
Syntax
$NK_PARALLEL[<n>] = "<name>"
Meaning
$NK_PARALLEL: Name of the parallel element

Data type: STRING
Range of values: All names contained in $NK_NAME (Page 419)
Default value: "" "" (empty string)
Data type: INT
Data type: STRING
Example
The "Offset to the rotary table" element is arranged parallel to the 9th kinematic element:

N100 $NK_PARALLEL[8] = "Offset to the rotary ; Parallel to the 9th kin. element,
table" ; name = "Offset to the rotary table"
Basic functions
Kinematic chain
4.2 Commissioning
4.2.3.5 $NK_TYPE
Function
The element type should be entered in the system variable:
Type Description
AXIS_LIN The element describes a linear machine axis (linear axis) with direction vector
(Page 423) $NK_OFF_DIR and work offset $NK_A_OFF.
AXIS_ROT The element describes a rotary machine axis (rotary axis) with direction vector
(Page 426) $NK_OFF_DIR and work offset $NK_A_OFF or a spindle.
Note
The position of a spindle is considered differently depending on the function used by
the kinematic chain:
● Collision avoidance: Indeterminate position
● Kinematic transformation: Depending on the setting in $NT_CNTRL, bit 1-3, the
position corresponding to $NK_A_OFF or the speed setpoint is taken into con‐
sideration
ROT_CONST The element describes a constant rotation around direction vector $NK_OFF_DIR
(Page 429) and angle $NK_A_OFF.
OFFSET The element describes a constant linear offset with the offset vector $NK_OFF_DIR.
(Page 431)
SWITCH The element defines a switch, which is switched using system variable $NK_SWITCH
(Page 433) (Page 435).
Syntax
$NK_TYPE[<n>] = "<Typ>"
Meaning
$NK_TYPE: Type of the element

Data type: STRING
Data type: INT
<Typ>: Element name, max. string length: 31 characters
Data type: STRING
Range of values: "AXIS_LIN", "AXIS_ROT", "ROT_CONST", "OFFSET",
"SWITCH"
Basic functions
Kinematic chain
4.2 Commissioning
Example
The 9th kinematic element is a rotary axis:

N100 $NK_TYPE[8] = "AXIS_ROT" ; 9th kin. element
; type = rotary axis
4.2.3.6 Type-dependent variables for $NK_TYPE = "AXIS_LIN"
$NK_OFF_DIR
Function
The direction vector along which the linear axis $NK_AXIS assigned to the element moves,
should be entered in the system variable. The output coordinate system therefore results from
the input coordinate system, offset by the current position value of the linear axis and the work
offset specified in $NK_A_OFF.
Supplementary conditions:
● The direction vector must be specified as an absolute value, i.e. in relation to the world
coordinate system.
● The direction vector must be specified so that it points in the positive traversing direction of
the machine axis.
● The absolute value of the direction vector must be greater than 1*10-6.
Syntax
$NK_OFF_DIR[<n>,<k>] = <value>
Meaning
$NK_OFF_DIR: Direction vector (X; Y; Z)

Data type: REAL
Range of values: Direction vector: 1*10-6 < |Vector | ≤ max. REAL value
Default value: (0.0, 0.0, 0.0)
Data type: INT
<k>: Coordinate index
Data type: INT
Range of values: 0: X coordinate (abscissa)
1: Y coordinate (ordinate)
2: Z coordinate (applicate)
<value>: Coordinate value
Data type: REAL
Range of values: - max. REAL value ≤ x ≤ + max. REAL value
Basic functions
Kinematic chain
4.2 Commissioning
Example
; The linear axis of the 9th element moves along the direction vector. The direction vector is the
unit vector (1; 0; 0), rotated around Z with γ=90° in the X/Y plane, and around X with α=10° in
the Y/Z plane referred to the world coordinate system. The following values result from this for
the individual components (x, y, z) of the direction vector:
● x = cos(γ) * cos(α) = cos(90) * cos(10) = 0.0
● y = sin(γ) * cos(α) = sin(90) * cos(10) ≈ 0.985
● z = sin(α) = sin(10) ≈ 0.174
))B ',5
1 . B2
˞ _Y_
<
ˠ ]
[
; \
Figure 4-6 Direction vector, general

; 9th kinematic element
N100 $NK_OFF_DIR[8,0] = COS(90)*COS(10) ; 0 = X component
N110 $NK_OFF_DIR[8,1] = SIN(90)*COS(10) ; 1 = Y component
N120 $NK_OFF_DIR[8,2] = SIN(10) ; 2 = Z component
$NK_AXIS
Function
The name of the machine axis (MD10000 $MN_AXCONF_MACHAX_NAME_TAB) that is to be
assigned to the element should be entered in the system variable.
The output coordinate system of the element results from the input coordinate system offset by
the current position setpoint of the machine axis in the MCS and the offset specified in
$NK_A_OFF. The position setpoint of the machine axis contains all the active work offsets and
corrections.
In accordance with the AXIS_LIN type entered in $NK_TYPE, the machine axis must be a linear
axis:
MD30300 $MA_IS_ROT_AX = 0
Syntax
$NK_AXIS[<n>] = <name>
Basic functions
Kinematic chain
4.2 Commissioning
Meaning
$NK_AXIS: Machine axis name

Data type: STRING
Range of values: Machine axis name
Data type: INT
<value>: Machine axis name
Data type: STRING
Range of values: Machine axis names
Example
The 9th kinematic element is assigned the machine axis with the name V1 as linear axis.

N100 $NK_AXIS[8] = "V1" ; 9th kin. element
; axis = machine axis V1
$NK_A_OFF
Function
An additional work offset can be entered in the system variable for the assigned machine axis
($NK_AXIS). This work offset is only effective within the kinematic chain.
Syntax
$NK_A_OFF[<n>] = <value>
Meaning
$NK_A_OFF: Work offset

Data type: REAL
Range of values: - max. REAL value ≤ x ≤ ± max. REAL value
Default value: 0.0
Data type: INT
Data type: REAL
Example
The linear axis zero point of the 9th kinematic element is moved by 30.0 mm compared to the
modelled kinematics.
Basic functions
Kinematic chain
4.2 Commissioning
The unit in which the numerical value is interpreted depends on the current input system (inch/
metric).

N100 $NK_A_OFF[8] = 30.0 ; 9th kin. element
; Work offset = 30.0 mm
4.2.3.7 Type-dependent variables for $NK_TYPE = "AXIS_ROT"
$NK_OFF_DIR
Function
The direction vector around which the rotary axis $NK_AXIS assigned to the element rotates,
should be entered in the system variable. The output coordinate system is therefore calculated
from the input coordinate system, rotated by the current position value of the rotary axis and the
offset specified in $NK_A_OFF around the direction vector $NK_OFF_DIR.
coordinate system.
● The direction vector must be specified so that, in accordance with the "right-hand rule", the
thumb points in the direction of the vector when the rotary axis turns in the positive direction.
Note
Spindle
If the assigned machine axis is a spindle, its position is taken into account in different ways
specific to the function:
● Collision avoidance: Indeterminate position
● Kinematic transformation: depending on the setting in $NT_CNTRL, bit 1-3
– Bit x == 0 → indeterminate position
– Bit x == 1 → current position value + $NK_A_OFF,
Syntax
Meaning

Data type: REAL
Basic functions
Kinematic chain
4.2 Commissioning

Data type: INT
Data type: INT
Data type: REAL
Example
The rotary axis of the 9th element rotates around the direction vector. The direction vector is the
unit vector (1; 0; 0), rotated around Z with γ=90° in the X/Y plane, and around X with α=10° in
the Y/Z plane referred to the world coordinate system. The following values result from this for
the individual components (x, y, z) of the direction vector:
● z = sin(α) = sin(10) ≈ 0.174
))B ',5
1 . B2
˞ _Y_
<
ˠ ]
[
; \
Figure 4-7 Direction vector, general

$NK_AXIS
Function
The name of the machine axis (MD10000 $MN_AXCONF_MACHAX_NAME_TAB) that is to be
assigned to the element should be entered in the system variable.
Basic functions
Kinematic chain
4.2 Commissioning
The output coordinate system of the element results from the input coordinate system rotated
through the current position setpoint of the machine axis in the MCS and the offset specified in
$NK_A_OFF. The position setpoint of the machine axis contains all the active work offsets and
corrections.
The machine axis type must correspond to the type entered in $NK_TYPE:
In accordance with the AXIS_ROT type entered in $NK_TYPE, the machine axis must be a
rotary axis:
MD30300 $MA_IS_ROT_AX = 1
Syntax
$NK_AXIS[<n>] = <name>
Meaning
$NK_AXIS: Machine axis name

Data type: STRING
Range of values: Machine axis name
Data type: INT
<value>: Machine axis name
Data type: STRING
Range of values: Machine axis names
Example
The 9th kinematic element is assigned the machine axis with the name B1 as rotary axis.

N100 $NK_AXIS[8] = "B1" ; 9th kin. element
; axis = machine axis B1
$NK_A_OFF
Function
An additional work offset can be entered in the system variable for the assigned machine axis
($NK_AXIS). This work offset is only effective within the kinematic chain.
Syntax
Basic functions
Kinematic chain
4.2 Commissioning
Meaning
$NK_A_OFF: Work offset

Data type: REAL
Default value: 0.0
Data type: INT
Data type: REAL
Example
The rotary axis zero point of the 9th kinematic elements is moved through 30.0° compared to
the modelled kinematics.

; Work offset = 30.0°
4.2.3.8 Type-dependent variables for $NK_TYPE = "ROT_CONST"
$NK_OFF_DIR
Function
The direction vector around which the constant rotation is performed should be entered in the
system variable. The output coordinate system is therefore calculated from the input coordinate
system, rotated through the angle specified in $NK_A_OFF around the direction vector
$NK_OFF_DIR.
coordinate system.
● The direction vector must be specified so that, in accordance with the "right-hand rule", the
thumb points in the direction of the vector when the rotary axis turns in the positive direction.
Syntax
Basic functions
Kinematic chain
4.2 Commissioning
Meaning

Data type: REAL
Data type: INT
Data type: INT
Data type: REAL
Example
The output coordinate system of the 9th Elements therefore arises from the input coordinate
system, rotated through the angle specified in $NK_A_OFF around the direction vector. The
direction vector is the unit vector (1; 0; 0), rotated around Z with γ=90° in the X/Y plane, and
around X with α=10° in the Y/Z plane referred to the world coordinate system. The following
values result from this for the individual components (x, y, z) of the direction vector:
● z = sin(α) = sin(10) ≈ 0.174
))B ',5
˞ 1 . B2
<
)
$ B2 )
ˠ ] 1. B
[
; \
Figure 4-8 ROT_CONST

Basic functions
Kinematic chain
4.2 Commissioning
$NK_A_OFF
Function
The angle through which the output coordinate system is rotated compared with the input
coordinate system around the direction vector $NK_OFF_DIR should be entered in the system
variable.
Syntax
Meaning
$NK_A_OFF: Angle of rotation

Data type: REAL
Default value: 0.0
Data type: INT
<value>: Angle
Data type: REAL
Example
The angle of rotation of the 9th kinematic element is 30.0°.

; Angle of rotation = 30.0°
4.2.3.9 Type-dependent variables for $NK_TYPE = "OFFSET"
$NK_OFF_DIR
Function
The offset vector by which the output coordinate system is moved compared to the input
coordinate system should be entered in the system variable.
The offset vector must be specified as an absolute value, i.e. in relation to the world coordinate
system.
Syntax
Basic functions
Kinematic chain
4.2 Commissioning
Meaning
$NK_OFF_DIR: Offset vector (X; Y; Z)

Data type: REAL
Range of values: (- max. REAL value) ≤ x ≤ (+ max. REAL value)
Data type: INT
Data type: INT
Data type: REAL
Range of values: (- max. REAL value) ≤ x ≤ (+ max. REAL value)
Example
The output coordinate system of the 9th element is obtained from the input coordinate system,
offset through the offset vector (x, y, z) with the following coordinates referred to the world
coordinate system:
● x = 10.0
● y = 20.0
● z = 30.0
=
))B ',5
1 . B2
<
]
[
; \
Figure 4-9 Offset vector

N100 $NK_OFF_DIR[8,0] = 10.0 ; 0 = X component
N110 $NK_OFF_DIR[8,1] = 20.0 ; 1 = Y component
N120 $NK_OFF_DIR[8,2] = 30.0 ; 2 = Z component
Basic functions
Kinematic chain
4.2 Commissioning
4.2.3.10 Type-dependent variables for $NK_TYPE = "SWITCH"
$NK_SWITCH_INDEX
Function
The switch is emulated using system variables $NK_SWITCH_INDEX and
$NK_SWITCH_POS (see the following paragraph)
Index i must be entered in $NK_SWITCH_INDEX, with which the switch is closed and opened
via system variable $NK_SWITCH[].
Syntax
$NK_SWITCH_INDEX[<n>] = 
Meaning
$NK_SWITCH_ Index i, via which the switch is addressed using system variable $NK_SWITCH[]
INDEX: Data type: INT
Range of values: -1, 0, 1, 2, ... ($MN_MAXNUM_KIN_SWITCHES - 1)
-1: The state of the switch is always CLOSED
Default value: -1
Data type: INT
: Index value
Data type: INT
Example
The 9th element of the kinematic chain is a switch, which is activated by system variable
$NK_SWITCH[ 2 ].

; 9th element
N100 $NK_SWITCH_INDEX[8] = 2 ; Index 2
$NK_SWITCH_POS
Function
A switch is emulated by system variables $NK_SWITCH_INDEX (see the previous paragraph)
and $NK_SWITCH_POS.
In $NK_SWITCH_POS, value p (close value) should be entered, where the switch is brought
into the CLOSED position by system variable $NK_SWITCH[].
Basic functions
Kinematic chain
4.2 Commissioning
Independent of $NK_SWITCH[], the switch has the following states:

● CLOSED: The close value p of the switch, specified in $NK_SWITCH_POS is the same as
the actual value of $NK_SWITCH[].
$NK_SWITCH_POS[<n>] == $NK_SWITCH[]
The previous element of the kinematic chain is connected with the output, i.e. the following
element of the switch specified in $NK_NEXT.
● OPEN: The close value of the switch, specified in $NK_SWITCH_POS, is not the same as
the actual value of $NK_SWITCH[].
$NK_SWITCH_POS[<n>] ≠ $NK_SWITCH[]
The previous element of the kinematic chain is notconnected with the output, i.e. the
following element of the switch specified in $NK_NEXT.
The close value can be freely selected.
Note
Parallel element $NK_PARALLEL
The connection to a parallel element specified in $NK_PARALLEL is not influenced by the
switch. This means that the previous element is always connected to the element in the branch
parallel with the switch.
Syntax
$NK_SWITCH_POS[<n>] = 
Meaning
$NK_SWITCH_ Close value

POS: Data type: INT
Range of values: 0 ≤ x ≤ positive max. INT value
Default value: 0
Data type: INT
: Value for switch position CLOSED
Data type: INT
Example
The 9th element of the kinetic chain is a switch, which is closed if $NK_SWITCH[ 3 ] == 1

; 9th element
N110 $NK_SWITCH_POS[8] = 1 ; switch position = 1
See also
$NK_SWITCH (Page 435)
$MN_MAXNUM_KIN_SWITCHES (Page 417)
Basic functions
Kinematic chain
4.2 Commissioning
$MN_MM_MAXNUM_KIN_CHAIN_ELEM (Page 417)
4.2.3.11 $NK_SWITCH
Function
The switch variable comprises an array of switch positions i. The actual switch positions p
should be entered in this array.
Function
To parameterize (Page 433) a switchi in a kinematic chain, switchiwith index i must be
connected to the switch variable and its switch position p for the CLOSED state assigned to it.
$NK_SWITCH_INDEX[<n>] = 
$NK_SWITCH_POS[<n>] = 
Switchi can then be closed and opened via index i of the switch variable:
Close: $NK_SWITCH[] = 
Open: $NK_SWITCH[] ≠ 
As many switches as required can be connected with an index of the switch variable.
Syntax
$NK_SWITCH[] = 
Meaning
$NK_SWITCH: Switch variable with switch positions i

Data type: INT
Value range: -1 ≤x ≤ positive max. INT value
Note
-1: Initial state OPEN
: Switch index
Data type: INT
Range of values: 0, 1, 2, ... (MD18882 $MN_MM_MAX_NUM_KIN_SWITCHES
- 1)
: Switch setting
Data type: INT
Value range: -1 ≤x ≤ positive max. INT value
-1: Initial state OPEN
Basic functions
Kinematic chain
4.3 Programming
Example
The 9th kinematic element is assigned the name "B axis":

N100 $NK_SWITCH[3] = 1 ; actual switch position
; for switch [3] = 1
4.3 Programming
4.3.1 Deletion of components (DELOBJ)

The DELOBJ() function "deletes" components by resetting the assigned system variables to
their default values:
● Elements from kinematic chains
● Protection areas, protection area elements and collision pairs
● Transformation data
Syntax
[<RetVal>=] DELOBJ(<CompType>[,,,<NoAlarm>)])
[<RetVal>=] DELOBJ(<CompType>,<Index1>[,,<NoAlarm>])
[<RetVal>=] DELOBJ(<CompType>[,<Index1>][,<Index2>][,<NoAlarm>])
Basic functions
Kinematic chain
4.3 Programming
Meaning
DELOBJ: Deletion of elements from kinematic chains, protection areas, protection area ele‐
ments, collision pairs and transformation data
<CompType>: Component type to be deleted
Data type: STRING
Value: "KIN_CHAIN_ELEM"
Meaning: System variables of all kinematic elements: $NK_...
Value: "KIN_CHAIN_SWITCH"
Meaning: System variable $NK_SWITCH[]
Value: "KIN_CHAIN_ALL"
Meaning: All kinematic elements and switches.
Is the same as the successive call of DELOBJ with "KIN_CHAIN_ELEM" and
"KIN_CHAIN_SWITCH"
Value: "PROT_AREA"
Meaning: System variables of the protection areas:
● $NP_PROT_NAME
● $NP_CHAIN_NAME
● $NP_CHAIN_ELEM
● $NP_1ST_PROT
Value: "PROT_AREA_ELEM"
Meaning: System variables of the protection area elements of machine protection
areas and/or automatic tool protection areas:
● $NP_NAME
● $NP_NEXT
● $NP_NEXTP
● $NP_COLOR
● $NP_D_LEVEL
● $NP_USAGE
● $NP_TYPE
● $NP_FILENAME
● $NP_PARA
● $NP_OFF
● $NP_DIR
● $NP_ANG
Value: "PROT_AREA_COLL_PAIRS"
Meaning: System variables of the collision pairs:
● $NP_COLL_PAIR
● $NP_SAFETY_DIST
Value: "PROT_AREA_ALL"
Meaning: All protection areas, protection area elements and collision pairs (system
variable $NP_... )
Is the same as the successive call of DELOBJ with "PROT_AREA,"
"PROT_AREA_ELEM," and "PROT_AREA_COLL_PAIRS"
Value: "TRAFO_DATA"
Meaning: System variables of all transformations $NT_...
Basic functions
Kinematic chain
4.3 Programming
<Index1>: Index of the first component to be deleted (optional)

Data type: INT
Default value: -1
Range of val‐ -1 ≤ x ≤ (maximum number of configured components -1)
ues:
Value Meaning
0, 1, 2, .... Index of the component to be deleted.
-1 All components of the specified type are deleted. <Index2> is not
evaluated.
<Index2>: Index of the last components to be deleted (optional)
If <Index2> is not programmed, only the system variables of the component refer‐
enced in <Index1> are deleted.
Data type: INT
Default value: Only the system variables of the component referenced in <In‐
dex1> are deleted.
Range of val‐ <Index1> < x ≤ (max. number of configured components -1)
ues:
<NoAlarm>: Alarm suppression (optional)
Data type: BOOL
Default value: FALSE
Value Meaning
FALSE In the event of an error (<RetVal> < 0), program processing is
stopped and an alarm displayed.
TRUE In the event of an error, the program processing is not stopped and
no alarm displayed.
Application: User-specific reaction corresponding to the return
value
<RetVal>: Function return value
Data type: INT
Range of val‐ 0, -1, -2, ... -7
ues:
Value Meaning
0 No error occurred.
-1 Call of the function without parameters. At least parameter
<CompType> must be specified.
-2 <CompType> identifies an unknown component
-3 <Index1> is less than -1
-4 <Index1> is greater than the configured number of components
-5 <Index1> has a value not equal to -1 when deleting a compo‐
nent group
-6 <Index2> is less than <Index1>
-7 <Index2> is greater than the configured number of components
Basic functions
Kinematic chain
4.3 Programming
4.3.2 Index determination by means of names (NAMETOINT)

User-specific names are entered in the system variable arrays of type STRING. Based on the
identifier of the system variables and the name, the NAMETOINT() function determines the
index value belonging to the name under which it is stored in the system variable array.
Syntax
<RetVal> = NAMETOINT(<SysVar>,<Name>[,<NoAlarm>])
Meaning
NAMETOINT: Determining the system variable index

<SysVar>: Name of the system variable array of typeSTRING
Data type: STRING
Range of val‐ Name of all NC system variable arrays of type STRING
ues:
<Name>: Character string or name for which the system variable index is to be determined.
Data type: STRING
<NoAlarm>: Alarm suppression (optional)
Data type: BOOL
Default value: FALSE
Value Meaning
TRUE In the event of an error, the program processing is not stopped and
no alarm displayed.
Application: User-specific reaction corresponding to the return
value
FALSE In the event of an error (<RetVal> < 0), program processing is
stopped and an alarm displayed.
<RetVal>: System variable index or error message

Data type: INT
Range of val‐ -1 ≤ x ≤ (max. number of configured components -1)
ues:
Value Meaning
≥0 The sought name has been found under the specified system
variable index.
-1 The sought name has not been found or an error has occurred.
Example
DEF INT INDEX
$NP_PROT_NAME[27]="Cover"
...
INDEX = NAMETOINT("$NP_PROT_NAME","Cover") ; INDEX == 27
Basic functions
Kinematic chain
4.4 Example
4.4 Example
4.4.1 Specifications
General Information
The principle approach when parameterizing a kinematic chain with three switches using a part
program is shown using as example a 5-axis machine with three different tool heads, which are
used alternately. All of the system variables, relevant for kinematic chain, are written to the part
program:
● Kinematic chain $NK_...
Option and machine data

The following option and machine data must be set for the example:
● MD19830 $ON_COLLISION_MASK.Bit 0 = 1
● MD18880 $MN_MM_MAXNUM_KIN_CHAIN_ELEM = 15
Kinematic chain
Schematic representation of the machine kinematics
&$$;,6
2))6(7
$$;,6

&$;,6
&$;,62))6(7
722/5()

=$;,6

6+($'

6
;,
$
<
6+($'
;$;,6
6+($'
Basic functions
Kinematic chain
4.4 Example
Elements of the kinematic chain
5RRW ;$;,6 <$;,6 =$;,6 &$;,6 &$;,6

2))6(7 $;,6B/,1 $;,6B/,1 $;,6B/,1 2)) $;,6B527
2))6(7

'2&.B3B +($'
6:,7&+ 2))6(7

'2&.B3B +($'
6:,7&+ 2))6(7

&$$;,6 $$;,6 722/5() '2&.B3B +($'

2)) $;,6B527 2))6(7 6:,7&+ 2))6(7
2))6(7

The kinematic chain starts with an element of the type "Offset". When completely
parameterizing the collision avoidance, these are assigned to all static protection areas of the
machine
The offset element is followed by the kinematic elements of the linear machine axes X, Y and
Z - as well as the offset and kinematic elements of rotary axes C and A.
The offset element for the reference point of the tool heads is followed by three switches to
switch on and switch off the tool heads. As a result of $NK_INDEX = 3 all three switches refer
to the same switch variable $NK_SWITCH[ 3 ]. As a result of the different switch positions (1,
2, 3), only the subchain of the active tool head is active.
Basic functions
Kinematic chain
4.4 Example
4.4.2 Part program of the machine model
Program code
;===========================================================
; Definitions
;===========================================================
N10 DEF INT KIE_CNTR ; COUNTER FOR ELEMENTS OF THE KIN. CHAINS
N20 DEF INT RETVAL
;
;===========================================================
; Initialization of collision data
;===========================================================
; Reset all parameters to their initial values:
N30 RETVAL = DELOBJ("KIN_CHAIN_ELEM")
N40 KIE_CNTR = 0
;
;===========================================================
; Kinematic chain
;===========================================================
; KE1: OFFSET: Root
; ----------------------------------------------------------
N50 $NK_TYPE[KIE_CNTR] = "OFFSET"
N60 $NK_NAME[KIE_CNTR] = "ROOT"
N70 $NK_NEXT[KIE_CNTR] = "X-AXIS"
N80 KIE_CNTR = KIE_CNTR + 1
;
; ----------------------------------------------------------
; Kinematic element: LINEAR AXIS: X axis
; ----------------------------------------------------------
N90 $NK_TYPE[KIE_CNTR] = "AXIS_LIN"
N100 $NK_NAME[KIE_CNTR] = "X-AXIS"
N110 $NK_NEXT[KIE_CNTR] = "Y-AXIS"
N120 $NK_AXIS[KIE_CNTR] = "X1"
;
N130 $NK_OFF_DIR[KIE_CNTR,0] = 1.0 ; X
;
; ----------------------------------------------------------
; Kinematic element: LINEAR AXIS: Y axis
; ----------------------------------------------------------
N160 $NK_NAME[KIE_CNTR] = "Y-AXIS"
N170 $NK_NEXT[KIE_CNTR] = "Z-AXIS"
N180 $NK_AXIS[KIE_CNTR] = "Y1"
;
N190 $NK_OFF_DIR[KIE_CNTR,1] = 1.0 ; Y
;
; ----------------------------------------------------------
; Kinematic element: LINEAR AXIS: Z axis
; ----------------------------------------------------------
N220 $NK_NAME[KIE_CNTR] = "Z-AXIS"
N230 $NK_NEXT[KIE_CNTR] = "C-AXIS-OFFSET"
N240 $NK_AXIS[KIE_CNTR] = "Z1"
;
Basic functions
Kinematic chain
4.4 Example
Program code
N250 $NK_OFF_DIR[KIE_CNTR,2] = 1.0 ; Z
;
; ----------------------------------------------------------
; Kinematic element: OFFSET: C axis
; ----------------------------------------------------------
N280 $NK_NAME[KIE_CNTR] = "C-AXIS-OFFSET"
N290 $NK_NEXT[KIE_CNTR] = "C-AXIS"
;
N300 $NK_OFF_DIR[KIE_CNTR,2] = 600.0 ; Z direction
N310 KIE_CNTR = KIE_CNTR + 1 ;
;
; ----------------------------------------------------------
; Kinematic element: ROTARY AXIS: C axis
; ----------------------------------------------------------
N320 $NK_TYPE[KIE_CNTR] = "AXIS_ROT"
N330 $NK_NAME[KIE_CNTR] = "C-AXIS"
N340 $NK_NEXT[KIE_CNTR] = "C-A-OFFSET"
N350 $NK_AXIS[KIE_CNTR] = "C1"
;
N360 $NK_OFF_DIR[KIE_CNTR,2] = 1.0 ; Z direction
;
; ----------------------------------------------------------
; Kinematic element: OFFSET: C-A axis
; ----------------------------------------------------------
N390 $NK_NAME[KIE_CNTR] = "C-A-OFFSET"
N400 $NK_NEXT[KIE_CNTR] = "A-AXIS"
;
N410 $NK_OFF_DIR[KIE_CNTR,0] = 20.0 ; X direction
N420 $NK_OFF_DIR[KIE_CNTR,1] = -5.0 ; Y direction
;
; ----------------------------------------------------------
; Kinematic element: ROTARY AXIS: A axis
; ----------------------------------------------------------
N440 $NK_TYPE[KIE_CNTR] = "AXIS_ROT"
N450 $NK_NAME[KIE_CNTR] = "A-AXIS"
N460 $NK_NEXT[KIE_CNTR] = "TOOL-REF"
N470 $NK_AXIS[KIE_CNTR] = "A1"
;
N480 $NK_OFF_DIR[KIE_CNTR,0] = 1.0 ; X direction
;
; ----------------------------------------------------------
; Kinematic element: OFFSET: Tool reference
; ----------------------------------------------------------
N510 $NK_NAME[KIE_CNTR] = "TOOL-REF"
N520 $NK_NEXT[KIE_CNTR] = "DOCKING_POINT 1"
;
N530 $NK_OFF_DIR[KIE_CNTR,2] = -200.0 ; Z direction
;
Basic functions
Kinematic chain
4.4 Example
Program code
; ----------------------------------------------------------
; Kinematic element: Switch 3/1
; ----------------------------------------------------------
N550 $NK_TYPE[KIE_CNTR] = "SWITCH"
N560 $NK_NAME[KIE_CNTR] = "DOCKING_POINT 1"
N570 $NK_NEXT[KIE_CNTR] = "HEAD 1"
N580 $NK_PARALLE[KIE_CNTR] = "DOCKING_POINT 2"
;
N590 $NK_SWITCH_INDEX[KIE_CNTR] = 3 ; Index 3
N600 $NK_SWITCH_POS[KIE_CNTR] = 1 ; switch position 1
;
; ----------------------------------------------------------
; ----------------------------------------------------------
N650 $NK_PARALLE[KIE_CNTR] = "DOCKING_POINT 3"
;
;
; ----------------------------------------------------------
; ----------------------------------------------------------
N720 $NK_PARALLE[KIE_CNTR] = ""
;
; ----------------------------------------------------------
; Kinematic element: OFFSET: HEAD 1
; ----------------------------------------------------------
N770 $NK_NAME[KIE_CNTR] = "HEAD 1"
N780 $NK_NEXT[KIE_CNTR] = ""
;
N790 $NK_OFF_DIR[KIE_CNTR,0] = 100 ; X direction
N800 $NK_OFF_DIR[KIE_CNTR,1] = -30 ; Y direction
;
; ----------------------------------------------------------
; ----------------------------------------------------------
;
N850 $NK_OFF_DIR[KIE_CNTR,2] = -230 ; Z direction
;
Basic functions
Kinematic chain
4.5 Data lists
Program code
; ----------------------------------------------------------
; ----------------------------------------------------------
;
N900 $NK_OFF_DIR[KIE_CNTR,0] = 50 ; X direction
N910 $NK_OFF_DIR[KIE_CNTR,1] = -20 ; Y direction
N920 $NK_OFF_DIR[KIE_CNTR,2] = -90 ; Z direction
End
4.5 Data lists
4.5.1 Machine data

16800 ROOT_KIN_ELEM_NAME Name of the first element in the kinematic chain
18880 MM_MAXNUM_KIN_CHAIN_ELEM Maximum number of elements for kinematic chains
18882 MM_MAX_NUM_KIN_SWITCHES Maximum number of switches for kinematic chains
$NK_NAME Name of the kinematic element
$NK_NEXT Name of the next element in the kinematic chain
$NK_PARALLEL Name of the first element of a parallel branching kinematic chain before the
element
$NK_TYPE Type of the kinematic element
$NK_OFF_DIR Depends on $NK_TYPE: Offset or direction vector
$NK_AXIS Name of the assigned machine axis or object name
$NK_A_OFF Work offset in the element for linear or rotary axes
$NK_SWITCH_INDEX Index i, via which the switch is addressed using system variable
$NK_SWITCH[]
$NK_SWITCH_POS Switch position CLOSED
$NK_SWITCH Switch variable
Basic functions
Kinematic chain
4.5 Data lists
Basic functions
Continuous-path mode, exact stop, LookAhead 5
5.1 Brief Description
Exact stop or exact stop mode

In exact stop traversing mode, all axes involved in the traversing motion (except axes of modal
traversing modes) are decelerated at the end of each block until they come to a standstill. The
transition to the next block occurs only when all axes involved in the traversing motion have
reached their programmed target position depending on the selected exact stop criterion.
Continuous-path mode
In the continuous-path mode, the NC attempts to keep the programmed path velocity as
constant as possible. In particular, deceleration of the path axes at the block limits of the part
program is to be avoided.
LookAhead
LookAhead is a function for optimizing the continuous path mode.
Smooth and uniform machining of workpieces is necessary to ensure a high-quality surface
finish. For this reason, path velocity variations should be avoided during machining whenever
possible. Without LookAhead, the NC only takes the traversing block immediately following the
current traversing block into consideration when determining the possible path velocity. If the
following block contains only a short path, the NC must reduce the path velocity (decelerate in
the current block) to be able to stop in time at the end of the next block, if necessary.
When the NC "looks ahead" over a configurable number of traversing blocks following the
current traversing block, a much higher path velocity can be attained under certain
circumstances because the NC now has considerably more traversing blocks and more path
available for calculation.
● Machining with higher path velocities on average
● Improved surface quality by avoiding deceleration and acceleration
Smoothed path velocity

"Smoothing the path velocity" is a function especially for applications (such as high speed
milling in mold and die making) that require an extremely steady and consistent path velocity.
Deceleration and acceleration processes that would cause high-frequency excitation of
machine resonances are avoided with the "Smoothing the path velocity" function.
Basic functions
Continuous-path mode, exact stop, LookAhead

● Improved surface quality and shorter machining time by avoiding excitation of machine
resonances.
● Constant profile of path velocity and cutting rates by avoiding "unnecessary" acceleration
processes, i.e. acceleration processes that do not greatly improve the program run time.
Adaptation of the dynamic path response

In addition to "smoothing the path velocity", "dynamic path response adaptation" is another
function for avoiding high-frequency excitations of machine resonances while optimizing the
dynamic path response at the same time. To achieve this, highly frequency changes in path
velocity are automatically executed with lower jerk or acceleration values than the dynamic
response limit value parameterized in the machine data.
Thus, with low-frequency changes in the path velocity, the full dynamic response limit values
apply, whereas with high-frequency changes, only the reduced dynamic response limit values
act due to the automatic dynamic response adaptation.
Dynamic response mode for path interpolation

Optimizing the path dynamic response also includes the technology-specific dynamic response
settings which are preset for different machining technologies (including tapping, roughing,
smoothing) and can be activated in the part program by calling the respective dynamic
response mode.
Free-form surface mode

Any fluctuation in curvature or torsion leads to a change in path velocity. This generally results
in unnecessary decelerating and accelerating while machining free-form surface workpieces,
which may adversely affect the quality of the surfaces of the workpieces.
The following functions are available for machining free-form surfaces.
● "Free-form surface mode: Basic functions"
This makes the definition of the path velocity profile "less sensitive" to fluctuations in
curvature and torsion.
● "Free-form surface mode: Extension function"
This extension in standard LookAhead functionality is used to calculate the path velocity
profile while machining free-form surfaces.
The advantages of free-form surface mode lie in a more homogeneous workpiece surface and
lower machine stress levels.
Compressing linear blocks

When a workpiece design is completed with a CAD/CAM system, the CAD/CAM system
generally also compiles the corresponding part program to create the workpiece surface. To do
so, most CAD/CAM systems use linear blocks to describe even curved sections of the
workpiece surface. Many interpolation points are generally necessary to maintain the required
contour accuracy. This results in many linear blocks, typically with very short paths.
Basic functions
5.2 Exact stop mode
The "Compressor function" uses polynomial blocks to perform a subsequent approximation of

the contour specified by the linear blocks. During this process, an assignable number of linear
blocks is replaced by a polynomial block.
Advantages:
● Reduction of the number of traversing blocks
● Increased path velocity
● Increased surface quality
● Continuous block transitions
Compressing short spline blocks

A spline defines a curve, which comprises 2nd or 3rd degree polynomials With spline
interpolation, the control system can generate a smooth curve characteristic from only a few
specified interpolation points of a set contour.
The advantages of the spline interpolation as compared to the linear interpolation are:
● Reduction of the number of required part program blocks for describing a curved contour.
● Soft characteristic that reduces the stress on the mechanical system, even between part
program blocks.
The disadvantages of spline interpolation as compared to linear interpolation are:
● For a spline curve no exact curve characteristic, but only a tolerance band can be specified,
within which the spline curve should lie.
As with linear interpolation, the processing of splines can produce such short blocks that the
path velocity must be reduced to enable interpolation of the spline blocks. This is also the case,
when the spline has a long, smooth curve. The "Compression of short spline blocks" function
allows you to combine these spline blocks such that the resulting block length is sufficient and
does not reduce the path velocity.
5.2 Exact stop mode
Exact stop or exact stop mode

In the exact stop traversing mode, all path axes and special axes involved in the traversing
motion that are not traversed modally, are decelerated at the end of each block until they come
to a standstill. The transition to the next block occurs only when all axes involved in the
traversing motion have reached their programmed target position depending on the selected
exact stop condition.
This results in the following response are obtained:
● The program run time is considerably longer compared to continuous path mode due to the
deceleration of the axes and the wait time until "Exact stop" status is reached for all machine
axes involved.
● In exact stop mode, undercuts can occur on the workpiece surface during machining.
Basic functions
5.2 Exact stop mode
Exact stop condition

The following exact stop conditions can be set:
● "Exact stop coarse"
● "Exact stop fine"
● "Interpolator end"
Application
Exact stop mode should always be used when the programmed contour must be executed
exactly.
Activation
In a program, exact stop operation can be specified using the following commands, either
modal or for specific blocks:
Command Meaning
G60 Exact stop operation is effective from the current modal block.
G9 Exact stop operation is effective in the current block.
Exact stop conditions - "Exact stop coarse" and "Exact stop fine"
The exact stop condition "coarse" or "fine" is fulfilled by a machine axis if its current following
error is less than or equal to the tolerance range around the setpoint position, parameterized in
the machine data:
● MD36000 $MA_STOP_LIMIT_COARSE (exact stop coarse)
● MD36010 $MA_STOP_LIMIT_FINE (exact stop fine)
)ROORZLQJHUURU 6HWSRLQWSRVLWLRQ
'%'%; H[DFWVWRSFRDUVH
'%'%; H[DFWVWRSILQH
9HORFLW\VHWSRLQW
*
0'
0$B6723B/,0,7B&2$56(
*
0'
0$B6723B/,0,7B),1(
W
Figure 5-1 Tolerance window of exact stop conditions
Basic functions
5.2 Exact stop mode
Note
The tolerance windows of the exact stop conditions "Exact stop coarse" and "Exact stop fine"
should be assigned in such a way that the following requirement is fulfilled:
"Exact stop coarse" > "Exact stop fine"
Exact stop condition, "Interpolator end"

With exact stop condition "Interpolator end", the block change to the next block takes place as
soon as all path axes and non-modal special axes involved in the traversing motion have
reached the position programmed in the block in terms of the setpoint value. That is, the
interpolator has executed the block.
The actual position and the following error of the relevant machine axes are not taken into
consideration for exact stop condition "Interpolator end". Thus, depending on the dynamic
response of the machine axes, this can result in a relatively large smoothing of the contour at
the block changes in comparison to the exact stop conditions "Exact stop coarse" and "Exact
stop fine".
Activating the programmable exact stop conditions

The programmable exact stop conditions are activated using the following commands:
Command Exact stop condition

G601 Exact stop fine
G602 Exact stop coarse
G603 Interpolator end
Block change depending on exact stop condition

The figure below illustrates the block change timing in terms of the selected exact stop
condition.
)ROORZLQJHUURU 6HWSRLQWSRVLWLRQ
%ORFNFKDQJHWLPHV
*
9HORFLW\VHWSRLQW
*
0'
0$B6723B/,0,7B&2$56(
*
0'
0$B6723B/,0,7B),1(
W
Figure 5-2 Block change depending on exact stop condition
Basic functions
5.2 Exact stop mode
Weighting factor for exact stop conditions

A parameter set-dependent evaluation of the exact stop conditions can be specified via the
following axis-specific machine data:
MD36012 $MA_STOP_LIMIT_FACTOR[<Parameter set>] = <Value>
The evaluation factor is applied to the values of the following machine data:
● MD36000 $MA_STOP_LIMIT_COARSE
● MD36010 $MA_STOP_LIMIT_FINE
● MD36030 $MA_STANDSTILL_POS_TOL
● Adaptation of the positioning response to different mass ratios, such as after a new gearbox
stage has been selected.
● Reduction in positioning time, depending on various machining states, such as roughing
and finishing
Parameterizable input of the effective exact stop conditions

The exact stop conditions for the commands of the 1st G group be permanently is specified. As
a consequence, programmed exact stop conditions are no longer effective.
Exact stop conditions can be set independently of one another for the following commands:
● Rapid traverse G0
● All other commands of the 1st G group
The exact stop condition is set on a channel-for-channel basis using the following decimal-
coded machine data:
MD20550 $MC_EXACT_POS_MODE = <Z><E>
Z E Effective exact stop condition

0 0 Programmed exact stop condition
1 1 G601 (Exact stop window fine)
2 2 G602 (Exact stop window coarse)
3 3 G603 (Interpolator end)
E (ones position): Setting the exact stop condition für rapid traverse.
Z (tens position): Setting the exact stop condition for all other commands of the 1st G group.
Example
MD20550 $MC_EXACT_POS_MODE = 02
● <E> = 2: With rapid traverse, exact stop condition G602 (exact stop window coarse) is
always active, irrespective of any programming.
● <Z> = 0: When traversing with all other commands of the 1st G group, the programmed
exact stop condition is effective.
Basic functions
5.3 Continuous-path mode
Block change behavior for block transitions from G0 ↔ non-G0 to continuous path mode
For the continuous path mode, the block change behavior between rapid traverse and non
rapid traverse blocks (G0 ↔ non-G0) can be set using the following machine data:
MD20552 $MC_EXACT_POS_MODE_G0_TO_G1 = <Value>
<Value> Meaning
0 No additional stop at the block transition.
1 Stop at the block transition.
The behavior corresponds to G601 (exact stop window, fine)
The behavior corresponds to G602 (exact stop window, coarse)
The behavior corresponds to G603 (interpolator end)
4 No stop at the block transition.
For the continuous path mode, for block changes from G0 → non-G0, in the G0 block, the
actual value of the feedrate correction of the subsequent non-G0 block is predicatively taken
into account. Depending on the axis dynamic performance and the path length of the current
block, the block change is executed with the exact or the best possible adapted velocity of the
following block.
5 No stop at the block transition.
For the continuous path mode, for block changes from G0 → non-G0 and non-G0 → G0, the
current value of the feedrate correction (G0 → non-G0) or the rapid traverse contour (non-G0
→ G0) of the following block is predicatively taken into account. Depending on the axis dy‐
namic performance and the path length of the current block, the block change is executed
with the exact or the best possible adapted velocity of the following block.
5.3.1 General functionality
In the continuous-path mode, the path velocity is not decelerated for the block change in order
to permit the fulfillment of an exact stop criterion. The objective of this mode is to avoid rapid
deceleration of the path axes at the block-change point so that the axis velocity remains as
constant as possible when the program moves to the next block. To achieve this objective, the
"LookAhead" function is also activated when the continuous-path mode is selected.
Continuous-path mode causes the smoothing and tangential shaping of angular block
transitions by local changes in the programmed contour. The extent of the change relative to
the programmed contour can be limited by specifying the overload factor or rounding criteria.
Basic functions
Continuous-path mode:
● Contour rounding.
● Reduces machining times by eliminating braking and acceleration processes that are
required to fulfill the exact-stop criterion.
● Improves cutting conditions because of the more constant velocity.
Continuous-path mode is suitable if:
● A contour must be traversed as quickly as possible (e.g. with rapid traverse).
● The exact contour may deviate from the programmed contour within a specific tolerance for
the purpose of obtaining a continuous contour
Continuous-path mode is not practical if a contour is to be traversed precisely.
Implicit exact stop

In some cases, an exact stop needs to be generated in continuous-path mode to allow the
execution of subsequent actions. In such situations, the path velocity is reduced to zero.
● If auxiliary functions are output before the traverse motion, the previous block is only
terminated when the selected exact-stop criterion is fulfilled.
● If auxiliary functions are to be output after the traverse motion, they are output after the
interpolator end of the block.
● If an executable block (e.g. starting of a positioning axis) contains no travel information for
the path axes, the previous block is terminated on reaching the selected exact-stop criterion.
● If a positioning axis is declared to be the geometry axis, the previous block is terminated at
the interpolator end when the geometry axis is programmed.
● If a synchronized axis is programmed that was last programmed as a positioning axis or
spindle (initial setting of the special axis is positioning axis), the previous block is ended at
the interpolator end.
● If the transformation is changed, the block previously processed is terminated with the
active exact-stop criterion.
● A block is terminated on interpolator end if the following block contains the changeover of
the acceleration profile BRISK/SOFT (see Function Manual Axes and Spindles,
Section Acceleration).
● If the "empty buffer" function is programmed, the previous block is terminated when the
selected exact-stop criterion is reached.
Basic functions
Velocity = 0 in continuous-path mode

Regardless of the implicit exact stop response, the path motion is braked down to zero velocity
at the end of the block in cases where:
● Positioning axes are programmed with the instruction POS, and their traversing time
exceeds that of the path axes. The block change occurs when the "exact stop fine" of the
positioning axes is reached.
● The time taken to position a spindle programmed with the instruction SPOS is longer than the
traversing time of the path axes. The block change is carried out when the "exact stop fine"
of the positioning spindle is reached.
● The current block contains traversing commands for geometry axes and the following block
traversing commands for synchronized axes or, alternatively, the current block contains
traversing commands for synchronized axes and the subsequent block traversing
commands for geometry axes.
● Synchronization is required.
5.3.2 Velocity reduction according to overload factor
Function
The function lowers the path velocity in continuou-path mode until the non-tangential block
transition can be traversed in one interpolation cycle while respecting the deceleration limit and
taking an overload factor into account.
With the reduced velocity, axial jumps in velocity are produced with a non-tangential contour at
the block transition. These jumps in velocity are also performed by the coupled motion
synchronized axes. The jump in velocity prevents the path velocity dropping to zero. This jump
is performed if the axial velocity was reduced with the axial acceleration to a velocity from which
the new setpoint can be reached with the jump. The magnitude of the setpoint jump can be
limited using an overload factor. Because the magnitude of the jump is axial, the minimum jump
of the path axes which are active during the block change is considered during block transition.
Basic functions
%ORFNFKDQJH [
3DWKYHORFLW\
%ORFNFKDQJH W
9HORFLW\RI;D[LV $[LDO
*UDGLHQWD[ YHORFLW\MXPS
*UDGLHQWI[D[I[!
,32F\FOH W
9HORFLW\RI<D[LV $[LDO
YHORFLW\MXPS *UDGLHQWD[
*UDGLHQWI\D\
I\!I[!
I2YHUORDGIDFWRU
,32F\FOH W
Figure 5-3 Axial velocity change on block transition
With a practically tangential block transition, the path velocity is not reduced if the permissible
axial accelerations are not exceeded. This means that very small bends in the contour (e.g.
0.5°) are overtraveled directly.
Overload factor
The overload factor restricts step changes in the machine axis velocity at block ends. To ensure
that the velocity jump does not exceed the maximum load on the axis, the jump is derived from
the acceleration of the axis.
The overload factor indicates the extent by which the acceleration of the machine axis
(MD32300 $MA_MAX_AX_ACCEL) may be exceeded for an IPO-cycle.
The velocity jump results as follows:
Velocity jump = axis acceleration * (overload factor-1) * interpolator cycle.
The overload factor is saved in the machine data:
MD32310 $MA_MAX_ACCEL_OVL_FACTOR (overload factor for axial velocity jumps)
Factor 1.0 means that only tangential transitions with finite velocity can be traversed. For all
other transitions, the velocity is reduced to zero by changing the setpoint. This behavior is
Basic functions
equivalent to the function "Exact stop with interpolator end". This is undesirable for continuous-
path mode, so the factor must be set to greater than 1.0.
Note
For startup and installation, please note that the factor must be reduced if the machine is likely
to be subject to vibrations during angular block transitions and rounding is not to be used.
By setting the following machine data, the block transitions are rounded independent of the set
overload factor with G641/G642:
MD20490 $MC_IGNORE_OVL_FACTOR_FOR_ADIS
Continuous-path mode with a reduction in speed according to the overload factor can be
activated in any NC part program block by the modal command G64.
Selecting the exact stop which works on a block-by-block basis enables rounding to be
interrupted (G9).
Continuous-path mode G64 can be deactivated by selecting:
● Modal exact stop G60
● Rounding G641, G642, G643, G644 or G645
Implicit continuous-path mode

If it is not possible to insert rounding blocks in continuous-path mode with rounding G641 due
to the very short block path lengths (e.g. zero-clocked blocks), the mode is switched over to
continuous-path mode G64.
5.3.3 Rounding
Function
The "Rounding" function adds intermediate blocks (positioning blocks) along a programmed
contour (path axes) at non-continuous (angular) block transitions so that the resulting new
block transition is continuous (tangential).
Synchronized axes
The rounding considers not only the geometry axes but also all synchronous axes. Although a
continuous block transition cannot be created for both axis types concurrently for the parallel
travel of path and synchronous axes. In this case, to favor path axes that always travel exactly,
only an approximately continuous block transition is created for synchronous axes.
Basic functions
Rounding for G64

Rounding is performed even when to observe the dynamic-response limits at the block
transition, a speed is required that for G64 exceeds the permitted speed at the block transition
(see Section "Velocity reduction according to overload factor (Page 455)" "Overload factor").
Impact on synchronization conditions

The use of rounding shortens the programmed blocks between which the rounding block(s) are
added. The programmed block boundary disappears and are then no longer available as
criterion for any synchronization conditions (e.g. auxiliary function output parallel to motion,
stop at block end).
Note
We recommend that when the "Rounding" function is used, synchronization conditions apply to
the end of the block before the rounding location rather than the end of the inserted rounding
block. The following block would then not be started and with a stop at the block end, the
contour of the following block can still be changed manually.
Exceptions
In the following cases, no rounding occurs at the block transition, for example, between the N10
blocks after N20, i.e. no rounding block is added:
Implicit stopping of the traversing motion

Possible causes:
● Auxiliary function output active before the traversing motion for N20
● N20 does not contain any traversing motion for path axes
● In N20, an axis that was previously a positioning axis traverses as a path axis for the first time
● In N20, an axis that was previously a path axis traverses as a positioning axis for the first time
● Geometry axes traverse in N10 but not in N20
● Geometry axes traverse in N20 but not in N10
● Activation of thread-cutting G33 in N20
● Change from BRISK and SOFT
● Transformation-relevant axes are not completely assigned to the path motion (e.g. for
oscillation axes, positioning axes).
Basic functions
The insertion of the rounding block would slow part program machining overproportionally
Possible causes:
● A program or program section consists of a number of very short traversal blocks (≈ 1
interpolator cycle / traversal block; because each traversal block requires at least one
interpolator cycle, the inserted intermediate block would almost double the machining time)
● G64 (path control operation without rounding) without speed reduction active for block
change
● The parameterized overload factor (MD32310 $MA_MAX_ACCEL_OVL_FACTOR) permits
the traversal of the programmed contour without the path speed needing to be reduced. See
also: MD20490 $MC_IGNORE_OVL_FACTOR_FOR_ADIS
Path parameters inhibit the rounding

Possible causes:
● G641 (path control operation with rounding in accordance with the path criterion) is active
but rapid traverse is active (G0) AND ADISPOS == 0 (rounding separation for G0)
● G641 (path control operation with rounding in accordance with the path criterion) is active
but rapid traverse is not active AND ADIS == 0 (rounding separation for path functions G1,
G2, G3, ...)
● G642 or G643 (path control operation with rounding while observing defined tolerances) is
active but all tolerances == zero
N10 or N20 does not contain traversing motion (zero block).

Normally no zero blocks are created. Exceptions:
● Active synchronous action
● Program jumps
Impact on synchronization conditions

The programmed blocks between which the rounding contour is added are shortened during
rounding. The original programmed block boundary disappears and is then no longer available
for any synchronization conditions (e.g. auxiliary function output parallel to motion, stop at block
end).
Note
We recommend that when the "Rounding" function is used, synchronization conditions apply to
the end of the block before the rounding location rather than the end of the inserted rounding
block. The following block would then not be started and with a stop at the block end, the
contour of the following block can still be changed.
Basic functions
5.3.3.1 Rounding according to a path criterion (G641)
Function
In continuous-path mode with rounding according to a path criterion, the size of the rounding
area is influenced by the path criteria ADIS and ADISPOS.
The path criteria ADIS and ADISPOS describe the maximum distances which a rounding block
can occupy before and after a block.
3DWKFULWHULRQ
$',6 3URJUDPPHG
$',6326 LQWHUPHGLDWHSRLQWLQEORFN
3URJUDPPHGLQSXWEORFN 3URJUDPPHGRXWSXW
EORFN
Note
Acute angles produce rounding curves with a large degree of curvature and therefore cause a
corresponding reduction in velocity.
Note
ADISPOS is programmed in the same way as ADIS, but must be used specifically for
movements in rapid traverse mode G0.
Scope of the path criterion

● ADIS or ADISPOS must be programmed. If the default is "zero", G641 behaves like G64.
● If only one of the blocks involved is rapid traverse G0, the smaller rounding distance applies.
Basic functions
● If a very small value is used for ADIS, the controller must make sure that every interpolated
block, even an intermediate rounding block, contains at least one interpolation point. The
maximum path velocity is thereby limited to ADIS / interpolator cycle.
● Irrespective of ADIS and ADISPOS, the rounding area is limited by the block length.
In blocks with short distances (distance < 4* ADIS and < 4 * ADISPOS respectively), the
rounding distance is reduced so that a traversable part of the original block is retained. The
remaining length depends on the axis path and is approximately 60% of the distance still to
be traversed in the block. ADIS or ADISPOS is therefore reduced to the remaining 40% of
the distance to be traversed. This algorithm prevents a rounding block being inserted for a
very small change in contour. In this case, switchover to continuous-path mode G64 is
automatic until rounding blocks can be inserted again.
1RVPRRWKLQJ
1
1
1
$',6
5HPDLQLQJSDWK
1
1
6WDUWRIEORFN1
1
$',6 $',6
5HPDLQLQJSDWK 5HPDLQLQJSDWK
1 1
Figure 5-4 Path with limitation of ADIS
Continuous-path mode with rounding based on a path criterion can be activated in any NC part
program block by the modal command G641. Before or on selection, the path criteria ADIS/
ADISPOS must be specified.
interrupted (G9).
Continuous-path mode with rounding based on a path criterion (G641) can be deactivated by
selecting:
● Modal exact stop (G60)
● Continuous-path mode G64, G642, G643, G644 or G645
Program example
N1 G641 Y50 F10 ADIS=0.5 ; Continuous-path mode with rounding based on a path
criterion (rounding clearance: 0.5 mm)
N2 X50
Basic functions

N3 X50.7
N4 Y50.7
N5 Y51.4
N6 Y51.0
N7 X52.1
5.3.3.2 Rounding in compliance with defined tolerances (G642/G643)
Function
In continuous-path mode involving rounding in compliance with defined tolerances, the
rounding normally takes place while adhering to the maximum permissible path deviation.
Instead of these axis-specific tolerances, the maintenance of the maximum contour deviation
(contour tolerance) or the maximum angular deviation of the tool orientation (orientation
tolerance) can be configured.
Activation
Continuous-path mode with rounding in compliance with defined tolerances can be activated in
any NC part program block by the modal command G642 or G643.
interrupted (G9).
Continuous-path mode with rounding in compliance with defined tolerances (G642/G643) can
be deactivated by selecting:
● Continuous-path mode G64, G641, G644 or G645
Differences between G642 - G643

With regard to their rounding behavior, commands G642 and G643 differ as follows:
G642 G643
With G642, the rounding path is determined on the In the case of G643, each axis may have a differ‐
basis of the shortest distance for rounding all axes. ent rounding path. The rounding travels are taken
This value is taken into account when generating a into account axis-specifically and block-internally
rounding block. (⇒ no separate rounding block).
With G642, the rounding area results from the Very different specifications for the contour toler‐
smallest tolerance setting. ance and the tolerance of the tool orientation can
only have effect with G643.
Parameterization
Maximum path deviation
Basic functions
The maximum path deviation permitted with G642/G643 is set for each axis in the machine
data:
MD33100 $MA_COMPRESS_POS_TOL
Contour tolerance and orientation tolerance
The contour tolerance and orientation tolerance are set in the channel-specific setting data:
SD42465 $SC_SMOOTH_CONTUR_TOL (maximum contour deviation)
SD42466 $SC_SMOOTH_ORI_TOL (maximum angular deviation of the tool orientation)
The settings data can be programmed in the NC program and can in this way be specified
differently for each block transition.
Note
The setting data SD42466 $SC_SMOOTH_ORI_TOL is effective only in active orientation
transformation.
Rounding behavior
Rounding behavior with G642 and G643 is configured via the machine data:
MD20480 $MC_SMOOTHING_MODE (rounding behavior with G64x)
The units positions (E) define the behavior for G643, the tens positions (Z) the behavior for
G642:
Value E or Z Meaning
0 All axes:
Rounding by maintaining the maximum permitted path deviation:
1 Geometry axes:
Rounding by maintaining the contour tolerance:
SD42465 $SC_SMOOTH_CONTUR_TOL
Remaining axes:
2 Geometry axes:
Rounding by maintaining the orientation tolerance:
SD42466 $SC_SMOOTH_ORI_TOL
Remaining axes:
Basic functions
Value E or Z Meaning
3 Geometry axes:
Rounding by maintaining the contour tolerance and the orientation tolerance:
SD42465 $SC_SMOOTH_CONTUR_TOL
SD42466 $SC_SMOOTH_ORI_TOL
Remaining axes:
4 All axes:
The rounding length programmed with ADIS or with ADISPOS is used (as in case of
G641).
Any axis-specific tolerance or contour and orientation tolerance specifications are
ignored.
Profile for limit velocity

The use of a velocity profile for rounding in compliance with defined tolerances is controlled via
the hundreds position in MD20480:
Value Meaning
< 100: A profile of the limit velocity is calculated within the rounding area, based on the defined
maximum values for acceleration and jerk on the participating axes or path.
This can lead to an increase in the path velocity in the rounding area and therefore to the
acceleration of the participating axes.
≥100: A profile of the limit velocity is not calculated for rounding blocks with G641/G642. A
constant velocity limit is specified instead.
This prevents the participating axes being accelerated into the rounding area during
rounding with G641/G642. However, in certain cases, this setting can cause the rounding
blocks to be traversed too slowly, especially in large rounding areas.
1xx: No velocity profile for G641
2xx: No velocity profile for G642
Note
MD28530 $MC_MM_PATH_VELO_SEGMENTS (number of memory elements for limiting the
path velocity)
Restriction for protection zones with active radius compensation and tool orientation:
Although tool radius compensation is applied for a tool orientation, which is not perpendicular
to one of the three datum planes of the basic coordinate system, the protection zones are not
rotated onto the corresponding plane.
For G643 the following must apply:
MD28530 $MC_MM_PATH_VELO_SEGMENTS > 0 (number of memory elements for limiting
the path velocity)
If this condition is met, then it must be applicable for all axes:
Basic functions
MD35240 $MC_ACCEL_TYPE_DRIVE = FALSE (acceleration characteristic DRIVE for axes

on/off)
5.3.3.3 Rounding with maximum possible axial dynamic response (G644)
Function
Maximizing the dynamic response of the axes is key to this type of continuous-path mode with
smoothing.
Note
Smoothing with G644 is only possible under the following conditions:
● All of the participating axes contain only one linear motion in the two blocks under
consideration.
● A kinematic transformation is not active.
If a participating axis contains a polynomial (polynomial programmed, spline active,
compressor active) or a kinematics transformation is active (PTP travel temporarily deactivates
a kinematics transformation), the block transition is smoothed with G642.
Activation
Continuous-path mode with smoothing with the maximum possible axial dynamic response can
be activated in any NC part program block by the modal command G644.
Selecting the exact stop which works on a block-by-block basis enables smoothing to be
interrupted (G9).
Continuous-path mode with smoothing with the maximum possible axial dynamic response
(G644) can be deactivated by selecting:
Smoothing behavior with G644 is configured via the thousands and tens of thousands places
in the machine data:
MD20480 $MC_SMOOTHING_MODE (smoothing behavior with G64x)
Value Meaning
Thousand's place:
0xxx: When smoothing with G644, the maximum deviations for each axis specified by the follow‐
ing machine data are respected:
If the dynamics of the axis permit, then any specified tolerance is not utilized.
Basic functions
Value Meaning
1xxx: Specification of the maximum smoothing path by programming ADIS=...
or ADISPOS=... (as for G641).
2xxx: Input the maximum possible frequencies of each axis in the smoothing area using the ma‐
chine data:
MD32440 $MA_LOOKAH_FREQUENCY (smoothing frequency for LookAhead)
The smoothing area is defined so that no frequencies in excess of the specified maximum
can occur while the smoothing motion is in progress.
3xxx: Any axis that has a velocity jump at a corner traverses around the corner with the maximum
possible dynamic response (maximum acceleration and maximum jerk).
SOFT:
If SOFT is active, the maximum acceleration and the maximum jerk of each axis are main‐
tained.
BRISK:
If BRISK is active, only the maximum acceleration and not the maximum jerk of each axis is
maintained.
With this setting, neither the maximum deviations nor the smoothing distance are checked.
The resulting deviations or smoothing distances are determined exclusively by the dynamic
limits of the respective axis and the current path velocity.
4xxx: As in case of 0xxx, the maximum deviations of each axis specified with the following ma‐
chine data are used:
Contrary to 0xxx, the specified tolerance is also utilized, if possible. Therefore, the axis does
not attain its maximum possible dynamics.
5xxx: As in case of 1xxx, the maximum possible smoothing path is specified through programming
of ADIS=... or ADISPOS=... respectively.
Contrary to 1xxx, the specified smoothing path is also utilized, if possible. Therefore, the
axes involved do not attain their maximum possible dynamics.
Ten thousands digit

0xxxx The velocity profiles of the axes in the smoothing area are determined without jerk limiting
for BRISK and with jerk limiting for SOFT.
1xxxx The velocity profiles of the axes in the smoothing area are always determined with jerk
limiting, regardless of whether BRISK or SOFT is active.
When specifying the maximum axial deviations (MD33100 $MA_COMPRESS_POS_TOL) or

the maximum smoothing distance (ADIS / ADISPOS) the available smoothing path is normally
not used, if permitted by the dynamic response of the axes involved. Through this, the length
of the smoothing path depends on the active path feedrate. In case of lower path speeds, one
gets lower deviations from the programmed contours. However, it can be set that in these cases
the specified maximum axial deviation or the specified smoothing distance is utilized, if
possible. In this case the deviations depend on the programmed contour independent of the
programmed path feedrate.
Note
Apart from the ones mentioned, the following limitation can also become active additionally:
The smoothing distance cannot exceed half the length of the original participating blocks.
Basic functions
Jerk limitation
The smoothing of the velocity jump on each axis and thus the shape of the smoothing path
depends on whether an interpolation is performed with or without jerk limitation.
Without jerk limitation the acceleration of each axis reaches its maximum value in the entire
smoothing area:
9HORFLW\
7LPH
Q
LR
VLW
3R
With jerk limitation, the jerk of each axis is limited to its maximum value within the smoothing
area. The smoothing motion thus generally consists of 3 phases(① ... ③):
9HORFLW\
7LPH
Q
LR
VLW
3R

① During phase 1, each axis builds up its maximum acceleration. The jerk is constant and equal to
the maximum possible jerk on the respective axis.
② During phase 2, the maximum permissible acceleration is applied.
③ During phase 3, which is the last phase, the acceleration of each axis is reduced back to zero with
the maximum permissible jerk.
5.3.3.4 Rounding of tangential block transitions (G645)
Function
In continuous-path mode with rounding, rounding blocks are also only generated on tangential
block transitions if the curvature of the original contour exhibits a jump in at least one axis.
Basic functions
The rounding motion is defined here so that the acceleration of all axes involved remains
smooth (no jumps) and the parameterized maximum deviations from the original contour
(MD33120 $MA_PATH_TRANS_POS_TOL) are not exceeded.
In the case of angular, non-tangential block transitions, the rounding behavior is the same as
with G642 (see Section "Rounding in compliance with defined tolerances (G642/G643)
(Page 462)").
Continuous-path mode with rounding of tangential block transitions can be activated in any NC
part program block by the modal command G645.
interrupted (G9).
Continuous-path mode with rounding of tangential block transitions (G645) can be deactivated
by selecting:
Comparison between G642 and G645

When rounding with G642, the only block transitions rounded are those which form a corner,
i.e. the velocity of at least one axis jumps. However, if a block transition is tangential, but there
is a jump in the curvature, no rounding block is inserted with G642. If this block transition is
traversed with finite velocity, the axes experience some degree of jump in acceleration which
(with the jerk limit activated!) may not exceed the parameterized limit (MD32432
$MA_PATH_TRANS_JERK_LIM). Depending on the level of the limit, the path velocity at the
block transition may be greatly reduced as a result. This constraint is avoided by using G645
because the rounding motion is defined here in such a way that no jumps occur in acceleration.
Parameterization
The following machine data indicates the maximum permissible path deviation for each axis
during rounding with G645:
MD33120 $MA_PATH_TRANS_POS_TOL
This value is only of relevance to tangential block transitions with variable acceleration. When
angular, non-tangential block transitions are rounded, (as with G642) the tolerance from
MD33100 $MA_COMPRESS_POS_TOL becomes effective.
See also
Free-form surface mode: Basic functions (Page 494)
Basic functions
5.3.3.5 Rounding and repositioning (REPOS)

If the machining in the area of the rounding contour is interrupted, a REPOS operation cannot
be used to position again directly on the rounding contour. In this case, positioning can be made
only on the programmed contour.
Example
Programmed: Two traversing blocks N10 and N20 with programmed rounding G641.
The traversing motion is interrupted in the rounding area. The axes, e.g. manually, are then
traversed to the REPOS start point. Depending on the selected REPOS mode, the
repositioning on the contour is made at the points ①, ② or ③.
5(326VWDUWLQJSRLQW
50%%/
50,%/50(%/
%UHDNSRLQW
501%/
1

7UDYHUVLQJ
GLUHFWLRQ
6PRRWKLQJVHW
1
RMBBL Repositioning at the start of the interrupted traversal block

RMIBL Repositioning at the interruption location
RMEBL Repositioning at the end of the interrupted traversal block
RMNBL Repositioning at the next contour point
① Block start N10
② To the REPOS start point of the next contour point
③ Block end N10 / block start N20
Basic functions
5.3.4 LookAhead
5.3.4.1 Standard functionality
Function
LookAhead is a function which is active in continuous-path mode (G64, G64x) and determines
a foreseeable velocity control for multiple NC part program blocks over and beyond the current
block.
Note
LookAhead is only available for path axes, not for spindles and positioning axes.
If a part program contains consecutive blocks with very small paths, only one velocity is
reached per block without LookAhead, enabling deceleration of the axes at the end of the block
while maintaining acceleration limits. This means that the programmed velocity is not reached
at all. With LookAhead, however, it is possible to implement the acceleration and deceleration
phase over multiple blocks with approximately tangential block transitions, thereby achieving a
higher feedrate with shorter distances.
)HHGUDWH
*3UHGLFWLYHYHORFLW\FRQWURO
SURJUDPPHG
)
*&RQVWDQWYHORFLW\SKDVHFDQQRWEH
UHDFKHG
1 1 1 1 1 1 1 1 1 1 1 1 %ORFNSDWK
Figure 5-5 Velocity control with short distances and exact stop G60 or continuous-path mode G64 with
LookAhead
Deceleration to velocity limits is possible with LookAhead such that violation of the acceleration
and velocity limit is prevented.
LookAhead takes plannable velocity limits into consideration such as:
● Exact stop at block end
● Velocity limit in the block
● Acceleration limit in the block
● Velocity limit on block transition
● Synchronization with block change at block transition.
Basic functions
Mode of operation
LookAhead carries out a block-specific analysis of velocity limits and specifies the required
brake ramp profile based on this information. LookAhead is adapted automatically to block
length, braking capacity and permissible path velocity.
For safety reasons, the velocity at the end of the last prepared block must initially be assumed
to be zero because the next block might be very small or be an exact-stop block, and the axes
must have been stopped by the end of the block.
With a series of blocks with high set velocity and very short paths, the speed can be increased
in each block depending on the velocity value currently calculated by the LookAhead function
in order to achieve the required set velocity. After this it can be reduced so that the velocity at
the end of the last block considered by the LookAhead function can be zero. This results in a
serrated velocity profile (see the following fig.) which can be avoided by reducing the set
velocity or increasing the number of blocks considered by the LookAhead function.
Y
9VHWSRLQW
9DFW
1 1 1 1 1 1 W
Figure 5-6 Example for modal velocity control (number of blocks considered by the LookAhead
function = 2)
LookAhead is activated by selecting continuous-path mode G64, G641, G642, G643, G644 or
G645.
Selecting the exact stop which works on a non-modal basis enables rounding to be interrupted
(G09).
LookAhead is deactivated by selecting the modal exact stop (G60).
Parameterization
Number of blocks
To achieve reliable axis traversal in continuous-path mode, the feedrate must be adapted over
several blocks. The number of blocks considered by the LookAhead function is calculated
automatically and can, if required, be limited by a machine data. The default setting is "1", which
means that LookAhead only considers the following block for velocity control.
Because LookAhead is especially important for short blocks (relative to the deceleration path),
the number of blocks required is of interest for LookAhead braking. It is sufficient to consider the
Basic functions
path length to be equal to the deceleration path that is required to brake from maximum velocity
to standstill.
For a machine with a low axial acceleration of a = 1 m/s2 and a high feedrate of vpath = 10 m/min,
the following number of nLookAhead blocks are allocated to the controller where it has an attainable
block cycle time of TB = 10 ms:
nLookAhead = Deceleration path/Block length = ( vpath2 / (2a)) / (vpath * TB) = 9
Considering these conditions, it is advisable to adapt the feedrate over 10 blocks. The number
of blocks entered for the LookAhead function forecast does not change the LookAhead
algorithm and memory requirement.
Since the machining velocity is very often set to a lower value than the maximum velocity in a
program, more blocks than are required would be predicted, overloading the processor
unnecessarily. For this reason, the required number of blocks is derived from the velocity which
is calculated from the following multiplication:
● Programmed velocity * MD12100 $MN_OVR_FACTOR_LIMIT_BIN
(when using a binary-coded feedrate override switch)
● Programmed velocity * MD12030 $MN_OVR_FACTOR_FEEDRATE[30]
(when using a Gray-coded feedrate override switch)
The value for MD12100 or the 31st override value for MD12030 defines the dynamic response
reserves which the velocity control provides for when the path feedrate is overshot.
Note
The 31st override value for MD12030 should correspond to the highest override factor which is
actually used.
Note
The number of blocks considered by the LookAhead function is limited by the possible number
of NC blocks in the IPO buffer.
Velocity profiles
In addition to the fixed, plannable velocity limitations, LookAhead can also take account of the
programmed velocity. This makes it possible to achieve a lower velocity by applying
LookAhead beyond the current block.
● Determination of the following block velocity
One possible velocity profile contains the determination of the following block velocity.
Using information from the current and the following NC block, a velocity profile is calculated
from which, in turn, the required velocity reduction for the current override is derived.
The calculated maximum value of the velocity profile is limited by the maximum path velocity.
With this function it is possible to initiate a speed reduction in the current block taking
override into account such that the lower velocity of the following block can be achieved. If
the reduction in velocity takes longer than the travel time of the current block, the velocity is
further reduced in the following block. Velocity control is only ever considered for the
following block.
The function is activated via the machine data:
MD20400 $MC_LOOKAH_USE_VELO_NEXT_BLOCK
Basic functions
Value Meaning
TRUE Function active
FALSE Function not active
Basic functions
● Definition of override points

If the velocity profile of the following block velocity is not sufficient because, for example,
very high override values (e.g. 200%) are used or a constant cutting rate G96/G961 is
active, with the result that the velocity must be further reduced in the following block,
LookAhead provides a way of reducing the programmed velocity over several NC blocks.
By defining override points, LookAhead calculates a limiting velocity profile for each value.
The required velocity reductions for the current override are derived from these profiles.
The calculated maximum value of the velocity profile is limited by the maximum path velocity.
The upper point should cover the velocity range that will be reached by the maximum value
set in the machine data:
MD12030 $MN_OVR_FACTOR_FEEDRATE[n] (evaluation of the path feedrate override
switch)
It can also be reached via the value of the machine data:
MD12100 $MN_OVR_FACTOR_LIMIT_BIN (limit for binary-coded override switch)
In this way, a reduction of the velocity continuing into the block in which it is programmed can
be avoided.
If velocity reductions across block boundaries are required at a 100% override, a point
should be set in the lower override range as well.
The number of override points used per channel is specified in the machine data:
MD20430 $MC_LOOKAH_NUM_OVR_POINTS (number of override switch points for
LookAhead)
The associated points are stored in the machine data:
MD20440 $MC_LOOKAH_OVR_POINTS (override switch points for LookAhead)
Example:
Limiting velocity characteristics, whereby:
– Override = 50%, 100% or 150%
– Number of LookAhead blocks = 4
– MD20430 $MC_LOOKAH_NUM_OVR_POINTS = 2
– MD20440 $MC_LOOKAH_OVR_POINTS = 1.5, 0.5
Basic functions
– MD20400 $MC_LOOKAH_USE_VELO_NEXT_BLOCK = 1
Y
YtPD[
9HORFLW\SURILOH
2YHUULGH
2YHUULGH 3URJUDPPHGVHWSRLQW
9HORFLW\SURILOH
9HORFLW\SURILOH
2YHUULGH
1 1 1 1 1 V
A combination of both procedures (determination of following block velocity and determination

of override points) can be used to calculate the velocity profiles and is generally advisable
because the preset machine data for these functions already takes the widest range of override-
dependent velocity limits into account.
Note
If neither of the procedures has been activated, the setpoint velocity is always applied in the
current block.
Note
Plannable velocity limits restrict override-specific velocity limits.
Relief factor with block cycle problems

Block cycle problems are encountered in cases where the traversing distances of the NC
blocks to be processed are so short that the LookAhead function has to reduce the machine
velocity to provide enough time for block processing. In this situation, constant braking and
acceleration of path motion may occur.
Velocity fluctuations of this type can be dampened by specifying a relief factor:
MD20450 $MC_LOOKAH_RELIEVE_BLOCK_CYCLE (relieving factor for the block cycle
time)
Basic functions
Boundary conditions
Axis-specific feed stop/axis disable
Axis-specific feed stop and axis-specific axis disable are ignored by LookAhead.
If an axis is to be interpolated that should on the other hand be made stationary by axis-specific
feed stop or axis disable, LookAhead does not stop path motion before the block in question but
decelerates in the block itself.
If this response is not wanted, an axis-specific feed stop can be transferred to a channel via the
PLC to stop the path immediately (see also Function Manual Monitoring and Compensating,
Section Clamping monitoring).
5.3.4.2 Free-form surface mode: Extension function
Function
The "Free-form surface mode: Extension function" is an extension of the Look Ahead standard
functionality and is used to calculate the path velocity profile during free-form surface
machining (see also Section "Free-form surface mode: Basic functions (Page 494)").
Its use optimizes the continuous-path mode as follows:
● Symmetry between the acceleration and deceleration profiles
● Uniform acceleration process, even with changing jerk or acceleration limits
● Uniform acceleration process of target velocity profiles, irrespective of the degree to which
they can or cannot be started with the specified dynamic response limit
● Look Ahead braking to lower setpoint velocities
Uniformity and compliance with the dynamic response limit guarantee that the setpoint velocity
profiles are smoothed to a homogeneous velocity profile on the part. This serves to minimize
the effect of following errors on the quality of the surface.
Advantages
● Greater uniformity in the surface of the workpiece
● Lower machine load
Applications
The "Free-form surface mode: Extension function" is used to machine workpieces which
primarily comprise free-form surfaces.
Note
As better results are not achieved for standard machining applications, standard Look Ahead
functionality should be used in these cases.
Basic functions
Activation
This function is only effective with the following conditions:
● AUTOMATIC mode active
● "Acceleration with jerk limitation (SOFT)" mode active
Parameterization
Working memory
The memory for the "Free-form surface mode: Extended function" is configured via the
machine data:
MD28533 $MC_MM_LOOKAH_FFORM_UNITS = <value>
The required memory depends on the part program, the block lengths, the axis dynamic
response, as well as on an active kinematic transformation.
The following setting applies as a guideline for machining free-form surfaces: MD28533 = 18
Note
Due to the additional storage requirements, MD28533 should only be set for the channels in
which free-form surfaces are being machined.
Number of NC blocks in the IPO buffer

It is generally advisable to significantly increase the configured number of NC blocks in the
interpolation buffer when using the "Free-form surface mode: Extension function":
MD28060 $MC_MM_IPO_BUFFER_SIZE > 100
If the block memory capacity is too low, this may diminish the uniformity of the path-velocity
profile.
The function can be switched on or off independently for every dynamic response mode (see
Section "Dynamic response mode for path interpolation (Page 492)"):
MD20443 $MC_LOOKAH_FFORM[<n>]= <value>
Index <n> Dynamic response mode <Value> Free-form surface mode: Extension
function
0 Standard dynamic response set‐ 0 Off
tings (DYNNORM) 1 On
1 Positioning mode, tapping 0 Off
(DYNPOS) 1 On
2 Roughing (DYNROUGH) 0 Off
1 On
3 Semi-finishing (DYNSEMIFIN) 0 Off
1 On
Basic functions
Index <n> Dynamic response mode <Value> Free-form surface mode: Extension
function
4 Finishing (DYNFINISH) 0 Off
1 On
5 Smooth-finishing (DYNPREC) 0 Off
1 On
The "Free-form surface mode: Extension function" is typically only active if the "Free-form
surface mode: Basic functions" are also active. Therefore, the settings in
MD20443 $MC_LOOKAH_FFORM[<n>] should correspond to the settings in
MD20606 $MC_PREPDYN_SMOOTHING_ON[<n>].
The standard Look Ahead functionality is active in the dynamic response modes in which the
"Free-form surface mode: Extension function" is switched off.
Programming
Generally speaking, the "Free-form surface mode: Extension function" becomes effective as a
result of a change in the dynamic response mode in the part program.
Example
The following parameters are assumed:
MD20443 $MC_LOOKAH_FFORM[0] = 0
Change of the dynamic response mode in the part program:

N10 DYNPOS ; Activate DYNPOS dynamic response
mode.
Standard Look Ahead functionality is
active in the DYNPOS dynamic re-
sponse mode.
...
N100 G17 G54 F10000
N101 DYNFINISH ; Activate DYNFINISH dynamic re-
sponse mode.
The "Free-form surface mode: Exten-
sion functions" are active in the
DYNFINISH dynamic response mode.
N102 SOFT G642
N103 X-0.274 Y149.679 Z100.000 G0
N104 COMPCAD
Basic functions

...
N1009 Z4.994 G01
N10010 X.520 Y149.679 Z5.000
N10011 X10.841 Y149.679 Z5.000
N10012 X11.635 Y149.679 Z5.010
N10013 X12.032 Y149.679 Z5.031
M30
Note
When switching between the standard Look Ahead functionality and the "Free-form surface
mode: Extension function" or vice versa, continuous-path mode is interrupted by an interpolator
stop.
Boundary conditions
Automatic changeover
The following functions result in an automatic switchover to standard Look Ahead functionality:
● Thread cutting/tapping (G33, G34, G35, G331, G332, G63)
● Path master-value coupling
● Punching, nibbling
● Cartesian PTP travel
The "Free-form surface mode: Extension function" is then switched on again automatically.
Using the commands of G group 15 (feed types)

The following feed types are not recommended in conjunction with the "Free-form surface
mode: extension function" function:
● Feedrate per revolution (G95, G96, G97, etc.)
● Inverse-time feedrate (G93)
Use of FLIN
The FLIN feedrate profile cannot be used in conjunction with the "Free-form surface mode:
extension function" function:
Influence of feedrate overrides

Feedrate overrides (via a machine control panel, $AC_OVR, ...) can extend the traverse time
over standard Look Ahead functionality considerably.
Interaction with rapid traverse motion (G0)

G0 blocks which are interspersed during free-form surface machining do not switch the Look
Ahead functionality over (from the "Free-form surface mode: Extended function" to the
standard Look Ahead functionality or vice versa). This means that even though the standard
dynamic response setting (DYNNORM) is effective with G0, the standard Look Ahead
Basic functions
5.4 Dynamic adaptations
functionality which is preset for DYNNORM (→ MD20443 $MC_LOOKAH_FFORM) does not

automatically become effective as well. By retaining the Look Ahead functionality which is
currently active, a more homogeneous velocity profile is achieved, particularly since G0 and
polynomial blocks are usually smoothed and connected by rounding.
5.4.1 Smoothing of the path velocity
Introduction
The velocity control function utilizes the specified axial dynamic response. If the programmed
feedrate cannot be achieved, the path velocity is brought to the parameterized axial limit values
and the limit values of the path (velocity, acceleration, jerk). This can lead to repeated braking
and acceleration on the path.
If a short acceleration takes place during a machining function with high path velocity, and is
thus followed almost immediately by braking, the reduction in the machining time is only
minimal. Acceleration of this kind can, however, have undesirable effects if, for example, it
results in machine resonance.
In some applications in mold making, especially in the case of high-speed cutting, it is desirable
to achieve a constant path velocity. In these cases, it can therefore be reasonable to sacrifice
transient acceleration processes in favor of a smoother tool path velocity.
Function
If the "smoothing the path velocity" function is active, a smoothing factor, which determines the
maximum permissible productivity loss, takes effect with a view to achieving smoother path
velocity control: Acceleration processes which contribute less than this factor to a shorter
program runtime are not performed. Account is only taken of acceleration processes whose
frequencies lie above the configurable limit frequencies of of the axes involved.
Benefits:
● Avoidance of excitations of possible machine resonance due to continuous, transient
braking and acceleration processes (in the area of less IPO cycles).
● Avoidance of constantly varying cutting rates due to acceleration which brings no significant
shortening of the program running time.
Basic functions
Note
The smoothing of the path velocity does not lead to contour errors.
Variations in axis velocity due to curvatures in the contour at constant path velocity may
continue to occur and are not reduced with this function.
Variations in path velocity due to the input of a new feedrate are not changed either. This
remains the responsibility of the programmer of the subprogram.
Requirements
● The smoothing of the path velocity is only effective in continuous-path mode with
LookAhead over multiple blocks with SOFT and BRISK. Smoothing is not effective with G0.
● The controller's cycle times must be configured in such a way that preprocessing can
prepare sufficient blocks to enable an acceleration process to be analyzed.
The "smoothing of the path velocity" function is activated/deactivated with the machine data:
MD20460 $MC_LOOKAH_SMOOTH_FACTOR (smoothing factor for LookAhead)
Value Meaning
0.0 Smoothing of the path velocity not active (default)
>0 Smoothing of the path velocity active
A change in the MD setting is only made effective through NEW CONF.
Parameterization
Smoothing factor
The smoothing factor is set via the channel-specific machine data:
The percentage value defines how much longer a processing step without accelerations/
decelerations may be than the corresponding step with accelerations/decelerations.
This would be a "worst-case" value, if all accelerations within the part program, except the initial
approach motion, were smoothed. The actual extension will always be smaller, and may even
be 0, if the criterion is not met by any of the accelerations. Values between 50 and 100% may
also be entered without significantly increasing the machining time.
Consideration of the programmed feed
The path velocity can be smoothed with or without taking the programmed feedrate into
consideration. The selection is made via the machine data:
Basic functions
MD20462 $MC_LOOKAH_SMOOTH_WITH_FEED (path smoothing with programmed

feedrate)
Value Meaning
0 Programmed feedrate is not taken into consideration.
1 Programmed feedrate is considered (default setting).
When considering the programmed feedrate, the specified smoothing factor (see MD20460) is
maintained better when the override is 100%.
Axis-specific limit frequencies
The axis-specific limit frequencies are defined via the machine data:
Acceleration and deceleration processes, which run with a high frequency, are smoothed
depending upon the parameterization of the following machine data or else are reduced in
dynamics:
MD20465 $MC_ADAPT_PATH_DYNAMIC (adaptation of the dynamic path response)
For further information on MD20465, see Section "Adaptation of the dynamic path response
(Page 483)".
Note
If vibrations are generated in the mechanical system of an axis and if the corresponding
frequency is known, MD32440 should be set to a value smaller than this frequency.
The needed resonance frequencies can be calculated using the built-in measuring functions.
Mode of operation
The minimum value for MD32440 is calculated as fpath on the basis of the axes involved in the
path. For the smoothing only those acceleration processes are taken into consideration, in
which the start and the end velocity of this motion are reached within the time given below:
t = t2 - t1 = 2 / fpath
These acceleration processes are dispensed with if the resulting extension in the processing
time does not exceed the limit specified in excess of the smoothing factor (MD20460).
Example
MD20460 $MC_LOOKAH_SMOOTH_FACTOR = 10%
MD32440 $MA_LOOKAH_FREQUENCY[AX1] = 20 Hz
The path involves the three axes X = AX1, Y = AX2, Z = AX3.
Basic functions
The minimum value of MD32440 for these three axes is thus 10 Hz. This means that any
acceleration, which is completed within a period of t2 - t1 = 2/10 Hz = 200 ms, is examined. The
time t2 is the time it takes to reach velocity v1 again following an acceleration process starting
from velocity v1. The extending of the execution time is also only considered within this range.
If the time t2 - t1 is greater than 200 ms or if the additional program execution time t3 - t2 is more
than 10% (= MD20460) of t2 - t1, the following time characteristic applies:
Y
Y
W W W
Figure 5-7 Characteristic of time-optimum path velocity (without smoothing)
If, however, the time t2 - t1 is less than 200 ms or if the additional program execution time t3 - t2
is no more than 10% of t2 - t1, the following time characteristic applies:
Y
Y
W
W W W
Figure 5-8 Characteristic of the smoothed path velocity
5.4.2 Adaptation of the dynamic path response
Function
Highly dynamic acceleration and deceleration processes during machining can cause
excitation of mechanical vibrations of machine elements and consequently a reduction of the
surface quality of the workpiece.
Basic functions
The dynamic response of the acceleration and deceleration processes can be adapted to the
machine conditions using the "adaptation of the dynamic path response" function.
Note
The "adaptation of the dynamic path response" function only concerns the resulting path and
not the deceleration and acceleration processes of the individual axes involved in the path. For
this reason, critical deceleration and acceleration processes of the axes with respect to the
excitation of mechanical vibrations can occur due to discontinuous contour profiles or kinematic
transformations, even with a constant path velocity profile.
Effectiveness
The "adaptation of the dynamic path response" function is only effective during path motions:
● Continuous-path mode (G64, G64x)
In continuous-path mode, the optimal effect of the dynamic response adaptation is attained
with an active 100% override. Considerable deviations from this value or functions that
cause the path axes to decelerate (e.g. auxiliary function outputs to the PLC) greatly reduce
the desired action.
● Exact stop (G60)
In addition, the "adaptation of the dynamic path response" function is not active during path
motions:
● Programmed rapid traverse (G0)
● Changes in the override value
● Stop requests during motion (e.g. NC Stop, NC Reset)
● "Velocity-dependent path acceleration" function (DRIVE) is active
The function is activated/deactivated with the machine data:
MD20465 $MC_ADAPT_PATH_DYNAMIC (adaptation of the dynamic path response)
Value Meaning
= 1.0 Dynamic adaptation not active (default setting)
> 1.0 Dynamic adaptation active
When activation takes place, the "smoothing the path velocity" function is always activated
internally in continuous-path mode as well (see Section "Smoothing of the path velocity
(Page 480)").
If the smoothing factor (MD20460 $MC_LOOKAH_SMOOTH_FACTOR) is set to 0%
(= function deactivated; default!), a smoothing factor of 100% is used as a substitute. For a
smoothing factor other than 0%, the set value takes effect.
Basic functions
Parameterization
Adaptation factor of the dynamic path response
Via the adaptation factor of the dynamic path response, temporary changes in the path velocity
are executed with smaller dynamic response limit values.
The adaptation factor is to be set on a channel-specific basis:
● For traversing motions with acceleration without jerk limitation (BRISK) via:
MD20465 $MC_ADAPT_PATH_DYNAMIC[ 0 ]
→ The adaptation factor acts on the acceleration.
● For traversing motions with acceleration with jerk limitation (SOFT) via:
MD20465 $MC_ADAPT_PATH_DYNAMIC[ 1 ]
→ The adaptation factor acts on the jerk.
Axis-specific limit frequencies
The dynamic response limiting should only be active during deceleration and acceleration
processes that trigger mechanical vibrations larger than a specific limiting frequency, thus
causing excitation of machine resonances.
This limit frequency from which the dynamic response limiting activates, is specified on an axis-
specific basis via the machine data:
For further information, see Section "Smoothing of the path velocity (Page 480)".
Mode of operation
During processing and via all the axes involved in the path, the controller cyclically establishes
the minimum of all the limit frequencies to be the limit frequency (f) for the adaptation of the
dynamic response and calculates the relevant time window (tadapt) from this:
tadapt = 1 / f
The size of the relevant time window tadapt determines the further behavior:
1. The time needed to change the velocity is less than tadapt:
The acceleration rates are reduced by a factor > 1 and ≤ the value written in machine data:
MD20465 ADAPT_PATH_DYNAMIC (adaptation of the path dynamics)
The reduction in acceleration rate increases the time taken to change the velocity.
The following cases are different:
– The acceleration rate is reduced with a value less than MD20465 so that the process
lasts for tadapt [s]. The permitted reduction does not need to be fully utilized.
– The acceleration time is reduced with the value written in MD20465. The process lasts
less than tadapt despite the reduced acceleration. The permitted reduction was fully
utilized.
2. The time needed to change the velocity is greater than tadapt:
No dynamic response adaptation is required.
Basic functions
Example
The following example is intended to show the effect of the "adaptation of the dynamic path
response" function on traversing motions with acceleration and without jerk limitation (BRISK).
MD20465 $MC_ADAPT_PATH_DYNAMIC[0] = 1.5

MD20460 $MC_LOOKAH_SMOOTH_FACTOR = 1.0
MD32440 $MA_LOOKAH_FREQUENCY[AX1] = 20 Hz TAX1 = 1/20 Hz = 50 ms
Note
To illustrate the effect of dynamic response adaptation, the value for the smoothing factor
(MD20460) is set to "1", whereby the "smoothing of the path velocity" function is practically
deactivated.

For path motions in which axis AX2 is involved, all deceleration and acceleration processes that
would last less than TAX2 are adapted.
If only axes AX1 and/or AX3 are involved in path motions, all deceleration and acceleration
processes that would last less than TAX1 = TAX3 are adapted.
The relevant time window is marked tadapt... in the figures below.
Basic functions
Y% WDGDSW
Y
WDGDSW
WDGDSW
WDGDSW
W W W W W W W W W
Y%
WDGDSW
Y
WDGDSW
WDGDSW
W W W W W W W W W
Figure 5-9 Path velocity profile optimized for time without smoothing or dynamic adaptation response
Y%
WDGDSW
Y
WDGDSW
WDGDSW
W W W W W W W W W
Figure 5-10 Path velocity profile with adaptation of dynamic path response
Basic functions
Intervals t0 - t1 and t2 - t3: The acceleration process between t0 - t1 and the deceleration
process between t2 - t3 are extended in terms of time to tadapt01
or tadapt23 as a result of the acceleration being adapted.
Interval t4 - t5: The acceleration process between t4 - t5 is executed with an
acceleration reduced by the maximum adaptation factor of
1.5. However, the acceleration process is completed before
time tadapt45.
Interval t6 - t7: The deceleration process between t6 - t7 remains unchanged
as it lasts longer than tadapt67.
5.4.3 Determination of the dynamic response limiting values

In addition to determining the natural frequency of the path axes for assigning parameters to the
axis-specific limit frequencies (MD32440 $MA_LOOKAH_FREQUENCY), the implementation
of the "adaptation of the dynamic path response" function also requires dynamic response
limits to be determined for velocity, acceleration and jerk.
Procedure
The determination of the dynamic response limits for the traversing of path axes by means of
acceleration with jerk limiting (SOFT) is described below. This procedure can be applied by
analogy to the case of acceleration without jerk limiting (BRISK).
1. Deactivate the "adaptation of the dynamic path response" function:
MD20465 $MC_ADAPT_PATH_DYNAMIC[1] = 1
2. Observe the positioning behavior of each path axis at different traversing velocities. When
doing so, set the jerk such that the desired positioning tolerance is maintained.
Note
The higher the traversing velocity from which the positioning process is started, the higher
in general the jerk can be set.
3. Use the maximum permissible jerk determined for the least critical traversing velocity:
MD32431 $MA_MAX_AX_JERK (maximum jerk)
4. Determine the FAPD factor for all of the path axes using:
FAPD = (largest determined jerk) / (smallest determined jerk)
Note
The smallest determined jerk is the value for the jerk during the most critical traversing
velocity.
5. Enter the largest FAPD factor that was determined via all the path axes as the value for the
adaptation factor for the path dynamic response:
MD20465 $MC_ADAPT_PATH_DYNAMIC[ 1 ] = FAPD
Basic functions
5.4.4 Interaction between the "smoothing of the path velocity" and "adaptation of the
path dynamic response" functions
The following examples serve to illustrate the interaction between the "smoothing of the path
velocity" and "adaptation of the path dynamic response" functions in continuous-path mode.
Example 1
Acceleration mode: BRISK
MD32440 $MA_LOOKAH_FREQUENCY[AX1] = 20 TAX1 = 1/20 Hz = 50 ms
Y%
Y
Y
W W W W W W
Figure 5-11 Path velocity profile optimized for time without smoothing or dynamic adaptation response
Y%
Y
W
W
W
W
W
W
Figure 5-12 Path velocity profile with smoothing of the path velocity and adaptation of dynamic path
response
Basic functions
Effects of smoothing of path velocity:
Interval t1 - t2: The acceleration and deceleration process between t1 and t2 does not
take place because the lengthening of the machining time without the
acceleration process to v12 is less than the resulting time if a smoothing
factor of 80% is applied.
Interval t3 - t5: The acceleration and braking profile between t3 and t5 does not fulfill this
condition or takes longer than the parameterized smoothing time
TAxn = 2/20 Hz = 100 ms.
Effects of the dynamic response adaptation:
Interval t3 - t4: The acceleration process between t3 and t4 is shorter than

MIN(TAXn) = 1/20 Hz = 50 ms and is, therefore, executed with an accel‐
eration reduced by an adaptation factor of 3.
Interval up to t1: The acceleration up to t1 left over after path smoothing is stretched to the
time period up to t1' by the dynamic response adaptation.
Note
The example shows that those acceleration or deceleration processes that are not eliminated
by the smoothing of the path velocity can be subsequently optimized by adapting the dynamic
path response. For this reason, both functions should always be activated, if possible.
Example 2
Acceleration mode: SOFT
This leads to a path velocity profile which is optimized in terms of time without smoothing the
path velocity or adapting the dynamic path response:
Basic functions

7LPHLQ,32F\FOHV
① Path velocity characteristic

② Limiting the path velocity due to the axis dynamics or the programmed feedrate
③ Block change markings
The parameter assignment is changed as follows:
This results in a path velocity profile with adaptation of the dynamic path response and with
minimum, and thus virtually deactivated, smoothing of the path velocity:

7LPHLQ,32F\FOHV
① More stable path velocity thanks to reduced jerk on path
The smoothing factor is set to 0% instead of 1% (in accordance with the default!):
A smoothing factor of 100% comes into effect with this parameter assignment.
This gives rise to a path velocity profile with smoothing of the path velocity and adaptation of
dynamic path response:

7LPHLQ,32F\FOHV
① More stable path velocity thanks to reduced jerk on path

② Dispensing with accelerations and braking, effect of path smoothing
Basic functions
5.4.5 Dynamic response mode for path interpolation
Function
Technology-specific, dynamic response settings can be saved in machine data and can be
activated in the part program via the commands from G group 59 (dynamic response mode for
path interpolation).
Command Activates the dynamic response settings for:

DYNNORM Standard dynamic response settings
DYNPOS Positioning mode, tapping
DYNROUGH Roughing
DYNSEMIFIN Semi-finishing
DYNFINISH Finishing
DYNPREC Smooth finishing
Note
The dynamic response of the path axes alone is determined by the commands from G group
59 (dynamic response mode for path interpolation). They have no effect on:
● Positioning axes
● PLC axes
● Command axes
● Motions based on axis coupling
● Overlaid motions with handwheel
● JOG motions
● Reference point approach (G74)
● Fixed-point approach (G75)
● Rapid traverse motion (G0)
The standard dynamic response setting (DYNNORM) always takes effect for these axis
motions.
Application
By switching the dynamic response settings, roughing can be optimized in terms of time and
smoothing can be optimized in terms of the surface, for example.
Axis-specific dynamic response settings:

● MD32300 $MA_MAX_AX_ACCEL[<n>] (axis acceleration)
● MD32310 $MA_MAX_ACCEL_OVL_FACTOR[<n>] (overload factor for axial jumps in
velocity)
● MD32431 $MA_MAX_AX_JERK[<n>] (maximum axial jerk for path motion)
Basic functions
● MD32432 $MA_PATH_TRANS_JERK_LIM[<n>] (maximum axial jerk at the block transition

in continuous-path mode)
● MD32433 $MA_SOFT_ACCEL_FACTOR[<n>] (scaling of the acceleration limitation with
SOFT)
Channel-specific dynamic response settings:

● MD22450 $MC_DYN_LIM_MODE[<n>] (axial or geometric velocity limits)
● MD20600 $MC_MAX_PATH_JERK[<n>] (path-related maximum jerk)
● MD20602 $MC_CURV_EFFECT_ON_PATH_ACCEL[<n>] (influence of path curvature on
path acceleration)
● MD20603 $MC_CURV_EFFECT_ON_PATH_JERK[<n>] (influence of path curvature on
path jerk)
where index <n> 0 for DYNNORM

=
1 for DYNPOS
2 for DYNROUGH
3 for DYNSEMIFIN
4 for DYNFINISH
5 for DYNPREC
Note
Writing the machine data without an index places the same value in all field elements of the
relevant machine data.
Reading the machine data without an index always supplies the value of the field with index 0.
Suppressing G commands
It is recommended that G commands from G group 59 (dynamic response mode for path
interpolation) which are not intended for use should be suppressed via the following machine
data:
MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[<n>] (list of reconfigured NC
commands)
If a suppressed G command is used, an alarm is displayed. This prevents machine data that
has not been parameterized taking effect.
Example
The G commands DYNPOS and DYNSEMIFIN can be suppressed with the following settings:
● MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[0]="DYNPOS"
● MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[1]=" "
● MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[2]="DYNSEMIFIN"
● MD10712 $MN_ NC_USER_CODE_CONF_NAME_TAB[3]=" "
Basic functions
Further information
Detailed information regarding programming of the G commands for G group 59 (dynamic
response mode for path interpolation) can be obtained in:
Use of the "Top Speed" option (position setpoint filter)

If the "Top Speed" option is used in one or more axes, the dynamic response-dependent FIR
filter settings for each dynamic response mode are also switched over.
For further information about the "Top Speed" option, see the Axes and Spindles Function
Manual.
Use of the "Intelligent load adaptation" option

If the "Intelligent load adaptation" option is used, the load-dependent scaling (especially the
limiting of the scaling) of acceleration and jerk for each dynamic response mode can be set
individually.
For further information about the "Intelligent load adaptation" option, see the Axes and Spindles
Function Manual.
5.4.6 Free-form surface mode: Basic functions
Introduction
In tool and mold making applications, it is important that the surfaces on the workpiece are as
uniform as possible. This requirement is generally more important than the precision of the
surface of the workpiece.
Workpiece surfaces that lack uniformity can be attributed to the following causes, for example:
● The part program to machine the workpiece contains a non-uniform geometry. This, most
notably, influences the profile of the curvature and torsion.
Note
The curvature k of a contour is the inverse of radius r of the adapted circle at a contour point
(k = 1/r). The torsion is the change in curvature (1st derivative).
As a result of the lack of uniformity in geometry, the machine's dynamic response limits are
reached when processing the part program - and axes are unnecessarily decelerated and
accelerated. Depending on the extent of the effective over-travel of the axes, this leads to
different deviations in contours.
● When an axis unnecessary brakes or accelerates, this can trigger machine vibration that
result in unwanted marks on the workpiece.
Basic functions
There are various options available for eliminating these problems:

● Use a CAD/CAM system
The part programs generated by CAD/CAM systems contain a very uniform curvature and
torsion profile, preventing unnecessary reductions in path velocity.
● Specify the maximum path velocity in such a way that unwanted geometric fluctuations in
the curvature and torsion profile have no effect.
Function
With the "Free-form surface mode: Basic functions" - for the active geometry axes and for active
orientation transformation of the rotary axes involved with the transformation - can be used to
define path velocity limits to make them less sensitive to small geometric fluctuations in
curvature and torsion without exceeding the machine's dynamic limits in terms of axis
acceleration and jerk.
● Greater uniformity in the profile of the path velocity
● Greater uniformity in the surface of the workpiece
● Shorter machining time (if the dynamic response of the machine permits it)
Applications
The function is used to machine workpieces which primarily comprise free-form surfaces.
Requirements
The function can only be activated if the required memory capacity is reserved when
configuring the memory:
MD28610 $MC_MM_PREPDYN_BLOCKS = 10
The value entered specifies the number of blocks that have to be taken into consideration when
determining the path velocity (velocity preparation).
A sensible value is "10".
If MD28610 has a value of "0", only the motion of the axes in a particular block are taken into
consideration when determining the maximum velocity of the path for that particular block. If the
geometry of neighboring blocks is also taken into consideration when determining the velocity
of the path (value > 0), a more uniform path velocity is achieved.
The function can be switched on or off independently for every dynamic response mode (see
Section "Dynamic response mode for path interpolation (Page 492)"):
Basic functions
MD20606 $MC_PREPDYN_SMOOTHING_ON[<n>] = <value>
Index <n> Dynamic response mode <Value> Free-form surface mode: Basic func‐
tions
0 Standard dynamic response set‐ 0 Off
tings (DYNNORM) 1 On
1 Positioning mode, tapping 0 Off
(DYNPOS) 1 On
2 Roughing (DYNROUGH) 0 Off
1 On
3 Semi-finishing (DYNSEMIFIN) 0 Off
1 On
4 Finishing (DYNFINISH) 0 Off
1 On
5 Smooth-finishing (DYNPREC) 0 Off
1 On
Note
Due to the additional memory requirement, the function should only be activated in the relevant
processing channels.
Parameterization
Change in the contour sampling factor
The secant error which occurs during the interpolation of curved contours is dependent on the
following factors:
● Curvature
● Interpolator clock cycle (indicated in MD10071 $MN_IPO_CYCLE_TIME)
● Velocity with which the relevant contour is traversed
The maximum possible secant error is defined for each axis in the machine data:
MD33100 $MA_COMPRESS_POS_TOL (max. deviation with compression)
If the set interpolator clock cycle is not sufficiently small, the max. path velocity may be reduced
in the case of contours with higher levels of curvature. This is necessary for ensuring that the
surface of the workpiece is also produced with an adequate degree of precision in cases such
as these.
By changing the contour sampling factor, the time interval with which a curved contour is
sampled in the interpolator (contour sampling time) can be set differently than the interpolator
clock cycle. A contour sampling time which is shorter than the interpolator clock cycle can
prevent a reduction in path velocity in the case of contours with a higher level of curvature.
The contour sampling factor is set with machine data:
MD10682 $MN_CONTOUR_SAMPLING_FACTOR
The effective contour sampling time is calculated as follows:
Basic functions
Ts = f * T1
with: Ts = effective contour sampling time

T1 = interpolator clock cycle
f = contour sampling factor (value from MD10682)
The default contour sampling factor is "1", i.e. the contour sampling time equals the interpolator
clock cycle.
The contour sampling factor can be both greater or less than "1".
If a value less than "1" is set, monitoring of contour sampling precision is deactivated.
The set sampling time must not be below the configured minimum contour sampling time:
MD10680 $MN_MIN_CONTOUR_SAMPLING_TIME
Note
MD10680 is specifically set for every control model, and cannot be changed.
Velocity limiting
The mode of velocity limiting due to curvatures can be specified for each dynamic response
mode with the following machine data:
MD22450 $MC_DYN_LIM_MODE [<n>] = <Value>
where index <n> 0 for DYNNORM

=
1 for DYNPOS
2 for DYNROUGH
3 for DYNSEMIFIN
4 for DYNFINISH
5 for DYNPREC
<Value> Meaning
=0 Velocity limitation is based on the axis-specific accelerations of the geometry axes involved
in the path
This setting increases path velocity as faster speeds are possible in a diagonal direction.
=1 Velocity limit is based on the geometric curvatures of the geometry axes involved in the path
This setting limits the path velocity at positions with diagonal and axis-parallel tangents
equally. The course of path velocity is thus smoother. This setting should therefore be se‐
lected for finishing.
MD22450 affects limiting of the path velocity with:

● "Programmable contour accuracy" function
● Maximum axis acceleration (MD32300 $MA_MAX_AX_ACCEL)
● Contour sampling factor (MD10682 $MN CONTOUR_SAMPLING_FACTOR)
Basic functions
5.5 Compressor functions
Programming
Depending on the setting in machine data MD20606 $MC_PREPDYN_SMOOTHING_ON,
"Free-form surface mode: Basic functions" can be activated and deactivated in the part
program by changing the active dynamic response mode.
Example:
By assigning the parameters MD20606 $MC_PREPDYN_SMOOTHING_ON[2-5] = 1 and
MD20606 $MC_PREPDYN_SMOOTHING_ON[0-1] = 0, the function can be activated using
the commands DYNROUGH, DYNSEMIFIN, DYNFINISH and DYNPREC and deactivated using
the commands DYNNORM and DYNPOS.
See also
Rounding of tangential block transitions (G645) (Page 467)
Free-form surface mode: Extension function (Page 476)
5.5.1 Compression of linear, circular and rapid traverse blocks
5.5.1.1 Function
CAD/CAM systems generate a large number of linear and circular blocks, some of which with
very short path lengths, to describe complex contours. The maximum possible path velocity is
frequently limited by the block change time. As of a certain path velocity, not enough new
traversing blocks can be prepared in the preprocessing and switched to the main run.
Compressing linear blocks

Compressor functions replace consecutive linear blocks with polynomial blocks having the
longest possible path lengths while maintaining a parameterizable contour precision. This has
the following advantages:
● Reduction of the number of traversing blocks
● Increasing the path velocity
● Increasing the surface quality
● Continuous block transitions
Basic functions
The compressor functions with their most important properties/attributes that are available are
listed in the following table:
Compressors Function Continuity at block tran‐ Notes about use

sitions
COMPON COMPON Continuous velocity
creates from up to 10
consecutive linear
blocks, type "G01 X...
Y... Z... F..." a polyno‐
mial block.
COMPCURV the same as COMPON Continuous velocity
and acceleration
COMPCAD COMPCAD can create Continuous velocity COMPCAD is very processor and memory-intensive. It
a polynomial block and acceleration is therefore recommended that COMPCAD only be
from any number of used where measures to improve surface quality were
consecutive linear not successful in the CAD/CAM program.
blocks.
COMPSURF the same as COMP‐ Continuous velocity Using COMPSURF, even better results can be ob‐
CAD and acceleration tained than with COMPCAD. However, just the same
as for COMPCAD, COMPSURF takes up a lot of com‐
putation time and memory space.
By using COMPSURF, for example for inclined line-by-
line finishing programs, poor data quality and/or irreg‐
ular point distribution in the CAD/CAM program, signif‐
icantly improved workpiece surfaces can be achieved.
In addition, COMPSURF facilitates a direction-inde‐
pendent identical smoothing of the milling paths that
can be deactivated; this significantly increases the sur‐
face quality for bidirectional milling tools.
If commands which are not traversing instructions are programmed in and between the
traversing blocks to be compressed (e.g. auxiliary function outputs, commands for activating
the absolute or chain dimensional notations, etc.), the compression process is interrupted. To
ensure that blocks can be compressed in the part program, only G0, G1, G2, G3, axis positions,
orientation vectors and feedrate values may be programmed. All other commands or G codes
will interrupt the compression and this can lead to a slowing down of the part program execution
for short paths.
The maximum tolerable deviation of the calculated path to the programmed positions can be
specified in machine data for all compressor functions (see "Parameterization (Page 500)").
Unlike COMPON and COMPCURV, the parameterized tolerances are not used in different
directions in neighboring paths with COMPCAD and COMPSURF.
Compression of circular and rapid traverse blocks

In addition to the compression of linear blocks, all compressor functions also allow rapid
traverse blocks (G0 blocks) to be compressed. On the other hand, circular blocks can only be
compressed using the COMPCAD compressor function.
The compression of circular and/or rapid traverse blocks is set for specific channels using the
hundreds position in machine data:
Basic functions
MD20482 $MC_COMPRESSOR_MODE = <value>
Value Meaning
0xx Circular blocks and G0 blocks are not compressed. This is compatible with earlier SW
versions.
1xx Circular blocks are linearized and compressed by COMPCAD.
Advantage:
The compressor function operates more precisely and therefore creates generally better
surfaces.
Disadvantage:
The compressor function is more sensitive to defects in the NC programs. For reasons of
compatibility it might therefore be necessary to keep the setting 0xx.
2xx G0 blocks are compressed - it is possible that a different tolerance becomes effective (see
"Tolerances for rapid traverse movements (Page 514)").
Advantage:
As a result that the tolerance has been set higher and the compression of G0 infeed motion,
these can be more quickly and more fluidly executed.
3xx Combination of the two previous options: Circular blocks as well as G0 blocks are com‐
pressed.
Activation / deactivation
Compressor functions COMPON, COMPCURV, COMPCAD and COMPSURF are activated/
deactivated using the G commands of G group 30 (see "Programming (Page 502)").
Parameterization
Number Identifier $MA_ Meaning

MD33100 COMPRESS_POS_TOL Maximum permissible axis-specific path deviation
with compression
Channel-specific machine data
Number Identifier $MC_ Meaning

MD20170 COMPRESS_BLOCK_PATH_LIMIT Maximum traversing length of an NC block that
can be compressed
MD20171 SURF_BLOCK_PATH_LIMIT Maximum traversing length of a compressible NC
block for compression with COMPSURF
MD20172 COMPRESS_VELO_TOL Maximum permissible deviation from path feed for
compression
MD20173 SURF_VELO_TOL Maximum permissible deviation from path feed for
compression with COMPSURF
Basic functions

MD20482 COMPRESSOR_MODE Principle of operation of the compressor
MD20485 COMPRESS_SMOOTH_FACTOR Smoothing factor for compression with COMP‐
CAD for the particular dynamic response mode
MD20486 COMPRESS_SPLINE_DEGREE Spline degree for compression with COMPCAD
for the particular dynamic response mode
MD20487 COMPRESS_SMOOTH_FACTOR_2 Smoothing factor for rotary axes for compression
with COMPCAD for the particular dynamic re‐
sponse mode
MD28071 MM_NUM_SURF_LEVELS Dimensioning the COMPSURF function (DRAM)
MD28072 MM_MAXNUM_SURF_GROUPS Dimensioning the COMPSURF function regarding
axis groups (DRAM)
Channel-specific setting data
Number Identifier $SC_ Meaning

SD42470 CRIT_SPLINE_ANGLE Corner angle limit for compression with COMP‐
CAD
SD42471 MIN_CURV_RADIUS Minimum radius of curvature for compression with
COMPCAD
SD42472 MIN_SURF_RADIUS Minimum radius of curvature for compression with
COMPSURF
SD42473 ACTNUM_SURF_GROUPS Number of axis groups for COMPSURF
SD42475 COMPRESS_CONTUR_TOL Maximum permissible contour deviation with com‐
pression
SD42476 COMPRESS_ORI_TOL Maximum deviation of the tool orientation for com‐
pression
Note:
Only for active orientation transformation!
SD42477 COMPRESS_ORI_ROT_TOL Maximum deviation of the tool rotation for com‐
pression
Note:
Only for 6-axis machines with rotatable tool!
Note
Corner limit angle and compressor function COMPCAD
The corner limit angle for the compressor function COMPCAD set via the setting data SD42470
$SC_CRIT_SPLINE_ANGLE is only used as an approximate measure for corner detection. By
evaluating the plausibility, the compressor can also identify flatter block transitions as corners
and larger angles as outliers.
Basic functions
Recommended settings for tool and mold making with Advanced Surface / Top Surface
Compressor functions are very important in milling of free-form surfaces in tool and mold
making. If they are used as part of the option "Advanced Surface" or "Top Surface" for which
a license is required, please observe the setting recommendations! A special test program is
provided via the SIOS portal for checking the set machine and setting data.
→ Test program for Advanced Surface / Top Surface (https://support.industry.siemens.com/cs/
ww/en/view/109738423)
5.5.1.3 Programming
Activating/deactivating NC block compression (COMPON, COMPCURV, COMPCAD, COMPSURF,

COMPOF)
The functions to compress linear blocks (and dependent on the parameterization, also circular
and/or rapid traverse blocks) are activated/deactivated using G commands of G group 30. The
commands are modal.
Syntax
COMPON / COMPCURV / COMPCAD / COMPSURF
...
COMPOF
Meaning
COMPON: Activating the compressor function COMPON

COMPCURV: Activating the compressor function COMPCURV
COMPCAD: Activating the compressor function COMPCAD
COMPSURF: Activating the compressor function COMPSURF
COMPOF: Deactivating the currently active compressor function
Note
The rounding function G642 and jerk limitation SOFT further improve the surface quality. These
commands must be written at the beginning of the program.
Example: COMPCAD
N10 G00 X30 Y6 Z40
N20 G1 F10000 G642 ; Activation: Rounding function G642
N30 SOFT ; Activation: Jerk limitation SOFT
N40 COMPCAD ; Activation: Compressor function COMPCAD
N50 FIFOCTRL
Basic functions

N24050 Z32.499 ; 1st traversing block
N24051 X41.365 Z32.500 ; 2nd traversing block
...
N99999 X... Z... ; last traversing block
COMPOF ; compressor function off.
...
Switching on/off NC block compression (COMPCAD, COMPSURF, COMPOF)

The functions to compress linear blocks (and dependent on the parameterization, also circular
and/or rapid traverse blocks) are activated/deactivated using G commands of G group 30. The
commands are modal.
Syntax
COMPCAD / COMPSURF
...
COMPOF
Meaning
COMPCAD: Activating the compressor function COMPCAD

COMPSURF: Activating the compressor function COMPSURF
COMPOF: Deactivating the currently active compressor function
Note
The smoothing function G642 and jerk limitation SOFT further improve the surface quality.
These commands must be written at the beginning of the program.
Example: COMPCAD
N10 G00 X30 Y6 Z40
N20 G1 F10000 G642 ; Activation: Smoothing function G642
N30 SOFT ; Activation: Jerk limitation SOFT
N40 COMPCAD ; Activation: Compressor function COMPCAD
N50 FIFOCTRL
N24050 Z32.499 ; 1st traversing block
N24051 X41.365 Z32.500 ; 2nd traversing block
...
N99999 X... Z... ; last traversing block
COMPOF ; compressor function off.
Basic functions

...
Orientation transformation (TRAORI)

When orientation transformation is active, the compressor functions can also compress motion
blocks for tool orientation and tool rotation.
Further information
Function Manual Transformations; Multi-axis transformations> Orientation > Compression of
the orientation

If the target block for block search type 2 or type 4 (block search with calculation to ...) is in a
program section in which a compressor function is active, positions are approached on the path
calculated by the compressor on repositioning. These positions must precisely match the
positions on the path programmed in the part program.
Part program blocks that are replaced by compression cannot be found as the target block in
the block search. Alarm 15370 "Search target for block search not found" is output.
5.5.2 Compression of short spline blocks
Function
When spline blocks are generated to describe complex contours using CAD/CAM systems,
spline blocks with very short path lengths occur between spline blocks with long path lengths.
These force the control to significantly reduce the path velocity. The functions for the
compression of short spline blocks generate new spline blocks with the longest possible path
lengths.
Commissioning
Activation
The compression of short spline blocks can be activated for the following spline types:
● BSPLINE
● BSPLINE/ORICURVE
● CSPLINE
It is activated in the channel-specific machine data:
Basic functions
MD20488 $MC_SPLINE_MODE, bit <n> = <value>
Bit <Value> Spline type Compressing short spline blocks

0 0 BSPLINE Not active
1 BSPLINE Active
1 0 BSPLINE/ORICURVE Not active
1 BSPLINE/ORICURVE Active
2 0 CSPLINE Not active
1 CSPLINE Active
Boundary conditions
● If commands that are not traverse commands, e.g. auxiliary function outputs, are
programmed in and between the traversing blocks to be compressed, the spline blocks
cannot be combined.
● The maximum number of blocks that can be combined into a program section in succession,
depends on the parameterized size of the block memory available in the block preparation.
MD28070 $MC_MM_NUM_BLOCKS_IN_PREP (number of blocks for block preparation)
Example
To achieve a higher path velocity when executing the traversing blocks, compression for short
spline blocks is activated for BSPLINE interpolation:
MD20488 $MC_SPLINE_MODE, Bit 0 = 1

N10 G1 G64 X0 Y0 Z0 F1000 ; Initial setting
N20 G91 F10000 BSPLINE ; Activation: B spline
N30 X0.001 Y0.001 Z0.001 ; From here: Combine short spline blocks
N40 X0.001 Y0.001 Z0.001
...
Basic functions
5.6 Contour/Orientation tolerance
5.6.1 Commissioning
Machine data
Contour tolerance / orientation tolerance

MD33100 $MA_COMPRESS_POS_TOL[<axis>] = <value> (maximum tolerance with
compression)
Via the axis-specific machine data, the maximum permitted contour deviation (contour
tolerance) or angle deviation of the tool orientation (orientation tolerance) of each axis is set.
The machine data is effective with the following functions:
● Smoothing: G642, G643, G644, G645
● Compressor: COMP...
● The higher the value, the more short blocks can be compressed into a long block.
The machine data is not effective for smoothing function G641. For G641, the path distance to
the block transition, which can be programmed with ADIS or ADISPOS, is effective.
Smoothing mode
MD20480 $MC_SMOOTHING_MODE (smoothing behavior with G64x)
Compressor mode
MD20482 $MC_COMPRESSOR_MODE (mode of compression)
Smoothing G645
MD33120 $MA_PATH_TRANS_POS_TOL (maximum contour deviation for smoothing G645)
Effective for smoothing tangential, but not continuously curved block transitions (e.g. circle -
straight line)
Setting data
Channel-specific contour tolerance

SD42465 $SC_SMOOTH_CONTUR_TOL (maximum contour deviation)
Channel-specific orientation tolerance

SD42466 $SC_SMOOTH_ORI_TOL (maximum angular deviation of the tool orientation)
Channel-specific orientation tolerance for smoothing with OST

SD42676 $SC_ORI_SMOOTH_TOL (tolerance for smoothing with orientation on smoothing)
Basic functions
Channel-specific orientation tolerance for smoothing orientation using ORISON

SD42678 $SC_ORISON_TOL (tolerance for smoothing the orientation)
5.6.2 Programming
5.6.2.1 Programming contour/orientation tolerance (CTOL, OTOL, ATOL)

Addresses CTOL, OTOL and ATOL can be used to adapt the machining tolerances -
parameterized using machine and setting data - for compressor functions, smoothing and
orientation smoothing in the part program.
The programmed tolerance values are valid until they are reprogrammed or deleted by
assigning a negative value. Further, they are deleted at the end of the program or a reset The
parameterized tolerance values become effective again after deletion.
Syntax
CTOL=<Value>
OTOL=<Value>
ATOL[<Axis>]=<Value>
Meaning
CTOL: Address to program the contour tolerance

Applications: ● All compressor functions
● All rounding types except G641 and G644
Preprocessing stop: No
Effective: Modal
<Value>: The value for the contour tolerance is specified as a length.
Type: REAL
Unit: inch/mm (dependent on the current dimensions
setting)
Value range: ≥ 0: Tolerance value
< 0: The programmed tolerance value is de‐
leted
⇒ The tolerance value parameterized in
the machine or setting data becomes ef‐
fective again.
Basic functions
OTOL: Address to program the orientation tolerance

● ORISON orientation smoothing
● All smoothing types except G641, G644 and OSD
Effective: Modal
<Value>: The value for the orientation tolerance is specified as an angle.
Type: REAL
Unit: degrees
leted
fective again.
ATOL: Address for programming an axis-specific tolerance
● ORISON orientation smoothing
● All smoothing types except G641, G644 and OSD
Effective: Modal
<Axis>: Name of the channel axis to which the programmed tolerance will
apply
<Value>: The value for the axis tolerance will be specified as a length or an
angle dependent on the axis type (linear or rotary axis).
Type: REAL
Unit: For linear axes: inch/mm (dependent on
the current dimensions set‐
ting)
For rotary axes: degrees
leted
fective again.
Note
The channel-specific tolerance values programmed with CTOL and OTOL have higher priority
than the axis-specific tolerance values programmed with ATOL.
Note
Scaling frames
Scaling frames affect programmed tolerances in the same way as axis positions; in other
words, the relative tolerance remains the same.
Basic functions
Example
COMPCAD G645 G1 F10000 ; Activate COMPCAD compressor function.
X... Y... Z... ; The machine and setting data is applied here.
X... Y... Z...
X... Y... Z...
CTOL=0.02 ; A contour tolerance of 0.02 mm is applied start-
ing from here.
X... Y... Z...
X... Y... Z...
X... Y... Z...
ASCALE X0.25 Y0.25 Z0.25 ; A contour tolerance of 0.005 mm is applied start-
ing from here.
X... Y... Z...
X... Y... Z...
X... Y... Z...
CTOL=–1 ; The machine and setting data is applied again
starting from here.
X... Y... Z...
X... Y... Z...
X... Y... Z...
Basic functions
5.6.2.2 Programming contour/orientation tolerance (CTOL, OTOL, ATOL) Additional information
System variables
Reading with preprocessing stop

Using the following system variables, the currently active tolerances can be read in the part
program and synchronized action:
● $AC_CTOL
Channel-specific contour tolerance effective when the actual main run block was
preprocessed.
If no contour tolerance is effective, $AC_CTOL will return the root of the sum of the squares
of the tolerances of the geometry axes.
● $AC_OTOL
Channel-specific orientation tolerance effective when the actual main run block was
preprocessed.
If no orientation tolerance is effective, $AC_OTOL will return the root of the sum of the
squares of the tolerances of the orientation axes during active orientation transformation.
Otherwise, it will return the value "-1."
● $AA_ATOL[<axis>]
Axis-specific contour tolerance effective when the actual main run block was preprocessed.
If no contour tolerance is active, $AA_ATOL[<geometry axis>] returns the contour tolerance
divided by the root of the number of geometry axes.
If an orientation tolerance and an orientation transformation are active
$AA_ATOL[<orientation axis>] will return the orientation tolerance divided by the root of the
number of orientation axes.
Note
If now tolerance values have been programmed, the $A variables are not differentiated enough
to distinguish the tolerance of the individual functions.
Circumstances like this can occur if the machine data and the setting data set different
tolerances for compressor functions, smoothing and orientation smoothing. The system
variables then return the greatest value occurring with the functions that are currently active.
For example, if a compressor function is active with an orientation tolerance of 0.1° and
ORISON orientation smoothing with 1°, the $AC_OTOL variable will return the value "1." If
orientation smoothing is deactivated, $AC_OTOL returns a value value "0.1."
Reading without preprocessing stop

Using the following system variables, the currently active tolerances can be read in the part
program:
● $P_CTOL
Currently active channel-specific contour tolerance.
● $P_OTOL
Currently active channel-specific orientation tolerance.
● $PA_ATOL
Currently active axis-specific contour tolerance.
Basic functions
5.7 Rapid traverse movements
The tolerances programmed with CTOL, OTOL and ATOL also affect functions that indirectly
depend on these tolerances:
● Limiting the chord error in the setpoint value calculation
● The basic functions of the free-form surface mode
The following smoothing functions are not affected by the programming of CTOL, OTOL and
ATOL:
● Smoothing the orientation with OSD
OSD does not use a tolerance, it uses a distance from the block transition.
● Smoothing with G644
G644 is not used for smoothing, it is used for optimizing tool changes and other motion not
involving machining.
● Smoothing with G645
G645 virtually always behaves like G642 and, thus, uses the programmed tolerances. The
tolerance value from machine data MD33120 $MA_PATH_TRANS_POS_TOL is only used
in uniformly tangential block transitions with a jump in curvature, e.g. a tangential circle/
straight line transition. The rounding path at these points may also be located outside the
programmed contour, where many applications are less tolerant. Furthermore, it generally
takes a small, fixed tolerance to compensate for the sort of changes in curvature which need
not concern the NC programmer.
5.7.1 Function
5.7.1.1 Rapid traverse

During rapid traversing, programmed tool movements are carried out at the fastest possible
traversing velocity.
The velocity of the rapid traversing is defined separately for each axis (see "Parameter
assignment (Page 515)").
Application
Rapid traversing movements are used for the following tasks, for example:
● Quickly positioning of the tool
● Passing around the workpiece
● Approaching tool change points
● Retracting the tool
Basic functions
Note
Rapid traversing movements are not suitable for workpiece machining!
Activation
Rapid traverse is activated by programming of G0 in the part program (see "Programming
(Page 516)").
5.7.1.2 Interpolation response of path axes for rapid traversing movements
Liner/non-linear interpolation
Path axes can be traversed in linear or non-linear interpolation mode in rapid traverse
movement.
=
<

;
① Path for rapid traverse with linear interpolation

② Single axis movements for rapid traverse with non-linear interpolation
Linear interpolation
Properties:
● The path axes are interpolated together.
● The tool movement programmed with G0 is executed at the highest possible velocity (rapid
traverse).
Basic functions
● The rapid traverse velocity is defined separately for each axis.

● If the rapid traverse movement is executed simultaneously on several axes, the rapid
traverse speed is determined by the axis which requires the most time for its section of the
path.
Linear interpolation is always performed in the following cases:
● For a G command combination with G0 that does not allow positioning axis motion, e.g.:
G40, G41, G42, G96, G961 and MD20750 $MC_ALLOW_G0_IN_G96 == FALSE
● With a combination of G0 and G64.
● When a compressor or transformation is active.
● In point-to-point (PTP) travel mode.
● When a contour handwheel is selected (FD = 0).
● In case of an active frame with rotation of geometry axes.
● If nibbling is active for geometry axes.
Non-linear interpolation
Properties:
● Each path axis interpolates as a single axis (positioning axis) independently of the other
axes at the axis-specific rapid traverse velocity.
● The channel-specific "Delete distance-to-go" command via the PLC and synchronized
action is applied to all positioning axes that were programmed as path axes.
In non-linear interpolation, with reference to the axis-specific jerk, one of the following two
settings applies alternatively:
● Positioning axis commands BRISKA, SOFTA, DRIVEA
● Machine data:
– MD32420 $MA_JOG_AND_POS_JERK_ENABLE
– MD32430 $MA_JOG_AND_POS_MAX_JERK
The existing system variables which refer to the distance-to-go ($AC_PATH, $AC_PLTBB and
$AC_PLTEB) are supported.
CAUTION
Risk of collision
Since the tool movement for non-linear interpolation can differ from the tool movement for
linear interpolation, synchronous actions relative to the coordinates of the path movement
may not become active.
Selection of interpolation type

The type of interpolation which is to be in effect for rapid traverse movements is preset by
machine data (see "Parameter assignment (Page 515)").
Basic functions
Independently of the default setting, the desired interpolation response can also be set in the
part program (see "Switch on/off linear interpolation for rapid traverse movements (RTLION,
RTLIOF) (Page 518)").
5.7.1.3 Tolerances for rapid traverse movements

Tolerances for rapid traverse movements (G0 tolerances) can have different settings for the
workpiece processing tolerances.
Advantage
Greater G0 tolerances allow a faster traversing of G0 blocks.
Prerequisites
G0 tolerances are only effective in compliance with the following conditions:
● One of the following functions is active:
– Compressor function COMP...
– Smoothing function G642 or G645
– Orientation smoothing OST
– Orientation smoothing ORISON
– Smoothing for path-relevant orientation ORIPATH
● Several (≥ 2) consecutive G0 blocks in the part program.
For a single G0 block, the G0 tolerances are not effective, as at the transition from a non G0
motion to a G0 motion (and vice versa), the "lower tolerance" always applies (workpiece
processing tolerance)!
Setting the G0 tolerances

G0 tolerances are preset channel-specifically with the machine data (see "Parameter
assignment (Page 515)").
The preset G0 tolerances can be temporarily adapted by programming in the part program (see
"Adapt tolerances for rapid traverse motion (STOLF, CTOLG0, OTOLG0) (Page 520)").
5.7.1.4 Rapid traverse override

With the rapid traverse override switch on the machine control panel, the operator can reduce
the rapid traverse velocity by percentages on-site and with immediate effect.
An active rapid traverse correction has an effect on all path axes that are traversed in rapid
traverse mode with linear or non-linear interpolation and are assigned to the current channel.
Additional information: Function Manual Axes and Spindles
Basic functions
5.7.2 Commissioning
Rapid traverse velocity

The rapid traverse velocity corresponds to the maximum permitted axis velocity, which is
defined for each axis via the following machine data:
MD32000 $MA_MAX_AX_VELO (maximum axis velocity) will still apply even after the coupling
is activated
Interpolation response for rapid traverse movements

The interpolation response for rapid traverse movements is channel-specifically preset for via
the machine data:
MD20730 $MC_G0_LINEAR_MODE = <Value> (interpolation behavior with G0)
<Value> Meaning
0 In the rapid traversing mode (G0) the non-linear interpolation is active.
Path axes are traversed as positioning axes.
1 In the rapid traversing mode (G0) the linear interpolation is active.
The path axes are interpolated together.
G0 tolerances
Relative G0 tolerance
Tolerances for rapid traverse movements can be set relative to the workpiece processing
tolerances via a channel-specific tolerance factor:
MD20560 $MC_G0_TOLERANCE_FACTOR (tolerance factor for G0)
The tolerance factor can be both greater or less than 1.0. If the factor is equal to 1.0 (default
value), then the same tolerances are active for rapid traverse movements as for non-rapid
traverse movements. Normally, the tolerance factor is set to > 1.0.
Basic functions
Absolute G0 tolerances
Alternatively, the channel-specific tolerances for rapid traverse movements can also be set
absolute and separate for contour tolerance and orientation tolerance:
● MD20561 $MC_G0_TOLERANCE_CTOL_ABS (contour tolerance for G0 movements) =
<Value>
<Value> Meaning
= 0 (default) The contour tolerance for G0 movements is determined by the relative G0 tol‐
erance.
>0 The contour tolerance for G0 movements is defined with the value of MD20651.
● MD20562 $MC_G0_TOLERANCE_OTOL_ABS (orientation tolerance for G0 movements)

= <Value>
<Value> Meaning
= 0 (default) The orientation tolerance for G0 movements is determined by the relative G0
tolerance.
>0 The orientation tolerance for G0 movements is defined with the value of
MD20652.
5.7.3 Programming
5.7.3.1 Activating rapid traverse (G0)

The traversing of the path axes at rapid traversing velocity is activated with the G command G0.
Syntax
G0 X… Y… Z…
G0 RP=… AP=…
Meaning
G0: Traversing the axis with rapid traverse velocity

Effective: Modal
X... Y... Z...: Specifying the end point in Cartesian coordinates
RP=... AP=... : Specifying the end point in polar coordinates
Basic functions
Examples
Example 1: Milling
<
1
1

;


N10 G90 S400 M3 ; Absolute dimension input, spindle clockwise
N20 G0 X30 Y20 Z2 ; Approach the starting position
N30 G1 Z-5 F1000 ; Tool infeed
N40 X80 Y65 ; Traversing along a straight line
N50 G0 Z2
N60 G0 X-20 Y100 Z100 M30 ; Retract tool, end of program
Basic functions
Example 2: Turning
;
1

1

=


N10 G90 S400 M3 ; Absolute dimension input, spindle clockwise
N20 G0 X25 Z5 ; Approach the starting position
N30 G1 G94 Z0 F1000 ; Tool infeed
N40 G95 Z-7.5 F0.2
N50 X60 Z-35 ; Traversing along a straight line
N60 Z-50
N70 G0 X62
N80 G0 X80 Z20 M30 ; Retract tool, end of program
5.7.3.2 Switch on/off linear interpolation for rapid traverse movements (RTLION, RTLIOF)
Independently of the default setting (MD20730 $MC_G0_LINEAR_MODE), the interpolation
response for rapid traverse movements can also be set in the part program using the
commands of the G group 55.
Syntax
RTLIOF
...
RTLION
Basic functions
Meaning
RTLIOF: G command for switching off the linear interpolation

⇒ In the rapid traversing mode (G0), the non-linear interpolation is active. All of the
path axes reach their end points independently of one another.
Effective: Modal
RTLION: G command for switching on the linear interpolation
⇒ In the rapid traversing mode (G0), the linear interpolation is active. All of the path
axes reach their end points simultaneously.
Effective: Modal
Note
Preconditions for RTLIOF
To ensure, with RTLIOF non-linear interpolation, the following conditions must be fulfilled:
● No transformation (TRAORI, TRANSMIT, etc.) active.
● G60 active (stop at the block end).
● No compressor active (COMPOF).
● No tool radius compensation active (G40).
● No contour handwheel selected.
● No nibbling active.
If one of these conditions is not met, linear interpolation is as with RTLION.
Example
; Linear interpolation is the default:
; MD20730 $MC_GO_LINEAR_MODE == TRUE
...
N30 RTLIOF ; Switch off linear interpolation.
N40 G0 X0 Y10 ; G0 blocks are traversed using non-linear inter-
polation.
N50 G41 X20 Y20 ; TRC active ⇒ G0 blocks are traversed using lin-
ear interpolation.
N60 G40 X30 Y30 ; TRC not active ⇒ G0 blocks are traversed using
non-linear interpolation.
N70 RTLION ; Switch on linear interpolation.
...
Further information
Reading the current interpolation behavior

The current interpolation behavior can be read via the system variables $AA_G0MODE.
Basic functions
5.7.3.3 Adapt tolerances for rapid traverse motion (STOLF, CTOLG0, OTOLG0)
The tolerances for rapid traverse motion (G0 tolerances) configured using machine data can be
temporarily adapted in the part program. In so doing, the settings in the machine data are not
changed. After channel or end of program reset, the configured tolerances become effective
again.
Requirements
G0 tolerances are only effective in compliance with the following conditions:
● One of the following functions is active:
– Compressor function COMP...
– Smoothing function G642 or G645
– Orientation smoothing OST
– Orientation smoothing ORISON
– Smoothing for path-relevant orientation ORIPATH
● Several (≥ 2) consecutive G0 blocks in the part program.
For a single G0 block, the G0 tolerances are not effective, as at the transition from non G0
motion to G0 motion (and vice versa), the "lower tolerance" always applies (workpiece
processing tolerance)!
Syntax
Adaptation of the relative G0 tolerance

STOLF=<Value>
Adaptation of the absolute G0 tolerances

CTOLG0=<Value>
OTOLG0=<Value>
Basic functions
Meaning
STOLF: Address for programming a temporarily effective tolerance factor for rapid traverse motion
<Value>: G0 tolerance factor
Type: REAL
Value: ≥ 0: The G0 tolerance factor can be greater or less than 1.0. If
the factor is equal to 1.0 (default value), then the same
tolerances are active for rapid traverse motion as for non-
rapid traverse motion. Normally, the tolerance factor is set
to > 1.0.
The programmed G0 tolerance factor remains effective
until it is overwritten by renewed STOLF programming,
replaced by CTOLG0/OTOLG0 programming or deleted
by channel or end of program reset.
< 0: the programmed tolerance factor is deleted
⇒ The tolerance value preset in the machine data becomes
effective again.
CTOLG0: Address for programming a temporarily effective contour tolerance factor for rapid traverse
motion
<Value>: Absolute value for the contour tolerance
Type: REAL
Value: ≥ 0: The programmed absolute value for the contour tolerance
remains effective until it is overwritten by renewed
CTOLG0 programming, replaced by STOLF programming
or deleted by channel or end of program reset.
< 0: the programmed tolerance value is deleted
effective again.
OTOLG0: Address for programming a temporarily effective orientation tolerance factor for rapid tra‐
verse motion
<Value>: Absolute value for the orientation tolerance
Type: REAL
Value: ≥ 0: The programmed absolute value for the orientation toler‐
ance remains effective until it is overwritten by renewed
OTOLG0 programming, replaced by STOLF programming
or deleted by channel or end of program reset.
< 0: the programmed tolerance value is deleted
effective again.
Note
The last programmed address always has priority, as shown in the following examples:
● When CTOLG0 is programmed with active STOLF, the tolerance value programmed with
CTOLG0 is applied to smooth the contour.
● When OTOLG0 is programmed with active STOLF, the tolerance value programmed with
OTOLG0 is applied to smooth the orientation.
● After programming STO again, the tolerance factor for the contour and orientation tolerance
is applied.
Basic functions
Examples
Example 1: Adaptation of the relative G0 tolerance

COMPCAD G645 G1 F10000 ; Compressor function COMPCAD
X... Y... Z... ; The machine and setting data apply here.
X... Y... Z...
X... Y... Z...
G0 X... Y... Z...
G0 X... Y... Z... ; Machine data $MC_G0_TOLERANCE_FACTOR (e.g. =3) is ef-
fective here, i.e. a smoothing tolerance of:
$MC_G0_TOLERANCE_FACTOR * $MA_COMPRESS_POS_TOL
CTOL=0.02
STOLF=4
G1 X... Y... Z... ; A contour tolerance of 0.02 mm is applied starting
from here.
X... Y... Z...
X... Y... Z...
G0 X... Y... Z...
X... Y... Z... ; From here, a G0 tolerance factor of 4 applies, i.e. a
contour tolerance of 0.08 mm.
...
Example 2: Adaptation of the absolute G0 tolerances

The following absolute G0 tolerances should be preset in the machine data:
● G0 contour tolerance: 0.1
● G0 orientation tolerance: 1.0
These tolerances should be temporarily adapted in the part program:

COMPCAD G645 G1 F10000 ; Compressor function COMPCAD
X... Y... Z... ; The configured workpiece machining tolerances apply
from here.
X... Y... Z...
X... Y... Z...
G0 X... Y... Z...
G0 X... Y... Z... ; The configured absolute G0 tolerances apply here.
CTOLG0=0.2 OTOLG0=2.0 ; Programming the absolute G0 tolerances.
G1 X... Y... Z...
X... Y... Z...
X... Y... Z...
G0 X... Y... Z...
X... Y... Z... ; The programmed G0 tolerances apply from here.
...
Basic functions
5.8 RESET behavior
Further information
Reading the G0 tolerance factor

The currently active tolerance factor for rapid traverse motion can be read using system
variables:
● In synchronized actions or with preprocessing stop in the part program via system variable:
$AC_STOLF Active G0 tolerance factor
G0 tolerance factor, which was effective when processing the
actual main run block.
● Without preprocessing stop in the part program via system variable:

$P_STOLF Programmed G0 tolerance factor
If no value with STOLF is programmed in the active part program, then these two system
variables return the value configured in the machine data.
If no rapid traverse (G0) is active in a block, then these system variables always supply a value
of 1.
Reading absolute G0 tolerances

The currently active absolute tolerances for rapid traverse motion can be read via system
variables.
● In synchronized actions or with preprocessing stop in the part program via the system
variables:
$AC_CTOL_G0_ABS Active contour tolerance for G0 motion
G0 contour tolerance that was active when the current main
run block was preprocessed.
$AC_OTOL_ G0_ABS Active orientation tolerance for G0 motion
G0 orientation tolerance that was active when the current
main run block was preprocessed.
● Without preprocessing stop in the part program via system variables:

$P_CTOL_ G0_ABS Programmed contour tolerance for G0 motion
$P_OTOL_ G0_ABS Programmed orientation tolerance for G0 motion
If no absolute G0 tolerances with CTOLG0 and OTOLG0 are programmed in the active part
program, then these system variables supply the values configured in the machine data.
5.8 RESET behavior
MD20150
With the reset (channel or mode group reset), the initial setting parameterized channel-
specifically becomes effective for all G groups:
Basic functions
5.9 Supplementary conditions
MD20150 $MC_GCODE_RESET_VALUES (initial setting of the G groups)

The following G groups are of relevance to "continuous-path mode, exact stop, LookAhead":
● Group 10: Exact stop - continuous-path mode
● Group 12: Block-change criterion for exact stop
● Group 21: Acceleration profile
● Group 30: NC block compression
● Group 59: Dynamic response mode for path interpolation
For detailed information on setting initial states, see Section "Mode group, channel, program
operation, reset response (Page 29)."
5.9.1 Block change and positioning axes

If path axes are traversed in continuous path mode in a part program, traversing positioning
axes can also simultaneously affect both the response of the path axes and the block change.
A detailed description of the positioning axes can be obtained in:
Further information
Function Manual Axes and Spindles; Positioning axes
5.9.2 Block change delay

Even if all path axes and special axes traversing in the part program block have satisfied their
specific block transition criteria, the block change can still be delayed due to other unsatisfied
conditions and/or active functions:
Examples:
● Missing auxiliary function acknowledgement by the PLC
● Non-existent following blocks
● Active function "Empty buffer"
Effects
If a block change cannot be executed in continuous path mode, all axes programmed in this
part program block (except cross-block traversing special axes) are stopped. In this case,
contour errors do not occur.
The stopping of path axes during machining can cause undercuts on the workpiece surface.
Basic functions
5.10 Data lists
5.10 Data lists
5.10.1 Machine data

10110 PLC_CYCLE_TIME_AVERAGE Average PLC acknowledgment time
10680 MIN_CONTOUR_SAMPLING_TIME Minimum contour sampling time
10682 CONTOUR_SAMPLING_FACTOR Contour sampling factor
10712 NC_USER_CODE_CONF_NAME_TAB List of reconfigured NC commands
12030 OVR_FACTOR_FEEDRATE Evaluation of the path feedrate override switch
12100 OVR_FACTOR_LIMIT_BIN Limit for binary-coded override switch
18360 MM_EXT_PROG_BUFFER_SIZE FIFO buffer size for execution from external source
(DRAM)
5.10.1.2 Channelspecific machine data

20150 GCODE_RESET_VALUES Basic setting of the groups
20170 COMPRESS_BLOCK_PATH_LIMIT Maximum traversing length of an NC block that can be
compressed
20171 SURF_BLOCK_PATH_LIMIT Maximum traversing length of a compressible NC block
for compression with COMPSURF
20172 COMPRESS_VELO_TOL Maximum permissible deviation from path feed for com‐
pression
20173 SURF_VELO_TOL Maximum permissible deviation from path feed for com‐
pression with COMPSURF
20400 LOOKAH_USE_VELO_NEXT_BLOCK LookAhead following block velocity
20430 LOOKAH_NUM_OVR_POINTS Number of override switch points for LookAhead
20440 LOOKAH_OVR_POINTS Override switch points for LookAhead
20443 LOOKAH_FFORM Activating the extended LookAhead
20450 LOOKAH_RELIEVE_BLOCK_CYCLE Relief factor for the block cycle time
20455 LOOKAH_FUNCTION_MASK Special LookAhead functions
20460 LOOKAH_SMOOTH_FACTOR Smoothing factor for LookAhead
20462 LOOKAH_SMOOTH_WITH_FEED Smoothing with programmed feed
20465 ADAPT_PATH_DYNAMIC Adaptation of path dynamic response
20480 SMOOTHING_MODE Rounding behavior with G64x
20482 COMPRESSOR_MODE Principle of operation of the compressor
20484 COMPRESSOR_PERFORMANCE Compressor performance
Basic functions
5.10 Data lists

20485 COMPRESS_SMOOTH_FACTOR Smoothing factor for compression with COMPCAD for
the particular dynamic response mode
20486 COMPRESS_SPLINE_DEGREE Spline degree for compression with COMPCAD for the
particular dynamic response mode
20487 COMPRESS_SMOOTH_FACTOR_2 Smoothing factor for rotary axes for compression with
COMPCAD for the particular dynamic response mode
20488 SPLINE_MODE Setting for spline interpolation
20490 IGNORE_OVL_FACTOR_FOR_ADIS G641/G642 independent of the overload factor
20550 EXACT_POS_MODE Exact-stop conditions with G0/G1
20552 EXACT_POS_MODE_G0_TO_G1 Exact stop criterion for rapid traverse transitions in the
continuous path mode
20560 G0_TOLERANCE_FACTOR G0 tolerance factor
20561 G0_TOLERANCE_CTOL_ABS Contour tolerance for G0 movements
20562 G0_TOLERANCE_OTOL_ABS Orientation tolerance for G0 movements
20602 CURV_EFFECT_ON_PATH_ACCEL Influence of path curvature on path dynamic response
20603 CURV_EFFECT_ON_PATH_JERK Influence of path curvature on path jerk
20605 PREPDYN_SMOOTHING_FACTOR Factor for smoothing the curvature
20606 PREPDYN_SMOOTHING_ON Activation of the curvature smoothing
20730 G0_LINEAR_MODE Interpolation behavior with G0
28070 MM_NUM_BLOCKS_IN_PREP Number of NC blocks for block preparation (DRAM)
28071 MM_NUM_SURF_LEVELS Dimensioning the COMPSURF function (DRAM)
28072 MM_MAXNUM_SURF_GROUPS Dimensioning the COMPSURF function regarding axis
groups (DRAM)
28520 MM_MAX_AXISPOLY_PER_BLOCK Maximum number of axis polynomials per block
28530 MM_PATH_VELO_SEGMENTS Number of storage elements for limiting path velocity in
block
28533 MM_LOOKAH_FFORM_UNITS Memory for extended LookAhead
28540 MM_ARCLENGTH_SEGMENTS Number of storage elements for arc length function rep‐
resentation per block
28610 MM_PREPDYN_BLOCKS Number of blocks for velocity preparation

32000 MAX_AX_VELO Maximum axis velocity
32310 MAX_ACCEL_OVL_FACTOR Overload factor for axial velocity jumps
32431 MAX_AX_JERK Maximum axial jerk when traversing along the path
32432 PATH_TRANS_JERK_LIM Maximum axial jerk at the block transition in continuous-
path mode
32433 SOFT_ACCEL_FACTOR Scaling of acceleration limitation for SOFT
Basic functions
5.10 Data lists

32434 G00_ACCEL_FACTOR Scaling of acceleration limitation for G00
32435 G00_JERK_FACTOR Scaling of axial jerk limitation for G00
32440 LOOKAH_FREQUENCY Smoothing limit frequency for LookAhead
33120 PATH_TRANS_POS_TOL Maximum deviation when rounding with G645
35240 ACCEL_TYPE_DRIVE DRIVE acceleration characteristic for axes on/off
36000 STOP_LIMIT_COARSE Exact stop coarse
36010 STOP_LIMIT_FINE Exact stop fine
36012 STOP_LIMIT_FACTOR Exact stop coarse/fine factor and zero speed monitoring
36020 POSITIONING_TIME Delay time exact stop fine
5.10.2 Setting data
Number Identifier $SC_ Description

42465 SMOOTH_CONTUR_TOL Max. contour deviation during rounding
42466 SMOOTH_ORI_TOL Max. deviation of the tool orientation during rounding
42470 CRIT_SPLINE_ANGLE Corner angle limit for compression with COMPCAD
42471 MIN_CURV_RADIUS Minimum radius of curvature for compression with
COMPCAD
42472 MIN_SURF_RADIUS Minimum radius of curvature for compression with
COMPSURF
42473 ACTNUM_SURF_GROUPS Number of axis groups for COMPSURF
42475 COMPRESS_CONTUR_TOL Maximum permissible contour deviation with compres‐
sion
42476 COMPRESS_ORI_TOL Maximum deviation of the tool orientation for compres‐
sion
Note:
Only for active orientation transformation!
42477 COMPRESS_ORI_ROT_TOL Maximum deviation of the tool rotation for compression
Note:
Only for 6-axis machines with rotatable tool!
42676 ORI_SMOOTH_TOL Tolerance for smoothing of the orientation when
smoothing
42678 ORISON_TOL Smoothing tolerance of the orientation
Basic functions
5.10 Data lists
Basic functions
Cross-channel program coordination and channel-by-
channel running-in 6
6.1 Cross-channel program coordination
6.1.1 Cross-channel program coordination (INIT, START, WAITM, WAITMC, WAITE,

SETM, CLEARM)
In principle, a channel of the NC can execute the program started in it independently of other
channels in its mode group. If, however, several programs in several channels of the mode
group are involved in machining a workpiece, the program sequences in the various channels
must be coordinated with the following coordination commands.
Requirement
All the channels involved in the program coordination must belong to the same mode group:
MD10010 $MC_ASSIGN_CHAN_TO_MODE_GROUP[<Channel>] = <Mode group number>
Channel name instead of channel number

Instead of the channel numbers, the channel names entered in MD20000
$MC_CHAN_NAME[<Channel index>] can be used as parameters of the predefined
procedures for the program coordination. The use of the channel names in the NC programs
first has to be enabled:
MD10280 $MN_PROG_FUNCTION_MASK, bit 1 = TRUE
Note
Minimum distance between commands
At least two traversing block distances must be maintained between the commands INIT,
START, WAITE, WAITM, SETM, CLEARM and the command WAITMC. WAITMC is an executable
block, but is moved into the previous block for optimization, and then deleted as a block. SETM
for example is not an executable block, and is moved into the next block so that if there were
a distance of one block between two commands, both commands would be in the middle block.
As only one block is possible, optimization is not performed with a one block distance
for WAITMC.
This stops the program, and processing is briefly interrupted.
Syntax
INIT(<ChanNo>, <Prog>, <AckMode>)
START(<ChanNo>, <ChanNo>, ...)
WAITM(<MarkNo>, <ChanNo>, <ChanNo>, ...)
WAITE(<ChanNo>, <ChanNo>, ...)
Basic functions
Cross-channel program coordination and channel-by-channel running-in
WAITMC(<MarkNo>, <ChanNo>, <ChanNo>, ...)

SETM(<MarkNo>, <MarkNo>, ...)
CLEARM(<MarkNo>, <MarkNo>, ...)
Meaning
INIT(): Predefined procedure for selecting the NC program that is to be executed in the speci‐
fied channel
START(): Predefined procedure for starting the selected program in the respective channel
WAITM(): Predefined procedure to wait for a wait marker to be reached in the specified channels
The specified wait marker is set by WAITM in the same channel. The previous block is
terminated with exact stop. The wait marker is deleted after synchronization.
A maximum of 10 markers can be set simultaneously in each channel.
WAITE(): Predefined procedure to wait for the end of program in one or more other channels
WAITMC(): 1) Predefined procedure to wait for a wait marker to be reached in the specified channels
In contrast to WAITM, the braking of the axes to exact stop is only initiated if the other
channels have not yet reached the wait marker.
SETM(): 1) Predefined procedure to set one or more wait markers for the channel coordination
The processing in own channel is not affected by this.
SETM remains valid after a channel reset and NC start.
CLEARM(): 1)
Predefined procedure to delete one or more wait markers for the channel coordination
The processing in own channel is not affected by this.
CLEARM() deletes all wait markers in the channel.
CLEARM(0) only deletes wait marker "0".
CLEARM remains valid after a channel reset and NC start.
<ChanNo>: Channel number
The number of the own channel does not have to be specified.
Type: INT
<Prog>: Absolute or relative path specification (optional) + program name
Type: STRING
Information relating to path data, see the Programming Manual NC Programming,
Chapter "Addressing program memory files".
<AckMode>: Acknowledgment mode (optional)
Type: CHAR
Val‐ "N" Without acknowledgment
ues: The program execution is continued after the command has been sent.
The sender is not informed if the command cannot be executed suc‐
cessfully.
"S" Synchronous acknowledgment
The program execution is stopped until the receiving component has
acknowledged the command. If the acknowledgment is positive, the
next command is executed. If the acknowledgment is negative, an error
message is output.
Basic functions
<MarkNo>: Number of the wait marker

Note
In a multi-channel system, a maximum of 100 wait markers are available (wait markers
0 ... 99).
Only wait marker 0 is available in a single-channel system.
1) For user-specific communication and/or coordination of channels, wait markers can be deployed
using SETM / CLEARM – and also without using the conditional wait command WAITMC. The wait markers
retain their values, even after a channel reset and NC start.
Examples
START using channel names from MD20000

● Parameter assignment
MD10280 $MN_PROG_FUNCTION_MASK, bit 1 = TRUE
$MC_CHAN_NAME[ 0 ] = "MACHINING"; Name of channel 1
$MC_CHAN_NAME[ 1 ] = "INFEED"; Name of channel 2
● Programming

START(MACHINING) ; Start of channel 1
START(INFEED) ; Start of channel 2
START using local "channel names" and user variables

DEF INT MACHINE = 1 ; Definition of user variable for channel 1
DEF INT LOADER = 2 ; Definition of user variable for channel 2
...
START(MACHINE) ; Start of channel 1
START(LOADER) ; Start of channel 2
START using local "channel names", user variables and parameterized channel names

DEF INT chanNo1 ; Definition of user variable for channel 1
DEF INT chanNo2 ; Definition of user variable for channel 2
chanNo1 = CHAN_1 ; Assignment of parameterized channel name channel 1
chanNo2 = CHAN_2 ; Assignment of parameterized channel name channel 2
...
START(ChanNo1) ; Start of channel 1
START(ChanNo2) ; Start of channel 2
INIT command with absolute path specification

Selection of program /_N_MPF_DIR/_N_ABSPAN1_MPF in channel 2.
Program code
INIT(2,"/_N_WCS_DIR/_N_SHAFT1_WPD/_N_CUT1_MPF")
Basic functions
INIT command with program name

Selection of the program with the name "MYPROG". The control searches for the program
using the search path.
Program code
INIT(2,"MYPROG")
Program coordination with WAITM

● Channel 1: The program /_N_MPF_DIR/_N_MPF100_MPF has already been selected and
started.

; Program MPF100
N10 INIT(2,"MPF200","N") ; Selection of program MPF200, channel 2
N11 START(2) ; Start of channel 2
...
N80 WAITM(1,1,2) ; Wait for WAIT marker 1 in channels 1 and
2
N81 ... ; Channel 1, N81 and channel 2, N71 are
; started synchronously
...
N180 WAITM(2,1,2) ; Wait for WAIT marker 2 in channels 1 and
2
...
N200 WAITE(2) ; Wait for end of program in channel 2
N201 ... ; N201 is not started until the end of
program
; MPF200 started in channel 2
N201 M30 ; End of program channel 1
● Channel 2: In channel 1, the program MPF200_MPF is selected and started for channel 2
using blocks N10 and N20.

;$PATH=/_N_MPF_DIR ; Program MPF200
...
N70 WAITM(1,1,2) Wait for WAIT marker 1 in channels 1 and 2
...
N270 WAITM(2,1,2) Wait for WAIT marker 2 in channels 1 and 2
...
N400 M30 End of program channel 2
Basic functions
1 1
:$,70 :$,70
&KDQQHO
1
03) 1
0
:DLWLQJ
&KDQQHO 1
1 1

03) :DLWLQJ :DLWLQJ 0
1 1 1

67$57
:$,70 :$,70 :$,7(
6WDUW 67$57 0 0 (QGRIWLPH
Boundary conditions
Non-synchronous start of execution of following blocks after WAIT markers

In the case of channel coordination using WAIT markers, execution of the following blocks may
start non-synchronously. This behavior occurs if an action is triggered in one of the channels to
be synchronized immediately before reaching the common WAIT marker; the consequence of
which is implicit repositioning (REPOSA) in this delete distance-to-go.
Assumption: Current axis assignment in channels 1 and 2
● Channel 1: Axes X1 and U
● Channel 2: Axis X2
Table 6-1 Time sequence in channels 1 and 2
Channel 1 Channel 2 Description

... ... Arbitrary processing in channels 1 and 2
N100 Channel 1: reaches the WAIT marker and waits for
WAITM(20,1,2) synchronization with channel 2
Start of the GETD(U) N200 GETD(U) Channel 2: Requests axis U from channel 1
processing: Channel 1: Processing of GET(U) in the background
● Axis interchange N210 Channel 2: reaches the WAIT marker. ⇒ This com‐
● Delete distance-to- WAITM(20,1,2) pletes the synchronization of channels 1 and 2
go N220 G0 X2=100 Channel 2: Start of processing of N220
● REPOSA
End
N110 G0 X1=100 Channel 1: Staggered start of processing of N110
Basic functions
See also
Conditional wait (WAITMC) in the continuous path mode (Page 534)
Programming: Fetching an axis (GET, GETD) (Page 551)
6.1.2 Conditional wait (WAITMC) in the continuous path mode

If in a channel, at the time that WAITMC is being processed, all of the required wait markers of
the other channels have already been received, then in this channel, traversing motion is not
braked, or the further program execution is not stopped, but continued with the processing of
the following block.
WAITMC is in separate block as function call. For the correct execution of WAITMC without
braking, a traversing block must be immediately before WAITMC. For traversing blocks with
G64x, the block with WAITMC is added to the previous block to avoid a drop in velocity. If there
are no traversing blocks, e.g. "IF loops", immediately before WAITMC, the command cannot be
assigned consistently and braking occurs.
Requirement
The following functions must be active in the channel:
● Continuous-path mode (G64, G641, G642, G643, G644 or G645)
● "LookAhead" function
Braking behavior
No braking
Starting with the motion block before the WAITMC call, the wait markers of the other channels
to be synchronized are checked. If these are already available, no braking is performed:
Y
:$,70&
Figure 6-1 Change of the path velocity for the conditional waiting with WAITCM: Wait markers for all
channels already available
Short-time braking
If the wait marker for a channel to be synchronized is missing, braking will be started. During
braking, a check is made in each interpolator cycle as to whether the still missing wait markers
have been received in the meantime. If this is the case, then the axis accelerates back to the
programmed velocity:
Basic functions
Y
:$,70&
Figure 6-2 Change of the path velocity for the conditional waiting with WAITCM: The last wait marker
arrives during braking
Braking down to standstill

If the wait marker is not received during the braking phase, then the axis is braked down to
standstill and the system waits. When the wait marker is received, the axis accelerates back to
the programmed velocity.
Y
:$,70&
6WDQGVWLOO
Figure 6-3 Change of the path velocity for the conditional waiting with WAITCM: The last wait marker
arrives after the braking
Block change while braking (IPOBRKA)

If the IPOBRKA (block change criterion "braking ramp") end of motion criterion is active, the
arrival of the last missing wait marker causes a transition to the next block and the axis is
accelerated.
Example 1: Conditional wait in continuous-path mode

The example is schematic, and shows only those commands that are relevant for the
synchronization.
Channel 1

N10 INIT(2, "_N_200_MPF","n") ; Select partner program channel 2.
N11 INIT(3,"_N_300_MPF","n") ; Select partner program channel 3.
N15 START(2,3) ; Start programs in channels 2, 3.
... ; Machining in channel 1.
Basic functions

N20 WAITMC(7,2,3) ; Conditional wait for marker 7 from channels 2 and
3.
... ; Further machining in channel 1.
N40 WAITMC(8,2) ; Conditional wait for marker 8 from channel 2.
N70 M30 ; End channel 1.
Channel 2

N200 ... ; Machining in channel 2.
N210 SETM(7) ; Channel 2 sets wait marker 7.
N250 SETM(8) ; Channel 2 sets wait marker 8.
Channel 3

N300 ... ; Machining in channel 3.
...
N350 WHEN <condition> DO SETM(7) ; Set wait marker in a synchronous action.
... ; Additional machining in channel 3.
Basic functions
&RQGLWLRQIXOILOOHG :+(1FRQGLWLRQ!
&KDQQHO '26(70
1 1 1

&KDQQHO 6(70 6(70
1 1 1 1
&KDQQHO
1 1 1 1 1 1
:$,70& :$,70&
3DWKYHORFLW\
1REUDNLQJ
&KDQQHO
Figure 6-4 Conditional wait in path-controlled operation with three involved channels (schematic)
Example 2: WAITMC and read-in disable

Auxiliary function M555 is output in channel 3 while the axis is traversing and creates a read-in
disable. As WAITMC is assigned block N312, the wait marker is set, and channel 2 progresses.
The read-in disable causes the program execution in channel 3 to stop.
Note
For an active G64, WAITMC does not to create a dedicated block, but instead, is added to the
previous block. A drop in velocity must be prevented when continuous-path mode is active.
A WAITMC is therefore fulfilled if the preceding block is stopped, e.g. by a read-in disable.
Channel 2

N112 G18 G64 X200 Z200 F567 ; Machining in channel 2
Basic functions
6.2 Running-in channel-by-channel

N120 WAITMC(1,2,3) ; Conditional wait for wait marker 1
; from channels 2 and 3
... ; Additional machining in channel 2, as
; WAITMC is added to block N312.
... ; Additional machining in channel 2
N170 M30 ; End of channel 2
Channel 3
Comment
; During traversing read-in disable M555
N300 ; Machining in channel 3
N312 G18 G64 D1 X180 Z300 M555
N320 WAITMC(1,2,3) ; Wait because of read-in inhibit
6.2.1 Function
The "channel-by-channel running-in" function is used to test or run-in the NC programs of one
or more channels that are synchronized with each other. The programmed traversing motion of
the channel axes and/or spindles in the channels, which are in the "Normal operating" state,
results in the machine axes traversing. The following applies to channels that are in the
"Program test" state:
● In the default setting, for axes for normal operation, identical setpoints are generated,
however, these are not output at the machine axes .
● In the default setting, the setpoints for spindles are output at the machine axes.
● The displayed actual values of the inhibited axes/spindles are internally generated from
setpoints.
● The commands for channel synchronization are processed normally.
● The NC/PLC interface signals are processed normally.
● The processing time of the program is the same as in normal operation.
Temporarily when required, the "Program test" state can be exited on an axis-for-axis basis.
The setpoints are then output again on the machine axes so that they are really traversed on
the machine.
Basic functions
6.2.2 Sequence
Normally, a channel moves a tool in the working area. If several channels are each moving a
tool in the same working area, the tool movements must be synchronized. The following
synchronizations are possible:
● Channel synchronization via the program coordination commands WAITM, WAITMC, WAITE,
START.
● Channel synchronization via the PLC user program and NC/PLC interface signals. For
example, via M function output from the channel to the PLC and read-in disable from the
PLC to the channel.
● Axis interchange: The channel waits until the other channel relinquishes the axis.
● Synchronization by means of global variables in the NC program.
● Cross-channel couplings
● Axis container rotation
● Testing the program including the parallel synchronized actions in the main run and
synchronization of the synchronized actions with the channel.
Under these general conditions, it is almost impossible to just start one channel - it would
remain stationary at the first synchronization location.
Using the "Channel-by-channel running-in", function, all of the required channels can be started
so that only those channels receive the traversing enable signals, whose interaction of the
programmed traversing motion are to be tested. The other channels are then in the "program
test" state.
To do this, before starting the channels, the machine operator must define the channels that are
to be traversed under "Program test". This is made from the user interface in the "Program
controls" menu.
6.2.3 Single-channel view
Selection
"Program test" (PRT) for the channel displayed in the "Machine" basic display is selected via
the user interface, e.g. SINUMERIK Operate:
2. "Program controls" menu: Select check box "Program test (PRT)".
Basic functions

After selecting program test (PRT), the following NC/PLC interface signals are set (see below
note "Automatic transfer of interface signals"):
● Channels
– DB21, ... DBX25.7 == 1 (from HMI: program test selected)
– DB21, ... DBX1.7 == 1 (from PLC: activate program test)
– DB21, ... DBX33.7 == 1 (from NC: program test active)
● Axes
– DB31, ... DBX128.0 == 0 (from HMI: suppress program test)
– DB31, ... DBX128.1 == 0 (activate program test from HMI)
– DB31, ... DBX14.0 == 0 (from PLC: suppress program test)
● Spindles
– DB31, ... DBX128.1 == 0 (from HMI: activate program test)
Note
● Axes: Inhibited
Note
Automatic transfer of the interface signals
The HMI request signals DB21, ... DBX128.0 / .1 are only transferred from the basic PLC
program to the PLC request signals DB21, ... DBX14.0 / .1 if FB1 parameter MMCToIF is set
to TRUE. If the parameters are not set, then the PLC request signals must be set by the PLC
user program.

If, during "Program test" spindles are not to be traversed, then they must be explicitly inhibited/
locked via the PLC user program:
● DB31, ... DBX128.0 = 0 (suppress program test)
● DB31, ... DBX128.1 = 1 (activate program test)
● DB31, ... DBX14.0 = 0 (from PLC: suppress program test)
● DB31, ... DBX14.1 = 1 (from PLC: activate program test)
Basic functions
NOTICE
Traversing motion of the spindles of the channel is enabled in the "Program test" as default
setting.
Enabling traversing motion of the axes


● Channel
● Axes/spindles
6.2.4 Multi-channel view

Prerequisites
The following preconditions must be satisfied so that in the multi-channel view in menu
"Program controls", the channels and spindles can be displayed:
● Channels
– More than one channel is parameterized (MD10010
$MN_ASSIGN_CHAN_TO_MODE_GROUP[<channel>] ≠ 0)
– Option "programSYNC" (6FC5800-0AP05-0YB0) is set/licensed
● Spindles
– The significance of the spindle, parameterized in the channel, has been defined
(MD52206 $MC_AXIS_USAGE[<spindle>] ≠ 0)
Selection
"Program test" (PRT) for one or several channels parameterized in the control is selected via
the user interface, e.g. SINUMERIK Operate:
2. Softkey: "Running-in"
3. "Program controls" menu: Deselect group "Running-in” > Check box "Channel x".
Basic functions
Check box channel/spindle

In menu "Program controls": The following behavior can be set for the "Running-in" group using
check box "Channel x" or "Spindle x":
Check box Selected Deselected

"Channel x" Normal operation Program is only calculated
(channel in test run)
"Spindle x" Normal operation No machining at spindle x
(spindle in test run)

After deselecting the checkbox for "Channel x", the channel is in the "Program test (PRT)" state.
The following NC/PLC interface signals are set (see below note "Automatic transfer of interface
signals"):
● Channels
– DB21, ... DBX25.7 == 1 (from HMI: program test selected)
– DB21, ... DBX33.7 == 1 (from NC: program test active)
● Axes
– DB31, ... DBX128.1 == 0 (activate program test from HMI)
In the default setting, the control boxes for the spindles are selected, i.e. spindles are in normal
operation:
● Spindles
– DB31, ... DBX128.1 == 0 (from HMI: activate program test)
Note
● Axes: Inhibited
Basic functions
Note
Automatic transfer of the interface signals
The HMI request signals DB21, ... DBX128.0 / .1 are only transferred from the basic PLC
program to the PLC request signals DB21, ... DBX14.0 / .1 if FB1 parameter MMCToIF is set
to TRUE. If the parameters are not set, then the PLC request signals must be set by the PLC
user program.

If, during "Program test" spindles of the channel are not to be traversed, then they must be
explicitly inhibited/locked via the PLC user program:
● DB31, ... DBX128.0 = 0 (suppress program test)
● DB31, ... DBX128.1 = 1 (activate program test)
NOTICE
Traversing motion of the spindles of the channel is enabled in the "Program test" as default
setting.
Enabling traversing motion of the axes


● Channel
● Axes/spindles
Basic functions

The "program test" state can be interrogated using system variables:
● For the display in the user interface, in synchronized actions or with a preprocessing stop in
the part program via the system variables:
$AC_ISTEST "Program test" state for the channel

Supplies TRUE (1), if the "program test" state for the channel is active.
$AA_ISTEST[<n>] "Program test" state for the axis <n>
Supplies TRUE (1), if the "program test" state for axis <n> is active.
● Without preprocessing stop in the part program via the system variable:
$P_ISTEST Supplies TRUE (1), if the "program test" state for the channel is active.
Example
The channel runs under "program test" and axis "C" was withdrawn using "suppress program
test". A query using system variables then supplies the following result:
● $AC_ISTEST == TRUE
● $P_ISTEST == TRUE
● $AA_ISTEST[C] == FALSE

Axis interchange
The "axis interchange" function allows that an axis/spindle is known in several channels and
can be programmed by these alternately (see Section "Cross-channel axis interchange
(Page 549)").
In conjunction with the functions "program test" and "channel-by-channel running-in", the
following must be observed for an axis interchange:
● If only one of the channels is in the "program test" state, then the interchanged axis is taken
from this channel and is inserted in a channel that is not in the "program test" state. For an
interchanged axis with active axis disable, for a change via the channels with/without
channel state "program test", then the state in the axis itself does not change (see example
3).
● For a program test, for end of part program/reset, for all axes/spindles that do not
interpolate, resynchronization is made at the actual position. As a consequence, for an axis
interchange that is first made after the end of the program, as the axis may only exit the
channel at the end of the program, the simulated position reached is not transferred to the
accepting channel.
Note
The programs should also include a WAIT tag at the end in order that they are
simultaneously exited.
Basic functions
6.2.7 Examples
Example 1: Channel 2 is to be tested in a 3-channel system.
Test option 1: Program test without SERUPRO
1. The user decides which axes/spindles should actually be physically traversed. "Suppress
program test" is set for these axes.
2. The "program test" state is selected for channels 1 and 3.
3. Channels 1, 2 and 3 are started via the PLC.
4. "Program test" can be selected again after the end of the program.
5. If the actual setting of "suppress program test" is also practical for other situations (channel
1 or channel 3 are to be tested), then this signal can remain set. This is certainly practical
in many cases.
Test option 2: Program test with SERUPRO
1. The user decides which axes/spindles should actually be physically traversed. "Suppress
program test" is set for these axes.
2. The "program test" state is selected for channels 1 and 3.
3. Channels 1, 2 and 3 are started via the PLC.
4. A fault or an alarm occurs, the user interrupts with RESET.
5. SERUPRO at the interruption location of all 3 channels.
6. Search destination has been reached in all 3 channels.
7. Start all 3 channels.
8. Channels 1 and 3 are now again in "program test" and "channel-by-channel running-in" is
continued.
Example 2: Activating "suppress program test"

A channel is in program test. In operation, "suppress program test" should be initiated for axis
"Y" (at block N1010).

N1000 G0 Y1000
N1010 G4 F10
N1020 G0 G91 Y=10 ; Incremental traversing.
N1030 M30
With this sequence, the program moves to position 1010, i.e. the simulated component "1000"
of this axis is moved after activating "suppress program test".
Example 3: Program test and axis interchange

Axis X1 from channel 1 and axis X2 from channel 2 are assigned to the 1st machine axis AX1
of the NC.
Channel 1 with "Program test" Channel 2 without "Program test"

N10010 G0 G90 X0
Basic functions
Channel 1 with "Program test" Channel 2 without "Program test"

N10020 X1=100
N10030 WAITM(91,1,2)
N10040 WAITM(92,1,2)
N10050 M0
N10060 M30
N20010 WAITM(91,1,2)
N20020 G91 G0 X2=10
N20030 WAITM(92,1,2)
N20040 M0
N20050 M30
In block N20040, machine axis AX1 is interchanged to channel 2, the last position of the axis
from channel 1 is taken over and the axis traversed to position 110.
6.3.1 MDI mode: Path control mode and WAITMC
MDI mode: Continuous path mode and WAITMC

In the MDI mode, when starting to execute the MDI block buffer, it is not permissible that
the WAITMC in conjunction with the path control mode (G64 / G604), is located in the last block
of the MDI block buffer. Otherwise the program will stop with the last but one traversing block,
and can only be canceled with a reset.
Example
Before an NC start, the MDI block buffer contains the following blocks:

N10 G64 G1 G94 F5000 X100 ; Continuous path mode in the first block of
the
; MDI block buffer
N20 X200
N30 X300 ; Last but one traversing block
N40 X400 ; Program execution stops here
N50 WAITMC(...) ; due to WAITMC in N50.
; Cancellation with reset required!
Basic functions
6.3.2 Non-synchronous start of traversing motion after WAIT commands

In the case of channel coordination using WAIT commands, a non-synchronous start when
executing the following blocks can occur. This behavior occurs if an action is triggered in one
of the channels immediately before reaching the common synchronization location; the
consequence of which is implicit repositioning (REPOSA) in this delete distance-to-go.
Assumption: Current axis allocation in channels 1 and 2
● Channel 1: Axes Z1 and W
● Channel 2: Axis Z2
Example 1: Start of traversing motion with time offset

The following command sequences in channels 1 and 2 result in a possible problematical start
of traversing motion with time offset after the synchronization location N110 / N210:
Table 6-2 Sequence (time) in channels 1 and 2

... ... Any processing in channels 1 and 2
N100 W100 Channel 1: Traversing axis W
N110 WAITM(2,1,2) N210 WAITM(2,1,2) Channels 1 and 2: wait for synchronization
Start "AUTOGET(W)": "AUTOGET(W)" and
● Axis replacement wait for axis W from
channel 1 Channel 2: Start of traversing motion with time off‐
● Delete distance-to-
N220 Z2=100 W100 set
go
● REPOSA
End
Channel 1: Start of traversing motion
N120 Z1=100
Example 2: Simultaneous start of traversing motion

Start of traversing motion with time offset (delay) in example 1 can be avoided by explicitly
enabling and requesting the axis W to be replaced and by inserting an additional
synchronization location. The following command sequences in channels 1 and 2 result in a
simultaneous start of traversing motion after the synchronization location N120 / N220:
Table 6-3 Sequence (time) in channels 1 and 2

N100 W100 Channel 1: Traversing axis W
RELEASE(W) Channel 1: Enable axis W ⇒ The axis replacement
in channel 2 no longer affects channel 1
N215 GET(W) Channel 2: Request axis W. Axis replacement is
optimum from a time perspective, as axis W is al‐
ready enabled
Basic functions

N130 Z1=100 N230 Z2=100 W100 Channels 1 and 2: simultaneous start of traversing
motion
Basic functions
Cross-channel axis interchange 7
7.1 Overview
Note
Spindles
The following statements and functions regarding the "axis replacement" function for axes also
apply to spindles.
Each axis must be assigned to a channel during control commissioning. The axis can only be
traversed, for example, by part programs or synchronized actions from the channel to which the
axis is assigned. With the "axis replacement" function, it is possible to enable an axis and to
allocate it to another channel, that is, to replace the axis. Only than can the axis be traversed
by another channel.
Axis states
As part of the "axis replacement" function, an axis can have the following states:
● "Channel axis"
A channel axis is an axis that is assigned to a channel. It can be traversed via a part program
or manually.
● "PLC axis"
A PLC axis is an axis that is assigned to the PLC. It can only be traversed by the PLC user
program or function block FC18.
● "Neutral axis"
A neutral axis is an axis that is not currently assigned to a channel or the PLC. Before
traversing, it must first be requested by a channel or the PLC.
● "Axis in another channel"
An axis is in this state if a channel has requested the axis. However, it could not yet be
assigned to it because it is still occupied by another channel.
7.2 Commissioning

● General parameterization of the axis replacement form
MD10722 $MN_AXCHANGE_MASK
Basic functions
Cross-channel axis interchange
7.3 Programming: Releasing an axis (RELEASE)

● Parameterization of which axes belong to the channel or are channel axes:
MD20070 $MC_AXCONF_MACHAX_USED[<channel axis>] = <machine axis>
Note: Assignment of all axes used in the NC must be performed in any case as channel axes
of one or more channels, irrespective of the "axis replacement" function.

● If an axis is a channel axis in multiple channels, the machine data defines to which channel
the axis is assigned after control startup (power-on reset):
MD30550 $MA_AXCONF_ASSIGN_MASTER_CHAN[<channel>] = <channel number>
The parameterized channel is the master channel of the axis.
● Parameterization of the response if an axis is programmed in a part program and the axis
is not currently assigned to the channel:
– Display an alarm and do not traverse the axis.
– Automatically requesting the axis according to the command GET (Page 551)
– Automatically requesting the axis according to the command GETD (Page 551)
MD30552 $MA_AUTO_GET_TYPE[<axis>] = <response>
System variable
Axis-specific system variable
● Axis type in relation to axis replacement:
$AA_AXCHANGE_TYP[<axis>]
● Axis replacement status of the axis:
$AA_AXCHANGE_STAT[<axis>]
7.3 Programming: Releasing an axis (RELEASE)
Function
An axis that is assigned to the current channel is released for an axis interchange via the
predefined RELEASE() procedure and put into the "neutral axis" state for this purpose.
Syntax
RELEASE(<axis1>[, axis2 ... axis15])
Meaning
RELEASE: Release axis for axis interchange

Preprocessing Yes
stop:
Alone in the Yes
block:
Basic functions
7.4 Programming: Fetching an axis (GET, GETD)
<axis>: Axis: Channel axis name of the releasing axis

Spindle: Channel axis name of the releasing spindle or conversion of the spindle num‐
ber in the channel axis names by means of SPI(<spindle number>)
Type: AXIS
No enable possible
● The axis is involved in a transformation.
● The axis belongs to an axis grouping.
Guide axis of a gantry grouping

If the guide axis of a gantry grouping is released, all synchronous axes are also released.
Requesting axis interchange (GET):
Function
With the predefined GET() procedure, an axis is requested for the same channel.
In the channel, to which the axis is currently assigned, the axis must be released in a part
program or synchronized action for axis interchange with RELEASE().
After axis interchange, the axis has "channel axis" status.
Syntax
GET(<axis1>[, axis2 ... axis15])
Meaning
GET: Request of an axis for the current channel

Preprocessing Yes
stop:
Alone in the Yes
block:
<axis>: Axis: Channel axis name of the requested axis
Spindle: Channel axis name of the requested spindle or conversion of the spindle num‐
ber in the channel axis names by means of SPI(<spindle number>)
Type: AXIS
Axis interchange is delayed in the following situations:
● The axis has not yet been released with RELEASE by the channel to which it is assigned.
● A change of measuring system has not yet been completed.
Basic functions
● The change of status of the controller enable has not yet been completed (transition of rules
to follow-up/stop and vice versa).
● The NC/PLC interface signal "axis or spindle disable" is pending (DB31, ... DBX1.3 == 1)
● The current traversing movement (interpolation) of the axis has not yet been completed.
Fetching an axis directly (GETD)
Function
An axis that is not assigned to the current channel is required for the following machining
section of a part program. With the predefined procedure GETD(), the axis is fetched directly
from the channel to which the axis is assigned. For this purpose, the axis does not have to be
released by this channel with RELEASE().
After axis interchange, the axis has "channel axis" status.
Depending on the state of the axis in the relinquishing channel, a preprocessing stop is
triggered in this channel (STOPRE):
● "Channel axis" status ⇒ preprocessing stop
● "Neutral axis" status ⇒ no preprocessing stop
To coordinate transfer of the axis between the channels with GETD(), we recommend using
channel synchronization (Page 529) between the requesting and the relinquishing channel.
NOTICE
Preprocessing stop in the relinquishing channel
If the axis in the relinquishing channel has "channel axis" status, a preprocessing stop will be
triggered in this channel (STOPRE):
Syntax
GETD(<axis>)
Meaning
GETD: Fetching an axis directly into the current channel

Preprocessing Yes
stop:
Alone in the Yes
block:
<axis>: Axes: Channel axis name of the requested axis
Spindles: Channel axis name of the requested spindle or conversion of the spindle
number in the channel axis names by means of SPI(<spindle number>)
Supplementary condition
If the axis has "PLC axis" status in the relinquishing channel, the axis must be released for axis
interchange by the PLC user program.
Basic functions
7.5 Automatic axis replacement
Channel reset
● If a channel reset is triggered in the channel that requested the axis, axis interchange is
canceled.
● A replaced axis remains assigned to the channel that last requested it even after a channel
reset.
7.5 Automatic axis replacement
Function
Automatic axis replacement or automatic fetching of an axis into the current channel is
performed if the axis is programmed in the part program or synchronized action, but it is not
assigned to the channel at the moment.
Requirement
Parameterization of automatic axis replacement by GET() or GETD():
MD30552 $MA_AUTO_GET_TYPE (Page 549)
See Description (Page 551) of GETD().
Examples
Example 1

N1 M3 S1000 ; Traversing the main spindle
N2 RELEASE (SPI(1)) ; Release to neutral status
N3 S3000 ; Programming the main spindle => automatic fetching
; Behavior depending on MD30552 $MA_AUTO_GET_TYPE:
; 0 => Alarm "Wrong axis type"
; 1 => implicit GET(SPI(1))
; 2 => implicit GETD(SPI(1))
Example 2

; Machine axis AX1 ≙ channel axis X
N1 RELEASE (AX1) ; Release to neutral status
N2 G04 F2 ; Dwell time
N3 G0 X100 Y100 ; Programming axis X as a path axis
Basic functions
7.6 Axis replacement via PLC

; 1 => implicit GET(AX1)
; 2 => implicit GETD(AX1)
Example 3

; Machine axis AX1 ≙ channel axis X
N1 RELEASE (AX1) ; Release to neutral status
N2 G04 F2 ; Dwell time
N3 POS (X) = 100 ; Programming axis X as a positioning axis
; 1 => implicit GET(AX1) *)
; 2 => implicit GETD(AX1) *)
*) If the axis has not yet been synchronized, a separate block is generated for automatic
fetching of the axis using (GET() or GETD().
Function
Axis replacement can be requested by the PLC user program via the NC/PLC interface:
● From an NC channel to the PLC
● From the PLC to an NC channel
● From an NC channel to another NC channel
'%'%%3/&ൺ1&
%LW

5HTXLUHPHQW&KDQQHOQXPEHURIWKH
FKDQQHOWRZKLFKWKHD[LVLVWREHDVVLJQHG
5HTXLUHPHQW6ZLWFKRYHUD[LV
5HTXHVWIURP3/&ൺ
$FNQRZOHGJPHQWE\1&ൺ
5HTXLUHPHQW$[LVW\SH3/&D[LV
Figure 7-1 Axis replacement request: DB31, ... DBB8 (PLC → NC)
Axis replacement status

The current status of an axis with regard to axis replacement can be read by the PLC user
program via the NC/PLC interface.
Basic functions
'%'%%1&ൺ3/&
%LW

&KDQQHOQXPEHURIWKHFKDQQHOWR
ZKLFKWKHD[LVLVDVVLJQHG
1HZD[LVW\SHUHTXHVWHGE\WKH3/&
$[LVUHSODFHPHQWLVSRVVLEOH
1HXWUDOD[LV
$[LVW\SH
3/&D[LV
Figure 7-2 Axis replacement status: DB31, ... DBB68 (NC → PLC)
Examples
Example 1
Axis replacement of an axis from channel 1 to channel 2 by means of RELEASE() and GET()
in part programs that are executed in each channel:
● Channel 1: RELEASE(<axis>)
● Channel 2: GET(<axis>)
'%'%% '%'%%
$IWHUSRZHURQ

FKDQQHOD[LVLQ.
.5(/($6($;

7LPH
.*(7$;

Example 2
Status change of an axis assigned to channel 1 from "NC axis" to "PLC axis" by the PLC user
program.
Basic functions
'%'%% '%'%%
7LPH
$IWHUSRZHURQ
FKDQQHOD[LVLQ.
5HTXHVWE\3/&
1HZ7<33/&D[LV
5HTXHVWGHWHFWHG
$[LVUHSODFHPHQWSRVVLEOH
5HTXHVWE\1&UHVHW

3/&D[LVLQ.

Example 3
Status change of an axis assigned to channel 1 from "NC axis" via "PLC axis" to "neutral axis"
by the PLC user program.
'%'%% '%'%%
$IWHUSRZHURQ
7LPH
FKDQQHOD[LVLQ.
5HTXHVWE\3/&
1HZ7<33/&D[LV
5HTXHVWGHWHFWHG
5HTXHVWE\1&UHVHW

3/&D[LVLQ.
5HTXHVWE\3/&
1HZ7<31HXWUDOD[LV
5HTXHVWGHWHFWHG
1HXWUDOD[LVLQ 5HTXHVWE\1&UHVHW
.
Basic functions
7.8 Axis replacement with and without preprocessing stop
7.7 Axis interchange via axis container rotation
Enabling axis container rotation

When an axis container rotation is enabled, all container axes that can be allocated to a channel
are allocated to this channel using implicitly generated GET or GETD. An axis can only be
relinquished, e.g. to another channel, after container rotation.
Note
The implicit assignment of an axis to a channel is notpossible if the axis in the state "main run
axis" (e.g. is a PLC axis). In order to be able to participate in the axis container rotation, the axis
must first exit the state.
For further explanations on the axis replacement of container axes (see Section "B3:
Distributed systems").
Example: Axis container rotation with an implicit GET or GETD
Action Channel 1 Action Channel 2

SPOS = 180 positioned
AXCTSWE(CT 1) ; gets spindle in Channel 1
; and allows axis container rotation
Assumption:
The spindle is used in both channels and is also an axis in axis container CT 1.
Activation
Axis interchange using axis container rotation and implicit GET/GETD is activated using
machine data MD10722 $MN_AXCHANGE_MASK, bit 1=1.
Axis replacement extension without preprocessing stop

Instead of a GET block with a preprocessing stop, this GET request only generates an
intermediate block. In the main run, when this block is executed, the system checks whether the
states of the axes in the block match the current axis states. If they do not match, forced
reorganization can be triggered.
The following states of an axis or positioned spindle are checked for:
● The mode, either for the axis or for positioned spindle
● Setpoint position
Basic functions
The following states of a Spindle in speed mode are checked:

● Spindle mode: Speed mode
● Spindle speed S
● Direction of rotation M3, M4
● Gear stage M40, M41, M42, M43, M44, M45
● Master spindle at constant cutting rate.
In some instances, forced reorganization may be possible. Reorganization of the following
axes is forced in any case.
Activation
Replacement without preprocessing and checking of the current states is activated with
machine data MD10722 $MN_AXCHANGE_MASK, Bit 2=1.
Example
Activating an axis replacement without a preprocessing stop
Table 7-1
N010 M4 S1000
N011 G4 F2
N020 M5
N021 SPOS=0
N022 POS[B]=1
N023 WAITP(B) ; Axis b becomes the neutral axis
N030 X1 F10
N031 X100 F500
N032 X200
N040 M3 S500
N041 G4 F2
N050 M5
N099 M30
If the spindle (axis B) is traversed immediately after block N023 as a PLC axis to 180° and back
to 1°, and then again to the neutral axis, block N040 does not trigger a preprocessing stop nor
a reorganization.
Special case: Axis replacement with preprocessing stop

Without a GET or GETD instruction having previously occurred in the main run, the spindle or
the axis can be made available again by RELEASE (axis) or WAITP (axis), for example. A
subsequent GET leads to a GET with a preprocessing stop.
Basic functions
7.9 Axis exclusively controlled from the PLC
7.9 Axis exclusively controlled from the PLC
Function
After the control boots, the axis is in the "neutral axis" state. The PLC controls it. To traverse the
axis as competing positioning axis (from the PLC via function block FC18), the axis must first
be explicitly requested from the PLC.
Note
Per machine data, the axis interchange to the PLC can be exclusively restricted to PLC
controlled axes: MD10722 $MN_AXCHANGE_MASK, Bit 3 = 1
The axis cannot be traversed from an NC part program.
Parameterizing an axis as axis that is exclusively controlled from the PLC is realized using the
axis-specific machine data:
MD30460 $MA_BASE_FUNCTION_MASK, Bit 4 = 1
Control by PLC
The traversing behavior of an axis exclusively controlled from the PLC is only influenced by the
axial NC/PLC interface signals:
● DB31, ... DBX28.1 (reset)
● DB31, ... DBX28.2 (continue)
● DB31, ... DBX28.6 (stop along braking ramp)
Possible traversing functions

The following traversing functions are possible for axes exclusively controlled from the PLC:
1. Traversing in the JOG mode using the traversing keys and handwheel
2. Referencing the axis
3. Traversing as command axis via static synchronized actions
4. Traversing as asynchronous oscillating axis
5. Traversing as competing positioning axis from the PLC via FC18
After traversing functions 1. to 4. have been completed, the axis automatically goes back into
the "neutral axis" state. After traversing function 5. from the PLC has been completed, the axis
remains in the state "PLC axis". The axis only changes into the "Neutral axis" state after having
been explicitly released by the PLC.
Basic functions
7.10 Axis permanently assigned to the PLC
7.10 Axis permanently assigned to the PLC
Function
After the control has booted, the axis is in the "neutral axis" state and is controlled from the NC
channel. To traverse the axis as competing positioning axis (from the PLC via function block
FC18), the axis does not have to be explicitly requested from the PLC. Axis interchange to the
PLC is realized automatically using the traversing request via FC18. After the traversing motion
requested via FC18 has been completed, the axis again automatically changes into the "neutral
axis" state.
After the axis has been interchanged, and after the request from the PLC, the axis can also be
controlled from the PLC: "PLC axis" state.
Note
Per machine data, the axis interchange to the PLC can be exclusively restricted to axes that are
permanently assigned to the PLC: MD10722 $MN_AXCHANGE_MASK, Bit 3 = 1
Parameterizing an axis as axis that is permanently assigned to the PLC is realized using the
axis-specific machine data:
MD30460 $MA_BASE_FUNCTION_MASK, Bit 5 = 1
Control by the PLC or NC channel

The traversing behavior of an axis permanently assigned to the PLC can either be influenced
by the NC channel or by the PLC:
NC channel: Channel-specific NC/PLC interface signals (selection)
● DB21, ... DBXDBX7.1 (NC start)
● DB21, ... DBXDBX7.3 (NC stop)
● DB21, ... DBXDBX7.7 (reset)
PLC: Axial NC/PLC interface signals
● DB31, ... DBX28.1 (reset)
● DB31, ... DBX28.2 (continue)
● DB31, ... DBX28.6 (stop along braking ramp)
Possible traversing functions

The following traversing functions are possible for an axis permanently assigned to the PLC:
1. Traversing in the JOG mode using the traversing keys and handwheel
2. Referencing the axis
3. Traversing as competing positioning axis from the PLC via FC18
Basic functions
7.11 Geometry axis in rotated frame and axis replacement
After traversing functions 1. to 3. have been completed, the axis automatically goes back into
the "neutral axis" state.
7.11 Geometry axis in rotated frame and axis replacement
Replacement expansion via Frame with Rotation

In the JOG mode, a geometry axis with rotated WCS can be traversed as PLC axis or as a
command axis via static synchronized actions. For this purpose, the following machine data
must be set:
MD32074 $MA_FRAME_OR_CORRPOS_NOTALLOWED, bit 10 == 1
Note
Changing the operating mode in the JOG mode
Before changing the operating mode from JOG into another mode, all traversing motion of all
PLC and command axes, which have been linked as geometry axes in the rotated WCS, must
have been concluded. These axes must at least have become neutral axes again, otherwise
alarm 16908 will be output when the operating mode is changed. This alarm is also displayed
when only a single geometry axis is traversed as a PLC or command axis in the rotated
coordinate system.
Such an axis can only become a PLC or command axis within the channel. An axis replacement
in another channel is not permissible.
Prerequisite for changing from JOG to AUTOMATIC

When changing from the JOG to the AUTOMATIC mode, in the "Program interrupted" state, the
end point of geometry axis motion is only accepted if the following machine data is set:
MD 32074: FRAME_OR_CORRPOS_NOTALLOWED, bit 11 == 1
This positions the PLC or command axes in relation to the rotation of the frame.
All axes influenced by a rotating frame are considered as geometry axes grouping and are
handled collectively. In this way, all axes of the
● assigned to the NC program or
● all axes are neutral or
● all axes are active as main run axes (PLC, command, or oscillation axis).
For example, if one axis is programmed with a WAITP, the system waits for all further axes of
the geometry axis grouping, so that these axes can collectively become neutral axes. If one of
the axes becomes a PLC axis in the main run, then all other axes of this grouping become
neutral axes.
Basic functions
7.12 Axis replacement from synchronized actions
If MD32074 $MA_FRAME_OR_CORRPOS_NOTALLOWED, bit 10 == 0 and ROT Z45 is
programmed in the NC program, then for the X and Y axes no axis interchange is possible. This
is also analogously valid for the Z axis for e.g. ROT X45 or ROT Y45 – and also in the JOG
operating mode – if a block was interrupted with this type of programming. Although in this case
the NC/PLC interface signals "Axis replacement possible" (DB31, ...DBX68.5) are set for the X
and Y axes, these are however reset.
Only if MD32074 $MA_FRAME_OR_CORRPOS_NOTALLOWED, Bit 10 == 1 and no block
with this programming is being currently traversed, then in the JOG mode, these types of axes
can be interchanged.
Function
As action of a synchronized action, an axis can be requested for the channel (GET(<axis>))
or released for axis replacement (RELEASE(<axis>)).
Note
The axis must be assigned as a channel axis via machine data.
An axis can be transferred directly between channels to a certain channel with command
AXTOCHAN via synchronized actions or in the part program. This axis does not have to be the
same channel and it is not necessary that this channel be in possession of the current
interpolation right for the axis.
Current state and interpolation right of the axis

With which axis type and interpolation right a possible axis replacement is to be performed, can
be read from the following system variable:
<Value> = $AA_AXCHANGE_TYP[<axis>]
<Value> Meaning
0 The axis is assigned to the NC program
1 Axis assigned to PLC or active as command axis or oscillating axis
2 Another channel has the interpolation right.
3 Axis is neutral axis.
4 Neutral axis is controlled by the PLC.
5 Another channel has the interpolation right, axis is requested for NC program.
6 Another channel has the interpolation right, axis is requested as neutral axis.
7 Axis is PLC axis or active as a command axis/oscillating axis; the axis is requested for the NC
program.
8 Axis is PLC axis or active as a command axis/oscillating axis; the axis is requested as neutral
axis.
Basic functions
<Value> Meaning
9 Permanently assigned PLC axis, in the neutral axis state.
10 Permanently assigned PLC axis, controlled by PLC, in the neutral axis state.
A "permanently assigned PLC axis in the neutral axis state" (9) and a "permanently assigned
PLC axis controlled from the PLC in the neutral axis state" (10) is independent of GET and
RELEASE permanently assigned to the PLC. Whether the axis can also be replaced is
displayed in system variable $AA_AXCHANGE_STAT[axis].
State transitions GET, RELEASE from synchronous actions and when GET is completed
$AA_AXCHANGE_TYP=3 $AA_AXCHANGE_TYP=4
Neutral axis neutral axis is
requested as neutral axis

Axis (spindle) controlled by PLC
=3
$AA_AXCHANGE_TYP=
=4
GSf
Channel RSy Chan- =6
1 nel 2
GSy
GSy
$AA_AXCHANGE_TYPE=0
GSf
the interpolation right

another channel has
GSy
NC program
NC program
Axis (spindle) Axis (spindle)
GD
After power ON GSf =2
GSf
R0
BP GSy
requested for NC program

BP Rn
BP
Rn =5
PLC axis
(spindle)
PLC =8 PLC $AA_AXCHANGE_TYP=
GSy GSy
=1 requested as =7
neutral axis PLC
PLC assigned or
active as HL axis requested for NC program
RELEASE(AX ...) from synchronous actions GET (AX ...) from synchronous actions
RSy GSy
$AA_AXCHANGE_TYP=0 $AA_AXCHANGE_TYP=n
RESET key GSf GET if fulfilled in synchronous actions
R0 Release in neutral state via PLC BP GET via PLC
Rn Release to a spec. channel via PLC GD GET directly from NC program
PLC axis: PLC assigned or

PLC
active as HL axis
Basic functions
7.13 Axis interchange for leading axes (gantry)
Figure 7-3 Transitions from synchronized actions
Further information
Function Manual Synchronized Actions; Actions in synchronized actions
7.13 Axis interchange for leading axes (gantry)
Function
A closed gantry grouping is treated regarding its axes always as a unit regarding axis
interchange. This is the reason why for an axis interchange of the leading axis, an axis
interchange is simultaneously made for all synchronous axes of the gantry grouping. In addition
to the preconditions for the leading axis described in the previous chapters, the appropriate
preconditions must also be fulfilled for all synchronous axes of the gantry grouping.
Axial machine data

For an axis interchange, the following axial machine data must be set the same for all axes of
a closed gantry group:
● MD30460 $MA_BASE_FUNCTION_MASK, Bit 4 (control executing components)
● MD30460 $MA_BASE_FUNCTION_MASK, Bit 5 (assignment to components)
Axial NC/PLC interface signals

Within the scope of the axis interchange function, the following axial NC/PLC interface signals
always have the same values for all axes of a closed gantry grouping:
● DB31, ... DBX63.0 (reset executed)
● DB31, ... DBX63.1 (PLC controlled axis)
● DB31, ... DBX63.2 (axis stop active)
Axial system variable

Within the scope of the axis interchange function, the following axial system variables always
have the same values for all axes of a closed gantry group:
● $AA_AXCHANGE_TYP (axis type regarding axis interchange)
● $AA_AXCHANGE_STAT (axis status regarding axis interchange)
● $AA_SNGLAX_STAT (axis type of the individual axis)
Basic functions
7.14 State diagram
7.14 State diagram

The following figure shows the states, events, actions, and state transitions for an axis for
channel 1 in relation to the "axis replacement" function.
For channel 2, the sub-states "neutral axis" and "PLC axis" are not shown for clarity's sake.
Assumption: The axis is assigned to channel 1 by default:
MD30550 $MA_AXCONF_ASSIGN_MASTER_CHAN[<axis>] = 1
3RZHU2Q

&KDQQHO
:$,73$1'
$[LVLVQRWV\QFKURQL]HG
$1'
$[LVQRWPDLQUXQD[LV
5(/($6( 67235( 5(/($6(
25 25
:$,73 :$,73
1HXWUDOD[LV
*(7 *(7
25 25
&KDQQHOUHVHW &KDQQHOUHVHW
67235( 67235(
5HTXHVWE\3/&
*(7'D[LV!
67235(
&KDQQHO
&KDQQHOD[LV &KDQQHOD[LV
*(7'D[LV!
67235(
5HTXHVWE\3/& 5HTXHVWE\3/&
5HOLQTXLVKPHQWE\3/&
QHXWUDO
5HOLQTXLVKPHQWE\3/& 5HOLQTXLVKPHQWE\3/&
WRFKDQQHO WRFKDQQHO
67235( 67235(
3/&D[LV
① MD30550 $MA_AXCONF_ASSIGN_MASTER_CHAN[<axis>]
Figure 7-4 State diagram: Axis replacement
Basic functions

On the transition of an axis from "PLC axis," "neutral axis," or "axis in another channel" status
to "channel axis" status, synchronization with preprocessing stop and synchronization in the
fetching channel are performed. This involves:
● Axis: Accept the actual axis position
● Spindle: Accepting the current speed and current gearbox stage
7.15.1 Axis replacement by PLC

If the part program of the channel is in one of the following sections at the time the axis
replacement (PLC → channel or channel → PLC) is requested by the PLC, axis replacement will
only be performed after this machining section has been exited:
● Continuous-path mode (G64/G640)
● Thread cutting/tapping (G33/G331/G332)
7.15.2 Block search with calculation

On a block search with calculation, only the commands GET, GETD, and RELEASE, which do not
cancel each other out, are output in the action block.
Example
Block search with calculation to target block N700:

...
N100 RELEASE(AX1) ; RELEASE(AX1) is collected
N110 GET(AX2) ; GET(AX2) is collected
...
N400 GET(AX1) ; GET(AX1) cancels RELEASE(AX1) =>
; RELEASE(AX1) and GET(AX1) are not saved
...
N700 ... ; Target block ⇒ output: GET(AX2)
N710 RELEASE(AX2)
...
Further information
You will find more information under Block search, types 1, 2, and 4: (Page 121).
Basic functions
7.16 Example
7.16 Example
Assumptions
● Channel 1: The following axes are channel axes: 1, 2, 3, 4
● Channel 2: The following axes are channel axes: 4, 5, 6
● Default assignment: Axis 4 (AX4) is assigned to channel 1 by default
Channel 1
Axis names in the channel: MD20080
● $MC_AXCONF_CHANAX_NAME_TAB[<channel 1>][ 0 ] = "X" ; 1st channel axis
● $MC_AXCONF_CHANAX_NAME_TAB[<channel 1>][ 1 ] = "Y" ; 1st channel axis
● $MC_AXCONF_CHANAX_NAME_TAB[<channel 1>][ 2 ] = "Z" ; 1st channel axis
● $MC_AXCONF_CHANAX_NAME_TAB[<channel 1>][ 3 ] = "U" ; 1st channel axis
Machine axes used: MD20070
● $MC_AXCONF_MACHAX_USED[<channel 1>][ 0 ] = 1 ; 1st channel axis → axis 1
● $MC_AXCONF_MACHAX_USED[<channel 1>][ 1 ] = 2 ; 2nd channel axis → axis 2
● $MC_AXCONF_MACHAX_USED[<channel 1>][ 2 ] = 3 ; 3rd channel axis → axis 3
● $MC_AXCONF_MACHAX_USED[<channel 1>][ 3 ] = 4 ; 4th channel axis → axis 4
Channel 2
Axis names in the channel: MD20080
● $MC_AXCONF_CHANAX_NAME_TAB[<channel 2>][ 0 ] = "X" ; 1st channel axis
● $MC_AXCONF_CHANAX_NAME_TAB[<channel 2>][ 1 ] = "Y" ; 1st channel axis
● $MC_AXCONF_CHANAX_NAME_TAB[<channel 2>][ 2 ] = "U" ; 1st channel axis
Machine axes used: MD20070
● $MC_AXCONF_MACHAX_USED[<channel 2>][ 0 ] = 5 ; 1st channel axis → axis 5
● $MC_AXCONF_MACHAX_USED[<channel 2>][ 1 ] = 6 ; 2nd channel axis → axis 6
● $MC_AXCONF_MACHAX_USED[<channel 2>][ 2 ] = 4 ; 3rd channel axis → axis 4
Default assignment
Master channel of axis 4 (AX4) → channel 1
AX4 is the standard name of the 4th machine axis according to MD10000
$MN_AXCONF_MACHAX_NAME_TAB[ 3 ]
● MD30550 $MA_AXCONF_ASSIGN_MASTER_CHAN[ AX4 ] = 1
Basic functions
7.17 Data lists
Program example
Program in channel 1 Program in channel 2
... ...
; Traversing axis 4 (AX4) ; Synchronization point with channel 1
G01 F1000 U100 ; WAITM(1,1,2)
; Release of AX4 ; Request for AX4
RELEASE(AX4) GET(AX4)
; Selection of program TAUSH2 in channel ; Traversing axis 4 (AX4)
2: G0 U0
INIT (2,"_N_MPF_DIR\_N_TAUSH2_MPF","S")
; Start program TAUSH2 in channel 2 ...
START(2)
; Synchronization point with channel 2 ; Release of AX4
WAITM (1,1,2) RELEASE(AX4)
... ...
M30 M30
7.17 Data lists
7.17.1 Machine data

10010 ASSIGN_CHAN_TO_MODE_GROUP[n] Channel valid in mode group [Channel No.]: 0, 1
10722 AXCHANGE_MASK Parameterization of the axis replacement response
Basic machine data of channel

20050 AXCONF_GEOAX_ASSIGN_TAB[n] Assignment of geometry axis to channel axis
[GEOAxisNo.]: 0...2
20060 AXCONF_GEOAX_NAME_TAB[n] Geometry axis name in the channel
[GEOAxisNo.]: 0...2
20070 AXCONF_MACHAX_USED[n] Machine axis number valid in channel
[Channel axis No.]: 0...7
Basic functions
7.17 Data lists

20080 AXCONF_CHANAX_NAME_TAB[n] Channel axis name in the channel
[Channel axis No.]: 0...7
20090 SPIND_DEF_MASTER_SPIND Initial setting of master spindle in channel
20100 DIAMETER_AX_DEF Geometry axis with transverse axis function
20110 RESET_MODE_MASK Determination of basic control settings after Reset/TP
End
20112 START_MODE_MASK Determination of basic control settings for NC start
20150 GCODE_RESET_VALUES[n] Initial setting of the G groups
[G group No.]: 0...59
20160 CUBIC_SPLINE_BLOCKS Number of blocks for C spline
20170 COMPRESS_BLOCK_PATH_LIMIT Maximum traversing length of NC block for compression
20200 CHFRND_MAXNUM_DUMMY_BLOCKS Empty blocks with phase/radii
20210 CUTCOM_CORNER_LIMIT Max. angle for compensation blocks for tool radius com‐
pensation
20220 CUTCOM_MAX_DISC Maximum value for DISC
20230 CUTCOM_CURVE_INSERT_LIMIT Maximum angle for intersection calculation with tool ra‐
dius compensation
20240 CUTCOM_MAXNUM_CHECK_BLOCKS Blocks for predictive contour calculation with tool radius
compensation
20250 CUTCOM_MAXNUM_DUMMY_BLOCKS Number of blocks without traversing motion for tool ra‐
dius compensation
20270 CUTTING_EDGE_DEFAULT Initial state of tool cutting edge without programming
20400 LOOKAH_USE_VELO_NEXT_BLOCK Look Ahead to programmed following block velocity
20430 LOOKAH_NUM_OVR_POINTS Number of override switch corner values for Look Ahead
20440 LOOKAH_OVR_POINTS[n] Override switch corner values for Look Ahead
[Corner value No.]: 0...1
20500 CONST_VELO_MIN_TIME Minimum time with constant velocity
20610 ADD_MOVE_ACCEL_RESERVE Acceleration reserve for overlaid motion
20650 THREAD_START_IS_HARD Acceleration behavior of axis when thread cutting
20700 REFP_NC_START_LOCK NC start inhibit without reference point
20750 ALLOW_GO_IN_G96 G0 logic in G96
20800 SPF_END_TO_VDI Subprogram end to PLC
21000 CIRCLE_ERROR_CONST Circle end point monitoring constant
21010 CIRCLE_ERROR_FACTOR Circle end point monitoring factor
21100 ORIENTATION_IS_EULER Angle definition for orientation programming
21110 X_AXIS_IN_OLD_X_Z_PLANE Coordinate system for automatic frame definition
21200 LIFTFAST_DIST Traversing path for fast retraction from the contour
21250 START_INDEX_R_PARAM Number of first channel-specific R parameter
Basic functions
7.17 Data lists
Auxiliary function settings of the channel

22000 AUXFU_ASSIGN_GROUP[n] Auxiliary function group
[aux. func. no. in channel]: 0...49
22010 AUXFU_ASSIGN_TYPE[n] Auxiliary function type
22020 AUXFU_ASSIGN_EXTENSION[n] Auxiliary function extension
22030 AUXFU_ASSIGN_VALUE[n] Auxiliary function value
22200 AUXFU_M_SYNC_TYPE Output timing of M functions
22210 AUXFU_S_SYNC_TYPE Output timing of S functions
22220 AUXFU_T_SYNC_TYPE Output timing of T functions
22230 AUXFU_H_SYNC_TYPE Output timing of H functions
22240 AUXFU_F_SYNC_TYPE Output timing of F functions
22250 AUXFU_D_SYNC_TYPE Output timing of D functions
22260 AUXFU_E_SYNC_TYPE (available soon) Output timing of E functions
22400 S_VALUES_ACTIVE_AFTER_RESET S function active after RESET
22410 F_VALUES_ACTIVE_AFTER_RESET F function active after reset
22500 GCODE_OUTPUT_TO_PLC G commands to PLC
22550 TOOL_CHANGE_MODE New tool offset for M function
22560 TOOL_CHANGE_M_CODE M function for tool change
Channel-specific memory settings

25000 REORG_LOG_LIMIT Percentage of IPO buffer for log file enable
28000 MM_REORG_LOG_FILE_MEM Memory size for REORG (DRAM)
28010 MM_NUM_REORG_LUD_MODULES Number of blocks for local user variables for REORG (DRAM)
28020 MM_NUM_LUD_NAMES_TOTAL Number of local user variables (DRAM)
28030 MM_NUM_LUD_NAMES_PER_PROG Number of local user variables per program (DRAM)
28050 MM_NUM_R_PARAM Number of channelspecific R parameters (SRAM)
28070 MM_NUM_BLOCKS_IN_PREP Number of blocks for block preparation (DRAM)
28090 MM_NUM_CC_BLOCK_ELEMENTS Number of block elements for compile cycles (DRAM)
28100 MM_NUM_CC_BLOCK_USER_MEM Size of block memory for compile cycles (DRAM)
28500 MM_PREP_TASK_STACK_SIZE Stack size of preparation task (DRAM)
28510 MM_IPO_TASK_STACK_SIZE Stack size of IPO task (DRAM)
Basic functions
7.17 Data lists

30460 BASE_FUNCTION_MASK Axis functions
30550 AXCONF_ASSIGN_MASTER_CHAN Reset position of channel for axis change
30552 AUTO_GET_TYPE Definition of automatic GET
30600 FIX_POINT_POS Fixed value positions of axes with G75
32074 FRAME_OR_CORRPOS_NOTALLOWED Frame or HL offset are not allowed
7.17.2 Setting data
Number Identifier: $SC_ Description

42000 THREAD_START_ANGLE Start angle for thread
42100 DRY_RUN_FEED Dry run feedrate
Basic functions
7.17 Data lists
Basic functions
Preprocessing 8
Preprocessing
The programs stored in the directories for standard and user cycles can be preprocessed to
reduce runtimes.
Preprocessing is activated via machine data.
Standard and user cycles are preprocessed when the power is switched on, i.e. as an internal
control function, the part program is translated (compiled) into a binary intermediate code
optimized for processing purposes.
All program errors that can be corrected by means of a compensation block are detected during
preprocessing. In addition, when the program includes branches and check structures, a check
is made to ensure that the branch destinations are present and that structures are nested
correctly.
The full scope of control functionality is available:
● Override influence
● Reactions to data and signals that are input by the PLC or the operator
● Current block display
● The programs can be processed in single block mode (SBL1 and SBL2). Block searches
can be executed. The compilation cannot be stored; it is concealed from the user and
regenerated every time the power is switched on.
Preprocessing can be used:
● To optimize the runtimes of part programs with high-level language components (branches,
check structures, motion-synchronous actions)
● CPU time intensive part programs (e.g. stock removal cycles)
● Faster processing of time-critical sections (e.g. program continuation after preprocessing
stop during rapid deletion of distance-to-go, or return stroke, or in the tool change cycle).
General information
Preprocessing standard and user cycles is possible. The processing time of part programs can
then be reduced without restricting the control functionality.
The standard and user cycles are preprocessed when machine data is set accordingly:
MD10700 $MN_PREPROCESSING_LEVEL (program preprocessing level)
Preprocessing is carried out program-specifically. It is possible to mix preprocessed part
programs and part programs interpreted in ASCII format. Preprocessing serves to reduce
incidental times.
Basic functions
Preprocessing
Memory space is needed for preprocessing cycles. You can optimize your memory utilization
in two ways:
● The program to be executed can be shortened with the command DISPLOF (display off).
● MD10700 $MN_PREPROCESSING_LEVEL has been expanded by bit 2 and 3. This allows
selective cycle preprocessing of the individual directories (e.g. user cycles).
MD10700 $MN_PREPROCESSING_LEVEL has been expanded by bit 4. In this way, the
preprocessing of the user cycles can be selected from the directory _N_CMA_DIR.
MD10700 $MN_PREPROCESSING_LEVEL has been expanded by bit 5. In this way,
individual user cycles can be preprocessed in a targeted manner if they have the command
PREPRO after the PROC instruction.
Precompiled cycles are stored in the dynamic NC memory by default. MD10700
$MN_PREPROCESSING_LEVEL has been expanded by bit 6. This allows specifying that the
compiled programs that are now stored in the dynamic NC memory and no longer have enough
space can be stored in static NC memory.
Functionality
The programs stored in the directories for standard and user cycles are preprocessed when the
power is switched on, i.e. the part program is translated (compiled) into an intermediate binary
code optimized for processing purposes. The compilation is processed when called.
Runtime optimization
The preprocessing function is primarily suited for optimizing the runtimes of part programs with
high-level language components (jumps, control structures, synchronized actions).
While jumps and control structures are dissolved by a search through all blocks (block start)
when part programs are interpreted in ASCII format (active as default), a branch is made
directly to the destination block in a preprocessed part program.
This lifts the runtime differences between jumps and control structures.
Example of preprocessing execution time:
Execution reduction by 30% with active compressor
DEF INT COUNTER
Target: G1 G91 COMPCAD
G1 X0.001 Y0.001 Z0.001 F100000
COUNTER=COUNTER +1
COUNTER=COUNTER -1
COUNTER=COUNTER +1
IF COUNTER<= 100000 GOTOB TARGET
Computation-intensive programs and programs with symbolic names are processed more
quickly.
Execution time-critical sections (e.g. continuation of processing after deletion of distance-to-go
or preprocessing stop in cycles) can be processed faster.
Basic functions
Preprocessing
8.2 Program handling
If the interrupt routine exists as a preprocessed cycle, the processing can be continued more
quickly after the program interrupt.
Activation/Deactivation
Cycles are preprocessed on POWER ON if the following machine data is set:
MD10700 $MN_PREPROCESSING_LEVEL, bit 1 (program preprocessing level)
Bit Value Meaning

0 No preprocessing
0 Call description of cycles is not known by default.
Cycles, like normal subprograms, have to be stated as external before the cycle call.
This is a sensible setting when no cycles with call parameters are used.
1 During control power-up, the call description of the cycles is generated. All user cycles
(_N_CUS_DIR directory) and Siemens cycles (_N_CST_DIR directory) with transfer
parameters can be called up without external statement. Changes to the cycle-call
interface do not take effect until the next POWER ON.
The following machine data must be set:
MD18170 $MN_MM_NUM_MAX_FUNC_NAMES (number of auxiliary actions)
MD18180 $MN_MM_NUM_MAX_FUNC_PARAM (number of auxiliary parameters for
cycles)
1 1 During control power-up, all cycles are preprocessed into a compilation optimized for
processing. All user cycles (_N_CUS_DIR directory) and standard cycles
(_N_CST_DIR directory) are processed at high speed. Program changes to cycle
programs do not take effect until the next POWER ON.
2 1 During control power-up, the standard cycles in the _N_CST_DIR directory are pre‐
processed in a compilation optimized for processing.
3 1 During control power-up, the user cycles in the _N_CUS_DIR directory are prepro‐
cessed in a compilation optimized for processing.
4 1 Preprocessing of user cycles from the directory _N_CMA_DIR
5 1 Preprocessing the user cycles with the PREPRO command in the PROC instruction
line. Unmarked files of directories marked with bits 1-4 are not preprocessed.
If bit 0, then control of the preprocessing is carried out in accordance with the speci‐
fications of bits 0-4.
6 0 The compilation is stored in the dynamic NC memory as long as free memory is still
available. If sufficient memory is not available, preprocessing is aborted.
The size of the dynamic NC memory is obtained with this machine data:
MD18351 $MN_MM_DRAM_FILE_MEM_SIZE.
The areas occupied in the dynamic NC memory by the compilation are visible to the user.
Bit combinations are permissible.
Basic functions
Preprocessing
Compiling
Subroutines (_SPF file extension) located in the directories for standard cycles (_N_CST_DIR,
_N_CMA_DIR) and user cycles (_N_CUS_DIR) and any subroutines marked with PREPRO are
compiled. The name of the compilation corresponds to the original cycle with extension _CYC.
Note
Program changes to precompiled programs do not take effect until the next POWER ON.
Access rights
The preprocessed program can only be executed, but not read or written. The compilation
cannot be modified or archived. The original cycles _SPF files are not deleted.
The compilation is not changed when the ASCII cycle is altered, i.e. changes do not take effect
until after the next POWER ON.
Memory requirements
The memory requirement for compiled cycles is approximately factor 2 in addition to the ASCII
part program.
The memory requirements for variables defined in the part programs are defined by the
following machine data:
MD28020 $MC_MM_NUM_LUD_NAMES_TOTAL (number of local user variables)
MD28010 $MC_MM_NUM_REORG_LUD_MODULES (number of modules for local user
variables with REORG)
MD28040 $MC_MM_LUD_VALUES_MEM (memory size for local user variables)
MD18242 $MC_MM_MAX_SIZE_OF_LUD_VALUE (memory block size for LUD/GUD values)
Further information is provided under Memory configuration (Page 799).
While preprocessing is in progress, the amount of memory required is the same as if the
preprocessed program were called on the first subprogram level.
When programs are preprocessed after POWER ON, a name is counted for each branch
destination/label as if it were a variable. These names must be taken into account in the
MD28020 $MC_MM_NUM_LUD_NAMES_TOTAL (number of local user variables)
Example
PROC NAMES ;
DEF INT VARIABLE, ARRAY[2] ; 2 names
START: ; 1 name, only for preprocessing
FOR VARIABLE = 1 TO 9 ; 1 name, only for preprocessing
Basic functions
Preprocessing
8.3 Program call

G1 F10 X=VARIABLE*10-56/86EX4+4*SIN(VARI-
ABLE/3)
ENDFOR ; 1 name, only for preprocessing
M17
In order to execute this program normally, the following machine data must specify at least 3
names:
MD28020 $MC_MM_NUM_LUD_NAMES_TOTAL
Six names are required to compile this program after POWER ON.
Preprocessed programs/cycles are stored in the dynamic NC memory. The space required for
each program must be flashed over unmodified as outlined above. Adjustment of the memory
mapping in the static NC memory is required only if bit 6 = 1 is set in the following machine data:
MD10700 $MN_PREPROCESSING_LEVEL (program processing level)
In this case, the program compilations for which there is insufficient space in the dynamic NC
memory are stored in the static NC memory.
Examples for appropriate machine data settings can be found under "Examples" in the
Subsection "Preprocessing in the dynamic NC memory".
8.3 Program call
Overview
Main programs User cycles Standard cycles
/_N_MPF_DIR /_N_CUS_DIR /_N_CST_DIR
Main program
Call
CYCLE_SPF ASCII
without preprocessing Cycle
CYCLE _N_CYCLE_SPF
Preprocessing
CYCLE_CYC
_N_MAIN_SPF Call Pre-

with preprocessing processed
Cycle
_N_CYCLE_CYC
Figure 8-1 Generation and call of preprocessed cycles without parameters
Basic functions
Preprocessing
8.3 Program call
Main programs User cycles Standard cycles
/_N_MPF_DIR /_N_CUS_DIR /_N_CST_DIR
Main program ASCII

Call
without preprocessing Cycle
PROC CYCLE95
(REAL FFW1, ...)
CYCLE95 (10...)
_N_CYCLE95_SPF
Preprocessing
Call Pre-
with preprocessing processed
Cycle
_N_CYCLE95_CYC
Figure 8-2 Generation and call of preprocessed cycles with parameters
Call
● Compiled cycle: A compiled cycle is called in exactly the same way as a normal subroutine.
Example: CYCLE
● Preprocessing is activated: The compiled cycle is called instead of the ASCII cycle.
– If the subroutine is called explicitly with extension _SPF, then the ASCII cycle is called
even if a compilation is available.
Example: CYCLE_SPF; ASCII cycle call
– If the subroutine is called explicitly with extension _CYC, then the preprocessed cycle is
called (assuming that it is available). An error message is output if no compilation is
available.
Example: CYCLE_CYC; calls a precompiled cycle
– If bit 5 is set and a file that is not marked with PREPRO is called explicitly with the
extension _CYC, an error message is issued with Alarm 14011.
● If a subroutine is called without explicit extension, an attempt is first made to load the
program. If this is not possible (not marked with PREPRO), an attempt is made to load the
SPF program.
Basic functions
Preprocessing
8.4 Constraints
● The change to an external language mode with G291 is rejected and an alarm issued. When
calling a precompiled cycle, an explicit change is made into the Siemens language mode.
● When the subroutine is called, it is checked whether the compiled file is older than the cycle.
If so, the compile file is deleted and an alarm issued. The user must preprocess the cycles
again.
Note
Only cycles without parameters may be called with the extension _SPF or _CYC.
It is not permissible that PUDs are used in cycles that have been preprocessed. The PUDs
are created in the calling main program. At the time of compilation after POWER ON, this
data is not known to the cycles.
The actual program display shows whether the current ASCII cycle or the compilation has been
called (extension _SPF or _CYC).
Call condition
All cycles in the cycle directories must be compiled before preprocessing is activated. Non-
compiled cycles in _N_CUS_DIR and _N_CST_DIR which were loaded after POWER ON, for
example, can only be called through explicit specification of extension _SPF.
If preprocessing is active and bit 5 is set, all programs that do not start with the PREPRO PROC
instruction are not precompiled.
Syntax check
All program errors, which can be corrected using a correction block, are already identified at the
time of preprocessing. In addition, when the program includes branches and check structures,
a check is made to ensure that the branch destinations are present and that structures are
nested correctly.
Branch destinations and labels must be unique in the program.
After the errors detected during preprocessing have been corrected, preprocessing must be
started again by means of an NC POWER ON.
8.4 Constraints
Availability of the "preprocessing" function

The function is an option ("Program pre-processing"), which must be assigned to the hardware
via the license management.
Language scope
The full vocabulary of the NC language is available in the part program.
Basic functions
Preprocessing
8.4 Constraints
There are no restrictions on the calculation of measured process variables and in the reaction
to signals from the process and other channels (override, deletion of distance-to-go, motion-
synchronous actions, channel coordination, interrupt processing, etc.).
Axis name
Part programs are compiled independently of channels. For this reason, the geometry and
channel names set in the following machine data must be identical in all channels if they
are used directly in the precompiled cycles:
MD20060 $MC_AXCONF_GEOAX_NAME_TAB (name of the geometry axis in the channel)
Generally speaking, axis names are not used directly in machining cycles since cycles are
written as follows:
● independently of channels and
● independently of the axis names defined on the machine.
The axes to be traversed are addressed indirectly via machine data or transferred as
parameters:
● Indirect axis programming:
– IF $AA_IM[AXNAME($MC_AXCONF_CHANAX_NAME_TAB[4])] > 5
; This branch will pass through if the actual value of the 5th channel axis
; with reference to the machine coordinate system is greater than 5.
– G1 AX[AXNAME($MC-AXCONF-GEOAX-NAME-TAB[0])] = 10
F1000 G90.
; Traverse the 1st geometry axis to the value 10.
ENDIF
● Transfer of axis to be traversed from the main program:
– Cycle definition
PROC DRILL(AXIS DRILL_AXIS)
WHILE $AA_IW[DRILL_AXIS] > -10
G1 G91 F250 AX[DRILL_AXIS] = -1
ENDWHILE
– Call from the main program
DRILL(Z)
Basic functions
Preprocessing
8.5 Examples
8.5 Examples
8.5.1 Preprocessing individual files

PROC UP1 PREPRO ; Preprocessing if bit 5 = 1
; in PREPROCESSING_LEVEL
N1000 DEF INT COUNTER
N1010 TARGET: G1 G91 COMPCAD
N1020 G1 X0.001 Y0.001 Z0.001 F100000
N1030 COUNTER=COUNTER+1
N1040 COUNTER=COUNTER-1
N1050 COUNTER=COUNTER+1
N1060 IF COUNTER<=10 GOTOB TARGET
N1070 M30
PROC UP2
N2000 DEF INT VARIABLE, ARRAY[2]
N2010 IF $AN_NCK_Version < 3.4
N2020 SETAL(61000)
N2030 ENDIF
N2040 START:
N2050 FOR VARIABLE = 1 TO 5
N2060 G1 F1000 X=VARIABLE*10-56/86EX4+4*SIN(VARIABLE/3)
N2070 ENDFOR
N2080 M17
PROC MAIN
N10 G0 X0 Y0 Z0
N20 UP1
N30 G0 X10 Y10 Z10
N40 UP2
N50 G0 X100 Y100
N60 UP3
N70 G0 X10 Y10
N80 M30
Sample constellations:
a) Bit 5 = 1
MD10700 $MN_PREPROCESSING_LEVEL=45 ; bit 0, 2, 3, 5
Subprogram UP1 is pretranslated, and the call description is generated.
Subprogram UP2 is not pretranslated, but the call description is generated.
b) Bit 5 = 0
Basic functions
Preprocessing
8.5 Examples
MD10700 $MN_PREPROCESSING_LEVEL=13 ; bit 0, 2, 3,

Both subprograms are pretranslated, and the call description is generated.
c) Example of an invalid subprogram with activated compiling:

PROC SUB1 PREPRO
G291 ; ← Alarm when compiling, G291 not possible
G0 X0 Y0 Z0
M17
8.5.2 Preprocessing in the dynamic NC memory

Machine data for preprocessing only in the dynamic NC memory with selective selection:

; Bit 5 = 1 Selective program selection
; Bit 6 =0 no switch to
; static NC memory if
; dynamic NC memory is full
N30 $MN_MM_DRAM_FILE_MEM_SIZE = 800 ; Reserve space
N40 $MN_PREPROCESSING_LEVEL = 63 ; Bit 0-5 = 1
M17
Machine data for preprocessing in the dynamic NC memory with the option of using the static
NC memory and selective selection:

; Bit 5 = 1 Selective program selection
; Bit 6 = 1 switch to static
; NC memory if dynamic NC
; memory full
N30 $MN_MM_DRAM_FILE_MEM_SIZE = 800 ; Reserve space
N40 $MN_PREPROCESSING_LEVEL = 127 ; Bit 0-6 = 1
M17
Basic functions
Preprocessing
8.6 Data lists
8.6 Data lists
8.6.1 Machine data

10700 PREPROCESSING_LEVEL Program preprocessing level
18242 MM_MAX_SIZE_OF_LUD_VALUE Maximum LUD-variable array size

28010 MM_NUM_REORG_LUD_MODULES Number of blocks for local user variables for REORG
(DRAM)
28020 MM_NUM_LUD_NAMES_PER_PROG Number of local user variables (DRAM)
Basic functions
Preprocessing
8.6 Data lists
Basic functions
Emergency stop 9
Function
The control system supports the machine manufacturer in implementing an emergency stop
function on the basis of the following functions:
● An emergency stop button is installed in a location easily accessible to the machine operator
on all SINUMERIK machine control panels. The functionality of the emergency stop button
includes the positive opening of electrical switching contacts and a mechanical self-
activating latching/locking.
● The emergency stop request to the NC is transmitted via the NC/PLC interface on the PLC.
● The Emergency Stop function must bring the machine to a standstill according to stop
category 0 or 1 (EN 60204).
● In the case of an emergency stop, all machine functions controlled by the PLC can be
brought to a safe state that can be set by the machine manufacturer.
● Unlatching the emergency stop button does not cancel the emergency stop state nor does
it initiate a restart.
● After the emergency stop state has been canceled, it is not necessary to reference the
machine axes or synchronize the spindles. The actual positions of the machine axes are
continuously tracked during the emergency stop sequence.
9.2 Relevant standards
Relevant standards
Compliance with the following standards is essential for the emergency stop function:
● EN ISO 12000-1
● EN ISO 12000-2
● EN 418
● EN 60204
Emergency stop
In accordance with EN 418, an emergency stop is a function that:
● Is intended to prevent or diminish developing or existing risks to operating personnel, and
damage to the machine or machined materials.
● Is triggered by a single action of a person, if the normal stop function is not suitable for it.
Basic functions
Emergency stop
9.3 Emergency stop control elements
Hazards
In the terms of EN 418, risks may arise from:
● Functional irregularities (machine malfunctions, unacceptable properties of the material to
be machined, human error, etc.).
● Normal operation.
Stadard EN ISO 12000-2

In accordance with the basic safety requirement of the EC Machinery Directive regarding
emergency stop, machines must be equipped with an energency stop device.
Exceptions
No emergency stop device is required on machines:
● Where an emergency stop device would not reduce the risk, either because the shutdown
time would not be reduced or because the measures to be taken would not be suitable for
controlling the risk.
● That are held and operated manually.
Note
The machine manufacturer is expressly directed to comply with the national and
international standards. The SINUMERIK controllers support the machine manufacturer in
the implementation of the emergency stop function according to the specifications in the
following function description. But the responsibility for the emergency stop function (its
triggering, sequence and acknowledgement) rests exclusively with the machine
manufacturer.
9.3 Emergency stop control elements
Emergency stop control elements

In accordance with EN 418, emergency stop control elements must be designed so that they
latch mechanically on their own and are easy for the operator and others to actuate in the event
of an emergency.
The following list includes some possible types of control elements:
● Mushroom pushbutton switches
● Wires/cables, cords, rods
● Puller grips
● In special cases: Foot switches without protective covers
Basic functions
Emergency stop
9.4 Emergency stop sequence
Emergency stop button and control

Actuation of the emergency stop button or a signal derived directly from the button must be
routed to the controller (PLC) as a PLC input. In the PLC user program, this PLC input must be
forwarded to the NC on the interface signal:
DB10 DBX56.1 (Emergency stop)
Resetting of the emergency stop button or a signal derived directly from the button must be
routed to the controller (PLC) as a PLC input. In the PLC user program, this PLC input must be
forwarded to the NC on the interface signal:
DB10 DBX56.2 (Acknowledge emergency stop)
Connection conditions
For connection of the emergency stop button, see:
Equipment Manual Operator Components
9.4 Emergency stop sequence

After actuation of the emergency stop control element, the emergency stop device must
operate in the best possible way to prevent or minimize the danger.
"In the best possible way" means that the most favorable delay rate can be selected and the
correct stop category (defined in EN 60204) can be determined according to a risk assessment.
Emergency stop sequence in the NC

The predefined (in EN 418) sequence of internal functions implemented to obtain the
emergency stop state is as follows in the control system:
1. Part program execution is interrupted.
All machine axes are braked in the relevant axis-specific parameterized time:
MD36610 $MA_AX_EMERGENCY_STOP_TIME (time of braking ramp in event of errors)
The maximum braking ramp that can be achieved thereby, is defned by the maximum brake
current of the respective drive. The maximum brake current is achieved by setting a setpoint
= 0 (fast braking).
2. Reset interface signal:
DB11 DBX6.3 (Mode group ready)
3. Set the interface signal:
DB10 DBX106.1 (emergency stop active)
4. Alarm 3000 "Emergency stop" is displayed.
5. After the expiry of a paramaterized delay time, the servo enables of machine axes are reset.
The setting of the delay time is programmed in machine data:
MD36620 $MA_SERVO_DISABLE_DELAY_TIME (OFF delay of the controller enable)
The following setting rule must be observed: MD36620 ≥ MD36610
6. All machine axes are switched in the follow-up mode within the controller.
The machine axes are no longer in position control.
Basic functions
Emergency stop
9.5 Emergency stop acknowledgement
Emergency stop sequence at the machine

The emergency stop sequence on the machine is determined solely by the machine
manufacturer.
Attention should be paid to the following points in connection to the sequence on the NC:
● The process in the NC is started using the interface signal:
DB10 DBX56.1 (Emergency stop)
After the machine axes have come to a standstill, the power supply must be interrupted, in
compliance with EN 418.
Note
The responsibility for interrupting the power supply rests with the machine manufacturer.
● The digital and analog outputs of the PLC I/O are not influenced by the emergency stop
sequence in the NC.
If individual outputs are required to attain a particular state or voltage level in the event of an
emergency stop, the machine manufacturer must implement this in the PLC user program.
● The fast digital outputs of the NCK I/O system are not influenced by the emergency stop
sequence in the NC.
If individual outputs must assume a specific state in case of emergency stop, the machine
manufacturer must transmit the desired state to the NC in the PLC user program via
interface signals:
DB10 DBB4-7
Note
If the sequence in the NC is not to be executed as described above, then the interface signal
DB10 DBX56.1 (emergency stop) must not be set until an emergency stop state defined by
the machine manufacturer in the PLC user program is reached.
As long as the interface signal is not set and no other alarm is pending, all interface signals
are operative in the NC. Any emergency stop state defined by the manufacturer (including
axis-, spindle- and channel-specific emergency stop states) can therefore be assumed.

The emergency stop control element may only be reset as a result of manual manipulation of
the emergency stop control element according to EN 418.
Resetting of the emergency stop control element alone must not trigger a restart command.
A machine restart must be impossible until all of the actuated emergency stop control elements
have been deliberately reset by hand.
Emergency stop acknowledgment

The EMERGENCY STOP state is only reset if the interface signal:DB10 DBX56.2
(acknowledge EMERGENCY STOP) is set followed by the interface signal:DB11, ... DBX0.7
(mode group reset).
Basic functions
Emergency stop
Hence it can be noted that the interface signal DB10 DBX56.2 (acknowledge emergency stop)
and the interface signal DB21, ... DBX7.7 (Reset) together are set at least for so long until the
interface signal DB10 DBX106.1(emergency stop active) is reset.
Note
The emergency stop state cannot be reset with the interface signal DB21, ... DBX7.7 (Reset)
alone.
'%'%;(PHUJHQF\6WRS

'%'%;DFNQRZOHGJH(PHUJHQF\
6WRS
'%'%;HPHUJHQF\VWRS
DFWLYH

'%'%;5(6(7

(1) DB10 DBX56.2 (acknowledge emergency stop) is inoperative

(2) DB21, ... DBX7.7 (Reset) is inoperative
(3) DB10 DBX56.2 and DB21, ... DBX7.7 reset DB10 DBX106.1 (emergency stop active)
Figure 9-1 Resetting the emergency stop state
Effects
Resetting the emergency stop state has the following effects:
● Within the controller for all machine axes:
– The servo enables are set.
– The follow-up mode is canceled.
– The position control is activated.
● The following interface signals are set:
DB31, ... DBX60.5 (position control active)
DB11 DBX6.3 (mode group ready)
● The following interface signal is reset:
DB10 DBX106.1 (emergency stop active)
● Alarm 3000 "Emergency stop" is deleted.
● Part program processing is interrupted in all channels of the NC.
Basic functions
Emergency stop
9.6 Data lists
PLC and NC I/O

The PLC user program must switch the PLC and NC I/O back to the state for operation of the
machine.
POWER OFF / ON (supply off / on)

The emergency stop state can also be reset by switching the controller off and back on
(POWER OFF / ON).
Requirement:
During power-up of the controller the interface signal DB10 DBX56.1 (emergency stop) must
not be set.
9.6 Data lists
9.6.1 Machine data

36610 AX_EMERGENCY_STOP_TIME Length of the braking ramp for error states
36620 SERVO_DISABLE_DELAY_TIME Cutout delay servo enable
Basic functions
Various NC/PLC interface signals and functions 10
Contents
The PLC/NC interface comprises a data interface on one side and a function interface on the
other. The data interface contains status and control signals, auxiliary and G commands, while
the function interface is used to transfer jobs from the PLC to the NC.
This Description describes the functionality of interface signals, which are of general relevance
but are not included in the descriptions of functions.
● Asynchronous events
● Status signals
● PLC variable (read and write)
10.2 Functions
10.2.1 Screen refresh behavior for overload

There are part programs, where the main run must wait until the preprocessing run provides
new blocks.
Preprocessing run and display refresh compete for NC processor time.
The following machine data can be used to set how the NC should behave if the preprocessing
run is too slow:
MD10131 $MN_SUPPRESS_SCREEN_REFRESH
Value Meaning
0 If the preprocessing run of a channel is too slow, the display is not refreshed in all channels.
1 If the preprocessing run of a channel is too slow, the display is only refreshed in the time critical channels in order to
obtain processor time for the preprocessing run.
2 Display refresh is not suppressed.
Basic functions
Various NC/PLC interface signals and functions
10.2 Functions
10.2.2 Activate DEFAULT memory
GUD start values

The DEF... / REDEF... NC commands can be used to assign default settings to global user data
(GUD). To make these default values available at the parameterized initialization time, e.g. with
the attribute INIPO, after power on, they must be saved permanently in the system. The
required memory space must be enabled using the following machine data:
MD18150 $MM_GUD_VALUES_MEM (non-volatile memory space for GUD values)
Further information
● Memory configuration (Page 799)
● "NC Programming" Programming Manual
10.2.3 Read/write PLC variable
High-speed data channel

For high-speed exchange of information between the PLC and NC, a memory area is reserved
in the communications buffer on these modules (dual-port RAM). Variables of any type (I/O,
DB, DW, flags) may be exchanged within this memory area.
The PLC accesses this memory using 'Function Calls' (FC) while the NC uses system variables.
Organization of memory area

The user's programming engineer (NC and PLC) is responsible for organizing (structuring) this
memory area.
Every storage position in the memory can be addressed provided that the limit is selected
according to the appropriate data format (i.e. a DWORD for a 4-byte limit, a WORD for a 2-byte
limit, etc.).
The memory is accessed via the data type and the position offset within the memory area.
Access from NC
System variables are available in the NC for fast access to PLC variables from a part program
or synchronized action. The data is read/written directly by the NC. The data type results from
the identifier of the system variables. The position within the memory area is specified as index
in bytes.
System variable Data type Range of values

$A_DBB[<index>] Byte (8 bits) 0 <= x <= 255
$A_DBW[<index>] Word (16 bits) -32768 <= x <= 32767
$A_DBD[<index>] Double word (32 bits) -2147483648 <= x <= 2147483647
$A_DBR[<index>] Floating point (32 bits) ±(1.5·10−45 <= x <= 3.4·1038)
Basic functions
10.2 Functions
Access from PLC

The PLC uses function calls (FC) to access the memory. The data is read and written
immediately in the DPR with the FC and not just at the beginning of the PLC cycle. Data type
and position in the memory area are transferred as parameters to the FC.
1&$B'%'> 3/&&$//)&

2IIVHW[ 2IIVHW[

'DWHQW\S'%'%\WH

Figure 10-1 Communications buffer (DPR) for NC/PLC communication
Boundary conditions
● The structuring of the DPR memory area is the sole responsibility of the user. No checks are
made for matching configuration.
● A total of 4096 bytes are available in the input and output directions.
● Single-bit operations are not supported and must be linked back to byte operations by the
user.
● Since the contents of variables are manipulated directly in the communications buffer, the
user must remember that intermediate changes in values occur as a result of multiple
access operations where a variable is evaluated several times or when variables are linked
(i.e. it may be necessary to store values temporarily in local variables or R parameters or to
set up a semaphore).
● The user's programming engineer is responsible for coordinating access operations to the
communications buffer from different channels.
● Data consistency can be guaranteed only for access operations up to 16 bits (byte and
word). The user is solely responsible for ensuring consistent transmission of 32-bit variables
(double and real). A simple semaphore mechanism is available in the PLC for this purpose.
Basic functions
10.2 Functions
● The PLC stores data in 'Little Endian' format in the DPR.

● Values transferred with $A_DBR are subject to data conversion and hence to loss of
accuracy. The data format for floating-point numbers is DOUBLE (64 bits) in the NC, but
only FLOAT (32 bits) in the PLC. The format used for storage in the dual-port RAM is
FLOAT. Conversion takes place respectively before/after storage in the dual-port RAM.
If a read/write access is made from the NC to a variable in the dual-port RAM, the conversion
is performed twice. It is impossible to prevent differences between read and written values
because the data is stored in both formats.
Example
Bypassing the problem by means of comparison on "EPSILON" (minor deviation)
Program code
N10 DEF REAL DBR
N12 DEF REAL EPSILON = 0.00001
N20 $A_DBR[0]=145.145
N30 G4 F2
N40 STOPRE
N50 DBR=$A_DBR[0]
N60 IF ( ABS(DBR/145.145-1.0) < EPSILON ) GOTOF ENDE
N70 MSG ( "error" )
N80 M0
N90 END:
N99 M30
Activation
The maximum number of simultaneously writable output variables is adjustable via:
MD28150 $MC_MM_NUM_VDIVAR_ELEMENTS (number of elements for writing PLC
variables)
Example
A variable of type WORD is to be transferred from the PLC to the NC.
The position offset within the NC input (PLC output area) should be the fourth byte. The position
offset must be a whole-number multiple of the data width.
Writing from PLC:

. . .
CALL FC21 (
Enable :=M10.0, ; if TRUE, then FC21 active
Funct :=B#16#4,
S7Var :=P#M 104.0 WORD1,
IVAR1 :=04,
IVAR2 :=-1,
Error :=M10.1,
Basic functions
10.2 Functions

ErrCode :=MW12);
. . .
)
Reading in part program

. . .
PLCDATA = $A_DBW[4]; ; Read a word
. . .
Behavior during POWER ON, block search

The DPR communications buffer is initialized during "POWER ON".
During a "block search", the PLC variable outputs are collected and transferred to the DPR
communications buffer with the approach block (analogous to writing of analog and digital
outputs).
Other status transitions have no effect in this respect.
Further information
A detailed description of the data exchange by the PLC with FC 21 can be found in:
Function Manual PLC and Basic Program
10.2.4 Access protection via password and keyswitch
Access authorization
Access to functions, programs and data is useroriented and controlled via 8 hierarchical
protection levels. These are subdivided into:
● Password levels for Siemens, machine manufacturer and end user
● Keyswitch positions for end user
Basic functions
10.2 Functions
Multi-level security concept

A multi-level security concept to regulate access rights is available in the form of password
levels and keyswitch settings.
Protection level Type User Access to (examples)

0 Password Siemens All functions, programs and
data
1 Password Machine manufacturer: De‐ defined functions, programs
velopment and data;
for example: entering options
2 Password Machine manufacturer: Start‐ defined functions, programs
up engineer and data;
for example: Bulk of machine
data
3 Password End user: Service Assigned functions, pro‐
grams and data
4 Keyswitch position 3 End user: Programmer, ma‐ less than the protection level
chine setter 0 to 3; established by the ma‐
chine manufacturer or end
user
5 Keyswitch position 2 End user: Skilled operator less than the protection level
without programming knowl‐ 0 to 3; established by the end
edge user
6 Keyswitch position 1 End user: Trained operator Example:
without programming knowl‐ Program selection only, tool
edge wear entry, and work offset
entry
7 Keyswitch position 0 End user: Semi-skilled oper‐ Example:
ator no inputs and program selec‐
tion possible,
only machine control panel
operable
Access features
● Protection level 0 provides the greatest number of access rights, protection level 7 the least.
● If certain access rights are granted to a protection level, these protection rights automatically
apply to any higher protection levels.
● Conversely, protection rights for a certain protection level can only be altered from a higher
protection level.
● Access rights for protection levels 0 to 3 are permanently assigned by Siemens and cannot
be altered (default).
● Access rights can be set by querying the current keyswitch positions and comparing the
passwords entered. When a password is entered it overwrites the access rights of the
keyswitch position.
Basic functions
10.2 Functions
● Options can be protected on each protection level. However, option data can only be
entered in protection levels 0 and 1.
● Access rights for protection levels 4 to 7 are only suggestions and can be altered by the
machine tool manufacturer or end user.
10.2.4.1 Password
Set password
The password for a protection level (0 – 3) is entered via the HMI user interface.
Operating area "Commissioning" > "Password" > "Set password"
Delete password
Access rights assigned by means of setting a password remain effective until they are explicitly
revoked by deleting the password:
Operating area "Commissioning" > "Password" > "Delete password"
Change password
The password for a protection level (0 – 3) is changed via the HMI user interface.
Operating area "Commissioning" > "Password" > "Change password"
Note
Warm restart
Access rights and password status (set/deleted) are not affected by a warm restart!
New password
A password may contain up to eight characters. We recommend that you confine yourself to the
characters available on the operator panel front when selecting the password.
Where a password consists of less than eight characters, the additional characters are
interpreted as blanks.
Basic functions
10.2 Functions
When assigning a new password, the rules for assigning secure passwords must be taken into
account.
Note
Assigning secure passwords
Observe the following rules when assigning new passwords:
● When assigning new passwords, make sure that you do not assign passwords that can be
easily guessed, e.g. simple words, key combinations that can be easily guessed, etc.
● Passwords must always contain a combination of upper-case and lower-case letters as well
as numbers and special characters. Passwords must comprise at least eight characters.
PINS must comprise an arbitrary sequence of digits.
● Wherever possible and where it is supported by the IT systems, a password must always
have a character sequence as complex as possible.
Further rules for the assignment of secure passwords can be found at Federal Office for
Information Security (Bundesamt für Sicherheit in der Informationstechnik, abbreviated as
BSI). (https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Grundschutz/International/
GSK_15_EL_EN_Draft.pdf?__blob=publicationFile&v=2)
You can use a program for password management for assistance when dealing with
passwords. With its help, you can save passwords and PINs in encrypted form, manage them
and generate secure passwords.
Defaults
As standard, the following passwords are effective for protection levels 1 - 3:
● Protection level 1: SUNRISE
● Protection level 2: EVENING
● Protection level 3: CUSTOMER
NOTICE
A cold restart reset the passwords to the default settings
After a cold restart (the NC powers up and standard machine data is loaded), the passwords
of protection levels 1 - 3 are again reset to the default settings. For security reasons, after a
cold restart we urgently recommend that the default settings of the passwords are changed.
Further information
● Commissioning Manual Commissioning CNC: NC, PLC, Drive; Requirements for
commissioning > Switch-on and power up and Access levels
Basic functions
10.2 Functions
10.2.4.2 Keyswitch positions (DB10, DBX56.4 to 7)
Keyswitch
The keyswitch has four positions, to which protection levels 4 to 7 are assigned. The keyswitch
comprises a number of keys in a variety of colors which can be set to different switch positions.
6ZLWFKSRVLWLRQ 5HWUDFWLRQSRV '%'%% 3URWHFWLRQOHYHO
3RVLWLRQ %LW
RU
3RVLWLRQ %ODFNNH\ %LW
RURU
3RVLWLRQ *UHHQNH\ %LW
RURU
3RVLWLRQ RU %LW
5HGNH\
Figure 10-2 Switch positions 0 to 3
Switch positions
Switch position 0 has the most restricted access rights. Switch position 3 has the least restricted
access rights.
DB10, DBX56.4 / .5 / .6 / .7 (switch positions 0 / 1 / 2 / 3)
Machine-specific enables for access to programs, data and functions can be assigned to the
switch positions. For detailed information, please refer to:
Further information
● Commissioning Manual Commissioning CNC: NC, PLC, Drive; Requirements for
commissioning > Switch-on and power up and Access levels
Default settings via the PLC user program

The keyswitch positions are transferred to the NC/PLC interface via the basic PLC program.
The corresponding interface signals can be modified via the PLC user program. In this context,
from the point of view of the NC, only one switch position should ever be active, i.e. the
corresponding interface signal set to 1. If, from the point of view of the NC, a number of switch
positions are active at the same time, switch position 3, i.e. the keyswitch position with the least
restricted access rights, will be activated internally by the NC.
Basic functions
10.2 Functions
10.2.4.3 Parameterizable protection levels
Parameterizable protection level

The parameter level can be freely parameterized for a variety of functions and data areas. The
protection level is set via operator-panel machine data, designated as follows:
$MM_USER_CLASS_<Function_DataArea>
Examples:
$MM_USER_CLASS_READ_TOA Read tool offsets

$MM_USER_CLASS_WRITE_TOA Write tool offsets
$MM_USER_CLASS_READ_PROGRAM Read part programs
$MM_USER_CLASS_WRITE_PROGRAM Write/edit part programs
Default values
On delivery or following standard commissioning, with very few exceptions, the default value for
the protection level will be set to 7, i.e. the lowest protection level.
10.2.5 Switching over motor/drive data sets
10.2.5.1 General Information
Motor and drive data sets

For optimum adaptation to the particular machining situation or because of different machine
configurations, it may be necessary that several different data sets are available in a drive for
motors, drive parameters and encoders. The creation of the basic data sets of the drive objects
is performed during startup with the aid of the "Drive wizard".
Note
Further information
Commissioning Manual: CNC: NC, PLC, Drive, Commissioning NC-controlled drives
The following duplication and management of the data sets is performed via the user interface:
SINUMERIK Operate: Operating area "Start-up" > "Drive system" > "Drives" > "Data sets"
The activation of the motor data set (MDS) or drive data set (DDS) required for a machine axis
in a specific machining situation, must be made from the PLC user program via the interfaces
described below.
Basic functions
10.2 Functions
Axial NC/PLC interface

The interfaces in the axial NC/PLC interface for switching the motor and drive data sets is
divided into three areas:
● Formatting interface (Page 601)
● Request interface (Page 602)
● Display interface (Page 602)
10.2.5.2 Formatting interfaces
Formatting
The formatting interface is used to set which bits of the request and display interface are used
to address the motor data sets (MDS) and which are used to address the drive data sets (DDS):
DB31, ... DBX130.0 - 4, with bit x = <value>
<value> Meaning
0 Bit position for motor data set (MDS) – or invalid bit position
1 Bit position for drive data set (DDS)
Motor and drive data sets in the drive

Formatting depends on the number of motor data sets (MDS) and drive data sets (DDS) in the
drive. The number can be determined using the following drive parameters:
● p0130 (number of motor data sets)
● p0180 (number drive data sets)
Validity of the interfaces

After powering up, as soon as the control has received all the required information from the
drive and this has been evaluated by the NC, the request (Page 602) and display interfaces
(Page 602) are shown as valid:
DB31, ... DBX130.7 == 1 (request and display interfaces valid)
If no or incompatible information is transferred from the drive, the request and display interfaces
are shown as invalid.
Note
With invalid request and display interfaces, it however remains the sole responsibility of the
user / machine manufacturer to perform a data set switchover via the invalid request and
display interfaces.
Basic functions
10.2 Functions
See also
Example (Page 602)
Overview of the interfaces (Page 603)
10.2.5.3 Request interface

The switchover to a new motor (MDS) and/or drive data sets (DDS) is requested via the
interface:
DB31, ... DBX21.0 - .4 = <MDS/DDS index>
Value range
Addressing a motor or drive data set n, with n = 1, 2, 3, ..., is realized based on its index i, with
i = n - 1 = 0, 1, 2, ...
● Motor data sets: MDS[ 0, 1, 2, ... 15 ]
● Drive data sets: DDS[ 0, 1, 2, ... 31 ]
Formatting interfaces
Formatting the request interface, i.e. which bits are used to address the motor data sets (MDS)
– and which are used to address the drive data sets (DDS) is set via the formatting interface
(Page 601).
Motor and drive data sets in the drive

The number of motor data sets (MDS) and drive data sets (DDS) in the drive can be determined
using the following drive parameters:
● p0130 (number of motor data sets)
● p0180 (number drive data sets)
Motor data set (MDS) for main spindle drives

For main spindle drives, the following association applies:
● MDS[ 0 ] → star operation
● MDS[ 1 ] → delta operation
10.2.5.4 Display interface

The active motor data set (MDS) and drive data set (DDS) are displayed via the interface:
DB31, ... DBX93.0 - .4 == <MDS / DDS index>
Value range and formatting are identical to the request interface (Page 602).
10.2.5.5 Example
Two motor data sets (MDS) and two drive data sets (DDS) are available in the drive for each
motor data set. This corresponds to "No.": 9 of the possible data set combinations displayed in
the Figure 10-3 Principle of the motor/drive data set switchover (Page 604).
Basic functions
10.2 Functions
Format
Bit positions for drive data set switchover (DDS):
● DB31, ... DBX130.0 == 1
Bit positions for motor data set switchover (MDS):
● DB31, ... DBX130.1 == 0
Invalid bit positions:
● DB31, ... DBX130.2 == 0
● DB31, ... DBX130.3 == 0
● DB31, ... DBX130.4 == 0
Interfaces of the drive data sets (DDS)

Relevant bit positions of the request and display interfaces:
● DB31, ... DBX21.0 / DBX93.0
– DB31, ... DBX21.0 / DBX93.0 == 0 ⇒ 1st drive data set DDS[0]
– DB31, ... DBX21.0 / DBX93.0 == 1 ⇒ 2nd drive data set DDS[1])
Interfaces of the motor data sets (MDS)

Relevant bit positions of the request and display interfaces:
● DB31, ... DBX21.1 / DBX93.1
– DB31, ... DBX21.1 / DBX93.1 == 0 ⇒ 1st motor data set MDS[0]
– DB31, ... DBX21.1 / DBX93.1 == 1 ⇒ 2nd motor data set MDS[1])
Invalid bit positions (MDS/DDS)

Invalid bit positions of the request and display interfaces:
● DB31, ... DBX21.1 / DBX93.2 == 0
● DB31, ... DBX21.1 / DBX93.3 == 0
● DB31, ... DBX21.1 / DBX93.4 == 0
See also
10.2.5.6 Overview of the interfaces
Table 10-1 Configurable MDS / DDS combinations
Number of MDS (motors) Number of DDS (drives) per MDS

1 1 ... 32
2 1, 2, 4, 8, 16
3 1, 2, 4, 8
Basic functions
10.2 Functions
Number of MDS (motors) Number of DDS (drives) per MDS

4 1, 2, 4, 8
5 1, 2, 4
6 1, 2, 4
7 1, 2, 4
8 1, 2, 4
9 1, 2
10 1, 2
11 1, 2
12 1, 2
13 1, 2
14 1, 2
15 1, 2
16 1, 2
''6SHU0'6 '% '%

'%;[[ '%;[
0'6
1R

8QVXSSRUWHGFRPELQDWLRQ

5HOHYDQWELWSRVLWLRQZLWKUHJDUGWR

0RWRUGDWDVHW0'6
'ULYHGDWDVHW''6

,QYDOLGELWSRVLWLRQ

MDS Number of motor data sets

DDS per MDS Number of drive data sets per motor data set
DB31, ... DBX21.x Request interface
DB31, ... DBX93.x Display interface
DB31, ... DBX130.x Formatting interface
Figure 10-3 Principle of the motor/drive data set switchover
Basic functions
10.3 Examples
Variable number of drive data sets for the "last" motor data set
The "last" motor data set is the motor data set with the highest number or index.
Generally, the same number of drive data sets is created for each motor data set (number of
"DDS per MDS") in the drive. Only the "last" motor data set can differ from this; any number (a)
of drive data sets can be parameterized:
1 ≤ a ≤ (number of "DDS per MDS")
Example
4 motor data sets (MDS) and 8 drive data sets (DDS) per motor data set (DDS per MDS) are
to be parameterized. This corresponds to "No.": 22 of the possible data set combination
displayed in the Figure 10-3 Principle of the motor/drive data set switchover (Page 604):
● Motor data sets: MDS[ 0 ], MDS[ 1 ], ... MDS[ 3 ] ("last" motor data set)
● Drive data sets per motor data set: DDS[ 0 ] ... DDS[ 7 ]
The number of drive data sets for the individual motor data sets is therefore:
Motor data set (MDS) Number of drive data sets (DDS) per motor data set (MDS)
MDS[ 0 ] ... MDS[ 2 ] 8
MDS[ 3 ] 1-8
Switchover instant: Drive parameter set

In principle it is possible to switch over drive parameter sets at any point in time. While an axis
is traversing, especially when switching over speed controller parameters and the motor speed
scaling, torque jumps/steps can occur. We therefore recommend that a drive parameter set is
only switched over for stationary states, especially when the axis is at a standstill.
See also
10.3 Examples
10.3.1 Parameter set changeover
Parameter set changeover

A parameter set changeover is performed to change the position control gain (KVfactor) from KV
= 4.0 to KV = 0.5 for machine axis X1.
Basic functions
10.3 Examples
Preconditions
The parameter set changeover must be enabled by the machine data:
MD35590 $MA_PARAMSET_CHANGE_ENABLE [AX1] = 1 or 2 (parameter set change
possible)
The 1st parameter set for machine axis X1 is set, in accordance with machine data with index
"0" NC/PLC interface:
DB31, … DBX9.0 - DBX9.2 = 0 (controller parameter set)
Parameter-set-dependent machine data

Parameter-set-dependent machine data are set as follows:
Machine data Comment

MD32200 $MA_POSCTRL_GAIN [0, AX1] = 4.0 KV setting for parameter set 1
MD31050 $MA_DRIVE_AX_RATIO_DENOM [0, AX1] = 3 Denominator load gearbox for parameter set 1
MD31060 $MA_DRIVE_AX_RATIO_NUMERA [0, AX1] = 5 Counter load gearbox for parameter set 1
MD35130 $MA_AX_VELO_LIMIT [0...5, AX1] Setting for each parameter set*)
MD32800 $MA_EQUIV_CURRCTRL_TIME [0..5, AX1] Setting for each parameter set*)
MD32810 $MA_EQUIV_SPEEDCTRL_TIME [0..5, AX1] Setting for each parameter set*)
MD32910 $MA_DYN_MATCH_TIME [0...5, AX1] Setting for each parameter set*)
*) The appropriate line must be specified separately for each parameter set according to the applicable syntax rules.
Basic functions
10.4 Data lists
Switchover
In order to switch over the position-control gain, the PLC user program selects the 4th
parameter set for machine axis X1.
● Request by PLC user program:
DB31, … DBX9.0 – DBX9.2 = 3 (parameter set servo)
– A request to change over to the 4th parameter set is sent for machine axis AX1.
– The parameter set is changed over once a delay has elapsed.
– Parameter set 4 is now active, in accordance with machine data with index "3"
● Feedback by NC:
DB31, … DBX69.0 – DBX69.2 = 3 (parameter set servo)
– The NC confirms/acknowledges the parameter-set changeover.
10.4 Data lists
10.4.1 Machine data
10.4.1.1 Display machine data

SINUMERIK Operate
9000 LCD_CONTRAST Contrast
9001 DISPLAY_TYPE Monitor type
9004 DISPLAY_RESOLUTION Display resolution
9006 DISPLAY_SWITCH_OFF_INTERVAL Time for screen darkening

10350 FASTIO_DIG_NUM_INPUTS Number of active digital NC input bytes
10360 FASTIO_DIG_NUM_OUTPUTS Number of active digital NC output bytes
10361 FASTIO_DIG_SHORT_CIRCUIT Short-circuit digital inputs and outputs
11120 LUD_EXTENDED_SCOPE Activate global program variables (PUD)
11270 DEFAULT_VALUES_MEM_MSK Active.
Function: Save DEFAULT values of GUD.
18150 MM_GUD_VALUES_MEM Reserve memory space for GUD
Basic functions
10.4 Data lists

21015 INVOLUTE_RADIUS_DELTA NC start disable without reference point
21016 INVOLUTE_AUTO_ANGLE_LIMIT Automatic angle limitation for involute interpolation
27800 TECHNOLOGY_MODE Technology in channel
28150 MM_NUM_VDIVAR_ELEMENTS Number of write elements for PLC variables
28530 MM_PATH_VELO_SEGMENTS Number of storage elements for limiting path velocity in
block

30350 SIMU_AX_VDI_OUTPUT Output of axis signals for simulation axes
33050 LUBRICATION_DIST Lubrication pulse distance
35590 PARAMSET_CHANGE_ENABLE Parameter set definition possible from PLC
36060 STANDSTILL_VELO_TOL Maximum velocity/speed when axis/spindle stationary
36610 AX_EMERGENCY_STOP_TIME Length of the braking ramp for error states
36620 SERVO_DISABLE_DELAY_TIME Cutout delay servo enable
Basic functions
10.4 Data lists
Names Description
$P_FUMB Unassigned part program memory (Free User Memory Buffer)
$A_DBB[n] Data on PLC (data type BYTE)
$A_DBW[n] Data on PLC (WORD type data)
$A_DBD[n] Data on PLC (DWORD type data)
$A_DBR[n] Data on PLC (REAL type data)
Basic functions
10.4 Data lists
Basic functions
Auxiliary function outputs to PLC 11
11.1.1 Function
Auxiliary functions permit activation of the system functions of the NC and PLC user functions.
Auxiliary functions can be programmed in:
● Part programs
● Synchronized actions
● User cycles
For detailed information on the use of auxiliary function outputs in synchronized actions, see:
Further information
Predefined auxiliary functions

Predefined auxiliary functions activate system functions. The auxiliary function is also output to
the NC/PLC interface.
The following auxiliary functions are predefined:
Type Function Example Meaning

M Additional function M30 End of program
S Spindle function S100 Spindle speed 100 (e.g. rpm)
T Tool number T3 Tool number 3
D, DL Tool offset D1 Tool cutting edge number 1
F Feedrate F1000 Feedrate 1000 (e.g. mm/min)
Userdefined auxiliary functions

User-defined auxiliary functions are either extended predefined auxiliary functions or user-
specific auxiliary functions.
Extension of predefined auxiliary functions
Extension of predefined auxiliary functions refers to the "address extensions" parameter. The
address extension defines the number of the spindle to which the auxiliary function applies. The
spindle function M3 (spindle right) is predefined for the master spindle of a channel. If a
Basic functions
Auxiliary function outputs to PLC
2nd spindle is assigned to a channel, a corresponding user-defined auxiliary function must be

defined that extends the predefined auxiliary function.

M Additional function M2=3 2nd spindle: Spindle right
S Spindle function S2=100 2nd spindle: Spindle speed = 100 (e.g. rpm)
T Tool number T2=3
User-specific auxiliary functions

User-specific auxiliary functions do not activate system functions. User-specific auxiliary
functions are output to the NC/PLC interface only. The functionality of the auxiliary functions
must be implemented by the machine manufacturer / user in the PLC user program.

H 1)
Auxiliary function H2=5 User-specific function
1)
Recommendation
11.1.2 Definition of an auxiliary function

An auxiliary function is defined by the following parameters:
● Type, address extension and value
The three parameters are output to the NC/PLC interface.
● Output behavior
The auxiliary function-specific output behavior defines for how long an auxiliary function is
output to the NC/PLC interface and when it is output relative to the traversing motion
programmed in the same part program block.
● Group assignment
An auxiliary function can be assigned to a particular auxiliary function group. The output
behavior can be defined separately for each auxiliary function group. This becomes active
if no auxiliary function-specific output behavior has been defined. Group membership also
affects output of an auxiliary function after block search.
Further information
Function Manual PLC and Basic Program, Basic program
11.1.3 Overview of the auxiliary functions
M functions
M (special function)
Address extension Value
Range of values Meaning Value range 10) Type Meaning Number 8)
0 (implicit) --- 0 ... 99 INT Function 5
Basic functions
M (special function)
Range of values Meaning Value range 11) Type Meaning Number 8)
1 ... 20 Spindle number 1 ... 99 INT Function 5
Range of values Meaning Value range 12)
Type Meaning Number 8)
0 ... 99 Any 100 ... 2147483647 INT Function 5
8)
See "Meaning of footnotes" at the end of the overview.
10)
For the value range 0 ... 99, the address extension is 0. Mandatory without address extension: M0, M1, M2, M17, M30
11)
M3, M4, M5, M19, M70: The address extension is the spindle number, e.g. M2=5 ⇒ spindle stop (M5) for spindle 2.
Without address extension, the M function acts on the master spindle.
12)
User-specific M functions.
Use
Controlling machine functions in synchronism with the part program.
Further information
● The following M functions have a predefined meaning: M0, M1, M2, M17, M30, M3, M4, M5,
M6, M19, M70, M40, M41, M42, M43, M44, M45.
● A dynamic NC/PLC interface signal for displaying the validity is assigned to the M functions
(M0 - M99). Furthermore, 64 additional signals can be assigned for independent M functions
(see Function Manual PLC and Basic Program, Section Basic program).
● For subprograms, machine data can be used to set whether an output of the M function
should be realized for the end of the part program M17, M2 or M30 to the PLC:
MD20800 $MC_SPF_END_TO_VDI (subprogram end to PLC)
● For the predefined M functions M40 – M45, only limited redefinition of the output
specification is possible.
Basic functions
● The predefined auxiliary functions M0, M1, M17, M30, M6, M4, M5 cannot be redefined.
● M function-specific machine data:
– MD10800 $MN_EXTERN_CHAN_SYNC_M_NO_MIN
– MD10802 $MN_EXTERN_CHAN_SYNC_M_NO_MAX
– MD10804 $MN_EXTERN_M_NO_SET_INT
– MD10806 $MN_EXTERN_M_NO_DISABLE_INT
– MD10814 $MN_EXTERN_M_NO_MAC_CYCLE
– MD10815 $MN_EXTERN_M_NO_MAC_CYCLE_NAME
– MD20094 $MC_SPIND_RIGID_TAPPING_M_NR
– MD20095 $MC_EXTERN_RIGID_TAPPING_M_NR
– MD20096 $MC_T_M_ADDRESS_EXT_IS_SPINO
– MD22200 $MC_AUXFU_M_SYNC_TYPE
– MD22530 $MC_TOCARR_CHANGE_M_CODE
– MD22532 $MC_GEOAX_CHANGE_M_CODE
– MD22534 $MC_TRAFO_CHANGE_M_CODE
– MD22560 $MC_TOOL_CHANGE_M_CODE
S functions
S (spindle function)
Address extension10) Value
Range of values Meaning Range of values Type Meaning Number 8)
0 ... 20 Spindle number 5)
0 ... ± 3.4028 exp38 3)
REAL Spindle speed 3
3) 5) 8)
See "Meaning of footnotes" at the end of the overview
10)
The master spindle of the channel is addressed if no address extension is specified.
Use
Spindle speed.
Further information
● S functions are assigned to auxiliary function group 3 by default.
● Without an address extension, the S functions refer to the master spindle of the channel.
● S function-specific machine data:
MD22210 $MC_AUXFU_S_SYNC_TYPE (output time of the S functions)
Basic functions
H functions
The functionality of an H function must be implemented in the PLC user program.
H (auxiliary function) 10)

0 ... 99 Any - 2147483648 ... INT Any 3
+ 2147483647
0 ... ± 3.4028 exp38 2) 3) 4) REAL
2) 3) 4) 8)
Use
User-specific auxiliary functions.
Further information
H function-specific machine data:
● MD22110 $MC_AUXFU_H_TYPE_INT (type of H-auxiliary function is an integer)
● MD22230 $MC_AUXFU_H_SYNC_TYPE (output time of the H functions)
T functions
Tool names are not output at the NC/PLC interface.
T (tool number) 1) 5) 6)
1 ... 12 Spindle number 0 ... 32000 INT Selection of the tool 1
(with active tool man‐ (also symbolic names for ac‐
agement) tive tool management)
1) 5) 6) 8)
Use
Tool selection.
Further information
● Identification of the tools, optionally with tool number or location number (see Function
Manual Tools, Section Tool offset).
Function Manual Tool Management
● When T0 is selected, the current tool is removed from the toolholder but not replaced by a
new tool (default setting).
● T function-specific machine data:
MD22220 $MC_AUXFU_T_SYNC_TYPE (output time of the T functions)
Basic functions
D functions
The tool offset is deselected using D0. Default setting is D1.
D (tool offset)
--- --- 0 ... 9 INT Selection of the tool 1
offset
8)
Use
Selection of the tool offset.
Further information
● Initial setting: D1
● After a tool change, the default tool cutting edge can be parameterized via:
MD20270 $MC_CUTTING_EDGE_DEFAULT (basic position of the tool cutting edge
without programming)
● Deselection of the tool offset: D0
● D function-specific machine data:
MD22250 $MC_AUXFU_D_SYNC_TYPE (output time of the D functions)
DL functions
The additive tool offset selected with DL refers to the active D number.
DL (additive tool offset)

--- --- 0 ... 6 INT Selection of the sum‐ 1
med tool offset
8)
Use
Selection of the additive tool offset with reference to an active tool offset.
Further information
● Initial setting: DL = 0
● DL values cannot be output to the PLC via synchronized actions.
● Default setting of the additive tool offset without an active DL function:
MD20272 $MC_SUMCORR_DEFAULT (basic setting of the additive offset without a
program)
Basic functions
● Deselection of the additive tool offset: DL = 0

● DL function-specific machine data:
MD22252 $MC_AUXFU_DL_SYNC_TYPE (output time DL functions)
F functions
F (feedrate)
--- --- 0.001 ... 999 999.999 REAL Path feedrate 6
8)
Use
Path velocity.
Further information
F function-specific machine data:
● MD22240 $MC_AUXFU_F_SYNC_TYPE (output time of F functions)
FA functions
FA (axes-specific feedrate)
1 - 31 Axis number 0.001 ... 999 999.999 REAL Axial feedrate 6
8)
Use
Axis-specific velocity.
Further information
F function-specific machine data:
● MD22240 $MC_AUXFU_F_SYNC_TYPE (output time of F functions)
Meaning of footnotes
1)
If tool management is active, neither a T change signal nor a T word is output at the
channel-specific NC/PLC interface.
2)
The type for the values can be selected by the user via MD22110 $MC_AUX‐
FU_H_TYPE_INT.
Basic functions
11.2 Predefined auxiliary functions
3)
Because of the limited display options on the operator panel screens, the REAL type
values displayed are restricted to:
–999 999 999.9999 to 999 999 999.9999
The NC calculates internally but with complete accuracy.
4)
The REAL values are rounded and output to the PLC when setting the machine data:
MD22110 $MC_AUXFU_H_TYPE_INT = 1 (type of H-auxiliary functions is an integer)
The PLC user program must interpret the value transferred according to the machine data
setting.
5)
If the tool management is active, the meaning of the address extension can be parame‐
terized. Address extension = 0 means the value must be replaced by that of the master
spindle number, i.e. it is equivalent to not programming the address extension.
Auxiliary functions M19 "Position spindle" collected during a block search are not output to
the PLC.
6)
M6: Range of values of the address extension:
- without tool management: 0 ... 99
- with tool management: 0 ... maximum spindle number
0: To be replaced by the value of the master spindle number or master tool holder
7)
If tool management is active, the auxiliary function M6 "Tool change" can only be pro‐
grammed once in a part program block, irrespective the address extensions that are pro‐
grammed.
8)
Maximum number of auxiliary functions per part program block.
Function
Every pre-defined auxiliary function is assigned to a system function and cannot be changed.
If a pre-defined auxiliary function is programmed in a part program/cycle, then this is output to
the PLC via the NC/PLC interface and the corresponding system function is executed in the NC.
Definition of a predefined auxiliary function

The parameters of the predefined auxiliary function are stored in machine data and can be
changed in some cases. All machine data, which are assigned to an auxiliary function, have the
same index <n>.
● MD22040 $MC_AUXFU_PREDEF_GROUP[<n>] (group assignment of predefined
auxiliary functions)
● MD22050 $MC_AUXFU_PREDEF_TYPE[<n>] (type of predefined auxiliary functions)
● MD22060 $MC_AUXFU_PREDEF_EXTENSION[<n>] (address extension for predefined
● MD22070 $MC_AUXFU_PREDEF_VALUE[<n>] (value of predefined auxiliary functions)
● MD22080 $MC_AUXFU_PREDEF_SPEC[<n>] (output behavior of predefined auxiliary
functions)
Basic functions
11.2.1 Overview: Predefined auxiliary functions

Significance of the parameters listed in the following tables:
Parameter Meaning
Index <n> Machine data index of the parameters of an auxiliary function
Type MD22050 $MC_AUXFU_PREDEF_TYPE[<n>]
Address extension MD22060 $MC_AUXFU_PREDEF_EXTENSION[<n>]
Value MD22070 $MC_AUXFU_PREDEF_VALUE[<n>]
Group MD22040 $MC_AUXFU_PREDEF_GROUP[<n>]
Predefined auxiliary functions
General auxiliary functions, Part 1

System function Index <n> Type Address ex‐ Value Group
tension
Stop 0 M 0 0 1
Conditional stop 1 M 0 1 1
End of subprogram 2 M 0 2 1
3 M 0 17 1
4 M 0 30 1
Tool change 5 M (0) 6 1) (1)
Spindle-specific auxiliary functions, spindle 1

tension
Spindle right 6 M 1 3 (2)
Spindle left 7 M 1 4 (2)
Spindle stop 8 M 1 5 (2)
Position spindle 9 M 1 19 (2)
Axis mode 10 M 1 70 2)
(2)
Automatic gear stage 11 M 1 40 (4)
Gear stage 1 12 M 1 41 (4)
Gear stage 2 13 M 1 42 (4)
Gear stage 3 14 M 1 43 (4)
Gear stage 4 15 M 1 44 (4)
Gear stage 5 16 M 1 45 (4)
Spindle speed 17 S 1 -1 (3)
Basic functions
General auxiliary functions, Part 2

tension
Feedrate 18 F 0 -1 (1)
Cutting edge selection 19 D 0 -1 (1)
DL 20 L 0 -1 (1)
Tool selection 21 T (0) -1 (1)
Stop (associated) 22 M 0 -1 3)
1
Conditional stop (associated) 23 M 0 -1 4) 1
End of subprogram 24 M 0 -1 5) 1
Nibbling 25 M 0 20 6)
(10)
Nibbling 26 M 0 23 6) (10)
(11)
Nibbling 28 M 0 25 6) (11)
(12)
(11)
Nibbling 31 M 0 125 6) (11)
(12)

tension
(72)
Gear stage 1 39 M 2 41 (74)
Gear stage 2 40 M 2 42 (74)
Gear stage 3 41 M 2 43 (74)
Gear stage 4 42 M 2 44 (74)
Gear stage 5 43 M 2 45 (74)

tension
Basic functions

tension
(75)
Gear stage 1 51 M 3 41 (77)
Gear stage 2 52 M 3 42 (77)
Gear stage 3 53 M 3 43 (77)
Gear stage 4 54 M 3 44 (77)
Gear stage 5 55 M 3 45 (77)

tension
Axis mode 61 M 4 70 2) (78)
Gear stage 1 63 M 4 41 (80)
Gear stage 2 64 M 4 42 (80)
Gear stage 3 65 M 4 43 (80)
Gear stage 4 66 M 4 44 (80)
Gear stage 5 67 M 4 45 (80)

tension
(81)
Gear stage 1 75 M 5 41 (83)
Gear stage 2 76 M 5 42 (83)
Gear stage 3 77 M 5 43 (83)
Basic functions

tension
Gear stage 4 78 M 5 44 (83)
Gear stage 5 79 M 5 45 (83)

tension
Axis mode 85 M 6 70 2) (84)
Gear stage 1 87 M 6 41 (86)
Gear stage 2 88 M 6 42 (86)
Gear stage 3 89 M 6 43 (86)
Gear stage 4 90 M 6 44 (86)
Gear stage 5 91 M 6 45 (86)

tension
(87)
Gear stage 1 99 M 7 41 (89)
Gear stage 2 100 M 7 42 (89)
Gear stage 3 101 M 7 43 (89)
Gear stage 4 102 M 7 44 (89)
Gear stage 5 103 M 7 45 (89)
Basic functions

tension
Axis mode 109 M 8 70 2) (90)
Gear stage 1 111 M 8 41 (92)
Gear stage 2 112 M 8 42 (92)
Gear stage 3 113 M 8 43 (92)
Gear stage 4 114 M 8 44 (92)
Gear stage 5 115 M 8 45 (92)

tension
Axis mode 121 M 9 70 2) (93)
Gear stage 1 123 M 9 41 (95)
Gear stage 2 124 M 9 42 (95)
Gear stage 3 125 M 9 43 (95)
Gear stage 4 126 M 9 44 (95)
Gear stage 5 127 M 9 45 (95)

tension
Axis mode 133 M 10 70 2)
(96)
Basic functions

tension
Gear stage 1 135 M 10 41 (98)
Gear stage 2 136 M 10 42 (98)
Gear stage 3 137 M 10 43 (98)
Gear stage 4 138 M 10 44 (98)
Gear stage 5 139 M 10 45 (98)

tension
Axis mode 145 M 11 70 2)
(99)
Gear stage 1 147 M 11 41 (101)
Gear stage 2 148 M 11 42 (101)
Gear stage 3 149 M 11 43 (101)
Gear stage 4 150 M 11 44 (101)
Gear stage 5 151 M 11 45 (101)

tension
Axis mode 157 M 12 70 2)
(102)
Gear stage 1 159 M 12 41 (104)
Gear stage 2 160 M 12 42 (104)
Gear stage 3 161 M 12 43 (104)
Gear stage 4 162 M 12 44 (104)
Gear stage 5 163 M 12 45 (104)
Basic functions

tension
Axis mode 169 M 13 70 2)
(105)
Gear stage 1 171 M 13 41 (107)
Gear stage 2 172 M 13 42 (107)
Gear stage 3 173 M 13 43 (107)
Gear stage 4 174 M 13 44 (107)
Gear stage 5 175 M 13 45 (107)

tension
Axis mode 181 M 14 70 2) (108)
Gear stage 1 183 M 14 41 (110)
Gear stage 2 184 M 14 42 (110)
Gear stage 3 185 M 14 43 (110)
Gear stage 4 186 M 14 44 (110)
Gear stage 5 187 M 14 45 (110)

tension
Axis mode 193 M 15 70 2)
(111)
Basic functions

tension
Gear stage 1 195 M 15 41 (113)
Gear stage 2 196 M 15 42 (113)
Gear stage 3 197 M 15 43 (113)
Gear stage 4 198 M 15 44 (113)
Gear stage 5 199 M 15 45 (113)

tension
Axis mode 205 M 16 70 2)
(114)
Gear stage 1 207 M 16 41 (116)
Gear stage 2 208 M 16 42 (116)
Gear stage 3 209 M 16 43 (116)
Gear stage 4 210 M 16 44 (116)
Gear stage 5 211 M 16 45 (116)

tension
Axis mode 217 M 17 70 2)
(117)
Gear stage 1 219 M 17 41 (119)
Gear stage 2 220 M 17 42 (119)
Gear stage 3 221 M 17 43 (119)
Gear stage 4 222 M 17 44 (119)
Gear stage 5 223 M 17 45 (119)
Basic functions

tension
Axis mode 229 M 18 70 2)
(120)
Gear stage 1 231 M 18 41 (122)
Gear stage 2 232 M 18 42 (122)
Gear stage 3 233 M 18 43 (122)
Gear stage 4 234 M 18 44 (122)
Gear stage 5 235 M 18 45 (122)

tension
Axis mode 241 M 19 70 2) (123)
Gear stage 1 243 M 19 41 (125)
Gear stage 2 244 M 19 42 (125)
Gear stage 3 245 M 19 43 (125)
Gear stage 4 246 M 19 44 (125)
Gear stage 5 247 M 19 45 (125)

tension
Axis mode 253 M 20 70 2)
(126)
Basic functions

tension
Gear stage 1 255 M 20 41 (128)
Gear stage 2 256 M 20 42 (128)
Gear stage 3 257 M 20 43 (128)
Gear stage 4 258 M 20 44 (128)
Gear stage 5 259 M 20 45 (128)
Toolholder-specific auxiliary functions, T auxiliary functions

tension
Tool selection 261 T 1 -1 129
Toolholder-specific auxiliary functions, M6 auxiliary functions

tension
Tool change 281 M 1 6 1) 149
Tool change 282 M 2 6 1)
150
151
Tool change 284 M 4 6 1) 152
Basic functions
Toolholder-specific auxiliary functions, M6 auxiliary functions

tension
Tool change 285 M 5 6 1) 153
Tool change 286 M 6 6 1) 154
155
156
Tool change 289 M 9 6 1) 157
158
Tool change 291 M 11 6 1) 159
160
Tool change 293 M 13 6 1) 161
162
163
Tool change 296 M 16 6 1) 164
165
Tool change 298 M 18 6 1) 166
167
168
Legend:
( ) The value can be changed.
1)
The value is depends on the machine data:
MD22560 $MC_TOOL_CHANGE_M_MODE (M function for tool change)
2)
The value can be preset with a different value using the following machine data:
MD20095 $MC_EXTERN_RIGID_TAPPING_M_NR (M function for switching over to con‐
trolled axis mode (ext. mode))
MD20094 $MC_SPIND_RIGID_TAPPING_M_NR (M function for switching over to con‐
trolled axis mode)
Note
The value 70 is always output at the PLC.
3)
The value is set using machine data:
MD22254 $MC_AUXFU_ASSOC_M0_VALUE (additional M function for program stop)
4)
MD22256 $MC_AUXFU_ASSOC_M1_VALUE (additional M function for conditional stop)
5)
MD10714 $MN_M_NO_FCT_EOP (M function for spindle active after reset)
6)
MD26008 $MC_NIBBLE_PUNCH_CODE (definition of M functions)
Basic functions
11.2.2 Overview: Output behavior

Significance of the parameters listed in the following table:
Parameter Meaning
Index <n> Machine data index of the parameters of an auxiliary function
Output behavior MD22080 $MC_AUXFU_PREDEF_SPEC[<n>], Bits 0 ... 18
Bits 19 ... 31: Reserved
Output behavior of the predefined auxiliary functions
System function Index <n>

Output behavior, bit
18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Stop 0 0 0 0 (0) 0 0 0 0 (0) 0 0 1 0 0 0 0 0 (0) (1)
Conditional stop 1 0 0 0 (0) 0 0 0 0 (0) 0 0 1 0 0 0 0 0 (0) (1)
End of subroutine 2 0 0 0 (0) 0 0 0 0 (0) 0 0 1 0 0 0 0 0 (0) (1)
3 0 0 0 (0) 0 0 0 0 (0) 0 0 1 0 0 0 0 0 (0) (1)
4 0 0 0 (0) 0 0 0 0 (0) 0 0 1 0 0 0 0 0 (0) (1)
Tool change 5 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (0) (1) (0) (0) (0) (0) (1)
Spindle right 6 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (0) (1) (0) (0) (0) (0) (1)
Spindle left 7 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (0) (1) (0) (0) (0) (0) (1)
Spindle stop 8 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (0) (1) (0) (0) (0) (0) (1)
Spindle positioning 9 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (0) (1) (0) (0) (0) (0) (1)
Axis mode 10 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (0) (1) (0) (0) (0) (0) (1)
Automatic gear stage 11 0 0 0 (0) 0 0 0 (0) (0) (0) (0) 0 0 1 (0) (0) (0) (0) (1)
Gear stage 1 12 0 0 0 (0) 0 0 0 (0) (0) (0) (0) 0 0 1 (0) (0) (0) (0) (1)
Gear stage 2 13 0 0 0 (0) 0 0 0 (0) (0) (0) (0) 0 0 1 (0) (0) (0) (0) (1)
Gear stage 3 14 0 0 0 (0) 0 0 0 (0) (0) (0) (0) 0 0 1 (0) (0) (0) (0) (1)
Gear stage 4 15 0 0 0 (0) 0 0 0 (0) (0) (0) (0) 0 0 1 (0) (0) (0) (0) (1)
Gear stage 5 16 0 0 0 (0) 0 0 0 (0) (0) (0) (0) 0 0 1 (0) (0) (0) (0) (1)
Spindle speed 17 0 0 0 (0) 0 0 0 (0) (0) (0) 0 (0) (1) (0) (0) (0) 0 (0) (1)
Feed 18 0 0 0 (0) 0 0 0 (0) (0) (0) 0 (0) (1) (0) 0 (1) 0 (0) (1)
Cutting edge selection 19 0 0 0 (0) 0 0 0 (0) (0) (0) 0 (0) (0) (1) 0 (0) 0 (0) (1)
DL 20 0 0 0 (0) 0 0 0 (0) (0) (0) 0 (0) (0) (1) 0 (0) 0 (0) (1)
Tool selection 21 0 0 0 (0) 0 0 0 (0) (0) (0) 0 (0) (0) (1) 0 (0) 0 (0) (1)
Stop (associated) 22 0 0 0 (0) 0 0 0 0 (0) 0 0 1 0 0 0 0 0 (0) (1)
Conditional stop (asso‐ 23 0 0 0 (0) 0 0 0 0 (0) 0 0 1 0 0 0 0 0 (0) (1)
ciated)
End of subroutine 24 0 0 0 (0) 0 0 0 0 (0) 0 0 1 0 0 0 0 0 (0) (1)
Nibbling 25 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (1) (0) 0 (0) (0) (0) (1)
Nibbling 26 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (1) (0) 0 (0) (0) (0) (1)
Nibbling 27 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (1) (0) 0 (0) (0) (0) (1)
Nibbling 28 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (1) (0) 0 (0) (0) (0) (1)
Basic functions
System function Index <n>

Output behavior, bit
Nibbling 29 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (1) (0) 0 (0) (0) (0) (1)
Nibbling 30 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (1) (0) 0 (0) (0) (0) (1)
Nibbling 31 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (1) (0) 0 (0) (0) (0) (1)
Nibbling 32 0 0 0 (0) 0 0 0 (0) (0) (0) (0) (0) (1) (0) 0 (0) (0) (0) (1)
( ) The value can be changed.
Significance of the bits
Bit Meaning
0 Acknowledgement "normal" after an OB1 cycle
An auxiliary function with normal acknowledgment is output to the NC/PLC interface at the beginning of the OB1 cycle.
The auxiliary function-specific change signal indicates to the PLC user program that the auxiliary function is valid.
The auxiliary function is acknowledged as soon as organization block OB1 has run once. This corresponds to a
complete PLC user cycle.
The auxiliary function with normal acknowledgment is output in synchronism with the part program block in which it is
programmed. If execution of the parts program block, e.g. path and/or positioning axis movements, is completed before
acknowledgment of the auxiliary function, the block change is delayed until after acknowledgment by the PLC.
In continuous-path mode, a constant path velocity can be maintained in conjunction with an auxiliary function with
normal acknowledgment, if the auxiliary function is output by the PLC during the traversing motion and before reaching
the end of the block.
1 Acknowledgement "quick" with OB40
An auxiliary function with quick acknowledgment is output to the NC/PLC interface before the next OB1 cycle. The
auxiliary function-specific change signal indicates to the PLC user program that the auxiliary function is valid.
The auxiliary function is acknowledged immediately by the PLC basic program in the next OB40 cycle. Acknowledg‐
ment of the auxiliary function is not confirmation that the corresponding PLC user function has been executed. The
auxiliary function is still executed in the OB1 cycle. Next output of the auxiliary functions to the PLC is therefore not
possible until after this OB1 cycle has run completely. This is noticeable in continuous-path mode (drop in path velocity)
especially if auxiliary functions with quick acknowledgment are output in several consecutive part program blocks.
With auxiliary functions with quick acknowledgment, it cannot be guaranteed that the PLC user program will respond
in synchronism with the block.
Note
Parameterization of the output behavior of auxiliary functions as "quick auxiliary functions" is only possible in con‐
junction with user-defined auxiliary functions.
2 No predefined auxiliary function
A predefined auxiliary function is treated like a user-defined auxiliary function with this setting. The auxiliary function
then no longer triggers the corresponding system function but is only output to the PLC.
Example:
Reconfiguration of the "Position spindle" auxiliary function (index 9) to a user-defined auxiliary function with normal
acknowledgment and output prior to the traversing motion.
MD22080 $MC_AUXFU_PREDEF_SPEC [ 9 ] = 'H25' (100101B)
3 No output to the PLC
The auxiliary function is not output to the PLC.
Basic functions
Bit Meaning
4 Spindle response after acknowledgement by the PLC
The associated system function is only executed after acknowledgment by the PLC.
5 Output prior to motion
The auxiliary function is output to the PLC before the traversing motions programmed in the part program block (path
and/or block-related positioning axis movements).
6 Output during motion
The auxiliary function is output to the PLC during the traversing motions programmed in the part program block (path
and/or block-related positioning axis movements).
7 Output at block end
The auxiliary function is output to the PLC after the traversing motions programmed in the part program block have
been completed (path and/or block-related positioning axis movements).
8 Not output after block search, types 1, 2, 4
Block search, types 1, 2, 4: The auxiliary function collected during the block search is not output.
9 Collection during block search with program test (type 5, SERUPRO)
For a block search with program test, the auxiliary function is collected group-specific in the following system variables:
● $AC_AUXFU_M_VALUE[<n>]
● $AC_AUXFU_M_EXT[<n>]
● $AC_AUXFU_M_STATE[<n>]
10 No output during block search with program test (type 5, SERUPRO)
For block search with program test, the auxiliary function is not output to the PLC.
11 Cross-channel auxiliary function (SERUPRO)
For block search with program test (SERUPRO), the help function is collected on a cross-channel basis in the global
list of the auxiliary functions.
Note
For each auxiliary function group, only the last auxiliary function of the group is always collected.
12 Output performed via synchronized action (read only)
The bit is set if the auxiliary function was output to the PLC via a synchronized action.
13 Implicit auxiliary function (read-only)
The bit is set if the auxiliary function was implicitly output to the PLC.
14 Active M01 (read only)
The bit is set if the auxiliary function, for active M01, was output to the PLC.
15 No output during positioning test run
During the run-in test, the auxiliary function is not output to the PLC.
16 Nibbling off
17 Nibbling on
18 Nibbling
Basic functions
Note
In the case of auxiliary functions for which no output behavior has been defined, the following
default output behavior is active:
● Bit 0 = 1: Output duration one OB1 cycle
● Bit 7 = 1: Output at block end
11.2.3 Parameterization
11.2.3.1 Group assignment

The handling of the auxiliary functions for a block search is defined using the group assignment
of an auxiliary function. The 168 auxiliary function groups available are subdivided into
predefined and user-definable groups:
Predefined groups: 1 ... 4 10 ... 12 72 ... 168

User-defined groups: 5 ... 9 13 ... 71
Each predefined auxiliary function is assigned, as standard, to an auxiliary function group. For
most pre-defined auxiliary functions, this assignment can be changed using the following
machine data:
MD22040 $MC_AUXFU_PREDEF_GROUP[<n>] (group assignment of predefined auxiliary
functions)
If an auxiliary function is not assigned to any group, then a value of "0" should be entered into
the machine data.
For the pre-defined auxiliary functions with the following indices <n>, the group assignment
cannot be changed: 0, 1, 2, 3, 4, 22, 23, 24
Note
1. Auxiliary function group and block search
Auxiliary functions of the 1st auxiliary function group are, for a block search, only collected, but
not output.
11.2.3.2 Type, address extension and value

An auxiliary function is programmed via the type, address extension and value parameters (see
Section "Programming an auxiliary function (Page 647)").
Basic functions
Type
The identifier of an auxiliary function is defined via the "type," e.g.:
"M" For additional function

"S" For spindle function
"F" For feed
The setting is made via the following machine data:

MD22050 $MC_AUXFU_PREDEF_TYPE[<n>] (type of predefined auxiliary functions)
Note
The "type" cannot be changed for predefined auxiliary functions.
Address extension
The "address extension" of an auxiliary function is for addressing different components of the
same type. In the case of predefined auxiliary functions, the value of the "address extension"
is the spindle number to which the auxiliary function applies.
MD22060 $MC_AUXFU_PREDEF_EXTENSION[<n>] (address extension for predefined
Grouping together auxiliary functions
To assign an auxiliary function for all spindles of a channel to the same auxiliary function group,
the value "-1" is entered for the "address extension" parameter.
Example:
The auxiliary function M3 (machine data index = 6) is assigned to the second auxiliary function
group for all the channel's spindles.
MD22040 $MC_AUXFU_PREDEF_GROUP[ 6 ] =2
MD22050 $MC_AUXFU_PREDEF_TYPE[ 6 ] = "M"
MD22060 $MC_AUXFU_PREDEF_EXTENSION[ 6 ] = -1
MD22070 $MC_AUXFU_PREDEF_VALUE[ 6 ] =3
Value
The parameters "value" and "type" define the meaning of an auxiliary function, i.e. the system
function that is activated on the basis of this auxiliary function.
The "value" of an auxiliary function is defined in the machine data:
Basic functions
MD22070 $MC_AUXFU_PREDEF_VALUE[<n>] (value of predefined auxiliary functions)
Note
The "value" cannot be changed for a predefined auxiliary function. For some predefined
auxiliary functions, the "value" can be reconfigured via additional machine data (see Section
"Associated auxiliary functions (Page 642)").
11.2.3.3 Output behavior

Parameter "Output behavior" defines when the predefined auxiliary function is output to the NC/
PLC interface and when it is acknowledged by the PLC.
The setting is done via the following machine data:
MD22080 $MC_AUXFU_PREDEF_SPEC[<n>] (output behavior of predefined auxiliary
functions)
Output behavior relative to motion

Output prior to motion
● The traversing motions (path and/or block-related positioning axis movements) of the
previous part program block end with an exact stop.
● The auxiliary functions are output at the beginning of the current parts program block.
● The traversing motion of the actual part program block (path and/or positioning axis motion)
is only started after acknowledgment of the auxiliary functions by the PLC:
– Output duration one OB1 cycle (normal acknowledgment): after one OB1 cycle
– Output duration one OB40 cycle (quick acknowledgment): after one OB40 cycle
Output during motion
● The auxiliary functions are output at the beginning of the traversing motions (path and/or
positioning axis movements).
● The path velocity of the current parts program block is reduced so that the time to the end
of the block is greater than the time to acknowledgment of the auxiliary functions by the PLC.
– Output duration one OB1 cycle (normal acknowledgment): one OB1 cycle
– Output duration one OB40 cycle (quick acknowledgment): one OB40 cycle
Output after motion
● The traversing motions (path and/or block-related positioning axis movements) of the
current part program block end with an exact stop.
● The auxiliary functions are output after completion of the traversing motions.
● The block change is performed after acknowledgment of the auxiliary functions by the PLC:
– Output duration one OB1 cycle (normal acknowledgment): after one OB1 cycle
– Output duration one OB40 cycle (quick acknowledgment): after one OB40 cycle
Basic functions
Examples of different output behavior

The following figures illustrate the differing behavior regarding:
● Output and acknowledgment of the auxiliary function
● Spindle response (speed change)
● Traverse movement (velocity change)
The binary values specified in the diagrams under "Output behavior" refer to the parameterized
output behavior (MD22080).
06;
Y 2XWSXWEHKDYLRU
6SLQGOHUHVSRQVH
2XWSXW $FNQ
0 $[LVPRYHPHQW
%ORFNFKDQJH W
06;
Y 2XWSXWEHKDYLRU
6SLQGOHUHVSRQVH
2XWSXW $FNQ
0 $[LVPRYHPHQW
%ORFNFKDQJH W
06;
Y 2XWSXWEHKDYLRU
6SLQGOHUHVSRQVH
2XWSXW $FNQ
0 $[LVPRYHPHQW
%ORFNFKDQJH W
06;
Y 2XWSXWEHKDYLRU
6SLQGOHUHVSRQVH
2XWSXW $FNQ
0 $[LVPRYHPHQW
%ORFNFKDQJH W
Basic functions
0;
Y 2XWSXWEHKDYLRU
6SLQGOHUHVSRQVH
2XWSXW $FNQ
$[LVPRYHPHQW
0
%ORFNFKDQJH W
0;
Y
6SLQGOHUHVSRQVH 2XWSXWEHKDYLRU
2XWSXW $FNQ
$[LVPRYHPHQW
0
%ORFNFKDQJH W
Y 'HIDXOWVHWWLQJ
6SLQGOHUHVSRQVH 06;
2XWSXWEHKDYLRU
2XWSXW $FNQ
$[LVPRYHPHQW
0
%ORFNFKDQJH W
Y 'HIDXOWVHWWLQJ
6SLQGOHUHVSRQVH 06;
2XWSXWEHKDYLRU
2XWSXW $FNQ
$[LVPRYHPHQW
0
%ORFNFKDQJH W
'HIDXOWVHWWLQJ
Y 0;
6SLQGOHUHVSRQVH
2XWSXWEHKDYLRU
2XWSXW $FNQ
$[LVPRYHPHQW
0
%ORFNFKDQJH W
Basic functions
11.3 Userdefined auxiliary functions
Y 'HIDXOWVHWWLQJ
6SLQGOHUHVSRQVH 0;
2XWSXWEHKDYLRU
2XWSXW $FNQ
$[LVPRYHPHQW
0
%ORFNFKDQJH W
'HIDXOWVHWWLQJ
Y 0;
6SLQGOHUHVSRQVH
2XWSXWEHKDYLRU
2XWSXW $FNQ
$[LVPRYHPHQW
0
%ORFNFKDQJH W
Y 'HIDXOWVHWWLQJ
6SLQGOHUHVSRQVH 06;
2XWSXWEHKDYLRU
2XWSXW $FNQ
6 $[LVPRYHPHQW
%ORFNFKDQJH W

There are two uses for user-defined auxiliary functions:
● Extension of predefined auxiliary functions
● User-specific auxiliary functions
Extension of predefined auxiliary functions

Because there is only one set of machine data for the predefined auxiliary functions, they can
only ever be used to address one spindle of the channel. To address further spindles, user-
defined auxiliary functions must be parameterized to supplement the predefined auxiliary
functions.
Extension of predefined auxiliary functions refers to the "address extensions" parameter. The
number of the spindle that the auxiliary function refers to is entered in the "address extension"
parameter.
Basic functions
The relevant predefined auxiliary functions can be extended for the following system functions:
System function Type

Address extension 1)
Value
Tool change M 1 6
Spindle right M 1 3
Spindle left M 1 4
Spindle stop M 1 5
Position spindle M 1 19
Axis mode M 1 70
Automatic gear stage M 1 40
Gear stage 1 M 1 41
Gear stage 2 M 1 42
Gear stage 3 M 1 43
Gear stage 4 M 1 44
Gear stage 5 M 1 45
Spindle speed S 1 -1
Tool selection T 1 -1
1)
Address extension = 1 is the default value used in the auxiliary functions predefined in the machine
data
Example:
Extension of the predefined auxiliary function for the system function "spindle right" for the
second and third spindle of the channel.
Auxiliary function "spindle right" for the second spindle of the channel:
MD22010 $MC_AUXFU_ASSIGN_TYPE[ n ] = "M"
MD22020 $MC_AUXFU_ASSIGN_EXTENSION[ n ] =2
MD22030 $MC_AUXFU_ ASSIGN_VALUE[ n ] =3
Auxiliary function "spindle right" for the third spindle of the channel:
MD22010 $MC_AUXFU_ ASSIGN_TYPE[ m ] = "M"
MD22020 $MC_AUXFU_ASSIGN_EXTENSION[ m ] =3
MD22030 $MC_AUXFU_ ASSIGN_VALUE[ m ] =3
User-specific auxiliary functions

User-specific auxiliary functions have the following characteristics:
● User-specific auxiliary functions only activate user functions.
● No system functions can be activated by user-specific auxiliary functions.
Basic functions
● A user-specific auxiliary function is output to the PLC according to the parameterized output
behavior.
● The functionality of a user-specific auxiliary function is implemented by the machine
manufacturer/user in the PLC user program.
11.3.1.1 Maximum number of user-defined auxiliary functions

The maximum number of user-defined auxiliary function per channel can be parameterized via
the machine data:
MD11100 $MN_AUXFU_MAXNUM_GROUP_ASSIGN (maximum number of user-defined
11.3.1.2 Group assignment

The handling of the auxiliary functions for a block search is defined using the group assignment
of an auxiliary function. The 168 auxiliary function groups available are subdivided into
predefined and user-definable groups:
Predefined groups: 1 ... 4 10 ... 12 72 ... 168

User-defined groups: 5 ... 9 13 ... 71
Every user-defined auxiliary function is assigned as standard to the 1st auxiliary function group.
The assignment can be changed using the following machine data:
MD22000 $MC_AUXFU_ASSIGN_GROUP[<n>] (group assignment of user-defined auxiliary
functions)
If an auxiliary function is not assigned to any group, then a value of "0" should be entered into
the machine data.
Note
1. Auxiliary function group and block search
Auxiliary functions of the 1st auxiliary function group are, for a block search, only collected, but
not output.
11.3.1.3 Type, address extension and value

An auxiliary function is programmed via the type, address extension and value parameters (see
Section "Programming an auxiliary function (Page 647)").
Basic functions
Type
The name of an auxiliary function is defined via the "type".
The identifiers for user-defined auxiliary functions are:
Type Identifier Meaning

"H" Auxiliary function User-specific auxiliary functions
"M" Special function Extension of predefined auxiliary func‐
"S" Spindle function tions
"T" Tool number

MD22010 $MC_AUXFU_ASSIGN_TYPE[<n>] (type of user-defined auxiliary functions)
Address extension
MD22020 $MC_AUXFU_ASSIGN_EXTENSION[<n>] (address extension user-defined
The functionality of the address extension is not defined in user-specific auxiliary functions. It
is generally used to distinguish between auxiliary functions with the same "value".
If all the auxiliary functions of the same type and value are assigned to the same auxiliary
function group, a value of "-1" must be entered for the "address extension" parameter.
Example:
All user-specific auxiliary functions with the value "= 8" are assigned to the tenth auxiliary
function group.
MD22000 $MC_AUXFU_ASSIGN_GROUP [ 1 ] = 10
MD22010 $MC_AUXFU_ ASSIGN_TYPE [ 1 ] = "H"
MD22020 $MC_AUXFU_ ASSIGN_EXTENSION [ 1 ] = -1
MD22030 $MC_AUXFU_ ASSIGN_VALUE [ 1 ] =8
Value
MD22030 $MC_AUXFU_ASSIGN_VALUE[<n>] (value of user-defined auxiliary functions)
The functionality of the "value" parameter is not defined in user-specific auxiliary functions. The
value is generally used to activate the corresponding PLC user function.
If all the auxiliary functions of the same type and address extension are assigned to the same
auxiliary function group, a value of "-1" must be entered for the "value" parameter.
Example:
Basic functions
11.4 Associated auxiliary functions
All user-specific auxiliary functions with the address extension "= 2" are assigned to the
eleventh auxiliary function group.
MD22000 $MC_AUXFU_ASSIGN_GROUP [ 2 ] = 11
MD22010 $MC_AUXFU_ ASSIGN_TYPE [ 2 ] = "H"
MD22020 $MC_AUXFU_ ASSIGN_EXTENSION [ 2 ] =2
MD22030 $MC_AUXFU_ ASSIGN_VALUE [ 2 ] = -1
11.3.1.4 Output behavior

The "output behavior" of user-defined auxiliary functions can be parameterized via the machine
data:
MD22035 $MC_AUXFU_ASSIGN_SPEC[<n>] (output behavior of user-defined auxiliary
functions)
For a description of the individual output parameters, see the "Output behavior (Page 635)"
section of the predefined auxiliary functions. The information given there can be applied
analogously to the output behavior of user-defined auxiliary functions.
Function
Associated help functions are user-defined help functions with the same properties as the
corresponding predefined help functions. User-defined auxiliary functions can be associated
for the following predefined auxiliary functions:
● M0 (programmed stop)
● M1 (optional stop)
G group
An associated help function is assigned to the G group of the corresponding predefined help
function.
Parameterization
Association of a user-defined auxiliary function with one of the predefined auxiliary functions
mentioned is set in the machine data:
● MD22254 $MC_AUXFU_ASSOC_M0_VALUE (associated M function for "Programmed
stop")
● MD22256 $MC_AUXFU_ASSOC_M1_VALUE (associated M function for "Optional stop")
Basic functions
Selection
Selection of "Associated help function" (M-1) is made via the SINUMERIK Operate user
interface in the operating area "Automatic" > "Program control" by setting the HMI/PLC
interface signal DB21, ... DBX24.4.
Depending on the value of the FB1 parameter MMCToIf, the interface signal is transmitted from
the basic PLC program to the NC/PLC interface signal DB21, ... DBX30.5:
● "TRUE": Transmission
● "FALSE": No transmission
By default, the value of the parameter is "TRUE".
Note
Selection option via user interface SINUMERIK Operate
The selection of an associated help function is only displayed in the "Automatic" > "Program
control" operating area if it is parameterized in the machine data.
Application
Associated auxiliary functions can be used in:
● Main program
● Subprogram
● Cycle
Note
Associated auxiliary functions may not be used in synchronized actions.

In the case of an associated user-defined auxiliary function, the same signals are output to the
NC/PLC interface as for the corresponding predefined auxiliary function. To distinguish which
auxiliary function has actually been programmed, the value of the user-defined auxiliary
function ("value" parameter) is output as the value of the auxiliary function. This means it is
possible to distinguish between predefined and user-defined auxiliary functions in the PLC user
program.
NC/PLC interface signals for associated help functions:
● DB21, ... DBX24.4 (associated help function selected)
● DB21, ... DBX30.5 (activate associated help function)
● DB21, ... DBX318.5 (associated help function active)
Basic functions
11.5 Type-specific output behavior
Boundary conditions
Please note the following boundary conditions:
● A user-defined auxiliary function may not be associated a multiple number of times.
● It is not permissible to associate predefined auxiliary functions (e.g. M3, M4, M5 etc.).
Examples
1. Associating the user-defined auxiliary function M111 for M0:
MD22254 $MC_AUXFU_ASSOC_M0_VALUE = 111
The user-defined auxiliary function M111 therefore has the same functionality as M0.
2. Associating the user-defined auxiliary function M222 for M1:
MD22256 $MC_AUXFU_ASSOC_M1_VALUE = 222
The user-defined auxiliary function M222 therefore has the same functionality as M1.
Function
The output behavior of auxiliary functions relative to a traversing motions programmed in the
parts program block can be defined type-specifically.
Parameters are assigned to type-specific output behavior via the machine data:
MD22200 $MC_AUXFU_M_SYNC_TYPE (output time for M functions)
MD22210 $MC_AUXFU_S_SYNC_TYPE (output time for S functions)
MD22220 $MC_AUXFU_T_SYNC_TYPE (output time for T functions)
MD22230 $MC_AUXFU_H_SYNC_TYPE (output time for H functions)
MD22240 $MC_AUXFU_F_SYNC_TYPE (output time for F functions)
MD22250 $MC_AUXFU_D_SYNC_TYPE (output time for D functions)
MD22252 $MC_AUXFU_DL_SYNC_TYPE (output time for DL functions)
The following output behaviors can be parameterized:
MD $MC_AUXFU_xx_SYNC_TYPE = <value>
Value Output behavior

0 Output prior to motion
1 Output during motion
2 Output at block end
3 No output to the PLC
4 Output according to the output behavior defined with MD22080
Basic functions
For a description of the various output behaviors, see the section titled "Output behavior
(Page 635)".
Note
For the output behavior that can be set for each type of auxiliary function, please refer to the
"Detailed Description of Machine Data" Parameter Manual.
Example
Output of auxiliary functions with different output behaviors in a part program block with
traverse movement.
Output behavior for which parameters have been assigned:
MD22200 $MC_AUXFU_M_SYNC_TYPE = 1 ⇒ M function:

Output during motion
MD22220 $MC_AUXFU_T_SYNC_TYPE = 0 ⇒ T function:
Output prior to motion
MD22230 $MC_AUXFU_H_SYNC_TYPE = 2 ⇒ H function:
Output at the end of the block
Parts program block:
Program code
...
N10 G01 X100 M07 H5 T5
...
Time sequence for auxiliary function output:
;
7
0
+
!6WDUW1
Basic functions
11.6 Priorities of the output behavior for which parameters have been assigned
11.6 Priorities of the output behavior for which parameters have been
assigned
The following priorities must be observed for the following areas in connection with the
parameterized output behavior of an auxiliary function:
● Output duration (normal / quick acknowledgement)
● Output relative to motion (prior to / during / after the motion)
As a general rule, the parameterized output behavior with lower priority becomes active if no
output behavior with higher priority has been parameterized.
Output duration
The following priorities apply to the output duration:
Priority Output behavior Defined via:

Highest Auxiliary function-specific Part program instruction: QU(…)
(see Section "Programmable output duration (Page 648)")
↓ Auxiliary function-specific MD22035 $MC_AUXFU_ASSIGN_SYNC[<n>]
MD22080 $MC_AUXFU_PREDEF_SYNC[<n>]
↓ Group-specific MD11110 $MC_AUXFU_GROUP_SPEC[<n>]
Lowest Not defined Default output behavior: Output duration one OB1 cycle
Output relative to motion

The following rules apply to output relative to motion:
Priority Output behavior Defined via:

Highest Auxiliary function-specific MD22035 $MC_AUXFU_ASSIGN_SYNC[<n>]
MD22080 $MC_AUXFU_PREDEF_SYNC[<n>]
↓ Group-specific MD11110 $MC_AUXFU_GROUP_SPEC[<n>]
↓ Type-specific MD22200 $MC_AUXFU_M_SYNC_TYPE
MD22210 $MC_AUXFU_S_SYNC_TYPE
MD22220 $MC_AUXFU_T_SYNC_TYPE
MD22230 $MC_AUXFU_H_SYNC_TYPE
MD22240 $MC_AUXFU_F_SYNC_TYPE
MD22250 $MC_AUXFU_D_SYNC_TYPE
MD22252 $MC_AUXFU_DL_SYNC_TYPE
Lowest Not defined Default output behavior: Output at block end
Note
Part program blocks without path motion
In a part program block without a path motion (even those with positioning axes and spindles),
the auxiliary functions are all output immediately in a block.
Basic functions
11.7 Programming an auxiliary function
11.7 Programming an auxiliary function
Syntax
An auxiliary function is programmed in a part program block with the following syntax:
<Type>[<Address extension>=]<Value>
Note
If no address extension is programmed, the address extension is implicitly set = 0.
Predefined auxiliary functions with the address extension = 0 always refer to the master spindle
of the channel.
Symbolic addressing
The values for the "address extension" and "value" parameters can also be specified
symbolically. The symbolic name for the address extension must then be stated in brackets.
Example:
Symbolic programming of the auxiliary function M3 (spindle right) for the 1st spindle:

DEF SPINDEL_NR=1 ; 1st spindle in the channel
DEF DREHRICHTUNG=3 ; Clockwise rotation
N100 M[SPINDEL_NR]=DREHRICHTUNG ; in accordance with: M1=3
Note
If you use symbolic names to program an auxiliary function, the symbolic name is not
transferred when the auxiliary function is output to the PLC. The corresponding numerical value
is transferred instead.
Examples
Example 1: Programming of predefined auxiliary functions

N10 M3 ; "Spindle clockwise" for the master spindle of the channel.
N20 M0=3 ; "Spindle clockwise" for the master spindle of the channel.
N30 M1=3 ; "Spindle clockwise" for the 1st spindle of the channel.
N40 M2=3 ; "Spindle clockwise" for the 2nd spindle of the channel.
Basic functions
11.8 Programmable output duration
Example 2: Programming examples of auxiliary functions with the corresponding values for
output to the PLC

DEF Coolant=12 ; Output to the PLC: - - -
DEF Lubricant=130 ; Output to the PLC: - - -
H[coolant]=lubricant ; Output to the PLC: H12=130
H=coolant ; Output to the PLC: H0=12
H5 ; Output to the PLC: H0=5
H=5.379 ; Output to the PLC: H0=5.379
H17=3.5 ; Output to the PLC: H17=3.5
H[coolant]=13.8 ; Output to the PLC: H12=13.8
H='HFF13' ; Output to the PLC: H0=65299
H='B1110' ; Output to the PLC: H0=14
H5.3=21 ; Error
Function
User-specific auxiliary functions for which the output behavior "Output duration of an OB1 cycle
(slow acknowledgment)" was parameterized can be defined for individual outputs via the part
program instruction QU (Quick) for auxiliary functions with quick acknowledgment.
Syntax
An auxiliary function with quick acknowledgment is defined in a part program block with the
following syntax:
<Type>[<Address extension>]=QU(<Value>)
Example
Different behavior for the output of the auxiliary functions M100 and M200 in a part program.
The output behavior of the auxiliary functions is parameterized as follows:
● M100
– Output duration one OB1 cycle (slow acknowledgment)
– Output during motion
● M200
– Output duration one OB1 cycle (slow acknowledgment)
– Output prior to motion
Basic functions

N10 G94 G01 X50 M100 ; Output of M100: During motion
; Acknowledgment: Slow
N20 Y5 M100 M200 ; Output of M200: Prior to motion
; Output of M100: During motion
N30 Y0 M=QU(100) M=QU(200) ; Output of M200: Prior to motion
; Output of M100: During motion
; Acknowledgment: Fast
N40 X0
N50 M100 M200 ; Output of M200: Immediately 1)
; Output of M100: Immediately 1)
M17
1)
Without a traversing motion, auxiliary functions are always output to the PLC immediately.
The following figure shows the time sequence of the part program. Please note the time
difference during the processing of part program blocks N20 and N30.
;D[LV
<D[LV
0
0
%ORFNQXPEHU 1 1 1 1 1
6WUREHIURP1&.DQG 0
DFNQRZOHGJHPHQWE\3/&
EDVLFSURJUDP 0
0FKDQJH167
0FKDQJH167
3/&F\FOHWLPH2%
2%
Basic functions
11.10 Auxiliary functions without block change delay
11.9 Auxiliary function output to the PLC
Function
On output of an auxiliary function to the PLC, the following signals and values are transferred
to the NC/PLC interface:
● Change signals
● "Address extension" parameter
● "Value" parameter
Data areas in the NC/PLC interface

The change signals and values of the auxiliary functions are within the following data areas in
the NC/PLC interface:
● Change signals for auxiliary function transfer from NC channel:
DB21, ... DBB58 - DBB67
● Transferred M and S functions:
DB21, ... DBB68 - DBB112
● Transferred T, D and DL functions:
DB21, ... DBB116 - DBB136
● Transferred H and F functions:
DB21, ... DBB140 - DBB190
● Decoded M signals (M0 - M99):
DB21, ... DBB194 - DBB206 (dynamic M functions)
Further information
● Function Manual PLC and Basic Program, Basic PLC program
● Function Manual PLC and Basic Program, Reference on the basic PLC program
11.10 Auxiliary functions without block change delay
Function
For auxiliary functions with parameterized and/or programmed output behavior, too:
● "Output duration one OB40 cycle (quick acknowledgment)"
● "Output before the motion" or "Output during the motion"
there may be drops in velocity in continuos-path mode (short traverse paths and high
velocities). This the system has to wait for acknowledgment of the auxiliary function by the PLC
toward the end of the block. To avoid these velocity drops, the block change can be made
irrespective of whether such auxiliary functions have been acknowledged:
Basic functions
11.11 M function with an implicit preprocessing stop
Suppression of the block change delay with quick auxiliary functions is set via the machine data:
MD22100 $MC_AUXFU_QUICK_BLOCKCHANGE (block change delay with quick auxiliary
functions)
Value Meaning
0 In the case of quick auxiliary function output to the PLC, the block change is delayed until
acknowledgment by the PLC (OB40).
1 In the case of quick auxiliary function output to the PLC, the block change is not delayed.
Boundary conditions
Synchronism of auxiliary functions that are output without a block change delay is no longer
ensured for the part program block in which they are programmed. In the worst case scenario,
acknowledgment comes one OB40 cycle and execution of the auxiliary function comes one
OB1 cycle after the change to the next part program block.
11.11 M function with an implicit preprocessing stop
Function
Triggering a preprocessing stop in conjunction with an auxiliary function can be programmed
explicitly via the STOPRE part program command. Always triggering a preprocessing stop in M
function programming can be parameterized for each M function via the following machine data:
MD10713 $MN_M_NO_FCT_STOPRE[<n>] (M function with preprocessing stop)
Example
The user-defined M function M88 is intended to trigger a preprocessing stop.
Parameterization:
MD10713 $MN_M_NO_FCT_STOPRE [ 0 ] = 88
Application:
Part program (extract)

...
N100 G0 X10 M88 ; Traversing motion and implicit preprocessing stop via M88.
N110 Y=R1 ; N110 is only interpreted after the traversing motion has
been completed and the M function has been acknowledged.
...
Basic functions
11.12 Response to overstore
If a subprogram is called indirectly via an M function in a part program in one of the following
ways, no preprocessing stop is performed:
● MD10715 $MN_M_NO_FCT_CYCLE (M function to be replaced by subprogram)
● M98 (ISO dialect T / ISO dialect M)
11.12 Response to overstore
Overstore
On the SINUMERIK operator interface, before starting the following functions:
● NC START of a part program
● NC START to resume an interrupted part program
the auxiliary functions that are output at the start can be changed by the "Overstore" function.
Possible applications include:
● Addition of auxiliary functions after block search
● Restoring the initial state to position a part program
Types of auxiliary functions that can be overstored

The following types of auxiliary functions can be overstored:
● M (special function)
● S (spindle speed)
● T (tool number)
● H (aux. function)
● D (tool offset number)
● DL (additive tool offset)
● F (feed)
Duration of validity
An overstored auxiliary function, e.g. M3 (spindle right), is valid until it is overwritten by another
auxiliary function from the same auxiliary function group, by additional overstoring or by
programming in a part program block.
Basic functions
11.13 Behavior during block search
11.13.1 Auxiliary function output during type 1, 2, and 4 block searches
Output behavior
In the case of type 1, 2, and 4 block searches, the auxiliary functions are collected on the basis
of specific groups. The last auxiliary function in each auxiliary function group is output after NC-
START in a separate part program block before the actual reentry block, and has the following
output behavior:
● Output duration of one OB1 cycle (normal acknowledgement)
● Output prior to motion
Output control
Whether or not the auxiliary function is output to the PLC after a block search can be configured
via bit 8 of the machine data:
● MD22080 $MC_AUXFU_PREDEF_SPEC[<n>]
(output behavior of predefined auxiliary functions)
where <n> = system function index (0 ... 32)
● MD22035 $MC_AUXFU_ASSIGN_SPEC[<n>]
(output behavior of user-defined auxiliary functions)
where <n> = auxiliary function index (0 ... 254)
● MD11110 $MN_AUXFU_GROUP_SPEC[<n>]
(output behavior of the auxiliary functions in a group)
where <n> = group index (0 ... 63)
Bit Value Meaning

10 0 Output during type 1, 2, and 4 block searches
1 No output during type 1, 2, and 4 block searches
This behavior does not affect the display and does not affect variables
$AC_AUXFU_STATE[<n>], $AC_AUXFU_VALUE[<n>], and $AC_AUXFU_EXT[<n>].
The auxiliary functions are always regarded as collected after a block search, even though they
are not output to the PLC.
During collection, an auxiliary function that is not output after a block search also overwrites an
auxiliary function whose bit 8 is not set.
Basic functions
The user can scan the collected auxiliary functions after a block search and, under certain
circumstances, output them again by means of the subprogram or synchronized actions.
Note
The following auxiliary functions are not collected:
● Auxiliary functions which are not assigned to any auxiliary function group.
● Auxiliary functions which are assigned to the first auxiliary function group.
Overstorage of auxiliary functions

After completion of a block search, the collected auxiliary functions are ouput on the next NC-
START. If it is necessary to output additional auxiliary functions, they can be added via the
"Overstore" function (see Section "Response to overstore (Page 652)").
M19 behavior (position spindle)

After a block search, the last spindle positioning command programmed with M19 is always
carried out, even if other spindle-specific auxiliary functions are programmed between the part
program with M19 and the target block. Setting the necessary spindle enables must therefore
be derived from the interface signals of the traverse commands in the PLC user program:
DB31, ... DBX64.6/64.7 (traversing command minus/plus)
In this case, the spindle-specific auxiliary functions M3, M4, and M5 are not suitable because
they might not be output to the PLC until after the spindle positioning.
For detailed information on the block search, see Section "Mode group, channel, program
operation, reset response (Page 29)".
11.13.2 Assignment of an auxiliary function to a number of groups
Function
User-defined auxiliary functions can also be assigned to multiple groups via the group
assignment (MD22000 $MC_AUXFU_ASSIGN_GROUP). During the block search these
auxiliary functions are collected for all the configured groups.
Note
Predefined auxiliary functions can only be assigned to one group.
Basic functions
Example
The DIN includes the following M-commands for coolant output:
● M7: Coolant 2 ON
● M9: Coolants 1 and 2 OFF
Consequently, both coolants can also be active together:
● If M7 and M8 are collected in two separate groups (e.g. groups 5 and 6)
● If M9 has to be assigned to these two groups, e.g.
– Group 5: M7, M9
– Group 6: M8, M9
Parameterization:
MD11100 $MN_AUXFU_MAXNUM_GROUP_ASSIGN = 4
MD22000 $MC_AUXFU_ASSIGN_GROUP [0] = 5
MD22010 $MC_AUXFU_ASSIGN_TYPE [0] = M
MD22020 $MC_AUXFU_ASSIGN_EXTENSION [0] = 0
MD22030 $MC_AUXFU_ASSIGN_VALUE [0] = 7
MD22035 $MC_AUXFU_ASSIGN_SPEC [0] = 'H121'
Part program (section):
Program code
...
Basic functions
Program code
N10 ... M8
N20 ... M9
N30 ... M7
...
During the block search, the auxiliary function M9 is collected for groups 5 and 6.
Scan of the collected M auxiliary functions:
M function of the fifth group: $AC_AUXFU_M_VALUE [4] = 7
M function of the sixth group: $AC_AUXFU_M_VALUE [5] = 9
11.13.3 Time stamp of the active M auxiliary function

When outputting collected auxiliary functions following a block search, attention must be paid
to the sequence during collecting. For this reason, each group is assigned a time stamp which
can be queried on a group-specific basis by way of the system variable below:
$AC_AUXFU_M_TICK[<n>] (time stamp of the active M auxiliary function)
11.13.4 Determining the output sequence
Function
The following predefined procedure is provided to simplify the process of determining the
output sequence of M auxiliary functions for the programmer:
AUXFUMSEQ(VAR INT _NUM_IN, VAR INT _M_IN[], VAR INT _EXT_IN[], VAR
INT _NUM_OUT, VAR INT _M_OUT[], VAR INT _EXT_OUT[])
Input parameters:
VAR INT _NUM_IN: Number of relevant M commands
VAR INT _M_IN[]: Field of relevant M codes
VAR INT _EXT_IN[]: Field of relevant M address extensions
Output parameters:
VAR INT _NUM_OUT: Number of determined M codes
VAR INT _M_OUT[]: Field of determined M codes
VAR INT _EXT_OUT[]: Field of determined M address extensions
The function determines the sequence in which the M auxiliary functions, which have been
collected on a group-specific basis, are output for the predefined M codes. The sequence is
determined from the collection times $AC_AUXFU_M_TICK[<n>] (see Section "Time stamp of
the active M auxiliary function (Page 656)").
Basic functions
A particular M code is only taken into account once, even if it belongs to more than one group.
If the number of relevant M commands is less than or equal to 0, all the collected M codes are
output. The number of relevant M commands is limited to 64.
Example
M commands for coolant output:
● M9: Coolants 1 and 2 OFF
Group assignment:
● Group 5: M7, M9
● Group 6: M8, M9
Part program (section):
Program code
...
N10 ... M8
N20 ... M9
N30 ... M7
...
During block searches, the auxiliary functions are collected on the basis of specific groups. The
last auxiliary function in an auxiliary function group is output to the PLC following a block search:
● Group 5: M7
● Group 6: M9
If they are output in the sequence M7 → M9, no coolant is then active. However, coolant 2 would
be active during the execution of the program. Therefore, the correct output sequence for the
M auxiliary functions is determined with an ASUP which contains the predefined procedure
AUXFUMSEQ(…):
Program code
DEF INT _I, _M_IN[3], _EXT_IN[3], _NUM_OUT, _M_OUT[2], _EXT_OUT[2]
_M_IN[0]=7 _EXT_IN[0]=0
_M_IN[1]=8 _EXT_IN[1]=0
_M_IN[2]=9 _EXT_IN[2]=0
AUXFUMSEQ(3,_M_IN,_EXT_IN,_NUM_OUT,_M_OUT,_EXT_OUT)
FOR _I = 0 TO _NUM_OUT-1
M[_EXT_OUT[_I]]=_M_OUT[_I]
ENDFOR
Basic functions
11.13.5 Output suppression of spindle-specific auxiliary functions
Function
In certain situations, such as a tool change, it may be necessary not to output the spindle-
specific auxiliary functions collected during the block search in action blocks, but to delay
output, for example, until after a tool change. The automatic output of the spindle-specific
auxiliary functions after a block search may be suppressed for this purpose. Output can then be
performed manually later by overstoring or by an ASUP.
Parameterization
Suppression of the automatic output of the spindle-specific auxiliary functions after a block
search is set via machine data:
MD11450 $MN_SEARCH_RUN_MODE (behavior after a block search)
Bit Value Meaning

2 0 The output of the spindle-specific auxiliary functions is performed in the action blocks.
1 Output of the auxiliary functions is suppressed in the action blocks.
System variables
The spindle-specific auxiliary functions are always stored in the following system variables
during block searches, irrespective of the parameter assignment described above:

$P_SEARCH_S [<n> ] Accumulated spindle speed
Value range: 0 ... Smax
$P_SEARCH_SDIR [<n>] Accumulated spindle direction of rotation
Value range: 3, 4, 5, -5, -19, 70
$P_SEARCH_SGEAR [<n>] Accumulated spindle gear stage M function
Value range: 40 ... 45
$P_SEARCH_SPOS [<n>] Accumulated spindle position
Value range: 0 ... MD30330 $MA_MODULO_RANGE
(size of the module range)
or
Accumulated traversing path
Value range: -100,000,000 ... 100,000,000
$P_SEARCH_SPOSMODE [<n>] Accumulated position approach mode
Value range: 0 ... 5
For later output of the spindle-specific auxiliary functions, the system variables can be read in
an ASUP, for example, and output after the action blocks are output:
Basic functions
DB21, ... DBX32.6 = 1 (last action block active)
Note
The contents of the system variables $P_S, $P_DIR and $P_SGEAR may be lost after block
search due to synchronization operations.
For more detailed information on ASUP, block search and action blocks, see Section "Mode
group, channel, program operation, reset response (Page 29)".
Example
Block search for contour with suppression of output of the spindle-specific auxiliary functions
and start of an ASUP after output of action blocks.
Parameterization: MD11450 $MN_SEARCH_RUN_MODE, bit 2 = 1
After the block search on N55, the ASUP is started.
Part program:

N05 M3 S200 ; Spindle 1:
N10 G4 F3
N15 SPOS=111 ; Spindle 1 is positioned to 111 degrees in the ASUP
N20 M2=4 S2=300 ; Spindle 2:
N25 G4 F3
N30 SPOS[2]=IC(77) ; Spindle 2 traverses incrementally through 77 degrees
N55 X10 G0 ; Target block
N60 G4 F10
N99 M30
ASUP:

PROC ASUP_SAVE
MSG ("Output of the spindle functions")
DEF INT SNR=1
AUSG_SPI:
M[SNR]=$P_SEARCH_SGEAR[SNR] ; Output gear stage.
S[SNR]=$P_SEARCH_S[SNR] ; Output speed (for M40, a suitable
gear stage is determined).
M[SNR]=$P_SEARCH_SDIR[SNR] ; Output direction of rotation, posi-
tioning or axis mode.
SNR=SNR+1 ; Next spindle.
REPEAT AUSG_SPI P=$P_NUM_SPINDLES-1 ; For all spindles.
MSG("")
REPOSA
RET
Explanation of example
Basic functions
If the number of spindles is known, outputs of the same type can be written in one part program
block to reduce program runtime.
Output of $P_SEARCH_SDIR should be made in a separate part program block because
spindle positioning or switchover to axis mode in conjunction with the gear change can cause
an alarm.
If the ASUP which has been started is ended with REPOSA, spindle 1 remains at position 111
degrees, while spindle 2 is repositioned at position 77 degrees.
If a different response is required, the program sequence for block search (for example) "N05
M3 S..." and "N30 SPOS[2] = IC(...)" requires special treatment.
Whether block search is active can be ascertained in the ASUP via the system variable
$P_SEARCH.
$P_SEARCH==1 ; Block search active
In the case of incremental positioning after speed control operation, the path to be traversed is
defined but, in some cases, the final position reached only becomes known during positioning.
This is the case, for example, during position calibration on crossing the zero mark when
switching on position control. For this reason, the distance programmed after the zero position
is accepted as the REPOS position (REPOSA in the ASUP).
Collected S values
The meaning of an S value in the part program depends on the feed type that is currently active:
G93, G94, G95, G97, G971: The S value is interpreted as the speed
G96, G961: The S value is interpreted as a constant cutting rate
If the feed operation is changed (e.g. for a tool change) before output of the system variable
$P_SEARCH_S, the original setting from the target block in the part program must be restored
to avoid use of the wrong type of feed.
Collected direction of rotation
For output of the direction of rotation, the system variable $P_SEARCH_SDIR is assigned
default value "-5" at the start of the block search. This value has no effect on output.
This ensures that the last spindle operating mode is retained for a block search across program
sections in which spindles are not programmed with a direction of rotation, positioning or axis
mode.
The programming of M19, SPOS, and SPOSA is collected as "M-19" (internal M19) in the
system variables $P_SEARCH_SDIR as an alternative to M3, M4, M5, and M70.
For the output of "M-19", the positioning data is read internally from the system variables
$P_SEARCH_SPOS and $P_SEARCH_SPOSMODE. Both system variables can also be
written to, in order, for example, to make corrections.
Note
Because of the assignments described above (e.g. M[<n>] = $P_SEARCH_SDIR[<n>]), the
values "-5" and "19" generally remain hidden from the user and only have to be observed in the
case of special evaluation of the system variables in the ASUP.
Basic functions
11.13.6 Auxiliary function output with a type 5 block search (SERUPRO)
Output behavior
In the case of type 5 block searches (SERUPRO), an auxiliary function can be output to the PLC
during the block search and/or collected on a group-specific basis in the following system
variables:
● $AC_AUXFU_PREDEF_INDEX[<n>] (index of a predefined auxiliary function)
● $AC_AUXFU_TYPE[<n>] (type of auxiliary function)
● $AC_AUXFU_STATE[<n>] (output state of the auxiliary function)
● $AC_AUXFU_EXT[<n>] (address extension of the auxiliary function)
● $AC_AUXFU_VALUE[<n>] (value of the auxiliary function)
For a description of the system variables, see Section "Querying system variables
(Page 674)".
Output control
Whether an auxiliary function is output to the PLC during a type 5 block search (SERUPRO)
and/or collected on a group-specific basis in the following system variables can be configured
via bits 9 and 10 of the machine data:
● MD22080 $MC_AUXFU_PREDEF_SPEC[<n>]
where <n> = system function index (0 ... 32)
● MD22035 $MC_AUXFU_ASSIGN_SPEC[<n>]
where <n> = auxiliary function index (0 ... 254)
● MD11110 $MN_AUXFU_GROUP_SPEC[<n>]
where <n> = group index (0 ... 63)
Bit Value Meaning

9 0 No collection during type 5 block searches (SERUPRO)
1 Collection during type 5 block searches (SERUPRO)
10 0 Output during type 5 block searches (SERUPRO)
1 No output during type 5 block searches (SERUPRO)
Basic functions
Output counter
The user can output the collected auxiliary functions to the PLC on a channel-by-channel basis
in the block search ASUP. For the purposes of serialized output via multiple channels, the three
output counters are changed across all the channels each time an auxiliary function is output:

$AC_AUXFU_TICK[<n>,<m>] Output counter of the active auxiliary function
Index Meaning
<n> Group index (0 … 63)
<m> Output counter (0 ... 2)
Val‐ Meaning
ue
0 Output sequence counter (all outputs within an IPO
cycle)
1 Package counter within an output sequence in the
IPO cycle
2 Auxiliary function counter within a package
Explanation
● An auxiliary function package comprises a maximum of ten auxiliary functions.
● Two packages can be processed per IPO cycle in each channel during SERUPRO because
synchronized actions are processed in this cycle.
● An output sequence of up to a maximum of 20 packages (2 packages per channel * 10
channels) can be processed within an IPO cycle across all channels.
The encoding indicates how many auxiliary function packages and, within these, how many
auxiliary functions have been processed during the same IPO cycle:
● Auxiliary functions which have been collected in one IPO cycle have the same sequence
counter.
● Auxiliary functions which have been collected in one package (block or synchronized action)
all have the same package counter.
The total on the auxiliary function counter increases every time an auxiliary function is collected.
Global list of auxiliary functions

At the end of SERUPRO, the auxiliary functions collected on a group-specific basis in the
individual channels are entered in a cross-channel list with the channel number and group
index according to their counter state.
System variable 1) Meaning

$AC_AUXFU_TICK[<n>,<m>] Counter value
$AN_AUXFU_LIST_CHANNO[<n>] 2) Channel number
$AN_AUXFU_LIST_GROUPINDEX[<n>] 2)
Group index
1) Value range index <n>: 0 ... MAXNUM_GROUPS * MAXNUM_CHANNELS - 1
2) The system variables can be read and written.
Basic functions
&KDQQHO &KDQQHO &KDQQHO
Q 0$;180B*52836 Q 0$;180B*52836

Q 0$;180B*52836
Q Q Q
Q Q
Q
$&B$8;)8B35('()B,1'(;>Q@
$&B$8;)8B35('()B,1'(;>Q@ $&B$8;)8B35('()B,1'(;>Q@
$&B$8;)8B7<3(>Q@ $&B$8;)8B7<3(>Q@ $&B$8;)8B7<3(>Q@
$&B$8;)8B(;7>Q@ $&B$8;)8B(;7>Q@ $&B$8;)8B(;7>Q@
$&B$8;)8B9$/8(>Q@ $&B$8;)8B9$/8(>Q@ $&B$8;)8B9$/8(>Q@
$&B$8;)8B67$7(>Q@ $&B$8;)8B67$7(>Q@ $&B$8;)8B67$7(>Q@
$&B$8;)8B63(&>Q@ $&B$8;)8B63(&>Q@
$&B$8;)8B63(&>Q@
$&B$8;)8B7,&.>Q@ $&B$8;)8B7,&.>Q@ $&B$8;)8B7,&.>Q@
*OREDOOLVWRIDX[LOLDU\IXQFWLRQV
Q 0$;180B*52836 0$;180B&+$11(/6
Q $1B$8;)8B/,67B*5283,1'(;>Q@ $1B$8;)8B/,67B&+$112>Q@

$1B$8;)8B/,67B(1',1'(;

The global list is structured on the basis of the sequence in which the search target was found.
It is intended to be used as a system proposal for auxiliary functions to be output in the following
ASUP at the end of SERUPRO. If an auxiliary function is not to be output, the corresponding
group index is to be set to "0".
Behavior regarding spindle auxiliary functions

Following the start of the block search, all the channels collect the auxiliary functions in the
channel variables on a group-specific basis. In order to perform a far-reaching restoration of the
spindle state in the SERUPRO target block using the collected auxiliary functions, the last
active auxiliary function in any group of spindle auxiliary functions must characterize the state
of the spindle in the target block. In the case of transitions in spindle states, obsolete auxiliary
functions are deleted or, if necessary, implicit auxiliary functions are entered.
All the spindle auxiliary functions from the global auxiliary function list must correspond to the
spindle states achieved in the target block to enable the auxiliary functions to be processed
when the list is output and to ensure that no alarms or unintended spindle states are requested
which could prevent the continuation of the part program.
Basic functions
This affects the groups of auxiliary functions for any spindle configured in the system, whereby
the spindle number corresponds to an auxiliary function's address extension.
Group a: M3, M4, M5, M19, M70

Group b: M40, M41, M42, M43, M44, M45
Group c: S
Deleting obsolete auxiliary functions
In the functions below, the auxiliary functions from group a are deleted for the spindle
concerned:
● For the following spindle when a generic coupling, such as COUPON, TRAILON, EGON,
etc. is switched on
Generating implicit auxiliary functions from group a
In the functions below, the auxiliary functions from group a are generated implicitly for the
spindle concerned:
● For the following spindle when the synchronous spindle coupling is switched off
– COUPOF generates M3, M4 and S or M5 in the main run depending on the coupling
situation.
– COUPOF(S<n>, S<m>, POS) and COUPOFS(S<n>, S<m>, POS, POS) generate M3,
M4 and S.
– COUPOFS generates M5 in the main run.
– COUPOFS(S<n>, S<m>, POS) generates M19 in the main run.
The implicit M19 ("SPOS[<address extension>] = IC(0)" in the ASUP) activates the
positioning mode without a traversing motion.
● M70 is generated during a traversing motion as an axis or during the transition to axis mode
by selecting a transformation during which the spindle enters as an axis.
● M5 is generated during SPCOF.
Note
Within the context of the "axis interchange" and "axis container rotation" functions, the auxiliary
functions for programming the spindle must always be specified in a way which ensures
compatibility with the actual (motor) state during interchange/rotation. A distinction is made
here between the axis interchange and axis container mechanisms.
Example of axis container rotation:
An axis container has four spindles, each assigned to a separate channel (1 - 4). M3 S1000 is
always programmed in channel 1, and an axis container rotation is then executed. The other
channels do not perform any spindle programming. Following the third axis container rotation
and the fourth spindle programming, M3, all four spindles rotate clockwise at a speed of 1000
rpm. If the end of the SERUPRO now lies within this range, every ASUP for a channel is
expected to contain an M3 S1000 for the local spindle.
During interchange however, the collected auxiliary functions may only be assigned to the
channel where the spindle is currently located.
Basic functions
Cross-channel auxiliary function

An auxiliary function can also be collected on a cross-channel basis in the global auxiliary
function list in the case of type 5 block searches (SERUPRO). Only the last auxiliary function
collected from this group (highest counter state) is entered in the global list.
The appropriate configuring is performed with the following machine data:
● MD22080 $MC_AUXFU_PREDEF_SPEC[<n>], Bit 11
where <n> = system function index
● MD22035 $MC_AUXFU_ASSIGN_SPEC[<n>], Bit 11
where <n> = auxiliary function index
● MD11110 $MN_AUXFU_GROUP_SPEC[<n>], Bit 11
where <n> = group index
Bit Value Meaning

11 0 Channel-specific collection
1 Cross-channel collection
The spindle auxiliary functions are filtered out beforehand at the end of the block search
depending on the spindle state. The channel data is updated accordingly. The global auxiliary
function list can be processed sequentially in the ASUPs at the end of the SERUPRO, and the
sorted auxiliary functions can be output with channel synchronization.
Querying the last auxiliary function collected

The index of the last auxiliary function collected in the global list can be queried using the
system variable $AN_AUXFU_LIST_ENDINDEX.
11.13.7 ASUB at the end of the SERUPRO
Function
After completing the block search with the program test (SERUPRO), before starting the
subsequent processing, the auxiliary functions collected during the block search must be
output. For this purpose, during the block search, the auxiliary functions are collected in a global
list. The SERUPRO end ASUPs generate the corresponding part program blocks channel-
specific from this list. This ensures that the collected auxiliary functions can be output both
channel-specific as well as cross-channel in the correct sequence. A fully functional SERUPRO
end ASUP is a component of the NC software.
Users/machinery construction OEMs can change the SERUPRO end ASUP. The
subsequently described functions support processing the global list of auxiliary functions and
generating the part program blocks required for synchronized auxiliary function output.
Basic functions
Function AUXFUSYNC(...)
Function:
The function AUXFUSYNC generates a complete part program block as string from the global list
of auxiliary functions at each call. The part program block either contains auxiliary functions or
commands to synchronize auxiliary function outputs (WAITM, G4, etc.).
The function triggers a preprocessing stop.
Syntax:
PROC AUXFUSYNC(VAR INT <NUM>, VAR INT <GROUPINDEX>[10], VAR
STRING[400] <ASSEMBLED>)
Parameters:
<NUM>: Contains information about the part program block, supplied in param‐
eter <ASSEMBLED> or the auxiliary functions contained in it.
Value range: -1, 0, 1 ... 10
Val‐ Meaning
ue
≥1 Number of auxiliary functions contained in the part program block
0 Part program block without auxiliary functions, e.g. WAITM, G4
-1 End identifier. The global list of auxiliary functions has been
completely processed for the actual channel.
<GROUP INDEX>: Contains the indices of the auxiliary function groups contained in the
part program block. With index = number of the auxiliary function group
-1
<ASSEMBLED>: Contains the complete part program block for the channel-specific
SERUPRO end ASUP as string.
If auxiliary functions were collected via a synchronized action, two NC blocks are generated.
One NC block to output the auxiliary functions. An executable NC block via which the NC block
is transported to the main run to output the auxiliary functions:
1. Output of the auxiliary functions via synchronized action, e.g.: WHEN TRUE DO M100 M102
2. Executable NC block, e.g.: G4 F0.001
Function AUXFUDEL(...)
Function:
The function AUXFUDEL deletes the specified auxiliary function from the global list of auxiliary
functions channel-specific for the calling channel. Deletion is realized by setting the
corresponding group index ...GROUPINDEX[n] to 0.
The function must be called before calling AUXFUSYNC.
Syntax:
PROC AUXFUDEL(CHAR <TYPE>, INT <EXTENSION>, REAL <VALUE>, INT
<GROUP>)
Basic functions
Parameters:
<TYPE>: Type of auxiliary function to be deleted

<EXTENSION>: Address extension of the auxiliary function to be deleted
<VALUE>: Value of auxiliary function to be deleted
<GROUP>: Number of the auxiliary function group
Function AUXFUDELG(...)
Function:
The function AUXFUDELG deletes all auxiliary functions of the specified auxiliary function
group from the global list of auxiliary functions channel-specific for the calling channel. Deletion
is realized by setting the corresponding group index ...GROUPINDEX[n] to 0.
The function must be called before calling AUXFUSYNC.
Syntax:
PROC AUXFUDELG(INT <GROUP>)
Parameters:
<GROUP>: Number of the auxiliary function group
Multi-channel block search
NOTICE
Multi-channel block search and AUXFUDEL / AUXFUDELG
If, for a multi-channel block search in the SERUPRO end ASUPs, auxiliary functions with
AUXFUDEL / AUXFUDELG are deleted from the global list of auxiliary functions, before
calling the AUXFUSYNC function, the channels involved must be synchronized. The
synchronization ensures that before calling the AUXFUSYNC, all delete requests are
processed and a consistent list is available.
Examples
Two examples for configuring a user-specific SERUPRO end ASUP.
Example 1: Deleting auxiliary functions and generating the auxiliary function output with
AUXFUSYNC(...)

N10 DEF STRING[400] ASSEMBLED=""
N20 DEF STRING[31] FILENAME="/_N_CST_DIR/_N_AUXFU_SPF"
N30 DEF INT GROUPINDEX[10]
N40 DEF INT NUM
N60 DEF INT ERROR
Basic functions

N90
N140 AUXFUDEL("M",2,3,5) ; M2=3 (5th auxiliary function group) delete
N150
N170 AUXFUDELG(6) ; Delete the collected auxiliary function of the
; 6th group.
N180
N190 IF ISFILE(FILENAME)
N210 DELETE(ERROR,FILENAME) ; Delete the FILENAME file
N220 IF (ERROR<>0) ; Error evaluation
N230 SETAL(61000+ERROR)
N240 ENDIF
N250 ENDIF
; CAUTION!
; If, for a multi-channel block search, auxiliary functions with AUXFUDEL/AUXFUDELG
; are deleted from the global list of auxiliary functions, before the loop to
; generate the subprogram FILENAME with AUXFUSYNC, the channels must be synchronized.
The synchronization ensures that all delete requests were processed
; in all channels and a consistent list is available.
; Example: WAITM(99,1,2,3)
N270 LOOP
N300 AUXFUSYNC(NUM,GROUPINDEX,ASSEMBLED) ; Generate a part program block
N310
N320 IF (NUM==-1) ; All auxiliary functions of the channel
; have been executed.
N340 GOTOF LABEL1
N350 ENDIF
N380 WRITE(ERROR,FILENAME,ASSEMBLED) ; Write a part program block to file FILENAME.
N390 IF (ERROR<>0) ; Error evaluation
N410 ENDIF
N430 ENDLOOP
N440
N450 LABEL1:
N460
N480 CALL FILENAME ; Execute a generated subprogram.
N490
N510 DELETE(ERROR,FILENAME) ; Delete the file again after execution.
N520 IF (ERROR<>0)
N540 ENDIF
N550
N560 M17
Basic functions
Example 2: Deleting auxiliary functions and generating the auxiliary function output without
AUXFUSYNC(...)

N0610 DEF STRING[400] ASSEMBLED=""
N0620 DEF STRING[31] FILENAME="/_N_CST_DIR/_N_AUXFU_SPF"
N0630 DEF INT GROUPINDEX[10]
N0640 DEF INT NUM
N0650 DEF INT LAUF
N0660 DEF INT ERROR
N0670 DEF BOOL ISQUICK
N0680 DEF BOOL ISSYNACT
N0690 DEF BOOL ISIMPL
...
N0760 AUXFUDEL("M",2,3,5) ; M2=3 (5th auxiliary function group) delete
N0770
N0790 AUXFUDELG(6) ; Delete the collected auxiliary function of the
; 6th group.
N0800
N0810 IF ISFILE(FILENAME)
N0830 DELETE(ERROR,FILENAME) ; File already exists and must be
; deleted.
N0840 IF (ERROR<>0)
N0860 ENDIF
N0870 ENDIF
N0880
; CAUTION!
; If, for a multi-channel block search, auxiliary functions with AUXFUDEL/AUXFUDELG
; are deleted from the global list of auxiliary functions, before the loop to
; generate the subprogram FILENAME with AUXFUSYNC, the channels must be synchronized.
The synchronization ensures that all delete requests were processed
; in all channels and a consistent list is available.
; Example: WAITM(99,1,2,3)
N0890 LOOP
N0920 AUXFUSYNC(NUM,GROUPINDEX,ASSEMBLED) ; Procedure to generate
; auxiliary function blocks from the global
; auxiliary function list.
N0930
N0940 IF (NUM==-1) ; All auxiliary functions of the channel
; have been executed.
N0960 GOTOF LABEL1
N0970 ENDIF
N0980
N1000 IF (NUM>0) ; If auxiliary functions are output,
; the block is generated.
Basic functions

N1010
N1020 ASSEMBLED=""
N1030
N1050 FOR LAUF=0 TO NUM-1 ; Collected auxiliary functions for a
; block.
N1060
N1080 IF GROUPINDEX[LAUF]<>0 ; Auxiliary functions deleted from the
; global list have the group index 0.
N1090
N1100 ISQUICK=$AC_AUXFU_SPEC[GROUPINDEX[LAUF]] BAND'H2'
N1110
N1120 ISSYNACT=$AC_AUXFU_SPEC[GROUPINDEX[LAUF]] BAND'H1000'
N1130
N1140 ISIMPL=$AC_AUXFU_SPEC[GROUPINDEX[LAUF]] BAND'H2000'
N1150
N1180 IF ISSYNACT ; Assemble a block for the M auxiliary
; function output
N1190 ASSEMBLED= ASSEMBLED << "WHEN TRUE DO "
N1200 ENDIF
N1210 ; Implicitly generated M19 is mapped to SPOS[SPI(<Spindle no.>)] = IC(0)
N1230 IF (ISIMPL AND ($AC_AUXFU_VALUE[GROUPINDEX[LAUF]==19))
N1240 ASSEMBLED= ASSEMBLED << "SPOS[SPI(" <<
$AC_AUXFU_EXT[GROUPINDEX[LAUF]] << ")=IC(0)"
N1260 ELSE
N1270 ASSEMBLED= ASSEMBLED << "M[" << $AC_AUXFU_EXT[GROUPINDEX[LAUF]] << "]="
N1280
N1290 IF ISQUICK
N1300 ASSEMBLED= ASSEMBLED << "QU("
N1310 ENDIF
N1320
N1330 ASSEMBLED= ASSEMBLED << $AC_AUXFU_VALUE[GROUPINDEX[LAUF]]
N1340
N1350 IF ISQUICK
N1360 ASSEMBLED= ASSEMBLED << ")"
N1370 ENDIF
N1380 ENDIF
N1400 ENDIF
N1420 ENDFOR
N1430
N1450 WRITE(ERROR,FILENAME,ASSEMBLED) ; Write an auxiliary function block to a file.
N1460
N1470 IF ISSYNACT
N1480 ASSEMBLED="G4 F0.001"
N1490 WRITE(ERROR,FILENAME,ASSEMBLED)
Basic functions
11.14 Implicitly output auxiliary functions

N1500 ENDIF
N1510
N1520 ELSE
N1540 WRITE(ERROR,FILENAME,ASSEMBLED) ; Write an auxiliary function block to a file.
N1550 ENDIF
N1560
N1570 ENDLOOP
N1580
N1590 LABEL1:
N1600
N1620 CALL FILENAME ; Execute a generated subprogram.
N1630
N1650 DELETE(ERROR,FILENAME) ; Delete the file again after execution.
N1660 IF (ERROR<>0)
N1680 ENDIF
N1690
N1700 M17
11.14 Implicitly output auxiliary functions
Function
Implicitly output auxiliary functions are auxiliary functions which have not been programmed
explicitly and which are also output by other system functions (e.g. transformation selection,
tool selection, etc.). These implicit auxiliary functions do not lead to any system function;
instead, the M codes are collected according to output behavior parameters assigned to them
and/or are output to the PLC.
Basic functions
11.15 Information options
Parameterization
The M codes for auxiliary functions to be output implicitly are defined with the machine data:
● MD22530 $MC_TOCARR_CHANGE_M_CODE (M code at toolholder change)
This machine data value indicates the number of the M code which is output when a
toolholder is activated at the NC/PLC interface.
If the value is positive, the unchanged M code is always output.
If the value is negative, the number of the toolholder is added to the machine data value, and
this number is output.
● MD22532 $MC_GEOAX_CHANGE_M_CODE (M code when switching the geometry axes)
Number of the M code which is output when the geometry axes on the NC/PLC interface are
switched.
● MD22534 $MC_TRAFO_CHANGE_M_CODE (M code in the case of transformation
changes)
Number of the M code which is output during a transformation switch of the geometry axes
at the NC/PLC interface.
Note
No M code is output if the number of the M code being output or the MD22530/MD22532/
MD22534 value is between 0 and 6, or is either 17 or 30. Whether or not an M code which
is generated in this manner leads to conflicts with other functions is not monitored.
Output behavior
In the case of implicitly output auxiliary functions, bit 13 is set in machine data MD22080 or
MD22035 (output behavior of predefined or user-defined auxiliary functions).
This bit can be queried via the system variable $AC_AUXFU_SPEC[<n>].
Implicitly output auxiliary function M19

To achieve uniformity in terms of how M19 and SPOS or SPOSA behave at the NC/PLC
interface, auxiliary function M19 can be output to the NC/PLC interface in the event of SPOS
and SPOSA (see Function Manual Axes and Spindles, Section Spindles).
The implicitly output auxiliary function M19 is collected during the block search.

Information about auxiliary functions (e.g. about the output status) is possible via:
● The group-specific modal M auxiliary function display on the user interface
● Querying system variables in part programs and synchronized actions
Basic functions
11.15.1 Group-specific modal M auxiliary function display
Function
The output status and acknowledgment status of M auxiliary functions can be displayed on the
user interface on a group-specific basis.
Requirements
To implement function-oriented acknowledgment and display of M auxiliary functions, the
auxiliary functions must be managed in the PLC and, thus, in the user program itself. Therefore,
it is up to the PLC programmer to program the acknowledgment of these auxiliary functions.
The programmer must know which auxiliary functions in which group have to be acknowledged.
Standard
M auxiliary functions that are not managed by means of the PLC are identified by the NC as
"transferred" and output to the PLC. There is no functional acknowledgment for these auxiliary
functions. All M-auxiliary functions collected after a block search are also displayed so that the
operator knows which auxiliary functions will be output after a start following a block search.
PLC activities
In the case of auxiliary function groups that are managed by the PLC itself, the PLC user
program must acknowledge all auxiliary functions of this group at Transfer and End of function.
The PLC programmer must know all the auxiliary functions of these groups.
Miscellaneous
Only the group-specific M auxiliary functions are displayed. The block-by-block display is also
retained. Up to 15 groups can be displayed, whereby only the last M function of a group that was
either collected or output to the PLC is displayed for each group. The M functions are presented
in various display modes depending on their status:
Status Display mode

Auxiliary function is collected Inverted with yellow font
Auxiliary function is output from NC to PLC Inverted
Auxiliary function has been transferred from NC to PLC and Black font on gray background
transport acknowledgment has taken place
Auxiliary function is managed by the PLC and has been Black font on gray background
taken over directly by the PLC
Auxiliary function is managed by the PLC and the function Black font on gray background
acknowledgment has taken place
Basic functions
Display update
The display is organized in such a way that the collected auxiliary functions are always output
first, before those managed by the PLC and before those managed by the NC. A collected
auxiliary function is marked as collected until it has been output from the NC to the PLC. PLC-
managed auxiliary functions are retained until they are substituted by another auxiliary
function. At a reset, only the collected auxiliary functions and the NC-managed auxiliary
functions are deleted.
11.15.2 Querying system variables
Function
Auxiliary functions can be queried on a group-specific basis via system variables in the part
program and via synchronized actions:
$AC_AUXFU_... [<n>] = <Value>

$AC_AUXFU_PREDEF_INDEX[<n>] <Value>: Index of the last auxiliary function collected for an
auxiliary function group (block search) or the last
predefined auxiliary function to be output
Type INT
:
If no auxiliary function has been output yet for the
specified group or if the auxiliary function is a
user-defined auxiliary function, the variable sup‐
plies the value "-1".
<n>: Group index (0 … 63)
Note:
A predefined auxiliary function can be uniquely identified via
this variable.
$AC_AUXFU_TYPE[<n>] <Value>: Type of the last auxiliary function collected for an
auxiliary function group (block search) or the last
auxiliary function to be output
Type CHAR
:
$AC_AUXFU_EXT[<n>] <Value>: Address extension of the last auxiliary function
or or M function-specific: collected for an auxiliary function group (block
search) or the last auxiliary function to be output
$AC_AUXFU_M_EXT[<n>]
Type INT
:
Basic functions

$AC_AUXFU_VALUE[<n>] <Value>: Value of the last auxiliary function collected for an
or or M function-specific: auxiliary function group (block search) or the last
auxiliary function to be output
$AC_AUXFU_M_VALUE[<n>]
Type REAL
:
$AC_AUXFU_SPEC[<n>] Value: Bit-encoded output behavior according to
MD22080/MD22035 (or QU programming) of the
last auxiliary function collected for an auxiliary
function group (block search) or the last auxiliary
function to be output
Type INT
:
Note:
This variable can be used to determine whether the auxiliary
function should be output with a fast acknowledgment.
$AC_AUXFU_STATE[<n>] <Value>: Output state of the last auxiliary function collec‐
or or M function-specific: ted for an auxiliary function group (block search)
or the last auxiliary function to be output
$AC_AUXFU_M_STATE[<n>]
Type: INT
Range of values: 0 ... 5
0: Auxiliary function does not exist
1: M-auxiliary function was collected via a
block search
2: M-auxiliary function has been output to the
PLC
3: M-auxiliary function has been output to the
PLC and the transport acknowledgment has
taken place
4: M-auxiliary function is managed by the PLC
and has been taken over by the PLC
5: M-auxiliary function is managed by the PLC,
and the function acknowledgment has taken
place
Example
All M-auxiliary functions of the 1st group will be stored in the order they are output
id=1 every $AC_AUXFU_M_STATE[0]==2 do $AC_FIFO[0,0]=
$AC_AUXFU_M_VALUE[0]
Further information
List Manual System Variables
Basic functions
11.16.1 General constraints
Spindle replacement
Because the auxiliary functions are parameterized channel-specifically, if function: "spindle
replacement" is used, the spindle-specific auxiliary function must be parameterized
immediately in all channels that use the spindles.
Tool management
If tool management is active, the following constraints apply:
● T and M<k> functions are not output to the PLC.
Note
k is the parameterized value of the auxiliary function for the tool change (default: 6):
MD22560 $MC_TOOL_CHANGE_M_CODE (auxiliary function for tool change)
● If no address extension is programmed, the auxiliary function refers to the master spindle or
the master tool holder of the channel.
Definition of the master spindle:
– MD20090 $MC_SPIND_DEF_MASTER_SPIND
– Part program instruction: SETMS
Definition of the master tool holder
– MD20124 $MC_TOOL_MANAGEMENT_TOOLHOLDER
– Part program instruction: SETMTH
Maximum number of auxiliary functions per part program block

A maximum of 10 auxiliary functions may be programmed in one part program block.
DL (additive tool offset)

The following restrictions apply to the DL function:
● Only one DL function can be programmed per part program block.
● If DL functions are used in synchronous actions, parameter: "Value" is not output to the PLC.
Basic functions
11.16.2 Output behavior
Thread cutting
During active thread cutting G33, G34 and G35, the following output behavior is always active
for the spindle-specific auxiliary functions:
● M3 (spindle right)
● M4 (spindle left)
● Output duration of one OB40 cycle (quick acknowledgement)

● Output during motion
The spindle-specific auxiliary function M5 (spindle stop) is always output at the end of the block.
The part program block that contains M5 is always ended with exact stop, i.e. even during active
continuous-path mode.
With output auxiliary functions from synchronized actions, the parameterized output behavior
is ignored except for the following parameters:
● Bit0: Output duration of one OB1 cycle (normal acknowledgement)
● Bit1: Output duration of one OB40 cycle (quick acknowledgement)
Auxiliary functions: M17 or M2/M30 (end of subprogram)

In its own part program block
If one of the auxiliary functions M17, M2 or M30 is programmed as the only auxiliary function in
a part program block and an axis is still in motion, the auxiliary function is not output to the PLC
until after the axis has stopped.
Overriding the parameterized output behavior
The parameterized output behavior of the auxiliary functions M17 or M2/M30 is overridden by
the output behavior that is determined in the following machine data:
MD20800 $MC_SPF_END_TO_VDI, bit 0 (subprogram end / stop to PLC)
Bit Value Meaning

0 0 The auxiliary functions M17 or M2/M30 (subprogram end) are not output to the PLC. Con‐
tinuous-path mode is not interrupted at the end of the subprogram
1 The auxiliary functions M17 or M2/M30 (subprogram end) are output to the PLC.
Auxiliary function: M1 (conditional stop)

Overriding the parameterized output behavior
The parameterized output behavior of the auxiliary function M1 is overridden by the output
behavior defined in the following machine data:
Basic functions
11.17 Examples
MD20800 $MC_SPF_END_TO_VDI, bit 1 (subprogram end / stop to PLC)
Bit Value Meaning

1 0 The auxiliary function M01 (conditional stop) is always output to the PLC. A quick ac‐
knowledgement is ineffective, because M01 is permanently assigned to the first auxiliary
function group and is therefore always output at the end of the block.
1 The auxiliary function M01 (conditional stop) is only output to the PLC, if the function:
"Programmed stop" is activated via the HMI user interface.
In the case of a quick acknowledgement, the M1 is output to the PLC during the motion.
While the function is not active, this does not interrupt continuous-path mode.
Part program blocks without traversing motion

In a part program block without a traversing motion, all auxiliary functions are output in a block
immediately, irrespective of their parameterized output behavior.
Spindle-specific auxiliary function output only as information for the PLC user program
In certain controller situations, e.g. at the end of a block search, the collected spindle-specific
auxiliary functions (e.g. M3, M4, M5, M19, M40...M45, M70) is output to the NC/PLC interface only
for information purposes for the PLC user program. The controller generates a part program
block (action block) in which the collected auxiliary functions are entered with a negative
address extension. The corresponding system functions are then not executed.
Example: M(-2) = 41 request gear stage change for the 2nd spindle
11.17 Examples
11.17.1 Extension of predefined auxiliary functions
Task
Parameter assignment of auxiliary functions M3, M4, and M5 for the second spindle of the
channel
Parameter assignment: M3
Requirements:
● Machine data index: 0 (first user-defined auxiliary function)
● auxiliary function group: 5
● Type and value: M3 (spindle right)
Basic functions
11.17 Examples
● Address extension: 2 as appropriate for the 2nd spindle of the channel

● Output behavior:
– Output duration one OB1 cycle (normal acknowledgment)
Parameter assignment:
MD22000 $MC_AUXFU_ASSIGN_GROUP[ 0 ] =5
MD22010 $MC_AUXFU_ASSIGN_TYPE [ 0 ] = "M"
MD22020 $MC_AUXFU_ASSIGN_EXTENSION [ 0 ] =2
MD22030 $MC_AUXFU_ASSIGN_VALUE [ 0 ] =3
MD22035 $MC_AUXFU_ASSIGN_SPEC [ 0 ] = 'H21'
Requirements:
● Machine data index: 1 (second user-defined auxiliary function)
● Type and value: M4 (spindle left)
– Spindle response following acknowledgment
– Output during motion
MD22000 $MC_AUXFU_ASSIGN_GROUP [ 1 ] =5
Requirements:
● Machine data index: 2 (third user-defined auxiliary function)
● Type and value: M5 (spindle stop)
Basic functions
11.17 Examples

– Spindle response following acknowledgment
– Output at block end
MD22000 $MC_AUXFU_ASSIGN_GROUP [ 2 ] =5
11.17.2 Defining auxiliary functions
Task
Parameterization of the auxiliary function-specific machine data for a machine with the
following configuration:
Spindles
● Spindle 1: Master spindle
● Spindle 2: Second spindle
Gear stages
● Spindle 1: 5 gear stages
● Spindle 2: No gear stages
Switching functions for cooling water on/off
● Spindle 1
– "On" = M50
– "Off" = M51
● Spindle 2
– "On" = M52
– "Off" = M53
Basic functions
11.17 Examples
Requirements
Spindle 1 (master spindle)
Note
Default assignments
● The auxiliary functions M3, M4, M5, M70 and M1=3, M1=4, M1=5, M1=70 of spindle 1
(master spindle) are assigned as standard to the 2nd auxiliary function group.
● All S and S1 values of spindle 1 (master spindle) are assigned as standard to the
3rd auxiliary function group.
● The gear stage last programmed is to be output after block search. The following auxiliary
functions are assigned for this reason to the 9th auxiliary function group:
– M40, M41, M42, M43, M44, M45
– M1=40, M1=41, M1=42, M1=43, M1=44, M1=45
● The auxiliary functions M3, M4, M5, M70 and M1=3, M1=4, M1=5, M1=70 (2nd auxiliary
function group) and S and S1 values (3rd auxiliary function group) should possess the
following output behavior:
– Output duration one OB40 cycle (quick acknowledgment)
● The auxiliary functions for gear changeover M40 to M45 and M1=40 to M1=45 (9th auxiliary
function group) should have the following output behavior:
– Output duration of one OB1 cycle (normal acknowledgment)
Spindle 2
● Only one M function for directional reversal may be programmed in one block. The direction
of rotation last programmed is to be output after block search. The following auxiliary
functions are assigned for this reason to the 10th auxiliary function group:
– M2=3, M2=4, M2=5, M2=70
● All S2 values are assigned to the 11th auxiliary function group.
● The auxiliary functions M2=3, M2=4, M2=5, M2=70 (10th auxiliary function group) and S2
values (11th auxiliary function group) should have the following output behavior:
– Output duration one OB40 cycle (quick acknowledgment)
Basic functions
11.17 Examples
Cooling water
● It is not permissible to switch the cooling water on and off in one part program block. After
a block search, the cooling water will be switched on or off. The following auxiliary functions
are assigned for this reason, e.g. to the 12th or 13th auxiliary function group:
– 12th auxiliary function group: M50, M51
– 13th auxiliary function group: M52, M53
● The auxiliary functions M50, M51 (12th auxiliary function group) and M52, M53
(13th auxiliary function group) should have the following output behavior:
– Output duration of one OB1 cycle (normal acknowledgment)
Parameterization of the machine data

The machine data is parameterized by appropriate programming within a part program.

$MN_AUXFU_MAXNUM_GROUP_ASSIGN=21 ; Number of user-defined auxiliary functions
per channel
$MN_AUXFU_GROUP_SPEC[1]='H22' ; Output behavior of the 2nd auxiliary func-

tion group
$MN_AUXFU_GROUP_SPEC[2]='H22' ; Output behavior of the 3rd auxiliary func-
tion group
$MN_AUXFU_GROUP_SPEC[8]='H21' ; Output behavior of the 9th auxiliary func-
tion group
$MC_AUXFU_ASSIGN_TYPE[0]="M" ; Description of the 1st auxiliary function:

M40
$MC_AUXFU_ASSIGN_EXTENSION[0]=0
$MC_AUXFU_ASSIGN_VALUE[0]=40
$MC_AUXFU_ASSIGN_GROUP[0]=9
; ... (and analogously for the 2nd - 5th auxil-
iary functions)
$MC_AUXFU_ASSIGN_TYPE[5]="M" ; Description of the 6th auxiliary function:
M45

M1=40
; . . . (and analogously for the 8th - 11th
Basic functions
11.17 Examples

M1=45
$MN_AUXFU_GROUP_SPEC[9] = 'H22' ; Output behavior of the 10th auxiliary func-

tion group

M2=3

M2=4

M2=5

M2=70
$MN_AUXFU_GROUP_SPEC[10]='H22' ; Specification of the 11th auxiliary function

group
$MC_AUXFU_ASSIGN_TYPE[16]="S" ; Description of the 17th auxiliary function:

S2=<all values>
$MC_AUXFU_ASSIGN_VALUE[16]=-1

group
Basic functions
11.18 Data lists

M50

M51

group

M52
$MC_AUXFU_ASSIGN_TYPE[20]="M" ; Description of the 21st auxiliary function:

M53
11.18 Data lists
11.18.1 Machine data

10713 M_NO_FCT_STOPRE M function with preprocessing stop
10714 M_NO_FCT_EOP M function for spindle active after NC RESET
10715 M_NO_FCT_CYCLE M function to be replaced by subroutine
11100 AUXFU_MAXNUM_GROUP_ASSIGN Maximum number of user-defined auxiliary functions
per channel
Basic functions
11.18 Data lists

11110 AUXFU_GROUP_SPEC Group-specific output behavior
11450 SEARCH_RUN_MODE Behavior after a block search

20110 RESET_MODE_MASK Definition of control initial setting after part program
start.
20112 START_MODE_MASK Definition of control initial setting after powerup and on
RESET or at end of part program
20270 CUTTING_EDGE_DEFAULT Basic setting of tool cutting edge without programming
20800 SPF_END_TO_VDI Subroutine end / Stop at PLC
22000 AUXFU_ASSIGN_GROUP Group assignment of user-defined auxiliary functions
22010 AUXFU_ASSIGN_TYPE Type of user-defined auxiliary functions
22020 AUXFU_ASSIGN_EXTENSION Address extension for user-defined auxiliary functions
22030 AUXFU_ASSIGN_VALUE Value of user-defined auxiliary functions
22035 AUXFU_ASSIGN_SPEC Output behavior of user-defined auxiliary functions
22040 AUXFU_PREDEF_GROUP Group assignment of predefined auxiliary functions
22050 AUXFU_PREDEF_TYPE Type of predefined auxiliary functions
22060 AUXFU_PREDEF_EXTENSION Address extension for predefined auxiliary functions
22070 AUXFU_PREDEF_VALUE Value of predefined auxiliary functions
22080 AUXFU_PREDEF_SPEC Output behavior of predefined auxiliary functions
22100 AUXFU_QUICK_BLOCKCHANGE Block change delay with quick auxiliary functions
22110 AUXFU_H_TYPE_INT Type of H auxiliary functions
22200 AUXFU_M_SYNC_TYPE M functions output time
22210 AUXFU_S_SYNC_TYPE S functions output time
22220 AUXFU_T_SYNC_TYPE T functions output time
22230 AUXFU_H_SYNC_TYPE H functions output time
22240 AUXFU_F_SYNC_TYPE F functions output time
22250 AUXFU_D_SYNC_TYPE D functions output time
22252 AUXFU_DL_SYNC_TYPE DL functions output time
22254 AUXFU_ASSOC_M0_VALUE Additional M function for program stop
22256 AUXFU_ASSOC_M1_VALUE Additional M function for conditional stop
22530 TOCARR_CHANGE_M_CODE M code for change of tool holder
22532 GEOAX_CHANGE_M_CODE M code for replacement of geometry axes
22534 TRAFO_CHANGE_M_CODE M code for change of tool holder
22560 TOOL_CHANGE_M_CODE Auxiliary function for tool change
Basic functions
11.18 Data lists
Basic functions
Digital and analog NC I/O 12
12.1 Introduction
Functions
I/O modules can be connected to a SINUMERIK 840D sl via PROFIBUS or PROFINET.
Normally, the PLC user program uses the appropriate digital or analog inputs and outputs for
access. The "Digital and analog NC I/O for SINUMERIK 840D sl" function enables access to the
inputs/outputs of the I/O modules via system variables of compile cycles directly from the NC
(part programs, synchronized actions and compile cycles). This I/O is referred to as the NC I/O
in the following.
Three different functions are available for compatibility reasons:
1. Indirect I/O access via PLC (Page 688)
The read and write requests of the inputs/outputs of the I/O modules are written from the NC
via the interface to the PLC. The requests are processed cyclically in the OB1 cycle.
This function has the lowest performance with regard to the quantity structure and response
time.
2. Direct I/O access via PLC (Page 709)
The read and write requests of the inputs/outputs of the I/O modules are written from the NC
via the interface to the PLC. An interrupt is then triggered on the PLC. The requests from the
PLC are processed as part of the interrupt processing.
From the quantity structure, the function is equivalent to that described above. However, the
response time is not as good.
3. Direct I/O access without PLC (Page 714)
Avoiding the PLC, the control internal images of the inputs/outputs of the I/O modules can
be accessed directly from the NC.
This is currently the function with the highest performance with regard to the quantity
structure and response time.
Prerequisites
● The PROFIBUS/PROFINET I/O modules of the NC I/O must be connected and ready to use.
● The HW configuration of the PROFIBUS/PROFINET I/O modules of the NC I/O has been
performed with the SIMATIC S7 Manager or HW Config and loaded to the PLC.
Basic functions
Digital and analog NC I/O
12.2 Indirect I/O access via PLC
Monitoring
The following monitoring functions are active for the NC I/Os:
● Run-up:
– Check for consistency of the I/Os detected on the PLC and the NC I/O parameterized in
the machine data.
● Cyclic operation:
– Sign-of-life monitoring in interpolation cycles
– Module monitoring in interpolation cycles
– Temperature monitoring
In the event of an error, the DB10.DBX104.7 "NC ready" signal is reset and an alarm is
displayed.
Response to faults
The digital and analog outputs of the NC I/O are switched to a safe status (0 V) in the event of
faults (e.g. NC ready = 0), for errors in the NCU or power failures.
Application
The NC I/O is used, for example, by the following NC functions:
● Several feedrate values or auxiliary functions in one block
● Rapid retraction on final dimension
● Axis-specific delete distance-to-go
● Program branches
● Rapid NC Start
● Analog calipers
● Position switching signals
● Punching/nibbling functions
● Analog-value control
12.2.1 Brief description

There are three I/O interfaces (X122, X132 and X142) on the SINUMERIK 840D sl NCU.
Four digital inputs and outputs of the X142 interface are available as so-called fast NC I/O. They
can be read or written via the first address byte and via the $A_IN[1...4] and $A_OUT[1...4]
system variables.
Basic functions
I/O modules can also be connected to the PROFIBUS DP/MPI interfaces X126 and X136. This
enables the number of digital and analog NC inputs/outputs to be expanded by 32 digital and 8
analog inputs and outputs respectively. These NC inputs/outputs are called external NC I/Os
in the following.
Table 12-1 Maximum number of digital and analog NC I/Os
Onboard NC I/O Total

Digital inputs 4 32 36
Digital outputs 4 32 36
Analog inputs - 8 8
Analog outputs - 8 8
Further information
● Manual SINUMERIK 840D sl
● Operating instructions for SIMATIC ET 200S FC
See also
Direct I/O access via PLC (Page 709)
Machine data
Number of active NC I/Os

The number of active or from the NC usable digital NC I/O bytes are set in the following machine
data:
● Number of digital NC input bytes
MD10350 $MN_FASTIO_DIG_NUM_INPUTS = <number>
● Number of digital NC output bytes
MD10360 $MN_FASTIO_DIG_NUM_OUTPUTS = <number>
The number of active or from the NC usable analog I/Os are set in the following machine data:
● Number of analog NC inputs
MD10300 $MN_FASTIO_ANA_NUM_INPUTS = <number>
● Number of the analog NC outputs
MD10310 $MN_FASTIO_ANA_NUM_OUTPUTS = <number>
The I/Os do not have to actually exist in the hardware. In this case, the signal states or the
analog values are set to "zero" in a defined way inside the NC.
The values present at the I/O inputs can be changed from the PLC user program before they
are read by the NC.
Basic functions
Slot addresses
Addressing of the digital I/Os:
● HW assignment for external digital inputs
MD10366 $MN_HW_ASSIGN_DIG_FASTIN[ <n> ] = <addressH>
● HW assignment for external digital outputs
MD10368 $MN_HW_ASSIGN_DIG_FASTOUT[ <n> ] = <addressH>
Addressing of the analog I/Os:
● HW assignment for external analog inputs
MD10362 $MN_HW_ASSIGN_ANA_FASTIN[ <n> ] = <addressH>
● HW assignment for external analog outputs
MD10364 $MN_HW_ASSIGN_ANA_FASTOUT[ <n> ] = <addressH>
<n>: Index for addressing the external digital I/O bytes (0 ... 3) or the external analog
I/Os (0 ... 7)
<address>: Slot address of the PROFIBUS/PROFINET module with 05 00 xxxx
05 Identifier for PROFIBUS/PROFINET module
00 Permanently assigned
xxxxH Hexadecimal logical start address of the slot
0000 = no active slot
The following must be taken into account for logical start addresses
within the PLC process image:
● Input slots: Reading from the NC also possible
● Output slots: Writing from the NC not permitted ⇒ alarm after run-
up of the NC
Further information
Equipment Manual NCU 7x0.3 PN, NCU 7x0.3B PN; Technical data >
PLC > Process image size
Detailed information can be obtained under Address (http://
support.automation.siemens.com/WW/view/de/54058408)
Weighting factors for analog inputs/outputs

The weighting factor can be used to adapt each individual analog NC I/O to the AD or DA
converter of the analog I/O module used:
● Weighting factor for the analog NC inputs (see "Analog NC inputs (Page 698)"):
MD10320 $MN_FASTIO_ANA_INPUT_WEIGHT[<n>]
● Weighting factor for the analog NC outputs (see "Analog NC outputs (Page 700)"):
MD10330 $MN_FASTIO_ANA_OUTPUT_WEIGHT[<n>]
<n>: Index for addressing the external analog I/Os (0 ... 7)
Assignment to NC functions
The I/Os are required by several NC functions. The assignment of the I/Os used is performed
function-specifically via machine data, e.g. for the "Multiple feedrates in one block" function via
the machine data:
Basic functions
MD21220 $MC_MULTFEED_ASSIGN_FASTIN = <byte address>
<byte address> Digital NC I/Os

0 None
1 1 ... 4 Onboard inputs/outputs
5 ... 8 NC output without hardware
2 9 ... 16 External NC I/O
128 Inputs 1 to 8 of comparator byte 1
129 Inputs 9 to 16 of comparator byte 2
Note
Multiple assignments
Multiple assignments of inputs are not considered to be incorrect parameterization.
Multiple assignments of outputs are considered to be incorrect parameterization, are checked
during run-up and indicated by an alarm.
Example: Hardware assignment of external I/Os

Two input bytes and one output byte are parameterized for the reading/writing of digital I/Os of
a PROFIBUS module.
Number of active NC I/O bytes
MD10350 $MN_FASTIO_DIG_NUM_INPUTS ; 2 digital input bytes + 1 onboard byte

=2+1=3
MD10360 $MN_FASTIO_DIG_NUM_OUT‐ ; 1 digital output byte + 1 onboard byte
PUTS = 1 + 1 = 2
Hardware assignment
MD10366 $MN_HW_ASSIGN_DIG_FAS‐ ; $A_IN[ 9 ] ... [ 16 ] from 1st I/O input byte

TIN[ 0 ] = 'H5000200'
MD10366 $MN_HW_ASSIGN_DIG_FAS‐ ; $A_IN[ 17 ] ... [ 24 ] from 2nd I/O input byte
TIN[ 1 ] = 'H5000201'
MD10368 $MN_HW_ASSIGN_DIG_FAST‐ ; $A_OUT[ 9 ] ... [ 16 ] in 1st I/O output byte
OUT[ 0 ] = 'H5000200'
The hexadecimal addresses 200H and 201H entered in the machine data correspond to those
assigned during the configuration in the SIMATIC S7 Manager, decimal logical start addresses
512D and 513D
Basic functions

Input data
System variable Index or input number <n>

$A_IN[ <n> ] 1 ... 4 and 9 ... 40, see Digital NC inputs (Page 692)
$A_INA [<n>] 1 ... 8, see Analog NC inputs (Page 698)
A preprocessing stop is triggered in the channel when reading input data from a part program.
Output data
System variable Index or output number <n>

$A_OUT [<n>] 1 ... 4 and 9 ... 40, see Digital NC outputs (Page 694)
$A_OUTA [<n>] 1 ... 8, see Analog NC outputs (Page 700)
A preprocessing stop is triggered in the channel when reading output data from a part program.
12.2.4 Comparator inputs

In addition to the I/O inputs, 16 control-internal comparator inputs are available.
The current signal state of a comparator input results from the comparison of an analog I/O
input with a threshold value specified in the setting data.
See "Comparator inputs (Page 705)".
12.2.5 Digital NC I/Os
12.2.5.1 Digital NC inputs
Function
Using system variables $A_IN, values of digital NC inputs can be read into an NC program or
synchronized action. The read value can be influenced via NC/PLC interface signals.
Digital NC inputs are used, for example, for the following NC functions:
● Delete distance-to-go with positioning axes
● Fast program branching at the end of block
● Programmed read-in disable
● Several feedrates in one block
Further information
Basic functions
1&LQSXW
1& 3/&
$FWXDOYDOXH

'%'%%'%%

/RFN
'%'%%'%%

6HW
'%'%%'%%
1&SURJUDP

$B,1>@ 1&LQSXWYDOXH

Actual value
The actual value of the NC input can be read in the PLC user program via the actual value
interface.
Note
Different values
The value in the "Actual value" interface can, as a result of the various subsequent influencing
possibilities, have a different value than that available at the NC input, which is read using
system variable $A_IN.
Lock
If a bit is set in the interface, for the corresponding input, a value of 0 is transferred.
Set
Overview
Lock Set Actual value NC input

DBX0.0 - 7 DBX1.0 - 7 DBX60.0 - 7 1-8
DBX122.0 - 7 DBX123.0 - 7 DBX186.0 - 7 9 - 16
DBX124.0 - 7 DBX125.0 - 7 DBX187.0 - 7 17 - 24
DBX126.0 - 7 DBX127.0 - 7 DBX188.0 - 7 25 - 32
DBX128.0 - 7 DBX129.0 - 7 DBX189.0 - 7 33 - 40
Basic functions
Boundary conditions
Response after a warm restart and channel reset

The value at the hardware input is transferred, unchanged after a warm restart and channel
reset.
12.2.5.2 Digital NC outputs
Function
Using system variables $A_OUT, values of digital NC outputs can be written to an NC program
or synchronized action. The written value can be influenced using NC/PLC interface signals.
● Positioning switching signals (see Function Manual Axes and Spindles, Section Software
cams)
● Output of comparator signals
Further information
1& 3/&
1&SURJUDP

$B287>@ 6HWWLQJYDOXH
'%'%%'%%

2YHUZULWH
'%'%%'%%
1&RXWSXWYDOXH 6HWSRLQW
'%'%%'%%

7DUJHW
'%'%%'%%

/RFN
'%'%%'%%
1&RXWSXW
Basic functions
Overwrite
If, in the interface, a bit is set, then for the corresponding output, instead of the value written
using system variables $A_OUT, the setting value specified from the PLC user program is
used. The value written via system variables $A_OUT is then lost.
If the bit in the interface is reset, then the actual value is kept at the hardware output.
Setting value
Using the setting value, the PLC user program can specify a defined output value. In order that
the setting value becomes active, it must be activated via the interfaces for "Overwrite" or
"Target".
Setpoint
The actual NC output value can be read in the PLC user program via the setpoint.
Note
Different values
The value in the "Setpoint" interface can, as a result of the various subsequent influencing
possibilities, have a different value than that available at the NC output.
Target
If, in the interface, a bit is set, then for the corresponding output, instead of the NC output value,
the setting value specified by the PLC user program is used. The actual NC output value is kept.
If a bit is reset in the interface, then the last NC output value becomes active again.
Lock
If a bit is set in the interface, for the corresponding output, a value of 0 is output.
Overview
Lock Overwrite Setting value Target Setpoint NC output

DBX4.0 - 7 DBX5.0 - 7 DBX6.0 - 7 DBX7.0 - 7 DBX64.0 - 7 1-8
DBX130.0 - 7 DBX131.0 - 7 DBX132.0 - 7 DBX133.0 - 7 DBX190.0 - 7 9 - 16
Boundary conditions
NC outputs without hardware

An alarm is not displayed if NC outputs are written to, which were defined (MD10360
$MN_FASTIO_DIG_NUM_OUTPUTS), but the corresponding hardware is not available. The
setpoint can be read via the PLC user program.
Basic functions
Behavior at end of program reset/channel reset

From the PLC user program, via the interfaces for "Overwrite", "Target" or "Lock", at the end of
program or for a channel reset, every NC output can be set in defined fashion as a function of
the specific application.
Behavior for a warm restart

All NC outputs are set to "0" after a warm restart. From the PLC user program, using the
overwrite or setting screen form, every NC output can be set as a function of the specific
application.
12.2.5.3 Connection and logic operations of fast digital I/Os
Function
Fast NC I/O inputs can be set via the software depending on the fast-output signal states.
Overview:
2XWSXW ,QSXW
%\WH %\WH
%LW %LW
$OWHUQDWLYHV
,QWHUFRQQHFW
25ORJLFRSHUDWLRQ
$1'ORJLFRSHUDWLRQ
Connecting
The NC I/O fast input is set to the signal state of the assigned fast output.
OR operation
The NC I/O fast input adopts the signal state as a result of the ORing of the output signal with
the assigned input signal.
AND operation
The NC I/O fast input adopts the signal state as a result of the ANDing of the output signal with
the assigned input signal.
Basic functions
Special cases
● If several output bits are assigned to the same input bit, then the one with the highest MD
index becomes effective.
● If inputs or outputs are specified which do not exist or are not activated, then the assignment
is ignored without an alarm. Checking of the active bytes of the NC I/Os is performed via the
entries in machine data:
MD10350 $MN_FASTIO_DIG_NUM_INPUTS
MD10360 $MN_FASTIO_DIG_NUM_OUTPUTS
Defining assignments
The assignments are specified via machine data:
MD10361 $MN_FASTIO_DIG_SHORT_CIRCUIT[n]
n: can accept values 0 to 9, so up to 10 assignments can be specified.
Two hexadecimal characters are provided for specifying the byte and bit of an output and an
input.
Specifying 0, A and B in input bits 12 - 15 results in the following logic operations:
0 Connecting
A AND operation
B OR operation
)$67,2B',*B6+257B&,5&8,7>Q@
2XWSXW ,QSXW
%LW %\WH %LW %\WH
൹7\SHRIORJLFRS
%LW
Examples
Connect:
MD10361 $MN_FASTIO_DIG_SHORT_CIRCUIT = '04010302H'
Output 4, byte 1, connect to
Input 3, byte 2
AND operation:
MD10361 $MN_FASTIO_DIG_SHORT_CIRCUIT = '0705A201H'
Output 7, byte 5 AND operation with
Input 2, byte 1
OR operation:
Basic functions
MD10361 $MN_FASTIO_DIG_SHORT_CIRCUIT = '0103B502H'

Output 1, byte 3 OR operation with
Input 5, byte 2
12.2.6 Analog NC I/Os
12.2.6.1 Analog NC inputs
Function
Using system variables $A_INA, values of analog NC inputs can be read into an NC program
or synchronized action. The read value can be influenced via NC/PLC interface signals.
Binary analog value display
1&LQSXW
1& 3/&
$FWXDOYDOXH
'%'%:'%:

/RFN
'%'%%
6HWWLQJYDOXH
'%'%:'%:

7DUJHW
'%'%%
1&SURJUDP

$B,1>@ 1&LQSXWYDOXH

Actual value
The actual value of the NC input can be read in the PLC user program via the actual value
interface.
Basic functions
The actual value is represented as a fixed point number (16 bit value including sign) in a 2's
complement.
See "Representation of the analog I/O values (Page 703)".
Note
Different values
The value in the "Actual value" interface can, as a result of the various subsequent influencing
possibilities, have a different value than that available at the NC input, which is read using
system variable $A_INA.
Lock
Setting value
Using the setting value, the PLC user program can specify a defined input value. In order that
the setting value becomes active, it must be activated via the "Overwrite" interface.
The setting value must be specified as a fixed point number (16 bit value including sign) in 2's
complement.
Target
If a bit is set in the interface, for the corresponding input, the associated "Setting value" is
transferred.
Overview
Lock Target Setting value Actual value NC input

DBX146.0 - 7 DBX147.0 - 7 DBW148 - 162 DBW194 - 209 1-8
Machine data
Weighting factor
Using the weighting factor, for each analog NC input, the DA converter of the I/O module being
used can be adapted by appropriately parameterizing it.
MD10320 $MN_FASTIO_ANAINTPUT_WEIGHT[<Output>]
Note
Analog NC inputs without hardware
With a weighting factor of 32767, the digitized analog values for the NC program and PLC user
program are identical. As a consequence, the NC output can be used for 1:1 communication
between the NC program and PLC user program.
Basic functions
Analog NC inputs without hardware

$MN_FASTIO_ANA_NUM_INPUTS), but the corresponding hardware is not available. The
actual value can be read via the PLC user program.
Behavior for a warm restart, end of program reset and channel reset
After a warm restart, end of program reset or channel reset, for all NC inputs, the analog value
present is transferred. Every NC input can be set as a function of the specific application from
the PLC user program.
12.2.6.2 Analog NC outputs
Function
Using system variables $A_OUTA, values of analog NC outputs can be written to an NC
program or synchronized action. The written value can be influenced using machine data and
NC/PLC interface signals.
Further information
Basic functions
1& 3/&
1&SURJUDP

$B287$>@

(YDOXDWLRQ
6HWWLQJYDOXHIURPWKH3/&
'%'%:'%:

2YHUZULWH
'%'%%
6HWSRLQW
1&RXWSXWYDOXH
'%'%:'%:

7DUJHW
'%'%%

/RFN
'%'%%
1&RXWSXW
1) MD10330 $MN_FASTIO_ANA_OUTPUT_WEIGHT[<Output>]
Setting value
Using the setting value, the PLC user program can specify a defined output value. In order that
the setting value becomes active, it must be activated via the interfaces for "Overwrite" or
"Target".
The setting value must be specified as a fixed point number (16 bit value including sign) in 2's
complement.
Overwrite
If a bit is set, then for the corresponding output, instead of the value written using system
variables $A_OUTA, the setting value specified from the PLC user program is used. The value
written via system variables $A_OUTA is then lost.
Basic functions
If a bit is reset, for the corresponding output, the actual value at the hardware output is kept.
Target
If a bit is set, then for the corresponding output, instead of the NC output value, the setting value
specified by the PLC user program is used. The actual NC output value is kept.
If a bit is reset, then for the corresponding output, the last NC output value becomes active
again.
Lock
If a bit is set in the interface, a value of 0 is output at the corresponding NC output.
Setpoint
The actual NC output value can be read in the PLC user program via the setpoint.
The setpoint is represented as a fixed point number (16 bit value including sign) in a 2's
complement.
Note
Different values
The value in the "Setpoint" interface can, as a result of the various subsequent influencing
possibilities, have a different value than that available at the NC output.
Overview
Lock Overwrite Setting value Target Setpoint NC output

DBX168.0 - 7 DBX166.0 - 7 DBW170 - 184 DBX167.0 - 7 DBW210 - 225 1-8
Machine data
Weighting factor
Using the weighting factor, for each analog NC output, the DA converter of the I/O module being
used can be adapted by appropriately parameterizing it.
MD10330 $MN_FASTIO_ANA_OUTPUT_WEIGHT[<Output>]

; Assumption: Analog value range ±10 V
; Parameterization: MD10330 $MN_FASTIO_ANA_OUTPUT_WEIGHT[<output>] = 10000
$A_OUTA[<output>] = 9500 ; NC output: 9.5 V
$A_OUTA[<output>] = -4120 ; NC output: -4.12 V
Basic functions
Note
Analog NC outputs without hardware
With a weighting factor of 32767, the digitized analog values for the NC program and PLC user
program are identical. As a consequence, the NC output can be used for 1:1 communication
between the NC program and PLC user program.
Boundary conditions
Analog NC outputs without hardware

$MN_FASTIO_ANA_NUM_OUTPUTS), but the corresponding hardware is not available. The
setpoint can be read via the PLC user program.
Behavior for a warm restart

All NC outputs are set to "0" after a warm restart. Every NC input can be set as a function of the
specific application from the PLC user program.
Behavior at end of program reset/channel reset

From the PLC user program, via the interfaces for "Overwrite", "Target" or "Lock", at the end of
program or for a channel reset, every NC output can be set in defined fashion as a function of
the specific application.
12.2.6.3 Representation of the analog I/O values

The digitized analog values are represented at the NC/PLC interface as fixed-point numbers
(16 bits including sign) in the two's complement.
Bit number 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Signifi‐ SG 2 14
2 13
2 12
2
11
2 10
2 9
2 8
27
2 6
2 5
24
2 3
2 2
21
20
cance
SG: Sign
Minimum value Maximum value

-32768D 32767D
8000H 7FFFH
Increment
For a resolution of 16 bits and a nominal range of ±10 V, the increment is:
20 V / 216 = 20 V / 65536 ≈ 0.305 mV
Basic functions
Resolutions < 16 bits

If the resolution of an analog module is less than 16 bits including sign, then the digitized analog
value is entered in the interface starting from bit 14. The unused least significant bit positions
are filled with "0".
14-bit resolution
For a resolution of 14 bits including sign and a nominal range of ±10 V, the increment is:
20 V / 214 = 20 V / 16384 ≈ 1.22 mV
Bit 0 ... 1 are always "0".
12-bit resolution
For a resolution of 12 bits including sign and a nominal range of ±10 V, the increment is:
20 V / 212 = 20 V / 4096 ≈ 4.88 mV
Bit 0 ... 3 are always "0".
Representation of the maximum value for different resolutions
Bit number 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Significance of the bits SG 2 14
2
13
2
12
211
2
10
29
2 8
2
7
2 6
2 5
24
2 3
2 2
21
20
16-bit resolution: 32767D = 7FFFH 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
14-bit resolution: 8191D = 1FFFH 0 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0
12-bit resolution: 2047D = 7FFH 0 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0
Note
The data (resolution, nominal range) of the analog input/output module used can be taken from
the documentation of the particular module.
Examples
Digital representation of analog values at a resolution of 14 bits including sign and a nominal
range of ±10 V.
Example 1: Analog value = 9.5 V
Digitized analog value (decimal): 9.5 V / 20 V * 16384 = 7782

Digitized analog value 14-bit (binary): 01 1110 0110 0110
Digitized analog value 16-bit (hex): 7998H
Example 2: Analog value = -4.12 V
Digitized analog value (decimal): -4.12 V / 20 V * 16384 = -3375

Digitized analog value 16-bit (hex): CB44 H
Basic functions
12.2.7 Comparator inputs
Function
Two internal comparator input bytes, each with eight comparator inputs, are available in
addition to the digital and analog NC inputs. The signal state of the comparator inputs is
generated on the basis of a comparison between the analog values present at the fast analog
inputs and the threshold values parameterized in setting data.
The $A_INCO[<n>] system variable allows the signal state (i.e. the result of the comparison) of
comparator input [<n>] to be scanned directly in the part program.
Applies for index <n>:
<n> = 1 ... 8 For comparator byte 1

<n> = 9 ... 16 For comparator byte 2
Terms
In this description, the terms comparator inputs (with index <n>; value range of <n>: 1 ... 8 or
9 ... 16) and comparator input bits (with index ; value range of : 0 ... 7) are used.
They are related as follows:
For <n> = 1 ... 8: Comparator input <n> is equivalent to comparator input bit
 = <n> - 1.
For <n> = 9 ... 16: Comparator input <n> is equivalent to comparator input bit
 = <n> - 9.
Example: Comparator input 1 is equivalent to comparator input bit 0.
Assignment of the analog inputs

The following machine data is used to assign an analog input to input bit of comparator byte
1:
MD10530 $MN_COMPAR_ASSIGN_ANA_INPUT_1[]
Example:
MD10530 $MN_COMPAR_ASSIGN_ANA_INPUT_1[0] = 1
Analog input 1 acts on input bits 0 and 1 of comparator byte 1.
Analog input 7 acts on input bit 7 of comparator byte 1.
The analog inputs for comparator byte 2 are assigned with the machine data:
MD10531 $MN_COMPAR_ASSIGN_ANA_INPUT_2[]
Basic functions
Comparator settings
The settings for the individual bits (0 to 7) of comparator byte 1 or 2 are parameterized via the
machine data:
MD10540 $MN_COMPAR_TYPE_1 (parameter assignment for comparator byte 1)
or
MD10541 $MN_COMPAR_TYPE_2 (parameter assignment for comparator byte 2)
The following settings are possible:
● Comparison type mask (bits 0 … 7)
The type of comparison condition is defined for each comparator input bit:
Bit = 1: Associated comparator input bit is set to "1" if:

Analog value ≥ threshold value
Bit = 0: Associated comparator input bit is set to "0" if:
Analog value < threshold value
● Output of the comparator input byte via digital NC outputs (bits 16 … 23)
The comparator bits can also be output directly via the digital NC outputs byte-by-byte. This
requires specification in this byte (bits 16 … 23) of the digital NC output byte to be used.
Byte = 0: No output via digital NC outputs

Byte = 1: Output via digital onboard NC outputs 9 … 16
Byte = 2: Output via external digital NC outputs 17 … 24
● Inversion mask for output of the comparator input byte (bits 24 … 31)
For every comparator signal it is also possible to define whether the signal state to be output
at the digital NC output is to be inverted or not.
Bit = 1: Associated comparator input bit is not inverted.

Bit = 0: Associated comparator input bit is inverted.
Threshold values
The threshold values used for comparisons on comparator byte 1 or 2 must be stored as setting
data. A separate threshold value must be entered for each comparator input bit (with 
= 0 … 7):
SD41600 $SN_COMPAR_THRESHOLD_1[]
or
SD41601 $SN_COMPAR_THRESHOLD_2[]
Basic functions
Comparator signals as digital NC inputs

All NC functions that are processed as a function of digital NC inputs can also be controlled by
the signal states of the comparators. The byte address for comparator byte 1 (HW byte 128) or
2 (HW byte 129) must be entered in the machine data associated with the NC function
("Assignment of hardware byte used").
Example:
"Multiple feedrates in one block" NC function
Entry in channel-specific machine data:
MD21220 $MC_MULTFEED_ASSIGN_FASTIN = 129
This activates various feedrate values as a function of the status of comparator byte 2.
Basic functions
Functional sequence
The functional sequence for comparator input byte 1 is represented schematically in the
following figure.
'LJLWDO
$QDORJLQSXW
2XWSXWE\WH
$QDORJLQSXW
0'>E!@ Q! $VVLJQPHQWRIDQDORJLQSXW 'LJLWDORXWSXWV 0'%LW

Q!WRFRPSDUDWRUELW %\WHVSHFLILFDWLRQ
0'%LW &RPSDULVRQ
ELW $QDORJYDOXHWKUHVKROGYDOXH ,QYHUVLRQPDVN 0'%LW
RU
%LW $QDORJYDOXHุWKUHVKROGYDOXH
7KUHVKROGYDOXH
7KUHVKROGYDOXH
6'
&RPSDUDWRULQSXWE\WH &RPSDUDWRULQSXWE\WH
&RPSDUDWRULQSXWELW
&RPSDUDWRULQSXW
3DUWSURJUDP

$B,1&2>Q!@ 1&IXQFWLRQV

5HDGLQJRIFRPSDUDWRU $FFHVVWRFRPSDUDWRULQSXWE\WH
LQSXWQ!Q! bb RURI1&IXQFWLRQV
)URPWKHSDUWSURJUDP
Basic functions
12.3 Direct I/O access via PLC
Machine data
Length of the I/O ranges

● Number of PLC I/O input bytes that are read directly by the NC:
MD10394 $MN_PLCIO_NUM_BYTES_IN
● Number of PLC I/O output bytes that are written directly by the NC:
MD10396 $MN_PLCIO_NUM_BYTES_OUT
Logical start addresses

● Logical start address as of which the data is read from the PLC input I/O. The offset used for
the subsequent addressing, e.g. $A_PBB_IN[< offset >] refers to the start address specified
in the machine data:
MD10395 $MN_PLCIO_LOGIC_ADDRESS_IN
● Logical start address as of which the data is written to the PLC input I/O. The offset used for
the subsequent addressing, e.g. $A_PBB_OUT[< offset >] refers to the start address
specified in the machine data:
MD10397 $MN_PLCIO_LOGIC_ADDRESS_OUT
Update time
● Time within which the data that can be read by means of $A_PBx_IN is updated (see
Subsection "Transfer times" below).
MD10398 $MN_PLCIO_IN_UPDATE_TIME
Format display
● Format display of system variables $A_PBx_OUT and $A_PBx_IN (see Subsection
"Selection of the storage format (little/big endian)" below).
MD10399 $MN_PLCIO_TYPE_REPRESENTATION
Note
The logical PLC I/O addresses entered in the machine data and the number of bytes to be
transferred must be consistent with the PLC hardware configuration. In the configured areas,
there must not be any "address gaps" in the PLC I/O expanded configuration.
Basic functions
Principle of the parameterization of the NC I/O in the input area
0'01B3/&,2B/2*,&B$''5(66B,1
0'01B3/&,2B180B%<7(6B,1

3/&LQSXWLPDJH
Transfer times
● Transfer of the output data from the NC to the output modules
– The output data is transferred from the NC to the output modules at the end of the current
interpolator cycle.
– The transfer is only performed when at least one output data item has been written in the
current interpolator cycle.
● Transfer of the input data from the input modules to the NC
– Time within which the cyclic request for the update of the input data (input image of the
modules → NC input data) from the NC to the PLC is sent, can be set via the machine
data:
– MD10398 $MN_PLCIO_IN_UPDATE_TIME = <update time>
– The parameterized update time is rounded up internally to the next highest multiple of an
interpolator cycle. With update time = 0, the request is transferred to the PLC in each
interpolation cycle.
– The request for the update of the input data is sent to the PLC at the end of the
parameterized interpolation cycle.
– The updated input data is available at the earliest in the following interpolation cycle.
Selection of the storage format (little/big endian)

A total of 16 KB is available for the data transfer between the NC and PLC for all NC channels.
These areas have to be managed by the user (i.e. no overlapping of the variables, not even
across channel borders).
The display of the variables within these areas depends on the setting in the machine data:
Basic functions
MD10399 $MN_PLCIO_TYPE_REPRESENTATION = <value>
<val‐ Meaning
ue>
0 Little endian format (default setting)
System variables are displayed in little endian format ⇒ least significant byte at least significant
address
1 Big endian format (PLC standard format, recommended)
System variables are displayed in big endian format ⇒ most significant byte at least significant
address
Note
The big endian format is the format usually used in the PLC and PLC I/O. Therefore, it is
recommended that you use this setting.
12.3.2 Reading/writing: System variables

Input data
System variable Type Offset <n>

$A_PBB_IN[<n>] Byte 0, 1, 2, ... (MD10394 $MN_PLCIO_NUM_BYTES_IN -1)
$A_PBW_IN[<n>] Word 0, 2, 4, ... (MD10394 $MN_PLCIO_NUM_BYTES_IN - 2)
$A_PBD_IN[<n>] Double 0, 4, 8, ... (MD10394 $MN_PLCIO_NUM_BYTES_IN - 4)
$A_PBR_IN[<n>] Real 0, 4, 8, ... (MD10394 $MN_PLCIO_NUM_BYTES_IN - 4)
A preprocessing stop is triggered in the channel when reading from a part program.
Output data
System variable Type Offset <n>

$A_PBB_OUT[<n>] Byte 0, 1, 2, ... (MD10396 $MN_PLCIO_NUM_BYTES_OUT - 1)
$A_PBW_OUT[<n>] Word 0, 2, 4, ... (MD10396 $MN_PLCIO_NUM_BYTES_OUT - 2)
$A_PBD_OUT[<n>] Double 0, 4, 8, ... (MD10396 $MN_PLCIO_NUM_BYTES_OUT - 4)
$A_PBR_OUT[<n>] Real 0, 4, 8, ... (MD10396 $MN_PLCIO_NUM_BYTES_OUT - 4)
A preprocessing stop is triggered in the channel when reading output data from a part program.
Value ranges of the output data
Type Value range

Byte With sign: -128 ... +127
Without sign: 0 ... 255
Word With sign: -32768 ... +32767
Without sign: 0 ... 65535
Double With sign: -2147483648 ... +2147483647
Without sign: 0 ... 4294967295
Real -3.402823466*10+38 ... +3.402823466*10+38
Basic functions

Several slots
If several slots form an input or output range of the PLC I/O used directly by the NC, the address
range of the slots must be configured as a continuous range without gaps.
Parallel writing of the NC and PLC

Parallel writing of I/O outputs by the NC via direct access over the PLC and from the PLC user
program results in a random, mutual overwriting of the output values. The application is
therefore not permitted, but cannot be prevented on the control.
Time response
The time when the data is read in from the PLC I/Os is not synchronized with the time when the
data is made available to the part program via system variables!
Data transfer
● The output of the output data on the PLC I/O is always for all parameterized output data,
even when only one output data item was written for each system variable.
● If several system variables are assigned values simultaneously, it is not certain that they are
transferred in the same interpolation cycle.
12.3.4 Examples
12.3.4.1 Writing to PLC-I/Os
Specifications
● Decimal logical addresses of the output data to be written within the PLC I/O
– 521: 1-byte integer value
● The output data is written to a part program via the R parameters R10 - R11.
● In order to only slow down the execution of the PLC user program (OB1) slightly, the update
cycle for write access should be 3-times the interpolator cycle of 12 ms.
● Data is to be output directly to the following PLC I/Os:
Parameterization
The machine data should be set as follows:
● Length of the NC I/O output data area: 2 + 1 = 3 bytes
MD10396 $MN_PLCIO_NUM_BYTES_OUT= 3
● Logical start address of the input data area: 521
MD10397 $MN_PLCIO_LOGIC_ADDRESS_OUT = 521
Basic functions
● Update cycle: I/O input data → system variables = 3 * interpolator cycle= 3 * 12 ms = 36 ms

MD10398 $MN_PLCIO_OUT_UPDATE_TIME = 3 * 0.012 = 0.036
● Data format: Big endian
MD10399 $MN_PLCIO_TYPE_REPRESENTATION = 1
Refreshing
The transfer of the system data to the PLC I/O is not performed until the PLC has detected the
PROFIBUS/PROFINET I/O error-free after the control startup. The transfer is then performed
in every third interpolation cycle.
Programming
Writing the NC I/O to synchronized actions with R parameters:

R10=123
R11='Habcd'
ID=1 WHENEVER TRUE DO $A_PBB_OUT[0]=R10 ; 1-byte integer value
ID=2 WHEN $AA_IW[x] >= 5 DO $A_PBW_OUT[1]=R11 ; 2-byte integer value
Addressing example: $PBW_OUT[ 1 ] = R11
0'01B3/&,2B/2*,&B$''5(66B287
0'
01B3/&,2B180B%<7(6B287
$B3%:B287>@

3/&RXWSXWLPDJH
12.3.4.2 Reading from PLC-I/Os
Specifications
● Decimal logical addresses of the input data to be read within the PLC I/O
– 426: 4-byte real value
● The input data should be stored in a part program in the R parameters R1 - R4.
● In order to only slow down the execution of the PLC user program (OB1) slightly, the update
cycle for read access should be 3-times the interpolator cycle of 12 ms.
Basic functions
12.4 Direct I/O access without PLC
Parameterization
● Length of the NC I/O input data area: 2 + 4 + 4 + 1 = 11 bytes
MD10394 $MN_PLCIO_NUM_BYTES_IN = 11
● Logical start address of the input data area: 420
MD10395 $MN_PLCIO_LOGIC_ADRESS_IN = 420
● Update cycle: I/O input data → system variables = 3 * interpolator cycle= 3 * 12 ms = 36 ms
MD10398 $MN_PLCIO_IN_UPDATE_TIME = 3 * 0.012 = 0.036
● Data format: Big endian
MD10399 $MN_PLCIO_TYPE_REPRESENTATION = 1
Refreshing
The system variables are updated in every third interpolation cycle after the NC and PLC
startup.
Programming
Reading in the NC I/O in R parameters:

R1=$A_PBW_IN[0] ; 2-byte integer value
R2=$A_PBD_IN[2] ; 4-byte integer value
R3=$A_PBR_IN[6] ; 4-byte real value
R4=$A_PBB_IN[10] ; 1-byte integer value
Addressing example: R2 = $PBD_IN[ 2 ]
0'01B3/&,2B/2*,&B$''5(66B,1
0'01B3/&,2B180B%<7(6B,1
$B3%'B,1>@

3/&LQSXWLPDJH
12.4.1 Brief description
Isochronous and non-isochronous PROFINET

Reading / writing of the PROFINET I/O is possible with both isochronous and non-isochronous
PROFINET configuration.
Basic functions
I/O range
If slots are configured for a PROFINET slave used for the NC I/O in such a way that they are
in ascending order without gaps, they are called the I/O range in the following.
An I/O range is therefore characterized by:
● Logical start address: Logical start address of the first slot of the PROFINET slave
● Length: Total length of all slots used for the PROFINET slave
The parameterization of the logical start address and the length of the I/O range is performed
in the NC via machine data (see "Parameter assignment (Page 716)").
Reading/writing
Part programs / synchronized actions: System variables

The reading/writing of the NC I/O is performed in the NC via system variables in the interpolator
cycle. The writing on the NC I/O is performed after the interpolation cycle.
Data consistency: Interpolator cycle
See "System variables (Page 717)".
Parallel reading/writing
Reading
Parallel reading through compile cycles and part programs / synchronized actions on input data
of the same I/O range is possible. Write access to the NC I/O is performed in different ways.
● The data consistency is ensured.
● The data equality during an interpolator cycle is not ensured.
Writing
Parallel writing through compile cycles and part programs / synchronized actions on output
data of the same I/O range is not possible.
Basic functions
12.4.2 Parameter assignment
Machine data
Logical start addresses of the I/O ranges

The logical start addresses of the I/O ranges used are set via the following machine data:
● Logical start addresses of the input range 1, 2, ... m:
MD10500 $MN_DPIO_LOGIC_ADDRESS_IN[ <n>] = <logical start address> ; with <n> = 0,
1, 2, ... (m - 1)
● Logical start addresses of the output range 1, 2, ... m:
MD10510 $MN_DPIO_LOGIC_ADDRESS_OUT[ <n>] = <logical start address> ; with <n>
= 0, 1, 2, ... (m - 1)
The following must be taken into account for logical start addresses within the PLC process
image:
– Input slots: Reading from the NC also possible
– Output slots: Writing from the NC not permitted ⇒ alarm after run-up of the NC
Further information
Equipment Manual NCU 7x0.3 PN, NCU 7x0.3B PN; Technical data > PLC > Process image
size
Detailed information can be obtained under Address (http://
support.automation.siemens.com/WW/view/de/54058408)
Note
I/O ranges for the write access (MD10510) on the PROFIBUS I/O must not be in the range
of the process image, e.g. PLC 317-3, output addresses 0 - 1023.
For PROFINET I/O, these I/O ranges must be assigned in the process image to "TPA 2"; the
configuration is realized using the synchronous cycle interrupt "NC".
Lengths of the I/O ranges

The lengths of the I/O ranges used are set via the following machine data:
● Length of the input range 1, 2, ... m:
MD10501 $MN_DPIO_RANGE_LENGTH_IN[ <n> ] = <length>; with <n> = 0, 1, 2, ... (m - 1)
● Length of the output range 1, 2, ... m:
MD10511 $MN_DPIO_RANGE_LENGTH_OUT[ <n> ] = <length>; with <n> = 0, 1, 2, ... (m
- 1)
If the value 0 is entered as length, the length of the first user data slot found under the specified
start address (MD10500/MD10510) is set internally as the length of the I/O range.
Basic functions
I/O range attributes

● Attribute of the input range 1, 2, ... m:
MD10502 $MN_DPIO_RANGE_ATTRIBUTE_IN[ <n> ] ; with <n> = 0, 1, 2, ... (m - 1)
Bit Val‐ Meaning

ue
0 Format display of system variables $A_DPx_IN[<n>,<m>]
0 Little endian format
1 Big endian format
2 Reading of input data
0 Reading possible via system variables and CC-binding
1 Reading possible only for CC-binding
3 Output of slot sign-of-life alarms
0 Slot sign-of-life alarms are issued
1 Slot sign-of-life alarms are suppressed
● Attribute of the output range 1, 2, ... m:

MD10512 $MN_DPIO_RANGE_ATTRIBUTE_OUT[ <n> ] ; with <n> = 0, 1, 2, ... (m - 1)
Bit Value Meaning

0 Format display of system variables $A_DPx_OUT[<n>,<m>]
0 Little endian format
1 Big endian format
1 Writing of output data
0 Writing only via system variable
1 Writing only via CC-binding
3 Output of slot sign-of-life alarms
0 Slot sign-of-life alarms are issued
1 Slot sign-of-life alarms are suppressed
12.4.3 Reading/writing
12.4.3.1 System variables
Input data

$A_DPB_IN[<n>,] 8-bit unsigned Reads a data byte (8-bit)
$A_DPW_IN[<n>,] 16-bit unsigned Reads a data word (16-bit)
$A_DPSB_IN[<n>,] 8-bit signed Reads a data byte (8-bit)
$A_DPSW_IN[<n>,] 16-bit signed Reads a data word (16-bit)
Basic functions

$A_DPSD_IN[<n>,] 32-bit signed Reads a data double word (32-bit)
$A_DPR_IN[<n>,] 32-bit REAL Reads input data (32-bit REAL)
<n> = input range 1, 2, ... m; = byte index within the input range: 0, 1, ... (length - 1)
Output data

$A_DPB_OUT[<n>,] 8-bit unsigned Writes a data byte (8-bit)
$A_DPW_OUT[<n>,] 16-bit unsigned Writes a data word (16-bit)
$A_DPSB_OUT[<n>,] 8-bit signed Writes a data byte (8-bit)
$A_DPSW_OUT[<n>,] 16-bit signed Writes a data word (16-bit)
$A_DPSD_OUT[<n>,] 32-bit signed Writes a data double word (32-bit)
$A_DPR_OUT[<n>,] 32-bit REAL Writes output data (32-bit REAL)
<n> = output range 1, 2, ... m; = byte index within the output range: 0, 1, ... (length - 1)
Configured and parameterized I/O ranges for part programs / synchronized actions
Each system variable is a 32-bit bit array. Each bit is assigned to an I/O range.
Bit <n> ≙ machine data index <n> ≙ I/O range <n+1>
Bit <n> == 1 ⇒ The I/O range <n+1> is configured/parameterized.

$A_DP_IN_CONF 32-bit bit array Reads all configured input ranges
$A_DP_OUT_CONF 32-bit bit array Reads all configured output ranges
Valid I/O ranges for part programs / synchronized actions

Each system variable is a 32-bit bit array. Each bit is assigned to an I/O range.
Bit <n> ≙ machine data index <n> ≙ I/O range <n+1>
Bit <n> == 1 ⇒ The I/O range <n+1> is valid. Reading/writing via part programs / synchronized
actions

$A_DP_IN_VALID 32-bit bit array Reads all valid input ranges
$A_DP_OUT_VALID 32-bit bit array Reads all valid output ranges
State of an I/O range

The state of an I/O range can be read via the following system variables.

$A_DP_IN_STATE[<n>] INT Reads the state of the input range
$A_DP_OUT_STATE[<n>] Reads the state of the output range
Basic functions

<n> = index of the I/O range
State
0: I/O range has not been configured
1: I/O range could not be activated
2: I/O range is available
3: I/O range is currently not available
Length of an I/O range

The configured length of an I/O range can be read via the following system variables.

$A_DP_IN_LENGTH[<n>] Reading the length of the input data range
$A_DP_OUT_LENGTH[<n>] Reading the length of the output data range
<n> = index of the I/O range
● A preprocessing stop is triggered in the channel when reading/writing from a part program.
● To ensure data consistency during programming from the part program and the
synchronized actions, the PROFIBUS I/O data is accessed which is kept consistent for the
respective IPO cycle.
● If the same PROFIBUS I/O data is to be write-accessed several times within an interpolation
cycle (e.g. synchronized actions, access from different channels, etc.), then the data of the
last write access is valid.
● The PROFIBUS I/O data to be written is output at the PROFIBUS I/O only after the
corresponding IPO cycle.
● The (RangeOffset) indicates the place (byte offset) within the I/O range as of which the
data access is to be started. Data types can be read/written at any byte offset within the I/O
range. Read/write accesses which exceed the configured limits of the respective I/O range
are rejected with the generation of an alarm (17030).
● Via the machine data MD10502 $MN_DPIO_RANGE_ATTRIBUTE_IN or MD10512
$MN_DPIO_RANGE_ATTRIBUTE_OUT (see "Parameter assignment (Page 716)"), the
display format (little/big endian) for $A_DPx_IN[<n>,] or $A_DPx_OUT[<n>,]
system variables can be defined for the read/write direction as well as for each individual I/
O range.

Parallel writing of the NC and PLC
Parallel writing of I/O outputs by the NC via direct access and from the PLC user program
results in a random, mutual overwriting of the output values. The application is therefore not
permitted, but cannot be prevented on the control.
Basic functions
Life beat monitoring

At the start of an interpolator cycle, a check is made for each I/O range whether the sign-of-life
of the associated slot or I/O range has failed. If this is the case, alarm 9050 or 9052 is displayed.
Effects:
● The part program processing is not stopped.
● When the sign-of-life returns, the alarm is cleared automatically.
12.4.5 Examples
12.4.5.1 Writing to the NC I/O
Requirement
A valid configuration must already have been loaded to the PLC.
Parameterization for part programs / synchronized actions
Specifications
● Parameterization of the 6th data record: Machine data / system variable index = 5
● Configuration data:
– Logical start address = 334
– Slot length = 8 bytes
● Representation: Little endian format
Parameterization in the machine data

● MD10510 $MN_DPIO_LOGIC_ADDRESS_OUT[ 5 ] = 334 (logical start address)
● MD10511 $MN_DPIO_LENGTH_OUT[ 5 ] = 8 (length of the I/O-range in bytes)
● MD10512 $MN_DPIO_ATTRIBUTE_OUT[ 5 ]
– Bit0 = 0 (little endian format)
– Bit1 = 0 (writing only via system variable)
– Bit3 = 0 (issue slot sign-of-life alarms)
Examples

$A_DPB_OUT[5,6]=128 ; Byte ≙ 8 bits, index=5, offset=6
$A_DPW_OUT[5,5]='B0110' ; Word ≙ 16 bits, index=5, offset=5
; Caution: Data on offset 6 will be overwritten
$A_DPSD_OUT[5,3]=’H8F’ ; Double ≙ 32 bits, index=5, offset=3
; Caution: Data on offsets 4, 5, 6 will be overwritten
Basic functions

$AC_MARKER[0]=5 ; Index=5
$AC_MARKER[1]=3 ; Offset=3
$A_DPSD_OUT[$AC_MARKER[0],$AC_MARKER[1]]=’H8F’ ; indirect addressing
; Double ≙ 32 bits, on index=5, offset=3
R1 = $A_DPB_OUT[5,6] ; Assignment to R parameter, byte ≙ 8 bits, index=5,
offset=6
;Result: R1 == 'HFF'
ID=1 WHENEVER TRUE DO $A_DPB_OUT[5,0]=123 ; cyclic writing per IPO cycle
; Byte ≙ 8 bits, index=5, offset=0
; Faulty programming
$A_DPB_OUT[5.255]=128 ; ⇒ Alarm 17030: Offset 255 > I/O range
$A_DPB_OUT[6.10]=128 ; ⇒ Alarm 17020: Index 6 reserved for compile cycle, see
below
$A_DPB_OUT[7.10]=128 ; ⇒ Alarm 17020: Index 7 not defined in the machine data
$A_DPB_OUT[16.6]=128 ; ⇒ Alarm 17020: Index 16 outside the value range
Configuration for programming via CompileCycles
Specifications
● Representation: Little endian format

● MD10511 $MN_DPIO_LENGTH_OUT[ 6 ] = 0 (only the first user data slot is used)
– Bit1 = 1 (writing only via CC-binding)
– Bit3 = 1 (slot sign-of-life alarms are suppressed)
12.4.5.2 Reading from the NC I/O
Requirement
Basic functions
Specifications
● Parameterization of the 1st data record: Machine data / system variable index = 0
● Representation: Big endian format

● MD10500 $MN_DPIO_LOGIC_ADDRESS_IN[ 0 ] = 456 (logical start address)
● MD10501 $MN_DPIO_LENGTH_IN[ 0 ] = 32 (length of the I/O-range in bytes)
● MD1050ß2 $MN_DPIO_ATTRIBUTE_IN[ 0 ]
– Bit0 = 1 (big endian format)
– Bit2 = 0 (reading possible via system variables and CC-binding)
– Bit3 = 0 (slot sign-of-life alarms are issued)
Examples

$AC_MARKER[0]= ; Byte ≙ 8 bits, index=0, offset=0
$A_DPW_IN[0,0]
$AC_MARKER[1]= ; Signed double ≙ 32 bits, index=0, offset=1
$A_DPSD_IN[0,1]
$AC_MARKER[1]= ; Signed double ≙ 32 bits, index=0, offset=8
$A_DPSD_IN[0.8]
$AC_MARKER[2]=0 ; Index=0
$AC_MARKER[3]=8 ; Offset=8
$AC_MARKER[1]=$A_DPSD_IN[$AC_MARKER[2],$AC_MARKER[3]] ; indirect addressing
; Signed double ≙ 32 bits, index=0, offset=8
ID=2 WHEN $A_DPB_IN[0,11]>=5 DO $AC_MARKER[2]=$A_DPSD_IN[0,8]
; IF index 0, offset 11 >= 5
; THEN signed double ≙ 32 bits, index=0, offset=8
; Faulty programming
R1=$A_DPB_IN[0,255] ; ⇒ Alarm 17030: Offset 255 > I/O range
R1=$A_DPB_IN[2.6] ; ⇒ Alarm 17020: Index 2 not defined in the machine data
R1=$A_DPB_IN[1.10] ; ⇒ Alarm 17020: Index 1 reserved for compile cycle, see
below
R1=$A_DPB_IN[16.6] ; ⇒ Alarm 17020: Index 16 outside the value range
Basic functions
Parameterization for programming via CompileCycles
Specifications
● Parameterization of the 2nd data record: Machine data / system variable index = 1

● MD10500 $MN_DPIO_LOGIC_ADDRESS_IN[ 01 ] = 312 (logical start address)
● MD10501 $MN_DPIO_LENGTH_IN[ 1 ] = 32 (length of the I/O-range in bytes)
● MD10502 $MN_DPIO_ATTRIBUTE_IN[ 1 ]
– Bit0 = 1 (big endian format)
– Bit2 = 1 (reading possible only for CC-binding)
– Bit3 = 1 (suppress slot sign-of-life alarms)
12.4.5.3 Writing of the NC I/O with status query
Requirement
Specifications

● MD10511 $MN_DPIO_LENGTH_OUT[ 5 ] = 0 (length of the I/O-range in bytes)
– Bit1 = 0 (writing only via system variable)
– Bit3 = 0 (issue slot sign-of-life alarms)
Basic functions
12.5 Data lists
Examples
check: ; Jump marker

IF $A_DP_OUT_STATE[5]==2 GOTOF write ; If data range valid; => jump to
N15
GOTOB check ; Jump back to check
write: ; Jump marker
$A_DPB_OUT[5,6]=128 ; Writing the data byte

IF $A_DP_OUT_CONF==$A_DP_OUT_VALID GOTOF write ; If data range valid
; => jump to N15
SETAL(61000) ; Set alarm no. 61000

IF $A_DP_OUT_VALID B_AND ’B100000’ GOTOF write ; If data range valid
; => jump to N15
SETAL(61000) ; Set alarm no. 61000
R1=$A_DP_OUT_LENGTH[5] ; Length of the I/O-range (slot) in bytes

;Result: R1 = 32
12.5 Data lists
12.5.1 Machine data

10300 FASTIO_ANA_NUM_INPUTS Number of active analog NC inputs
10310 FASTIO_ANA_NUM_OUTPUTS Number of active analog NC outputs
10320 FASTIO_ANA_INPUT_WEIGHT Weighting factor for analog NC inputs
10330 FASTIO_ANA_OUTPUT_WEIGHT Weighting factor for analog NC outputs
10350 FASTIO_DIG_NUM_INPUTS Number of active digital NC input bytes
10360 FASTIO_DIG_NUM_OUTPUTS Number of active digital NC output bytes
Basic functions
12.5 Data lists

10362 HW_ASSIGN_ANA_FASTIN Hardware assignment of external analog NC inputs
10364 HW_ASSIGN_ANA_FASTOUT Hardware assignment of external analog NC outputs
10366 HW_ASSIGN_DIG_FASTIN Hardware assignment of external digital NC inputs
10368 HW_ASSIGN_DIG_FASTOUT Hardware assignment of external digital NC outputs
10500 DPIO_LOGIC_ADDRESS_IN Logical slot address of the PROFIBUS I/O
10501 DPIO_RANGE_LENGTH_IN Length of the PROFIBUS I/O range
10502 DPIO_RANGE_ATTRIBUTE_IN Attributes of the PROFIBUS I/O
10510 DPIO_LOGIC_ADDRESS_OUT Logical slot address of the PROFIBUS I/O
10511 DPIO_RANGE_LENGTH_OUT Length of the PROFIBUS I/O range
10512 DPIO_RANGE_ATTRIBUTE_OUT Attributes of the PROFIBUS I/O
10530 COMPAR_ASSIGN_ANA_INPUT_1 Hardware assignment of NC analog inputs for comparator byte 1
10531 COMPAR_ASSIGN_ANA_INPUT_2 Hardware assignment of NC analog inputs for comparator byte 2
10540 COMPAR_TYPE_1 Parameterization for comparator byte 1
10541 COMPAR_TYPE_2 Parameterization for comparator byte 2

21220 MULTFEED_ASSIGN_FASTIN Assignment of input bytes of NC I/Os for "multiple fee‐
drates in one block"
12.5.2 Setting data
12.5.2.1 General setting data
Number Identifier: $SN_ Description

41600 COMPAR_THRESHOLD_1 Threshold values for comparator byte 1
41601 COMPAR_THRESHOLD_2 Threshold values for comparator byte 2
12.5.3 System variable
$A_IN Digital NC input
$A_OUT Digital NC output
$A_INA Analog NC input
$A_OUTA Analog NC output
$A_DPB_IN Reads a data byte (8 bit)
Basic functions
12.5 Data lists
$A_DPW_IN Reads a data word (16 bit)
$A_DPSB_IN Reads a data byte (8 bit)
$A_DPSW_IN Reads a data word (16 bit)
$A_DPSD_IN Reads a double word (32 bit)
$A_DPR_IN Reads input data (32 bit REAL)
$A_DPB_OUT Writes a data byte (8 bit)
$A_DPW_OUT Writes a data word (16 bit)
$A_DPSB_OUT Writes a data byte (8 bit)
$A_DPSW_OUT Writes a data word (16 bit)
$A_DPSD_OUT Writes a double word (32 bit)
$A_DP_IN_VALID Reads all valid input ranges
$A_DP_OUT_VALID Reads all valid output ranges
$A_DP_IN_STATE[<n>] Reads the state of the input range
$A_DP_OUT_STATE[<n>] Reads the state of the output range
$A_DP_IN_LENGTH[<n>] Reads the length of the input data range
$A_DP_OUT_LENGTH[<n>] Reads the length of the output data range
12.5.4 Signals
12.5.4.1 Signals to NC
Signal name SINUMERIK 840D sl SINUMERIK 828D

Disable of the digital NC inputs DB10.DBB0/122/124/126/128 DB2800.DBB0/1000
Setting of the digital NC inputs from the PLC DB10.DBB1/123/125/127/129 DB2800.DBB1/1001
Disable of the digital NC outputs DB10.DBB4/130/134/138/142 DB2800.DBB4/1008
Overwrite mask of the digital NC outputs DB10.DBB5/131/135/139/143 DB2800.DBB5/1009
Setting value of the digital NC outputs from the PLC DB10.DBB6/132/136/140/144 DB2800.DBB6/1010
Input mask of the digital NC outputs DB10.DBB7/133/137/141/145 DB2800.DBB7/1011
Disable of analog NC inputs DB10.DBB146 -
Input mask for analog NC inputs DB10.DBB147 -
Setting value from PLC for the analog NC inputs DB10.DBB148-163 -
Overwrite mask for the analog NC outputs DB10.DBB166 -
Input mask for analog NC outputs DB10.DBB167 -
Disable of NC outputs DB10.DBB168 -
Setting value from PLC for the analog NC outputs DB10.DBB170-185 -
Basic functions
12.5 Data lists
12.5.4.2 Signals from NC

Actual value for digital NCK inputs DB10.DBB60/186-189 DB2900.DBB0/1000
Setpoint for digital NCK outputs DB10.DBB64/190-193 DB2900.DBB4/1004
Actual value for analog NCK inputs DB10.DBB194-209 -
Setpoint for analog NCK outputs DB10.DBB210-225 -
Basic functions
12.5 Data lists
Basic functions
Distributed systems 13
13.1.1 Several operator panels on several NCUs (T:M:N)

Under certain circumstances, a single operator control and monitoring station may not be
sufficient for complex plants and machines. Therefore, several operator control and monitoring
stations in a SINUMERIK system network (Ethernet) can be connected to several numerical
controls (NCU) via a PCU in such a way that they enable flexible and distributed operation and
monitoring of the entire system.
The following figure provides an overview of the components that currently can be connected
in a system network to form an operator control and monitoring system T:1:N. Meanings:
● T: Thin Client Unit (TCU) or handheld unit HT8/HT10 (connected with the PCU)
● M: Man Machine Control (MMC), e.g. PCU 50.x with SINUMERIK Operate
● N: Numeric Control Unit (NCU), e.g. NCU 7x0.3 PN
2SHUDWRUSDQHOIURQW23[[[ 2SHUDWRUSDQHOIURQW23[[[ +DQGKHOGXQLW

ZLWK ZLWK +7
7KLQ&OLHQW8QLW7&8 7KLQ&OLHQW8QLW7&8
0DFKLQHFRQWUROSDQHO 0DFKLQHFRQWURO
0&3[[[ SDQHO
,QGXVWULDO(WKHUQHW 0&3[[[
3&XQLW3&8[
,(6ZLWFK ZLWK
6&$/$1&([[[ 8VHULQWHUIDFH
6,180(5,.2SHUDWH
6,180(5,.' 6,180(5,.' 6,180(5,.' 6,180(5,.'

VO VO VO VO
1&8[31 1&8[31 1&8[31 1&8[31
Basic functions
Distributed systems
Figure 13-1 Example of a T:1:N network
T: Thin Client Unit (TCU) or HT8 handheld unit

The graphic information of the PCU user interface is transferred via the TCU to the operator
panel front (OP) and displayed there. TCU and operator panel front together form an operator
station.
● Maximum number
In principle, any number of operator stations, only limited by the amount of available address
space, can be operated in the system network.
● Online
A maximum of four operator stations per PCU can be online simultaneously.
● Operating focus
At any one time, only one of the operator stations on the PCU that are online, can have the
operating focus. Entries with regard to the user interface can only be made via this operator
station. The user interfaces on the other online operator stations are darkened to indicate
that they do not have operating focus. Only a message is displayed on operator stations that
are not online.
The operating focus can be switched between the online operator stations.
● HT8 handheld unit
A HT8 handheld unit combines a TCU, an operator panel front and a machine control panel
in a single device.
M: PCU/IPC with SINUMERIK Operate

Several operator stations and several NCUs can be connected to a PCU with SINUMERIK
Operate user interface. The data of the channels of different NCUs can be displayed on the
operator stations through suitable configuring of the channel menu.
N: SINUMERIK 840D sl
● Internal SINUMERIK Operate user interface
Because of the existing external SINUMERIK Operate user interface on the PCU in the
system network, the NCU-integrated internal SINUMERIK Operate user interface must be
switched off. The internal SINUMERIK Operate user interface must not be switched off only
when it is used with a limited range of functions, exclusively within the scope of tool
management. Detailed information on this can be found in the Commissioning Manual
"Operator Components and Networking (IM5)", Section "Network configuration" >
"Application example"
● Machine control panel (MCP)
For a flexible switchover of the machine control panels, only one MCP can be connected to
one NCU. The switchover of the MCPs is user-specifically via the PLC user program
(function block FB 9).
Basic functions
Distributed systems
Installation and connection
Further information
● TCU, MCP, PCU:
SINUMERIK 840D sl Operator Components and Networking Manual
● NCU:
Equipment Manual SINUMERIK Control
● Machine control panel (MCP)
FB 9: MtoN Control Unit Switchover
● Switch SCALANCE:
System Manual Communication with SIMATIC
● Industry PCs compatible with PCU-Basesoftware
Commissioning Manual SINUMERIK 840D sl PCU-Basesoftware
Configuration, commissioning and parameter assignment
Further information
● Structure of the system network and commissioning of a TCU:
Operator Components and Networking Commissioning Manual (IM5)
● Configuration of the channel menu
SINUMERIK Operate Commissioning Manual (IM9), Section "Channel menu"
Programming
You can find further information in the PLC Function Manual.
Constraints
Currently, only one PCU (M) can be configured for each T:M:N network ⇒ T:1:N
13.1.2 NCU link
13.1.2.1 Link communication

The NCU-link communication allows an interpolator clock-synchronous cross-NCU data
exchange for the following applications:
● Cross-NCU data exchange via link variables $A_DLx
● Cross-NCU traversing of axes and spindles using link axes and container link axes
● Cross-NCU master value coupling of axes and spindles using lead link axes
Basic functions
Distributed systems
Safety Integrated
If axis-specific Safety Integrated Functions are active for a link axis, data that is not safety-
related is exchanged between the local safety axis (link axis on NCUx) and the channel that is
traversing it (NCUy) via the NCU link. This also enables Safety Integrated-supporting functions
for link axes, such as velocity/speed monitoring-dependent setpoint limiting and higher-order
stop functions (STOP D/E).
Link module
The link communication requires optional link modules. A link module is an optional PROFINET
module for isochronous real-time communication (IRT) via Ethernet. The link module occupies
the option slot of the NCU.
Quantity structure
As standard, a maximum of three NCUs can be interconnected to form a link group.
Note
For a specific project, on request to your local regional Siemens representative, further NCUs
can be integrated to form a link group.
13.1.2.2 Link variables

Link variables are global system user variables that for configured link communication can be
used by all NCUs of the network. Link variables can read and written in part programs, cycles
and synchronized actions.
The reading and writing of link variables is performed in the main run. A channel
synchronization is therefore performed implicitly with regard to the link variables so that all
channels read the same value in the same interpolator cycle. By comparison, global user data
(GUD) can also be used cross-channel like the link variables. However, as GUD variables are
preprocessed, no implicit channel synchronization is performed here. If necessary, GUD
variables must therefore be synchronized by the user through specific programming.
Note
On systems without an NCU link, link variables can also be used as additional NCU global user
data alongside standard global user data (GUD).
13.1.2.3 Link axes

Link axes enable the creation of distributed control systems, in which the setpoints of the
machine axes are not created by channels of the NCU to which the machine axes are physically
connected, but by channels of an arbitrary NCU of the link group.
Basic functions
Distributed systems
Fixed assignment for link axes

The assignment, on which NCU the setpoints for which machine axis are created, is fixed for
link axes through the machine data configuration.
Variable assignment for container link axes

The assignment, on which NCU the setpoints for which machine axis are created, is variable for
container link axes. A container link axis can therefore be traversed alternatively by each NCU
of the link group. See Section "Axis container (Page 757)".
Irrespective of the assignment described above, the logical machine axis can be made known
to the link axis of several channels on the NCU generating the setpoint and then functionally
handled as a local logical machine axis, e.g. master value for position/feed couplings, NCU-
local axis interchange.
13.1.2.4 Lead link axes

If in conjunction with the coupling functions of the generic coupling, all interpolators, i.e. the
setpoint-creating/processing channels, the leading and following axes/spindles, are on the
same NCU, the use of a lead link axis is not required. The machine axes of the leading and/or
following axes/spindles can also be connected link axes to different NCUs.
Application
A lead link axis is always required when not all interpolators of a coupling group are on the same
NCU. The lead link axis provides an image of the leading axis/spindle or the master value for
the local interpolators, on another NCU. Starting from this master value, the setpoints of the
following axes/spindles are then generated by the interpolators on this NCU.
Further application
A lead link axis is also used if more machine axes are involved in a coupling than are available
absolutely or relatively on an NCU for the coupling.
Further information
Function Manual Axes and Spindles, Axis couplings
13.1.2.5 Dependencies
In order that several axes can be traversed in an interpolatary relationship, it is essential that
the setpoints generated by the interpolator of the traversing channel be transferred to the
position control at the same time.
During the transfer of the setpoints via the NCU link, for example, for a link axis there is a delay
of one interpolator cycle in relation to the setpoint of a local axis. The delay must be
compensated by a suitable increase of the buffer between the interpolator and the position
controller :
Basic functions
Distributed systems
MD18720 $MN_MM_SERVO_FIFO_SIZE = <value> = <default value + compensation value>
Function Compensation value

Link axis One interpolator cycle must be compensated on all NCUs with axes that in‐
Container-link axis terpolate with a link or container link axis.
Compensation value = 1
Lead-link axis Two interpolator cycles must be compensated on the NCU of the leading axis
that generates the setpoints for the lead link axis.
Compensation value = 2
Note
In contrast to lead link axes, link and container link axes require another compensation value
(MD18720 $MN_MM_SERVO_FIFO_SIZE). With simultaneous use of link or container link
axes and lead link axes within a link group, the delays cannot be compensated.
13.1.2.6 Application example: Rotary indexing machine

On the basis of rotary cycle machine with two NCUs, the application of the "NCU Link" function
is shown as example. The principal units of the rotary indexing machine are:
● MTR rotary axis for the rotary table
● MS1 - MS4 spindles
● Machining stations 1 and 2, each with the X1 and Z1 linear axes
● Loading and unloading station
All of the machine axes remain permanently assigned to their particular NCU. The same axes
(X and Z) and spindles (S1) are always addressed in the machining program of the relevant
NCU.
The workpiece status is represented schematically after each machining step.
For each machining step, the rotary table (MTR) advances one position counter-clockwise.
This so assigns the spindles to another station for each machining step. The changing
relationships of the spindles defined in the channels to the machine axes are represented as an
axis container in the NCU.
If the machine axis of a spindle is not contained on its own NCU, the spindle setpoints are
transferred by link communication to the associated NCU and output there at the machine axis.
Basic functions
Distributed systems
1&8/LQNYLD352),1(7
1&8 6HWSRLQWWUDQVIHULVQRWFXUUHQWO\UHTXLUHG 1&8
/LQNPRGXOH /LQNPRGXOH
1&8 6SLQGOH06 1&8

6SLQGOH06
5RWDU\WDEOH
'ULYH 075 'ULYH
8QORDGLQJVWDWLRQ
/RDGLQJVWDWLRQ
6SLQGOH06
=
6SLQGOH06
;
=
0DFKLQLQJVWDWLRQ
;
0DFKLQLQJVWDWLRQ
Figure 13-2 Fig. 1: Initial situation
1&8/LQNYLD352),1(7
1&8 6HWSRLQWWUDQVIHU1&8!1&8VSLQGOH06 1&8
6SLQGOH06
1&8 6SLQGOH06 1&8
5RWDU\D[LV075
'ULYH 'ULYH
/RDGLQJVWDWLRQ 8QORDGLQJVWDWLRQ
6SLQGOH06
=
6SLQGOH06
= ;
0DFKLQLQJVWDWLRQ
;
0DFKLQLQJVWDWLRQ
Figure 13-3 Fig. 2: Location after rotation by one position
Basic functions
Distributed systems
13.2 NCU link
Parameterization (schematic)
General
Programmed channel axes in the part programs of both NCUs: X, Z, S1
NCU1 Machine axes defined in the NCU:
Local: X1, Z1
Axis container: MS1, MS2
NCU2 Machine axes defined in the NCU:
Local: X1, Z1
Axis container: MS3, MS4
Initial setting Rotation of the MTR (rotary table) rotary axis

(Fig. 1) by one position
(Fig. 2)
NCU1 Machining station 1: X1, Z1, MS2
Diagram showing the channel axes programmed in the part program:
X → X1 and Z → Z1 X → X1 and Z → Z1
S1 → MS2 S1 → MS1
NCU2 Machining station 2: X1, Z1, MS2
Diagram showing the channel axes programmed in the part program:
X → X1 and Z → Z1 X → X1 and Z → Z1
S1 → MS3 S1 → MS2 (link axis)
13.2 NCU link
13.2.1 Link communication
'DWDH[FKDQJHE\1&8/LQNYLD352),1(7
1&8 1&8 1&8Q

1&8 1&8 1&8
/LQNPRGXOH /LQNPRGXOH /LQNPRGXOH
Figure 13-4 Link communication (principle)
Basic functions
Distributed systems
13.2 NCU link
The NCU-link communication cycle allows an interpolator clock-synchronous cross-NCU data

exchange for the following applications:
● Cross-NCU link variables $A_DLx
All the NCUs involved with the NCU-link communication have a common view of the link
variables because they are exchanged via the NCU link interpolator cycle clock-
synchronous between the NCU of the link group.
● Cross-NCU traversing of axes and spindles using link axes and container-link axes
If single or interpolation axis traversal is made from a channel of an NCU, NCU-link setpoints
can also be transferred to axes physically connected to another NCU of the link group.
These axes are designated as link axes.
● Cross-NCU master value coupling of axes and spindles using lead-link axes
NCU1 traverses axis X1 (leading axis), the setpoints are transferred to a link axis of NCU2
(lead-link axis) via the NCU link. Coupling of axis X2 is realized in NCU2 on this lead-link
axis. This means axis X2 is indirectly the following axis of X1.
Data transfer
Depending on the active functions, the following cyclic and non-cyclical data transmissions
occur between the NCUs involved with the link communication:
● High-priority, cyclic data transfer:
– Setpoints, actual values and status signals of the axes
– NCU status signals
● High-priority, non-cyclic, non-displaceable data transfer:
– Non-safety-related data as part of the Safety Integrated function
– States of the container axes during an axis container rotation
● Low-priority, non-cyclic, displaceable data transfer (listed in order of decreasing priority):
– Link variables
– Warm restart requirements
– Activation of axis container rotations
– Changes in NCU-global machine and setting data
– Activation of the axial machine data for link axes
– Alarms
Displacement
If for low-priority, non-cyclic, displaceable data transmission not all requirements can be sent
in a single interpolator cycle, the request with higher priority displaces that with a lower priority.
The requirements with lower priority are then sent at a later point in time.
Basic functions
Distributed systems
13.2 NCU link
Quantity structure: NCU 7x0.3 PN

As standard, a maximum of three NCUs can be interconnected to form a link group.
Note
For a specific project, on request to your local regional Siemens representative an NCU-link
group with more than three NCUs is possible. Without project-specific supplements, more than
three NCUs are rejected with Alarm 380020.
NCU link and Safety Integrated

The following figure shows a constellation with two NCUs and two machine axes, of which the
MA2 machine axis of the NCU2 is traversed as link axis for NCU1. The Safety Integrated
function monitors the safety-related aspects of both axes.
1&8/LQNYLD352),1(7
6DIHW\,QWHJUDWHG
(WKHUQHW352),1(7
1&8 1&8
352),%86
1&. 1&.
&KDQQHO
1*)
1;=
&KDQQHOD[HV
; =
0'
1&B$;
$;
$;
/RJ0DFKLQHD[LVLPDJH
$;
0'
0DFKLQHD[HV
0'
0$
0$
&RQWURO8QLW &RQWURO8QLW
;
0RWLRQ 0RWLRQ
0RQLWRU 0RQLWRU
00 60 60 00
63/ 63/
3/& 3/&
; ; ;
;
3 3 3
0 0
)6HQG)5HFY
1&8ORFDOD[LV 31 /LQND[LV
31
352),VDIH 352),VDIH
)B', )B'2 ', '2 ', '2 )B', )B'2
Figure 13-5 NCU link and Safety Integrated
The safety-related input signals (F_DI) of both NCUs can be acquired, linked via the safe
programmable logic (SPL) and exchanged using the safety-related CPU-CPU communication
(FSend/FRecv).
Basic functions
Distributed systems
13.2 NCU link
As part of the Safety Integrated function, the NCU-link communication permits the single-
channel non-safety-related transfer of link axis data for Safety Integrated-supporting functions.
Examples:
● Interpolatory braking for an implicit Stop D of all traversing axes, including the link axes, in
the channel.
● Reduce the speed of all axes traversing in the channel, including link axes, for a change of
the safe speed.
Safety Integrated acceptance test and NCU link

The Acceptance Test wizard (ATW) is generally used to perform the acceptance test
separately for each NCU. Only alarms on the home NCU of the axis are displayed for link axes.
To make the ATW also check alarms for link axes, the ATW must be told the safety-relevant
NCU connected via the NCU link. For this purpose, these must be entered in the
NETNAMES.INI file on the PG/PCU on which the ATW runs.
Example: Entries in the NETNAMES.INI file for NCU link with two safety-relevant NCUs
Adapt file: NETNAMES.INI (excerpt)

[own]
owner = HMI_1
[conn HMI_1]
conn_1= NCU_1
conn_2= NCU_2
[param HMI_1]
mmc_address = 1
[param network]
[param NCU_1]
nck_address= 192.168.214.2,LINE=10,NAME=/NC,SAP=030d,PROFILE=CLT1__CP_L4_INT
plc_address= 192.168.214.2,LINE=10,NAME=/PLC,SAP=0201,PROFILE=CLT1__CP_L4_INT
ADDRESS2= 192.168.214.2,LINE=10,NAME=/CP,SAP=0501,PROFILE=CLT2__CP_L4_INT
ADDRESS10= 192.168.214.2,LINE=10,NAME=/
DRIVE_00_000,SAP=0201,SUBNET=0000-00000000:000,PROFILE=CLT2__CP_L4_INT
ADDRESS11= 192.168.214.2,LINE=10,NAME=/DRIVE_03_003,SAP=0900,PROFILE=CLT2__CP_L4_INT
ADDRESS12= 192.168.214.2,LINE=10,NAME=/DRIVE_03_011,SAP=0B00,PROFILE=CLT2__CP_L4_INT
ADDRESS13= 192.168.214.2,LINE=10,NAME=/DRIVE_03_012,SAP=0C00,PROFILE=CLT2__CP_L4_INT
ADDRESS14= 192.168.214.2,LINE=10,NAME=/DRIVE_03_013,SAP=0D00,PROFILE=CLT2__CP_L4_INT
ADDRESS15= 192.168.214.2,LINE=10,NAME=/DRIVE_03_014,SAP=0E00,PROFILE=CLT2__CP_L4_INT
ADDRESS16= 192.168.214.2,LINE=10,NAME=/DRIVE_03_015,SAP=0F00,PROFILE=CLT2__CP_L4_INT
name=Machine_1
[param NCU_2]
nck_address= 192.168.214.1,LINE=10,NAME=/NC,SAP=030d,PROFILE=CLT1__CP_L4_INT
plc_address= 192.168.214.1,LINE=10,NAME=/PLC,SAP=0201,PROFILE=CLT1__CP_L4_INT
ADDRESS2= 192.168.214.1,LINE=10,NAME=/CP,SAP=0501,PROFILE=CLT2__CP_L4_INT
ADDRESS10= 192.168.214.1,LINE=10,NAME=/
DRIVE_00_000,SAP=0201,SUBNET=0000-00000000:000,PROFILE=CLT2__CP_L4_INT
ADDRESS11= 192.168.214.1,LINE=10,NAME=/DRIVE_03_003,SAP=0900,PROFILE=CLT2__CP_L4_INT
ADDRESS12= 192.168.214.1,LINE=10,NAME=/DRIVE_03_011,SAP=0B00,PROFILE=CLT2__CP_L4_INT
ADDRESS13= 192.168.214.1,LINE=10,NAME=/DRIVE_03_012,SAP=0C00,PROFILE=CLT2__CP_L4_INT
ADDRESS14= 192.168.214.1,LINE=10,NAME=/DRIVE_03_013,SAP=0D00,PROFILE=CLT2__CP_L4_INT
ADDRESS15= 192.168.214.1,LINE=10,NAME=/DRIVE_03_014,SAP=0E00,PROFILE=CLT2__CP_L4_INT
ADDRESS16= 192.168.214.1,LINE=10,NAME=/DRIVE_03_015,SAP=0F00,PROFILE=CLT2__CP_L4_INT
name=Machine_2
Basic functions
Distributed systems
13.2 NCU link
Further information
The "Safety Integrated" function is described in detail in:
SINAMICS S120 Safety Integrated Function Manual
13.2.1.2 Link module

The NCU-link communication takes place via link modules A link module is an optional
PROFINET module for isochronous real-time communication (IRT) via Ethernet. The link
module can be used only for the NCU-link communication. It is not possible to use a link module
for general PROFINET communication.
The option slot is required on the NCU module for the link module.
Note
There is only one option slot on the NCU module. This prevents the parallel use of an NCU-link
module and other optional modules.
Link module and NCU modules

The Communication Board Ethernet CBE30-2 is available as link module for the "NCU710.3
PN", "NCU720.3 PN" and "NCU730.3 PN" NCU modules. The option slot is required on the
NCU module for the link module.
Further information
Equipment Manual NCU7x0.3 PN; Connectable components > CBE30-2
13.2.1.3 Parameter assignment: NC system cycles

As basic requirement for link communication, the following system cycle clocks must be set the
same in all NCUs involved in the NCU group:
● Basic system cycle clock
● Position control cycle clock
● Interpolator cycle
Basic system cycle clock

The DP cycle set for isochronous communication in the STEP 7 project is used as basic system
cycle clock. The current basic system cycle clock is displayed in machine data:
Basic functions
Distributed systems
13.2 NCU link
MD10050 $MN_SYSCLOCK_CYCLE_TIME
Note
Manual alignment across several communications buses
If several isochronous communication buses (PROFIBUS 1 ... n, PROFINET 1 ... m) have been
configured on an NCU, the same DP cycle time in STEP 7 HW Config must be set for each
communication bus.
Depending on the position control cycle clock
For the SINUMERIK 840D sl, the ratio between the basic system cycle clock and the position
control cycle clocks is fixed (1:1) and cannot be changed. Because only certain position control
cycle clocks can be set for the NCU link, only these position control cycle clocks can be set as
the basic system cycle clock or DP cycle time. See the next paragraph "Position control cycle
clock".
Position control cycle clock

The position control cycle clock is set as a ratio to the basic system cycle clock. For the
SINUMERIK 840D sl, the ratio is fixed (1:1) and cannot be changed. The current position
control cycle clock is displayed in the machine data:
MD10061 $MN_POSCTRL_CYCLE_TIME
Note
Permitted position control cycle clocks
For the NCU link, depending on the number of NCUs in the link group, only the following
position control cycle clocks [ms] are set:
● 2 NCU: 2.0, 2.5, 3.0, 3.5, 4.0
● 3 NCU: 3.0, 3.5, 4.0
See Section "Configuration (Page 743)".
Interpolator cycle
The interpolator cycle clock is set as a ratio of the basic system cycle clock. The setting is made
via the following machine data:
MD10070 $MN_IPO_SYSCLOCK_TIME_RATIO
The actual interpolator cycle clock is displayed in machine data:
MD10071 $MN_IPO_CYCLE_TIME
Basic functions
Distributed systems
13.2 NCU link
Notes on setting
Cycle clock settings

It is recommended that the following settings are made:
● The default 90% setting for the CPU time share of the NC should be retained:
MD10185 $MN_NCK_PCOS_TIME_RATIO
● The system cycle clocks must be set so that the average system utilization caused by the
interpolator and the position controller does not exceed 60% in normal program operation.
As maximum value, 90% should be not be exceeded.
Note:
In special circumstances, maximum values > 100% can be displayed.
Lowest cyclic communication load

The lowest cyclic communication load during the Link communication results for a cycle ratio
of interpolator clock to position controller clock cycle of 1: 1. With activated "Dynamic Servo
Control (DSC)" drive function, this is generally the most effective setting.
Disadvantage: No telegram repetitions are possible for the link communication.
Time frame of the NC/PLC interface update

The following setting is active during the run-up of all NCUs involved in the link group:
MD18000 $MN_VDI_UPDATE_IN_ONE_IPO_CYCLE = 1
This causes the NC/PLC interface to be read and written completely in just one interpolation
cycle.
System utilization
The system utilization is displayed on the SINUMERIK Operate user interface, under:
"Diagnostics" operating area > "ETC key (">") > "System utilization"
Interpolator clock cycle and link variables

When parameterizing the system clock cycles, in addition to the maximum system utilization
values in the "worst-case" scenario, the expected maximum CPU time loading at the
interpolator level as a result of transferring link variables in productive operation must be taken
into account.
WARNING
Open-loop control failure due to CPU time overflow at the interpolator level
If, when parameterizing the NC, the interpolator clock cycle was set to short, then as a result
of the additional CPU time load due to transferring link variables, in productive operation CPU
time overflow can occur at the interpolator level.
Further information: Diagnostics Manual; NC Alarms > Alarm 4240 level overflow at the IPO
or position controller level.
Basic functions
Distributed systems
13.2 NCU link
13.2.1.4 Parameter assignment: Link communication
Number Identifier $MN_ Meaning

MD12510 NCU_LINKNO Unique numerical identification of the NCU within the link group. The
identifiers must be assigned without any gaps in ascending ordering
starting from 1.
Value range: 1, 2, ... Maximum NCU number
Note:
The NCU to which the value 1 is assigned as NCU identification is
the master NCU of the link group. The parameterization of link axes and
axis containers may only be made with the machine and setting data of
the master NCU.
MD18780 MM_NCU_LINK_MASK.Bit 0 Activation of the link communication
MD18781 NCU_LINK_CONNECTIONS Number of internal link connections
Note:
It is recommended to retain the default value 0 (determination of the
number by the NC).
MD18782 MM_LINK_NUM_OF_MODULES Number of NCUs to be connected with one another via NCU link.
13.2.1.5 Configuration
The NC system software supplies specific configurations for each supported combination of
NCU number and position controller cycle of a link group (see section "Parameter assignment:
NC system cycles (Page 740)").
During the system startup, the appropriate configuration will be loaded (as specified by the
values parameterized in the machine data):
● MD18782 $MN_MM_LINK_NUM_OF_MODULES (number of NCUs of the line group))
● MD10061 $MN_POSCTRL_CYCLE_TIME (position controller cycle)
Note
For applications, in which the standard configurations that have been supplied cannot be used,
please contact your local Siemens sales person.
13.2.1.6 Wiring the NCUs

The numerical sequence of the NCUs within a link group is defined in the NCUs using the
MD12510 $MN_NCU_LINKNO = <NCU number>, with NCU number = 1 ... max. NCU number
Cabling
Starting from the NCU1, the NCU link modules should be wired up in the NCU number
sequence according to the following schematic: NCU(n), Port 0 → NCU(n+1), Port 1
Basic functions
Distributed systems
13.2 NCU link
1&8/LQNYLD352),1(7 1&8/LQNYLD352),1(7
3RUW
3RUW
3RUW
3RUW
3RUW
3RUW
3RUW
3RUW
3RUW
3RUW
3RUW
3RUW
1&8 1&8 1&8
/LQNPRGXOH /LQNPRGXOH /LQNPRGXOH
1&8 1&8 1&8Q
Figure 13-6 Wiring schematic, NCU link
13.2.1.7 Activation
The link communication is activated using the following machine data:
MD18780 $MN_ MM_NCU_LINK_MASK, Bit 0 = 1
Note
Activation time
It is recommended to activate the link communication only after complete commissioning of the
entire functionality on all participating NCUs has been done.
13.2.2 Link variables
Complex systems with several NCUs require for the complete system coordination of the
manufacturing processes a cyclic exchange of user-specific data between the NCUs. The data
exchange is performed via the link communication and a special memory area, the link
variables memory available for each NCU.
The size and data structure of the link variables memory can be specified for each specific user.
The data stored in the link variables memory is addressed using a special $A_DLx link
variables.
Link variables are therefore system-global user variables that can be read and written in part
programs and cycles by all NCUs involved in a link group if link communication has been
configured. Unlike global user variables (GUD), link variables can also be used in synchronized
actions.
Basic functions
Distributed systems
13.2 NCU link
1&8/LQNYLD352),1(7
1&8 1&8 1&8 1&8

&KDQQHO /LQNYDULDEOH /LQNYDULDEOH

PHPRU\ PHPRU\
1$B'/[>@
Figure 13-7 Link variables
Link variabls as NCU-global user variables
Note
If an NCU Is not a node of a link group or the link variables are not required for communication
via NCU link, the link variables can be used as the NCU-global user variables.
13.2.2.1 Properties of the link variables memory
Parameterizing the memory size

The size of the link variables memory in bytes is set with the following machine data:
MD18700 $MN_MM_SIZEOF_LINKVAR_DATA (size of the link variables memory)
The setting for the size of the link variables memory should be identical for all NCUs involved
in the link group. If the memory sizes are different, the largest value assigned is used.
Initialization
After an NCU is powered up, the link variables memory is initialized with 0.
Structure
From the point of view of the system, the link variables memory is an unstructured memory area
that is available for link communication purposes. The link variables memory is structured by
the user/machine manufacturer alone. Depending on how the data structure is defined, the link
variables memory is accessed by means of data format-specific link variables.
System-wide alignment
Once a link variables memory has been written to, the changes that have been made to the data
are transferred to the link variables memories of all other NCUs involved in the link group. The
link variables memories are usually updated by means of link communication within two
interpolation cycles.
Basic functions
Distributed systems
13.2 NCU link
13.2.2.2 Properties of the link variables

The link variables memory is accessed via the following data format-specific link variables:
Data type 1) Designation Data format 2) Bytes 2) Index i 3) Value range

UINT $A_DLB[ i ] BYTE 1 i=n*1 0 ... 255
INT $A_DLW[ i ] WORD 2 i=n*2 -32768 ... 32767
INT $A_DLD[ i ] DWORD 4 i=n*4 -2147483648 ... 2147483647
REAL $A_DLR[ i ] REAL 8 i=n*8 ±(2,2*10-308 … 1,8*10+308)
1) Data type of link variables when used in part program/cycle
2) Data format of link variables or number of bytes addressed by the link variables in the link variables memory
3) The following must be noted for index i:
● Index i is a byte index that relates to the beginning of the link variables memory.
● The index must be selected so that the bytes addressed in the link variables memory are located on a data format limit ⇒
index i = n * bytes, where n = 0, 1, 2, etc.
– $A_DLB[i]: i = 0, 1, 2, ...
– $A_DLW[i]: i = 0, 2, 4, ...
– $A_DLD[i]: i = 0, 4, 8, ...
– $A_DLR[i]: i = 0, 8, 16, ...
Write
A link variable is written with main-run synchronism.
Read
A preprocessing stop is initiated when a link variable is read.
Checks
The following checks are performed for the link variables and link variables memory:
● Observance of the value range limits
● Access to format limit
● Observance of defined memory area in link variables memory
The user/machine manufacturer is solely responsible for preventing the following errors:
● Accessing with incorrect data format
● Accessing the wrong address (index i)
● Reciprocal overwriting of the same data item by multiple channels of a single NCU or
different NCUs
● Reading a data item before it has been updated by a channel of its own NCU or of a different
NCU
Note
Data consistency
The user/machine manufacturer is solely responsible for ensuring data consistency within
the link variables memory, both on a local-NCU basis and across NCUs.
Basic functions
Distributed systems
13.2 NCU link
13.2.2.3 Write elements

In the case of write access to the link variables memory (e.g. $A_DLB[4] = 21), what is known
as a link variables write element is required for managing the write process within the system.
The maximum number of write elements that are available for each interpolation cycle is set by
means of the following machine data:
MD28160 $MC_MM_NUM_LINKVAR_ELEMENTS
The maximum number of write elements thus restricts the number of link variables that can be
written during each interpolation cycle.
13.2.2.4 Dynamic response during write

The link variables are written with main-run synchronism. The new value may be read by the
other channels in its own NCU no later than the next interpolation cycle. It can be read in the
next part program block in its own channel.
The channels of the other NCUs in the link group normally see the new value after two
interpolation cycles. However, the limited bandwidth can lead to delays in transferring write
requests to the other NCUs in the link group (message delays). Causes for a message delay
can be:
● Writing a large number of link variables in an interpolation cycle
● Writing link variables and a the request for an axis container rotation in the same interpolator
cycle
● Writing link variables and transferring an alarm in the same interpolation cycle
NC-specific system variable
Identifier Meaning
$AN_LINK_TRANS_RATE_LAST The number of write requests that were still free in
the last interpolator cycle.
$AN_LINK_TRANS_RATE_LAST_SUM[<n>] The number of write requests that were still free in
the last interpolator cycle in the send direction to
the specified NC <n> (NCU number).
$AN_LINK_CONN_SIZE_LINKVAR The number of bytes to be transferred for a write
request of a link variable.
$AN_LINK_CONN_SND[<n>] The maximum number of bytes that can be trans‐
ferred per interpolator cycle from the current NCU
to the specified NCU.
$AN_LINK_CONN_RCV[<n>] The maximum number of bytes that can be trans‐
ferred per interpolator cycle from the specified
NCU to the current NCU.
<n>: NCU number according to MD12510 $MN_NCU_LINKNO of the relevant NCU
Basic functions
Distributed systems
13.2 NCU link
Note for: $AN_LINK_CONN_SIZE_LINKVAR

The writing of a link variable causes the number of bytes specified in
$AN_LINK_CONN_SIZE_LINKVAR to be transferred via the not-cyclic link communication.
The number is independent of the format of the link variables.
The maximum number of write requests that can be transferred to the specified NCU for each
interpolator cycle is calculated as:
Max. number of write requests = $AN_LINK_CONN_SND[<n>] /
$AN_LINK_CONN_SIZE_LINKVAR
Channelspecific system variable
Identifier Meaning
$A_LINK_TRANS_RATE 1)
Number of write requests that still can be transfer‐
red in the current interpolator cycle.
1) Application example, refer to Section: "Synchronization of a write request (Page 748)"
13.2.2.6 Synchronization of a write request

If certain applications require the new value of a link variable to be transferred to the other
NCUs in the link group in precisely two interpolation cycles, writing to the link variable must be
made in a synchronized action. In the synchronized action, writing to the link variable is only
executed if in the actual interpolator cycle, the write request can still be executed. The
$A_LINK_TRANS_RATE system variable contains the number of write requests that can still
be transferred in the current interpolator cycle.
In the following example, a link variable, data type WORD (2 bytes) and a link variable, data
type DWORD (4 bytes), are written:
Program example
N120 WHEN $A_LINK_TRANS_RATE > 0 DO $A_DLW[0] = 9
N125 WHEN $A_LINK_TRANS_RATE > 0 DO $A_DLD[2] = 7
N130 G4 F1
The synchronized action in N120 is performed only when the write request can be transferred
in the same interpolator cycle to the other NCU of the link group. In this case, the
$A_LINK_TRANS_RATE system variable is also decremented in the same interpolator cycle
so that the updated value is available for the synchronized action in the following N125 block.
13.2.2.7 Example: Structure of the link variables memory

The following data are defined for the link communication:
Data format Number Bytes per data Bytes required

BYTE 2 1 2
WORD 1 2 2
DWORD 3 4 12
Basic functions
Distributed systems
13.2 NCU link
Data format Number Bytes per data Bytes required

REAL 1 8 8
required size of the link variables memory: 24
Memory structure
The data is arranged in the link variables memory as follows, with the data format limits taken
into account:
/LQNYDULDEOHPHPRU\
0'01B00B6,=(2)B/,1.9$5B'$7$
,QGH[ %<7( %<7( :25' ':25'
':25' ':25'
5($/
Figure 13-8 Example: Structure of the link variables memory
Note
Memory structure
The data in the link variables memory is always arranged randomly and may therefore appear
different (although the data format limits will still be taken into account).
Access via a link variable must be programmed as follows, in accordance with the memory
structure defined:
Program code Description

$A_DLB[0] ; BYTE(1)
$A_DLB[1] ; BYTE(2)
$A_DLW[2] ; WORD
$A_DLD[4] ; DWORD(1)
$A_DLR[16] ; REAL
Basic functions
Distributed systems
13.2 NCU link
13.2.2.8 Example: Read drive data
Task
A system contains two NCUs (NCU1/NCU2). The NCUs are connected via the NCU link. The
MA2 machine axis of NCU1 (drive 2) travels in interpolation mode as link axis for NCU2. The
actual current value of drive 2 should be transferred for evaluation from NCU1 to NCU2. The
figure below shows the basic design of the system.
1&8OLQNYLD352),1(7
1&8 1&8 1&8 1&8

1&B$;
/RJPDFKLQHD[LVLPDJH
0'
$;
$;
$;
$;
$;
01B$;&21)B/2*,&B0$&+$;B7$%
0DFKLQHD[HV
0$
0$
0$
0$
0$
0$
0$
0'
01B$;&21)B0$&+$;B1$0(B7$%
'ULYH
'ULYH
'ULYH
'ULYH
'ULYH
'ULYH
Requirement
The actual current value for drive 2 (NCU1/MA2) can be read via the $VA_CURR system
variable. In the case of PROFIdrive-based drives, the following machine data item needs to be
set for this purpose:
MD36730 $MA_DRIVE_SIGNAL_TRACKING = 1 (acquisition of additional actual drive values)
Setting the machine data makes the following drive actual values available:
● $AA_LOAD, $VA_LOAD (drive capacity utilization in %)
● $AA_POWER, $VA_POWER (drive active power in W)
● $AA_TORQUE, $VA_TORQUE (drive torque setpoint in Nm)
● $AA_CURR, $VA_CURR (actual current value of axis or spindle in A)
Basic functions
Distributed systems
13.2 NCU link
Programming
NCU1
A static synchronized action is used to write cyclically in the interpolation cycle the actual
current value $VA_CURR of axis 2 (NCU1/MA2) via the link variable $A_DLR[0] (REAL value)
to the first 8 bytes of the link variables memory:
Program code
IDS=1 WHENEVER TRUE DO $A_DLR[0]=$VA_CURR[MA2]
NCU2
With a static synchronized action, the transferred actual current value is read cyclically in the
interpolator cycle via link variable $A_DLR[0]. If the actual current value is greater than 23 A,
alarm 61000 is displayed.
Program code
IDS=1 WHEN $A_DLR[0] > 23.0 DO SETAL(61000)
13.2.3 Link axes

A link axis is designated as a machine axis for which the setpoints are generated by a different
NCU than that to which the machine axis is physically connected. Link axes in conjunction with
axis containers (see Section "Axis container (Page 757)") permit in complex plants, such as
rotary indexing machines with several NCUs, the alternate use of machine axes of the NCU of
the link group.
The following figure shows as example an MA1 machine axis connected to the NCU1. The MA2
machine axis is connected to the NCU2. The X and Z channel axes travel in interpolation mode
by a part program that runs in a channel of NCU1. The setpoints are generated in the NCU1
interpolator. For machine axis MA1, they are forwarded to the position control of the NCU1. For
machine axis MA2, they are transferred via the NCU link to the position control of the NCU2 and
output there to the drive.
Basic functions
Distributed systems
13.2 NCU link
1&8OLQN
1&8 1&8
&KDQQHO
1*)
1;=
&KDQQHOD[HV
0'
;
=
0&B$;&21)B&+$1$;B1$0(B7$%
1&B$;
/RJPDFKLQHD[LVLPDJH
$;
$;
$;
0'
01B$;&21)B/2*,&B0$&+$;B7$%
0DFKLQHD[HV
0$
0$
0'
;
01B$;&21)B0$&+$;B1$0(B7$%
'ULYH
'ULYH
/RFDOD[LV /LQND[LV
Figure 13-9 Link axes
Requirement
The use of link axes requires a link communication defined in accordance with "Section Link
communication (Page 736)".
Home NCU
The home NCU of a link axis is the NCU on which it is physically connected as machine axis.
The position control and the exchange of axial NC/PLC interface signals of a link axis always
occurs on the home NCU. The generation of the setpoint can in principle be performed on any
NCU of the link group.
In the above figure:
● NCU1: Home NCU of machine axis MA1
● NCU2: Home NCU of machine axis MA2
Basic functions
Distributed systems
13.2 NCU link
13.2.3.2 Name of a link axis

The name of a link axis is composed of the identifier for the home NCU on which the machine
axis is physically connected and the general machine axis name AXn:
NC<ID>_<axis>
<ID>: Identification of the NCU of the link group in accordance with:

MD12510 $MN_NCU_LINKNO
See Section "Parameter assignment: Link communication (Page 743)"
<axis>: General machine axis name: AX1, AX2, AX3, ...
Assignment: Geometry axis or special axis to link axis
Direct assignment
A geometry or special axis can be assigned directly to a link axis in the logical machine axis
image by specification of the link axis name:
MD10002 $MA_AXCONF_LOGIC_MACHAX_TAB[ <axis>] = <link axis>
Parameters Meaning
<axis>: Machine axis index: 0, 1, 2, … (max. number of machine axes - 1)
<link axis>: Name of the link axis: NCx_AXy, see Section "Name of a link axis (Page 753)"
Indirect assignment
A geometry or special axis can be assigned to a link axis indirectly in the logical machine axis
image by specification of a container slot. The container slot then contains the actual name of
the link axis, as described above. This is called a container-link axis. See also Section: "Axis
container (Page 757)".
Synchronous setpoint output

A delay of one interpolator cycle results during the transfer of the setpoints of a link axis for the
setpoint-generating NCU to the home NCU. To ensure that the setpoints for the interpolation of
local axes and link axes are output to the drives at exactly the same time, this delay must be
compensated. To do this, on the setpoint-generating NCU, the number of buffer elements of the
buffer between the interpolator and the position controller must be set one element larger than
the number of buffer elements of the home NCU:
MD18720 $MN_MM_SERVO_FIFO_SIZE= 3
Basic functions
Distributed systems
13.2 NCU link
Example
1&8
*HRPHWU\D[LVQDPH *HRPHWU\D[HVXVHGLQWKHFKDQQHO &KDQQHOD[LVQDPH
0' 0' 0'
0&B$;&21)B*(2$;B1$0(B7$% 0&B$;&21)B*(2$;B$66,*1B7$% 0&B$;&21)B&+$1$;B1$0(B7$%
; ;
= =
VWJHRPHWU\D[LV>@ ; VWFKDQQHOD[LV>@ ;

QGJHRPHWU\D[LV>@ = QGFKDQQHOD[LV>@ =
UGJHRPHWU\D[LV>@ UGFKDQQHOD[LV>@

0DFKLQHD[HVXVHGLQWKHFKDQQHO /RJLFDOPDFKLQHD[LVLPDJH
0'0&B$;&21)B0$&+$;B86(' 0'01B$;&21)B/2*,&B0$&+$;B7$%

&KDQQHO

1&B$;
1&B$;
&KDQQHO

$;
$;

Figure 13-10 Example: Parameterization of link axes
Channel 1
The local AX1/AX2 machine axes of the NCU1 are assigned to the X/Z geometry axes.
Channel 2
The NC2_AX1/NC2_AX2 link axes of the NCU2 are assigned to the X/Z geometry axes.
13.2.3.4 Auxiliary function output for spindles
Description
During program execution and after block search with "search via program test" (SERUPRO),
the pre-defined auxiliary functions S, M3, M4, M5, M19 and M70 are output channel-specific on
the NCU on which the spindle has been programmed and also axis-specific on the home NCU.
Output of the channel-specific auxiliary functions

● DB21, ... DBW68 (extended address of the M function)
● DB21, ... DBD70 (M function 1)
● DB21, ... DBW98 (extended address of S function 1)
● DB21, ... DBD100 (S function 1)
Basic functions
Distributed systems
13.2 NCU link
Output of the axis-specific auxiliary functions

● DB31, ... DBD78 (F function for axis)
● DB31, ... DBW86 (M function for spindle)
● DB31, ... DBD88 (S function for spindle)
Further information
Detailed information regarding the auxiliary function output can be obtained in:
Function Manual Basic Functions, Auxiliary function outputs to PLC
Maximum number of machine axes

Even for the use of link axes, as previously, the maximum number of concurrently-usable
geometry and special axes as well as machine axes are still available for each NCU type.
"Lead link axes and "link axes" functions

As the functions "lead link axes" and "link axes" require different settings in machine data
MD18720 $MN_MM_SERVO_FIFO_SIZE, they cannot be used within a link group at the same
time.
Alarms: General behavior

If an error is detected at the position control level of the home NCU of a link axis and the relevant
alarm does not have "NC not ready" as response, the alarm is transferred via the NCU link to
the setpoint-generating NCU and then output.
Alarms: Behavior for emergency stop

If an emergency stop request is activated for an NCU via the NC/PLC interface, all axes
physically connected to this NCU will be switched to the "follow-up" mode. This also affects link
axes whose setpoints are currently generated by other NCUs. Under the assumption that no
further practical machining operations are then possible on these NCUs, an additional alarm
will be generated that stops all dependent axis movements.
Alarm acknowledgement
This additional alarm must be acknowledged by an NC reset. If the original alarm is still active
at this time, although the additional alarm can be acknowledged, an additional self-clearing
alarm will be generated that prevents a traversal of the axes or a program start until the original
alarm has been acknowledged.
Basic functions
Distributed systems
13.2 NCU link
Alarms: Response for "NC not ready" alarm response

If an error is detected at the position control level of the home NCU of a link axis and the relevant
alarm does not have "NC not ready" as response, the alarm is transferred to the setpoint-
generating NCU via the NCU link and output there. The alarm output is also made on the home
NCU.
Under the assumption that no further practical machining operations are then possible on the
setpoint-generating NCU, an additional alarm will be generated that stops all dependent axis
movements.
Alarm acknowledgement
See alarm acknowledgement under "Alarms: Behavior for Emergency Stop"
Alarms: Behavior for "Mode group not ready" alarm response

If an error is detected within a mode group with several channels and the relevant alarm has
"Mode group not ready" as response, this causes the traversing movements in all channels of
the mode group to stop. If the traversing movements are generally independent of each other,
the response via the following machine data item can be changed to "Channel not ready":
MD11412 $MN_ALARM_REACTION_CHAN_NOREADY = TRUE
Effect
In the NC/PLC interface, instead of signal DB11 DBX26.3 (mode group ready), the signal
DB21, DBX36.5 (channel ready), is reset.
Advantage
The alarm response remains limited to the channel in which the error is detected. If required,
the PLC user program can initiate further responses.
Requirement
There is no higher-priority alarm response than "Mode group not ready".
Compensations
The following compensations are not available:
● Link axes: Quadrant error compensation (QEC)
● Container link axes: Sag compensation (CEC)
Switch-off an NCU in a link group

If an NCU in a link group is switched off, the machining on all other NCUs of the link group will
be cancelled and an alarm issued.
Powering up an NCU group

If an NC reset is triggered on an NCU in a link group, it will also be transferred to all other NCUs
of the link group so that all NCUs of the link group perform a warm restart.
Basic functions
Distributed systems
13.2 NCU link
Nibbling and punching technologies

The fast inputs/outputs required for the nibbling and punching must be connected and
parameterized on the NCU on which the part program is processed and the axes interpolated.
The commands for "High-speed nibbling and punching", e.g. PONS and SONS, are not available
for link axes.
Frames
A link axis is permitted in a Frame command only when it is a geometry axis. The Frame
command changes only the geometry in the channel to which the link axis is currently assigned.
Speed/torque coupling, master-slave

The drives of all axes/spindles of a master-slave group must be connected to the same NCU.
The master axis can, however, be traversed as link axis for the channel of another NCU.
13.2.4 Axis container

An axis container is a circular data structure with a parameterized number of elements. These
elements together with axis containers, are designated as slots (Slot 1, Slot 2, ... Slot n). The
slots allow a variable assignment of geometry and/or special axes to machine axes. The entry
in a slot can reference an NCU-local machine axis (container axis) or a link axis (container-link
axis).
The following figure shows an axis container with four slots. The container axes refer in the
current position of the axis container to the following machine axes:
Container axis Machine axis

CT1_SL1 NCU 1: AX1
CT1_SL2 NCU 1: AX2
CT1_SL3 NCU 2: AX1
CT1_SL4 NCU 2: AX2
Basic functions
Distributed systems
13.2 NCU link
$[LVFRQWDLQHU&7
6ORW 6ORW
;

;
$
$
B
B
&
&
1
1
1
1
&
&
B
B
$
$
;
;

6ORW 6ORW
Figure 13-11 Example: Axis container CT1 with four slots
Rules
The following rules must be observed with regard to axis containers:
● All machine axes of an axis container may be assigned to just one channel axis at any one
time.
● Multiple slots of an axis container must not reference the same machine axis.
● At any one time, only one channel is authorized to write to a machine axis, directly or via a
container axis.
● Several geometry and/or special axes of a channel can also be assigned to the container
axes of an axis container.
Assignment: Geometry or special axis → container axis

In the logical machine axis image MD10002 $MN_AXCONF_LOGIC_MACHAX_TAB, a
container axis can be assigned as a machine axis via container and slot to a geometry or
special axis, e.g. CONTAINER "CT1", slot "1":
MD10002 $MN_AXCONF_LOGIC_MACHAX_TAB[ n ] = CT1_SL1
During the traversing of the geometry or special axis, the machine axis assigned at this time to
slot 1 then traverses.
Axis container rotation

An axis container rotation is always performed when all channels involved on the axis container
have granted their enable with a program command. After the axis container rotation, other
machine axes are assigned to the geometry or special axes of the channels.
The setting data specifies the increment of an axis container rotation.
See Section "Parameterization (Page 760)".
Basic functions
Distributed systems
13.2 NCU link
Axis container name

The following program commands can be addressed via the axis container name (<axis
container>):
● Program commands:
– AXCTSWE(<axis container>)
– AXCTSWED(<axis container>)
– AXCTSWEC(<axis container>)
The following names are possible:
CT<container number>: The number of the axis container is attached to the CT letter
combination.
Example: CT3
<container name>: Individual name of the axis container set using
MD12750 $MN_AXCT_NAME_TAB
Example: A_CONT3
<axis name>: Axis name of a container axis which is known in the channel
involved.
Implicit wait
There is an implicit wait for the completion of a requested axis container rotation if one of the
following events has occurred:
● Part program language commands which will cause a container axis assigned to this axis
container in this channel to move
● GET(<channel axis name>) on a corresponding container axis
● The next AXCTSWE(<axis container>) for this axis container
Note
Even an IC(0) will result in a wait including synchronization where necessary (block-by-
block change in addressing according to incremental dimension even though an absolute
dimension has been set globally).
Basic functions
Distributed systems
13.2 NCU link
Synchronization with axis position

If the new container axis assigned to the channel after a container rotation does not have the
same absolute machine position as the previous axis, then the container is synchronized with
the new position (internal REORG).
Note
SD41700 $SN_AXCT_SWWIDTH[<axis container>] is only updated for a new configuration. If,
after incremental rotation of the RTM/MS, the position of a circuit before the initial position is
reached, the container can be rotated normally in the forward direction to reach the initial
position of the container again. The drum or rotary table must however be turned back to the
original position, so that measuring and supply cables are not twisted.
See also
System variable (Page 768)
Machine data

MD12750 AXCT_NAME_TAB Name of the axis container
MD12760 AXCT_FUNCTION_MASK.Bit x Axis container-specific functions
MD1270x AXCT_AXCONF_ASSIGN_TABx Assignment of machine axes to the slots of an axis container
MD18720 MM_SERVO_FIFO_SIZE Size of the IPO/SERVO data buffer
Note:
The value 3 must be set on all participating NCUs for cross-NCU axis
containers.
Name of the axis container

MD12750 $MN_AXCT_NAME_TAB[ <index> ] = "<name>"
Parameters Meaning
<index>: 0, 1, … max. axis container index
<name>: Name of the axis container (e.g. CT1)
Basic functions
Distributed systems
13.2 NCU link
Axis container-specific functions

MD12760 $MN_AXCT_FUNCTION_MASK.Bit x = <value>
Parameters <value> Meaning

Bit 0: 0 For a direct axis container connection (AXCTSWED), all other chan‐
nels must be in the RESET state.
1 For a direct axis container connection (AXCTSWED), only other chan‐
nels that have the interpolation authorization to axes of the axis con‐
tainer need to be in the RESET state.
The machine data is used to activate the axis container-specific functions.
Assignment of machine axes to the slots of an axis container

MD1270x $MN_AXCT_AXCONF_ASSIGN_TABx[ <index> ] = <axis>
Parameters Meaning
x: 1 … max. number of axis containers
<index>: 0, 1, … max. slot index
<axis>: Name of a local machine axis (e.g. AX1)
Name of a link axis. See Section "General information (Page 751)".
The slots within an axis container must be assigned in ascending order without gaps, starting
with slot index 0.
Setting data
Increment of an axis container rotation

SD41700 $SN_AXCT_SWWIDTH[<index>]=<increment>
Parameters Meaning
<index>: 0, 1, … max. axis container index
<increment>: Number of slots through which the axis container rotates
Illustration of the axis container rotation

The axis container rotation is enabled by means of program commands. See Section
"Programming (Page 766)".
In the left-hand part of the figure "Axis container rotation, Fig. 1," the link axis NCU1_AX1 is
assigned to slot 1 in the initial setting of the axis container.
After the rotation with an increment of 1 (right-hand side), the link axis NCU2_ AX2 is assigned
to slot 1.
Basic functions
Distributed systems
13.2 NCU link
$[LVFRQWDLQHU&7 $[LVFRQWDLQHU&7
6ORW 6ORW 6ORW 6ORW

;
;
;
;
$
$
$
$
B
B
B
B
&
&
&
&
1
1
1
1
1
1
1
&
&
&
&
B
B
B
B
$
$
$
;
;
;
;

6ORW 6ORW 6ORW 6ORW
$VVLJQPHQWSULRUWRURWDWLRQ $VVLJQPHQWDIWHUURWDWLRQ
6'61B$;&7B6::,'7+>@
Figure 13-12 Axis container rotation, Fig. 1
Based on the initial setting stated above, the link axis NCU2_ AX1 is assigned to slot 1 after a
rotation with an increment of 2, (figure "Axis container rotation, Fig. 2," left part).
Based on the initial setting stated above, the link axis NCU1_ AX2 is assigned to slot 1 after a
rotation with an increment of -1 (figure "Axis container rotation, Fig. 2," right part).
$[LVFRQWDLQHU&7 $[LVFRQWDLQHU&7
6ORW 6ORW 6ORW 6ORW

;
;
;
;
$
$
$
B
B
B
B
&
&
&
&
1
1
1
1
1
1
&
&
&
&
B
B
B
B
$
$
$
;
;
;
;

6ORW 6ORW 6ORW 6ORW
$VVLJQPHQWDIWHUURWDWLRQ $VVLJQPHQWDIWHUURWDWLRQ
6'61B$;&7B6::,'7+>@ 6'61B$;&7B6::,'7+>@
Figure 13-13 Axis container rotation, Fig. 2
Axis container with container-link axes

The parameterization of an axis container that contains container-link axes must be made on
the master NCU of the link group (MD12510 $MN_NCU_LINKNO == 1).
Basic functions
Distributed systems
13.2 NCU link
Alignment of axial machine data

For container axes, all axial machine data marked with the "CTEQ" (container equal) attribute
must have the same value for all container axes. Any different values will be aligned
automatically.
Control startup
During the control startup, all machine data will be aligned to the values of the container axis of
the first slot. If the value of a machine data item changes, the following message will be
displayed: "The axial machine data of the axes in axis container <n> has been adapted".
Activate machine data

If a machine data item of any container axis is changed, the new value also becomes
immediately available in all other container axes. The following message is displayed:
"Caution: This MD will be set for all container axes".
Slot change
If a slot of an axis container is assigned another machine axis, (MD127xx
AXCT_AXCONF_ASSIGN_TAB<x>), the following message is displayed: "The machine data
of the axes in axis container <n> will be adapted at the next startup".
Note
Container-link axes
For container-link axes, a machine data alignment is performed for all NCUs of the link group
involved on the axis container.
Parameter example
Assumptions
NCU Components
NCU1: Channel 1, X/Z geometry axes → 1st/2nd channel axis
Channel 2, X/Z geometry axes → 1st/2nd channel axis
Machine axes: AX1, AX2
CT1 axis container with four slots
NCU2: Machine axes: AX1, AX2
Basic functions
Distributed systems
13.2 NCU link
Parameter assignment: NCU1
1&8
*HRPHWU\D[LVQDPH *HRPHWU\D[HVXVHGLQWKHFKDQQHO &KDQQHOD[LVQDPH
0' 0' 0'
0&B$;&21)B*(2$;B1$0(B7$% 0&B$;&21)B*(2$;B$66,*1B7$% 0&B$;&21)B&+$1$;B1$0(B7$%
; ;
= =
VWJHRPHWU\D[LV>@ ; VWFKDQQHOD[LV>@ ;

QGJHRPHWU\D[LV>@ = QGFKDQQHOD[LV>@ =
UGJHRPHWU\D[LV>@ UGFKDQQHOD[LV>@

0DFKLQHD[HVXVHGLQWKHFKDQQHO /RJLFDOPDFKLQHD[LVLPDJH
0'0&B$;&21)B0$&+$;B86(' 0'01B$;&21)B/2*,&B0$&+$;B7$%

&KDQQHO

&7B6/
&7B6/
&7B6/
&7B6/
&KDQQHO

$[LVFRQWDLQHU&7
6ORW 6ORW
6ORWDVVLJQPHQW
0'
;

;
$
01B$;&21)B$66,*1B7$%>@ ಯ1&B$;ರ
$
B
B
&
01B$;&21)B$66,*1B7$%>@ ಯ1&B$;ರ
&
1
01B$;&21)B$66,*1B7$%>@ ಯ1&B$;ರ
01B$;&21)B$66,*1B7$%>@ ಯ1&B$;ರ
1
1
&
&
B
B
$
$
;
;

6ORW 6ORW
Figure 13-14 Example: Parameter assignment of channel axes and axis containers
Effect
By programming the X and Z geometry axes in the 1st and 2nd channel of the NCU1, the
following axes traverse in the current position of the container:
● The local AX1 and AX2 machine axes of the NCU1.
● As container-link axes, the AX1 and AX2 machine axes of the NCU2.
For the axis container rotation, see Section "Programming (Page 766)".
Basic functions
Distributed systems
13.2 NCU link
Notes on the parameter assignment
Container axis distribution and communications utilization

In the case of a plant with several NCUs that traverse alternately axes of other NCUs (link axes)
in conjunction with axis containers, the type and manner how the link axes are distributed within
the axis container decide on the utilization of the link communication.
$[LVFRQWDLQHU&7[ $FKVFRQWDLQHU&7[

1&8
1&8
1&8
1&8
6\PPHWULFDOD[LVGLVWULEXWLRQ $V\PPHWULFDOD[LVGLVWULEXWLRQ
① Blue slot: Refers to a drive connected to the NCU1

② Red slot: Refers to a drive connected to the NCU2
③ Drives connected to NCU1
④ Drives connected to NCU2
Figure 13-15 Axis distribution
● Symmetrical axis distribution

In the case of a symmetrical axis distribution, each NCU first traverses only local axes. This
means no link communication occurs. Provided all NCUs only traverse link axes, each
transition of the axis container increases the utilization of the link communication up to a
maximum.
● Asymmetrical axis distribution
For an asymmetric axis distribution, each NCU traverses local and link axes from the
beginning. Unlike with symmetrical axis distribution, this results in a constant average
utilization of the link communication.
Basic functions
Distributed systems
13.2 NCU link
Drive distribution and communications utilization

In a system with several NCUs that in conjunction with axis containers alternately traverse axes
of another NCU (link axes), the distribution of the drives connected to the NCU decides the
utilization of the link communication.
● Symmetric drive distribution
In the case of a symmetric drive distribution, the drives addressed via the axis container are
connected to both NCUs. On account of this arrangement, the maximum possible number
of drives can still be addressed via the logical machine axes images (LAI) on both NCUs.
1&8 &7 1&8

&7B6/
&7B6/
&7B6/
&7B6/

/$,
$;
$;
$;
$;
$ $
$ $

$ $ $ $ $ $ $ $
Figure 13-16 Symmetric drive distribution
● Asymmetric drive distribution

In the case of an asymmetric drive distribution, the drives addressed via the axis container
are only connected to NCU1. On account of this arrangement, the maximum possible
number of drives can only be addressed via the logical machine axes images (LAI) on
NCU2. Only the maximum number minus the drives used by NCU2 can be addressed via
the LAI of NCU1. In order to also be able to use the maximum number of drives on NCU1,
they must be connected to NCU2 and addressed from NCU1 via the NCU link. This results
in a higher cyclic link communication load.
1&8 &7 1&8

&7B6/
&7B6/
&7B6/
&7B6/

/$,
$;
$;
$ $
$ $

$ $ $ $ $ $
Figure 13-17 Asymmetric drive distribution
Function
The AXCTSWE or AXCTSWED commands are used to enable the rotation of the specified axis
container.
Any previously set enable for axis container rotation is cancelled with the AXCTSWEC command.
Syntax
AXCTSWE(<ID>)
AXCTSWED(<ID>)
Basic functions
Distributed systems
13.2 NCU link
AXCTSWEC(<ID)
Meaning
AXCTSWE: Enable for rotation of the axis container

The program processing is not stopped by AXCTSWE.
The rotation is performed as soon as all channels involved on the axis con‐
tainer have been enabled.
The increment of an axis container rotation is set via the SD41700
$SN_AXCT_SWWIDTH setting data (see Section "Parameterization
(Page 760)")
AXCTSWED: Enable to rotate the axis container without consideration of the other channels
involved on the axis container
The increment of an axis container rotation is set via the SD41700
$SN_AXCT_SWWIDTH setting data (see Section "Parameterization
(Page 760)")
Note
● Command variant to simplify the commissioning of the part program or
synchronized action.
● The behavior with regard to the other channels involved on the axis con‐
tainer can be specified via:
MD12760 $MN_ AXCT_FUNCTION_MASK, bit 0
See Section "Parameterization (Page 760)".
AXCTSWEC: Canceling the enable to rotate the axis container
Note
The enable for rotating an axis container can only be cancelled when the
rotation has yet not been started:
$AN_AXCTSWA[<axis container>] == 0
See Section "System variable (Page 768)"
<ID>: Name of the axis container or a container axis:
CT<number>: Default identifier of an axis container:
Example: CT1
<Container>: User-specific name of an axis container:
Example: CONTAINER_1
<axis>: Name of a known container axis in the channel
Further information
The use of the AXCTSWEC command in synchronized actions is described in detail in:
Function Manual Synchronized Actions, Detailed description > Actions in synchronized actions
> Cancel release for axis container rotation (AXCTSWEC)
Basic functions
Distributed systems
13.2 NCU link
Description
Container-specific system variable

$AC_AXCTSWA[<ID>] Channel-specific status of the axis container rotation
$AN_AXCTSWA[<ID>] NCU-specific status of the axis container rotation
$AN_AXCTSWE[<ID>] Slot-specific status of the axis container rotation
$AN_AXCTAS[<ID>] Number of slots through which the axis container was just switched
through.
ID: Axis container name or name of a container axis
NC-specific system variable

$AN_LAI_AX_IS_AXCTAX 1)
Status: LAI axis == container axis
of the machine axes in the logical machine axis image
(MD10002 $MN_AXCONF_LOGIC_MACHAX_TAB)
regarding axis container.
$AN_LAI_AX_IS_LEADLINKAX 1) Status: LAI axis == lead-link axis
$AN_LAI_AX_IS_LINKAX 1) Status: LAI axis == link axis
$AN_LAI_AX_TO_IPO_NC_CHANAX[<ID>] Channel and channel axis number or NCU-ID and the
global axis number
$AN_LAI_AX_TO_MACHAX[<ID>] NCU-ID and axis number of the machine axis
1) Bit mask: Bit n ≙ LAI axis (n+1) from MD10002 $MN_AXCONF_LOGIC_MACHAX_TAB
ID: LAI axis number
NCU-ID: Value from MD12510 $MN_NCU_LINKNO
Further information
A detailed description of the system variables can be found in:
See also
Evaluating axis container system variables (Page 780)
Basic functions
Distributed systems
13.2 NCU link
13.2.4.5 Machining with axis container (schematic)
6WDUW
,QLWLDOVHWXS
,)
+DVD[LVFRQWDLQHU
URWDWLRQWHUPLQDWHG" 1R
<HV $1B$;&76:$&7
6HWXSF\FOLF
,)
+DVURWDWLRQRQWKH 0DLQWDLQLQJ
PDFKLQHWHUPLQDWHG" 1R
<HV
0DFKLQHF\FOLF
&OHDQXSF\FOLF
&RQWDLQHUURWDWLRQHQDEOH
$;&76:(&7
,)
&RQWLQXHF\FOLF
<HV PDFKLQLQJ"
1R
)LQDOFOHDQXS
(QG
Figure 13-18 Example: Schematic machining sequence for a station of a rotary cycle machine
13.2.4.6 Behavior in different operating states
Startup (Power On)

In the startup the controller, with regard to the slot assignment, the initial state defined in the
machine data is always assumed irrespective in which state of the axis container the control
was switched off:
Basic functions
Distributed systems
13.2 NCU link
MD1270x $MN_AXCT_AXCONF_ASSIGN_TABx
Note
Alignment between setpoint and actual status
After a controller startup, it is the sole responsibility of the user / machine manufacturer to detect
any difference between the status of the axis container and the machine status and to
compensate for this with a suitable axis container rotation.
Mode change
A container axis whose axis container in the Automatic mode was enabled for rotation cannot
be traversed after a change in the JOG mode.
Channel-specific Reset state

As soon as a channel involved on the axis container is in the Reset state, no enable for axis
container rotation is required for this channel. It suffices to enable the remaining active
channels.
Block search
An axis container rotation (AXCTSWE) cannot be enabled and activated in one block, but the
enabling and activation commands must be programmed in separate action blocks. In other
words, the axis container status changes in response to each separate rotation command as
a function of the status of other channels.
13.2.4.7 Behavior when withdrawing the release for axis container rotation
TheAXCTSWE command enables the channel-specific axis container rotation for an axis
container. The AXCTSWEC command cancels the enable.
The following figure shows an example the sequence of an axis container rotation as
represented in the axis container-specific system variables. Two channels for two NCUs are
always involved on the axis container.
Basic functions
Distributed systems
13.2 NCU link
1&8

&KDQQHO
$&B$;&76:$>,'!@

&KDQQHO
$&B$;&76:$>,'!@

1&8
$1B$;&76:$>,'!@

1&8

&KDQQHO
$&B$;&76:$>,'!@

&KDQQHO
$&B$;&76:$>,'!@

1&8
$1B$;&76:$>,'!@

① NCU1, channel1: Enable issued using the AXCTSWE command

② NCU2, channel2: Enable issued using the AXCTSWE command
③ NCU1, channel2: Enable issued via AXCTSWE command → all enables of all channels are now
present in the NCU1 → the overall enable status of NCU1 is transferred to NCU2 via link com‐
munication
④ NCU2, channel1: Enable issued via AXCTSWE command → all enables of all channels are now
present in the NCU2 → the overall enable status of NCU2 is transferred to NCU1 via link com‐
munication
All enable signals for all channels (NCU2 and NCU1) are now present in NCU2 → the axis
container rotation is performed in NCU2
⑤ NCU1: All enable signals for all channels (NCU1 and NCU2) are now present in NCU1 → the axis
container rotation is performed in NCU1
⑥ NCU1/NCU2: axis container rotation has been completed
Figure 13-19 Cross-NCU enable and axis container rotation
To allow a previously granted enable to be canceled, the enable for at least one of the channels
(NCU1 or NCU2) involved on the axis container must still be pending at the time of the
cancellation. This means the cancel must be made before time ④.
Basic functions
Distributed systems
13.2 NCU link
Withdrawal is no longer possible as soon as all enable signals are available from all channels
of all NCUs (instant in time ④). In this case, the AXCTSWEC command has no effect. No
feedback is sent to the user.
See also
Axis mode
If a container axis in axis mode or as a positioning spindle (POSA, SPOSA) traverses, the axis
container rotates only after reaching the programmed end position.
Spindle
● A container axis active as a spindle continues to rotate during an axis container rotation.
● The control type of a spindle (speed / position control) refers to the associated machine axis.
The set control type "moves" with the machine axis when an axis container rotates.
● For commands that refer to the master spindle of the channel, a machine axis with the
corresponding spindle number must exist in the channel at the time of execution of the
command:
MD35000 $MA_SPIND_ASSIGN_TO_MACHAX[ <axis>] == number of the master spindle
Note
It is the sole responsibility of the user / machine manufacturer to ensure for spindles as
container axes that an appropriate machine axis must still exist in the channel after an axis
container rotation for the master spindle.
Work offsets
Note
It is the sole responsibility of the user / machine manufacturer to ensure that after an axis
container rotation the effective work offsets in the channel are adapted to the changed machine
axis assignments.
If continuous-path mode is active in the channel and an axis container rotation is performed, a
subsequent programming of a container axis interrupts the continuous-path mode. The
interruption also occurs even when the container axis not a path axis.
Basic functions
Distributed systems
13.2 NCU link
PLC axis
If a container axis whose axis container has been enabled for rotation becomes a PLC axis, the
status change occurs only after completion of the axis container rotation.
Command axis
If a container axis whose axis container has been enabled for rotation traverses as a command
axis, the traversing movement is performed only after completion of the axis container rotation.
Oscillating axis
If a container axis whose axis container has been enabled for rotation becomes an oscillation
axis, the status change occurs only after completion of the axis container rotation.
External work offset

The "external work offset" is based on the machine coordinate system (MCS). Therefore, for an
active "external work offset", one of the container axes rejects the axis container rotation with
alarm 4022.
Axial frames
The axial frame of a channel axis, which is also a container axis, is no longer valid after an axis
container rotation. Since the axis container rotation assigns a new machine axis to the channel
axis, but the axial frame is referred to a machine axis, the rotation also changes the axial frame.
If the two frames do not coincide, a synchronization process (internal REORG) is performed.
Note
The assignment between a channel axis and a machine axis is altered by the axis container
rotation. The current frames remain unchanged after a rotation. The user is responsible for
ensuring that the correct frames are selected after a rotation by programming basic frame
masks, for example.
Transformation
If a container axis is involved as a spindle in a transformation, the transformation must be
deselected before the enable of the axis container rotation.
Axis couplings
If an axis coupling is active for a container axis, the coupling with COUPOF must be deselected
before the enable of the axis container rotation. After completion of the rotation, the coupling
can be immediately selected again with COUPON. A new define of the coupling is not required.
Basic functions
Distributed systems
13.2 NCU link
Gantry axis
A gantry axis cannot be a container axis.
Travel to fixed limit

If a container axis is at the limit stop, no axis container rotation can be performed.
Drive alarms
If a drive alarm is pending for a container axis, the axis container rotation is not performed.
13.2.5 Lead link axes

If, for an axis coupling, the the machine axes of the leading and following axes are not
connected to the same NCU, the coupling must be established using a link axis of the NCU of
the following axis. In this case, the link axis is designated as lead-link axis.
The setpoints of the master axis are transferred synchronously in the interpolator cycle via the
NCU link to the lead-link axis. Similarly, in the opposite direction, the actual values and the
status data of the lead-link and the following axis are transferred to the leading axis.
The lead-link axis is parameterized as local leading axis of the following axis.
/HDGLQJD[LVGDWD
$[LVFRXSOLQJ
)ROORZLQJD[LVGDWD /HDGOLQND[LV
8S
1&8OLQN )ROORZLQJD[LV
1&8 1&8
.DQDODFKVHQ
; ; < 0'
0&B$;&21)B&+$1$;B1$0(B7$%
/RJ0DVFKLQHQDFKVDEELOG
$; 1&B$; $; 0'
01B$;&21)B/2*,&B0$&+$;B7$%
/HDGOLQN 0DVFKLQHQDFKVHQ
0$ 0$ 0'
$[LV
01B$;&21)B0$&+$;B1$0(B7$%
$QWULHE
$QWULHE
/HDGLQJD[LV )ROORZLQJD[LV
Figure 13-20 Lead-link axis
Basic functions
Distributed systems
13.2 NCU link
Coupled axes
Lead link axes can be used in conjunction with following axis couplings:
● Master value coupling
● Coupled motion
● Tangential tracking
● Electronic gear (ELG)
● Synchronous spindle
Requirement
The NCU must communicate via the NCU link. See Section "Link communication (Page 736)"
Link communication

MD12510 NCU_LINKNO Unique numerical identification of the NCU within the link group. The
identifiers must be assigned without any gaps in ascending ordering
starting from 1.
Value range: 1, 2, ... Maximum NCU number
Note:
The NCU to which the value 1 is assigned as NCU identification is
the master NCU of the link group. The parameterization of link axes and
axis containers may only be made with the machine and setting data of
the master NCU.
MD18780 MM_NCU_LINK_MASK.Bit 0 Activation of the link communication
MD18781 NCU_LINK_CONNECTIONS Number of internal link connections
Note:
It is recommended to retain the default value 0 (determination of the
number by the NC).
MD18782 MM_LINK_NUM_OF_MODULES Number of NCUs to be connected with one another via NCU link.
Basic functions
Distributed systems
13.2 NCU link
Setpoint synchronization

MD18720 MM_SERVO_FIFO_SIZE Size of the IPO/SERVO data buffer
The transfer of the setpoints of the leading axis via the NCU link to the
NCU of the lead-link axis produces a deadtime of two interpolator cycles.
The dead time is compensated by parameterizing the sizes of the IPO/
SERVO data buffer on the NCU of the leading axis and the NCU of the
lead-link axis:
● NCU of the leading axis: 4
● NCU of the lead-link axis: 2
Note
With the simultaneous use of lead link axes and cross-NCU axis containers, the axis container
means machine data MD18720 $MN_MM_SERVO_FIFO_SIZE = 3 must be set. This means a
synchronous output of the setpoints for leading and following axis is not possible. The offset
then has the size of one interpolator cycle.
Leading, lead-link and following axis

MD10000 AXCONF_MACHAX_NAME_TAB Machine axis name
MD10002 AXCONF_LOGIC_MACHAX_TAB Logical machine axis image

MD20070 AXCONF_MACHAX_USED Used machine axis
Number Identifier $MA_ Meaning

MD30554 AXCONF_ASSIGN_MASTER_NCU Master NCU
If a machine axis can be traversed for several NCUs, one NCU must be
defined as master NCU. The setpoint generation is made after the
startup of the control for this NCU.
Basic functions
Distributed systems
13.2 NCU link
13.2.5.3 System variables to enter a leading value

Leading values can be specified on the NCU of the leading axis using the following system
variable:
● Position leading value: $AA_LEAD_SP[<leading axis>]
● Velocity leading value: $AA_LEAD_SV[<leading axis>]
When making a change, the values are also transferred to the NCU of the following axis per
NCU link.
Note
These system variables have a lower transfer priority than those of the link variables.

The following supplementary conditions must be observed:
● The leading axis cannot be a link axis
● The leading axis cannot be a container axis
● The leading axis cannot be a gantry axis
● The leading axis may only be replaced within its own NCU (see Section "Cross-channel axis
interchange (Page 549)")
● Couplings with lead link axes must not be cascaded
● A lead link axis must not be traversed independently of the leading axis
Note
"Lead link axes" and "link axes" functions
Because the "lead link axes" and "link axes" functions require different settings in machine
data: MD18720 $MN_MM_SERVO_FIFO_SIZE, they cannot be used simultaneously within
a link group.
13.2.5.5 Example
A detailed example for parameterizing and programming an axis coupling with lead-link axis is
provided in the Section: "Examples" > "Lead link axis (Page 791)".
13.2.6 System of units within a link group

For a cross-NCU interpolation, the same system of units must be active on all NCUs of the link
group.
Basic functions
Distributed systems
13.3 Examples
Common system of units changeover via HMI

The following conditions must be fulfilled for all NCUs of the link group in order that a system
of units changeover can be made from the HMI user interface of an NCU of the link group as
well as on all other NCUs of the link group:
● MD10260 $MN_CONVERT_SCALING_SYSTEM = 1
● For all channels:
MD20110 $MC_RESET_MODE_MASK, Bit 0 = 1
● All channels are in the reset state
● No axis is traversed in the JOG or DRF mode or via the PLC
● The function "constant grinding wheel peripheral speed (GWPS)" is not active.
If, on one NCU of the link group, one of the specified conditions is not fulfilled, then the system
of units changeover is not made on any of the NCUs of the link group.
Different systems of units

Different systems of units are possible in spite of an active link group, as long as no cross NCU
interpolation takes place. The system of units settings are made for a specific NCU in the part
program or synchronous action using G commands (G70, G71, G700, G710).
Further information
Function Manual Basic Functions; Velocities, setpoint/actual value systems, closed-loop
control
13.3 Examples
13.3.1 Link axis
Parameter example for two NCUs each with a link axis
NCU1
Machine data Note

General link data:
$MN_NCU_LINKNO = 1 Master NCU
$MN_MM_NCU_LINK_MASK = 1 Set NCU-link active
$MN_MM_SERVO_FIFO_SIZE = 3 Size of the data buffer between interpolation and position con‐
trol
$MN_MM_LINK_NUM_OF_MODULES = 2 Number of link modules
Logical machine axis image (LAI):
$MN_AXCONF_LOGIC_MACHAX_TAB[0] = "AX1" Local machine axis
Basic functions
Distributed systems
13.3 Examples
Machine data Note

$MN_AXCONF_LOGIC_MACHAX_TAB[2] = "NC2_AX3" Link axis
Machine axis name, unique system-wide as NCU identifier:
$MN_AXCONF_MACHAX_NAME_TAB[0] = "NC1_A1"
Assignment of channel axis to machine axis:
$MC_AXCONF_MACHAX_USED[0] = 1 1. Channel axis to the machine axis of LAI[0]
$MC_AXCONF_MACHAX_USED[2]=3 3. Channel axis to the machine axis of LAI[2]
NCU2
Machine data Note

General link data:
$MN_NCU_LINKNO = 2 Slave NCU
$MN_MM_NCU_LINK_MASK = 1 Set NCU-link active
$MN_MM_SERVO_FIFO_SIZE = 3 Size of the data buffer between interpolation and position con‐
trol
$MN_MM_LINK_NUM_OF_MODULES = 2 Number of link modules
Logical machine axis image (LAI):
$MN_AXCONF_LOGIC_MACHAX_TAB[2] = "NC1_AX3" Link axis
Machine axis name, unique system-wide as NCU identifier:
Assignment of channel axis to machine axis:
$MC_AXCONF_MACHAX_USED[2]=3 3. Channel axis to the machine axis of LAI[2]
13.3.2 Axis container coordination
The characteristic as a function of time is displayed from top to bottom in the following tables.
The data are valid on condition that only two channels have axes in the container.
Basic functions
Distributed systems
13.3 Examples
13.3.2.1 Axis container rotation without a part program wait
Channel 1 Channel 2 Comment

AXCTWE(C1) Part program ... Channel 1 enables the axis container for
rotation.
Part program without movement of a Part program ...
container axis
AXCTSWE(C1) Channel 2 enables the axis container for
rotation, container rotates because both
channels have enabled rotation
Part program with movement of a con‐ Part program with movement of a con‐ Without wait
tainer axis tainer axis
13.3.2.2 Axis container rotation with an implicit part program wait

AXCTWE(C1) Part program ... Channel 1 enables the axis container for
rotation.
Part program with movement of a con‐ Part program ... Channel 1 waits implicitly for axis con‐
tainer axis tainer rotation
AXCTSWE(C1) Channel 2 enables the axis container for
rotation, rotation occurs.
Channel 1 is continued.
13.3.2.3 Axis container rotation by one channel only (e.g. during power up)

AXCTWED(C1) In the RESET state Instantaneous rotation
13.3.3 Evaluating axis container system variables
13.3.3.1 Conditional branch
Channel 1 Comment
N100 AXCTWE(CT1) Channel 1: Enable of the rotation of axis container CT1
MARKER1:
N200 ... Part program without movement of a container axis
IF $AC_AXCTSWA[CT1] == 1 GOTOB MARKE1 IF rotation of axis container CT1 still active
THEN continue with MARKER1
ELSE (rotation of axis container CT1 completed)
N300 ... Part program with movement of a container axis
Basic functions
Distributed systems
13.3 Examples
13.3.3.2 Static synchronized action with $AN_AXCTSWA
Channel 1 Comment
IDS =1 EVERY $AN_AXCTSWA[CT1] == 1 DO M99 Static synchronized action:
Always output auxiliary function M99 at the beginning of an
axis container rotation.
Further information: Synchronized Actions Function Manual
13.3.3.3 Wait for certain completion of axis container rotation
Note
Although programming system variables $AN_AXCTSWA initiates an implicit preprocessing
stop, the subsequent command sequence cannot be used to uniquely identify the completion
of a requested axis container rotation in the channel:
WHILE ($AN_AXCTSWA[<ID>] == TRUE) ; wait: until the enable for axis
container rotation was canceled
ENDWHILE
While the channel in the command sequence waits for the completion of the axis container
rotation, initiated from another channel, a reorganization could be carried out in the
background. For instance, by transferring a requested axis to another channel. As a
consequence, the system variable would then supply the value FALSE. Even if the axis
container rotation had still not been completed.
Recommended command sequence:
RL = $AN_AXCTAS[<ID>] ; read: actual axis container position
AXCTSWE(<ID>) ; enable: axis container rotation
WHILE (RL == $AN_AXCTAS[<ID>]) ; wait: until the read is not equal to
the actual axis container
; position
ENDWHILE
RL is any random user variable.
Example 1: Explicit waiting using system variable $AN_AXCTAS

RL = $AN_AXCTAS[<ID>] ; Reading: actual axis container position
AXCTSWE(<ID>) ; Enable: Axis container rotation
WHILE (RL == $AN_AXCTAS[<ID>]) ; Wait: Change the axis container
ENDWHILE ; Position
Basic functions
Distributed systems
13.3 Examples
Example 2: Explicit wait using the WAIT mark

CLEARM(9) ; Delete: marker (tag) 9 in the channel
AXCTSWE(<ID>) ; Enable: Axis container rotation
; SynAct: Wait for axis container rotation to have been completed ⇒ set: marker (tag)
9 in the channel
WHEN $AN_AXCTSWA[<ID>] == TRUE DO SETM(9)
WAITMC(9, 1) ; Wait: Marker (tag) 9 of channel 1
Example 3: Implicit wait using the container spindle

; Program (again) the container spindle
; Internally, before starting the container spindle, the system waits for the end
; of the axis container rotation
M3 S100 ; Master spindle of the channel
Example 4: Implicit wait using the container axis

; Program the container axis incrementally without traversing path
; Internally, before starting the container axis, the system waits for the end
; of the axis container rotation
X=IC(0) ; Channel axis X
13.3.4 Configuration of a multi-spindle turning machine
Introduction
The following example describes the use of:
● Several NCUs in the NCU link group
● Flexible configuration with axis containers
Basic functions
Distributed systems
13.3 Examples
Machine description
● Over the circumference of a drum A (front-plane machining), the machine has distributed:
– 4 main spindles, HS1 to HS4
Each main spindle has the possibility of material feed (bars, hydraulic bar feed, axes:
STN1-STN4).
– 4 cross slides
– Each slide has two axes.
– Optionally, a powered tool S1-S4 can operate on each slide.
● Over the circumference of a drum B (back-plane machining), the machine has distributed:
– 4 counterspindles GS1 to GS4
– 4 cross slides
– Each slide has two axes.
– Optionally, a powered tool S5-S8 can operate on each slide.
– Each counterspindle can be moved through a linear axis, for example, for transferring
parts from the main spindle for the rear-plane machining in drum B. (Transfer axes. Axes:
ZG1-ZG4).
● Couplings:
– If drum A rotates, all of the main spindles of this drums are subordinated to a different
group of slides.
– If drum B rotates, all of the counterspindles and all of the transfer axes of this drum are
subordinated to a different group of slides.
– The rotations of drums A and B are autonomous.
– The rotations of drums A and B are limited to 270 degrees.
(range and twisting of supply cables)
Term: Position
Main spindle HSi and counterspindle GSi together with their slides characterize a position.
NCU assignment
The axes and spindles of a position (for this example) are each assigned to an NCU. One of the
NCUs, the master NCU, also controls the axes for rotating drums A and B. The result is 4 NCUs
with a maximum of the following axes:
Number of axes
Per NCUi the following axes/spindles must be configured:
Slide 1: Xi1, Zi1
2: Xi2, Zi2
Spindles: HSi, GSi, powered tools: S1, S2
Basic functions
Distributed systems
13.3 Examples
Transfer axis: ZGi

Bar feed: STNi.
For the master NCU, the two axes for rotating drums A and B are added to the above-
mentioned axes. The list shows that it would not be possible to configure the axis number for
a total of 4 positions via an NCU. (Limit 31 axes, 4 + 10 + 2 axes are required).
Axis container
With rotation of drums A/B, HSi, GSi, ZGi and STNi must be assigned to another NCU and must
therefore be configured as link axes in axis containers.
Front-plane machining: Drum V Back-plane machining: Drum H
NCUd
ZG4
STN4
HS4 Part transfer GS4
Position d
NCUc
STN3 ZG3
HS3 GS3
Part transfer
Position c
TRV TRH
NCUa
ZG1
HS1 GS1
Part transfer
Position a
STN1 NCUb
ZG2
Bar feed: HS2 GS2
STN2 Part transfer
Position b
Figure 13-21 Schematic diagram of main spindles HSi, countersp. GSi, bar feed axis STNi and transfer axes ZGi
Basic functions
Distributed systems
13.3 Examples
;&
=&
3RVLWLRQF
+6
=&
;&
Figure 13-22 Two slides per position can also work together on one spindle.
Note
The axes are given the following names in order to clarify the assignments of axes to slides and
positions:
Xij with i slide (1, 2), j position (A-D)
Zij with i slide (1, 2), j position (A-D)
Whereas the positions and their slides remain in one place, main spindles, counterspindles, bar
feed axes STN and transfer axes ZG move to new positions as the result of rotations of drums
V or H.
For example, the axes to be managed per NC when the slide is taken into account are as
follows for the configurations shown in the above diagrams:
Axes of master NCU
Table 13-1 Axes of master NCU: NCUa
Common axes Local axes Remark

TRV (drum V) Only master NCU
TRH (drum H) Only master NCU
X1A Slide 1
Z1A Slide 1
X2A Slide 2
Basic functions
Distributed systems
13.3 Examples
Common axes Local axes Remark

Z2A Slide 2
S1 Slide 1
S2 Slide 2
HS1 Axis container required
GS1 Axis container required
ZG1 Axis container required
STN1 Axis container required
4 8
Axes of the NCUb to NCUd

The NCUs that are not master NCUs have the same axes with the exception of the axes for the
drive for drums TRV and TRH. The letter designating the position must be replaced accordingly
for the NCU and axis name (a, A → b, B to d, D).
Configuration rules
The following rules were applied for the configuration described below:
● Main spindle, counterspindles and axes that are assigned to different NCUs through drum
rotation while they are operating as illustrated in the above diagram "Main spindle ..." must
be configured in an axis container.
(HSi, GSi, ZGi, STNi).
● All main spindles of drum A are in the same container (No. 1).
● All bar feed axes of drum A are in the same container (No. 2).
● All counterspindles of drum B are in the same container (No. 3).
● All transfer axes of drum B are in the same container (No. 4).
● The main spindles HSi and their counterspindles GSi as well as the transfer axes of the
counterspindle ZGi and the bar feed axes STNi of the main spindle are assigned as follows
for reasons of NCU equal load distribution:
NCUa HS1-STN1,
NCUb HS2-STN2, ... etc.
● Slide axes Xij, Zij are purely local axes with fixed NCU assignment.
● Slides are assigned to a dedicated channel of an NCU in each case.
Slides can therefore be moved autonomously.
Basic functions
Distributed systems
13.3 Examples
Configuration options
● Main spindles or counterspindles must be flexibly assigned to the slide.
● The speed of the main spindle and the counterspindle can be defined independently in each
position.
Exceptions:
During the parts change from front-plane machining in drum V to rear-plane machining in
drum H, the speeds of the main spindle and the counterspindle must be synchronized
(synchronous spindle coupling).
In cases where slide 2 also participates in front-plane machining so as to "support" slide 1,
the main spindle speed also applies to slide 2. Similarly if slide 1 participates in rear-plane
machining, the counterspindle speed also applies to slide 1.
Minor changes in speed

Due to the unavoidable time delays incurred in the processing of actual values, abrupt changes
in speed should be avoided during cross-NCU machining operations. See axis data and
signals.
Configuration for NCU1

Uniform use of channel axis names in the part programs:
S4: Main spindle
S3: Counterspindle
X1: Infeed axis
Z1: Longitudinal axis
S1: Driven tool
Z3: Transfer axis
TRV: Drum V for main spindle
TRH: Drum H for counterspindle
STN: Hydraulic bar feed
Axes highlighted in bold characterize the current channel as home channel for the axis in
conjunction with axis replacement.
Table 13-2 NCUa, position: a, channel: 1, slide: 1
Channel axis name ..._MA‐ $MN_ Container, slot Machine axis name
CHAX_USE AXCONF_LOGIC_MA‐ entry (string)
D CHAX_TAB
S4 1 AX1: CT1_SL1 11 HS1
NC1_AX1
S3 2 AX2: CT3_SL1 31 GS1
NC1_AX2
X1 3 AX3: X1A
Z1 4 AX4: Z1A
Basic functions
Distributed systems
13.3 Examples
D CHAX_TAB
Z3 5 AX5: CT4_SL1 41 ZG1
NC1_AX5
S1 6 AX6: WZ1A
STN 7 AX7: CT2_SL1 21 STN1
NC1_AX7
TRV 11 AX11: TRV
TRH 12 AX12: TRH
x2 *
z2 *
Table 13-3 NCUa, position: a, channel: 2, slide: 2
D CHAX_TAB
S4 1 AX1: CT1_SL1 11 HS1
NC1_AX1
S3 2 AX2: CT3_SL1 31 GS1
NC1_AX2
Z3 5 AX5: CT4_SL1 41 ZG1
NC1_AX5
STN 7 AX7: CT2_SL1 21 STN1
NC1_AX7
X2 8 AX8: X2A
Z2 9 AX9: Z2A
S1 10 AX10: WZ2A
x1 *
z1 *
Note
* due to program coordination via axis positions and 4-axis machining in one position
For the entry in a location of the axis container, the format: "NC1_AX.." is required, with the
meaning NC1 = NCU 1. In the above tables, NCUa is mapped to NC1_..., NCUb to NC2_..., etc.
Basic functions
Distributed systems
13.3 Examples
Further NCUs
The above listed configuration data must be specified accordingly for NCUb to NCUd. The
following must be observed:
● The axes TRA and TRB are only available for NCUa, channel 1.
● The container numbers are retained for the additional NCUs, as specified for the individual
axes.
● The slot numbers are as follows:
NCUb → 2
NCUc → 3
NCUd → 4.
● The machine axis names are as follows:
NCUb → HS2, GS2, ZG2, STN2
NCUc → HS3, GS3, ZG3, STN3
NCUd → HS4, GS4, ZG4, STN4.
Axis container
The information relating to containers given in Table 7-17 and the container entries of the
similarly configured NCUs, NCUb to NCUd, are specified in the following tables, sorted
according to containers and slots, as they have to be set in machine data:
MD12701 $MN_AXCT_AXCONF_ASSIGN_TAB1[slot]
...
MD12716 $MN_AXCT_AXCONF_ASSIGN_TAB16[slot]
whereby slots: 1-4 must be set for the 4 positions of a multi-spindle turning machine:
Note
For the machine data entry
$MN_AXC_AXCONF_ASSIGN_TABi[slot]
the values (without decimal point and machine axis name) that are entered under initial position
in the above tables must be set.
Table 13-4 Axis containers and their position-dependent contents for drum A
Container Slot Initial Situation Switch 1 Switch 2 Switch 3 Switch 4 =

(TRA 0°) (TRA 90°) (TRA 180°) (TRA 270°) (TRA 0°)
1 1 NC1_AX1, HS1 NC2_AX1, HS2 NC3_AX1, HS3 NC4_AX1, HS4 NC1_AX1, HS1
2 NC2_AX1, HS2 NC3_AX1, HS3 N4C_AX1, HS4 NC1_AX1, HS1 NC2_AX1, HS2
3 NC3_AX1, HS3 NC4_AX1, HS4 NC1_AX1, HS1 NC2_AX1, HS2 NC3_AX1, HS3
4 NC4_AX1, HS4 NC1_AX1, HS1 NC2_AX1, HS2 NC3_AX1, HS3 NC4_AX1, HS4
Basic functions
Distributed systems
13.3 Examples

(TRA 0°) (TRA 90°) (TRA 180°) (TRA 270°) (TRA 0°)
2 1 NC1_AX7, STN1 NC2_AX7, STN2 NC3_AX7, STN3 NC4_AX7 STN4 NC1_AX7, STN1
2 NC2_AX7, STN2 NC3_AX7, STN3 NC4_AX7, STN4 NC1_AX7, STN1 NC2_AX7, STN2
Drum movement 0° + 90° + 90° + 90° - 270°
STN4 STN3 STN2 STN1 STN4

HS4 HS3 HS2 HS1 HS4
HS3 HS2 HS1 HS4 HS3

HS1 HS4 HS3 HS2 HS1

HS2 HS1 HS4 HS3 HS2
Figure 13-23 Positions of drum A
Table 13-5 Axis containers and their position-dependent contents for drum B

(TRB 0°) (TRB 90°) (TRB 180°) (TRB 270°) (TRB 0°)
3 1 NC1_AX2, GS1 NC2_AX2, GS2 NC3_AX2, GS3 NC4_AX2, GS4 NC1_AX2, GS1
2 NC2_AX2, GS2 NC3_AX2, GS3 NC4_AX2, GS4 NC1_AX2, GS1 NC2_AX2, GS2
4 1 NC1_AX5, ZG1 NC2_AX5, ZG2 NC3_AX5, ZG3 NC4_AX5 ZG4 NC1_AX5, ZG1
2 NC2_AX5, ZG2 NC3_AX5, ZG3 NC4_AX5, ZG4 NC1_AX5, ZG1 NC2_AX5, ZG2
Basic functions
Distributed systems
13.3 Examples
13.3.5 Lead link axis
13.3.5.1 Configuration
Lead link axes

Master Following
axis axes
X Y Z X Y Z X Y Z
LAX 1 LAX 2 LAX 3 LAX 1 LAX 2 LAX 3 LAX 1 LAX 2 LAX 3
AX 1 AX 3
AX 1 AX 2 AX 3 AX 2 AX 3
NCU 1 NCU 2 NCU n
Coupled axes on leading axis NC1_AX3 with

Z(LAX1) on NCU2 and Z(LAX2) on NCUn as
lead link axes
Figure 13-24 NCU2 to NCUn use a lead link axis to enable coupling to the machine axis on NCU1 (NCU1-AX3).
The following example refers to the axis coupling section between Y(LAX2, AX2) as following
axis on NCU2 and Z(LAX3, NC1_AX3) as lead link axis.
Machine data
● The machine data of a leading value axis may only be loaded on the home NCU. From this
NCU, the relevant machine data are distributed to the other NCUs where a lead link axis has
been defined.
● Each lead link axis reduces the maximum number of axes that can be traversed on this NCU
by one axis.
Machine data for NCU1 (leading axis)

$MN_NCU_LINKNO = 1 1. or master NCU
$MN_MM_NCU_LINK_MASK = 1 NCU link active
$MN_MM_LINK_NUM_OF_MODULES= 2 Number of link modules
Basic functions
Distributed systems
13.3 Examples

$MN_MM_SERVO_FIFO_SIZE = 4 The size of the data buffer is increased to 4 between interpo‐
lation and position control
$MN_AXCONF_LOGIC_MACHAX_TAB[0] = "AX1"
$MN_AXCONF_MACHAX_NAME_TAB[0] = "XM1"
$MN_AXCONF_MACHAX_NAME_TAB[2] = "YM1"
$MA_AXCONF_ASSIGN_MASTER_NCK[ AX3 ] = 1
$MC_AXCONF_MACHAX_USED[0]=1 ; X
$MC_AXCONF_MACHAX_USED[1]=2 ; Y
$MC_AXCONF_MACHAX_USED[2]=3 ; Z
Machine data for NCU2 (following axis)

$MN_NCU_LINKNO = 2 2. NCU number
$MN_MM_NCU_LINK_MASK = 1 Activate link
$MN_MM_NUM_CURVE_TABS = 5 Number of curve tables
$MN_MM_LINK_NUM_OF_MODULES= 2 Number of link modules
$MN_MM_NUM_CURVE_SEGMENTS= 50
$MN_MM_NUM_CURVE_POLYNOMS = 100
$MN_MM_SERVO_FIFO_SIZE = 2 Size of the data buffer between interpolation and position
control (standard)
$MN_AXCONF_LOGIC_MACHAX_TAB[0] = "NC1_AX3" Lead link on NCU1/AX3
$MC_AXCONF_MACHAX_USED[0]=3 AX3 is machine axis of the 1st channel axis

$MC_AXCONF_MACHAX_USED[1]=2 AX2 is machine axis of the 2nd channel axis
$MC_AXCONF_MACHAX_USED[2]=1 AX3 on NCU1 is machine axis of the 3rd channel axis
Program for NCU1 (leading axis)

NCU1 traverses leading axis Z
Identifier for NCU2, that the leading axis of NCU1 is assigned: Link variable $A_DLB[0] = 1
Basic functions
Distributed systems
13.3 Examples
Identifier for NCU2, that the leading axis of NCU1 has been released: Link variable $A_DLB[0]
=0

N1000 R1 = 0 ; Initialize loop counter
N1004 G1 Z0 F1000 ; Traverse axis Z to the starting position
N1005 $A_DLB[0] = 1 ; Identifier for NCU2: Axis Z is assigned
LOOP10: ;
N1005 R1=R1+1 ; Increment loop counter
N1006 Z0.01 G91 ; Traversing the leading value axis Z
N1008 Z0.02 ; Traversing the leading value axis Z
N1010 Z0.03 ; Traversing the leading value axis Z
N1012 IF R1 < 10 GOTOB LOOP10 ;
N1098 $A_DLB[0] = 0 ; Identifier for NCU2: Axis Z is free
Program for NCU2 (following axis)

The program establishes a connection between leading axis movements on NCU1 and
following axis movements on NCU2 via a curve table. If the table has been defined, NCU2 goes
into the wait position (N2006) until NCU1 has assigned axis Z as the leading axis (N1005). The
coupling is activated (N2010) as soon as axis Z has been assigned as leading axis. The
coupling is kept until NCU1 has released axis Z as the leading axis.

N2000 CTABDEL(1) ; Initialize table 1
N2001 G04 F.1 ;
N2003 G0 Y0 Z0 ; Traverse axes Y, Z into the starting position
N2002 CTABDEF(Y, Z, 1, 0) ; Table definition ON
N2003 G1 X0 Y0 ; Intermediate point 1
N2004 G1 X100 Y200 ; Intermediate point 2
N2005 CTABEND ; Table definition OFF
LOOP20: ;
N2006 IF ($A_DLB[0] == 0) GOTOB LOOP20 ; Wait for NCU1
N2010 LEADON(Y,Z,1) ; => close coupling
LOOP25: ;
N2030 IF ($A_DLB[0] > 0) GOTOB LOOP25 ; Keep the coupling until NCU1 no longer traver-
ses the leading value axis
N2090 LEADOF(Y,Z) ; => open coupling
Basic functions
Distributed systems
13.4 Data lists
13.4 Data lists
13.4.1 Machine data

10002 AXCONF_LOGIC_MACHAX_TAB Logical NCU machine axis image
10065 POSCTRL_DESVAL_DELAY Position setpoint delay
10134 MM_NUM_MMC_UNITS Number of simultaneous MMC communication partners
12510 NCU_LINKNO NCU number in an NCU group
12520 LINK_TERMINATION NCU numbers for which bus terminating resistors are
active
12530 LINK_NUM_OF_MODULES Number of link modules
12701 AXCT_AXCONF_ASSIGN_TAB1 List of axes in the axis container
... ...
12716 AXCT_AXCONF_ASSIGN_TAB16
12750 AXCT_NAME_TAB List of axis container names
12760 AXCT_FUNCTION_MASK Functions for the axis container
18700 MM_SIZEOF_LINKVAR_DATA Size of the link variables memory
18720 MM_SERVO_FIFO_SIZE Size of the data buffer between interpolation and posi‐
tion controller
18780 MM_NCU_LINK_MASK, bit 0 Link communication activation

28160 MM_NUM_LINKVAR_ELEMENTS Number of write elements for the NCU link variables

30550 AXCONF_ASSIGN_MASTER_CHAN Default assignment between an axis and a channel
30554 AXCONF_ASSIGN_MASTER_NCU Initial setting defining which NCU generates setpoints
for the axis
30560 IS_LOCAL_LINK_AXIS Axis is a local link axis
32990 POCTRL_DESVAL_DELAY_INFO Current position setpoint delay
Basic functions
Distributed systems
13.4 Data lists
13.4.2 Setting data
13.4.2.1 General setting data
Number Identifier: $SA Description

41700 AXCT_SWWIDTH[container number] Axis container rotation setting
13.4.2.2 Axis/spindle-specific setting data
Number Identifier: $SA_ Description

43300 ASSIGN_FEED_PER_REV_SOURCE Rotational feedrate for positioning axes/spindles
13.4.3 Signals
13.4.3.1 Signals from NC
Signal name SINUMERIK 840D sl

MCP1 ready DB10.DBX104.0
MCP2 ready DB10.DBX104.1
HHU ready DB10.DBX104.2
NCU link active DB10.DBX107.6
HMI2-CPU ready (HMI connected to OPI or MPI) DB10.DBX108.1
HMI1-CPU at MPI ready DB10.DBX108.2
HMI1-CPU at OPI ready (standard connection) DB10.DBX108.3
13.4.3.2 Signals from HMI/PLC

ONL_REQUEST DB19.DBB100
Online request from HMI
ONL_CONFIRM DB19.DBB102
Acknowledgement from PLC for online request
PAR_CLIENT_IDENT DB19.DBB104
HMI writes its client identification (bus type, HMI bus ad‐
dress)
PAR_MMC_TYP DB19.DBB106
HMI type according to NETNAMES.INI: Main/secondary
operator panel/alarm server
Basic functions
Distributed systems
13.4 Data lists

PAR_MSTT_ADR DB19.DBB107
HMI writes address to the MCP to be activated
PAR_STATUS DB19.DBB108
PLC writes the online enable for the HMI (connection state)
PAR_Z_INFO DB19.DBB109
PLC writes additional information to the connection state
M_TO_N_ALIVE DB19.DBB110
Sign of life from the PLC to HMI using M to N block
13.4.3.3 General online interface

MMC1_CLIENT_IDENT DB19.DBB120
PLC writes PAR_CLIENT_IDENT to MMCx_CLI‐
ENT_IDENT, if HMI goes online.
MMC1_TYP DB19.DBB122
PLC writes PAR_MMC_TYP to MMCx_TYP, if HMI goes
online.
MMC1_MSTT_ADR DB19.DBB123
PLC writes PAR_MSTT_ADR to MMCx_MSTT_ADR, if HMI
goes online
MMC1_STATUS DB19.DBB124
Connection state, HMI and PLC write alternating, their re‐
quests/acknowledgements.
MMC1_Z_INFO DB19.DBB125
Additional information, connection state (pos./neg. acknowl‐
edgement, error messages, ...)
MMC1_SHIFT_LOCK DB19.DBX126.0
HMI switchover lock
MMC1_MSTT_SHIFT_LOCK DB19.DBX126.1
MCP switchover lock
MMC1_ACTIVE_REQ DB19.DBX126.2
HMI requests active operator mode
MMC1_ACTIVE_PERM DB19.DBX126.3
Enable from PLC to change the operator mode
MMC1_ACTIVE_CHANGED DB19.DBX126.4
HMI has changed the operator mode
MMC1_CHANGE_DENIED DB19.DBX126.5
HMI active/passive switchover denied
MMC2_CLIENT_IDENT DB19.DBB130
PLC writes PAR_CLIENT_IDENT to MMCx_CLI‐
ENT_IDENT, if HMI goes online.
Basic functions
Distributed systems
13.4 Data lists

MMC2_TYP DB19.DBB132
PLC writes PAR_MMC_TYP to MMCx_TYP, if HMI goes
online.
MMC2_MSTT_ADR DB19.DBB133
PLC writes PAR_MSTT_ADR to MMCx_MSTT_ADR, if HMI
goes online.
MMC2_STATUS DB19.DBB134
Connection state, HMI and PLC write alternating, their re‐
quests/acknowledgements.
MMC2_Z_INFO DB19.DBB135
Additional information, connection state (pos./neg. acknowl‐
edgement, error messages, ...)
MMC2_SHIFT_LOCK DB19.DBX136.0
HMI switchover lock
MMC2_MSTT_SHIFT_LOCK DB19.DBX136.1
MCP switchover lock
MMC2_ACTIVE_REQ DB19.DBX136.2
HMI requests active operator mode
MMC2_ACTIVE_PERM DB19.DBX136.3
Enable from PLC to change the operator mode
MMC2_ACTIVE_CHANGED DB19.DBX136.4
HMI has changed the operator mode
MMC2_CHANGE_DENIED DB19.DBX136.5
HMI active/passive switchover denied
13.4.3.4 Signals from axis/spindle

NCU link: Axis active DB31, ... DBX60.1 -
Axis-specific alarm DB31, ... DBX61.1 DB390x, DBX1.1
Axis ready DB31, ... DBX61.2 DB390x, DBX1.2
Axis container: Rotation active DB31, ... DBX62.7 -

$AN_AXCTSWE[axis] Supplies the slots of the axis container of the specified axis which are en‐
abled for the next axis container rotation
$AN_LAI_AX_IS_AXCTAX Contains the container axes of the logical machine axis image as bit field
$AN_LAI_AX_IS_LINKAX Contains the link axes of the logical machine axis image as bit field
$AN_LAI_AX_IS_LEADLINKAX Contains the lead-link axes of the logical machine axis image as bit field
Basic functions
Distributed systems
13.4 Data lists

$AN_LAI_AX_TO_MACHAX[axis] For the specified axis of the logical machine axis image, supplies the NCU-
ID and the axis number of the associated machine axis
$AN_LAI_AX_TO_IPO_NC_CHANAX[axis] For the specified axis of the logical machine axis image, supplies the chan‐
nel and channel axis number and/or the NCU and global axis number
$AN_IPO_CHANAX[global axis number] For the specified global axis number, supplies the channel and channel axis
number
$AA_MACHAX[axis] For the specified axis, supplies the NCU-ID and the machine axis number
$AA_IPO_NC_CHANAX[axis] For the specified axis, supplies the channel and channel axis number or
NCU-ID and the global axis number
$VA_IPO_NC_CHANAX[axis] For the specified machine axis, supplies the channel and channel axis
number or NCU-ID and global axis number
Detailed explanations regarding system variables can be obtained in:

Basic functions
Memory configuration 14
14.1 Introduction
Memory areas
The memory card of the NCU contains two memory areas for storing and managing the data of
the local persistent and non-persistent data of the NC:
● Static NC memory
That static NC memory contains the persistent NC data of the active and passive file system
(Page 799).
● Dynamic NC memory
The dynamic NC memory contains the non-persistent NC data, such as macros, local user
data, buffer memory, etc., generated dynamically by the NC.
Deterministic behavior
To ensure the behavior of the NC is deterministic in all machining situations, all memory areas
of the local static and dynamic NC memory have a settable, but permanent size.
Memory configuration
The memory areas of the local static and dynamic NC memory are set up when the control is
first started based on the standard settings of the machine data that configure the memory.
These settings are adequate in most cases.
Reconfiguration
If necessary, the memory configuration can be adapted to the user-specific requirements. The
necessary reconfiguration of the memory can result in loss of all user data in the static NC
memory. Therefore, after a change to memory-configuring machine data, the Alarm 4400: "MD
change results in reorganization of the buffered memory (loss of data!)" is displayed. Prior to
activating the machine data change or reconfiguration of the memory by an NC reset, a
commissioning archive should be created.
The memory configuration will be changed the next time the NC is started. Then the created
commissioning archive can be read-in for restoring the user data.
14.2 Active and passive file system

The user-specific data of the NC are stored in the local static NC memory. The memory area
contains the data of the active and passive file system.
Basic functions
14.2 Active and passive file system
Active file system

The active file system contains system data used to parameterize the NC. Essentially, these
are:
● Machine data
● Setting data
● Option data
● Global user data (GUD)
● Tool-offset/magazine data
● Protection areas
● R parameters
● Work offsets/FRAME
● Sag compensations
● Quadrant error compensation
● Leadscrew error compensation
The data of the active file system represent the current work data of the NC.
The view of the active file system is data-oriented.
Passive file system

The passive file system contains all local files loaded in the NC:
● Main programs
● Subprograms
● Workpieces
● Global user data and macro definition files (*.DEF)
● Standard cycles
● User cycles
● Comments
● Binary files (e.g. pictures, PDF documents)
The view of the passive file system is file-oriented.
Basic functions
14.3 Commissioning
14.3 Commissioning
14.3.1 Configuration
The configuration of the local static and dynamic NC memory is set and influenced by the
● Machine data that configure the memory:
– $MN_MM_... (NC-specific, memory-configuring machine data)
– $MC_MM_... (channel-specific memory-configuring machine data)
– $MA_MM_... (axis-specific memory-configuring machine data)
● Number of parameterized channels:
– MD10010 $MN_ASSIGN_CHAN_TO_MODE_GROUP (channel valid in mode group)
14.3.2 Reconfiguration
The first time the controller starts up, the sizes of the memory areas of the local NC memory are
set based on the default settings of the memory-configuring machine data. Generally, these
settings are sufficient for the operation of the control. If the memory areas of the local NC
memory are adapted because of special user-specific requirements, this results in
reconfiguration of the local NC memory. If the active and/or passive file system of the static NC
memory is affected, Alarm 4400 is displayed. The user should then back up the relevant data
by creating a commissioning archive on an external storage medium.
Alarm 4400 is displayed in the following cases:
● Memory-configuring machine data of the passive file system was changed
● Memory-configuring machine data of the active file system was changed and the function
"Automatic Memory Reconfiguration" (AMR) is not active
● Memory-configuring machine data of the active file system was changed, the AMR function
is active, but the data of the active file system cannot be buffered locally
NOTICE
Loss of data due to reconfiguration
A reconfiguration of the local static NC memory can result in the loss of the user data on the
active and/or passive file system. We therefore urgently recommend the back up of all relevant
data by creating a commissioning archive if Alarm 4400 is displayed, before activating the
changed memory configuration by an NC reset.
Basic functions
14.4 Configuration of the static user memory
"Automatic memory reconfiguration" function (AMR)
Active file system

The AMR function enables the reconfiguration of memory areas of the active file system
(Page 799) without having to create and then read back a commissioning archive to prevent the
loss of user data.
If the function is active, and memory-configuring machine data that affects the active file system
is modified, it is first checked whether all data of the active file system can be buffered locally.
If this is the case, the data of the active file system will be first buffered locally on activation of
the modified memory configuration by triggering a warm restart. The memory of the active file
system is then reconfigured. Finally, the buffered data are read back to the newly configured
active file system.
If the data of the active file system cannot be buffered, Alarm 4400 is displayed. Then, before
activating the machine data change, a commissioning archive containing the relevant user data
should be created. Refer to the paragraph "Further information".
Passive file system

If machine data that requires a reconfiguration of the passive file system is changed, Alarm
4400 will always be displayed, independent of the AMR function. Then, before activating the
machine data change, a commissioning archive containing the relevant user data should be
created.
If machine data that only requires a reconfiguration of the active file system is changed, the data
of the passive file system is retained.
Activation
The "Automatic memory reconfiguration" function (AMR) is activated via machine data:
MD17950 $MN_IS_AUTOMATIC_MEM_RECONFIG = TRUE
Further information
CNC Commissioning Manual: NC, PLC, drive; Saving and managing data
14.4.1 Division of the static NC memory
The static NC memory is used jointly by the system and by the user. The area available to the
user is defined as the static user memory. It contains the data from the active and passive file
system.
The following figure shows principle partitioning of the static NC memory:
Basic functions
0HPRU\XVHGE\WKHV\VWHP
8VHUF\FOHVSDUWSURJUDPV
ZRUNSLHFHV
8
0'01B00B8B),/(B0(0B6,=(
3DVVLYHILOH
V\VWHP
0'01B00B86(5B0(0B%8))(5('
0DFKLQHPDQXIDFWXUHUF\FOHV
0 0'01B00B0B),/(B0(0B6,=(
7RROPDQDJHPHQW
*OREDOXVHUGDWD
$FWLYHILOH
V\VWHP

6WDWLFXVHUPHPRU\

)UHHFDSDFLW\
0'01B,1)2B)5((B0(0B67$7,&
0HPRU\H[SDQVLRQRSWLRQ
Static-user-memory size
The size of the static user memory is displayed in machine data:
MD18230 $MN_MM_USER_MEM_BUFFERED
Parts of the static user memory
Passive file system

The following partitions of the passive file system are present in the static user memory:
Partition Storage of:

U (User) ● Files from the _N_CUS_DIR directory (user cycles)
● Part programs
● Workpieces
M (Manufacturer = Machine manufacturer) Files from the _N_CMA_DIR directory (Machine-manufac‐
turer cycles)
Basic functions
The free memory of the passive file system displayed in MD18060

$MN_INFO_FREE_MEM_STATIC can be divided among the partitions U and M. The setting is
made via the machine data:
● MD18352 $MN_MM_U_FILE_MEM_SIZE = <memory size for user data>
● MD18353 $MN_MM_M_FILE_MEM_SIZE = <memory size for machine manufacturer data>
Note
Partition S
Partition S (Siemens = Control manufacturer) of the passive file systems is in the dynamic NC
memory (Page 805).
Active file system

The memory of the active file system is divided into different areas (tool management, global
user data, ...). The size can be set for each area in the machine data that configures memory
(...MM_...).
Free static user memory

The free static user memory is displayed in the machine data:
MD18060 $MN_INFO_FREE_MEM_STATIC
Note
The memory required to expand the memory areas is displayed in the "Startup" area of the user
interface. This information enables the system startup engineer to estimate the actual memory
requirements for the planned expansion.
Memory expansion (option)

If additional static user memory is required, a memory expansion can be purchased as an
option.
You can use the additional memory as required to expand partitions U and/or M or to expand
the memory area of the active file system.
You can adjust the default memory division by increasing/decreasing individual memory areas
for each user.
Basic functions
14.5 Configuration of the dynamic user memory
Basic procedure:
1. Load standard machine data.
Further information
Commissioning Manual CNC: NC, PLC, drive; Requirements for commissioning
2. Determining the maximum possible size of the static user memory (including the optional
memory expansion):
MD18230 $MN_MM_USER_MEM_BUFFERED
3. Optional: modifying the size of the static user memory:
– MD19250 $ON_USER_MEM_BUFFERED
– Perform a power-on reset.
4. Optional: setting the size partitions U and M:
– MD18352 $MN_MM_U_FILE_MEM_SIZE
– MD18353 $MN_MM_M_FILE_MEM_SIZE
5. Optional: setting up additional channels of the control:
MD10010 $MC_ASSIGN_CHAN_TO_MODE_GROUP
6. Optional: setting the size of the memory areas of the active file system (tool management,
global user data, ...):
– Determining the free static user memory:
MD18060 $MN_INFO_FREE_MEM_STATIC
– Setting the size of the memory areas of the active file system in the machine data that
configure memory (...MM_...).
7. Perform a power-on reset.
The memory will be reconfigured the next time the control starts up.
Further information
● List Manual Machine Data and Parameters
14.5.1 Division of the dynamic NC memory
The dynamic NC memory is used jointly by the system and by the user. The area available to
the user is defined as the dynamic user memory.
The figure below shows the principle division of the dynamic NC memory:
Basic functions
'\QDPLFPHPRU\XVHGE\WKHV\VWHP
6 6LHPHQVF\FOHV
0DFURV
0LVFHOODQHRXVIXQFWLRQVDQGSDUDPHWHUV
0'01B00B86(5B0(0B'<1$0,&
/RFDOXVHUGDWD
+DVKWDEOHV
7DVNV
5HRUJIXQFWLRQ
,QWHUSRODWLRQEXIIHU
'\QDPLFXVHUPHPRU\
&RPSLOHF\FOHV
3URWHFWLRQDUHDV
)UHHFDSDFLW\
0'01B,1)2B)5((B0(0B'<1$0,&
Dynamic-user-memory size
The size of the dynamic user memory is displayed in machine data:
MD18210 $MN_MM_USER_MEM_DYNAMIC
Parts of the dynamic user memory
Passive file system

Partition S of the passive file system is in the dynamic user memory:
Partition Storage of:

S (Siemens = Control manufacturer) Files from the _N_CST_DIR directory (Siemens cycles)
The size of partition S is preset and cannot be modified.
User data areas

The dynamic user memory contains the user data areas for saving the non-persistent NC data
dynamically generated by the NC, e.g. macros, local user data, buffer, etc.
Basic functions
Dynamic user memory still available

The dynamic memory still available is shown in machine data:
MD18050 $MN_INFO_FREE_MEM_DYNAMIC
The value of the machine data specifies how much memory is available per channel for
enlarging the user data areas.
You can adjust the default memory division by increasing/decreasing individual memory areas
for each user.
Basic procedure:
1. Determining the size of the free dynamic user memory:
MD18050 $MN_INFO_FREE_MEM_DYNAMIC
2. Optional: Setting the size of the memory areas of the dynamic user memory in the machine
data that configure memory (...MM_...):
3. Perform a power-on reset.
The memory will be reconfigured the next time the control starts up.
For further information, see Machine Data and Parameters List Manual.
14.6.1 Depending on the number of channels and tool carriers

If the number of channels is increased, then it may also be necessary to increase the number
of tool carriers.
The number of tool carriers available in the control has to be set according to the following rule:
MD18088 $MN_NUM_TOOL_CARRIER =
<Highest number of tool carriers in one channel> *
<Number of parameterized channels>
The tool carriers are distributed in the control equally among the available channels.
Example
3 channels are parameterized in the NC. The number of tool carriers required in the channels
is:
1. Channel: 3 ⇒ maximum value
2. Channel: 2
3. Channel: 1
Basic functions
14.7 Data lists
MD18088 = <Highest number of tool carriers in one channel> * <Number of

channels> = 3 * 3 = 9
3 tool carriers are thus assigned to each channel
14.6.2 Subsequent reduction of the number of channels and/or axes

Once an increase in the number of channels and/or axes has been made effective in the control
by a warm restart, it cannot then be reversed if a setup archive is to be created for this control.
If such a setup archive is loaded into a control, the process is interrupted by an alarm.
Differences between the dynamic and static memory of the NC

● Dynamic memory: The internal memory requirement increases if the numbers of channels
and axes are increased.
● Static memory: The internal memory requirement increases only if the number of channels
is increased.
14.7 Data lists
14.7.1 Machine data

10134 MM_NUM_MMC_UNITS Number of simultaneous HMI communication partners
10850 MM_EXTERN_MAXNUM_OEM_GCODES Maximum number of OEM-G commands
10880 MM_EXTERN_CNC_SYSTEM Definition of the control system to be adapted
10881 MM_EXTERN_GCODE_SYSTEM ISO_3 Mode: GCodeSystem
18050 INFO_FREE_MEM_DYNAMIC Free-dynamic-memory display data
18060 INFO_FREE_MEM_STATIC Free-static-memory display data
18070 INFO_FREE_MEM_DPR Display data for free memory in
dual-port RAM
18072 INFO_FREE_MEM_CC_MD Displays memory available in the CC-MD memory
18078 MM_MAX_NUM_OF_HIERARCHIES Maximum number of definable magazine-location-type
hierarchies
18079 MM_MAX_HIERARCHY_ENTRIES Maximum permissible number of entries in a magazine-
location-type hierarchy
18080 MM_TOOL_MANAGEMENT_MASK Mask for reserving memory for tool management
18082 MM_NUM_TOOL Number of tools managed by NC
18084 MM_NUM_MAGAZINE Number of magazines managed by NC
Basic functions
14.7 Data lists

18086 MM_NUM_MAGAZINE_LOCATION Number of magazine locations
18088 MM_NUM_TOOL_CARRIER Maximum number of definable toolholders
18090 MM_NUM_CC_MAGAZINE_PARAM Compile-cycle tool management:
quantity of magazine data
18092 MM_NUM_CC_MAGLOC_PARAM Compile-cycle tool management:
quantity of magazine-location data
18094 MM_NUM_CC_TDA_PARAM Compile-cycle tool management: quantity of TDA data
18096 MM_NUM_CC_TOA_PARAM Compile-cycle tool management: quantity of TOA data
18098 MM_NUM_CC_MON_PARAM Compile-cycle tool management:
quantity of monitor data
18100 MM_NUM_CUTTING_EDGES_IN_TOA Number of tool offsets in NC
18102 MM_TYPE_OF_CUTTING_EDGE Type of D-number programming
18104 MM_NUM_TOOL_ADAPTER Tool adapter in TO area
18105 MM_MAX_CUTTING_EDGE_NO Maximum value of D number
18106 MM_MAX_CUTTING_EDGE_PERTOOL Maximum number of D numbers per tool
18108 MM_NUM_SUMCORR Additive offsets in the TO area
18110 MM_MAX_SUMCORR_PER_CUTTEDGE Maximum number of sum offsets per cutting edge
18112 MM_KIND_OF_SUMCORR Properties of additive offsets in the TO area
18114 MM_ENABLE_TOOL_ORIENT Assign orientation to cutting edges
18116 MM_NUM_TOOL_ENV Number of tool environments in TO area
18118 MM_NUM_GUD_MODULES Number of GUD modules
18120 MM_NUM_GUD_NAMES_NCK Number of global user variables
18130 MM_NUM_GUD_NAMES_CHAN Number of channel-specific user variables
18150 MM_GUD_VALUES_MEM Memory space for global user variables
18160 MM_NUM_USER_MACROS Number of macros
18170 MM_NUM_MAX_FUNC_NAMES Number of miscellaneous functions
18180 MM_NUM_MAX_FUNC_PARAM Number of additional parameters
18190 MM_NUM_PROTECT_AREA_NCK Number of protection zones in NC
18200 MM_NUM_CCS_MAGAZINE_PARAM Number of Siemens OEM magazine data
18201 MM_TYPE_CCS_MAGAZINE_PARAM Siemens OEM magazine data type
18202 MM_NUM_CCS_MAGLOC_PARAM Number of Siemens OEM magazine location data
18203 MM_TYPE_CCS_MAGLOC_PARAM Siemens OEM magazine location data type
18204 MM_NUM_CCS_TDA_PARAM Number of Siemens OEM tool data
18205 MM_TYPE_CCS_TDA_PARAM Siemens OEM tool data type
18206 MM_NUM_CCS_TOA_PARAM Number of Siemens OEM data per cutting edge
18207 MM_TYPE_CCS_TOA_PARAM Siemens OEM data type per cutting edge
18208 MM_NUM_CCS_MON_PARAM Number of Siemens OEM monitor data
18209 MM_TYPE_CCS_MON_PARAM Siemens OEM monitor data type
18210 MM_USER_MEM_DYNAMIC User memory for non-persistent data
18220 MM_USER_MEM_DPR User memory in dual-port RAM
18230 MM_USER_MEM_BUFFERED User memory for persistent data
18231 MM_USER_MEM_BUFFERED_TYPEOF Data-buffer technology
Basic functions
14.7 Data lists

18232 MM_ACTFILESYS_LOG_FILE_MEM System: Log-file size
18238 MM_CC_MD_MEM_SIZE Memory size for compile cycle machine data
18240 MM_LUD_HASH_TABLE_SIZE Hash-table size for user variables
18242 MM_MAX_SIZE_OF_LUD_VALUE Maximum LUD-variable array size
18250 MM_CHAN_HASH_TABLE_SIZE Hash-table size for channel-specific data
18260 MM_NCK_HASH_TABLE_SIZE Hash-table size for global data
18270 MM_NUM_SUBDIR_PER_DIR Number of subdirectories
18280 MM_NUM_FILES_PER_DIR Number of files per directory
18290 MM_FILE_HASH_TABLE_SIZE Hash-table size for files in a directory
18300 MM_DIR_HASH_TABLE_SIZE Hash-table size for subdirectories
18310 MM_NUM_DIR_IN_FILESYSTEM Number of directories in passive file system
18320 MM_NUM_FILES_IN_FILESYSTEM Number of files in passive file system
18332 MM_FLASH_FILE_SYSTEM_SIZE Size of flash file system on PCNC
18342 MM_CEC_MAX_POINTS Maximum table size for sag compensation
18350 MM_USER_FILE_MEM_MINIMUM Minimum part-program memory
18352 MM_U_FILE_MEM_SIZE End-user memory for part programs/cycles/files
18353 MM_M_FILE_MEM_SIZE Memory size for cycles/files of the machine manufac‐
turer
18354 MM_S_FILE_MEM_SIZE Memory size for cycles/files of the NC manufacturer
18355 MM_T_FILE_MEM_SIZE Memory size for temporary files
18356 MM_E_FILE_MEM_SIZE Memory size for external files
18360 MM_EXT_PROG_BUFFER_SIZE FIFO buffer size for execution from an external source
18362 MM_EXT_PROG_NUM Number of program levels that can be processed si‐
multaneously from external
18370 MM_PROTOC_NUM_FILES Maximum number of log files
18371 MM_PROTOC_NUM_ETPD_STD_LIST Number of standard ETPD data lists
18372 MM_PROTOC_NUM_ETPD_OEM_LIST Number of ETPD OEM data lists
18373 MM_PROTOC_NUM_SERVO_DATA Number of servo data for log
18374 MM_PROTOC_FILE_BUFFER_SIZE Log-file buffer size
18375 MM_PROTOC_SESS_ENAB_USER User-enabled for sessions
18390 MM_COM_COMPRESS_METHOD Supported compression method
18400 MM_NUM_CURVE_TABS Number of curve tables (persistent)
18402 MM_NUM_CURVE_SEGMENTS Number of curve segments (persistent)
18403 MM_NUM_CURVE_SEG_LIN Number of linear curve segments (persistent)
18404 MM_NUM_CURVE_POLYNOMS Number of curve table polynomials (persistent)
18406 MM_NUM_CURVE_TABS_DRAM Number of curve tables (non-persistent)
18408 MM_NUM_CURVE_SEGMENTS_DRAM Number of curve segments (non-persistent)
18409 MM_NUM_CURVE_SEG_LIN_DRAM Number of linear curve segments (non-persistent)
18410 MM_NUM_CURVE_POLYNOMS_DRAM Number of curve table polynomials (non-persistent)
18450 MM_NUM_CP_MODULES Maximum number of CP modules
18452 MM_NUM_CP_MODUL_LEAD Maximum number of leading values per CP coupling
module
Basic functions
14.7 Data lists

18500 MM_EXTCOM_TASK_STACK_SIZE Stack size of external communication task (non-persis‐
tent)
18502 MM_COM_TASK_STACK_SIZE Stack size in Kbytes of communication task (non-per‐
sistent)
18510 MM_SERVO_TASK_STACK_SIZE Stack size of servo task (non-persistent)
18512 MM_IPO_TASK_STACK_SIZE Stack size of IPO task (non-persistent)
18520 MM_DRIVE_TASK_STACK_SIZE Stack size of drive task (non-persistent)
18540 MM_PLC_TASK_STACK_SIZE Stack size of the PLC task (non-persistent)
18600 MM_FRAME_FINE_TRANS Fine offset for FRAME (persistent)
18601 MM_NUM_GLOBAL_USER_FRAMES Number of globally predefined user frames (persistent)
18602 MM_NUM_GLOBAL_BASE_FRAMES Number of global basic frames (persistent)
18660 MM_NUM_SYNACT_GUD_REAL Number of configurable real-type GUD variables
18661 MM_NUM_SYNACT_GUD_INT Number of configurable integer-type GUD variables
18662 MM_NUM_SYNACT_GUD_BOOL Number of configurable Boolean-type GUD variables
18663 MM_NUM_SYNACT_GUD_AXIS Number of configurable axis-type GUD variables
18664 MM_NUM_SYNACT_GUD_CHAR Configurable char-type GUD variable
18665 MM_NUM_SYNACT_GUD_STRING Configurable STRING-type GUD variable
18700 MM_SIZEOF_LINKVAR_DATA Size of the NCU link variable memory
18710 MM_NUM_AN_TIMER Number of global time variables for synchronized ac‐
tions
18720 MM_SERVO_FIFO_SIZE Setpoint for buffer size between IPO and closed-loop
position control
18780 MM_NCU_LINK_MASK Activation of NCU link communication
18781 NCU_LINK_CONNECTIONS Number of internal link connections
18782 MM_LINK_NUM_OF_MODULES Number of NCU link modules
18790 MM_MAX_TRACE_LINK_POINTS Size of trace data buffer for NCU link
18792 MM_TRACE_LINK_DATA_FUNCTION Specifies the contents of NCU link files
18794 MM_TRACE_VDI_SIGNAL Trace specification of VDI signals
18800 MM_EXTERN_LANGUAGE Activation of external NC languages
18860 MM_MAINTENANCE_MON Activate recording of maintenance data
18870 MM_MAXNUM_KIN_CHAINS Maximum number of trains
18880 MM_MAXNUM_KIN_CHAIN_ELEM Maximum number of train elements
18890 MM_MAXNUM_3D_PROT_AREAS Maximum number of elements in 3D protection zones
18892 MM_MAXNUM_3D_PROT_AREA_ELEM Maximum number of protection-zone elements
18894 MM_MAXNUM_3D_PROT_GROUPS Maximum number of protection-zone groups
18896 MM_MAXNUM_3D_COLLISION Maximum number of temporary memory locations for
collision check
Basic functions
14.7 Data lists

20096 T_M_ADDRESS_EXIT_SPINO Spindle number as address extension
27900 REORG_LOG_LIMIT Percentage of IPO buffer for log-file enable
28000 MM_REORG_LOG_FILE_MEM Memory size for REORG
28010 MM_NUM_REORG_LUD_MODULES Number of modules for local user variables with RE‐
ORG
28020 MM_NUM_LUD_NAMES_TOTAL Number of local user variables
28040 MM_LUD_VALUES_MEM Memory size for local user variables
28050 MM_NUM_R_PARAM Number of channel-specific R parameters
28060 MM_IPO_BUFFER_SIZE Number of NC blocks in the IPO buffer
28070 MM_NUM_BLOCKS_IN_PREP Number of blocks for block preparation
28080 MM_NUM_USER_FRAMES Number of settable frames
28081 MM_NUM_BASE_FRAMES Number of basic frames (persistent)
28082 MM_SYSTEM_FRAME_MASK System frames (persistent)
28083 MM_SYSTEM_DATAFRAME_MASK System frames (persistent)
28085 MM_LINK_TOA_UNIT Allocation of a TO unit to a channel
28090 MM_NUM_CC_BLOCK_ELEMENTS Number of block elements for compile cycles
28100 MM_NUM_CC_BLOCK_USER_MEM Size of block memory for compile cycles
28105 MM_NUM_CC_HEAP_MEM Heap memory in KB for compile cycle applications (non-
persistent)
28150 MM_NUM_VDIVAR_ELEMENTS Number of elements for writing PLC variables
28160 MM_NUM_LINKVAR_ELEMENTS Number of write elements for the NCU link variables
28180 MM_MAX_TRACE_DATAPOINTS Size of trace data buffer
28200 MM_NUM_PROTECT_AREA_CHAN Number of modules for channel-specific protection
zones
28210 MM_NUM_PROTECT_AREA_ACTIVE Number of simultaneously active protection zones
28212 MM_NUM_PROTECT_AREA_CONTOUR Elements for active protection zones (non-persistent)
28250 MM_NUM_SYNC_ELEMENTS Number of elements for expressions in synchronized
actions
28252 MM_NUM_FCTDEF_ELEMENTS Number of FCTDEF elements
28254 MM_NUM_AC_PARAM Dimension of $AC_PARAM.
28255 MM_BUFFERED_AC_PARAM $AC_PARAM[...] (persistent)
28256 MM_NUM_AC_MARKER Dimension of $AC_MARKER
28257 MM_BUFFERED_AC_MARKER $AC_MARKER[...] (persistent)
28258 MM_NUM_AC_TIMER Number of $AC_TIMER time variables (non-persistent)
28274 MM_NUM_AC_SYSTEM_PARAM Number of $AC_SYSTEM_ PARAM for motion-syn‐
chronous actions
28276 MM_NUM_AC_SYSTEM_MARKER Number of $AC_SYSTEM_ MARKER for motion-syn‐
chronous actions
28290 MM_SHAPED_TOOLS_ENABLE Enable tool-radius compensation for contour tools
28300 MM_PROTOC_USER_ACTIVE Activate logging for a user
28301 MM_PROTOC_NUM_ETP_OEM_TYP Number of ETP OEM event types
Basic functions
14.7 Data lists

28302 MM_PROTOC_NUM_ETP_STD_TYP Number of ETP standard event types
28400 MM_ABSBLOCK Activate block display with absolute values
28402 MM_ABSBLOCK_BUFFER_CONF Dimension size of upload buffer
28450 MM_TOOL_DATA_CHG_BUFF_SIZE Buffer for tool data changes (non-persistent)
28500 MM_PREP_TASK_STACK_SIZE Stack size of preparatory task
28520 MM_MAX_AXISPOLY_PER_BLOCK Maximum number of axis polynomials per block
28530 MM_PATH_VELO_SEGMENTS Number of memory chips for limiting the tool-path ve‐
locity
28535 MM_FEED_PROFILE_SEGMENTS Number of memory chips for feed profiles
28540 MM_ARCLENGTH_SEGMENTS Number of memory chips for displaying the arc length
function
28560 MM_SEARCH_RUN_RESTORE_MODE Restore data after a simulation
28580 MM_ORIPATH_CONFIG Setting for ORIPATH tool orientation trajectory referred
to path

38000 MM_ENC_COMP_MAX_POINTS Number of interpolation points with interpolatory com‐
pensation
38010 MM_QEC_MAX_POINTS Number of values for quadrant-error compensation
38020 MM_CPREC_FIR_POINTS Number of points for characteristic approximation of
FIR filters for CPRECON
Basic functions
14.7 Data lists
Basic functions
Appendix A
A.1 List of abbreviations
A
O Output
ADI4 (Analog drive interface for 4 axes)
AC Adaptive Control
ALM Active Line Module
ARM Rotating induction motor
AS Automation system
ASCII American Standard Code for Information Interchange: American coding standard for
the exchange of information
ASIC Application-Specific Integrated Circuit: User switching circuit
ASUB Asynchronous subprogram
AUXFU Auxiliary function: Auxiliary function
STL Statement List
UP User Program
B
OP Operating Mode
BAG Mode group
BCD Binary Coded Decimals: Decimal numbers encoded in binary code
BERO Contact-less proximity switch
BI Binector Input
BICO Binector Connector
BIN BINary files: Binary files
BIOS Basic Input Output System
BCS Basic Coordinate System
BO Binector Output
OPI Operator Panel Interface
C
CAD Computer-Aided Design
CAM Computer-Aided Manufacturing
CC Compile Cycle: Compile cycles
CEC Cross Error Compensation
CI Connector Input
CNC Computerized Numerical Control: Computer-Supported Numerical Control
Basic functions
Appendix
C
CO Connector Output
CoL Certificate of License
COM Communication
CPA Compiler Projecting Data: Configuring data of the compiler
CRT Cathode Ray Tube: picture tube
CSB Central Service Board: PLC module
CU Control Unit
CP Communication Processor
CPU Central Processing Unit: Central processing unit
CR Carriage Return
CST Configured Stop: Configured stop
CTS Clear To Send: Ready to send signal for serial data interfaces
CUTCOM Cutter radius Compensation: Tool radius compensation
D
DAC Digital-to-Analog Converter
DB Data Block (PLC)
DBB Data Block Byte (PLC)
DBD Data Block Double word (PLC)
DBW Data Block Word (PLC)
DBX Data block bit (PLC)
DDE Dynamic Data Exchange
DDS Drive Data Set: Drive data set
DIN Deutsche Industrie Norm
DIO Data Input/Output: Data transfer display
DIR Directory: Directory
DLL Dynamic Link Library
DO Drive Object
DPM Dual Port Memory
DPR Dual Port RAM
DRAM Dynamic memory (non-buffered)
DRF Differential Resolver Function: Differential revolver function (handwheel)
DRIVE-CLiQ Drive Component Link with IQ
DRY Dry Run: Dry run feedrate
DSB Decoding Single Block: Decoding single block
DSC Dynamic Servo Control / Dynamic Stiffness Control
DW Data Word
DWORD Double Word (currently 32 bits)
Basic functions
Appendix
E
I Input
EES Execution from External Storage
I/O Input/Output
ENC Encoder: Actual value encoder
EFP Compact I/O module (PLC I/O module)
ESD Electrostatic Sensitive Devices
EMC ElectroMagnetic Compatibility
EN European standard
ENC Encoder: Actual value encoder
EnDat Encoder interface
EPROM Erasable Programmable Read Only Memory: Erasable, electrically programmable
read-only memory
ePS Network Services Services for Internet-based remote machine maintenance
EQN Designation for an absolute encoder with 2048 sine signals per revolution
ES Engineering System
ESR Extended Stop and Retract
ETC ETC key ">"; softkey bar extension in the same menu
F
FB Function Block (PLC)
FC Function Call: Function Block (PLC)
FEPROM Flash EPROM: Read and write memory
FIFO First In First Out: Memory that works without address specification and whose data is
read in the same order in which they was stored
FIPO Fine interpolator
FPU Floating Point Unit: Floating Point Unit
CRC Cutter Radius Compensation
FST Feed Stop: Feedrate stop
FBD Function Block Diagram (PLC programming method)
FW Firmware
G
GC Global Control (PROFIBUS: Broadcast telegram)
GDIR Global part program memory
GEO Geometry, e.g. geometry axis
GIA Gear Interpolation dAta: Gear interpolation data
GND Signal Ground
GP Basic program (PLC)
GS Gear Stage
GSD Device master file for describing a PROFIBUS slave
Basic functions
Appendix
G
GSDML Generic Station Description Markup Language: XML-based description language for
creating a GSD file
GUD Global User Data: Global user data
H
HEX Abbreviation for hexadecimal number
AuxF Auxiliary function
HLA Hydraulic linear drive
HMI Human Machine Interface: SINUMERIK user interface
MSD Main Spindle Drive
HW Hardware
I
IBN Commissioning
ICA Interpolatory compensation
IM Interface Module: Interconnection module
IMR Interface Module Receive: Interface module for receiving data
IMS Interface Module Send: Interface module for sending data
INC Increment: Increment
INI Initializing Data: Initializing data
IPO Interpolator
ISA Industry Standard Architecture
ISO International Standardization Organization
J
JOG Jogging: Setup mode
K
KV Gain factor of control loop
Kp Proportional gain
KÜ Transformation ratio
LAD Ladder Diagram (PLC programming method)
L
LAI Logic Machine Axis Image: Logical machine axes image
LAN Local Area Network
LCD Liquid Crystal Display: Liquid crystal display
LED Light Emitting Diode: Light-emitting diode
LF Line Feed
Basic functions
Appendix
L
PMS Position Measuring System
LR Position controller
LSB Least Significant Bit: Least significant bit
LUD Local User Data: User data (local)
M
MAC Media Access Control
MAIN Main program: Main program (OB1, PLC)
MB Megabyte
MCI Motion Control Interface
MCIS Motion Control Information System
MCP Machine Control Panel: Machine control panel
MD Machine Data
MDA Manual Data Automatic: Manual input
MDS Motor Data Set: Motor data set
MSGW Message Word
MCS Machine Coordinate System
MM Motor Module
MPF Main Program File: Main program (NC)
MCP Machine control panel
N
NC Numerical Control: Numerical control with block preparation, traversing range, etc.
NCU Numerical Control Unit: NC hardware unit
NRK Name for the operating system of the NC
IS Interface Signal
NURBS Non-Uniform Rational B-Spline
WO Work Offset
NX Numerical Extension: Axis expansion board
O
OB Organization block in the PLC
OEM Original Equipment Manufacturer
OP Operator Panel: Operating equipment
OPI Operator Panel Interface: Interface for connection to the operator panel
OPT Options: Options
OLP Optical Link Plug: Fiber optic bus connector
OSI Open Systems Interconnection: Standard for computer communications
Basic functions
Appendix
P
PIQ Process Image Output
PII Process Image Input
PC Personal Computer
PCIN Name of the SW for data exchange with the control
PCMCIA Personal Computer Memory Card International Association:
Plug-in memory card standardization
PCU PC Unit: PC box (computer unit)
PG Programming device
PKE Parameter identification: Part of a PIV
PIV Parameter identification: Value (parameterizing part of a PPO)
PLC Programmable Logic Control: Adaptation control
PN PROFINET
PNO PROFIBUS user organization
PO POWER ON
POU Program Organization Unit
POS Position/positioning
POSMO A Positioning Motor Actuator: Positioning motor
POSMO CA Positioning Motor Compact AC: Complete drive unit with integrated power and control
module as well as positioning unit and program memory; AC infeed
POSMO CD Positioning Motor Compact DC: Like CA but with DC infeed
POSMO SI Positioning Motor Servo Integrated: Positioning motor, DC infeed
PPO Parameter Process data Object: Cyclic data telegram for PROFIBUS DP transmission
and "Variable speed drives" profile
PPU Panel Processing Unit (central hardware for a panel-based CNC, e.g SINUMERIK
828D)
PROFIBUS Process Field Bus: Serial data bus
PRT Program Test
PSW Program control word
PTP Point-To-Point: Point-To-Point
PUD Program global User Data: Program-global user variables
PZD Process data: Process data part of a PPO
Q
QEC Quadrant Error Compensation
R
RAM Random Access Memory: Read/write memory
REF REFerence point approach function
REPOS REPOSition function
RISC Reduced Instruction Set Computer: Type of processor with small instruction set and
ability to process instructions at high speed
ROV Rapid Override: Input correction
Basic functions
Appendix
R
RP R Parameter, arithmetic parameter, predefined user variable
RPA R Parameter Active: Memory area in the NC for R parameter numbers
RPY Roll Pitch Yaw: Rotation type of a coordinate system
RTLI Rapid Traverse Linear Interpolation: Linear interpolation during rapid traverse motion
RTS Request To Send: Control signal of serial data interfaces
RTCP Real Time Control Protocol
S
SA Synchronized Action
SBC Safe Brake Control: Safe Brake Control
SBL Single Block: Single block
SBR Subroutine: Subprogram (PLC)
SD Setting Data
SDB System Data Block
SEA Setting Data Active: Identifier (file type) for setting data
SERUPRO SEarch RUn by PROgram test: Block search, program test
SFB System Function Block
SFC System Function Call
SH Safe standstill
SIM Single in Line Module
SK Softkey
SKP Skip: Function for skipping a part program block
SLM Synchronous Linear Motor
SM Stepper Motor
SMC Sensor Module Cabinet Mounted
SME Sensor Module Externally Mounted
SMI Sensor Module Integrated
SPF Sub Routine File: Subprogram (NC)
PLC Programmable Logic Controller
SRAM Static RAM (non-volatile)
TNRC Tool Nose Radius Compensation
SRM Synchronous Rotary Motor
LEC Leadscrew Error Compensation
SSI Serial Synchronous Interface: Synchronous serial interface
SSL Block search
STW Control word
GWPS Grinding Wheel Peripheral Speed
SW Software
SYF System Files: System files
SYNACT SYNchronized ACTion: Synchronized Action
Basic functions
Appendix
T
TB Terminal Board (SINAMICS)
TCP Tool Center Point: Tool tip
TCP/IP Transport Control Protocol / Internet Protocol
TCU Thin Client Unit
TEA Testing Data Active: Identifier for machine data
TIA Totally Integrated Automation
TM Terminal Module (SINAMICS)
TO Tool Offset: Tool offset
TOA Tool Offset Active: Identifier (file type) for tool offsets
TRANSMIT Transform Milling Into Turning: Coordination transformation for milling operations on a
lathe
TTL Transistor-Transistor Logic (interface type)
TZ Technology cycle
U
UFR User Frame: Work offset
SR Subprogram
USB Universal Serial Bus
UPS Uninterruptible Power Supply
V
VDI Internal communication interface between NC and PLC
VDI Verein Deutscher Ingenieure [Association of German Engineers]
VDE Verband Deutscher Elektrotechniker [Association of German Electrical Engineers]
VI Voltage Input
VO Voltage Output
FDD Feed Drive
W
SAR Smooth Approach and Retraction
WCS Workpiece Coordinate System
T Tool
TLC Tool Length Compensation
WOP Workshop-Oriented Programming
WPD Workpiece Directory: Workpiece directory
TRC Tool Radius Compensation
T Tool
TO Tool Offset
TM Tool Management
TC Tool change
Basic functions
Appendix
A.2 Documentation overview
X
XML Extensible Markup Language
Z
WOA Work Offset Active: Identifier for work offsets
ZSW Status word (of drive)
A.2 Documentation overview

You will find extensive documentation on the functions of SINUMERIK 840D sl from version 4.8
SP4 at 840D sl documentation overview (https://support.industry.siemens.com/cs/ww/en/view/
109766213).
You can display the documents or download them in PDF or HTML5 format.
The documentation is divided into the following categories:
● User: Operating
● User: Programming
● Manufacturer/Service: Configure
● Manufacturer/Service: Commissioning
● Manufacturer/Service: Functions
● Safety Integrated
● SINUMERIK Integrate / MindApp
● Information and training
Basic functions
Appendix
A.3 Available IPCs
A.3 Available IPCs
IPCs recommended for SINUMERIK
Panel IPC
IPC 477E 22" Win 7 6AV7241-3YA04-0FA0
IPC 477E 24" Win 7 6AV7241-5SB04-0FA0
IPC 477E 15" Win10 6AV7241-1WA07-0FA0
IPC 477E 19" Win10 6AV7241-3XB07-0FA0
IPC 477E 22" Win10 6AV7241-3YA07-0FA0
IPC 477E 24" Win10 6AV7241-5SB07-0FA0
Box IPC
IPC 427E (Standard) Win7 6AG4141-1AA14-0FA0
IPC 427E (High) Win7 6AG4141-5AB14-0FA0
IPC 427E (Standard) Win10 6AG4141-1AA17-0FA0
IPC 427E (High) Win10 6AG4141-5AB17-0FA0
Basic functions
Index
$AN_AUXFU_LIST_ENDINDEX, 665
$AN_AXCTAS, 768
$ $AN_AXCTSWA, 768
$AN_LAI_AX_IS_AXCTAX, 768
$A_DP_IN_CONF, 718
$AN_LAI_AX_IS_LEADLINKAX, 768
$A_DP_IN_STATE, 718
$AN_LAI_AX_IS_LINKAX, 768
$A_DP_IN_VALID, 718
$AN_LAI_AX_TO_IPO_NC_CHANAX, 768
$A_DP_OUT_CONF, 718
$AN_LAI_AX_TO_MACHAX, 768
$A_DP_OUT_STATE, 718
$AN_POWERON_TIME, 245
$A_DP_OUT_VALID, 718
$AN_SETUP_TIME, 245
$A_IN, 692
$C_AUX_EXT, 226
$A_INA, 692, 698
$C_AUX_IS_QUICK, 226
$A_INCO, 705
$C_AUX_VALUE, 226
$A_OUT, 692, 694
$C_D, 227
$A_OUTA, 692, 700
$C_D_PROG, 227
$AA_ATOL, 510
$C_DL, 227
$AA_G0MODE, 519
$C_DL_PROG, 227
$AA_ISTEST, 544
$C_DUPLO, 227
$AC_ACT_PROG_NET_TIME, 246
$C_DUPLO_PROG, 227
$AC_ACTUAL_PARTS, 252, 257
$C_M, 226
$AC_ASUP, 182
$C_M_PROG, 226
$AC_AUXFU_EXT, 674
$C_ME, 226
$AC_AUXFU_M_EXT, 674
$C_MTL, 223, 227
$AC_AUXFU_M_STATE, 675
$C_MTL_PROG, 223, 227
$AC_AUXFU_M_TICK, 656
$C_T, 226
$AC_AUXFU_M_VALUE, 675
$C_T_PROG, 226
$AC_AUXFU_PREDEF_INDEX, 661, 674
$C_TCA, 227
$AC_AUXFU_SPEC, 672, 675
$C_TE, 227
$AC_AUXFU_STATE, 675
$C_THNO, 227
$AC_AUXFU_TYPE, 674
$C_THNO_PROG, 227
$AC_AUXFU_VALUE, 675
$C_TS, 227
$AC_AXCTSWA, 768
$C_TS_PROG, 227
$AC_AXCTSWE, 768
$NK_A_OFF, 425, 428, 431
$AC_CTOL, 510
$NK_AXIS, 424, 428
$AC_CTOL_G0_ABS, 523
$NK_NAME, 419
$AC_CUTTING_TIME, 248
$NK_NEXT, 420
$AC_CYCLE_TIME, 248
$NK_OFF_DIR, 423, 426, 429, 431
$AC_DELAYFST, 82
$NK_PARALLEL, 421
$AC_ISTEST, 544
$NK_SWITCH, 435
$AC_OLD_PROG_NET_TIME, 246
$NK_SWITCH_INDEX, 433
$AC_OLD_PROG_NET_TIME_COUNT, 247
$NK_SWITCH_POS, 434
$AC_OPERATING_TIME, 248
$NK_TYPE, 422
$AC_OTOL, 510
$P_CHANNO, 74
$AC_OTOL_ G0_ABS, 523
$P_CTOL, 510
$AC_PROG_NET_TIME_TRIGGER, 247
$P_CTOL_ G0_ABS, 523
$AC_PROGINF, 121
$P_DELAYFST, 82
$AC_REQUIRED_PARTS, 252, 257
$P_DRYRUN, 121
$AC_SPECIAL_PARTS, 252, 257
$P_GFRNUM, 336
$AC_STOLF, 523
$P_IFRAME, 332
$AC_TOTAL_PARTS, 252, 257
Basic functions
Index
$P_ISDRF, 121 adaptation factor

$P_ISPROGSTOP, 121 dynamic path response, 485
$P_ISRG0, 121 ADDFRAME, 376
$P_ISSKIP, 121 ALF, 178
$P_ISTEST, 95, 121, 544 ASUB
$P_OTOL, 510 Activation, 169
$P_OTOL_ G0_ABS, 523 For user alarms, 183
$P_PROG_EVENT, 74 Priority, 178
$P_REPINF, 177 ASUP
$P_SEARCH_S, 127, 658 Internal, 181
$P_SEARCH_SDIR, 127, 658 Reorganization, 170
$P_SEARCH_SGEAR, 127, 658 SERUPRO end, 665
$P_SEARCH_SMODE, 127 ATOL, 507
$P_SEARCH_SPOS, 127, 658 ATRANS, 266
$P_SEARCH_SPOSMODE, 128, 658 Automatic axis replacement, 553
$P_SIM, 256 Autonomous singleaxis operations, 164
$P_STOLF, 523 AUXFUDEL, 666
$P_SUB_AUTOGEAR, 235 AUXFUDELG, 667
$P_SUB_AXFCT, 235, 236 AUXFUMSEQ, 656
$P_SUB_CA, 236 AUXFUSYNC, 666
$P_SUB_GEAR, 235 Auxiliary function
$P_SUB_LA, 236 Address extension, 634
$P_SUB_M19, 236 Associated, 642
$P_SUB_SPOS, 236 -counter, 662
$P_SUB_SPOSA, 236 Definition, 612
$P_SUB_SPOSIT, 236 Output behavior, 635
$P_SUB_SPOSMODE, 236 Predefined, 611
$P_SUB_STAT, 225, 227 Type, 634
$P_UIFR, 332 User-defined, 611
$P_UIFRNUM, 332 Value, 634
$PA_ATOL, 510 Auxiliary function output, 46
auxiliary functions
User-specific, 639
_ Auxiliary functions
Pre-defined, 618
_N_STRTLK, 45
AXCTSWE, 766
_N_STRTUL, 45
AXCTSWEC, 766
AXCTSWED, 766
Axis configuration, 276
A Axis container
Access authorization, 595 -Identifier, 759
Access features, 596 Axis identifier, 580
Access rights, 576 Axis replacement
Access security, 595 Axis replacement via synchronized actions, 562
Action blocks, 124 Geometry axis in rotated frame, 561
Activating an axis replacement without a Release axis container rotation, 557
preprocessing stop, 558 without preprocessing stop, 557
Activation/Deactivation, 575 AXTOCHAN, 562
Active file system, 800
Actual-value system
workpiecerelated, 396
Basic functions
Index
states, 56
status display, 55
B Channel axes, 271
Channel state
Basic block display
Channel active, 37
Activating, 86
Channel interrupted, 37
Configuring, 85
Channel reset, 37
Basic coordinate system (BCS), 265, 295
CLEARM, 529
Basic display
CLRINT, 179
Size of the display buffer, 86
Coarse offset, 266
Block
Collision avoidance
Skip, 101
Fundamentals example, 440
Block search
Commissioning archive, 801
Cascaded, 122
Comparator inputs, 705
with calculation at block end point (type 4), 122
COMPCAD, 499, 502, 503
with calculation at the contour (type 2), 122
COMPCURV, 499, 502
with calculation in program test mode, SERUPRO
Compiling, 576
(type 5), 122
COMPOF, 502, 503
without calculation (type 1), 122
COMPON, 499, 502
Block search SERUPRO
COMPSURF, 499, 502, 503
Basic settings, 166
Continuous-path mode, 453
Conditions for axis functions, 163
Implicit, 457
Control REPOS with NC/PLC interface
Contour
signals, 143
sampling factor, 496
Gear stage change, 164
sampling time, 496
Overlaid movements, 165
tolerance, 506
Path axes, 142
Control system response
REPOS acknowledgments, 143
at the end of the part program, 212
REPOS offset after an axis interchange, 146
at the start of the part program, 212
REPOS offset in the range of validity, 145
during run-up, 212
REPOS offset with synchronous spindle
When resetting, 212
coupling, 146
Controller parameter set switchover, 605
Reposition positioning axes, 141
CORROF, 304
Set REPOS response, 139
Counter pulse, 254
Setpoint and actual value couplings, 160
CT, 766
Time sequence, 136
CTOL, 507
CTOLG0, 520
accumulated spindle functions, 127
CTRANS, 266
BLSYNC, 178
Curvature, 494
Boundary conditions, 579
D
C
D functions, 616
Call, 578
D/DL function replacement, 223
Call condition, 579
Data channel, faster, 592
Cascaded block search, 130
DB10
CFINE, 266
DBB4-7, 588
Channel
DBX106.1, 587, 589
Basic settings, 46
DBX56.1, 587, 588, 590
Configuration, 42
DBX56.2, 587, 588
Current, 74
DBX56.4, 599
Properties, 41
DBX56.5, 599
Basic functions
Index
DBX56.6, 599 DBX30.5, 643

DBX56.7, 599 DBX31.0 - 2, 142
DB11 DBX31.0 - DBX31.2, 143
DBX0.0, 36, 38 DBX31.0-31.2, 147
DBX0.1, 36 DBX31.4, 141, 142, 143
DBX0.2, 36 DBX31.6-7, 103
DBX0.4, 41 DBX317.1, 252, 257
DBX0.5, 34 DBX318.0, 171
DBX0.6, 34 DBX318.5, 643
DBX0.7, 34, 54, 588 DBX318.6, 97
DBX1.0 - DBX1.2, 37 DBX319.0, 143
DBX26.4, 39 DBX319.1- DBX319.3, 142, 143, 144, 145
DBX26.5, 39 DBX319.5, 143, 146
DBX4.0 - DBX4.2, 36 DBX32.3, 123
DBX46.4, 39 DBX32.4, 123, 125
DBX46.5, 39 DBX32.5, 99
DBX5.0 - DBX5.2, 37 DBX32.6, 123, 659
DBX6.0, 37, 39 DBX33.3, 100
DBX6.1, 37 DBX33.4, 123
DBX6.2, 37 DBX35.0, 51, 55
DBX6.3, 35, 587, 589 DBX35.0 - DBX35.4, 176
DBX6.4, 39 DBX35.1, 55
DBX6.5, 39 DBX35.2, 55, 99, 104, 114
DBX6.7, 35 DBX35.3, 55
DBX7.0, 39 DBX35.4, 55
DBX7.0 - DBX7.2, 37 DBX35.5, 51, 56
DB21 DBX35.5 - DBX35.7, 176
DBX24.4, 643 DBX35.6, 56
DBX378.1, 176 DBX35.7, 54, 56
DB21, ... DBX36.7, 127
D35.0, 52 DBX384.0, 59
D35.5, 52 DBX39.4, 104
DBB116 - DBB136, 650 DBX39.6, 114
DBB140 - DBB190, 650 DBX39.7, 114
DBB194 - DBB206, 650 DBX6.6, 98
DBB376, 70 DBX7.1, 53, 95
DBB58 - DBB67, 650 DBX7.2, 52, 78
DBB68 - DBB112, 650 DBX7.3, 52, 78
DBX0.3, 100 DBX7.4, 52, 78
DBX0.4, 104 DBX7.5, 44
DBX0.5, 99 DBX7.6, 114
DBX0.6, 97 DBX7.7, 54, 589
DBX1.6, 123, 127 DB21, ... DB32.6, 126
DBX2.0, 52, 78, 79 DB21, ... DBX0.4, 125, 176
DBX2.0-7, 103 DB21, ... DBX1.7, 94
DBX24.1, 114 DB21, ... DBX25.7, 94
DBX24.3, 100 DB21, ... DBX33.7, 94
DBX24.5, 99 DB21, ... DBX36.6, 127
DBX24.6, 96 DB21, ... DBX6.1, 175
DBX25.3, 98 DB21, …
DBX26.0-7, 102 DBX378.0, 169
DBX27.1-2, 102
Basic functions
Index
DB31, ... Emergency stop control elements, 586

DBX10.0, 139, 142, 143, 144, 147 ENABLE, 179
DBX2.2, 140 ENDLABEL, 61
DBX28.7, 44 Event-controlled program sequences, 66
DBX3.7, 163 Exact stop, 449
DBX60.5, 589 Implicit, 454
DBX64.6, 654 Exact stop conditions, 450, 451
DBX64.7, 654 Execute external subprogram, 191
DBX69.0, 607 EXTCLOSE, 208
DBX69.1, 607 External program memory, 191
DBX69.2, 607 External work offset, 301
DBX70.0, 143, 145 EXTOPEN, 208
DBX70.1, 143, 145
DBX70.2, 143, 144, 145
DBX72.0, 143 F
DBX76.4, 143, 146
F functions, 617
DBX9.0, 606
FA functions, 617
DBX9.1, 606
FGROUP, 272, 274
DBX9.2, 606
FIFO Buffer, 191
DB31, ... DBX128.0, 94
Fine offset, 266
DB31, ... DBX128.1, 94
FRAME, 271
DB31, ... DBX14.0, 94
Frame rotations, 268
DB31, ... DBX14.1, 94
in the direction of the tool, 385, 386
Debug mode for SB2, 105
with solid angles, 381
Default passwords, 598
Free-form surfaces, 495
DELAYFSTOF, 80
mode, 448, 495
DELAYFSTON, 80
Functionality, 574
DELOBJ, 436
Detailed description, 573
DISABLE, 179
Display block, structure (DIN), 88
G
DL functions, 616 G groups, 46
DRF, 100 G0 tolerance factor, 515
Dry run feedrate, 96 G0 tolerances, 514, 515, 520
Dynamic NC memory, 799 G58, 266
Dynamic response G59, 266
adaptation, 483 G60, 450
DYNFINISH, 492 G601, 451
DYNNORM, 492 G602, 451
DYNPOS, 492 G603, 451
DYNPREC, 492 G64, 457
DYNROUGH, 492 G642, 462
DYNSEMIFIN, 492 G643, 462
G644, 465
G645, 468
E G9, 450
General functionality, 573
EES, 195
General information, 573
Element, 412
Geometry axes, 271, 295
Emergency stop
Geometry axis grouping are either, 561
Acknowledgment, 588
GET, 551
Interface, 587
GETD, 552
Sequence, 587
Basic functions
Index
GFRAME0 ... GFRAME100, 336 Language scope, 579

Grouping together auxiliary functions, 634 LIFTFAST, 178
Loader axes, 272
Lockable data areas, 600
H LookAhead, 470
Selection and deselection, 471
H functions, 615
Handwheel offset, 100
Helical interpolation, 275
Helix interpolation, 275
M
High-speed data channel, 592 M function replacement, 221
Home NCU, 752 M01, 99
M1, 677
M17, 677
I M2, 677
M30, 677
I/O range, 715
Machine axes, 270
ID check, 254
Machine coordinate system (MCS), 265, 284
Implicit continuous-path mode, 457
Machine tool axes, 272
Implicit exact stop, 454
Machine zero M, 279
Implicit preprocessing stop, 158
Main axes, 273
INIT, 529
Main run, 42
Interpolation
MD10000, 264
Linear, 512
MD10010, 32, 529
Non-linear, 513
MD10050, 741
With G0, 512
MD10061, 741
Interpolator end, 451
MD10070, 741
Interrupt
MD10071:, 741
lock, 179
MD10125, 202
routine, 168
MD10131, 591
signal, 168
MD10185, 742
Interrupt routine
MD10260, 778
End, 170
MD10280, 529
MD10300, 689, 700
MD10310, 689, 703
J MD10320, 690, 699
Jerk limitation, 467 MD10330, 690, 702
Jogging MD10350, 689, 697
in the mode type AUTOMATIC, 38 MD10360, 689, 695, 697
Jump marker MD10361, 697
For program section repetitions, 61 MD10362, 690
MD10364, 690
MD10366, 690
K MD10368, 690
MD10398, 710
Keyswitch, 599
MD10399, 711
Kinematic chains, 412
MD10500, 716
Kinematic structure, 411
MD10501, 716
Kinematic transformation, 295
MD10502, 717
MD10510, 716
MD10511, 716
L MD10512, 717
Label, 61 MD10530, 705
Basic functions
Index
MD10531, 705 MD12712, 763, 789

MD10540, 706 MD12713, 763, 789
MD10541, 706 MD12714, 763, 789
MD10600, 311, 384 MD12715, 763, 789
MD10602, 345, 347, 355, 359 MD12716, 763, 789
MD10610, 268, 341 MD12717, 763
MD10612, 341 MD12750, 759
MD10615, 390 MD15700, 233
MD10680, 497 MD15702, 233
MD10682, 496 MD16800, 417
MD10700, 86, 573, 575, 577 MD17200, 86
MD10702, 105, 125, 176 MD17950, 802
MD10703, 115 MD18000, 742
MD10707, 136 MD18050, 807
MD10708, 136 MD18060, 804, 805
MD10712, 244, 493 MD18150, 592
MD10713, 651 MD18170, 575
MD10714, 222, 629 MD18180, 575
MD10715, 221 MD18210, 806
MD10716, 221 MD18230, 803, 805
MD10719, 224 MD18242, 576
MD10722, 557, 558 MD18351, 575
MD10735, 38 MD18352, 804, 805
MD10804, 222 MD18353, 804, 805
MD10806, 223 MD18360, 192
MD10814, 223 MD18362, 192
MD11100, 640 MD18600, 309
MD11110, 646 MD18602, 331, 334, 337, 338
MD11411, 44 MD18720, 734
MD11450, 127, 128, 130, 138, 162, 658 MD18880, 417
MD11470, 139, 140, 164 MD18882, 417
MD11550, 80 MD19250, 805
MD11600, 173 MD20000, 42
MD11602, 172, 174, 175 MD20050, 216, 264, 365
MD11604, 162, 172, 174 MD20060, 264, 580
MD11610, 182 MD20070, 264
MD11620, 71 MD20080, 264, 275, 580
MD11625, 202 MD20090, 676
MD11626, 203 MD20094, 223, 629
MD12030, 472, 474 MD20095, 223, 629
MD12100, 472, 474 MD20105, 162, 180
MD12701, 763, 789 MD20106, 71, 105, 129
MD12702, 763, 789 MD20107, 72, 129
MD12703, 763, 789 MD20108, 70
MD12704, 763, 789 MD20109, 71
MD12705, 763, 789 MD20110, 172, 390, 391, 393, 399, 778
MD12706, 763, 789 MD20112, 137, 172, 216, 395, 399
MD12707, 763, 789 MD20115, 162, 175, 180
MD12708, 763, 789 MD20116, 175
MD12709, 763, 789 MD20117, 105, 176
MD12710, 763, 789 MD20118, 216
MD12711, 763, 789 MD20120, 216
Basic functions
Index
MD20121, 216 MD22050, 634

MD20124, 676 MD22060, 634
MD20130, 216 MD22070, 635
MD20140, 216 MD22080, 234, 635
MD20144, 218 MD22100, 651
MD20150, 42, 46, 216, 323, 393, 394, 524 MD22110, 615, 617, 618
MD20152, 216, 393 MD22200, 644
MD20170, 500 MD22210, 614, 644
MD20171, 500 MD22220, 615, 644
MD20172, 500 MD22230, 615, 644
MD20173, 500 MD22240, 617, 644
MD20184, 386 MD22250, 616, 644
MD20191, 176 MD22252, 617, 644
MD20192, 73 MD22254, 223, 629, 642
MD20193, 73 MD22256, 223, 629, 642
MD20194, 172, 184 MD22510, 46
MD20270, 616 MD22530, 672
MD20272, 616 MD22532, 672
MD20310, 150 MD22534, 672
MD20400, 472 MD22550, 224
MD20430, 474 MD22560, 223, 629, 676
MD20440, 474 MD22600, 148
MD20443, 477 MD22620, 166
MD20450, 475 MD24004, 390
MD20460, 481, 482 MD24006, 303, 323, 392
MD20462, 482 MD24007, 394
MD20465, 485 MD24008, 303, 391
MD20480, 463, 465, 506 MD24010, 341
MD20482, 501, 506 MD24020, 329
MD20485, 501 MD24040, 365
MD20486, 501 MD24805, 354, 355
MD20487, 501 MD24855, 354, 355
MD20488, 505 MD24905, 348
MD20490, 457 MD24955, 348
MD20550, 452 MD26008, 223, 629
MD20552, 453 MD26012, 223
MD20560, 515 MD27100, 87
MD20561, 516 MD27800, 43
MD20562, 516 MD27850, 249
MD20606, 496 MD27860, 59, 249
MD20700, 175 MD27880, 59, 252
MD20730, 515 MD27882, 253
MD20750, 513 MD28010, 576
MD20800, 613, 677, 678 MD28020, 576
MD21220, 691, 707 MD28040, 576
MD21330, 216 MD28060, 83, 86
MD22000, 640 MD28070, 505
MD22010, 641 MD28071, 501
MD22020, 641 MD28072, 501
MD22030, 641 MD28082, 323, 342, 378, 386
MD22035, 642 MD28150, 594
MD22040, 633, 640 MD28400, 86
Basic functions
Index
MD28402, 86 of the mode group, 35

MD28530, 464 Priorities, 36
MD28533, 477 MTL, 223
MD28560, 395
MD28610, 495
MD30552, 553 N
MD31050, 606
NAMETOINT, 439
MD31060, 606
NC
MD32000, 515
language scope, 46
MD32060, 164
start, 50
MD32074, 391, 561
NC/PLC interface, 42
MD32200, 606
Negative address extension, 678
MD32310, 456
MD32420, 513
MD32430, 513
MD32440, 482, 485
O
MD32800, 606 Operating modes
MD32810, 606 Interlocks, 40
MD32910, 606 monitoring functions, 40
MD33100, 463, 496, 500, 506 Operating states, 37
MD33120, 468, 506 Orientation
MD35000, 264, 319 tolerance, 506
MD35130, 606 OTOL, 507
MD35240, 465 OTOLG0, 520
MD35590, 606 Output
MD36000, 450 Behavior of an auxiliary function, 635
MD36010, 450 -counter, 662
MD36012, 452 Sequence, 662
MD36610, 587 to external device/file, 208
MD36620, 587 Overload factor, 456
MD51029, 103
MD51074, 253
MD9004, 88 P
MD9010, 88
Package
MD9011, 88
-counter, 662
MD9424, 88, 299
Parallel subchains, 413
MD9440, 398
Part program
Memory expansion, 804
Selection, 50
Memory requirements, 576
Passive file system, 800
Mirroring
Password, 597
Frames, 318
Passwords, 598
Mode
Path axes, 272
AUTOMATIC, 35
Path criterion, 460
JOG, 36
PLC
JOG in AUTOMATIC, 35
- Read/write variable, 592
MDI, 36
-axes, 273
Mode change
POS, 272, 273
from/to the AUTOMATIC, JOG, MDI modes, 41
POSA, 272, 273
Mode group, 31
Position of the coordinate systems and reference
Modes
points, 281
change, 35, 40
Positioning axes, 272
cross-mode synchronized actions, 36
Preprocessing, 42
Basic functions
Index
PRESETON, 285
PRESETONS, 290
Process Datashare, 204 S
Process DataShare, 208
S functions, 614
Processing time, 248
SAVE, 179
Program
SBLOF, 106
action, 57
SBLON, 106
Runtimes, 245
SD41600, 706
states, 55
SD41601, 706
status display, 54
SD42100, 97
test, 91
SD42200, 106
Program handling, 575
SD42220, 115
Program operation, 45
SD42222, 115
Program section
SD42224, 116
repetition, 61
SD42440, 268
Programmed stop, 99
SD42444, 125
Protection level
SD42465, 463, 506
for user ASUP, 182
SD42466, 463, 506
Protection levels, 595
SD42470, 501
programmable, 600
SD42471, 501
SD42472, 501
SD42473, 501
R SD42475, 501
RangeOffset, 719 SD42476, 501
Rapid traverse SD42477, 501
Interpolation types, 512 SD42676, 506
Reduced, 98 SD42678, 507
Reaching simulated target point for LEAD with SD42700, 193
JOG, 161 SD42750, 85
Reduced rapid traverse, 98 SD42990, 83
Reference point R, 279 Secant error, 496
Reference points, 279 Self-acting SERUPRO, 152
RELEASE, 550 SERUPRO
Release guide axis, 551 Automatic interrupt pointer, 155
Relevant standards, 585 -end ASUP, 665
REPEAT, 61 Programmable interrupt pointer, 153
REPEATB, 61 SERUPRO approach
Replacement subprogram, 220 control from the PLC, 143
Reset SERUPRO ASUP
behavior, 212 Special features, 149
RESET seruproMasterChan, 152
Command, 54 SETINT, 168, 177
Residual time SETM, 529, 535
For a workpiece, 247 Simulation, 255
RG0, 98 Single block
Rotary axes, 272 Mode group-specific, 111
Rotation component, 379 SB1, 104
Rounding, 457 SB2, 104
Runtime optimization, 574 SB3, 104
Runtimes Single-block
Program, 245 suppression, 106
Skip blocks, 101
Basic functions
Index
Skip levels, 102 WAITMC, 529, 534

Smoothing Work offset
Path velocity, 480 External work offset, 301
Special axes, 271 Workpiece
Special points in the target block -counter, 251, 256
STOPRRE block, 157 -simulation, 255
Spindle functions using a PLC, 43 Workpiece coordinate system (WCS), 265, 300
Spline, 449 Workpiece zero W, 279
START, 529 World coordinate system, 414
Static NC memory, 799
STOLF, 520
Stop delay area, 77 X
Stop events, 77
XE \* MERGEFORMAT,
STRINGIS, 47
Synchronized axes, 274
Syntax check, 579
Z
Zero points, 279
T
T function, 615
T function replacement, 223
TCP Tool Center Position, 279
TEACH IN, 36
Tick, 662
Tolerance
With G0, 514
Tool
management, 31
-retraction, 217
Tool revolver axes, 272
Toolholder reference point T, 279
Torsion, 494
TRANS, 266
TRANSMIT, 295
U
User-defined ASUP
after SERUPRO operation, 137
V
V2 preprocessing
Brief description, 573
W
WAITE, 529
WAITENC, 218
WAITM, 529
Basic functions
Index
Basic functions

840Dsl Basic FCT Man 1219 en-US

Uploaded by

Copyright:

Available Formats

840Dsl Basic FCT Man 1219 en-US

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

840Dsl Basic FCT Man 1219 en-US

Uploaded by

Copyright:

Available Formats

Preface

Axes, coordinate systems,

Digital and analog NC I/O 12

Siemens AG Document order number: 6FC5397-2GP40-0BA0 Copyright © Siemens AG 2019.

Note regarding the General Data Protection Regulation

Information on the structure and contents

Notation of system data

Signal/Data Notation Example

Type Meaning Range of values

Querying REAL variables

Program code Comment

Program code Comment

2.8.8.1 STOPRE in the target block .................................................................................................157

2.14.1 Function ...............................................................................................................................195

2.21.2.1 General machine data..........................................................................................................257

3.5.2.5 Rotation with a Euler angles: ZX'Z" convention ...................................................................316

4.5 Data lists ..............................................................................................................................445

7.12 Axis replacement from synchronized actions.......................................................................562

10.2.4 Access protection via password and keyswitch ...................................................................595

11.11 M function with an implicit preprocessing stop.....................................................................651

12.3.4.2 Reading from PLC-I/Os........................................................................................................713

13.2.3.1 General information..............................................................................................................751

14 Memory configuration ...............................................................................................................................799

1.2 Warranty and liability for application examples

1.3 Industrial security

Further information is provided on the Internet:

● Type 4 with calculation at block end point

Asynchronous subprograms (ASUPs), interrupt routines

Basic block display

Program execution from external source

Behavior after POWER ON, Reset, ...

Subprogram call with M, T and D functions

Program runtime/part counter

2.2 Mode group

Further information can be found under Parameterization

Mode-group-specific NC/PLC interface signals

The mode-group-specific NC/PLC interface essentially comprises the following interface

Activated and non-activated channels, channel gaps

Table 2-1 Example

Machine data Meaning

2.2.1 Mode group stop

2.2.2 Mode group reset

2.3 Mode types and mode type change

Applies to all modes

Cross-mode synchronized actions

Activation and priorities

Priority Mode Mode group signal (NC → PLC)

Mode group signal (NC → PLC) Active operating mode

NC/PLC interface signals

Functions within modes

Boundary condition for the TEACH IN machine function

2.3.1 Monitoring functions and interlocks of the individual modes

Channel status determines monitoring functions

Monitoring functions in operating modes

Interlocking functions in operating modes

2.3.2 Mode change

Possible mode changes

AUTOMATIC JOG MDI

Possible mode changes are indicated by an "X".