EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20192020  2021  2022  2023  2024  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  <20192020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Camonitor with client dictated update rate
From: Hinko Kocevar via Tech-talk <[email protected]>
To: "[email protected]" <[email protected]>
Cc: Emanuele Laface <[email protected]>
Date: Sun, 2 Jun 2019 17:53:39 +0000
Thank you all for the input.

I understand that adding new records to the IOC database is the "EPICS" way of doing it, and I've done it so far for IOCs under my control, with success. The thing is that there are not enough bodies, with EPICS knowledge and free time, for this to happen on all IOCs at ESS, leading such low priority requirements being forgotten.

I've never used the base filters before - this looks like a good opportunity to look into that!
The PVs that need throttling are mainly scalars, but in some cases, even more critical PVs as waveforms. I would imagine that "deadband" filter might not play well with those. In any case, deadband filter looks promising, but at the end of the day, I'm after simple decimation of PV update rate, not depending on the value change itself.
(How) can filters be used with python client (pyepics3)?

The periodic polling, sounds like to most straightforward approach, for sure.
In python, there might be unwanted delays introduced to the "caget" if the PV is not accessible/reachable at the time of the poll. And then the rest of the PV updates (in a single thread) suffer from not being updated in timely fashion. Someone will say, use threads; but I can have +50 PVs to look at on this slow monitoring client hence each PV would need to get its own thread? Or would the use of PV instead of caget in pyepics3 lead to better experience?

Thanks,
Hinko
________________________________________
From: William Layne <[email protected]>
Sent: Thursday, May 30, 2019 7:19:24 PM
To: Hinko Kocevar
Cc: [email protected]; Emanuele Laface
Subject: Re: Camonitor with client dictated update rate

Oops forgot to CC tech-talk

--------- Forwarded message ---------
From: William Layne <[email protected]<mailto:[email protected]>>
Date: Wed, May 29, 2019, 5:08 PM
Subject: Re: Camonitor with client dictated update rate
To: Hinko Kocevar <[email protected]<mailto:[email protected]>>


You could create a record, with a 1hz scan rate, that has the input field linked to the desired PV. Then have your user monitor the subsampled PV.

On Wed, May 29, 2019, 1:21 PM Hinko Kocevar via Tech-talk <[email protected]<mailto:[email protected]>> wrote:
This might sound like a silly motion, but you are probably used to those from me by now.

A non-EPICS person at my facility wonders if EPICS could support camonitor like PV monitoring, but with CA client dictating the rate of value updates. Imagine 1s update rate, that certain slow client would use, while the PV would update much faster, and the rest of existing CA clients just use regular camonitor’ing.

I can see answers like, just use caget like approach and poll or define a new (set) of PVs for that slow rate, but that is IOC material. My use case revolves around very, very busy IOC devs that have no time to support crazy ideas of individuals who want slow updates.

Any insights appreciated!

Thanks (and have a nice weekend to those living in Sweden),
Hinko

On Wed, May 29, 2019, 1:21 PM Hinko Kocevar via Tech-talk <[email protected]<mailto:[email protected]>> wrote:
This might sound like a silly motion, but you are probably used to those from me by now.

A non-EPICS person at my facility wonders if EPICS could support camonitor like PV monitoring, but with CA client dictating the rate of value updates. Imagine 1s update rate, that certain slow client would use, while the PV would update much faster, and the rest of existing CA clients just use regular camonitor’ing.

I can see answers like, just use caget like approach and poll or define a new (set) of PVs for that slow rate, but that is IOC material. My use case revolves around very, very busy IOC devs that have no time to support crazy ideas of individuals who want slow updates.

Any insights appreciated!

Thanks (and have a nice weekend to those living in Sweden),
Hinko

Replies:
Re: Camonitor with client dictated update rate Matt Newville via Tech-talk
References:
Camonitor with client dictated update rate Hinko Kocevar via Tech-talk
Re: Camonitor with client dictated update rate William Layne via Tech-talk

Navigate by Date:
Prev: Re: Receiving duplicate monitor values using CA PV Gateway William Layne via Tech-talk
Next: Re: Camonitor with client dictated update rate Matt Newville via Tech-talk
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  <20192020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Camonitor with client dictated update rate William Layne via Tech-talk
Next: Re: Camonitor with client dictated update rate Matt Newville via Tech-talk
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  <20192020  2021  2022  2023  2024 
ANJ, 02 Jun 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·