EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: alarm/severity
From: Kay-Uwe Kasemir <[email protected]>
To: [email protected]
Date: Thu, 20 Oct 2005 14:06:16 -0400

On Oct 20, 2005, at 11:52 , Ralph Lange wrote:
The current plan (afaik) is to allow even more user-defined "triggers". Or "filters". Or "events". (Everyone of us has different interpretations of those terms...)

Your last mentioned subscription won't be enough, as e.g. the Alarm Hander is also interested in the value, but only wants updates when the severity changes.

The trigger/events and channels/fields/views aspects of a connection are orthogonal.
Hi Ralph:

Thanks, the example ("use case") of an alarm tool
wanting to subscribe to value & status, but only
needing updates on status change answers my question.

Yes, we wanted more triggers and filters.
And we're starting over at the level of use case collection
to determine which ones are actually needed.

From the 'office' side, support for the V3 and TANGO events
is a requirement, because the control system API used
by the office applications needs to support those as well.
As far as I can tell, that means:

* update on change in value
 with relative and absolute deadbands,
 each as a positive and negative limit.
 E.g. update when value increases by >= 1% or descreases by <=0.5%.
 EPICS V3 only has a single absolute deadband.

* update on change of 'quality'
 Is that like the V3 'alarm'?

* periodic updates with specified period.
 EPICS V3 doesn't have that on a per-user basis.

* update on archive related changes
 which are designated relative and absolute deadbands,
 again pos. & neg.,
 and in addition a minimum update rate.
 EPICS V3 only ADEL, no additional periodic update.

* 'event' would be another trigger, which Tango doesn't have,
 but V3 already supports as single, numeric events from
 post_event as well as device-supported interrupts.

Filters need to be added to all of these.
A machine-mode masks,
where e.g. 1b'0000001 means 'long pulse',
           1b'0000010 means 'to target A',
allows simple and/or masks to filter only on
long pulses to target A.
The use cases will decide what more we need.

Thanks,
-Kay

Replies:
Re: alarm/severity Benjamin Franksen
Re: alarm/severity Andrew Johnson
References:
alarm/severity Kay-Uwe Kasemir
Re: alarm/severity Ralph Lange

Navigate by Date:
Prev: Re: Link arrays / syntax Andrew Johnson
Next: Re: alarm/severity Benjamin Franksen
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: alarm/severity Ralph Lange
Next: Re: alarm/severity Benjamin Franksen
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·