Mitsubishi GX Configurator-PT, User Manual

Page: 23 / 224

1 - 10 1 - 10
MELSEC-Q
1 PRODUCT OUTLINE
1.2.2 Outline of stopping
The possible causes of a control stop are as follows.
(1) Control ended normally
(2) An error occurred in the PLC CPU
(3) An error occurred in the QD70
(4) The axis stop signal from the PLC CPU turned ON
Stop processings performed in the above cases are outlined in the following table.
(Except the case (1) where control stopped normally)
Stop processing
Stop factor
Stopped
axis
Axis operation
status (Md. 4 )
after stop
OPR control
Positioning
control
JOG operation
PLC CPU error All axes Error Deceleration stop
Software stroke limit
upper/lower limit error
1
Axis by axis Error Deceleration stop
QD70 error
Other error Axis by axis Error
Deceleration stop
2
"Axis stop signal" from PLC CPU turned
ON
Axis by axis Stopped
Deceleration stop
3
1: By making parameter setting, you can set the software stroke limit valid/invalid. When the stroke limit is set invalid, a
deceleration stop is not made. (Refer to Section 4.2.)
2: If an illegal positioning data setting value caused an error during position control (operation pattern: continuous path
control), an immediate stop is made at the positioning data preceding that illegal setting value. (Refer to Section 9.1.2.)
3: For position control (operation pattern: continuous path control), you can make parameter setting to select the
stopping method (position match stop or deceleration stop). (Refer to Section 4.2.)
Stop after multiple axes simultaneous start under positioning control
The axes started will not stop simultaneously. The stop command (axis stop signal
ON) must be given to each axis.