Different calibration settings by using Scope WebApp and python API
Posted: Sun Jan 21, 2024 10:30 pm
Hi all,
I recently updated my RP's OS to the latest stable version:
#######################################################################
# Red Pitaya GNU/Linux Ecosystem
# Version: 2.00-43f2d6cd9
# Build: 23
# Branch:
# Commit: 43f2d6cd994dfc684cd1e5e1c3ce85bab91e8e44
# U-Boot: "redpitaya-v2022.1"
# Linux Kernel: "branch-redpitaya-v2022.3"
# Pro Applications: ""
#######################################################################
by flashing an SD card. Because of that I re-calibrated my RP following this tutorial (automatic) https://redpitaya.readthedocs.io/en/lat ... ation.html.
After calibration, the oscilloscope readings using the oscilloscope WebApp seem fine.
Calibration parameters are for CH2 HV:
AA: 16901
BB: 193419
PP: 9830
KK: 14260634
Even though that works fine, I need to get the CH2 data through the python API, and here I stomp with a few problems:
1) There are different python APIs (the one on the jupyter notebook examples that uses mercury overlay and the one that is a wrapper of the C API shown here:
https://redpitaya.readthedocs.io/en/lat ... -exm1.html)
. I tried with both and both give me different results than the WebApp. For example, for a 5Vpp 100hz square wave with the jupyter notebook API and forced trigger I get this:
https://imgur.com/a/jB1DmdG
2) That is the best I could manage to get, but sometimes the trigger doesn't work properly and I get weird signals like in this picture:
https://imgur.com/a/v1rqhpc
Both APIs have these problems.
I didn't have these problems with the old version of the OS.
The code used for each acquisition is:
this one for the jupyter API:
https://github.com/RedPitaya/jupyter/bl ... rced.ipynb
This one for the C wrapper API:
https://redpitaya.readthedocs.io/en/lat ... -exm2.html
Why is this happening and how can I fix it?
What is the difference between the jupyter notebook (mercury) API and the API that is a python wrapper around C API? Which one should I use and why?
Why are the readings on the oscilloscope webapp right but wrong by using any python API? what API does the webapp use?
Thank you very much
I recently updated my RP's OS to the latest stable version:
#######################################################################
# Red Pitaya GNU/Linux Ecosystem
# Version: 2.00-43f2d6cd9
# Build: 23
# Branch:
# Commit: 43f2d6cd994dfc684cd1e5e1c3ce85bab91e8e44
# U-Boot: "redpitaya-v2022.1"
# Linux Kernel: "branch-redpitaya-v2022.3"
# Pro Applications: ""
#######################################################################
by flashing an SD card. Because of that I re-calibrated my RP following this tutorial (automatic) https://redpitaya.readthedocs.io/en/lat ... ation.html.
After calibration, the oscilloscope readings using the oscilloscope WebApp seem fine.
Calibration parameters are for CH2 HV:
AA: 16901
BB: 193419
PP: 9830
KK: 14260634
Even though that works fine, I need to get the CH2 data through the python API, and here I stomp with a few problems:
1) There are different python APIs (the one on the jupyter notebook examples that uses mercury overlay and the one that is a wrapper of the C API shown here:
https://redpitaya.readthedocs.io/en/lat ... -exm1.html)
. I tried with both and both give me different results than the WebApp. For example, for a 5Vpp 100hz square wave with the jupyter notebook API and forced trigger I get this:
https://imgur.com/a/jB1DmdG
2) That is the best I could manage to get, but sometimes the trigger doesn't work properly and I get weird signals like in this picture:
https://imgur.com/a/v1rqhpc
Both APIs have these problems.
I didn't have these problems with the old version of the OS.
The code used for each acquisition is:
this one for the jupyter API:
https://github.com/RedPitaya/jupyter/bl ... rced.ipynb
This one for the C wrapper API:
https://redpitaya.readthedocs.io/en/lat ... -exm2.html
Why is this happening and how can I fix it?
What is the difference between the jupyter notebook (mercury) API and the API that is a python wrapper around C API? Which one should I use and why?
Why are the readings on the oscilloscope webapp right but wrong by using any python API? what API does the webapp use?
Thank you very much