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

[korlatos]

Hello,

Has anybody successfully installed and used the CAN decoder option on DS2072 (non-A) with 2.0 HW?

[korlatos]

Thank you for the link, but that is a DS2072A scope. I know that Rigol added CAN decoding and 50 ohm termination to the A model, but the question is whether CAN decoder can be enabled on non-A models with current firmware (03.03.01).

[EV]

Thank you for the link, but that is a DS2072A scope. I know that Rigol added CAN decoding and 50 ohm termination to the A model, but the question is whether CAN decoder can be enabled on non-A models with current firmware (03.03.01).

Yes it can!

[korlatos]

Great - thank you!

[Teneyes]

Here is My DS2072  test with FW 00.03.03.01.00,,
I did have problems with trigger setup at 1st but finally it worked ??

[EV]

korlatos:  is the CAN decoder can be enabled on non-A models with current firmware (03.03.01).

Yes it can!

@EV , Do you have the Rigol CAN test PCB?

Here is My DS2072  test with FW 00.03.03.01.00,,
I did have problems with trigger setup at 1st but finally it worked ??

Yes I have Rigol DS6000 Demo Board. The CAN signal is from it.

[Teneyes]

If  you have a Rigol DG4000 and wish to play with CAN decoding , I have Attached two  ".RAF" files that you can load into the DG4000.  The Arb function has 66bits , so setting the Arb period to 66us, generates a 1 Mb/s data rate.
Then use the Burst function to Space the Burst of CAN messages.
Below I show a 500Kb/s message (period=132us) that is decoded correctly.

then I show  the message with the Burst period set too Small (Fast)  and the DSO does not detect the second message start and there are errors.  I am not sure what the Spec is for CAN message spacing

The Second file is a message with CRC error

[EV]

If  you have a Rigol DG4000 and wish to play with CAN decoding , I have Attached two  ".RAF" files one can load into the DG4000. 

Thanks for the files Teneyes!

[Teneyes]

Known Firmware Bugs/Issues
22) All SCPI commands related to CAN triggering appear to be missing in the latest FW.
[FW v.02.01.00.03 / FW v.03.00.01.03

Just cleaning up old bug report
FW 00.03.03.01.00,   Does appear to Fix this bug in the short testing shown below.
report to Marmad with tests.

[Teneyes]

Known Firmware Bugs/Issues
17) There is a visible offset from center position when using AC-coupled Triggers (including filtered LF and HF) at lower time bases (<= 2us/div), as well as serious jitter with certain settings.
[FW v.01.01.00.02 / FW v.02.01.00.03 / FW v.03.00.01.03]

As most of EEVBLOGers know, that after Dave Jones (#683) got on Rigol's case about AC-triggering , the Bugs were Fixed 

[neslekkim]

My scope is still at 00.02.01.00.03, and I added the hack to get some of the options (the scope is bought as 200mzh so I only added the other options), will I loose these if I upgrade to 00.03.03.01.00 now?
The release notes contained an long list of bugfixes so I guess an update is in order now.

[marmad]

My scope is still at 00.02.01.00.03, and I added the hack to get some of the options (the scope is bought as 200mzh so I only added the other options), will I loose these if I upgrade to 00.03.03.01.00 now?
The release notes contained an long list of bugfixes so I guess an update is in order now.

I have yet to hear of anyone losing any options when upgrading the FW of a DS2000(A).

[TheBay]

I've gone through almost every post on here to find the answer to this...

I have a DS2702 (Non A) I bought it from someone on this forum, it came with the 300mhz option and everything else enabled...
However I wanted to remove all the options and put it back to a DS2702 then do the software update, I used Ultrasigma to send an SCPI command to remove the options.

But although everything has gone to "Trial" Status, my scope is identifying itself as a DS2202? I do now have the latest firmware installed but how can I easily get it back to a DS2702 if I ever sell it or send it for repair?

[JDubU]

I see that there is a new firmware version available for the DS2000 series scopes:

http://beyondmeasure.rigoltech.com/acton/form/1579/0012:d-0001/1/index.htm

...
DS/MSO2000/A/-S:   00.03.03 SP2
...

Has anyone here tried it yet?

[EV]

Can this firmware be loaded somewhere?

[ted572]

Can this firmware be loaded somewhere?

Yes, you can load it on your DS2000/DS2000A.  Hi Hi

Version: 00.03.03.02.06 (00.03.03 SP2)  Date: 2015-06-17
Go to -> http://beyondmeasure.rigoltech.com/acton/fs/blocks/showLandingPage/a/1579/p/p-001a/t/page/fm/0    This will get it for you in Rigol's style!.
Select -> 'DS2000Update.zip' to download it.
This is what it improves on:
1. Added the persistence of XY wave.
2. Added the French language menu. 
3. Supporting the license file installed by U DISK.
4. Supporting the decoder of multi-modules license file.
5. The screen ASC format screen data are not corresponding with the real values.
6. The position of the Cursor is wrong in the saved snap pictures.
7. Improve the stability the LAN interface communication.
8. Fixed the wave stop refreshing in slow scan mode for MSO serials.
9. Memory LA wave data can’t be saved as CSV format.
10. The parallel decoder result can’t align with the Clock position.
11. The outputs of two Source channels are not equal with each other.
12. The Auto operation can’t execute the auto AC settings correctly. 
13. Update the system of SCPI commands. 
14. Modified the result type of“:wav:yor..”.
15. Fixed the data fetching of the decoder.

Edited FW version notes.  I think we can thank 'Teneyes' for reporting many of these issues to Rigol.  Anyway, thank you Rigol. .  .                                            

[EV]

ted572, Thanks for the link! 15 improvements! 

[dadler]

Any guinea pig installed it and confirmed if any installed options are affected?

[orbiter]

Any guinea pig installed it and confirmed if any installed options are affected?

All installed options fine here [emoji1]

[dadler]

I installed the new firmware.

On first boot, browsing the Utility menu with the down arrow caused the entire screen to "bounce" up vertically about 50 pixels, and then back down. It did this twice.

Can't seem to reproduce now, but it was sort of unnerving!

Options still active.

[ted572]

I installed the new firmware.
On first boot, browsing the Utility menu with the down arrow caused the entire screen to "bounce" up vertically about 50 pixels, and then back down. It did this twice.
Options still active.

The installation instructions "Step 9. Special Note for DS2000/DS2000A users:" covers this kind of thing.  In fact you should routinly perform this solution after updating the Firmware in the DS2000/A to clear FRAM. This has been often mentioned here in the past.

I didn't mention that I successfully installed this Firmware update yesterday without issue, because I thought that it would be understood after my describing how to get the update and what it does.

Edit follows below:
Recommendation:  After FW update  ->  1) ''Clear FRAM (by pressing 6th grey button on left side in & out repeatedly during Reboot)*,  2) Restore DEFAULTS*,  3) Perform 'Self-Cal'.  *Ref. Step 9.
Note: When you look at System Info you should see Firmware '00.03.03 SP2'.  For the Full Version Info you should see Firmware '00.03.03.02.06'.

[ted572]

Note: When you look at System Info you should see Firmware '00.03.03 SP2'.  For the Full Version Info you should see Firmware '00.03.03.02.06'.

Reminder: To get the full firmware version info from the DS2000, follow these instructions:
1 Go to the Trigger 'Menu' and set 'Edge' trigger.
2 While keeping the Trigger menu open, you are going to use the 6th and 7th
  (last/bottom) button in the menu buttons on the right-side of LCD as  follows:
3 Press the [Menu7][Menu6][Menu7][Utility] buttons in sequence one after
  another quickly.
4 Then select System, -> System Info.
5 You should see something like this:
     Software version: 00.03.03.02.06
     Hardware version: xxxxx
     FPGA version:
     SPU xxxxx
     WPU xxxxx
     CCU xxxxx
     MCU xxxxx
  If you DON'T see this detailed info, start again, and press those 4 buttons
  faster.
  To escape from this mode, press again [Menu7][Menu6][Menu7][Utility] while
  inside Trigger menu, or reboot the scope.

[dadler]

I installed the new firmware.
On first boot, browsing the Utility menu with the down arrow caused the entire screen to "bounce" up vertically about 50 pixels, and then back down. It did this twice.
Options still active.

The installation instructions "Step 9. Special Note for DS2000/DS2000A users:" covers this kind of thing.  In fact you should routinly perform this solution after updating the Firmware in the DS2000/A to clear FRAM. This has been often mentioned here in the past.

I didn't mention that I successfully installed this Firmware update yesterday without issue, because I thought that it would be understood after my describing how to get the update and what it does.

Edit follows below:
Recommendation:  After FW update  ->  1) ''Clear FRAM (by pressing 6th grey button on left side in & out repeatedly during Reboot)*,  2) Restore DEFAULTS*,  3) Perform 'Self-Cal'.  *Ref. Step 9.
Note: When you look at System Info you should see Firmware '00.03.03 SP2'.  For the Full Version Info you should see Firmware '00.03.03.02.06'.

Thanks for your help.

To be clear, I did in fact follow the exact prescribed procedure in the upgrade guide (including the exact steps you have listed).

However, on visiting the the Utility menu (on first boot post-calibration), the down button twice caused the display to "bounce".

The screen was never scrambled, the parameters were never wrong, and it never occurred again.

I think one of the "bounces" was timed along with the "Lan connected" message, so they may have been related. Might just be a UI quirk.

[Muxr]

hey dadler? was it just a one time glitch? Is everything fine now? I am considering an upgrade as well.

[dadler]

hey dadler? was it just a one time glitch? Is everything fine now? I am considering an upgrade as well.

Just one time and it was immediately after the forced-restart from the self-calibration.

It's been rock solid since, no issues. What I experienced wasn't even an issue, just unexpected.