Rockwell Automation 5094-OB32XT - Input Tags

Rockwell Automation Publication 5094-UM001E-EN-P - April 2020 171
Module Tag Definitions Appendix B
Input Tags
Tab le 56 describes the 5094-OB16 module input tags.
Table 56 - 5094-OB16 Module Input Tags
Name Data Type Definition Valid Values
RunMode BOOL The point’s operating state • 0 = Idle
•1 = Run Mode
ConnectionFaulted BOOL Indicates if a connection is running.
The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1.
• 0 = Connection running
• 1 = Connection not running
DiagnosticActive BOOL Indicates if any diagnostics are active or if the prognostics
threshold is reached.
• 0 = No diagnostics active
• 1 = One or more diagnostics are active or the
prognostics threshold is reached
Uncertain BOOL Indicates if the module is operating outside is designed
operating range of if data is under manual or override
control.
• 0 = Good
• 1 = Uncertain
DiagnosticSequenceCount SINT Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition
transitions from detected to not detected.
Set to zero by product reset or power cycle. Wraps from 255
(-1) to 1, skipping zero.
-128…+127
The value of 0 is skipped except during module
powerup.
CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master. • 0 = CIP Sync is not available
• 1 = CIP Sync is available
CIPSyncTimeout BOOL Indicates that the module was once synced with a 1588
master, but is not now due to a timeout.
• 0 = A valid time master has not timed out
• 1 = A valid time master was detected on the
backplane, but the time master has timed out.
The module is using its local clock and can be
drifting away from the last known master time.
Ptxx.Data BOOL Indicates the current digital input value. • 0 = Off
•1 = On
Ptxx.Fault BOOL Indicates that point data is inaccurate and cannot be trusted
for use in the application.
For more information, see Module Data Quality Reporting
on
page 47.
• 0 = Good
• 1 = Bad, causing fault
The typical causes of uncertain data are the
following:
– Field Power Loss condition
– No Load condition
– Short Circuit condition
If the tag is set to 1, you must troubleshoot the
module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag
automatically resets to 0.
Ptxx.Uncertain BOOL Indicates that the point data can be inaccurate but the
degree of inaccuracy is not known.
For more information, see Module Data Quality Reporting
on
page 47.
• 0 = Good data
• 1 = Uncertain data
If the tag is set to 1, you must troubleshoot the
module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag
automatically resets to 0.
Ptxx.NoLoad BOOL Indicates that the signal wire has been disconnected from
one of its terminals or the RTB has been removed. Used with
Output points.
•0 = No fault
•1 = Fault
Ptxx.ShortCircuit BOOL Indicates an output short circuit or overcurrent. • 0 = No short circuit
• 1 = Short circuit or overcurrent