Mitsubishi Melsec-Q Series User Manual page 446

Error code
Error item
(Hexadecimal)
4100
H
4101
H
4102
H
4103
H
4105
H
4106
H
Other errors
4107
H
4108
H
4109
H
410A
H
410B
H
4110
H
CPU mode
error
4111
H
12 - 151
Table12.2 Error code
Error details
CPU module hardware fault
Serial communication connection was executed
for a different CPU module series.
An attempt was made to erase the Flash ROM
during use of the file register.
The instruction written during RUN is wrong or
illegal.
CPU module internal memory hardware fault
The command cannot be executed since the CPU
module is performing system initialization pro-
cessing.
An attempt was made to perform the operation of
the function unavailable for the target CPU mod-
ule model name.
Operation cannot be made normally by device
monitor/test.
The specified operation cannot be executed since
the monitoring, set the condition for other appli-
cation in same computer, is in execution.
The specified command cannot be executed
because of online prgram change.
The registration of monitoring condition was can-
celed because of online program change.
Since the CPU module is in a stop error status, it
cannot execute the request.
The requested operation cannot be performed
since the other CPU modules have not yet started
in the multiple CPU system.
Corrective action
Change the CPU module.
Check the CPU module series.
Execute again after setting the CPU module to the STOP
status.
Execute online program change again, or write the program
after setting the CPU module to the STOP status.
Change the CPU module.
Execute the operation again after the CPU module has
started.
Do not execute the function unsupported by the target CPU
module.
Execute device monitor/test again. Before execution, check
that access is not made to the access prohibited area.
Execute the request again after deregistering the monitoring
condition on the same screen.
Execute the request again after the online program change.
Execute the registration of monitoring condition again after
the online program change.
Execute the request again after resetting the CPU module.
Execute the request again after the other CPU modules have
started.