ProSoft Technology ILX56-MM - Manual (Page 96)

Reference ILX56-MM ♦ ControlLogix Platform
User Manual InRAx Message Manager for Industrial Communication
Page 96 of 112 ProSoft Technology, Inc.
February 6, 2012
6.4.6 Operation of Transfer Status
When an error occurs:
The Error Code will be transferred to the desired destination tag selected to
contain the "Transfer Error Code".
The Error Count will be incremented and transferred to its desired destination
tag.
When the condition that caused the error is corrected, and the transfer
completes successfully, an error code of zero will be transferred to the
destination tag selected for the :Transfer Error Code", and the previous error
code will be overwritten.
If the condition is not cleared prior to another transfer attempt and the error
reoccurs, the error code will once again be transferred and the error count will
be incremented and transferred.
If the latest error detected is different from the previous error, the new error
code will overwrite the previous error code.
o
Occurrences of errors will be influenced by the selected "On Transfer
Technique" for a particular transfer list.
o
If the "Retry" technique is selected, the transfer causing the error will be
repeated until the transfer is successful. Subsequent transfers in the
transfer list will not be executed and any errors in them will not be
annunciated.
o
If the "Continue" technique is selected, then each transfer in the transfer
list will be attempted and any errors will be annunciated.
o
If the "Abort" technique is selected, the transfer that generated the error
will be annunciated but the remainder of the transfer list will not be
executed.
Error messages have the following general format:
ErrorCodeString ContextString
Where:
ErrorCodeString = Text string derived directly from an error code. For
example, scanner error code 804h = “timeout”.
ContextString = Context description. For example, if an error occurs while
reading trigger compare tag #1:
ContextString = “reading cmpVal 1 (TagPath), trig TrigName”, where:
TagPath = Configuration defined device path and tag name,
EnetBridge\PLC5\N7:1 for example.
TriggerName = Configuration defined trigger name.
Error codes in the 1h-1FFh range are generic driver errors. Codes in the 201h-
7FFh are driver specific errors (more than one driver may have an error 201h).
Codes in the 801h-1FFFh are scanner errors. Errors not specifically listed in this
document will likely require engineering intervention to determine the cause
(internal error, program bug, or unexpected/rare communications error).