On 05/22/2017 04:13 PM, Kasemir, Kay wrote:
> 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.
Look for qsrvSupport.dbd. At the moment, the associated library is
libpdbcore.so, which as I look at it now is wrong. I'll be changing
this to libqsrv.so soon.
The softIocPVA executable is built from softIoc.dbd and qsrvSupport.dbd.
> 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 <[email protected]>
> 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 <[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
>>
>>
>>
>>
>>
>
>
- 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
- Re: pvaSrv "can not monitor a link field" Kasemir, Kay
- Navigate by Date:
- Prev:
Re: pvaSrv "can not monitor a link field" Kasemir, Kay
- Next:
Build failed in Jenkins: epics-base-3.16-linux32-test #77 APS Jenkins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: pvaSrv "can not monitor a link field" Kasemir, Kay
- Next:
Build failed in Jenkins: epics-base-3.16-linux32-test #77 APS Jenkins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|