Skip to content
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

Closed
joewilliams opened this issue Nov 27, 2015 · 4 comments
Closed

TRANSFER_TIMED_OUT issue #19

joewilliams opened this issue Nov 27, 2015 · 4 comments

Comments

@joewilliams
Copy link

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 first interrupt_read on line 28. Unfortunately, the error does not contain transferred 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?

@larskanis
Copy link
Owner

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 transferred ? It is a method of LIBUSB::Error .

@joewilliams
Copy link
Author

What do you mean with transferred ? It is a method of LIBUSB::Error .

e.transferred is empty when I catch the exception.

@larskanis
Copy link
Owner

e.transferred is empty when I catch the exception.

Understood. However devices are very diverse, so I can't give you a general advice, except looking at the transferred packets.

@larskanis
Copy link
Owner

The issue is hopefully solved in the meantime, so that I'll close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants