Mitsubishi Melsec-Q Series User Manual page 432

Hide thumbs Also See for Melsec-Q Series:
Table of Contents

Advertisement

Error
Code
Error Contents and Cause
(SD0)
[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 con-
nected to the operating standby system.
6310
• The error occurred at a startup since the redun-
dant 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
6311
[CONTROL SYS. DOWN]
• As consistency check data has not transmitted
from the control system in a redundant system,
the other system cannot start as a standby sys-
tem.
• The error occurred at a startup since the redun-
dant system startup procedure was not followed.
(This can be detected from the standby system of
6312
the redundant system.)
■Collateral information
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[CONTROL SYS. DOWN]
The control system detected the error of the system
configuration and informed it to the standby system
(host system) in the redundant system.
6313
■Collateral information
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[PRG. MEM. CLEAR]
The memory copy from control system to standby
system was executed, and the program memory
was cleared.
■Collateral information
6400
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• At execution of the memory copy from control
system to standby system
12 - 137
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 con-
trol system and control system are combined cor-
rectly.
• 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 connec-
tion between base unit and the system configura-
tion (type/number/parameter of module) are
correct.
After the memory copy from control system to
standby system is completed, switch power OFF
and then ON, or make a reset.
LED Status
Corresponding
CPU Status
CPU
RUN:
Off
ERR.:
Flicker
CPU Status:
Stop
QnPRH
RUN:
Off
ERR.:
Flicker
CPU Status:
Stop
RUN:
Off
ERR.:
Flicker
QnPRH
CPU Status:
Stop
RUN:
Off
ERR.:
Flicker
QnPRH
CPU Status:
Stop
*1

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents