Client not Showing Server Side Serial Port

Submitted by bails66 on #1

I have inherited a project that is using a VH server on a remote device (not even sure what hardware the server is at the moment) whereby the server is exposing a serial com port to the client Windows 10 PC. I have been tasked with installing the client and following instructions I connected to the VH server via WiFi and changed the settings to fixed IP address to align with the network that the device and the PC are on. This is a local LAN on an industrial bit of machinery.

After the initial setup the USB server was recognised by the client and on the LAN and the tree on the client showed 'USB Servers>IDID#001>FT232R USB UART (In use by you)'. However, the virtual com port did not appear in the device manager. The Device manager did show a FT232R USB UART under Other devices with a yellow triangle overlay.

It was thought that the Win10 PC needed to have the FTDI driver updated by the site local IT department, which they did. This removed the errant FT232R USB UART from other devices and now there is a USB device shown in Device Manager under 'Universal Serial Bus controllers>VirtualHere USB 3 eXtensible Host Controller'. There is still no virtual com port in the device manger that links to VirtualHere and in addition the FT232R USB UART that was showing in the client has disappeared. The actual server is still visible in the client.

Can anybody offer some advice. Really don't know what to try next with this.

Submitted by Michael on Sun, 2025/08/10 - 07:55

#2

Unplug and replug the FT232R. Does that show then?

Submitted by bails66 on Sun, 2025/08/10 - 11:42

#3

The VH server is installed on a RaspPi 5. Do you mean unplug the LAN cable between the Win 10 client and the RaspPi, or unplug the usb side of the RaspPi or just power the RaspPi down and then up again. For further information the RaspPi is installed inside a flameproof enclosure with a 1000V also inside the same enclosure. It is generally unacceptable in terms of safety to access the inside of the enclosure while it is powered. When the machine powers up everything powers up together. If its relevant, the RaspPi and server would likely be running well before the Win10 PC that is trying to access the server would. 

Submitted by Michael on Sun, 2025/08/10 - 13:06

#4

OK no need to electrocute yourself :) Can you ssh to the pi and then type lsusb. Does that show the FT232 device? Basically i don't think the pi is recognizing the USB device and so VirtualHere doesn't see it. This is why i think it would be good to check if it was OK by physically re plugging. But you can also just reboot the pi.

Submitted by bails66 on Sun, 2025/08/10 - 13:14

#5

Thanks. Will look at creating a temporary wiring through the enclosure to repower it. I assume it's a bit like any USB device in Windows... it needs to be plugged in after Windows has started to install and setup drivers properly. Can you confirm it doesn't need this on every use as the machine goes underground in a mine and is power cycled often.

This won't happen for another 24hrs or so. Appreciate your response on a Sunday.

BTW, the Pi is not my bit of kit, so can look at getting the OEM to do it that way. 

Submitted by Michael on Sun, 2025/08/10 - 14:00

#6

Can you ssh to the pi? That will be helpful before you do anything else. 

Submitted by bails66 on Sun, 2025/08/10 - 14:33

#7

I'll have to get login details from OEM. No reason why not. The same pi has worked when connected to the OEMs laptop which has internet access.