High precision electron accelerator experiment with 4 RPs
Posted: Fri Oct 23, 2015 4:47 pm
Hi people,
finally I made it to this forum. In the last months I started to believe, that my (and others) work with the red pitayas may become more efficient when I get in touch with other rp users.
Following is my project I want to share with you:
I use (so far ) four RPs to stabilize a beam for an upcoming electron accelerator. The system is tested at an already existing electron accelerator.
The FPGAs shall provide both a feed forward as well as a closed control loop. For this in the next weeks I will modify the Design. The four RPs need to get the data totally synchronized. For that I need to start the data acquisition with the trigger and not by software arming. I will never use the 125MHz, so that I would always have some jitter of the size of sample distance. ( At the moment it's stopped by the trigger, not started). We could already succesfully stabilize a beam with the in-built PID-controller for demonstration purposes.
I modified an acquire to get data from the adc and save it to a file on a network disk. Red Pitayas are already running as a Run Control server client and are remote controlled. The trigger to synchronize the data is set up as pulses from a Spartan 6 evaluation board connected to all RPs. The power supply is solded to the RPs and has very low ripple (required for high precision).
What I am now on is the new ecosystem which is totally different than the one before. I wanted to load a bitstream but struggle with customization of network configs and profile on the /opt. When I manage this problem, I will squeeze out 2 bit more from the adc averaging. For some reason they are cut in the design and only 14 instead of 16 bit are given to the cpu...
finally I made it to this forum. In the last months I started to believe, that my (and others) work with the red pitayas may become more efficient when I get in touch with other rp users.
Following is my project I want to share with you:
I use (so far ) four RPs to stabilize a beam for an upcoming electron accelerator. The system is tested at an already existing electron accelerator.
The FPGAs shall provide both a feed forward as well as a closed control loop. For this in the next weeks I will modify the Design. The four RPs need to get the data totally synchronized. For that I need to start the data acquisition with the trigger and not by software arming. I will never use the 125MHz, so that I would always have some jitter of the size of sample distance. ( At the moment it's stopped by the trigger, not started). We could already succesfully stabilize a beam with the in-built PID-controller for demonstration purposes.
I modified an acquire to get data from the adc and save it to a file on a network disk. Red Pitayas are already running as a Run Control server client and are remote controlled. The trigger to synchronize the data is set up as pulses from a Spartan 6 evaluation board connected to all RPs. The power supply is solded to the RPs and has very low ripple (required for high precision).
What I am now on is the new ecosystem which is totally different than the one before. I wanted to load a bitstream but struggle with customization of network configs and profile on the /opt. When I manage this problem, I will squeeze out 2 bit more from the adc averaging. For some reason they are cut in the design and only 14 instead of 16 bit are given to the cpu...