Mitsubishi Electric MELSEC iQ-R Series User Manual page 613

Error Error name
code
413DH File related error
413EH File related error
413FH File related error
414AH Intelligent function module
specification error
414CH Intelligent function module
specification error
4150H File related error
4151H File related error
4160H Online registration error
4168H Online registration error
4169H Online registration error
416AH Online registration error
416BH Online registration error
41C1H File related error
41C2H File related error
41C3H File related error
41C4H File related error
41C5H File related error
41C7H File related error
41C8H File related error
41C9H File related error
41CAH File related error
41CBH File related error
Error details and cause
• The specified file capacity cannot be secured.
• Operation is disabled for the specified drive
(memory).
• The file is inhibited to be written to the file storage
area.
• In a multiple CPU system, operation was
performed to a non-controlled intelligent function
module or network module.
• The specified buffer memory address cannot be
accessed.
• An attempt was made to initialize the drive
(memory) protected by the system.
• An attempt was made to delete the file/folder
protected by the system.
• The registered number of I/O devices of the
forced on/off target exceeded the maximum.
• The number of registered settings of the device
test with execution conditions has exceeded 32.
• No settings of the device test with execution
conditions are registered.
• The specified execution conditions do not exist.
(Device test with execution conditions)
• Other than the ladder program was specified for
the registration of the device test with execution
conditions.
• The format information data of the specified drive
(memory) is abnormal.
• File open specification data for file access is
wrong.
• Simultaneously accessible files exceeded the
maximum.
• Simultaneously accessible files exceeded the
maximum.
• The specified file does not exist.
■When CPU Module Logging Configuration Tool is
used
When an attempt was made to re-register the data
logging with the previous settings, the
corresponding file did not exist.
• The specified file/folder or drive (memory) does
not exist.
• The size of the specified file has exceeded that of
the existing file.
• Access to the file sector has failed.
• The format information data of the target drive
(memory) is abnormal.
• Access to the file sector has failed.
• The format information data of the target drive
(memory) is abnormal.
• The file name is specified in a wrong method.
Action
• Execute again after increasing the capacity of the specified
drive (memory).
• Execute again after changing the target drive (memory).
• Execute again after changing the specified drive (memory).
• Execute the operation again from the control CPU of the
target module.
• Execute again after checking the buffer address.
• Do not initialize the target drive (memory) as it cannot be
initialized.
• Do not delete the target file as it cannot be deleted.
• Cancel the registration of I/O devices of the forced on/off
target that is not used.
• Disable the settings of the device test with execution
conditions registered in the CPU module. Alternatively,
reduce the number of executional conditioned device tests to
be registered at a time.
• Check the number of registered settings of the device test
with execution conditions in the CPU module, and disable the
settings.
• Check whether the execution conditions (program block, step
No., and execution timing) specified for disabling settings are
registered in the CPU module.
• Check and correct the program block specified when the
settings of the device test with execution conditions are
registered or disabled.
• The file information data may be corrupted.
• Back up data in the CPU module, and then initialize the
memory.
• Execute again after checking the specification data.
• Execute again after decreasing file operations.
• Execute again after decreasing file operations.
• Execute again after checking the file.
• Execute again after checking the file/folder or drive
(memory).
• Execute again after checking the size of the specified file.
• If the error recurs after re-execution, the file information data
may be corrupted.
• Back up data in the CPU module, and then initialize the
memory.
• Back up data in the CPU module, and then initialize the
memory.
• Back up data in the CPU module, and then initialize the
memory.
• Execute again after checking the file name.
36 ERROR CODES
36.4 List of Error Codes
36
611