-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3dConnexion Universal Receiver - Linux OK, Windows and MacOS not #136
Comments
Can you confirm, that you're opening the same interface ( Also, please check is it related to some known limitations (at least on Windows): #61. |
I believe I did. In fact, I tried explicitly specifying the interface number and none worked.
Given that the same spacemouse works quite happily when plugged in using the direct USB cable instead of the Universal Receiver, I don't think it's the same problem. But, perhaps it is? |
I'd suggest you check what is "correct" interface number on Linux, where you can get it to work, so you know exactly which one.
Maybe not. Maybe it is related, but not directly. Unfortunately I can't help you much more. Maybe someone else from the community will. |
Good idea, I will do that.
Thanks anyway for your assistance. Every little helps! |
I found the problem, on Windows (and probably MacOS too), I needed to match the usage page and usage to 1 and 8 respectively. |
Hi, I'm using hidapi (via cython-hidapi) to access a 3dConnexion Spacemouse. The mouse is supplied with a USB Universal Receiver. On Linux, I can open this device and read from it quite happily. But on both Windows and MacOS, although I can open the device, no data is ever returned from a read.
I am opening using the path returned from enumeration.
Also, on both Windows and MacOS, if I plug the same mouse into the computers using a USB cable, they both get mouse data OK (of course, they are then using a different vid:pid).
I don't really know that much about USB, HID, etc. so I am hoping someone can suggest where the problem lies.
Here's what lsusb -v on Linux says about the device...
Thanks.
The text was updated successfully, but these errors were encountered: