|
Hello Florian,
First, the usual questions. Which
versions of epics-base and associated modules are involved?
Including pvDataCPP, pvAccessCPP, and pva2pva if built as separate
modules. Do you set any of the EPICS_PVA* environment variables?
On this MPOD crate. Is there only the
one IOC process? fyi. you can add '-p' to 'netstat' and it will
tell you which PID each socket is associated with.
As Andrew mentioned. Setting $EPICS_PVA_DEBUG=3
will turn on a fire hose for logging.
From the output provided, PVXS is not
present. You might also try "pvxlist" and/or "softIocPVX" to see
if the behavior differs.
On 1/27/26 4:02 AM, Florian Feldbauer
via Tech-talk wrote:
Hey
all,
I have a strange problem, that I haven't encountered before.
In our lab we have a small test setup for our pixel sensors.
As HV/LV power supply for these sensors we use a Wiener MPOD crate
with an iseg Crate Controller.
The crate controller is running Linux (The Ångström Distribution
v2017.12) and an EPICS IOC with PVA.
Now, when I run `pvlist` from another PC I see a list of all the
IOCs running in this network except the one on the iseg Crate
Controller.
When I explicitly run `pvlist iseg-iCS2-5230317` I get a list of
all PVs from that IOC, so PVA communication works in general, but
for some reason this IOC is not reacting on broadcasts.
I checked with netstat and for me this looks correct:
root@iseg-iCS2-5230317:~# netstat -tuln |
grep 5076
udp 0 0 224.0.0.128:5076 0.0.0.0:*
udp 0 0 192.168.10.255:5076 0.0.0.0:*
udp 0 0 192.168.10.22:5076 0.0.0.0:*
udp 0 0 224.0.0.128:5076 0.0.0.0:*
udp 0 0 192.168.10.255:5076 0.0.0.0:*
udp 0 0 192.168.10.22:5076 0.0.0.0:*
udp 0 0 :::50767 :::*
There is no firewall running on the crate controller.
Any idea what could cause this issue?
Cheers,
Florian
|