Flexible NC programming
1.15 Axis replacement, spindle replacement (RELEASE, GET, GETD)
Job planning
Programming Manual, 07/2010, 6FC5398-2BP40-0BA0
129
Varying the axis replacement behavior
The transfer point of axes can be set as follows using machine data:
● Automatic axis replacement between two channels then also takes place when the axis
has been brought to a neutral state by WAITP (response as before)
● When requesting an axis container rotation, all axes of the axis container which can be
assigned to the executing channel are brought into the channel using implicit GET or
GETD. A subsequent axle replacement is only permitted again once the axis container
rotation has been completed.
● When an intermediate block is inserted in the main run, a check will be made to
determine whether or not reorganization is required. Reorganization is only necessary if
the axis states of this block do not match the current axis states.
● Instead of a GET block with preprocessing stop and synchronization between
preprocessing and main run, axes can be replaced without a preprocessing stop. In this
case, an intermediate block is simply generated with the GET request. 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.
For more information about how axis or spindle replacement works, see
/FB2/ Function Manual, Extended Functions, Mode Groups, Channels, Axis Replacement
(K5).
To Next Page
Loading...
Need help?
General
