Siemens SINUMERIK 840Di sl Function Manual page 80

Detailed description
2.4 Actions in synchronized actions
Example
GET, RELEASE in the technology cycle
It has been declared in first and second channel: The axis U, machine data:
MD30552 $MA_AUTO_GET_TYPE = 2 (get automatic GET for axis)
Currently, channel 1 has the interpolation right and the following technology cycle is started
in channel 2:
GET(U)
POS[U]=100
The command-axis-movement line (POS ...) is not executed until the U axis has been
fetched to channel 2.
AXTOCHAN Move axis to another channel
From a synchronous action, an axis for a specific channel can be requested with the NC-
language command AXTOCHAN (Axis, channel number)[axis, channel
number[, ...]])
This does not have to be its own channel, that currently has the interpolation authorization
for the axis. This means that it is possible to shift and axis into another channel.
If the axis is already assigned to the NC program of the requested channel
$AA_AXCHANGE_TYP[axis] == 0, then there is nostate change.
In the event of an axis being requested for the same channel, AXTOCHAN from the
synchronized action is mapped to a GET from a synchronized action. For the
1. first request for the own channel, the axis is assigned to the neutral axis.
2. second request assigned to the NC program, which is the case for an GET in the NC
Constraints AXTOCHAN
A PLC controlled corresponds to a "competing positioning axis" where special constraints
must be carefully observed.
Traversing using static synchronized actions: Stage 2 is necessary.
References:
/FB2/ Function Manual, Extended Functions; Positioning Axes (P2)
Note
A PLC axis cannot replace the channel. This is also not possible using an entry from the VDI
interface.
An axis controlled exclusively by the PLC cannot be assigned to the NC program.
80
program.
; Move U axis to channel
; U axis is to be moved to position 100
Function Manual, 11/2006, 6FC5397-5BP10-2BA0
Synchronized actions