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

Subject: Re: Channelfinder Recsync Client: Limit records client side
From: "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>
To: Tynan Ford <TFord at lbl.gov>, "Kenner, Daniel Craig" <kenner2 at llnl.gov>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Thu, 9 May 2024 23:07:09 +0000

We don't use reccaster in in the upgraded APS, but we have adopted the naming convention (from Python?) that record names which end in an underscore '_' are intended for internal use within the control system only, and shouldn't be used on any published display screens or by other clients. We haven't gone so far as to remove them from the lists of PV names that our name-servers recognize (which would limit access to other IOCs or clients running in the same subnet), but that would be our equivalent to what Daniel is asking for.

 

I would think it should be relatively easy to filter out matching names like that inside the reccaster code, whereas searching for an info tag in each record would probably slow up the reccaster somewhat at start-up. The use of a naming convention also makes it easier to see when someone is using a PV name that they aren't supposed to be connecting to.

 

- Andrew

 

-- 

Complexity comes for free, Simplicity you have to work for.

 

 

On 5/9/24, 5:25 PM, "Tech-talk" <tech-talk-bounces at aps.anl.gov> wrote:

 

Hi Daniel,

 

I am not aware of any field like that but it does sound like an interesting idea. Another place you could filter PVs before they reach channel finder is on the recceiver side, in the cfstore plugin.

 

Best,

Tynan

 

On Wed, May 8, 2024 at 6:32PM Kenner, Daniel Craig via Tech-talk <tech-talk at aps.anl.gov> wrote:

Hello all,

 

I have been working with LLNL on an EPICs application. The Channelfinder has critical functionality we would like to take advantage of, but one of the hurdles is limiting what records are allowed to be published through the reccaster module. I don’t want the end user to have visibility into every single record an IOC has, but I am unclear if the support module offers this functionality. Is there some field I can add to relevant records so that reccaster only publishes those PV’s?

 

Thank you for your time,

Daniel Kenner

Computer Engineer

Lawrence Livermore National Laboratory

Phone: (925) 758-2607

Email: kenner2 at llnl.gov

 


References:
Channelfinder Recsync Client: Limit records client side Kenner, Daniel Craig via Tech-talk
Re: Channelfinder Recsync Client: Limit records client side Tynan Ford via Tech-talk

Navigate by Date:
Prev: RE: Channelfinder Recsync Client: Limit records client side Kenner, Daniel Craig via Tech-talk
Next: RE: About the timestamp in py-epicsarchiver lib? Zhang, Tong 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  2019  2020  2021  2022  2023  <2024
Navigate by Thread:
Prev: RE: Channelfinder Recsync Client: Limit records client side Kenner, Daniel Craig via Tech-talk
Next: Limitations of some EPICS base's records Abdalla Ahmad 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  2019  2020  2021  2022  2023  <2024
ANJ, 10 May 2024 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·