Page 1 of 1

How to get the ADC to run continuosly.

Posted: Thu Feb 01, 2024 2:46 pm
by whatup.itswhit
Hi all,

I am coding in python on the Jupyter Lab and was wondering if there was any way to have the ADC run continuously even after a trigger happens. What I have coded currently is a loop that collects data and then the program is triggered. Then, I must apply a reset and then a start command. The reset and start portion of the code is slowing the program down by 8 microseconds and I need it to be faster. Is there any way to code it so that the ADC continues to run after the trigger so that I don't need that section of code? Someone suggested using rp_AcqSetArmKeep(<enable>) but that requires the use of the new rp library, and our code is currently using the mercury library. Is there an equivalent to the rp_AcqSetArmKeep(<enable>) in mercury?


Thanks for any help that can be offered!

Re: How to get the ADC to run continuosly.

Posted: Wed Feb 07, 2024 11:20 am
by redpitaya
Hello Whit,

Thank you for posting on the forum.

Yes, using the "rp_AcqSetArmKeep(<enable>)" function to enable prevents Red Pitaya from stopping the acquisition after the triggering moment.

We moved away from the "mercury" image as the functionality was not well documented. With the 2.00-30 OS, we integrated the standard "v0.94" image with Jupyter Notebook. We made Python wrappers for all C API commands (Python API commands), which are now accessible through the Jupyter Notebook with the "rp" library (the full range of commands from the command list is available: https://redpitaya.readthedocs.io/en/lat ... i-commands)

The "mercury" image has limited functionality compared to the C API commands, so the ArmKeep command is not included. Everything possible in the Mercury image is documented here: https://github.com/RedPitaya/jupyter. For the FPGA implementation, you will have to check the FPGA image itself (building the project): https://redpitaya.readthedocs.io/en/lat ... fpga-image