Communication Status Error Messages - Allen-Bradley 2755-SN3 Application Manual

17–22 Communicating with PanelView 900t Terminals on a DeviceNet Network
Code
No connections established. Occurs on power-up until a
1
device connection is established on the network.
A connection is in the timed out state. Occurs once I/O
2
messaging is stopped after an I/O connection has been
running.
An Explicit-Client tag cannot be obtained. Occurs if the device
associated with an Explicit-Client tag is not responding or the
peer tag does not exist at the specified class, instance, and
3 attribute number.
A zero length I/O message was received placing the I/O
4 application in idle mode. Occurs when the scanner is in
program mode.
Message Overrun. Message traffic from the PanelView is
being generated quicker than it is possible to send the data.
5 Occurs with large I/O sizes when Change-Of-State is being
used and state changes are occurring very quickly or if polling
too fast when large I/O sizes are involved.
No network power detected. Occurs if no network 24V is
11
present.
Dup MAC Failure. Occurs if the PanelView powers up with the
12
same Node Address present on the network.
Bus-Off Interrupt occurred. CAN Chip is held in reset. Caused
by noise on network signal lines or attempting to attach to the
13
network at the wrong baud rate. May also occur if some other
device on the network attaches at the wrong baud rate
Publication 2755-6.8

Communication Status Error Messages

These errors appear as a banner at the top of an application screen
(error #634 in upper left corner) or as Mod/Net LED status display
on the terminal configuration screen.
Errors numbered less than 10 are considered minor fault conditions
and will clear automatically when corrected. Errors numbered above
10 require that the terminal be reset to clear the error.
Indicates Recommended Action(s)
Establish a connection over DeviceNet to the PanelView.
Make sure that wiring is OK on the network and that the
master device (scanner, etc. ) is operational.
Make sure that the specified location of the data is correct and
that the end device is attached and operational. For write
tags, ensure that the appropriate attribute is targeted. If the
targeted device is UCMM capable, ensure it has enough
available explicit message connections to allow the PanelView
to take one. If the targeted device is not UCMM capable,
ensure that it is owned by a Master device (scanner, etc.).
Error clears when switched back to run. Correct the problem
of the Master sending the I/O idle condition.
Slow down I/O polling or the state changes generating change
of state I/O messages. Use cyclic I/O at a fast heartbeat rate
rather than change-of-state. Use the production inhibit
capability on the master.
Make sure DeviceNet wiring is providing power to the
PanelView and reset the terminal.
Change the node address to one not currently in use and reset
the terminal.
Make sure Baud Rate is correct and wiring is correct on the
network, including termination resistors. Reset the terminal.