Hi Márcio,
Have you looked at the asyn R4-29 release notes? It says this:
****************************
drvAsynIPPort now also directly supports the asynOption interface for 2 key/value pairs.
- key="disconnectOnReadTimeout", value="Y" or "N". This option replaces the USERFLAG_CLOSE_ON_READ_TIMEOUT that was introduced in R4-27.
The advantage of using the asynOption interface is that this behavior can now be changed at run-time, rather than being set once when the driver is created.
****************************
Since your device sends data every second, you can set the "disconnectOnReadTimeout" option and then read the device with a 10 second timeout. If it times out then it will reset the connection. Would this work
for you?
Mark
I am sorry to resurrect such an old thread. Mark, did you implement the optional keepalive support to the asyn socket driver, yet?
Here in SLAC we are seeing a scenario where it would be really useful. We have an equipment that sends data each second through a serial to ethernet converter. This equipment
does not accept any commands. Eventually, the converter reboots and Asyn receive no warning. So, for Asyn, we have an alive connection with no data, and for the converter, there is no active connection.
I tried this using only telnet without an IOC running and the behavior is the same: telnet does not know that the connection was broken with the converter.
The keepalive parameter would help us a lot in this case.
Software Engineer - SLAC - TID/AIR/ACS
----------------------------------------------
Subject:
Re: asyn timeout
Date:
Mon, 19 Oct 2015 18:24:12 -0300
I'd be happy to test the keepalive option when it's ready. It may not happen immediately since the instrument is a shared resource and the time to use it is allocated in blocks.
It seems like it might be a good idea to add optional keepalive support to the asyn socket driver. If I were to create a branch on github that implemented this would you be
able to test it?