Download JMobile Suite User Manual

There is some server specific problem with the
configuration. For example, the tag in question has
been deleted from the configuration file (tags.xml).
This quality may reflect that no value is available at this
time, for reasons such as the value may have not been
provided by the data source.
4
BAD
8
BAD
12
BAD
A device failure has been detected
16
BAD
Timeout occurred before device responded.
24
BAD
Communications have failed.
28
BAD
32
BAD
There are no data found to provide upper or lower
bound value (trend interface specific flag).
No data have been collected (i.e. archiving not active.
Trend interface specific flag).
64
UNCERTAIN There is no specific reason why the value is uncertain.
65
UNCERTAIN
66
UNCERTAIN
67
UNCERTAIN
84
UNCERTAIN
85
UNCERTAIN
86
UNCERTAIN
87
UNCERTAIN
192
GOOD
There is no specific reason why the value is uncertain.
(The value has ‘pegged’ at some lower limit)
There is no specific reason why the value is uncertain.
(The value has ‘pegged’ at some high limit.)
There is no specific reason why the value is uncertain.
(The value is a constant and cannot move.)
The returned value is outside the limits defined for it.
Note that in this case the “Limits” field indicates which
limit has been exceeded but the value can move farther
out of this range.
The returned value is outside the limits defined for it.
Note that in this case the “Limits” field indicates which
limit has been exceeded but the value can move farther
out of this range. (The value has ‘pegged’ at some
lower limit)
The returned value is outside the limits defined for it.
Note that in this case the “Limits” field indicates which
limit has been exceeded but the value can move farther
out of this range. (The value has ‘pegged’ at some high
limit.)
The returned value is outside the limits defined for it.
Note that in this case the “Limits” field indicates which
limit has been exceeded but the value can move farther
out of this range. (The value is a constant and cannot
move.)