Mitsubishi Electric QJ71LP21 Reference Manual page 297

8 TROUBLESHOOTING
Error Code
Error Contents and Cause
*1
(SD0)
Any of the following errors was detected in the backup
mode.
• The standby system has not started up in the redundant
system.
6300
• The standby system has developed a stop error in the
redundant system.
• The CPU module in the debug mode was connected to
the operating control system.
Any of the following errors was detected in the backup
mode.
• The control system has not started up in the redundant
system.
• The control system has developed a stop error in the
6310
redundant system.
• The CPU module in the debug mode was connected to
the operating standby system.
• The error occurred at a startup since the redundant
system startup procedure was not followed.
• As consistency check data has not transmitted from the
6311
control system in a redundant system, the other system
cannot start as a standby system.
• The error occurred at a startup since the redundant
6312
system startup procedure was not followed.
The memory copy from control system to standby system
6400
was executed, and the program memory was cleared.
The memory copy from control system to standby system
6410
was executed.
The file register file specified in the tracking setting of the
6500
PLC parameter dialog box does not exist.
The file register range specified in the device detail setting
6501 of the tracking setting of the PLC parameter dialog box
exceeded the specified file register file capacity.
• In a multiple CPU system, at CPU module fault
occurred at a station where "All station stop by stop
error of PLC " was selected in the operating mode.
• In a multiple CPU system, a CPU module incompatible
7000
with the multiple CPU system was mounted.
In a multiple CPU system, station 1 resulted in stop error
at power-on and the other stations cannot start. (This
error occurred at stations 2 to 4)
*1 : Characters in parentheses ( ) indicate the special register numbers where individual information is being stored.
*12 : This applies to the CPU of function version B or later.
8 - 90
Corrective Action
• Check whether the standby system is on or not, and if it
is not on, power it on.
• Check whether the standby system has been reset or
not, and if it has been reset, unreset it.
• Check whether the standby system has developed a
stop error or not, and if it has developed the error,
remove the error factor and restart it.
• When the CPU module in the debug mode was
connected to the control system operating in the
backup mode, make connection so that the control
system and standby system are combined correctly.
• The standby system exists but the control system does
not exist.
• Check whether the system other than the standby
system is on or not, and if it is not on, power it on.
• Check whether the system other than the standby
system has been reset or not, and if it is has been
reset, unreset it.
• Check whether the system other than the standby
system has developed a stop error or not, and if has
developed the error, remove the error factor, set the
control system and standby system to the same
operating status, and restart.
• When the CPU module in the debug mode was
connected to the control system operating in the
backup mode, make connection so that the control
system and control system are combined correctly.
• Confirm the redundant system startup procedure, and
execute a startup again.
• Replace the tracking cable. If the same error still
occurs, this indicates the CPU module is faulty.
(Contact your local Mitsubishi representative,
explaining a detailed description of the problem.)
• Confirm the redundant system startup procedure, and
execute a startup again.
After the memory copy from control system to standby
system is completed, switch power OFF and then ON, or
make a reset.
----
Read the individual information of the error using GX
Developer, and check and correct the drive name and file
name. Create the specified file.
Read the individual information of the error using GX
Developer, and increase the file register capacity.
• Read the individual information of the error using the
GX Developer, check the error of the PLC resulting in
CPU module fault, and remove the error.
• Remove the CPU module incompatible with the multiple
CPU system from the main base unit.
Read the individual information of the error using the GX
Developer, check the error of the CPU module resulting in
CPU module fault, and remove the error.
MELSEC-Q
Corresponding CPU
QnPRH
QnPRH
QnPRH
QnPRH
*12
Q00/Q01
*12
Qn(H)
QnPH
8 - 90