-
-
Notifications
You must be signed in to change notification settings - Fork 124
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
Fix to use endpoints MaxPacketSize instead of hardcoded RECV_CHUNK size #417
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #417 +/- ##
=======================================
Coverage 24.91% 24.92%
=======================================
Files 25 25
Lines 3516 3515 -1
Branches 489 489
=======================================
Hits 876 876
+ Misses 2623 2622 -1
Partials 17 17
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Wow a fix that helps with Rigol devices is definitively welcome ! The formatting failure is unrelated to your changes so do not worry about it. Could you add a changelog entry ? Once it is done I will merge. @Fellypao it may be worth checking if this fixes your issue. |
This was found using a Rigol DS1074Z scope which has a limited MaxPacketSize of 64.
added changelog (hope 0.7.2 is ok for the version) |
Perfect ! Thanks a ton ! |
@MatthieuDartiailh Yes, this definitely fixes my issue (#414). Thank you. And many thanks to @sessl3r 👍 |
Amazing !!! I will try to cut a release ASAP |
Only as a little late FYI: From the usbtmc PR I got the info that some Agilent scopes will suffer performance from this as they report a smaller MaxPacketSize then they can do (1k vs 4k). |
Could you open an issue so that the information is less likely to be lost ? Honestly I take the win of people having Rigol scope working out of the box over maximal performance for Agilent scope. |
Thanks @sessl3r |
The issue was found to be not able to download screenshots from a RigolDS1074Z.
From this issue it was seen there is some workaround but not a fix.
As the same issue existed in the linux-usbtmc driver module it was easy to refix it here.
The main point is that those scopes have a limited MaxPacketSize which is reported by the USB device correctly and the TMC protocol is relying on using this MaxPacketSize.