H1: Manual and handwheel travel
3.4 Handwheel travel in JOG
Extended Functions
Function Manual, 03/2013, 6FC5397-1BP40-3BA1
167
0RWLRQFRPPDQGVLJQDO
7UDYHOUHTXHVWVLJQDO
$[LVUHDFKHV
HQGSRLQW
2YHUULGHVWRS
FRQGLWLRQ
$[LVVKRXOG
WUDYHUVHZLWK
SHQGLQJVWRS
FRQGLWLRQ
Figure 3-2 Signal-time diagram:
Handwheel travel with distance specification, stop condition is not an abort criterion
MD17900 $MN_VDI_FUNCTION_MASK bit 0 = 1
Example 2: Handwheel travel, stop condition is an abort criterion
If a stop condition is selected as an abort criterion via machine data
MD32084 $MA_HANDWH_STOP_COND or
MD20624 $MC_HANDWH_CHAN_STOP_COND during handwheel travel, no travel
command is output, but the corresponding travel request is output.
When the stop condition is removed, the corresponding "Travel request" NC/PLC interface
signal is reset, as an abort is present. The stop condition is no longer active, but the axis
cannot be traversed as the stop condition has caused an abort.
In addition, either the distance specification (MD11346 $MN_HANDWH_TRUE_DISTANCE
== 1 or == 3) is active or the handwheel is moved continuously, i.e. it provides pulses.
To Next Page
Loading...
Need help?
General
