Extensions and kitControl components

You can add point extensions to many kitControl components, for example an alarm extension, history extension, or perhaps a control extension. For exceptions, see Components that cannot receive extensions. For general details on extensions, see “About point extensions” in the User Guide.

Some examples of using extensions with kitControl components include the following:

Average object (Math folder)

Inputs are linked to multiple proxy NumericPoints, each representing a room temperature. The Average object represents a “Zone” temperature (average). To this object you may wish to add an alarm extension (OutOfRangeAlarmExt) and history extension (NumericInterval).
And object (Logic folder)

Inputs are linked to multiple proxy BooleanPoints, each representing “fan status” (Off or On). The And object is linked to downstream control logic. To track when all fans are running, you may wish to a history extension (BooleanChangeOfValue) and perhaps a control extension to collect runtime (DiscreteTotalizerExt).
NumericSwitch object (Util folder)

Inputs are linked to two proxy NumericWritables, each representing a power rate (kW). The object output is linked to downstream control logic (and represents the current “switched” rate). To totalize this effective rate into energy accumulation, you add a control extension (NumericTotalizerExt) and add proper scaling to collect kWh.