Other Error Codes - Mitsubishi Electric MELSEC iQ-R Series User Manual

33.2

Other Error Codes

The following table shows the error codes detected by other than self-diagnostics.
Error Error name
code
4001H Common error
4002H Common error
4003H Common error
4004H Common error
4005H Common error
4008H Common error
4010H CPU module operation
related error
4013H CPU module operation
related error
4021H File related error
4022H File related error
4023H File related error
4024H File related error
4025H File related error
4026H File related error
4027H File related error
4028H File related error
4029H File related error
402AH File related error
402BH File related error
402CH File related error
4030H Device specification
error
4031H Device specification
error
4032H Device specification
error
33 ERROR CODE LIST
250
33.2 Other Error Codes
Error details and cause
• An unsupported request was executed.
(The request was issued to CPU module which does not
support the request.)
• An unsupported request was executed.
• Command for which a global request cannot be
performed was executed.
• A request was issued to the system file.
• The volume of data to be handled by the specified
request is too large.
• The CPU module is BUSY. (The buffer is not empty.)
• Because the CPU module is in the Y OUT state, the
request cannot be executed.
• Because the CPU module is not in the Y STOP state,
the request cannot be executed.
• The specified drive (memory) does not exist, or has an
error.
• The file with the specified file name or file number does
not exist.
• The file name and file number of the specified file do
not match.
• The specified file cannot be handled.
• The specified file is currently processing a request
from another engineering tool.
• Specifying the file password set to the target drive
(memory) is required.
• The specified range exceeded the file size.
• The same file already exists.
• The specified file capacity cannot be reserved.
• The specified file has an error.
• The request cannot be executed in the specified drive
(memory).
• The request cannot be executed currently.
• The specified device name cannot be handled.
• The specified device number is out of range.
• The CPU module does not support the specified
device name.
• The specified device modification is incorrect. Or, the
device names (TS, TC, SS, SC, CS, or CC) which
cannot be used for random read/random write (in word
units)/monitor registration/monitor command of SLMP/
MC protocol have been specified.
Corrective action
• Check the command data of SLMP/MC protocol.
• Check the CPU module name selected with an
engineering tool.
• Check the target CPU module name.
• Check the command data of SLMP/MC protocol.
• Check the CPU module name selected with an
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
contact your local Mitsubishi Electric sales office or
representative.
• Check the command data of SLMP/MC protocol.
• Check the command data of SLMP/MC protocol.
• Check the command data of SLMP/MC protocol.
• Execute the request again after arbitrary period of time
has elapsed.
• Execute the request after setting the CPU module to
the Y STOP state.
• Execute the request after setting the CPU module to
the Y STOP state.
• Check the status of the specified drive (memory).
• Back up the data in the CPU module, and then initialize
the memory.
• Check the specified file name and file number.
• Delete the file, and then create a file again.
• Do not access the specified file.
• Forcibly execute the request. Or, execute it again once
the processing from another engineering tool has been
completed.
• Specify the file password set to the target drive
(memory), and access it.
• Check the specified range, and access within the
range.
• Forcibly execute the request. Or, change the file name
and execute the request again.
• Review the specified file capacity, and execute the
request again.
• Back up the data in the CPU module, and then initialize
the memory.
• Execute the request again after placing the CPU
module into the Y STOP state.
• Execute it again after a while.
• Check the specified device name.
• Check the specified device number.
• Check the device assignment of the CPU module.
• Check the specified device name.
• Check the specified device modification method.
• Check the specified device name.