CP210x Silicon Labs device does not work on the Windows machine again...

Submitted by Martin_C on #1

Dear all,

I have been succesfully using Virtualhere Server/Client on two Windows_10 machines since September 2022. Three FTDIChip COM ports and one Silicon Labs device (with CP210x Universal Windows Driver) generating two COM ports. I have been using Silicon Labs drivers on both Windows_10 machines with no problem for two years.

In summer 2024 (I do not know when exactly), most likely after some Windows update, the Silicon Labs device stopped working, while FTDI devices work fine. I can see the CP210x ports in the VirtualHere client window but as soon as I apply any traffic into the COM port on the Client machine, the VirtualHere Server machine reboots.

I have tried not to install CP210x drivers on the Server machine, I have tried power management setup on the CP210x ports (everything what I have learned on the forum here) but nothing has helped. The Windows machine running the Virtual Here Server reboots every time I apply any traffic into the COM port on the Client side.

Currently I am using the latest Virtual Here Server/Client for Windows, the latest CP210x Universal Windows Driver v11.3.0, Windows 11 (23/H2) on the VirtualHere Server side and Windows 10 (22/H2) on the VirtualHere Client side.

Thank you for any help.

Submitted by Michael on Tue, 2024/11/12 - 06:43

#2

Could you stop and exit the virtualhere server. THen download and install the windows store version https://www.microsoft.com/store/productId/9PK805V256R6

That will install the Windows Store version of virtualhere server and put an icon in your start menu. Click the VirtualHere Server icon in the start menu and try to use the CP21xx again via virtualhere and see if it ok.

Submitted by Martin_C on Wed, 2024/11/13 - 10:26

#3

Hello Michael,

Thank you for your kind advice. The Server version from the Microsoft Store works (not rebooting the Server PC), if I make it working...

a) I am unfortunately still having troubles to see the CP210x devices in the Client window. If I launch the VirtualHere Server and Client and then re-attach (unplug/plug) the USB cable from the CP210x device (Icom IC-9700 transmitter) on the Server side, then I can see everything in the Client window, I can share the the USB ports over the local LAN and everything works.

If I then stop the Server (or shut-down and restart the Server PCs) and start the Server again, I can not unfortunately see the CP210x device in the Client window list. I can see just the FTDI devices. I will still play around with that to gather more data.

b) how to please correctly run the Microsoft Store version of the Server as a service (with the -b parameter) when the WindowsApps folder is inaccessible under normal circumstances. However, more important for me is to resolve the a) issue above. Thank you!

Thank you for your help.

Submitted by Michael on Wed, 2024/11/13 - 10:51

#4

a) Have a look in windows device manager to see if you can see the CP2x device there. It might be under Ports or it might be under Unknown Devices. Also if possible try to rollback the driver of the cp2x device using device manager Properties->Driver->Rollback and see if that helps

b) See here https://www.virtualhere.com/node/3952

Just type vhusbdwinw64.exe -b at the cmd.exe prompt

 

Submitted by Martin_C on Wed, 2024/11/13 - 11:03

#5

a) Yes, I can see the CP2x devices in the Device Manager on the Server side. There are FTDI COM ports and CP2x COM ports there. However, the Client can see the FTDI devices only :-(.... Until I unplug and plug the USB cable from the CP2x device...  Then the CP2x device re-initialize somehow and appears in the Client window.

But I can't do that (unplug and plug USB cable) every time as the Server PC is located remotely...

 

Submitted by Michael on Wed, 2024/11/13 - 11:14

#6

I suspect there is some bug in the latest cp2x driver. E.g its not responding to a query about it descriptors or something.

Can you:

  1. In the virtualhere server click Settings->View Server Log->Clear
  2. Reboot the server then check the virtualhere client after it reboots. If the cp21x doesnt appear unplug and replug then on the server click then click Settings->View Server Log->Copy to clipboard and paste in here

Submitted by Martin_C on Thu, 2024/11/14 - 08:38

#7

Hello Michael,

I installed old CP201x driver on the Server side (you spoke about fallback last time).

Then I cleared the server log, stopped the server, started the server, CP201N device did not appear in the Client window, then I unplugged and plugged again the CP201N USB device cable. The log is below:

2024-11-13 23:29:39 INFO :Device 5 [0403:6001] UNBOUND from connection 7
2024-11-13 23:29:39 INFO :Device 7 [0403:6001] UNBOUND from connection 7
2024-11-13 23:29:40 INFO :Device 24 [08bb:2901] UNBOUND from connection 7
2024-11-13 23:29:42 INFO :Device 22 [10c4:ea60] UNBOUND from connection 7
2024-11-13 23:29:43 INFO :Device 23 [10c4:ea60] UNBOUND from connection 7
2024-11-13 23:29:44 INFO :Connection 7 successfully removed (reason:server shutdown)
2024-11-13 23:29:44 INFO :Device 5 [0403:6001] BOUND to connection 7
2024-11-13 23:29:45 INFO :Unmanaging device 2 [174c:3074]
2024-11-13 23:29:45 INFO :Unmanaging device 3 [174c:2074]
2024-11-13 23:29:46 INFO :Device 5 [0403:6001] SURPRISE UNBOUND from connection 7
2024-11-13 23:29:46 INFO :Unmanaging device 5 [0403:6001]
2024-11-13 23:29:46 INFO :Unmanaging device 6 [1dd2:2211]
2024-11-13 23:29:46 INFO :Unmanaging device 7 [0403:6001]
2024-11-13 23:29:46 INFO :Unmanaging device 8 [8087:0026]
2024-11-13 23:29:46 INFO :Unmanaging device 21 [0451:2046]
2024-11-13 23:29:46 INFO :Unmanaging device 22 [10c4:ea60]
2024-11-13 23:29:46 WARNING :Warning, unbinding device at USB\VID_0451&PID_2046\6&11002365&0&1,USB\VID_10C4&PID_EA60\IC-9700_13008775_A,2 with 1 outstanding in-flight URBs
2024-11-13 23:29:46 INFO :Unmanaging device 23 [10c4:ea60]
2024-11-13 23:29:46 WARNING :Warning, unbinding device at USB\VID_0451&PID_2046\6&11002365&0&1,USB\VID_10C4&PID_EA60\IC-9700_13008775_B,3 with 1 outstanding in-flight URBs
2024-11-13 23:29:46 INFO :Unmanaging device 24 [08bb:2901]
2024-11-13 23:29:46 WARNING :Warning, unbinding device at USB\VID_0451&PID_2046\6&11002365&0&1,USB\VID_08BB&PID_2901\7&106FB2E1&4&4,4 with 1 outstanding in-flight URBs
2024-11-13 23:30:03 INFO :Listening on all network interfaces at TCP port 7575 (IPv6 dual-stack)
2024-11-13 23:30:03 WARNING :Loading string descriptor for device on port 6 failed, Zaøízení pøipojené k systému nefunguje. (0x0000001f)
2024-11-13 23:30:09 WARNING :Loading string descriptor for device on port 1 failed, Zaøízení pøipojené k systému nefunguje. (0x0000001f)
2024-11-13 23:30:11 ERROR :Error 3 opening hub interface of child USB\VID_0451&PID_2046\6&11002365&0&1 to get numPorts, Systém nemùže nalézt uvedenou cestu. (0x00000003)
2024-11-13 23:30:11 INFO :Found Super speed device [174c:3074] "Asmedia, ASM107x" at address 2
2024-11-13 23:30:11 INFO :Found High speed device [174c:2074] "Asmedia, ASM107x" at address 3
2024-11-13 23:30:11 INFO :Found Full speed device [0403:6001] "FTDI, FT232R USB UART" at address 5
2024-11-13 23:30:11 INFO :Found Full speed device [1dd2:2211] "0x1dd2, mini GPS Reference Clock" at address 6
2024-11-13 23:30:11 INFO :Found Full speed device [0403:6001] "FTDI, FT232R USB UART" at address 7
2024-11-13 23:30:11 INFO :Found Full speed device [8087:0026] "0x8087, 0x0026" at address 8
2024-11-13 23:30:11 INFO :Found Full speed device [0451:2046] "0x0451, 0x2046" at address 21
2024-11-13 23:30:26 INFO :192.168.13.122 connected as connection 14 (Standard TCP)
2024-11-13 23:30:28 INFO :Device 5 [0403:6001] BOUND to connection 14
2024-11-13 23:30:28 INFO :Unmanaging device 21 [0451:2046]
2024-11-13 23:30:29 INFO :Device 7 [0403:6001] BOUND to connection 14
2024-11-13 23:32:25 WARNING :Loading string descriptor for device on port 1 failed, Zaøízení pøipojené k systému nefunguje. (0x0000001f)
2024-11-13 23:32:25 INFO :Found Full speed device [0451:2046] "0x0451, 0x2046" at address 21
2024-11-13 23:32:25 INFO :Found Full speed device [10c4:ea60] "Silicon Labs, CP2102N USB to UART Bridge Controller" at address 22
2024-11-13 23:32:26 INFO :Found Full speed device [10c4:ea60] "Silicon Labs, CP2102N USB to UART Bridge Controller" at address 23
2024-11-13 23:32:26 INFO :Found Full speed device [08bb:2901] "Burr-Brown from TI              , USB Audio CODEC " at address 25
2024-11-13 23:32:27 INFO :Device 22 [10c4:ea60] BOUND to connection 14
2024-11-13 23:32:28 INFO :Device 23 [10c4:ea60] BOUND to connection 14
 

Submitted by Michael on Thu, 2024/11/14 - 10:00

#8

This line is the issue:

ERROR :Error 3 opening hub interface of child USB\VID_0451&PID_2046\6&11002365&0&1 to get numPorts, Systém nemùže nalézt uvedenou cestu. (0x00000003)

Virtualhere Server is attempting to enumerate all the usb devices connected to the server, so it asks Windows to return a list of attached USB Hubs that are connected. One of those hubs is the built-in Texas Instruments 4 port USB Hub (0451:2046) inside the ICON radio. Virtualhere then attempts to access the Hub and ask it how many ports it has. At this point Windows says the hub is not there! 

In the past, Ive seen these sorts of weird interactions when the USB device has complicated firmware inside it and it takes a few seconds for it to "boot" and actually be a complete USB device.

So what virtualhere server does is it will wait 1 second and try the procedure above again and again and on the 3rd fail it will return the error above. Since it cant enumerate the hub it cant see any CP devices attached.

So not sure of the issue, i cant do anything about it.

If you dont run virtualhere at all and just plug the icon into the windows server, does it appear ok in device manager, or does it take 5 seconds to appear perhaps?

I do sell a USB hub that can remotely power cycle ports if you want to try that https://modularkvmip.com/product/usb-hub/

 

 

 

Submitted by Martin_C on Sat, 2024/11/16 - 02:49

#9

Hello Michael,

thank you for your time and effort. If I resolve my problem by purchasing the USB hub for $40, it is not a big deal.

On the other hand, as I wrote at the beginning, I have been succesfully using your VirtualHere (with the same ICOM IC-9700 Radio firmware) for more than 2 years.

If I accept your explanation, it would mean that Windows has changed the way (by some Windows upgrade) how they approach the Texas Instruments 4 port USB Hub inside of the ICOM Radio. BTW, the CP2102N device appears in the Device Manager quite normally once plugged-in.
 

Anyway, just as a trial, I will try using some free trial of some other USB over LAN product. If the behaviour is the same, I will live with you VirtualHere SW and your special USB hub. Thank you for your help.

Submitted by Michael on Sat, 2024/11/16 - 07:18

#10

Sure, let me know how it goes

Submitted by Michael on Wed, 2024/11/27 - 09:07

#11

This is resolved in version 4.7.2 of the server.