SUMMARY QUESTION: Can Realport somehow reject (e.g. fire an error) when it receives RS232 read/write commands to a DigiPortSP that has been disconnected? Right now, when I unplug my DigiPortSP, my code continues to think its connected my device.
I have a problem porting my application to use Realport.
I have a simple device which communicates via RS232. I can communicate with it flawlessy when I connect it directly to my computer. But when I connect via the LAN using a Digi Connect SP and Realport then I run into problems.
The problem is related to when Realport loses its connection to the DigiConnectSP. My code (written in LabVIEW) thinks the device is still connected, so it hangs when attempting to send RS232 commands to the device. I think part of my challenge is that my device does not use any handshaking. And also because the Realport COM port remains "alive" even after the DigiConnectSP is unplugged.