2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | pvaSrv "can not monitor a link field" |
From: | "Kasemir, Kay" <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Mon, 22 May 2017 14:29:03 +0000 |
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
-> 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)
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
|