Experimental Physics and
Industrial Control System

On Mon, Jul 21 2014, Benjamin Franksen <[email protected]> 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

Replies:

Re: EPICS alarming on VAL != X Maren Purves

Re: EPICS alarming on VAL != X J. Lewis Muir

References:

EPICS alarming on VAL != X Jameson Graef Rollins

Re: EPICS alarming on VAL != X Johnson, Andrew N.

Re: EPICS alarming on VAL != X Jameson Graef Rollins

Re: EPICS alarming on VAL != X Benjamin Franksen

Navigate by Date:

Prev: RE: EPICS on VxWorks6.9 Mark Rivers

Next: Formatting StreamDevice input Elmer Pensack

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <2014>  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: EPICS alarming on VAL != X Benjamin Franksen

Next: Re: EPICS alarming on VAL != X Maren Purves

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <2014>  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024