EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: pvaSrv "can not monitor a link field"
From: Michael Davidsaver <[email protected]>
To: Ralph Lange <[email protected]>, "Kasemir, Kay" <[email protected]>
Cc: EPICS Core Talk <[email protected]>
Date: Mon, 22 May 2017 10:58:55 -0400
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 <[email protected]
> <mailto:[email protected]>> 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" Kasemir, Kay
Re: pvaSrv "can not monitor a link field" Kasemir, Kay
References:
pvaSrv "can not monitor a link field" Kasemir, Kay
Re: pvaSrv "can not monitor a link field" Ralph Lange

Navigate by Date:
Prev: Re: pvaSrv "can not monitor a link field" Ralph Lange
Next: Re: pvaSrv "can not monitor a link field" Kasemir, Kay
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: pvaSrv "can not monitor a link field" Ralph Lange
Next: Re: pvaSrv "can not monitor a link field" Kasemir, Kay
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
ANJ, 21 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·