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
TRANSFER_TIMED_OUT issue #19
Comments
You can inspect the USB traffic with wireshark. It can capture USB in real time on Windows and Linux (at least). You can capture the communication with the original program and use this information to build and debug your program. I implemented several unknown USB protocols without source code that way, so given you have the sources, you should certainly get this device under control 😀 What do you mean with |
|
Understood. However devices are very diverse, so I can't give you a general advice, except looking at the transferred packets. |
The issue is hopefully solved in the meantime, so that I'll close it. |
I am attempting to port the code from this blog post to ruby and libusb. It can be found here. I seem to be running into
TRANSFER_TIMED_OUT
on the firstinterrupt_read
on line 28. Unfortunately, the error does not containtransferred
so I think there's nothing to read. Since the C code from the blog post seems to work properly I assume either I am doing something wrong (likely) or there's a bug in ruby-libusb. Any thoughts or suggestions?The text was updated successfully, but these errors were encountered: