36 ERROR CODES
36.4 List of Error Codes
603
36
Codes of errors detected by other than the self-diagnostic
function (4000H to 4FFFH)
The following table lists the codes of errors, other than those detected by the self-diagnostic function of the CPU module.
Error codes returned to request source during communications with the CPU module
• Errors generated when the data communications are requested from the engineering tool, intelligent function module, or
network system connected
• Errors generated with the data logging function
These error codes are not stored in SD0 because they are not detected by the self-diagnostic function of the CPU module.
Error
code
Error name Error details and cause Action
4000H Common error • Serial communication sum check error • Connect the serial communication cable correctly.
• Take measures to reduce noise.
4001H Common error • An unsupported request was executed.
(The request was executed to the CPU module that
does not support the request.)
• Check the command data of the SLMP/MC protocol.
• Check the CPU module model name selected in the
engineering tool.
• Check the target CPU module model name.
• Check that the target network number is not duplicated.
4002H Common error • An unsupported request was executed. • Check the command data of the SLMP/MC protocol.
• Check the CPU module model name selected in the
engineering tool.
• Execute the request again.
• If the same error code is displayed again, the possible cause
is a hardware failure of the CPU module. Please consult your
local Mitsubishi representative.
4003H Common error • Command for which a global request cannot be
performed was executed.
• Check the command data of the SLMP/MC protocol.
4004H Common error All the operations to the CPU module are disabled
because of the following reason:
• The CPU module is starting up.
• Perform operations to the CPU module again after the start-
up processing ends.
4005H Common error • The amount of data handled according to a
specified request is out of range.
• Check the command data of the SLMP/MC protocol.
4006H Common error • Initial communication has failed. • When using serial communication, inquire of the external
device manufacturer for support conditions.
• When using serial communication, check the CPU module
model name selected in the engineering tool.
• When using Ethernet communication, shift the
communication start timing.
4008H Common error • The CPU module is BUSY. (The buffer is not
vacant.)
• Execute the request again after the specified period of time
has elapsed.
400BH Common error • A set value of data handled according to a
specified request is invalid.
• Check the request data of a dedicated instruction.
• Check the command data of the SLMP/MC protocol.
4010H CPU module operation
error
• The request cannot be executed because the
CPU module is running.
• Set the operating status of the CPU module to STOP, and
execute the request again.
4013H CPU module operation
error
• The request cannot be executed because the
CPU module is not in the STOP state.
• Set the operating status of the CPU module to STOP, and
execute the request again.
4021H File related error • The specified drive (memory) does not exist or
there is an error.
• Check the specified drive (memory) status.
• Back up data in the CPU module, and then initialize the
memory.
4022H File related error • The file with the specified file name or file No.
does not exist.
• The specified program block does not exist.
■When CPU Module Logging Configuration Tool is
used
The data logging was started in the following state.
• A program name (program No.) that does not
exist was specified.
• Check the specified file name and file No.
• Check the specified program block name.
■When CPU Module Logging Configuration Tool is used
• Check the name of the program specified.
4023H File related error • The file name and file No. of the specified file do
not match.
• Delete the file and then recreate the file.
4024H File related error • The specified file cannot be handled by a user. • Do not access the specified file.