Hi All,
I'm trying to connect to the SpaceMouse devices using hid api. When I iterate the devices installed on my machine, I get a single device for my SpaceMouse Pro or Compact being connected. Whereas when the usb dongle is connected I get around 5-6 devices all sharing the same vendor-id/product-id of the Universal Receiver, with different serial strings. I'm able to create an instance of these devices, but only able to read the device state from one of them.
How can i identify the 3dConnexxion Universal Receiver that provides the device state from the lists, is there any identification method?
Snapshot of 3dconnexion devices on my machine:-
Device detail:
Product Name: 3Dconnexion Universal Receiver
Product ID: C652
Vendor ID: 256F
Instance ID #1: AF5B
Instance ID #2: 18A0
Device detail:
Product Name: 3Dconnexion Universal Receiver
Product ID: C652
Vendor ID: 256F
Instance ID #1: AF5B
Instance ID #2: 3FB0
Device detail:
Product Name: 3Dconnexion Universal Receiver
Product ID: C652
Vendor ID: 256F
Instance ID #1: AF5B
Instance ID #2: 66C0
Device detail:
Product Name: SpaceMouse Compact
Product ID: C635
Vendor ID: 256F
Instance ID #1: 5AFB
Instance ID #2: B10
Device detail:
Product Name: 3Dconnexion Universal Receiver
Product ID: C652
Vendor ID: 256F
Instance ID #1: AF5B
Instance ID #2: 66C0
Device detail:
Product Name: 3Dconnexion Universal Receiver
Product ID: C652
Vendor ID: 256F
Instance ID #1: AF5B
Instance ID #2: 8DD0
Device detail:
Product Name: 3Dconnexion Universal Receiver
Product ID: C652
Vendor ID: 256F
Instance ID #1: AF5B
Instance ID #2: B4E0
Device detail:
Product Name: 3Dconnexion Universal Receiver
Product ID: C652
Vendor ID: 256F
Instance ID #1: AF5B
Instance ID #2: B4E0
Device detail:
Product Name: SpaceMouse Wireless BT
Product ID: C63A
Vendor ID: 256F
Instance ID #1: FF04
Instance ID #2: 29A0
Multiple Universal Receiver Adapters
Moderator: Moderators
Re: Multiple Universal Receiver Adapters
A device can be paired to each one of those slots. Identifying that device is complicated, inconsistent and proprietary.
This is definitely a reason to use our API. All that horrible detail (and more complications coming in the future) is hidden from you.
I highly encourage you to switch to a better API.
This is definitely a reason to use our API. All that horrible detail (and more complications coming in the future) is hidden from you.
I highly encourage you to switch to a better API.
