I am using AirBorne serial bridges from DPAC. And I am using their vcom utility. But because I did not know how to download the utility I gave you a link to another one. I am going to switch to it pretty soon. That utility is capable of constantly pinging the device and as soon as the device is disconnected for whatever reason the program creates a record into a log file. My program will monitor the log and reopen the port if needed. The utility even can reopen the port but it takes too long for it. About 20 sec. That is too long.
Yes, the project is very interesrting. It is manufacturing where we are implementing the Floor control system. Data collection is based on scanning. The scanner are installed everywhere we need to collect information. The whole solution is wireless.

>'Morning Mark,
>
>Are you using their supported devices - meaning, do the wireless/serial devices support RFC2217/NVT? If so, then this control seems to pass the handshake between the 'ports'. I'm testing with the VSP on both ends, one as client and the other as server. If not, then how does your serial data presently get to Ethernet?
>
>If your port closing is due to packet loss at the network level, I'm afraid the above won't help, unless they expose something I don't see.
>
>Interesting project, BTW.
>
>>Basically it's a form with MSCOMM control.
>>Vcom utility creates virtual ports and these ports are opened by the MSCOMM control. I have multiple exes - one per a port.
>>
>>>That's the one I thought. The documentation sucks, quite frankly. But the price is right...
>>>
>>>Can you give me a rough layout of your configuration? Who is client and/or server, and where in the mix is the MSCOMM control?
>>>
>>>>http://www.hw-group.com/download/sw/HW_VirtualSerialPort.zip