Redpitaya Forum

Hello,

I am trying to write a simple series of scpi commands to generate two different burst pulses from output 1 and 2. I was successful with making them generate both of them, however they are not syncing up properly. Does anyone have any suggestions or tips on how to accomplish this.

I've tried triggering output 2 to output 1 and then triggering output 1 immediately but that does not seem to be successful.

This is my code below:
rp_s.tx_txt('GEN:RST')

rp_s.tx_txt('SOUR2:FUNC ' + str(wave_form).upper())
rp_s.tx_txt('SOUR2:FREQ:FIX ' + str(freq))
rp_s.tx_txt('SOUR2:VOLT ' + str(ampl1))
# sets the number of cycles
rp_s.tx_txt('SOUR2:BURS:NCYC ' + str(push_num_cycles))
rp_s.tx_txt('SOUR2:BURS:NOR 21600')
rp_s.tx_txt('SOUR2:BURS:INT:PER ' + str(period1))


rp_s.tx_txt('SOUR1:FUNC ' + str(wave_form).upper())
rp_s.tx_txt('SOUR1:FREQ:FIX ' + str(freq))
rp_s.tx_txt('SOUR1:VOLT ' + str(ampl2))
# sets the number of cycles
rp_s.tx_txt('SOUR1:BURS:NCYC ' + str(burst_num_cycles))
rp_s.tx_txt('SOUR1:BURS:NOR 10800')
rp_s.tx_txt('SOUR1:BURS:INT:PER ' + str(period2))
# #
# #
# Enables output but does not start it
rp_s.tx_txt('OUTPUT1:STATE ON')
# turns on burst mode
rp_s.tx_txt('SOUR1:BURS:STAT ON')
# Enables output but does not start it
rp_s.tx_txt('OUTPUT2:STATE ON')
# turns on burst mode
rp_s.tx_txt('SOUR2:BURS:STAT ON')
rp_s.tx_txt('TRIG:IMM')

Please let me know if there are any obvious mistakes that I might be making. Thank you.

I am also trying to see if the jupyter notebook will be able to sync these two burst outputs. I was able to get a burst signal and a continuous signal to sync. Still working on it. Any guidance would be appreciated.

-Update: I was able to get them to sync but am having trouble with getting them to sync if their periods and burst_data_length are different. For some reason, it will run the period longer than it should, adding more cycles to the burst. If anyone has any experience with running burst on both outputs using jupyter, i would appreciate any tips.

Thank you for reporting this, it may be a bug and we are investigating it.