Hardware Id Missing

Submitted by jmart on #1

I have a device that works when connected locally but does not work remotely with VirtualHere. When I connect the device, Windows shows a message saying "Hardware Id Missing". I saw a previous post here describing a similar issue. I followed what you said on that post and updated my Pi and checked the syslog, which all looked normal. It looks like after that, you connected to the user's device and did troubleshooting yourself. This will not be possible in my case without significant headaches, since we have confidential information on our network.

Are there any other troubleshooting steps I can take in order to fix this?

Thanks

Submitted by jmart on Wed, 2017/03/15 - 23:36

#2

I also forgot to mention I am using the Windows client version 4.0.2 and vhusbdarmpi2 version 3.2.8. I believe they are the latest.

Submitted by Michael on Thu, 2017/03/16 - 09:06

#3

Is this with windows 10 or an earlier version of windows? Win10 uses a different virtualhere driver...

Submitted by jmart on Fri, 2017/03/17 - 03:07

#4

This is on Windows 7. I didn't realize there's a separate driver for Win10, but it makes sense.

Submitted by Michael on Fri, 2017/03/17 - 09:21

#5

OK, if possible can you tell me if it works on windows 10 and what the hardware ID shows? Or just plugging it in and getting the hardware id? You can find the hardware id by opening up windows device manager and right clicking on the device selecting properties -> Details -> Hardware Ids

Submitted by jmart on Sat, 2017/03/18 - 03:20

#6

It does indeed work on Windows 10 with VirtualHere. The device uses 4 different COM ports, here are the hardware IDs listed for each port:

FTDIBUS\COMPORT&VID_0403&PID_6011
FTDIBUS\COMPORT&VID_0403&PID_6011&MI_00

FTDIBUS\COMPORT&VID_0403&PID_6011
FTDIBUS\COMPORT&VID_0403&PID_6011&MI_01

FTDIBUS\COMPORT&VID_0403&PID_6011
FTDIBUS\COMPORT&VID_0403&PID_6011&MI_02

FTDIBUS\COMPORT&VID_0403&PID_6011
FTDIBUS\COMPORT&VID_0403&PID_6011&MI_03

Thanks

Submitted by Michael on Sat, 2017/03/18 - 21:56

#7

ok i think you will have to use win10 if possible as im not sure that device uses a standard usb descriptor compatible with the win7 virtualhere driver.

Submitted by jmart on Mon, 2017/03/20 - 23:39

#8

Don't those hardware IDs follow the format here https://msdn.microsoft.com/en-us/windows/hardware/drivers/install/stand… ? Looks like the "Multiple-Interface USB Devices" format that's listed on that page.

Windows 10 is not an option right now so I'd really love to figure out how to use this device on Windows 7 if possible. I was hoping that since Windows 7 supports multiple interface devices, VirtualHere would as well.

Thanks for the help.

Submitted by Michael on Tue, 2017/03/21 - 05:40

#9

Hardware/Device/Compatible id's always start with "USB" (as described on that page). However yours start with "FTDIBUS". Im wondering if perhaps you sent the wrong ids in the previous message? Were they on the composite leaf devices rather than the root device? Can you double check. In the windows Device Manager select View -> Devices by Connection, look at the device under those id's you sent. Put that hardware id & device id here

Submitted by jmart on Tue, 2017/03/21 - 22:33

#10

Yep, you were correct. I was getting the ID from the Ports section. Here is the correct ID:

USB\VID_0403&PID_6011&REV_0800
USB\VID_0403&PID_6011

So each of the 4 connections have the same IDs with &MI_00, &MI_01, &MI_02, and &MI_03 appended to each respectively.

Thank you

Submitted by Michael on Wed, 2017/03/22 - 12:00

#11

OK i think you will have to debug for me. Can you do this

1. Download usblyzer.com (the free version)
2. Start it and select the capture menu->Capture settings then select everything
3. Now start the capture and then plug in your device directly.
4. messages will start to stream after about 5 seconds stop the capture and then save the file
5. Now plug in the device into the virtualhere server
6. Clear the capture and then press start capture
7. Now use the device via virtualhere
8. A few messages should start streaming until the enumeration problem occurs
9 Wait a few more seconds then press stop capture
10. Save the capture

Send me those two captures. mail [at] virtualhere.com (mail[at]virtualhere[dot]com)