Error Code List (6000 To 6999) - Mitsubishi MELSEC Q Series Programming Manual

12.1.8

Error code list (6000 to 6999)

The following shows the error messages from the error code 6000 to 6999, the contents and
causes of the errors, and the corrective actions for the errors.
Error
Error Contents and Cause
Code
[FILE DIFF.]
In a redundant system, the control system and
standby system do not have the same programs
and parameters.
The file type detected as different between the two
systems can be checked by the file name of the
error common information.
• The program is different.
(File name = ********.QPG)
• The PLC parameters/network parameters/
redundant parameters are different.
(File name = PARAM.QPA)
• The remote password is different.
(File name = PARAM.QPA)
• The intelligent function module parameters are
different.
6000
(File name = IPARAM.QPA)
• The device initial values are different.
(File name = ********.QDI)
• The size of the area, which is used for enabling
writing multiple program blocks to the CPU
module during running, do not match.
(File name = MBOC.QMB)
(This can be detected from the standby system of
the redundant system.)
■Collateral information
• Common information: File name
• Individual information:-
■Diagnostic Timing
• At power-on/At reset/At tracking cable
connection/At changing to backup mode/At
completion of write during RUN/At system
switching/At switching both systems into RUN
[FILE DIFF.]
In the redundant system, the valid-parameter drive
setting (SW2, SW3) set by the DIP switches differs
between the control system and standby system.
■Collateral information
6001
• Common information:-
• Individual information:-
■Diagnostic Timing
• At power-on/At reset/At tracking cable
connection/At operation mode change
[OPE. MODE DIFF.]
The operational status of the control system and
standby system in the redundant system is not the
same.
(This can be detected from the standby system of
6010
the redundant system.)
■Collateral information
• Common information:-
• Individual information:-
■Diagnostic Timing
• Always
12-74
Corrective Action
• Match the programs and parameters of the
control system and standby system.
• Verify the CPU module by either of the following
procedures 1) or 2) to clarify the differences
between the files of both systems. Correct
wrong files and write them to the CPU module
again.
1) After reading the programs and parameters of
System A using GX Developer or PX
Developer, verify them with those of System
B.
2) Verify the programs and parameters of GX
Developer or PX Developer saved in the
offline environment with those written to the
CPU modules of both systems.
• When the size of the area, which is used for
enabling writing multiple program blocks to the
CPU module during running, do not match,
perform either of corrective actions 1) or 2).
1) Using the memory copy function, copy the
program memory from the control system to
the standby system.
2) Format the CPU module program memories of
both systems. (For both systems, specify the
same values for the size of the area, which is
used for enabling writing multiple program
blocks to the CPU module during running.)
Match the valid-parameter drive settings (SW2,
SW3) for both the control and standby systems
using the DIP switches.
Synchronise the operation statuses of the control
system and standby system.
LED Status Corresponding
CPU Status CPU
RUN:
Off
ERR.:
Flicker
CPU Status:
Stop
QnPRH
RUN:
On
ERR.:
On
CPU Status:
Continue