AW: pvget, pvxget and pvxs interoperability and differences

["Gotz, Malte via Tech-talk" <tech-talk at aps.anl.gov>]

Hello Michael,

 

thank you for your quick reply. I totally understand that pv… and pvx… are not fully compatible and you do give ample warning, that the command line tools from pvxs are rather for testing. I mostly remarked on the discrepancies, because I also couldn’t find a definitive documentation on how to use that feature. Now, I know, this wasn’t just a failure of my search skills.
As far as I understand it this explains the differences in some -r arguments working for pvxget but not for pvget and vice versa.

 

The more pressing issue for me is, that if I create an NT/Table group with QSRV2, I can’t retrieve a single column using pvget with any syntax. My understanding is that the client tool (pvget) should parse the string into some structure and send that via PVA to retrieve/request the data. The QSRV2 on the other hand doesn’t need to parse the string I give with pvget -r, right?

So, any idea what is going on here?

Von: Michael Davidsaver <mdavidsaver at gmail.com>
Gesendet: Mittwoch, 11. März 2026 21:48
An: Gotz, Malte <malte.gotz at helmholtz-berlin.de>
Cc: tech-talk at aps.anl.gov
Betreff: Re: pvget, pvxget and pvxs interoperability and differences

 

On 3/11/26 7:53 AM, Michael Davidsaver wrote:

PRs and issues open.

I have created an additional issue specifically about pvRequest syntax interoperability

https://github.com/epics-base/pvxs/issues/156

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature