Delta AH500 series, Hardware Operation Manual

Page: 576 / 681

C h a p t e r 1 2 Tr o u b l e s h o o t i n g
1 2 - 2 7
12.2.6
Troubleshooting for EtherNet/IP
Error
Code
Description How to fix them
16#B100 I/O Connections Duplicated
1. Check if the system has created the I/O
connections.
2. Change the connection type to Listen Only.
16#B106 Ownership Conflict
1. Check the scanner owner.
2. Reconfigure the invalid scanner.
3. Change the connection to multicast.
16#B110 Target for Connection not Configured
1. Check the I/O connection status.
2. Activate the I/O connections again.
16#B111 Adapter RPI Not Supported Check the RPI for the adapter.
16#B113 Out of Connections
1. Check if the connection exceeds the limit.
2. Reduce the number of the product
connection.
16#B119 Non-Listen Only Not Opened
1. Check if the system has created the I/O
connections.
2. Check the scanner I/O connection status.
16#B127 Invalid Originator to Target Size
1. Check the module number and the product
setup file to see if they are matched.
16#B128 Invalid Target to Originator Size
2. Check the output size in the connection
parameters.
16#B129
The configuration path parameters in the
EDS file are mismatched.
1. Check if the product information and the EDS
file are matched.
2. Reload the EDS file.
3. Ask the vendor of the device for the EDS file.
16#B12D Consumed Tag does not exist.
Check if the parameters in the consumed tag are
correctly set.
16#B12E Produced Tag does not exist.
Check if the parameters in the produced tag are
correctly set.
16#B203 I/O Connection Timeout
1. Check the network connection status.
2. Check if the module is working fine.
3. Increase the RPI value.
16#B204 Unconnected Request Timeout
No response from the adapter; check if the
power and the network connection of the
adapter are working properly.
16#B302
Network Bandwidth NOT Available for
Data
1. Check the I/O connection limit between the
scanner and the adapter.
2. Increase the RPI value or reduce the number
of the connections.
16#B315 Invalid Segment in Connection Path
Check the module number and the product
setup file to see if they are matched.