On 23/05/17 10:53, Christoph Schroeder wrote:
On 05/23/2017 10:40 AM, Torsten Bögershausen wrote:
Which side does the retransmission ?
The IOC ?
The device ?
The device retransmits a package that the IOC already received again and
again until it gives up. The IOC sends duplicate ACK. It seems the
acknowledge is ignored on the devices side.
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 ?
Right, netstat tells me the connection is still established, but there
is no flow of data anymore and the buffers are empty. The last package I
reveived from the device is the TCP RST.
Which OS are you using ?
Which version of asyn ?
My tests where done with Debian 7 and Debian 8. The asyn version is
R4-30. The problem seems to be caused by a lower layer. I got the same
problem with a simple TCP client I wrote and even with netcat, so Asyn
isn't at fault here.
You should be able to use the CONNECT_PER_TRANSACTION feature from asyn
drvAsynIPPortConfigure("xx", "<host>:<port>[:localPort] http",0,0,0)
(But I wonder if this helps, when your device seems to have such problems)
Is the IOC sending anything more to the device?
And wait the response ?
Why is it so quite on the line ?
When the IOC polls the device, there should be some traffic coming out,
If there is nothing to be polled from the IOC, then it doesn't matter,
if the underlying TCP connection is not working, half-broken or whatever.
- Re: Force TCP/IP reconnect from Asyn/Streamdevice Christoph Schroeder
- Force TCP/IP reconnect from Asyn/Streamdevice Christoph Schroeder
- Re: Force TCP/IP reconnect from Asyn/Streamdevice Torsten Bögershausen
- Navigate by Date:
Siemens S7-300 PLC and EPICS Florian Feldbauer
AW: Siemens S7-300 PLC and EPICS Rekow, Jens
- Navigate by Thread:
Re: Force TCP/IP reconnect from Asyn/Streamdevice Torsten Bögershausen
Re: Force TCP/IP reconnect from Asyn/Streamdevice Christoph Schroeder