Codes Of Errors Detected By Other Than The Self-Diagnostic Function (4000H To 4Fffh) - Mitsubishi Electric MELSEC iQ-R Series User Manual

Process cpu module
Hide thumbs Also See for MELSEC iQ-R Series:
Table of Contents

Advertisement

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
Error name
code
4000H
Common error
4001H
Common error
4002H
Common error
4003H
Common error
4004H
Common error
4005H
Common error
4006H
Common error
4008H
Common error
400BH
Common error
4010H
CPU module operation
error
4013H
CPU module operation
error
4021H
File related error
4022H
File related error
4023H
File related error
4024H
File related error
Error details and cause
• Serial communication sum check error
• An unsupported request was executed.
(The request was executed to the CPU module that
does not support the request.)
• An unsupported request was executed.
• Command for which a global request cannot be
performed was executed.
All the operations to the CPU module are disabled
because of the following reason:
• The CPU module is starting up.
• The amount of data handled according to a
specified request is out of range.
• Initial communication has failed.
• The CPU module is BUSY. (The buffer is not
vacant.)
• A set value of data handled according to a
specified request is invalid.
• The request cannot be executed because the
CPU module is running.
• The request cannot be executed because the
CPU module is not in the STOP state.
• The specified drive (memory) does not exist or
there is an 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.
• The file name and file No. of the specified file do
not match.
• The specified file cannot be handled by a user.
Action
• Connect the serial communication cable correctly.
• Take measures to reduce noise.
• 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.
• 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.
• Check the command data of the SLMP/MC protocol.
• Perform operations to the CPU module again after the start-
up processing ends.
• Check the command data of the SLMP/MC protocol.
• 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.
• Execute the request again after the specified period of time
has elapsed.
• Check the request data of a dedicated instruction.
• Check the command data of the SLMP/MC protocol.
• Set the operating status of the CPU module to STOP, and
execute the request again.
• Set the operating status of the CPU module to STOP, and
execute the request again.
• Check the specified drive (memory) status.
• Back up data in the CPU module, and then initialize the
memory.
• 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.
• Delete the file and then recreate the file.
• Do not access the specified file.
36 ERROR CODES
36.4 List of Error Codes
36
603

Advertisement

Table of Contents
loading

Table of Contents