Mitsubishi Electric Q26UD(E)HCPU - Appendix 1.8 List of Error Codes (6000 to 6999)

393
APPENDICES
A
Appendix 1 Error Codes Appendix 1.8 List of error codes (6000 to 6999)
Appendix 1.8 List of error codes (6000 to 6999)
The following table shows the error messages, the error contents and causes, and the corrective actions for the error
codes (6000 to 6999).
Error
code
Error and cause Corrective action
LED status,
CPU status
Corresponding
CPU
6000
[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. (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
• 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) Read the programs and parameters of
System A using GX Works2, GX
Developer, or PX Developer, and verify
them with those of System B.
2) Verify the programs and parameters
saved in GX Works2, GX Developer, or
PX Developer (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.)
RUN: Off
ERR.:Flashing
CPU Status:Stop
QnPRH
6001
[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
• Common information: -
• Individual information: -
■Diagnostic timing
• At power-on/At reset/At tracking cable
connection/At operation mode change
Match the valid-parameter drive settings
(SW2, SW3) for both the control and standby
systems using the DIP switches.
RUN: Off
ERR.:Flashing
CPU Status:Stop
QnPRH
6010
[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 the redundant system.)
■Collateral information
• Common information: -
• Individual information: -
■Diagnostic timing
• Always
Synchronize the operation statuses of the
control system and standby system.
RUN: On
ERR.:On
CPU Status:Continue
QnPRH