Mitsubishi MELSEC Q Series Programming Manual page 1000

Error
Error Contents and Cause
Code
[STANDBY]
The control system has been switched to the
standby system in a redundant system. (Detected
by the CPU that was switched from the control
system to the standby system.)
Since this error code does not indicate the error
information of the CPU module but indicates its
status, the error code and error information are not
stored into SD0 to 26, but are stored into the error
6210
log every system switching.
(To check the error information, obtain the error log
using the programming tool.)
■Collateral information
• Common information: Reason(s) for system
switching
• Individual information:-
■Diagnostic Timing
• Always
[CAN'T SWITCH]
The system cannot be switched due to a standby
system error, tracking cable failure, or online
module change being executed in the separate
mode. Causes for switching system at control
system are as follows:
• System switching by SP.CONTSW instruction
6220 • System switching request from network module
■Collateral information
• Common information: Reason(s) for system
switching
• Individual information: Reason(s) for system
switching failure
■Diagnostic Timing
• At switching execution
[STANDBY SYS. DOWN]
Any of the following errors was detected in the
backup mode.
• The standby system has not started up in the
redundant system.
• The standby system has developed a stop error
in the redundant system.
• The CPU module in the debug mode was
6300
connected to the operating control system.
(This can be detected from the control system of
the redundant system.)
■Collateral information
• Common information:-
• Individual information:-
■Diagnostic Timing
• Always
[CONTROL SYS. DOWN]
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 was
connected to the operating standby system.
6310
• 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.)
■Collateral information
• Common information:-
• Individual information:-
■Diagnostic Timing
• Always
12-80
Corrective Action
-
• Check the status of the standby system and
resolve the error.
• Complete the online module change.
• 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.
LED Status Corresponding
CPU Status CPU
RUN:
On
ERR.:
Off
CPU Status:
No error
RUN:
On
ERR.:
On
QnPRH
CPU Status:
Continue
RUN:
Off
ERR.:
Flicker
CPU Status:
Stop