Publication 2711-UM014B-EN-P
B-10 Messages, Codes and Self-Test Numbers
Alert codes appear as a box in the middle of the screen. Error 636
appears in the upper left corner. Operation of the terminal continues.
Alert messages can be cleared.
DeviceNet Alert Codes Indicates: Recommended Action
2 Unsupported DeviceNet Message received. The Network
Access Object received a message that is not supported.
Should not occur in normal operation. Clear the message.
If problem re-occurs, contact technical support.
3 Initial Writes Failure. The Motherboard failed to send all
input data to the daughter card prior to network startup.
Should not occur during normal operation. Clear the
message. If problem reoccurs, contact technical support.
4 Invalid Peer Address. Occurs at runtime if the node
address of a peer tag is the same as the PanelView.
Clear the message and determine which tag in the
application is pointing to the PanelView’s node address.
Correct the application.
7 Change-Of-State Input Overrun. Occurs if PanelView state
changes on I/O input data occurs faster than the
PanelView can send them to the I/O scanner.
Clear the message. Excessive network traffic could cause
this problem if inputs are changing rapidly.
8 An external network process has caused the reset of the
network access process. Connections are temporarily lost.
Occurs if an external device sends an Identify Object Reset
Service to the terminal or if an external device changes the
terminal’s node address (directly or using the Offline
Connection Set).
No action required. Any server connections will need to be
re-established.
10 Unsupported DeviceNet message received. Should not occur during normal operation. Clear the
message. If problem reoccurs, contact technical support.
12 Invalid ASA Number (0x00000000 or 0xFFFFFFFF). Occurs if
the flash memory is corrupt or an invalid ASA number was
programmed.
Clear the message. The message occurs each time the
terminal is reset. The terminal operates normally but you
should correct the problem. Contact technical support.
14 Get Next Scan Item Failed in peer mode. Should not occur in normal operation. Clear the message.
If problem reoccurs, contact technical support.
15 Peer Input Data not received. Will occur if an input (push
button) changes a second time before its previous state
was sent on the network. Only for Peer tags.
Clear the message. Excessive network traffic could cause
this problem if inputs are changing rapidly. Handle high
speed input data over I/O connections if possible.
16 I/O Connection Size does not match size of I/O data in
Assembly Instances 1 & 2. Programmed connection sizes
for I/O do not match the amount of data represented by the
I/O type tags.
Clear the message and if the problem reoccurs, consult
technical support.
19 Get Next Contact Request Failure. In Peer Mode scanning,
the request to obtain the next tag in current context failed.
Should not occur in normal operation. Clear the message.
If problem reoccurs, contact technical support.
20 Autobaud Failure. The autobaud process failed to detect a
valid baud rate within 10 seconds. Occurs if network traffic
is nonexistent or intermittent.
Start the terminal when network traffic exists or use a
fixed baud rate.
23 Nonvolatile Objects have been reset. Nonvolatile storage
of some objects required a full reset on powerup. Certain
nonvolatile values will be reset to defaults.
Can occur when the daughtercard firmware in the terminal
is upgraded. Clear the message and continue. If problem
reoccurs, contact technical support.
38 An external client device on the network has performed a
Set Attribute request on the Baud Rate setting. The baud
may be different on next terminal reset.
Confirm the Active Baud on the Communication Setup
screen of the terminal.
To Next Page
Loading...
Need help?
General
