REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol

[scummos]

Hey Teneyes, thanks for your effort!

No, nothing like that... I'm specifically interested in having the math function display Channel 1 plus Channel 2, but with different delays between the channels. I guess it's just not possible...
Thanks neverthereless

[marmad]

I'm specifically interested in having the math function display Channel 1 plus Channel 2, but with different delays between the channels. I guess it's just not possible...
Thanks neverthereless

I'm not exactly sure what you're trying to do - but it might be possible to use the delay trigger option to adjust the T between the two channels - if you can satisfy the edge trigger requirements. 

[Teneyes]

NOTE: This DS2072 display data  was Manually Created to test the  DSO measuring system.
so I can better understand .my first DSO.

THIS IS NOT A REAL SIGNAL

The display shows that the measurements are calculated/measured on the data that is displayed.

NOTE that the Sin(x)/x interpolation is  applied to the sample data points before measurements as shown by the "Vpp = 7.12V" , the peaks of the Sin ripples ( the data is a step of only 6.0V)

NOTE that the system knows only 2GSa/s is used , so cannot measure under 0.5ns thus rise time is measured as  "rise<500ps"

NOTE the difference among Max, Top, and Amp  measurements.

This maybe helpful to others to understand this DSO

[Salas]

Another thing now. The digital filter in the 1000 series was handy. Could limit the bandwidth very low, could notch out things etc. Brought ringing to pulse of course but for other stuff like susceptible power lines & motors (to fields, EMI or RFI, so to separate the original harmonic noise) was nice. Do you think that the lack of that menu in the 2000 is completely covered by Hi Res mode series averaging and large memory for instance? Any other settings suggestions for covering those needs?

P.S. Sorry if it has been mentioned before.

[Wim13]

NOTE: This DS2072 display data  was Manually Created to test the  DSO measuring system.
so I can better understand .my first DSO.


NOTE that the system knows only 2GSa/s is used , so cannot measure under 0.5ns thus rise time is measured as  "rise<500ps"

NOTE the difference among Max, Top, and Amp  measurements.

This maybe helpful to others to understand this DSO

Strange item, the signal seems to be able to look in the future,
before the signal goes up, ther is a reverse ringing, how does the signal
knows that some nSec later it has to go up..?

[Teneyes]

Strange item, the signal seems to be able to look in the future,
before the signal goes up, there is a reverse ringing, how does the signal
knows that some nSec later it has to go up..?

 @wim13
   It looks like the characteristics of the Sin(X) /x interpolation
See my post:
 http://www.eevblog.com/forum/testgear/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/msg182776/#msg182776
and Marmads dots & trace combined post at:
http://www.eevblog.com/forum/testgear/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/msg183376/#msg183376
note how the trace goes though the dots

Also check out:
http://cdn.teledynelecroy.com/files/whitepapers/wp_interpolation_102203.pdf

pages 3 8 10 for comparison to Lecroy, Tek, Aligent

check this pix for smoother step

[marmad]

One interesting thing I've learned while programming RUU is that the Rigol only displays 200 of the 256 possible ADC levels at any given time (mapped to the 8 vertical grid divisions) - even though the entire range is available via SCPI. My newest version of RUU (hopefully will post it tomorrow) has a 'Full ADC' switch - to allow seeing the full range.

Here is a clipped sine wave visible on the Rigol display:



And here is the same sine wave displayed in RUU (with 10 vertical divisions) at exactly the same time:

[Teneyes]

One interesting thing I've learned while programming RUU is that the Rigol only displays 200 of the 256 possible ADC levels at any given time (mapped to the 8 vertical grid divisions) - even though the entire range is available via SCPI. My newest version of RUU (hopefully will post it tomorrow) has a 'Full ADC' switch - to allow seeing the full range.

Yes Marmad , I noticed that when fudging the Waveform data, Just thought that data was rescaled on the the display , and not limited to the top and bottom, 

That wastes 25 % of the display resolution!!!
Yes,  nice if RUU displays the full resolution with 10 vertical divisions then there will not be a need to adjusted and the v/div.

By the way the waveform data file also has data before and after the data that is display.   I  put a dot  at middle screen Voltage but off to the right of the display and in the Pic below the sin(x) starts  at the end of the trace before the sample occurs off the display

[dougg]

One interesting thing I've learned while programming RUU is that the Rigol only displays 200 of the 256 possible ADC levels at any given time (mapped to the 8 vertical grid divisions) - even though the entire range is available via SCPI. My newest version of RUU (hopefully will post it tomorrow) has a 'Full ADC' switch - to allow seeing the full range.

I own a Agilent DSO1024A scope which is made by Rigol. One frustrating thing when viewing a signal with a large dynamic range (amplitude) was that as soon as a peak jutted out of the viewing window (either the top or bottom) then all the measurements that were impacted suddenly became "*****". So a little "headroom" above and below the displayed window in which measurements could still be taken is a good thing IMO.

[Teneyes]

One interesting thing I've learned while programming RUU is that the Rigol only displays 200 of the 256 possible ADC levels at any given time (mapped to the 8 vertical grid divisions) - even though the entire range is available via SCPI. My newest version of RUU (hopefully will post it tomorrow) has a 'Full ADC' switch - to allow seeing the full range.

I own a Agilent DSO1024A scope which is made by Rigol. One frustrating thing when viewing a signal with a large dynamic range (amplitude) was that as soon as a peak jutted out of the viewing window (either the top or bottom) then all the measurements that were impacted suddenly became "*****". So a little "headroom" above and below the displayed window in which measurements could still be taken is a good thing IMO.

The Rigol DS2000 will still measure and display the measurements if >top+25%  and < bot-25% , and what Marmad is proposing is only in his RUU. data utility program that the Display be extended to show the complete waveform , Great Idea 

When part of the trace is outside the extended range the waveform should show clipped as the measurements affected will show ****.

[marmad]

I own a Agilent DSO1024A scope which is made by Rigol. One frustrating thing when viewing a signal with a large dynamic range (amplitude) was that as soon as a peak jutted out of the viewing window (either the top or bottom) then all the measurements that were impacted suddenly became "*****". So a little "headroom" above and below the displayed window in which measurements could still be taken is a good thing IMO.

Sure, on many low-end scopes the moment your waveform goes off the screen above or below, then all the measurements were inaccurate. So I'm guessing that's one of the reasons that they've done it.

[marmad]

Here is a 3D-plot of a frame array (RUU does this now ) using the Rigol 8-division screen size - showing a square wave set to the boundaries of the screen. In the plot, each square represents two screen squares (i.e. 7 x 4 = 14 x 8 on the screen). Note the white streaks at the top - that is where the square is touching the screen top (and thus activating the white color in the CLUT):



Here is the same data plotted again - although this time using the full data set mapped to 10 divisions (7 x 5):

[zibadun]

Here is a 3D-plot of a frame array (RUU does this now ) ]

Man what a great idea to present frames on a 3d plot! 

[marmad]

Man what a great idea to present frames on a 3d plot!

Thanks  - it's what I've been planning with RUU all along. But since the memory read bug, I had to devise a different scheme to get to my goal. Now the software can save, load, plot, and play 'frame arrays':



Here's a 2D plot of frames of a voltage-increasing sine wave - using a black body color lookup table:



Here's the same frames plotted in 3D using a 2-color gradient on the Y-axis (Edit: Note the frame order is reversed in this plot - increasing away from the front plane):

[Hydrawerk]

Although I do not fully understand the pictures, they are cool. You must be a skilled programmer.