Rockwell Automation 1788-EN2DNR EtherNet/IP to DeviceNet Linking Device User Manual User Manual
Page 43
![background image](/manuals/579864/43/background.png)
Rockwell Automation Publication 1788-UM059A-EN-P - August 2014
43
Diagnostic Web Pages
Chapter 6
80
Module is in IDLE mode
Put controller in RUN mode. Enable RUN bit
in module command register.
81
Module is in FAULT mode
Check Module Command Register for fault
bit set.
82
Error detected in sequence of fragmented I/O
messages from device
Check scan list table entry for slave device to
make sure that input and output data
lengths are correct. Check slave device
configuration.
83
Slave device is returning error responses when
module attempts to communicate with it
Check accuracy of scan list table entry. Check
slave device configuration. Slave device can
be in another master’s scan list. Reboot slave
device.
84
Module is initializing the DeviceNet network
None. This code clears itself once module
attempts to initialize all slave devices on the
network.
85
Data size was incorrect for this device at
runtime
Slave device is transmitting incorrect length
data. Try replacing the device.
86
Device is producing zero length data (idle
state) while module is in Run mode
Check device configuration and slave node
status.
87
The primary owner has not allocated the slave
Put the primary owner on line.
88
The connection choices (such as polled or
strobed) between the primary connection and
the shared input only connection do not
match
Reconfigure the shared input only
connection's choices to be the same as, or a
subset of, the primary connection's
choice(s).
89
Slave device initialization using Auto Device
Replacement parameters failed
Put the slave device into configurable mode.
Check the slave's EDS file, if the slave is
configured offline.
Check to see if the slave device has been
replaced with an incompatible device.
90
User has disabled communication port
Check Module Command Register for
DISABLE bit set.
91
Bus-off condition detected on comm port.
Module is detecting communication errors
Check DeviceNet connections and physical
media integrity. Check system for failed
slave devices or other possible sources of
network interference.
92
No network power detected on
communication port
Provide network power. Make sure that
module drop cable is providing network
power to module comm port.
95
Application nonvolatile memory update in
progress
Do nothing. Do not disconnect the module
while application nonvolatile memory
update is in progress. You lose any existing
data in the module’s memory.
96
COMM port in Test mode
Do nothing.
97
Module operation halted by user command
Check Module Command Register for HALT
bit set.
98
General firmware error
Replace module.
99
System failure
Replace module.
Node Status Codes (Continued)
Status Code
Description
Action