Subject: |
alarm handler question: group FORCEPVs and severities at alh startup |
From: |
"Rock, Judith E." <[email protected]> |
To: |
<[email protected]> |
Date: |
Wed, 14 Feb 2007 17:30:35 -0800 |
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
- Replies:
- Re: alarm handler question: group FORCEPVs and severities at alh startup Brian Bevins
- Navigate by Date:
- Prev:
Re: evaluation of OMG DDS as a controls protocol for EPICS Lawrence T. Hoff
- Next:
Re: "Heartbeat" databases or sequences? Kay-Uwe Kasemir
- 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: evaluation of OMG DDS as a controls protocol for EPICS Lawrence T. Hoff
- Next:
Re: alarm handler question: group FORCEPVs and severities at alh startup Brian Bevins
- 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
|