Mitsubishi Electric MELSEC iQ-F Series User Manual page 125

Error Error name
code
10EH to TCP error
10FH
110H TCP error
112H TCP error
113H TCP error
114H TCP error
115H TCP error
119H CIP error
11AH CIP error
11BH CIP error
11CH CIP error
11DH CIP error
11EH CIP error
Error details and causes
An error has occurred in TCP
communications.
Socket generation has failed.
Incorrect send data has been specified.
There is insufficient cache memory available.
Failed to set the socket option (non-blocking).
The frame size has exceeded the maximum
size.
A timeout occurred in the connection with the
external device.
An incorrect Forward Open service request
has been received from the external device.
Incorrect network parameters (originator to
target) have been received from the external
device.
Incorrect network parameters (target to
originator) have been received from the
external device.
An incorrect UDP port specification has been
received from the external device.
Participation in a multicast group has failed.
Action
• Retry at a later time.
• Check whether the operating status of the external device is normal.
• Check for errors in the line status.
• The line may be busy, so retry at a later time.
• Reset the CPU module, and then switch it to RUN mode. If the error
occurs again even after the above action is taken, the possible
cause is a hardware failure of the module on which the error
occurred. Please consult your local Mitsubishi representative.
• Retry at a later time.
• Reset the CPU module, and then switch it to RUN mode. If the error
occurs again even after the above action is taken, the possible
cause is a hardware failure of the module on which the error
occurred. Please consult your local Mitsubishi representative.
• Take measures to reduce noise.
• Reset the CPU module, and then switch it to RUN mode. If the error
occurs again even after the above action is taken, the possible
cause is a hardware failure of the module on which the error
occurred. Please consult your local Mitsubishi representative.
• Retry at a later time.
• Restart the FX5-ENET/IP.
• Take measures to reduce noise.
• Reset the CPU module, and then switch it to RUN mode. If the error
occurs again even after the above action is taken, the possible
cause is a hardware failure of the module. Please consult your local
Mitsubishi representative.
• Use EtherNet/IP Configuration Tool for FX5-ENET/IP to write the
parameters to the module again.
• When performing UCMM communications, check whether the
setting details of the UCMM request area are correct.
• Check whether the operating status of the external device is normal.
• Check for errors in the line status.
• The line may be busy, so retry at a later time.
• The external device may not be able to send data at the specified
RPI due to a high communication load, so specify a larger RPI and
connect again.
• Check whether the operating status of the external device is normal.
• Check for errors in the line status.
• The line may be busy, so retry at a later time.
• The external device may not be able to send data at the specified
RPI due to a high communication load, so specify a larger RPI and
connect again.
• Check whether the operating status of the external device is normal.
• Check for errors in the line status.
• The line may be busy, so retry at a later time.
• The external device may not be able to send data at the specified
RPI due to a high communication load, so specify a larger RPI and
connect again.
• Check whether the operating status of the external device is normal.
• Check for errors in the line status.
• The line may be busy, so retry at a later time.
• The external device may not be able to send data at the specified
RPI due to a high communication load, so specify a larger RPI and
connect again.
• Check whether the external device is set to use UDP port number
2222 for EtherNet/IP communications.
• Check whether the operating status of the external device is normal.
• Check for errors in the line status.
• The line may be busy, so retry at a later time.
• The external device may not be able to send data at the specified
RPI due to a high communication load, so specify a larger RPI and
connect again.
• Take measures to reduce noise.
• Reset the CPU module, and then switch it to RUN mode. If the error
occurs again even after the above action is taken, the possible
cause is a hardware failure of the module on which the error
occurred. Please consult your local Mitsubishi representative.
10 TROUBLESHOOTING
10.6 List of Error Codes
10
123