I tried plugging the scope into my LAN via the Ethernet port but the update utility still does not see it.
I believe the utility did install the VISA driver
I don't know anything about the Ultra Sigma utility... where do I get that?
~ Russ
OK, I found the UltraSigma thing on the Rigol site, and I was able to install it and run it. It appears it is able to see my scope, though I have no idea what to do with it, but at least the scope is inline and apparently recognized.
So, for some reason, the utility seems to be having a problem seeing my scope in spite of it being properly connected.
Any more ideas?
~ Russ
I was finally able to unlock my DS2072A-S, using a hybrid approach. The utility refused to recognize my scope when I plugged it into the USB port, so I completed the rest of the process manually, using the guide found here:
http://gotroot.ca/rigol/D2072A%20Unlocking%20Guide.pdfI elected to go with the 200MHz option, plenty fast for my needs. All options unlocked. Happy camper!
The only problem I have now is that the CH1 vertical position knob does not work. I don't know if that has anything to do with all this firmware hacking or not. I may have to return the scope for service.
~ Russ
I had a similar problem as many others with the SW 03.00.SP1 and HW 2.0 DS2072A, it refuses to load any older firmware while re-flashing the current version works just fine. As I read further on other threads, I came across
https://www.eevblog.com/forum/testgear/rigol-mso2000-series-hacking/ thread and especially the discussion using the SCPI command :SYST:UTIL:READ? to get a memory dump.
I can confirm, the command ":SYST:UTIL:READ? 15441920, 13262848" works perfectly on my MSO 2072 A. The scope is connected via Lan cable.
SW 3.0.SP1
HW 2.2
The rigup.exe tool generates keys in miliseconds.
I used
NCat to get the partial memory dump (address range likely varies between SW versions) from the scope, ran the rigup.exe included in the DS2000A upgrade utility, and it created the keys for my DS2072A. Sent the 200MHz key to scope with netcat again and 200MHz was unlocked. Total time start to finish was under 2 minutes.
echo :SYST:UTIL:READ? 15441920,13262848 | ncat -i 1 SCOPE_ADDRESS_HERE 5555 > DS2072A_sdram.bin
rigup scan DS2072A_sdram.bin > EC-keys.txt
rigup DS2072 DS2072A_sdram.bin > Options.txt
type Options.txt
echo :SYST:OPT:INSTALL A_KEY_FROM_OPTIONS_WITHOUT_DASHES | ncat -i 1 SCOPE_ADDRESS_HERE 5555
--A
I used NCat to get the partial memory dump (address range likely varies between SW versions) from the scope, ran the rigup.exe included in the DS2000A upgrade utility, and it created the keys for my DS2072A. Sent the 200MHz key to scope with netcat again and 200MHz was unlocked. Total time start to finish was under 2 minutes.
echo :SYST:UTIL:READ? 15441920,13262848 | ncat -i 1 SCOPE_ADDRESS_HERE 5555 > DS2072A_sdram.bin
rigup scan DS2072A_sdram.bin > EC-keys.txt
rigup DS2072 DS2072A_sdram.bin > Options.txt
type Options.txt
echo :SYST:OPT:INSTALL A_KEY_FROM_OPTIONS_WITHOUT_DASHES | ncat -i 1 SCOPE_ADDRESS_HERE 5555
--A
I can confirm the above worked for me as well. I also had the same version/model, and the scope just would not upgrade from the USB stick to the key dump firmware, but this method using ncat worked.
Dear all,
Just received my brand new toy, MSO2072A. Unboxed it and connected it to the LAN, said the magic word ("xyzzy" for those who remember...) and turned it 5 minutes later into an MSO2302A.
Thanks to all of you guys, you're great!
@Jog
Just enter the keys from the front panel.
Forum member Zombie28 had posted a link to the firmware file DS2000Update.GEL in thread "sniffing-the-rigol's-internal-i2c-bus". I tried downloading that file but was met with the message "the file you are trying to download is no longer available". I found a zipfile named DS2000UpdateGEL.exe on the net but when unzipped, it did not contain a file with the "GEL" extension.
Can anyone tell me where I may find the latest DS2000Update.GEL file that allows me to recover the Rigol DS2072A system keys without needing to open up the unit for a memory dump (thereby voiding the warranty)? I really need the higher bandwidth but do not have the cash to shell out for a new o'scope.
Thanks for the help. This thread rocks!
If you read 4 post above yours, you will see something interresting..
You don't need to take apart your scope and void your warranty..
I have the DS2072A with SW 00.03.00.SP1 and HW 2.0 and have setup a number of Windows machines to try using DS2000A_Upgrade_Utility_1_0_0_1_Installer.exe to upgrade it. The Upgrade Utility seems to perform as described but when I boot the scope into update mode and insert the USB drive the CH1 light doesn't blink, instead all light turn on and stay on. I have tried 4 different USB drives varying in size from 1 to 32Gb.
They all behave the same.
I have therefore concluded that the combination of SW and FW is such that I must adopt an alternative method.
The next approach planned is to us the SCPI Method described elsewhere.
What I can't find is the "rigup.exe" file mentioned. I assumed it was installed from within "DS2000A_Upgrade_Utility_1_0_0_1_Installer.exe" but a search doesn't find it, I am running Win 7 Ultimate SP1.
Can someone please advise where I might find that file please so I can try the SCPI method ?
SW 3.0.SP1
HW 2.2
The rigup.exe tool generates keys in miliseconds.
This worked perfectly for me on HW 2.0 and the latest FW. Thanks!
Here: http://gotroot.ca/rigol/
BTW, just for clarity, that repository does not contain the latest version of the DS2000A firmware: #03.01.00.04. As of now, it's downloadable here.
Mirrored now
. I haven't been keeping up on developments on this lately, apologies.
apologies.
That seemed odd. Then I noticed your country flag. Rock on, friendly Canadian.
Dear all,
Just received my brand new toy, MSO2072A. Unboxed it and connected it to the LAN, said the magic word ("xyzzy" for those who remember...) and turned it 5 minutes later into an MSO2302A.
Thanks to all of you guys, you're great!
You had to plugh it in first, right?
Now in the correct thread,
Haven't used windows for over 10 years and having a few problems, can anyone please help me by advising what format I should be saving the SCPI dump in, should it be ASCII, byte-8bit, byte-16bit or byte-32bit.
When I rigup the file it says no keys. perhaps I need to hit the Advanced Tab in Current Return Value screen or something as not matter what file I save they are either 8 or 16 kb, not the 32 Mb file I am expecting. I have tried the scan with both 1,133554432 and 1544190,13262848.
Help will be greatly appreciated as have spend a couple of days on this now and getting very frustrated. Sorry should have mention scope is a DS2072A with 03.01.00.04 and HW 1.02.0.2 Manufactured August 2014.
Now in the correct thread,
Haven't used windows for over 10 years and having a few problems, can anyone please help me by advising what format I should be saving the SCPI dump in, should it be ASCII, byte-8bit, byte-16bit or byte-32bit.
When I rigup the file it says no keys. perhaps I need to hit the Advanced Tab in Current Return Value screen or something as not matter what file I save they are either 8 or 16 kb, not the 32 Mb file I am expecting. I have tried the scan with both 1,133554432 and 1544190,13262848.
Help will be greatly appreciated as have spend a couple of days on this now and getting very frustrated. Sorry should have mention scope is a DS2072A with 03.01.00.04 and HW 1.02.0.2 Manufactured August 2014.
I am pretty sure that rigup expects the SCPI dump in binary (i.e., 8-bit binary data to which any hex dump you did needs to be converted).
Thank you SharpEars, it transpires that I was approaching this all wrong by using usb and the rigol SCPI tool. By converting over to LAN and then using the 3rd party SCPI tool under native OSX it saved the magic 32mb file and the rest is history.
Yes that's what I used and mine is just a few weeks old.
Above posted firmware 03.01.00.04. BRICKED my scope. Be very careful!! It froze during firmware update and now just shows Rigol screen upon turn on. I can't believe it.
*EDIT* seems to be something to do with the stick's file system as reformatting the USB stick worked.
Above posted firmware 03.01.00.04. BRICKED my scope. Be very careful!! It froze during firmware update and now just shows Rigol screen upon turn on. I can't believe it. A thousand dollars down the drain
I didn't experienced that.
You'd better check your USB stick first, then flash your scope in bootloader mode. Also, since I don't know what the previous firmware version your scope was running, a reset (left vertical 6th key at boot time) should be helpful.
Cheers.
Reset with rapidly pressing 6th button after turn on does nothing. It shows Rigol and some buttons are lit up and that's it, it stays like that until turned off. This is the same stick I used to unlock the scope so I am sure it works.
What do you mean bootloader mode? Ah you mean double-click help button. I will give that a try.
Reset with rapidly pressing 6th button after turn on does nothing. It shows Rigol and some buttons are lit up and that's it, it stays like that until turned off. This is the same stick I used to unlock the scope so I am sure it works.
What do you mean bootloader mode?
Ton enter in the bootloader mode, quickly press "help" button at boot time (you probably have to retry few time to get into). Once you are (the scope stays black screen), plus the USB stick, wait till all buttons backlight turns on, reboot.
Cheers.