Advertisement
Table 11: Database qualifiers
Item
Item
1
Online
2
Restart
3
Communications lost
4
Overridden
16
Database qualifiers
This qualifier indicates if a point has meaning for this site. When supported, this qualifier will be set:
True when the data point is configured to be active.
False when the data point is configured to be inactive (i.e., that phase is not configured) and therefore
unable to obtain valid data.
When not supported, this qualifier will be set true.
Changes to this qualifier generate events tagged with RCU time.
This qualifier indicates if a point's data is not yet updated after a restart. When supported, this qualifier will be
set:
True on restart.
False when data is updated.
When not supported, this qualifier will be set false.
Changes to this qualifier generate events tagged with Fusesaver or RCU time as detailed for that point.
This qualifier indicates if a point's data cannot be retrieved from a Fusesaver. When supported, this qualifier
will be set:
True when no data is being received for this point due to a failure in communications (e.g., failed to
communicate with Fusesaver).
False if data is being received for this point.
False on restart and only set to true if there is a failure to establish communications to the Fusesaver.
When not supported, this qualifier will be set false.
Changes to this qualifier generate events tagged with RCU time.
This qualifier indicates that the data for the point has been overridden by a user and is not true data. Normally
this will only occur during protocol testing. When supported, this qualifier will be set:
False on restart.
True when data is overridden.
When not supported, this qualifier will be set false.
Once a point has been overridden, the overridden qualifier will remain true until the RCU is restarted.
Changes to this qualifier generate events tagged with RCU time.
Events are also generated by changes to
point data; the time tag for data changes is
detailed in the point list below.
When qualifier events are generated
simultaneously with point data, they are
merged as a single event with time tag set
by point-data event.
Example of points from Fusesaver
A configured point that comes from a
Fusesaver will have online set true and on
restart of the RCU will have restart set true.
When the RCU opens communications to the
Fusesaver and gets data, the restart qualifier
will be set to false and will stay false until a
future restart. If after a restart the RCU
cannot establish communications to the
Fusesaver or if communications fails, then
the communications lost qualifier will be
set.
Description
A point that comes from the Fusesaver but
is not configured in this particular
installation, such as a phase-B point in a
single-phase installation that only has phase
A, will have online set to false and restart
set true and communications lost set false.
Example of point from RCU
A point such as "door open," which is always
configured and always up-to-date, will
always have online set true and restart set
false and communications lost set false.
Advertisement
