Mitsubishi MELSEC Q4ARCPU User Manual page 255

Error
Code Error Contents and Cause
(SD0)
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 redundant system.
• The CPU module in the debug mode
6310
was connected to the operating
standby system.
• The error occurred at a startup since
the redundant system startup
procedure was not followed.
(This can be detected from the standby
system of the redundant system.)
• As consistency check data has not
6311
transmitted from the control system in
a redundant system, the other system
cannot start as a standby system.
• The error occurred at a startup since
the redundant system startup
6312
procedure was not followed.
(This can be detected from the standby
system of the redundant system.)
The control system detected the error of
the system configuration and informed it
6313
to the standby system (host system) in
the redundant system.
*1 The module whose first 5 digits of serial No. is 09012 or later.
Corrective Action
• 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.
Restart the system after checking that
the connection between base unit and
the system configuration (type/number/
parameter of module) are correct.
242
Corresponding
CPU
QnPRH
QnPRH
*1
QnPRH