Ubuntu 20.04 LTS USB ID seems wrong

[SparkerInVR 13]

Is there a reason the ID is 0000:0000? On my system Device 033 is the Fulcrum One Yoke.

bill@billsvr-2004:~$ lsusb
Bus 002 Device 003: ID 28de:2400 Valve Software 
Bus 002 Device 002: ID 0424:5744 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 020: ID 06a3:0d67 Saitek PLC Pro Flight Switch Panel
Bus 001 Device 032: ID 16d0:0a38 MCS 
Bus 001 Device 033: ID 0000:0000  
Bus 001 Device 017: ID 131d:0159 Natural Point 
Bus 001 Device 013: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub
Bus 001 Device 034: ID 24c6:581b  
Bus 001 Device 005: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub
Bus 001 Device 009: ID 0b05:18a3 ASUSTek Computer, Inc. 
Bus 001 Device 015: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 012: ID 09eb:0131 IM Networks, Inc. 
Bus 001 Device 006: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 016: ID 0424:2740 Microchip Technology, Inc. (formerly SMSC) 
Bus 001 Device 014: ID 28de:2102 Valve Software 
Bus 001 Device 011: ID 28de:2102 Valve Software 
Bus 001 Device 007: ID 28de:2300 Valve Software 
Bus 001 Device 004: ID 0424:2744 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 001 Device 002: ID 28de:2613 Valve Software 
Bus 001 Device 008: ID 8087:0aaa Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
bill@billsvr-2004:~$

Thanks Bill

[SparkerInVR 13]

I am seeing the same thing on my Windows install when looking at Events of the HID controller.

Device HID\VID_0000&PID_0000\8&961a9fd&0&0000 was started.

I have worked with USB devices for a very long time as the author of Xsaitekpanels and have never seen this before from any USB device.

The VID should be the Vendor and the PID is the product identifier.

Thanks Bill

 

[ark 1,291]

2 hours ago, sparker256 said:

I am seeing the same thing on my Windows install when looking at Events of the HID controller.

Device HID\VID_0000&PID_0000\8&961a9fd&0&0000 was started.

I have worked with USB devices for a very long time as the author of Xsaitekpanels and have never seen this before from any USB device.

The VID should be the Vendor and the PID is the product identifier.

Thanks Bill

 

Does the yoke not work correctly -- exactly what problem is this causing with the sim?

Edited October 30, 2020 by ark

[SparkerInVR 13]

1 hour ago, ark said:

Does the yoke not work correctly -- exactly what problem is this causing with the sim?

Yes the yoke works fine with no issues.

The issue is that each USB device should have a unique identifier so the OS and sim can tell the difference.

[ark 1,291]

1 hour ago, sparker256 said:

Yes the yoke works fine with no issues.

The issue is that each USB device should have a unique identifier so the OS and sim can tell the difference.

Well, all 0s is unique (at least in the above list)!  😉

What organization assigns these unique USB codes? Seems there needs to be a central control for this to keep things unique given the number of USB devices in the world.

Al

Edited October 30, 2020 by ark

[tutmeister 711]

Hi Bill

As far as I understand it, a vid and pid are not required when using a class driver and the yoke will appear using the standard hid game controller driver as specified in the descriptor hence 0000 being used as no proprietary driver is required to be loaded. I've just tested with 2 yokes attached to my machine and they both work correctly. Registering to get a VID costs $6000 and is not required for any regulatory reasons. It is on the to do list to go into some updated firmware but it was not deemed as a must have expense for launch. I'm not a usb expert so am going of what I have been advised.

Hope this helps.

[SparkerInVR 13]

38 minutes ago, tutmeister said:

Hi Bill

As far as I understand it, a vid and pid are not required when using a class driver and the yoke will appear using the standard hid game controller driver as specified in the descriptor hence 0000 being used as no proprietary driver is required to be loaded. I've just tested with 2 yokes attached to my machine and they both work correctly. Registering to get a VID costs $6000 and is not required for any regulatory reasons. It is on the to do list to go into some updated firmware but it was not deemed as a must have expense for launch. I'm not a usb expert so am going of what I have been advised.

Hope this helps.

Wow I did not know that a VID costs $6000 but now it make more sense.

Thanks for improving my understanding of USB devices.

Bill

[tutmeister 711]

No problem, I'm really not an expert on USB from a technical point of view, or any point of view!, but if you want a VID you need to subscribe to the USB-IF for $5000 per year. This gives you a VID and use of the USB logo so long as your device meets the USB specifications. If you don't subscribe then it costs $6000 for a VID and $3500 to use the logo again so long as your device meets the specs. None of this is required though if you are a small company and only using class drivers as the $6000 buys you nothing. It seems to be a good way for the USB Implementation Founders to print money, especially asthey stopped you selling your unused PIDs to other people. Who really needs 65536 product ids anyway?!

It is something I'd like us to have in future and will look at including in some new firmware.