How status flags are set

Status flags are set differently depending on the type of point or control object. The following sections explain:

Refer also to the Drivers Guide section “Proxy point status” for further details.

Simple control point status

For simple control points (NullProxyExt) the following status flags are the only ones set and cleared:

alarm

Point is currently in an alarm condition as defined in its alarm extension.
unackedAlarm

Point has alarm extension assigned to an alarm class requiring acknowledgment, but the last alarm event has not yet been acknowledged. Point may/may not be in alarm.
override

Writable points only, during a user-initiated action at priority levels 8 (override) or 1 (emergency). The override flag clears when the action “times out,” or when a user issues an “auto” action at that same priority level.
null

Writable point has “null” or otherwise “invalid” value at In1—In16, plus “null” configured as “Fallback” value. See About “isValid” status check.

See Figure 116 for examples of override and alarm status in simple control points.

Figure 116. Status with simple control points

Propagate Flags status option (linked Math and Logic objects)

By default, kitControl objects maintain independent status flags from input-linked points. However, as a configuration option in each math or logic-type kitControl object (kitControl palette folders “Math” and “Logic”), you can specify “out” status to propagate from input status.

The object’s Propagate Flags property allows you to select any combination of the following status types for propagation:

disabled
fault
down
alarm
overridden

If the math or logic object has multiple inputs, and you set the propagateFlags property to select one or more of the statuses above, simple “OR” logic is used across all inputs for the propagation of each selected status.

Depending on usage, status propagation may be extensive. Note that four of the five status types (all except alarm and overridden) are “invalid status,” meaning they cause the output of the object (if linked) to be considered invalid at its destination target. See About “isValid” status check.

As an example of status propagation, some number of NumericWritable points are used to establish setpoints, and you link them all to a Math: Average object for downstream zone control. In turn, the Average object feeds a Math: Reset object. Both math objects have “override” enabled in their “propagateFlags” property. A user issues an override (action) to one of the NumericWritable points, to override a setpoint (Figure 117).

Figure 117. Status propagation in linked writable points, kitControl objects

For the duration of the override, the linked Average object will also have an overridden status, as will the Reset object, and so on. However, note that the linked writable point (NWcombined) in this example does not have overridden status—status never propagates to any point.

Status propagation did not occur in Niagara r2, and is a new configuration option in NiagaraAX. Before using this feature in an actual job, you should test and evaluate results to be sure it has the desired effect. For example, if a Logic or Math object is exposed in a graphic and appears overridden, a user may (incorrectly) assume that they can right-click command (perform an action) on that kitControl object, based on status color indication.