No com port assigned on client side when virtualhere client connects to server through a remote TCP connection port 7575

2 posts / 0 new
Last post
kajeet
No com port assigned on client side when virtualhere client connects to server through a remote TCP connection port 7575

Under the same home network, when virtualhere client (my laptop) connects to a raspberry pi (where virtualhere server is installed) connected to a Solar controller, a comp port is assigned to the client machine. I then use the com port assigned in my Solar Controller software application, and I can run the solar software application without any issues. This allows me to run the solar app on my laptop in my office at the second level of my home when the solar controller itself and the raspberry pi are at the lowest level in the garage.

Works great but I could not do the same thing outside of my network. Actually, I just found a way to connect my client to the server using a TCP connection and port 7575 and using my public IP address. So it is great but the difference with when I run this under my home network is that for some reasons, no com port is associated with virtualhere client there is an attempt but I am getting these error messages "This device cannot start. (Code 10) The I/O request was canceled."

And of course the solar controller software needs a com port to run.....!!!

Has anyone faced this issue and resolved it? or do you know a workaround? I am new to the Forum so I hope I am not asking a duplicate question. Thanks in advance for your time and support....

Michael
.

Sounds like your network latency is too high over the external network. Serial devices are sensitive to latency because they need data bits within a certain time. In the virtualhere client right click USB Hubs -> About -> Statistics. What does that show when using the serial device on your external network?

Log in or register to post comments