Hi Keith,
On 2011-07-18 [email protected] wrote:
>
> My requirement is to only register an alarm if the value exceeds the
> threshold persistently for 120 seconds.
...
> The other behaviour I've noticed is that once in alarm, the same criteria
> is used to decide when to drop down to no alarm. i.e. if the PV value
> drops below the threshold then it takes inputSeconds before this is
> recognised, or inputCount drops within inputSeconds. I am just curious as
> to whether this is behaviour that anybody wants or uses? I'd prefer to
> drop out of the alarm state immediately.
It's likely that the behaviour implemented was required by someone at APS when
we wrote ALH, I see it being used fairly heavily in our operational alhConfig
files.
I would suggest that your alarm filter should probably be implemented inside
the IOC, rather than rely on ALH to do it. It's much easier to customize
there anyway.
- Andrew
--
Optimization is the process of taking something that works and
replacing it with something that almost works, but costs less.
-- Roger Needham
- Replies:
- RE: Alarm Handler and $ALARMCOUNTFILTER keith.baker
- References:
- Alarm Handler and $ALARMCOUNTFILTER keith.baker
- Navigate by Date:
- Prev:
Re: EPICS OSI and events Andrew Johnson
- Next:
RE: Delay problem in ca_array_put() command Jeff Hill
- 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:
Alarm Handler and $ALARMCOUNTFILTER keith.baker
- Next:
RE: Alarm Handler and $ALARMCOUNTFILTER keith.baker
- 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
|