Experimental Physics and
Industrial Control System

Meeus Kris via Tech-talk <tech-talk at aps.anl.gov> · Fri, 13 Aug 2021 13:49:28 +0000

Dear techtalk community

I'm fairly new to EPICS and currently exploring an IOC running on a mTCA CPU board, where a have issues with CA and PVA.

The mTCA CPU has a fresh installed CentOS8, no specific configuration done except from installing epics-base and our applications binaries / libraries and add their location to PATH and LD_LIBRARY_PATH variables.
We have an example IOC application which we use, based on PVA. This works fine on our development system (wsl with CentOS8).
Alternatively, I also used a CA softIoc and PVA softIocPVA with the same result.

Here is my setup:
	- On the mTCA CPU board a terminal is opened and the application is started.
	The application runs fine.
	- On the mTCA CPU board open a second terminal and try to consult with pvinfo or pvget.
	The PVA requests always times out

After some readings on internet/communities, I can get it working by setting environment variables on server and client side (with IP address = mTCA IP address).
Server side:
export EPICS_PVAS_ADDR_LIST="192.168.0.101"
export EPICS_PVAS_INTF_ADDR_LIST="192.168.0.101"
export EPICS_PVAS_BEACON_ADDR_LIST="192.168.0.101"
export EPICS_PVA_AUTO_ADDR_LIST=NO

Client side
export EPICS_PVA_ADDR_LIST="192.168.0.101"
export EPICS_PVAS_AUTO_ADDR_LIST=NO

With these settings, I'm able to access the PVA's of the IOC application.
However, setting these environment variables shouldn't be required (and I never did before e.g. in wsl) since this is all localhost access.

Does anyone have an idea what could be wrong (and gets patched by setting the variables) and how to solve this?

Thanks in advance for your feedback !

Kind regards,
Kris Meeus 
-
Belgian Nuclear Research Centre
www.sckcen.be

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System