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

[marmad]

Hello
There is  a new firmware to Rigol DS2000:
DS2000(DSP)update_00.01.01.00.02.

Thanks, g2!

The bug fixes/changes from new FW#01.01.00.02 are listed as folllows:

1. Optimized  the .csv file accuracy  in DC coupling.
2. Fixed the Uart decoding error when baud rate is 10400.
3. Fixed the crash when math advanced is “CH1==CH2”.
4. Fixed storage and recall waveform error in ROLL mode
5. Fixed trigger delay in 500uV/div
6. Added file name when printing screen
7. Fixed measure error when delete some measure items
8. Fixed trial license lost when do self-calibration
9. Optimized source setting for DS2000-S series

[darrylp]

See picture with a rise time of 1.5 nSec that is 350/1.5  is 233 Mhz,
what is also measured with a signal generator

It is even better. Look at the picture, there rise time is 1.32 ns which gives BW = 350 / 1.32 = 265 MHz.

That's hardly 10% to 90% rise time, more like 15% to 85% which will show a much shorter time and thus calculated bandwidth.
--
 Darryl

[marmad]

Updated the bug list (download links for FW at the bottom of that post):

Struck out bugs #6, #12, and #13 which appear to have been fixed.
Anti-aliasing still does NOT anti-alias.

I haven't tested the RS-232 decoding issue yet. If someone else finds that it's been updated, let me know.


On another note, I love that Rigol continues the confusing reverse downward notation of the final version number digit - hopefully next version will end with .01 or .00 

[EV]

That's hardly 10% to 90% rise time, more like 15% to 85% which will show a much shorter time and thus calculated bandwidth.
--
 Darryl

Are you telling that Rigol calculates the rise time in wrong way?

[EV]

The bug fixes/changes from new FW#01.01.00.02 are listed as folllows:

Looks good, there are not many bugs anymore. I hope there are no new bugs! 
I am not at home now, so I can not test it.

[Harvs]

Is it just me or is the "Project" tab a new one?  I can't remember that being there before, and it's got some weird stuff in it!

[bambam]

I to have the project tab, but have no idea what it's for 

@marmad have you found any changes to security with the new FW, ie have rigol closed the door on down grading FW, DSA9 keys etc with the all the recent revelations lately its got me curious.

[marmad]

Is it just me or is the "Project" tab a new one?  I can't remember that being there before, and it's got some weird stuff in it!

Project tab was always there when you entered F7-F6-F7-Utility key sequence for full version info.

@marmad have you found any changes to security with the new FW, ie have rigol closed the door on down grading FW, DSA9 keys etc with the all the recent revelations lately its got me curious.

I haven't checked any of that - I have official options, etc. so I'll leave it to others to test.

[Chet T16]

Is there issues with playing around with these codes if you have options installed?

[Harvs]

Is it just me or is the "Project" tab a new one?  I can't remember that being there before, and it's got some weird stuff in it!

Project tab was always there when you entered F7-F6-F7-Utility key sequence for full version info.

I see, that's why it popped up.  My bad.

[Harvs]

I to have the project tab, but have no idea what it's for 

@marmad have you found any changes to security with the new FW, ie have rigol closed the door on down grading FW, DSA9 keys etc with the all the recent revelations lately its got me curious.

DSA9 key appears to work exactly as before.

[darrylp]

That's hardly 10% to 90% rise time, more like 15% to 85% which will show a much shorter time and thus calculated bandwidth.
--
 Darryl

Are you telling that Rigol calculates the rise time in wrong way?

Well if those cursors are auto placed, then I would say that's very poor placing.

Anyone else think the same ?


--
 Darryl

[EV]

That's hardly 10% to 90% rise time, more like 15% to 85% which will show a much shorter time and thus calculated bandwidth.
--
 Darryl

Are you telling that Rigol calculates the rise time in wrong way?

There in the picture is rise time from 20% to 80% measured with cursors as 840 ps.

Then rise time from 10% to 90 % can be calculated as Ln(9/1) / Ln(8/2) * 840 ps = 1331 ps = 1.331 ns, which is not far from by Rigol calculated value 1.32 ns.

[EV]

Well if those cursors are auto placed, then I would say that's very poor placing.

Anyone else think the same ?

 Darryl

No, cursors are not placed automatically. They are for rise time from 20%to 80%, which is 840 ps. Look at the table on the upper left corner. Rise time from 10% to 90% is at the under left corner and it is 1.32 ns.

[darrylp]

Ahh yes, too quick looking at the picture and typing a reply. I see the delta x is not the rise time its measuring. Sorry my bad !


--
 Darryl

[Teneyes]

Reporting a Bug
At higher Frequencies
When in AC coupled Trigger mode the Counter does not display the Correct Frequency but the measurement displays correct.

When in DC coupled Trigger, the Counter is correct

[EV]

Reporting a Bug
At higher Frequencies
When in AC coupled Trigger mode the Counter does not display the Correct Frequency but the measurement displays correct.

When in DC coupled Trigger, the Counter is correct

Is this bug with the new FW?

[Wim13]

Mine seems ok mate, I tried it at a few frequencies inc the 20MHz.. Both WITH and without the options mod. Can't go any higher than 20MHz at the moment though



And 20MHz.......




I think AUTO mode has packed-in again too in latest FW (02) 

It is in TRIGGER mode, you tested the AC-DC input, Teneyes mentioned the TRIGGER mode AC/DC

[Wim13]

Reporting a Bug
At higher Frequencies
When in AC coupled Trigger mode the Counter does not display the Correct Frequency but the measurement displays correct.

When in DC coupled Trigger, the Counter is correct

Is this bug with the new FW?

It was also in the older FW, but never discovered...and again for the readers, AC in TRIGGER mode menu

I have the same behavior on my DSO... even worse, get a shake...
See the channel is on DC, the trigger is on AC

[Wim13]

From the Rigol website , the latest FW versions

Here are the latest Firmware versions by Rigol product family as of July 1, 2013:

DS2000 FW-Version: 00.01.01.00.02
DS4000 FW-Version: 00.01.00.00.07
DS6000 FW-Version: 00.01.04
DSA815 FW-Version: 00.01.07
DSA1000 FW-Version: 00.01.16
DG4000 FW-Version: 00.01.06
DG5000 FW-Version: 01.01.08

[gierig]

Big thanks to marmad .

good work on the Updates and infos & Tables and Stuff.

got my DS2102 since few days and for bug hunting and "hey support give me the Updates that i need"
that info was this very helpfuel  (i upgrade just from 60 Year old HP 140A  - 20MHZ )

Just upgrade to 01.01.00.02 and that solve the the bug above #3, #6, very Importet #13 for me.
Nice thing also i got still the 2202 Bandwidth settings as i use the nice DSA9 thing.

[EV]

Big thanks to marmad .

Wellcome to the forum! Have you already found this thread?
https://www.eevblog.com/forum/projects/software-tips-and-tricks-for-rigol-ds200040006000-ultravision-dsos/

[gierig]

Wellcome to the forum! Have you already found this thread?
https://www.eevblog.com/forum/projects/software-tips-and-tricks-for-rigol-ds200040006000-ultravision-dsos/

Thanks.
Yes, that the what i meaning with the Stuff  above. :-)
I use it to take Pictures more then to record, but i don't found any other tool with nearly this functions...

[orbiter]

It is in TRIGGER mode, you tested the AC-DC input, Teneyes mentioned the TRIGGER mode AC/DC

Wim13.. I removed my scope capture images to avoid confusion on the thread. My results were indeed in the trigger mode AC/DC, although
apparently this 'bug' does not show up at the frequencies I was testing at (below 20MHz.)

[poida_pie]

Hi all, just a FYI on the current situation for DS2072 stock here in AUS.
I bought maybe the last DS2072 from Emona yesterday, it arrived today.
I can't fault Emona for service, I would suggest anyone here gives them a go.
They say there is new stock arriving in two weeks.
My model shows:
f/w 00.01.00.00.03
h/w 1.0.1.0.0
with the trails installed as usual.

I would like to say THANK YOU to Marmad for his work in bringing to life a great community of users of this great instrument.