Rockwell Automation 2755-SNx Adaptascan Bar Code Readers - Manual (Page 345)

17–23 Communicating with PanelView 900
t
Terminals on a DeviceNet Network
Publication 2755-6.8
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 particular condition.
Operation of the terminal continues. Alert messages can be cleared.
Code Indicates Recommended Action(s)
2
Unsupported DeviceNet Message type received. A message
was received by the Network Access Object that is not
supported. This should not occur in normal operation. Clear the message
and if the problem reoccurs, consult Allen-Bradley.
3
Initial Writes Failure. The Motherboard failed to send all input
data to the daughter card prior to network startup. This error
should not happen during normal operation. Clear the message and if the problem reoccurs, consult
Allen-Bradley.
4
Invalid Explicit-Client Address. Occurs at run time if the node
address associated with an Explicit-Client tag is the same as
the PanelView’s own. 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 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 a Identity Object Reset
Service to the PanelView. An external network device has requested the PanelView be
reset. Reset the PanelView manually from the configuration
screen.
10
Unsupported DeviceNet message received. Should not occur
under normal operating conditions. Clear the message and if the problem reoccurs, consult
Allen-Bradley.
12
Invalid ASA Number (0x00000000 or 0xFFFFFFFF). Will not
occur unless the flash memory has been corrupted or an
invalid ASA number was programmed in the production
process. Clear the message. The message will reoccur each time the
terminal is reset. The terminal will operate normally but the
problem should be corrected. Consult Allen-Bradley.
13
Invalid Screen Context Priority received. Should not occur
under normal operating conditions. Clear the message and if the problem reoccurs, consult
Allen-Bradley.
14
Get Next Scan Item Failed in peer mode. Should not occur
under normal operating conditions. Clear the message and if the problem reoccurs, consult
Allen-Bradley.
15
Explicit-Client Input Data not received. Will occur if an input
(push-button, etc.) changes a second time before its previous
state was successfully sent on the network. Only for
Explicit-Client 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.
Also make sure that the addressed attribute exists and is
settable 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 Context Request Failure. In Explicit-Client mode
scanning, the request for obtaining the next tag in current
context failed. Should not occur under normal operating
conditions. Clear the message and if the problem reoccurs, consult
Allen-Bradley.