Mitsubishi Electric MELSEC iQ-F Series User Manual page 126

Error Error name
code
11FH Memory error
120H CIP error
121H Connection error
124H Connection error
126H EPIC error
128H EPIC error
129H EPIC error
12AH EPIC error
12BH EPIC error
12DH EPIC error
12EH Disconnected error
12FH System error
130H to Connection error
131H
132H Memory error
133H Disconnected error
134H Connection error
135H CIP error
136H Connection error
10 TROUBLESHOOTING
124
10.6 List of Error Codes
Error details and causes
An error was detected in the memory.
The available resources are insufficient.
The connection has stopped.
The connection has been set to disabled.
An incorrect RegisterSession command has
been received.
An incorrect request frame has been
received.
An incorrect session handle has been
received.
Request data with an incorrect size has been
received.
Request data including an unsupported
protocol version has been received.
Request data with an incorrect size has been
received.
Communications have been disconnected.
The connections have been disconnected.
Forward Close has been received from the
external device.
An error was detected in the memory.
Communications have been disconnected.
A timeout occurred in the connection with the
external device.
A timeout occurred in the connection with the
external device.
A timeout occurred in the connection with the
external device.
Action
• 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.
• 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.
• 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 the parameter set with EtherNet/IP Configuration Tool for FX5-
ENET/IP, and rewrite the parameter to the module.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
Check whether 'EtherNet/IP communication start request'
(Un\G37.b0) is on.
• 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.
• 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.
• 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.
Check whether 'EtherNet/IP communication start request'
(Un\G37.b0) is on.
• 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.
• 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.