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

Fix: timebase ps4000a #197

Merged
merged 2 commits into from
Feb 21, 2024
Merged

Fix: timebase ps4000a #197

merged 2 commits into from
Feb 21, 2024

Conversation

NINI1988
Copy link
Contributor

The timebase calculation for ps4000a devices was wrong:
See 3.7 Timebases from https://www.picotech.com/download/manuals/picoscope-4000-series-a-api-programmers-guide.pdf.

@hmaarrfk
Copy link
Collaborator

you believe that the 4824 and the 4000a are the same. is that correct?

@NINI1988
Copy link
Contributor Author

In the documentation PicoScope 4824 and 4000A Series are in the same Timebase calculation table. Only the PicoScope 4444 is different.
Also the calculation of the existing 4824 code matches my calculation and the datasheet, so I have combined them.
I have removed the 4828 because I can't find it on google and does not exists in the programmers api guide.

So yes I believe they are the same for the timebase calculation

@hmaarrfk hmaarrfk merged commit 7b7e692 into colinoflynn:master Feb 21, 2024
2 checks passed
@NINI1988 NINI1988 deleted the fixTimebase branch February 21, 2024 14:32
@NINI1988
Copy link
Contributor Author

Could you please release a new version, so the 4000 series can be used easily. Thank you.

@hmaarrfk
Copy link
Collaborator

hmaarrfk commented Apr 2, 2024

Sorry for the delay: https://github.com/colinoflynn/pico-python/releases/tag/0.7.28

@BenediktBurger
Copy link
Contributor

Thanks for cleaning up the code.

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 this pull request may close these issues.

3 participants