Re: EPICS 7.0.4.1. Gettings Started under Windows 10 WSYS2 MinGW UCRT 64, Problem with camonitor

[Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>]

Trying to give a bit more details...

On Mon, 8 May 2023 at 21:21, Alexander Kessler via Tech-talk <tech-talk at aps.anl.gov> wrote:

I have compiled EPICS 7.0.4.1 following these instructions:

https://docs.epics-controls.org/projects/how-tos/en/latest/getting-started/installation-windows-msys2.html
under Windows 10 MSYS2 MinGW.

[...]

That all looks good.

 

[...]

My dev PC has two ethernet cards. The second one has multiple IP4 addresses for communication with lab network and local test equipment.

That's what is causing your issues.

By default, the CA client broadcasts the channel name resolution requests on all network interfaces found. If the IOC is hosted on a machine that is part of multiple of those networks, it will get multiple name requests and send back multiple answers, which the client detects and doesn't like.

The set of EPICS env. variables looks like this:

$ printenv | grep EPICS

EPICS_CA_ADDR_LIST=192.168.50.222:5065

EPICS_HOST_ARCH=windows-x64-mingw

EPICS_CA_AUTO_ADDR_LIST=NO

EPICS_BASE=C:\Users\AlexK\work\epics\base-R7.0.4.1

I think I am close to the target,

You are!

EPICS_CA_AUTO_ADDR_LIST=NO

That's correct and necessary. It stops the CA client from sending broadcasts on all found networks.

Next step: Decide which network should be used for your CA connection to the IOC. I am assuming it's the 192.168.50.0/24 network.

Now, to reach all IOCs on the selected CA network, set the EPICS address list variable to its broadcast address. 

The port number you are setting (5065) is *not* the default port for CA. Do this only if you also set your IOC to use a non-standard port. Assuming this was not intended, I would try using

EPICS_CA_ADDR_LIST=192.168.50.255

Hope this helps.

~Ralph

Liebe Grüße nach Jena!