Troubleshooting ethernet/ip i/o – Delta RMC151 User Manual
Page 477
6 Communication
These status bits are located in the DDT input structure in a field called Status, which is
an array of 16 BYTEs. To determine the correct bit to check for a given target device, you
must locate the Connection Bit field for the device:
1. Start Unity Pro.
2. In the DTM Browser, right click on the Ethernet communication module (named
‘NOC01’ in this example) and click Open.
3. In the NOC01 – fdtConfiguration window, in the left-side tree, expand the Device
List group, expand the target device (RMC) that you want to look at, and select the
connection node named Input/Output, which will generally be the only connection
listed. Then in the right part of the window, select the Connection Settings tab, and
look at the Connection Bit value, which should be in the range of 0..127:
The value of the Connection Bit is the bit offset from the start of the 16-byte
HEALTH_BITS_IN [] array located in the input Derived Variable created for the
EtherNet/IP communication module. For example, for a module named NOC01, offsets 0-
7 correspond to NOC01_IN.HEALTH_BITS_IN[0].0 to NOC01_IN.HEALTH_BITS_IN[0].7,
offsets 8-15 correspond to NOC01_IN.HEALTH_BITS_IN[1].0 to
NOC01_IN.HEALTH_BITS_IN[1].7, and so on. If this bit is 1, then the connection is
healthy. If this bit is 0, then the connection has been lost.
6.8.10.6.5. Troubleshooting EtherNet/IP I/O
Using the Event Log
The Event Log is the primary troubleshooting tool in the RMC for EtherNet/IP I/O. It can
record every change in the EtherNet/IP I/O data received (consumed) by the RMC. This is the
Output Data from the PLC. It does not record the data produced by the RMC (the Input Data in
the PLC).
The Event Log can report the following events based on Incoming I/O Data:
deltamotion.com
457