Re: Equivalent of EPICS_CA_NAME_SERVERS for PV Access?

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

EPICS_PVA_NAME_SERVERS works with PVXS (pvxget, pvxmonitor, ..) and the gateway based on PVXS: https://github.com/mdavidsaver/pvxs/, https://mdavidsaver.github.io/p4p/gw.html

It also works with the new Java PVA client (CS-Studio phoebus, https://github.com/ControlSystemStudio/phoebus/ can also used from matlab, https://github.com/ControlSystemStudio/phoebus/tree/master/core/pva).

It has not been ported to the older C++ and Java code, so the EPICS IOCs, Area Detector PVA plugins, ImageJ etc. won't support it.

The primary reason for using EPICS_PVA_NAME_SERVERS might however be the gateway, since it's easier to reach TCP via firewalls etc., so you can use the new gateway for that and the IOCs behind the gateway won't know anything about it.

For a client to the gateway you'll have to use CS-Studio or something else that uses the new C++ or Java client libs.

-Kay

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Gibbs, Matt via Tech-talk <tech-talk at aps.anl.gov>
Sent: Friday, July 15, 2022 2:10 PM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: [EXTERNAL] Equivalent of EPICS_CA_NAME_SERVERS for PV Access?

 

Hi all,

I often use the EPICS_CA_NAME_SERVERS environment variable to tell my CA client to do PV discovery on one specific hostname (usually a CA gateway server).

I’d like to be able to do the same thing for PV Access as well.  I’ve tried the naive approach of just setting “EPICS_PVA_NAME_SERVERS”, but that doesn’t seem to work.  Is there some other way to do the same thing?

Thanks,
—Matt