EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: alarm handler question: group FORCEPVs and severities at alh startup
From: Brian Bevins <[email protected]>
To: "Rock, Judith E." <[email protected]>
Cc: [email protected]
Date: Tue, 20 Feb 2007 09:38:06 -0500
Rock, Judith E. wrote:
Hi -
We're setting up an alarm handler tree, and plan to use the FORCEPV feature for temporarily disabling alarming for branches of the tree. All is working wonderfully.
Except...when I start a new alarm handler display while a group FORCEPV has been previously set to forceValue (i.e. group disabled). The group mask of the disabled group is set to the proper force mask at startup, but its alarm severity on the display and the alarm severities of the parent groups still show an alarm state. The only way the group severity gets set properly is to change its FORCEPV to resetValue, and then back to forceValue. I.e., the FORCEPV for a group is only picked up upon transition from resetValue to forceValue while alh is running, not at alh startup.


Is there a way to trigger the proper group alarm severities at startup?

I did notice that the force severity at startup works properly at the channel level.

Sorry if I've missed something really obvious!

thanks for your help,
Judy, et al at SLAC


Hi Judy,


We have run into the same problem. Our workaround has been to use the FORCEPV for each channel in the group instead of using it at the group level. This seems to work properly, though it is a bit of a pain. If the channels have their own FORCEPV's then you can use FORCEPV CALC's to get the same effect.

This is pretty easy for us to do since our alh files are generated semi-automatically by scripts. It would be more of a hassle for hand-edited alh files.

--
Brian S. Bevins, PE
Computer Scientist / Mechanical Engineer
Thomas Jefferson National Accelerator Facility

     "Progress, far from consisting in change,
      depends on retentiveness. Those who cannot
      remember the past are condemned to repeat it."
                                         -- George Santayana



References:
alarm handler question: group FORCEPVs and severities at alh startup Rock, Judith E.

Navigate by Date:
Prev: Re: evaluation of OMG DDS as a controls protocol for EPICS Lawrence T. Hoff
Next: Re: EPICS and HEPiX @ DESY - make your hostel reservations! Matthias Clausen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: alarm handler question: group FORCEPVs and severities at alh startup Rock, Judith E.
Next: time synchronization Geoff Savage
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·