Changing Alarm Limits via Automation Interface

[sbeadle1]

📖 Home  Back  
When using the automation interface to modify the alarm limits of an analog point, it is important to understand the peoprties which are available and when they should be used.

For drivers where alarm limit tuning can be applied, there are multiple sets of properties for the alarm limits depending on whether tuning has been enabled for that point.

Using the automation interface the analogue High High alarm limits cannot be changed, only the full scale limits. The property HighHighLimit is read only.

There are either three or four properties for each alarm limit except FullScale and ZeroScale. This is because all the limits except for Zero Scale and Full Scale, can be 'tuned' (if tuning is enabled) and can have both a standard and alternate limit (if multiple alarm limits is enabled, otherwise just standard).

These properties are used to store the Tuned Limit (e.g. HighHighLimitTuned), the current limit (e.g. HighHighLimit) and if multiple limits are disabled the default limit set in the point properties form (e.g. HighHighLimitStd), or if multiple limits are enabled the standard and alternate limits set in the point properties form (e.g. HighHighLimitStd and HighHighLimitAlt). Note. 'Std' and 'Alt' are usually renamed to something more descriptive when multiple limits are enabled, e.g. 'Summer' and 'Winter'.

To change the alarm limits using the automation interface, the default limit(s) should be used ("HighHighLimitStd" (and "HighHighLimitAlt" if multiple alarms are enabled) for the High High alarm limit).

The Zero Scale and Full Scale limits cannot be tuned, and only have one property each: ZeroScale and FullScale. These properties can written to by the automation interface.

Go: Home Back