B3: Distributed systems - 840D sl only
2.2 NCU link
Extended Functions
Function Manual, 03/2013, 6FC5397-1BP40-3BA1
113
2.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:
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.
2.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.
To Next Page
Loading...
Need help?
General
