5 TROUBLESHOOTING
5.6 List of Error Codes
127
5
Error codes when a communication error occurs
Error codes for communication errors can be checked with 'Class1 Connection Behavior Error status' (Un\G27392 to
Un\G27647). ( Page 151 Class1 Connection Behavior Error status (Un\G27392 to Un\G27647))
Error code Error details and causes Action
102H EtherNet/IP communication has not started properly. • When UCMM communications are performed, check whether a
module error occurs in the following pages.
Page 110 Checking with LEDs
• 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.
103H A parameter error was detected. • 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.
104H to 105H 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.
• Check the settings of the connection with the external device.
• When Application Trigger is used, check whether the data send
timing is correct.
106H The target device does not exist. • Use EtherNet/IP Configuration Tool to write the parameters to
the module again.
• 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.
107H An error was detected in the memory. • 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.
10AH Production processing failed to start. • 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.
10BH Consumption processing failed to start. • 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.
10CH There is insufficient memory available for connection
processing.
• 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.
To Next Page
Loading...
