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

Subject: Re: Intended use of NTMultiChannel
From: Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>
To: "Paduan Donadio, Marcio" <marcio at slac.stanford.edu>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Thu, 17 Dec 2020 07:27:01 -0800
On 12/16/20 9:11 PM, Paduan Donadio, Marcio via Tech-talk wrote:
> I have a NTMultiChannel created using the C++ API.

Which c++ API specifically?

> I pvput to channelName passing a valid PV name. I placed a printf inside the process() method just to check if the record is processing and I can confirm it does.
> 
>  
> 
> When I pvget I expected to see the other fields of the record populated with values from the PV in channelName. Is it intended that inside process() I write the commands to bring the data for each channel and write to the fields of the NTMultiChannel? Is there a default “record support” that has it already implemented and I can use?

If you are referring to pvDatabaseCPP, then probably not.  It is more analogous to PCAS.

You might look at the PVA link support as a way of having an IOC act as a PVA client.

https://epics-base.github.io/pva2pva/qsrv_page.html#qsrv_link


> Some data:
> 
>  
> 
> Epics base 7.0.3
> 
>  
> 
> $ pvget GMDTest:NTScalar
> 
> GMDTest:NTScalar 0
> 
>  
> 
> $ pvput GMDTest:NTMultiChannel 'channelName=["GMDTest:NTScalar"]'
> 
> Old : epics:nt/NTMultiChannel:1.0
> 
>     any[] value
> 
>     string[] channelName []
> 
>     int[] severity []
> 
>     int[] status []
> 
>     string[] message []
> 
>     boolean[] isConnected []
> 
> New : epics:nt/NTMultiChannel:1.0
> 
>     any[] value
> 
>     string[] channelName ["GMDTest:NTScalar"]
> 
>     int[] severity []
> 
>     int[] status []
> 
>     string[] message []
> 
>     boolean[] isConnected []
> 
>  
> 
> $ pvget GMDTest:NTMultiChannel
> 
> GMDTest:NTMultiChannel epics:nt/NTMultiChannel:1.0
> 
>     any[] value
> 
>     string[] channelName ["GMDTest:NTScalar"]
> 
>     int[] severity []
> 
>     int[] status []
> 
>     string[] message []
> 
>     boolean[] isConnected []
> 


Replies:
Re: Intended use of NTMultiChannel Paduan Donadio, Marcio via Tech-talk
References:
Intended use of NTMultiChannel Paduan Donadio, Marcio via Tech-talk

Navigate by Date:
Prev: synApps_6_1 build error on windows-x64 with EPICS 7 Markus Huber via Tech-talk
Next: Re: synApps_6_1 build error on windows-x64 with EPICS 7 Johnson, Andrew N. 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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Intended use of NTMultiChannel Paduan Donadio, Marcio via Tech-talk
Next: Re: Intended use of NTMultiChannel Paduan Donadio, Marcio 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  <20202021  2022  2023  2024 
ANJ, 17 Dec 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·