Experimental Physics and
Industrial Control System

Not with asyn in special, but with all kind of TCP/IP related devices.

TCP/IP has a „Keepalive“, but this is typically 2 hours.

Could you share more information about that "component in the communication chain“ ?
And what happens if the communication is broken ?
Is there a clean FIN on the TCP-layer ?
Is it just dropped ?

Can you run Wireshark on the IOC ?
On the instrument ?
More info is appreciated

Am 19.10.2015 um 16:38 schrieb Pedro Gigoux <[email protected]>:

> Hi,
>
> We are using asynDriver to talk to an instrument connected to a socket port on a remote site using an ASCII based protocol. The communication works well except that the connection consistently drops when the exposure time is longer than 30 minutes. While the instrument is exposing there's no traffic in the socket; this points to a component in the communication chain that times out if it doesn't see any traffic for more than a certain time. I did not find timeouts in the asynDriver code so I suspect that the problem is in a network switch/firewall. Has anyone seen a similar problem with asyn before?
>
> Thank you,
> Pedro Gigoux
> Gemini Observatory
>