Re: EPICS alarming on VAL != X

[Jameson Graef Rollins <jrollins@ligo.caltech.edu>]

On Mon, Jul 21 2014, Benjamin Franksen <benjamin.franksen@helmholtz-berlin.de> wrote:
> Why don't you just set DRVL=DRVH=<the desired value>. In that case the 
> record simply can't take on any other value. No need to even think about 
> alarms for situations that can never arise...

Hi, Ben.  For the moment we want to be able to easily change the
parameters if needed; we just also want a good way to track any changes.
The alarm system would be a good way to do that, if we could alarm on
records not being at a particular set point.

We have also looked at "locking" the parameters to their set point
values by using the access security framework, but we're hoping to avoid
that level of restriction for the time being.  Access security would I
think be preferable to something like DRVL=DRVH=VAL, since it would
provide feedback to our MEDM operators that the parameters are
purposely locked in place.

Thanks for the suggestions, though.  Others are welcome!

jamie.

Attachment: pgpqJ3NdTwGKV.pgp
Description: PGP signature