Mitsubishi MELSEC Q Series Programming Manual page 996

Error
Error Contents and Cause
Code
[CAN'T EXE. MODE]
The function inexecutable in the debug mode or
operation mode (backup/separate mode) was
executed.
(This can be detected from the control system or
6050
standby system of the redundant system.)
■Collateral information
• Common information:-
• Individual information:-
■Diagnostic Timing
• Always
[CPU MODE DIFF.]
In a redundant system, the operation mode
(backup/separate) differs between the control
system and standby system.
(This can be detected from the standby system of
the redundant system.)
6060
■Collateral information
• Common information:-
• Individual information:-
■Diagnostic Timing
• At power-on/At reset/At tracking cable
connection
[CPU MODE DIFF.]
In a redundant system, the operation mode
(backup/separate) differs between the control
system and standby system.
(This can be detected from the standby system of
6061
the redundant system.)
■Collateral information
• Common information:-
• Individual information:-
■Diagnostic Timing
• When an END instruction executed
[CPU MODE DIFF.]
Both System A and B are in the same system
status (control system).
(This can be detected from the system B of the
redundant system.)
6062
■Collateral information
• Common information:-
• Individual information:-
■Diagnostic Timing
• At power-on/At reset/At tracking cable
connection
[TRK. TRANS. ERR.]
• An error (e.g. retry limit exceeded) occurred in
tracking data transmission.
(This error may be caused by tracking cable
removal or other system power-off (including
reset).)
• The error occurred at a startup since the
6100
redundant system startup procedure was not
followed.
■Collateral information
• Common information: Tracking transmission
data classification
• Individual information:-
■Diagnostic Timing
• Always
12-76
Corrective Action
Execute the function executable in the debug
mode or operation mode (backup/separate mode).
Match the operation modes of the control system
and standby system.
Power the CPU module (System B) which resulted
in a stop error, OFF and then ON.
• Check the CPU module or tracking cable. If the
error still occurs, this indicates the CPU module
or tracking cable is faulty. (Please consult your
local Mitsubishi representative, explaining a
detailed description of the problem.)
• Confirm the redundant system startup
procedure, and execute a startup again.
LED Status Corresponding
CPU Status CPU
RUN:
On
ERR.:
On
CPU Status:
Continue
RUN:
Off
ERR.:
Flicker
CPU Status: QnPRH
Stop
RUN:
On
ERR.:
On
CPU Status:
Continue