Experimental Physics and
Industrial Control System

The instrument is located in a remote institution so I don't have much details about their network setup. On our side, the machine where the software runs goes through a couple of switches and the firewall before connecting to the remote host. Our IP is registered on their firewall to accept connections to the instrument. According to our IT department we don't have timeouts for outgoing traffic so we suspect the remote network equipment is the one dropping the connection (I don't have hard evidence to support this yet, though). A workaround that has been proposed is to modify the software to send a ping-like packet every minute to prevent the link from going down.

Thank you,

Pedro.

On 19 October 2015 at 12:27, Torsten bögershaus <[email protected]> wrote:

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