I created a panel of switches (displayed as checkboxes) to disable the hi/lo alarm
settings. I could have used a symbolicLink to avoid creating so many switch
objects, but I like the visual panel --- easy to see what is currently disabled.
When a sensor gets into an oscillation around the alarm setting, the operator can
open the Override panel and disable that specific alarm. For example, my alarm
objects have this form:
Name:Alarm_heliumbottle Alarm area:Ops
Message="OUT OF TOLERANCE Helium Bottle Pressure: "&
..\heliumbottle&" psia"
Signal=..\heliumbottle
Lo Level=if(Switch_heliumbottle_lo,0,500)
Lo-Lo Level=200
If the switch is on, then the lo level is set to 0 psia, below the Lo-Lo level of
that sensor. For my app, I don't want the operator's
to override the Hi-Hi and
Lo-Lo alarms, but the same logic could be applied to them.
I also added a Reset Button to my panel and linked it to the panel's $Alarm (to its
connection Ops.ack). That way all the Ops alarms can be silenced with a single
click.
Andrew Graham wrote:
> We have had several ocasions where a faulty sensor has generated so many alarms
> that is swamps the rest of the alarms. Short of editing the lookout files
> is there any way to filter out these alarms until the sensor is fixed ? Normaly
> the users have to resort to shorting out the alarm signal physicaly when
> this happens.
