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: processing pva records
From: Michael Davidsaver via Tech-talk <[email protected]>
To: Pierrick M Hanlet <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Thu, 19 Dec 2019 12:21:21 -0800
Hi Pierrick,

You question contain a lot of unfamiliar jargon.  "aSub" is reasonably
clear to me, but "v7Struct" could be referring to several possible
C++ classes.  It would be clearer if you could use literal C/C++
type names (eg. 'aSubRecord' or 'PVStructure').

Also, FYI.

http://epics-base.github.io/pvDataCPP/

http://epics-base.github.io/pvAccessCPP/

Specifically, I recommend looking at pvac::ClientProvider instead of PvaClient
and pvas::SharedPV instead of PVDatabase.

Example can be found in: https://github.com/epics-base/pvAccessCPP/tree/master/examples


On 12/18/19 1:51 PM, Pierrick M Hanlet via Tech-talk wrote:
> Hi all,
> I am developing a module for use at Fermilab which allows an easy interface
> from EPICS IOCs to our native control system.  I want to use aSub records
> so that I have the flat db files which can be populated with macros.  
> Within
> my module I've created a structure, v7Struct which carries all of the 
> pertinent
> information; e.g. Reading and Setting.  At initialization, I instantiate 
> as many
> of these objects (v7Structs) as I need.
> 
> So, to read from my v3 PVs, I do:
> v3PV -> aSub(Reading) -> v7Struct -> operator (via native system)
> 
> This works well.  Where I'm having difficulty is the other way around:
> operator -> v7Struct ->(?) aSub(Setting) -> v3PV
> 
> In other words, I don't know how to get my v7Struct to process my 
> aSub(Setting).
> I've been going through exampleCPP, which is a very helpful work, but thin
> on documentation.  Do I need to set up a PvaClient and set up monitor and
> then a link, or is there someway to do this directly from PVData or 
> PVDatabase?
> Thank you,
> Pierrick
> 


References:
processing pva records Pierrick M Hanlet via Tech-talk

Navigate by Date:
Prev: Re: stream output not as I thoutght Christoph Schroeder via Tech-talk
Next: caQtDM Mezger Anton Christian (PSI) 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: processing pva records Pierrick M Hanlet via Tech-talk
Next: ci-scripts 2.0.1 maintenance release Ralph Lange 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, 20 Dec 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·