Appendix 1.7
The following table shows the error messages, the error contents and causes, and the corrective actions for the error
codes (5000 to 5999).
Error
Error and cause
code
[WDT ERROR]
The scan time of the initial execution type program
exceeded the initial execution monitoring time
specified in the PLC RAS tab of "PLC Parameter".
■Collateral information
• Common information: Time (value set)
• Individual information: Time (value actually
measured)
■Diagnostic timing
• Always
5000
[WDT ERROR]
• The power supply of the standby system is
turned OFF.
• The tracking cable is disconnected or connected
without turning off or resetting the standby
system.
• The tracking cable is not secured by the
connector fixing screws.
■Collateral information
• Common information: Time (value set)
• Individual information: Time (value actually
measured)
■Diagnostic timing
• Always
[WDT ERROR]
The scan time of the program exceeded the WDT
value specified in the PLC RAS tab of "PLC
Parameter".
■Collateral information
• Common information: Time (value set)
• Individual information: Time (value actually
measured)
■Diagnostic timing
• Always
5001
[WDT ERROR]
• The power supply of the standby system is
turned OFF.
• The tracking cable is disconnected or connected
without turning off or resetting the standby
system.
• The tracking cable is not secured by the
connector fixing screws.
■Collateral information
• Common information: Time (value set)
• Individual information: Time (value actually
measured)
■Diagnostic timing
• Always
List of error codes (5000 to 5999)
Corrective action
• Read the individual information of the error
using the programming tool to identify the
numeric value (time). Check the value and
shorten the scan time.
• Change the initial execution monitoring
time or the WDT value in the PLC RAS tab
of "PLC Parameter".
• Resolve the endless loop caused by jump
transition.
• If the error persists even after the actions
mentioned above are taken, the possible
cause is a hardware failure of the system.
Please consult your local Mitsubishi
representative.
• Since power-off of the standby system
increases the control system scan time,
reset the WDT value, taking the increase of
the control system scan time into
consideration.
• If the tracking cable was disconnected
during operation, securely connect it and
restart the CPU module. If the same error
code is displayed again, the cause is a
hardware failure of the tracking cable or
CPU module. Please consult your local
Mitsubishi representative.
• Read the individual information of the error
using the programming tool to identify the
numeric value (time). Check the value and
shorten the scan time.
• Change the initial execution monitoring
time or the WDT value in the PLC RAS tab
of "PLC Parameter".
• Resolve the infinite loop caused by jump
sequence.
• Check the execution number of the
interrupt program, and reduce the
occurrence number of interruption.
• If the error persists even after the actions
mentioned above are taken, the possible
cause is a hardware failure of the system.
Please consult your local Mitsubishi
representative.
• Since power-off of the standby system
increases the control system scan time,
reset the WDT value, taking the increase of
the control system scan time into
consideration.
• If the tracking cable was disconnected
during operation, securely connect it and
restart the CPU module. If the same error
code is displayed again, the cause is a
hardware failure of the tracking cable or
CPU module. Please consult your local
Mitsubishi representative.
APPENDICES
LED status,
Corresponding
CPU status
CPU
Qn(H)
QnPH
QnPRH
QnU
LCPU
RUN: Off
ERR.:Flashing
CPU Status:Stop
QnPRH
QCPU
LCPU
RUN: Off
ERR.:Flashing
CPU Status:Stop
QnPRH
A
391