Products > Test Equipment
REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol
Wim13:
I never use the trigger outs, as Marmad said, just use one of the signals to trigger the other DSO also.
So i have 4 signals on the DS1000, and 1 of these signals is also connected to the ext trigger input of the DS2000
The jitter of the DS1000 is 8 nSec, independed of the input frequency, see picture below, displayed on the DS2000
the other signal is the orginal, that i can vary to any freq. the jitter will not change
pa3bca:
--- Quote from: marmad on May 21, 2014, 04:03:13 pm ---But I don't think the annoyance of the jitter would be related to the frequency of the input signal (or DUT).
--- End quote ---
Yes of course, the jitter is always 8 ns, independent of the timebase and/or the observed waveform. What I meant to say is that (in my opinion) this method of locking both scopes is not very useful for displaying waveforms above (an arbitrary chosen frequency of say) 1 MHz as then 8 ns becomes a significant percentage of the analyzed and displayed frequency's period, resulting in a visible and annoying smear of the waveform.... For lower frequencies the jitter is just less or not at all visible.
But Wim's method of syncing the scopes works much better.
marmad:
pa3bca:
Hi Marmad,
Thanks for this interesting video. I was just struggling with an I2C problem, and learned a few things how to optimise use of the segmented memory (bummer it will not decode in analyze mode, maybe in the next FW update?). Maybe I should fire up the hex editor.
Looking forward to seeing this functionality in RUU.
marmad:
--- Quote from: pa3bca on May 25, 2014, 05:17:31 pm ---Thanks for this interesting video. I was just struggling with an I2C problem, and learned a few things how to optimise use of the segmented memory (bummer it will not decode in analyze mode, maybe in the next FW update?). Maybe I should fire up the hex editor.
Looking forward to seeing this functionality in RUU.
--- End quote ---
You're welcome, pa3bca.
I think not-decoding in Analyze is a bug of some sort - the DSO seems to want to decode the data, but gets stuck on the 1st frame. But it might be my settings as well - I haven't spent much time playing around with different sample lengths (which would change the granularity of the data), so maybe a different size would yield different results. For now, I've just been making a mental note (or writing down) the match frames - then leaving Analyze and returing to normal Playback (where the decode works fine).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version