Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: Re: pvaSrv "can not monitor a link field"
From: "Kasemir, Kay" <kasemirk@ornl.gov>
To: EPICS Core Talk <core-talk@aps.anl.gov>
Date: Mon, 22 May 2017 20:13:56 +0000
Hi:

I followed Michael's instructions from https://github.com/mdavidsaver/v4workspace/tree/pva2pva .
Builds OK, just had to manually edit the RELEASE.local.in into a RELEASE.local, not sure if there's an automake way to handle that.
Also couldn't find "qsrv" as such, but in the end the pva2pva/bin/linux-x86_64/softIocPVA contains a PVA server, there's no need to add anything to the st.cmd.

With that, I can monitor link fields.
Also, not having to add anything to the st.cmd file to get the PVA server started is nice.
So this limited test suggests replacing pvaSrv with qsrv.

Thanks,
Kay


________________________________________
From: Michael Davidsaver <mdavidsaver@gmail.com>
Sent: Monday, May 22, 2017 10:58 AM
To: Ralph Lange; Kasemir, Kay
Cc: EPICS Core Talk
Subject: Re: pvaSrv "can not monitor a link field"

On 05/22/2017 10:48 AM, Ralph Lange wrote:
> Depending on what the release plans for QSRV are (@Michael?),
> You actually might want to add this as an issue to pvaSrv.

I was just about to ask Kay if he would be willing to test QSRV,


> Thanks a lot,
> ~Ralph
>
> ps. We need more unit tests.
>
>
>
> On Mon, May 22, 2017 at 11:29 PM, Kasemir, Kay <kasemirk@ornl.gov
> <mailto:kasemirk@ornl.gov>> wrote:
>
>     Hi:
>
>
>     This came up during the V4 introduction at the recent EPICS meeting.
>
>     I first thought it's a bug in CS-Studio, but instead it's a
>     limitation in pvaSrv.
>
>
>     Assume an IOC with pvaSrv added to it, take any calc or ai record:
>
>
>     pvget that_record
>
>     -> fine
>
>
>     pvget that_record.INP (or INPA for a calc record)
>
>     -> fine
>
>
>     pvget -m that_record
>
>     -> fine
>
>
>     pvget -m that_record.INP (or INPA for a calc record)
>
>     -> Don't get a value, instead message(can not monitor a link field,
>     error)
>     monitorConnect(Status [type=ERROR, message=create dbPvMonitor failed])
>
>
>     Checking the 4.6.0 release of V4, pvaSrv/src/dbPv/[3.14,
>     3.15]/dbPvMonitor.cpp both check for link fields and refuse to
>     monitor them with this error message.
>
>
>     Fundamentally, 'camonitor' can monitor link fields, and there are
>     some use cases for doing this:
>
>     Displays (EDM, CSS, ..) sometimes need to put 'INP' links on the
>     display so that users can change the input.
>
>     The CSS EPCIS PV Tree tool monitors input links to show the link
>     hierarchy.
>
>
>
>     Is monitoring link fields supported in QSRV?
>
>
>     Thanks,
>
>     Kay
>
>
>
>
>



Replies:
Re: pvaSrv "can not monitor a link field" Michael Davidsaver
References:
pvaSrv "can not monitor a link field" Kasemir, Kay
Re: pvaSrv "can not monitor a link field" Ralph Lange
Re: pvaSrv "can not monitor a link field" Michael Davidsaver

Navigate by Date:
Prev: Re: pvaSrv "can not monitor a link field" Kasemir, Kay
Next: Re: pvaSrv "can not monitor a link field" Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: Re: pvaSrv "can not monitor a link field" Kasemir, Kay
Next: Re: pvaSrv "can not monitor a link field" Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 22 May 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·