Re: [EXTERNAL] Disable alarm at IOC via PVAccess

[Maren Purves via Tech-talk <tech-talk@aps.anl.gov>]

Actually, if the prior alarm values are in the database (or the
startup file) you only have to set those back to what you know. We
sometimes have instruments that run a bit warmer than their default
(for whatever reasons) and you can set higher alarm thresholds from
the command line, or if you don't have direct access with cau or
probe. I wouldn't normally put them into the user interface in a
writable way though.

Maren (now more or less retired from the EAO)

On Fri, Nov 21, 2025 at 6:00 AM Hartman, Steven via Tech-talk
<tech-talk@aps.anl.gov> wrote:
>
>
> To re-enable alarms, you would have needed to have remembered the prior value to restore it
>
>
>
>  . . . which would not be very practical. A more manageable approach would be to add some database logic on top to handle bypassing alarms instead. For example, a calc record and’ing the I/O record’s state with an alarm enable bo record, and using that result in your alarm handler rather than the I/O record itself. You can build on this to handle cases where you only want certain alarms in certain machine configurations, or where some equipment may be offline on purpose, and it also allows you to combine multiple inputs into a summary status alarm.
>
> --
> Steven Hartman
> hartmansm@ornl.gov
>