Siemens SINUMERIK 840D sl Programming Manual page 506

Motion synchronous actions
10.7 Restrictions
• End of program
Synchronized action/
technology cycle
Axis/
positioning spindle
Speed-controlled
spindle
Master value coupling $MC_RESET_MODE_MASK, bit13 == 1:
Measuring operations
• Block search
• Program interruption by the asynchronous subroutine ASUB
10-80
End of program and synchronized action do not influence one another. Current
synchronized actions are completed even after end of program. Synchronized actions
active in the M30 block remain active. If you do not want them to remain active, cancel
the synchronized action before end of program by pressing CANCEL (see preceding
section).
Modal and non-modal actions
are aborted
M30 is delayed until the axis / spindle is
stationary.
End of program:
$MA_SPIND_ACTIVE_AFTER_RESET==1
:
Spindle remains active
$MA_SPIND_ACTIVE_AFTER_RESET==0
:
Spindle stops
The spindle remains active if the operating
mode changes
Master value coupling remains active
$MC_RESET_MODE_MASK, Bit13 == 0:
Master value coupling is separated
Measuring operations started from
synchronized actions are aborted
Synchronized actions are collected during a block search and evaluated on NC Start; the
associated actions are then started if necessary. Static synchronized actions are active
during block search. If polynomial coefficients programmed with FCTDEF are found during
a block search, they are written directly to the setting data.
ASUB start:
Modal and static motion-synchronous actions remain active and are also operative in the
asynchronous subprogram (ASUB).
ASUB end:
If the asynchronized subroutine is not resumed with REPOS modal and static motion-
synchronized actions that were modified in the asynchronized subroutine remain active in
the main program.
Response following end of program
Programming Manual, 03/2006 Edition, 6FC5398-2BP10-1BA0
Static actions (IDS)
remain active
Motion continues
Spindle remains active
A coupling started from a static
synchronized action remains
active
Measuring operations started
from static synchronized
actions remain active
Job planning