Mitsubishi Electric MELSEC iQ-R Series User Manual page 614

Error Error name
code
41CCH File related error
41CDH File related error
41CEH File related error
41CFH File related error
41D0H File related error
41D1H File related error
41D5H File related error
41D6H File related error
41D7H File related error
41D8H File related error
41DFH File related error
41E0H File related error
41E1H File related error
41E4H File related error
41E7H File related error
41E8H File related error
41E9H File related error
41EBH File related error
41ECH File related error
36 ERROR CODES
612
36.4 List of Error Codes
Error details and cause
• The specified file does not exist. Or, the specified
subdirectory does not exist.
■When CPU Module Logging Configuration Tool is
used
• The data logging was started in a state that sub-
folders for storing data logging files (or folders)
cannot be created or accessed. Or, sub-folders
cannot be created or accessed while the data
logging is being performed or the logged data is
being saved.
• An access to the file is prohibited in the system.
■When CPU Module Logging Configuration Tool is
used
• The data logging was started in a state that files
(or folders) cannot be created or accessed
because a file (or folder) with the same name
exists. Or, files (folders) cannot be created or
accessed while the data logging is being
performed or the logged data is being saved.
• The file cannot be written because the specified
file is read-only.
• The specified drive (memory) has been used
exceeding the capacity.
• The specified drive (memory) has no free space.
Or, the number of files in the directory of the
specified drive (memory) has exceeded the
maximum.
• The file name is specified in a wrong method.
• The SD memory card is disabled by SM606 (SD
memory card forced disable instruction).
• The file of the same name exists.
• The format information data of the specified drive
(memory) is abnormal.
• The format information data of the specified drive
(memory) is abnormal.
• The specified file is being accessed.
• The specified drive (memory) is write-protected.
• The specified drive (memory) is abnormal or
does not exist.
• Access to the SD memory card has failed.
• Access to the SD memory card has failed.
• The format information data of the specified drive
(memory) is abnormal.
• The format information data of the specified drive
(memory) is abnormal.
• The specified file is being accessed.
• The file name is specified in a wrong method.
• The file system of the specified drive (memory) is
logically corrupted.
Action
• Check the file name and subdirectory name. Then, execute
the operation again.
• Do not access the specified file or subdirectory.
• Execute again after checking the file and subdirectory.
• Execute again after checking the open mode of the file.
• Execute again after checking the attribute of the specified
file.
• Execute again after checking the drive (memory) capacity.
• Execute again after increasing the free space of the drive
(memory).
• Delete files in the drive (memory), and execute the function
again.
• Execute again after checking the file name.
• 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.
• Cancel the SD memory card forced disable instruction.
• Forcibly execute the request, or execute after changing the
file name.
• The file information data may be corrupted.
• Back up data in the CPU module, and then initialize the
memory.
• The file information data may be corrupted.
• Back up data in the CPU module, and then initialize the
memory.
• Execute again after a while.
• Execute again after canceling the write protect of the
specified drive (memory).
• Execute the operation again after checking that the SD
memory card has been inserted.
• Back up data, and then initialize the memory.
• Back up data, and then write the data to the data memory.
• Execute the operation again after checking that the SD
memory card has been inserted.
• Execute the operation again after replacing the SD memory
card.
• Back up data, and then initialize the memory.
• The file information data may be corrupted.
• Back up data in the CPU module, and then initialize the
memory.
• The file information data may be corrupted.
• Back up data in the CPU module, and then initialize the
memory.
• Execute again after a while.
• Execute again after checking the file name.
• The file information data may be corrupted.
• Back up data in the CPU module, and then initialize the
memory.