12 - 240
12.3 Error Code List
12.3.11 Error codes returned to request source during communication with CPU module
12
TROUBLESHOOTING
Table12.12 Error code
Error code
(Hexadecimal)
Error item Error details Corrective action
4248
H
Redundant
system-related
error
• Communication was made during system
switching.
• The system specified in the transfer setup
(request destination module I/O number)
does not exist.
• Execute again after system switching.
• After checking whether the specified system exists or
not, restart communication.
4249
H
The redundant system is not established.
(Control system/standby system or System A/
System B not yet definite)
• Normally start the system as the redundant system.
(Make communication again after establishing the
system.)
• Execute again after changing the transfer setup
(request destination module I/O number) to "No
settings have been made" (03FF
H).
424A
H
The command that could not be processed
was executed when the transfer setup
(request destination module I/O number) is
Control system/Standby system/System A/
System B.
Execute again after changing the transfer setup (request
destination module I/O number) to "No settings have
been made" (03FF
H).
424B
H
The command cannot be executed since
system switching is inhibited by the manual
system switching enable flag (SM1592).
Manual system switching is inhibited by the manual
system switching enable flag (SM1592). Execute again
after turning ON SM1592.
424C
H
The specified command cannot be executed
during online program change operation.
Execute again after the online program change operation
is finished.
424D
H
The transfer setup or function unavailable for
the debug mode was used.
• Execute again after changing to the backup mode.
• Execute again after changing the transfer setup
(request destination module I/O number) to System A
or control system.
424E
H
The control system/standby system specifying
method is not supported.
This function cannot be executed since it is not
supported.
424F
H
System switching was executed by the other
condition during execution of system switching
by GX Developer.
Although system switching was executed from GX
Developer, system switching was executed first by the
other condition. Check the system for any problem and
execute the operation again as necessary.
4250
H
Sum check error occurred in tracking
communication.
Execute communication again after changing the
tracking cable.
If the same error recurs after the tracking cable is
changed, the cause is the hardware fault of the CPU
module.
(Please contact your local nearest Mitsubishi or
representative, explaining a detailed description of the
problem.)
4251
H
The command cannot be executed in the
separate mode.
Execute again after changing to the backup mode.
4252
H
System switching was not executed since an
error occurred in the redundant system
compatible network module of the standby
system.
By monitoring SD1690 (other system network module
No. that issued system switching request), identify the
faulty redundant-compatible intelligent module of the
standby system, then remove the module fault, and
execute again.