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

Rewrite Transport to use bMaxPacketSize #190

Closed
ap-- opened this issue Apr 23, 2023 · 0 comments · Fixed by #198
Closed

Rewrite Transport to use bMaxPacketSize #190

ap-- opened this issue Apr 23, 2023 · 0 comments · Fixed by #198
Assignees

Comments

@ap--
Copy link
Owner

ap-- commented Apr 23, 2023

Every now and then Overflow errors pop up in the issue tracker, that I can't reproduce locally with the spectrometers available to me.

My current guess is that the issue is that the transport class should check the endpoint size and read data in the provided packet size. Under some situations (firmware? hardware version?) the hardcoded values seem to mismatch with the actual endpoint size. Packets are zero padded by libusb. So we can just read whatever size is reported there.

Hopefully this should fix those issues.

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

Successfully merging a pull request may close this issue.

1 participant