-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Possible issue with get_input_report #174
Comments
Can you please share your code and describe which HW are you using for testing? |
I am using a custom device (OpenFFBoard) that was previously used with pywinusb successfully. This is the descriptor section for this report: https://github.com/Ultrawipf/OpenFFBoard/blob/master/Firmware/FFBoard/UserExtensions/Src/usb_hid_1ffb_desc.c#L49 This is the section of the code that builds and sends the packet and waits for the reply:
What actually does work is just getting all packets until the right one is found so i know that the packet is being sent at the right time and received:
But this is not a good solution as the device will be sending gamepad data at the same time which would be received here too. |
When calling
get_input_report
(with a length of 25) it does not return any actual data.Only a list with the requested ID as the first and only entry no matter if the device actually has sent data with this id or not.
When instead reading all reports with
device.read()
until a report with the correct ID in the first byte is received i can confirm that the device actually sends the requested data.Not sure if this is an issue with the python library or the underlying hidapi.
OS: Windows 10
Version: 0.14.0
Python 3.11.1
The text was updated successfully, but these errors were encountered: