Jog Mode - Siemens SINUMERIK 840D sl Function Manual

2.10.1

JOG mode

It is not possible to traverse orientation axes in JOG mode until the following conditions are
fulfilled:
● The orientation axis must be defined as such, that is, a value must be set in the following
machine data:
MD24585 $MC_TRAFO5_ORIAX_ASSIGN_TAB (ORI/channel axis assignment
Transformation 1)
● A transformation must be active (TRAORIcommand)
Axis traversal using traverse keys
When using the traverse keys to move an axis continuously (momentary-trigger mode) or
incrementally, it must be noted that only one orientation axis can be moved at a time.
If more than one orientation axis is moved, alarm 20062 "Channel 1 axis 2 already active" is
generated.
Traversal using handwheels
More than one orientation axis can be moved simultaneously via the handwheels.
Feedrate in JOG
When orientation axes are traversed manually, the channel-specific feedrate override switch
or the rapid traverse override switch in rapid traverse override is applied.
Until now, velocities for traversal in JOG mode have always been derived from the machine
axis velocities. However, geometry and orientation axes are not always assigned directly to a
machine axis.
For this reason, new machine data have been introduced for geometry and orientation axes,
allowing separate velocities to be programmed for these axis types:
● MD21150 $MC_JOG_VELO_RAPID_ORI[n]
(conventional fast traverse for ORI axes)
● MD21155 $MC_JOG_VELO_ORI[n]
(conventional ORI axis speed)
● MD21160 $MC_JOG_VELO_RAPID_GEO[n]
(conventional fast traverse for GEO axes)
● MD21165 $MC_JOG_VELO_GEO[n]
(conventional GEO axis speed)
Appropriate speed values for the axes must be programmed in these data.
Acceleration
Acceleration for the orientation axes can be set by means of the following machine data:
MD21170 $MC_ACCEL_ORI[n] (ascceleration for orientation axes)
Special functions
Function Manual, 01/2015, 6FC5397-2BP40-5BA2
F2: Multi-axis transformations
2.10 Orientation axes
105