Troubleshooting; Safety Observation Error List - Mitsubishi Electric MELSEC Q Series Programming Manual

6 TROUBLESHOOTING

6. TROUBLESHOOTING

6.1 Safety Observation Error List

When errors which turn off the shut-off signal occur in the safety observation function,
the safety observation error flag (SM57) turns ON and the error code (SD32) and detail
code (SD33) are stored. Release the alarm depending on contents of error codes.
The errors other than with (Note-2, Note-6) cannot be reset. Restart the system (power
supply ON or reset of PLC CPU) after release of errors.
In addition, when the safety observation errors occurred, a self-diagnostic error flag
(SM1) and diagnostic error flag (SM0) turn ON, and a self-diagnostic errors (error code
10050) is stored in diagnostic errors (SD0).
Error Detail
code code Error contents
(SD32) (SD33)
0021H Unsupported CPU
9 type for safety
(Note-1)
observation
function
0022H
0400H
0401H
1000H
Sequence program
10
error
2700H
2701H
2702H
2800H
Error
Safety signal
20 device No.
compare error
(HEX)
Table 6.1 Safety observation error list
Error cause
The safety observation function parameters
are set to Q17 DCPU that does not
support the safety observation function.
The safety observation function parameter
is set to other than CPU No.2.
• An attempt was made to execute the
unsupported instruction code.
• The specified target does not exist in the
CALL or CJ instruction.
An attempt was made to execute the CALL
instruction at the jump destination of the
CALL instruction.
An attempt was made to execute the
unsupported instruction code.
• An unsupported instruction or device
description exists.
• Outside the device range description
exists.
• The file (File name: ERRLAD- ) that has
a sequence program error remains in the
program memory.
One or more program is registered, but the
P252 label does not exist.
The internal memory for executing the
sequence program is insufficient.
The PLC parameters of GX Works2 project
on Motion CPU side are changed from the
default settings.
A mismatch between safety signals that
were input to the PLC CPU and those that
were input to the Motion CPU was
detected.
The following causes are assumed:
• Cable disconnection
• Faulty door switch
• The control status of the output signal by
the user safety sequence program differs
between the Motion CPU and the PLC
CPU
6 - 1
Corrective action
Change the CPU to
Q17 DCPU-S1/Q17 DSCPU.
To a Motion CPU other than CPU No.2, write
parameters for which the safety observation
function parameter is not set.
Correct the user safety sequence program of
the Motion CPU.
Delete the file of the faulty sequence program.
Set the P252 label to the user safety
sequence program of the Motion CPU.
Decrease the number of steps of the user
safety sequence program of the Motion CPU.
Write the user safety sequence program to
the Motion CPU in the status that the PLC
parameters are set to the default settings.
Check the wiring.
Correct the sequence program so that the
Motion CPU and the PLC CPU have the
same control logic.
Relevant CPU
PLC Motion Reset
CPU CPU

6

(Note-2)