Mitsubishi Electric MELSEC iQ-R-R00CPU User Manual page 774

Error Error name
code
424CH Redundant
system related
error
424EH Redundant
system related
error
424FH Redundant
system related
error
4251H Redundant
system related
error
4252H Redundant
system related
error
4256H Redundant
system related
error
4258H Redundant
system related
error
4259H Redundant
system related
error
425AH Redundant
system related
error
425EH Redundant
system related
error
425FH Redundant
system related
error
4269H Any other error
426AH Any other error
4270H Debug related
function error
4271H Debug related
function error
APPX
772
Appendix 1 Error Codes
Error details and cause
• The request cannot be executed because the online
program change function is being executed.
• The request cannot be executed because an unsupported
system switching is specified.
• The request cannot be executed because system switching
due to a different cause was executed during execution of
system switching by the engineering tool.
• The request cannot be executed because the redundant
system is in separate mode.
• The systems cannot be switched because an error has
occurred in an intelligent function module of the standby
system.
• The request cannot be executed because a timeout error
has occurred in tracking communications.
• The operation mode cannot be changed because the control
system in separate mode is in a state waiting for transition to
RUN.
• The operation mode cannot be changed from separate
mode to backup mode because the communication route
differs from that of when the mode was changed from
backup mode to separate mode.
The system cannot be started as a control system because of
either of the following reasons:
• The system A/B setting has not been determined.
• The system is being changed to the control system.
• Data communications cannot be performed with the other
system because a module communication test is being
executed on a redundant function module.
• The memory copy function cannot be executed because the
CPU module models differ between the control system and
the standby system.
• The remote RUN (function) cannot be executed.
• The date and time data specified by an engineering tool
(personal computer) are less than one hour from the start
time of daylight saving time.
• Data logging is being performed (data logging status: RUN
waiting (no collection), Condition waiting (no collection),
Start waiting (no collection), Pause, Collecting, Trigger
waiting (collecting before trigger), Collecting after trigger, or
Saving the logging data) to another memory.
• The specified data logging is already being performed (data
logging status: RUN waiting (no collection), Condition
waiting (no collection), Start waiting (no collection), Pause,
Collecting, Trigger waiting (collecting before trigger),
Collecting after trigger, or Saving the logging data).
Action
• Execute the request again after the online program change
processing ends.
• Take measures to reduce noise, and execute the request
again. If the same error code is displayed again, the possible
cause is a hardware failure of the target module. Please
consult your local Mitsubishi representative.
• Check that the systems are switched successfully. If not,
monitor SD1644 (Cause of system switching failure),
eliminate the error cause, and then execute the function
again.
• Change the operation mode to backup mode, and execute
the request again.
• Identify an error module by monitoring SD1646 (System
switching request status from a network module of the other
system), eliminate the error cause, and then switch the
systems again.
• Check if the tracking cables have been properly connected.
If the same error code is displayed again even after the
tracking cables are connected properly, the possible cause
is a hardware failure of the CPU module, redundant function
module, or tracking cable. Please consult your local
Mitsubishi representative.
• Change the operating status of the CPU module whose
PROGRAM RUN LED is flashing to RUN by using the RUN/
STOP/RESET switch or remote operation, and change the
operation mode again.
• Change the operation mode using the same communication
route of when the mode was changed from backup mode to
separate mode.
Take the following actions:
• Set one system as system A and the other system as
system B, restart the CPU module.
• Check that the system has been changed to the control
system.
• Retry data communications after the module communication
test ends.
• Match the CPU module model between the systems, and
execute the function again.
• Execute the function again after a while.
• Specify the time to other than one less than one hour from
the start time of daylight saving time using an engineering
tool (personal computer). Then, execute the function again.
• Check and Correct the start time of the daylight saving time
setting.
• Register data logging to the memory where the data logging
is being performed. Or, stop the data logging being
performed and register again.
■When CPU Module Logging Configuration Tool is used
• Start the data logging to the memory where the data logging
is being performed. Or, stop the data logging being
performed, and start the data logging.
• Stop the data logging. Or, write, delete, or register data
logging to the setting number where no data logging is being
performed.