We know you were missing a lot of data early on. To run this test, the sampling will need to be solid. No missing data. The trigger jigger will need to be VERY small. on and on.... Once you have all the small details ironed out, it should be flat. There should be no need to disguard data.
Hi, thanks for the response.
I think the triggering is OK now, using the sync pulse of 5 ns rise time at a cycle of ms, should do the trick.
Also because I have 2 simple ramps, I don’t think the timing can create the glitches I’m still seeing (1 I tackled).
Making the averaging more advanced, did not make it better. I’m seeing more of the true measurements now, thus the adc’s discrete values. But it is also an indication that the glitches are not single high spikes that where averaged down. They are in the signal of all the frames and go up and down with the AWG offset.
I’m not sure about what you mean by missing data. I turned away from scope averaging to do it in a script myself. So I know I get 378 frames of data.
My setup is way more simple (and slower) than yours. But still I seem to get some ringing. I purposely choose a ramp which was symmetrical and thus not having large change in voltages/currents.
Even in the most simple setup of having the AWG directly connected to the scope, they turn up.
Maybe I should suspect the AWG of acting strange. I could “zoom” on a glitch and see how that looks like.
If it’s in the signal than it will show up enlarged. Maybe showing dac issues.