hit counter script

Mitsubishi Electric MELSEC iQ-F FX5 User Manual page 351

Hide thumbs Also See for MELSEC iQ-F FX5:
Table of Contents

Advertisement

Error
Error name
Error details and cause
code
4053H
Protect error
• An error occurred when writing data to the specified drive
(memory).
4060H
Online
• The online debug function is being executed with another
registration error
engineering tool.
4080H
Other errors
• Request data error.
4081H
Other errors
• The search target data cannot be detected.
408BH
Other errors
• The remote request cannot be executed.
4121H
File related error
• The specified drive (memory) or file does not exist.
4122H
File related error
• The specified drive (memory) or file does not exist.
4127H
File related error
• File password 32 mismatch.
4135H
File related error
• The date/time data of the engineering tool (personal
computer) is out of range.
4139H
File related error
• The size of the specified file has exceeded that of the
existing file.
413AH
File related error
• The specified file has exceeded the already existing file
size.
413BH
File related error
• The same file was simultaneously accessed from different
engineering tools.
413EH
File related error
• Operation is disabled for the specified drive (memory).
4171H
CPU module
• The port for communication use is in remote password
built-in Ethernet
locked status.
port error
4181H
CPU module
• Transmission to the receiving modules is unsuccessful.
built-in Ethernet
port error
4183H
CPU module
• Communication with receiving modules was interrupted.
built-in Ethernet
port error
419EH
CPU module
• Connection to the module was unsuccessful or interrupted.
built-in Ethernet
port error
41C5H
File related error
• The specified file does not exist.
41C8H
File related error
• The size of the specified file has exceeded that of the
existing file.
Action
• Check the specified drive (memory). Or, write data again
after changing the corresponding drive (memory).
• Finish the operation of the other engineering tool and then
execute the function again.
• If the operation of the other engineering tool is on hold,
resume and finish the operation of the other engineering
tool, and then execute the function again.
• Check the request data that has been specified.
• Check the data to be searched.
• Reexecute after the CPU module is in a status where the
remote request can be executed.
• For remote operation, set the parameter to "Enable remote
reset".
• Execute again after checking the specified drive (memory)
or file.
• Execute again after checking the specified drive (memory)
or file.
• Execute again after checking the file password 32.
• Execute again after checking the clock setting of the
engineering tool (personal computer).
• Execute again after checking the size of the specified file.
• Execute again after checking the size of the specified file.
• Execute again after a while.
• Execute again after changing the target drive (memory).
• Execute communication after unlocking the remote
password processing.
• Check the external device operation.
• Check the status of the lines, such as cables, hubs and
routes, connected to receiving modules.
• Some line packets may be engaged. Retry to communicate
a little while later.
• The receiving module may have no free space in receive
area (TCP window size is small). Check whether the
receiving module processes receive data, or whether the
CPU module does not send unnecessary data.
• Check whether the settings of the subnet mask pattern and
the default router IP address of the CPU module and the
receiving modules are correct, or whether the class of the IP
address is correct.
• Check the external device operation.
• Check the status of the lines such as cables, hubs and
routes connected to receiving modules.
• Error may be generated when connection is forcibly
canceled during communication. In that case, there is no
issue, so clear the error.
• Check the external device operation.
• Check the status of the lines such as cables, hubs and
routes connected to receiving modules.
• Retry to connect a little while later, if the error occurred in
communication.
• Execute again after checking the file.
• 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.
Appendix 3 Error Code
A
APPENDIX
349

Advertisement

Table of Contents
loading

Table of Contents