Mitsubishi Electric Q26UD(E)HCPU User Manual page 401

Melsecq series
Hide thumbs Also See for Q26UD(E)HCPU:
Table of Contents

Advertisement

Error
Error and cause
code
[CONTROL EXE.]
The standby system has been switched to the
control system in a redundant system. (Detected
by the CPU that was switched from the standby
system to the control 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
6200
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
[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
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.
APPENDICES
LED status,
Corresponding
CPU status
CPU
RUN: On
ERR.:Off
QnPRH
CPU Status:No error
RUN: On
ERR.:Off
QnPRH
CPU Status:No error
RUN: On
ERR.:On
QnPRH
CPU Status:Continue
RUN: On
ERR.:On
QnPRH
CPU Status:Continue
A
399

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents