EasyManua.ls Logo

Mitsubishi Electric MELSEC iQ-RJ71EIP91 - Page 130

Mitsubishi Electric MELSEC iQ-RJ71EIP91
180 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
128
5 TROUBLESHOOTING
5.6 List of Error Codes
10EH to 10FH An error has occurred in TCP communications. 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.
Check the settings of the connection with the external device.
110H Socket generation has failed. 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.
112H Incorrect send data has been specified. 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.
113H There is insufficient cache memory available. Retry at a later time.
Restart the RJ71EIP91.
114H Failed to set the socket option (non-blocking). 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.
115H The frame size has exceeded the maximum size. Use EtherNet/IP Configuration Tool to write the parameters to
the module again.
When UCMM communications are performed, check whether
the setting details of the UCMM request area are correct.
119H A timeout occurred in the connection with the external device. 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.
11AH An incorrect Forward Open service request has been received
from the external device.
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.
11BH Incorrect network parameters (originator to target) have been
received from the external device.
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.
11CH Incorrect network parameters (target to originator) have been
received from the external device.
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.
Error code Error details and causes Action

Table of Contents

Related product manuals