Rockwell Automation 2711-K9A10_K9C10_T9A10_T9C10 DeviceNet Communications User Guide - Manual (Page 26)

26
Publication 2711-6.0.4
Alert Messages These messages appear as a box in the middle of the screen (Error
#636 in upper left of box) and alert the user to a condition. Operation
of the terminal continues. Alert messages can be cleared.
Code 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 Allen-Bradley.
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 Allen-Bradley.
4 Invalid Explicit-Client Address. Occurs at runtime if the
node address associated with the Explicit-Client tag is
the same as the PanelView. Clear the message and determine which tag in the appli-
cation is pointing to the PanelView’s node address. Cor-
rect the application.
7 Change-Of-State Input Overrun. Occurs if PanelView
state changes on I/O input data occurred faster than the
PanelView could send them to the I/O scanner. Clear the message. Excessive network traffic could
cause this problem if inputs are changing rapidly.
8 Identity Object Reset Service received over DeviceNet.
Occurs if an external device sends an Identify Object
Reset Service to the PanelView. An external network device has requested a PanelView
terminal reset. Press a key to clear the alarm.
10 Unsupported DeviceNet message received. Should not occur during normal operation. Clear the
message. If problem reoccurs, contact Allen-Bradley.
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 Allen-Bradley.
13 Invalid Screen Context Priority received. Should not occur in normal operation. Clear the
message. If problem reoccurs, contact Allen-Bradley.
14 Get Next Scan Item Failed in peer mode. Should not occur in normal operation. Clear the
message. If problem reoccurs, contact Allen-Bradley.
15 Explicit-Client 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 Explicit-
Client Tags.
Also occurs when the packet bytes do not match the
number of bytes in the server’s assembly instance.
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.
Also make sure the addressed attribute exists and is set-
table on the network.
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
Allen-Bradley.
19 Get Next Contact Request Failure. In Explicit-Client 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 Allen-Bradley.