Saturday, December 28, 2013

HMI update 12/28/2013

In the last HMI update for 2013, we realigned the alarm ‘blocking’ logic to maintain continuity between configuration settings and runtime actions.

The SetAlarmEnables function is still present but, will be removed in a future release. See SetAlarmBlocks.

Alarms are enabled / disabled, at runtime start, as determined by project configuration.

Alarm logic can be blocked / unblocked at runtime to temporarily disable and then enable the alarm logic processing for a point.

Alarm blocks are designed to be a temporary solution, when for example, a transmitter fails and the configured alarm needs to be 'blocked' so as not to provide false information.

The alarm configuration should be altered if the 'block' is used as a permanent or long term solution.

Also the SetAlarmSetpoints has a new flag to disable the alarm check when the function is called. This really should only be called with ‘false’ at runtime start, via the runtime start script, when the data from external devices has not yet been collected.

Happy New Year

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.