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  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 
<== Date ==> <== Thread ==>

Subject: Re: Basic PVAccess question
From: Marty Kraimer via Tech-talk <tech-talk@aps.anl.gov>
To: tech-talk@aps.anl.gov, Michael Davidsaver <mdavidsaver@gmail.com>
Date: Fri, 1 Mar 2019 06:44:50 -0500
On 2/27/19 6:27 AM, will.rogers--- via Tech-talk wrote:
I am looking at the exampleCPP repo for EPICS7.


When I run helloRPC I can use pvcall and p4p as a client successfully.


When I run pvDatabaseRPC, I can't use either, and I get the following message:

ChannelRPC not supported


HelloClient.cpp (helloRPC) and positionClient.cpp (pvDatabaseRPC) both use an RPCClient to communicate the server.


I think I don't understand fully. Can anyone clear this up for me?


Cheers,

Will



Will and I had some private messages and now I think I can give an explanation of what we found. pvcall appears to assume that both the client and server use normative type nturi.
https://github.com/epics-base/normativeTypesCPP/blob/master/src/pv/nturi.h

But neither exampleCPP/helloRPC or exampleCPP/pvDatabaseRPC use nturi.


Will did get helloRPC to work by making the following change to HelloService.cpp

-    epics::pvData::PVStringPtr nameField = pvArgument->getSubField<PVString>("personsname");
+    std::cout << "Argument " << pvArgument << "\n";
+    epics::pvData::PVStructurePtr queryField = pvArgument->getSubField<PVStructure>("query");
+    epics::pvData::PVStringPtr nameField = queryField->getSubField<PVString>("personsname");


Now I have some questions about pvcall and channelRPC.
Is pvcall meant to replace eget?
Are there plans for future enhancements to channelRPC?
If yes then what is the status?


Marty Kraimer



Replies:
Re: Basic PVAccess question Michael Davidsaver via Tech-talk
References:
Basic PVAccess question will.rogers--- via Tech-talk

Navigate by Date:
Prev: Re: timeStamp in pvget request not populated when using display field in v3 IOC Jack Harper - UKRI STFC via Tech-talk
Next: Re: Fw: asynDriver - update record (timestamp), on no change Rod Nussbaumer 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 
Navigate by Thread:
Prev: Re: Basic PVAccess question Marty Kraimer via Tech-talk
Next: Re: Basic PVAccess question Michael Davidsaver 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 
ANJ, 04 Mar 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·