EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  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  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Alarm trigger for persistent values?
From: Ralph Lange <[email protected]>
To: Bernhard Lopez <[email protected]>
Cc: [email protected]
Date: Thu, 21 Sep 2006 16:18:04 +0200
Hello Bernhard,

If you use the Alarm Handler (ALH) to display your alarms, there is a configuration option that allows you to have an alarm appear only after it occurred for a certain number of times or persisted for a certain time.
Look for chapter 6.3.12 or "Alarm Count Filter" in the Alarm Handler User's Guide.


If you want to solve this within the database, use Pete's approach, but rather use a calcout record and use the OCAL field (or a second calc record) to write the RAWTEMP value to the final ai, else you will end up showing the counter instead of the temperature.
I would separate the time counting from forwarding the value, which also doesn't link the update period of your final TEMPERATURE ai to the time counter resolution. So I would do something like


record (ai, "RAWTEMP")
{
	...
	field (SCAN, "I/O Intr")
	field (FLNK, "CALCFORWARD")
}

record (calc, "CALCFORWARD")
{
	field (CALC, "A")
	field (INPA, "RAWTEMP NPP MS")
	field (INPB, "CALCULATION NPP MS")
	field (FLNK, "TEMPERATURE")
}

record (calc, "CALCULATION")
{
	field (SCAN, "1 second")
	field (CALC, "(B>C||B<D)?(A+1):0")
	field (INPA, "CALCULATION.VAL")
	field (INPB, "RAWTEMP")
	field (INPC, "RAWTEMP.HIHI")
	field (INPD, "RAWTEMP.LOLO")
	field (HIHI, "60")
	field (HHSV, "MAJOR")
	field (FLNK, "CALCFORWARD")
}

record (ai, "TEMPERATURE")
{
	field (INP, "CALCFORWARD NPP MS")
}

(Code is not tested and may contain more bugs ...)

Hope this helps,
Ralph


Bernhard Lopez wrote:
Hi,

At our infrastructure monitoring system we have the case that
some temperature values should trigger an alarm only if they
remain above/below a threshold (HIHI/LOLO) for longer than a
defined amount of time.

As we could not find support for this feature in the documentation,
we would be glad to receive a suggestion regarding a solution or
implementation we could go for.

The involved sensor devices are represented by "ai" records
with a home-made device implementation. We use EPICS release
3.14 on Linux.

Many thanks in advance!

Bernhard.



References:
Alarm trigger for persistent values? Bernhard Lopez

Navigate by Date:
Prev: RE: Alarm trigger for persistent values? Owens, PH (Peter)
Next: CLOUDSPAPS: Look in the mirror and enjoy the new you Tabatha Huynh
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Alarm trigger for persistent values? Owens, PH (Peter)
Next: CLOUDSPAPS: Look in the mirror and enjoy the new you Tabatha Huynh
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·