Connection errors with 3x Ifm agents polling different ports on the same IO-Link master

[swh76]

I'm adding an agent for another Ifm device, a KQ1001 level sensor (see branch https://github.com/simonsobs/socs/tree/ifm_kq1001_levelsensor) and noticed something that may or may not matter; when I run multiple agents all polling my AL1340 IO-Link master (which as two SBN246 flowmeters and this KQ1001 level sensor on it) if more than one is running at a time, I see many of this error in each of the agents' logs;

2024-09-26T19:56:30+0000 Connection error occured: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
2024-09-26T19:56:32+0000 Connection error occured: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
2024-09-26T19:56:33+0000 Connection error occured: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
2024-09-26T19:56:37+0000 Connection error occured: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
2024-09-26T19:56:40+0000 Connection error occured: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))

Perhaps due to collisions between http requests of the different agents? It seems to push through the error, so maybe doesn't matter but fyi @sanahabhimani @BrianJKoopman.

[sanahabhimani]

Just to double check, you saw this even with 2 devices (i.e., 2 flowmeters) connected to the same AL1340 IO-Link?

[swh76]

Ah, good question. I don't think I do. I just checked that it doesn't happen if I have just 2 agents polling the AL1340 (of either the SBN246 agent or my new KQ1001 agent). So perhaps only an issue with polling >2 ports with 3+ independent agents?