Rockwell Automation 1788-EN2DNR EtherNet/IP to DeviceNet Linking Device User Manual - Manual (Page 42)

42 Rockwell Automation Publication 1788-UM059A-EN-P - August 2014
Chapter 6 Diagnostic Web Pages
Invalid Nodes
The Invalid Nodes page indicates which DeviceNet nodes are not the correct
device type. If a node’s device type is different than that configured in the scan
list, the page displays ‘Invalid’ next to the node’s MAC ID. Note that only nodes
configured as slaves to the linking device are updated on this page.
Node Status
The Node Status page displays the current status of all DeviceNet nodes that are
configured as slaves to the linking device and the linking device itself. The status
of each node is displayed next to the node’s MAC ID. Note that only nodes
configured as slaves to the linking device and the linking device itself are updated
on this page.
The page displays the status textually for many of the common status values.
However, to save web page size, many of the status values are displayed only
numerically. The table below describes the meaning of each status value.
Node Status Codes
Status Code Description Action
0 OK Do nothing.
60 Duplicate MAC ID test in progress Do nothing.
65 Autoscan active Do nothing. The scanner’s autoscan
functionality is active.
70 Module failed Duplicate Node Address check Change the module address to another
available one. The node address you
selected is already in use on that network.
71 Illegal data in scan list table Reconfigure the scan list table and remove
any illegal data.
72 Slave device stopped communicating Inspect the field devices and verify
connections.
73 Device’s identity information does not match
electronic key in scan list table entry Verify that the correct device is at this node
number. Make sure that the device at the
scrolling node address matches the desired
electronic key (such as vendor, product code,
and product type).
74 Data overrun on port detected Modify your configuration and check for
invalid data. Check network communication
traffic.
75 No traffic detected on the network Check the network configuration.
76 No direct network traffic for module detected None. The module hears other network
communication.
77 Data size expected by the device does not
match scan list entry Reconfigure your module for the correct
transmit and receive data sizes.
78 Slave device in scan list table does not exist Add the device to the network, or delete the
scan list entry for that device.
79 Module has failed to transmit a message Make sure that your module is connected to
a valid network.
Check for disconnected cables.