<< Click to Display Table of Contents >>
Substatus Field |
This field's layout depends on the Quality field.
Substatus for BAD Quality
SubStatus |
Description |
Limit |
|||
---|---|---|---|---|---|
No Limit |
Low |
High |
Constant |
||
Non-specific |
This value is bad, but no specific reason is known |
0 |
1 |
2 |
3 |
Configuration Error |
There is some specific configuration problem in the server. For example, this specific item could be deleted |
4 |
5 |
6 |
7 |
Not Connected |
Input must be logically connected to something, but it is not. This quality may reflect that no value is available at this time, because this value could not be provided by its data source |
8 |
9 |
10 |
11 |
Device Failure |
A device failure was detected |
12 |
13 |
14 |
15 |
Sensor Failure |
A sensor failure was detected (the Limit field may provide additional information) |
16 |
17 |
18 |
19 |
Last Known Value |
Communication failed. However, the last known value is available. Notice that this value's age may be determined by the Timestamp property |
20 |
21 |
22 |
23 |
Communication Failure |
Communication failed. There is no last known value available |
24 |
25 |
26 |
27 |
Out of Service |
Block is off scan, or locked |
28 |
29 |
30 |
31 |
N/A |
Not used |
32 - 63 |
Substatus for UNCERTAIN quality
SubStatus |
Description |
Limit |
|||
---|---|---|---|---|---|
No Limit |
Low |
High |
Constant |
||
Non-specific |
There is no specific reason |
64 |
065 |
066 |
067 |
Last Usable Value |
A device providing this value stopped doing so. The returned value must be considered as old. Notice that this differs from a Bad value with Substatus 5 (last known value). That status is associated specifically with a detectable communication error on a retrieved value. This error is associated with a failure of some external source that would insert something into this value within an acceptable period of time. Notice that this value's age can be determined by the Timestamp property |
68 |
069 |
070 |
071 |
N/A |
Not used |
72 - 79 |
|||
Sensor Not Accurate |
Either this value is stuck at one of sensor's limits (in which case the Limit field must be set to 1 or 2) or this sensor is otherwise known to be out of calibration via some internal diagnosis (in which case the Limit field must be zero) |
80 |
81 |
82 |
83 |
Engineering Unit Exceeded |
The returned value is outside the limits defined for this parameter. Notice that in this case the Limits field indicates which limit was exceeded, but does not necessarily imply that this value cannot move outside the specified range |
84 |
85 |
86 |
87 |
Sub-Normal |
This value is derived from multiple sources and there is a number smaller than required of good sources |
88 |
89 |
90 |
91 |
N/A |
Not used |
92 - 127 |
NOTE |
Servers that do not support Substatus must return 0 (zero). |
Substatus for GOOD Quality
SubStatus |
Description |
Limit |
|||
---|---|---|---|---|---|
No Limit |
Low |
High |
Constant |
||
Non-specific |
This value is good. There are no special conditions |
192 |
193 |
194 |
195 |
N/A |
Not used |
196 - 215 |
|||
Local Override |
Typically indicates that an input was disconnected and a manually-entered value was forced |
216 |
217 |
218 |
219 |
N/A |
Not used |
220 - 255 |
NOTE |
Servers that do not support Substatus for good quality must return 0 (zero). |