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

Subject: Re: question about pvAccess monitor
From: Mark Rivers <[email protected]>
To: "Johnson, Andrew N." <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Sun, 1 Apr 2018 14:20:11 +0000
The EPICS areaDetector project has examples of:

pvAccess server,  NDPluginPva, written in C++. It is in the ADCore repository.

pvAccess client, pvaDriver, written in C++. It is in the pvaDriver repository.

pvAccess client, NTNDArray_Viewer, written in Java. It is in the ADViewers repository.

EPICS_NTNDA_Viewer and pvaDriver both work fine with NDPluginPva.

https://github.com/areaDetector.

Mark


Sent from my iPhone

> On Apr 1, 2018, at 5:44 AM, Johnson, Andrew N. <[email protected]> wrote:
> 
> Hi Renato,
> 
> Monitors for pvAccess were based on the ideas originally developed for Channel Access, although there has been a little parallel evolution that has yet to be recombined.
> 
> 1. A pvAccess channel name is the name of a top-level object, meaning that its value is usually going to be a structure with at least some and possibly many sub-fields. One function of the pvRequest object is to provide information about which subset of that top-level object you want to monitor. There are other uses for it, and if you are writing your own server code you can use it to pass additional information from the client at connection time. IIRC there is some documentation about it associated with the pvget command-line program.
> 
> 2. The two language implementations (C++ and Java) are supposed to be able to interoperate perfectly, so if you come across parts that don’t we want to know about them. There could be some features of individual servers that are only available on one side though, for example there is no Java equivalent of the IOC database.
> 
> HTH,
> 
> - Andrew
> 
> -- 
> Sent from my iPad
> 
>> On Apr 1, 2018, at 5:51 AM, renato sanhueza <[email protected]> wrote:
>> 
>> Hi EPICS community, I am trying to understand how the monitors of pvAccess work. I have a few quick questions, hopefully someone can help me :)
>> 
>> 1) What information does the monitor need about the monitored component to create the connection between them? I noticed in an example provided in Github that the monitor use a channelName (I assume that it is for the UDP broadcast name resolution mechanism) and a pvRequest string (which I don't understand)
>> 
>> 2) Can a C++/Java/Python component monitor another one regardless its implementation language?
>> 
>> 
>> Best regards,
>> Renato
>> -- 
>> Renato Sanhueza Ulsen
>> Ing Civil Informática.

Replies:
Re: question about pvAccess monitor Johnson, Andrew N.
References:
question about pvAccess monitor renato sanhueza
Re: question about pvAccess monitor Johnson, Andrew N.

Navigate by Date:
Prev: Re: question about pvAccess monitor Johnson, Andrew N.
Next: Re: question about pvAccess monitor Johnson, Andrew N.
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  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: question about pvAccess monitor Johnson, Andrew N.
Next: Re: question about pvAccess monitor Johnson, Andrew N.
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  <20182019  2020  2021  2022  2023  2024 
ANJ, 01 Apr 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·