Experimental Physics and
Industrial Control System

Torsten Bögershausen <[email protected]> · Tue, 23 May 2017 10:40:49 +0200

On 23/05/17 10:21, Christoph Schroeder wrote:

Hi all,

I am currently struggling with a TCP/IP controlled device that has
problems with it's network stack or it's server implementation. After
some spurious retransmissions, which occurs several hours after the
connection was established, the device gives up and sends a TCP reset.
No communication after this point.

Which side does the retransmission ?
The IOC ?
The device ?

I am looking for a feasible workaround until the manufacturer can fix
this problem. Is there any way to force a reconnect of the TCP/IP
connection from Streamdevice context which I am currently using or at
least from Asyn? I would like to do this from software side without
rebooting the IOC e.g. with a cronjob.

Note: the connection still counts as "established" as shown by netstat
after the reset was received which is the reason why the autoconnect
option of drvAsynIPPortConfigure doesn't work in this case.

Now, well, it looks as if the reset was not processed by the IOC ?
At least it didn't cause the TCP connection to be terminated, right ?

Which OS are you using ?
Which version of asyn ?

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System