changing the rigol DS1052E to DS1102E using USB , the dummy guide

[tsaavik]

says DS1102E on it

Your right, I posted the wrong link: http://www.rigolna.com/products/digital-oscilloscopes/ds1000e/ds1052e/
Check it out, that's a DS1052e with a 100MHZ sticker. I updated my previous post.

[cs.dk]

Check it out, that's a DS1052e with a 100MHZ sticker. I updated my previous post.

Just in case, that Rigol "forgots"

[killerwhale]

Hi, guys!
So, here's my (though somewhat belated) Christmas present to all you 2.05-FW scope owners.  It is at last possible to downgrade it! The procedure is the same as described in the beginning of the thread, except you should use the attached file instead of the 2.02 SP2 found elsewhere in the forum.
It should work with 2.05 but not with 2.05 SP1 (if there are any of you that have that firmware already).
I did it on my own scope and haven't found any glitches after the "upgrade."
Enjoy! 

[ultrasounder]

Bravo!. That is a "killer" hack, killerwhale. I have a 02.05F/W, 58 H/W version. I was wondering what F/W version this patch of yours would downgrade my scope to? Also, were you able to verify that you can actually verify that the hack worked by measuring the rise time/fall time. Awaiting your confirmation with bated breath!

[Gallymimus]

Just got mine today from Saelig.com, they give a free bag and 5% discount if you mention the president Alan Lowne.

HW ver 58, firmware 2.04!

hack worked fine (did not verify rise time or anything yet though).

[killerwhale]

@ultrasounder:
The hack downgrades to 2.02 SP2, which I think is the least common denominator to be able to change the model number. After doing that, I upgraded to 2.04 SP1 as per the present guide. Actually, afterwards I went ahead and upgraded it to 2.05 (though I would not necessarily advise it).
I didn't measure rise times, but the timebase goes down to 2 ns now.

P.S. You may downgrade it to whatever version you want by taking the first 21 bytes from the attached file and overwriting the header of the file you intend to downgrade to.

[Fraser]

Hi Killerwhale,

Nice hack on the header :-) My DSO was 2.04SP1 upgraded some time ago to 100MHz so I was already OK, but I know the owners of FW2.05 scopes will be very pleased with your work. You mention FW2.05 being reloaded on your scope. Are you able to make that FW available for those who wish to reload it after upgrade ?

Cheers ! :-)

[ultrasounder]

Congrats!. I am at work right now so, I just cant wait to go try it on my scope when i get back home today. How were you able to upgrade to 02.05 from 02.04 SP1.? I dont see the 02.05 firmware out on their website. Btw, there isnt a big difference between 02.04 SP1 and 02.05(anecdotal infromation from RigolNA rep-Houssam).

Thanks for your good work. I will keep you posted once i am sucessful the quest.

[Polossatik]

cool,
can someone with a 2.05 (no SP1) system (before trying to downgrade please ) provide me with
1) a screen shot of the version info of the scope (optional, but would be nice)
2) the full version string ( you can use shafry's tool for that. should be somthing like 02.05.00.02 or so

i'll the rewrite/update the guide (need to rewrite it anyway, looks it's getting confusing)


Edit: random nonexisting bonus points for somone who can figure out what mapping is used to make from the string " 02.05.01.00 " (= 30 32 2E 30 35 2E 30 31 2E 30 30 in hex) - or something similar like 02050100 - the 11 bytes result " 82 85 84 88 C3 7B 47 92 39 C8 7E "

Btw, there isnt a big difference between 02.04 SP1 and 02.05(anecdotal infromation from RigolNA rep-Houssam).

I don't have a change log , but a quick look in winMerge shows quite some diff between 02.05.01.00 and 02.04.01.02 , I would say more then between 02.04.01.02 and 02.04.00.03

[killerwhale]

Hi, Aurora. Here's the 02.05 SP1 (00.02.05.01.00) file for those who need it.

[silent3xe]

Thanks KillerWhale.

The 2.05 downgrade, mod,  and 2.05 SP1 upgrade worked on my HW58 2.05 DS1052E. I followed the guide on the first page using your files and shafri's program and everything went flawlessly.

[killerwhale]

Great! Good to hear from someone else who succeeded!  

[ultrasounder]

Kudos to KillerWhale! I just got done with the hack myself. That was the longest 20 minutes of my life. Thank you so very much for everyone in this thread/forum for sharing the tribal knowledge and the secret sauce. Using Shafri's tool makes the 1102E upgrade a breeze. Decided to stay at 02.04 SP1 released by d0ss  until more information is available on the 02.05. Intend to perform a full-up compare with the TDS 100 MHz at work tomorrow.

Great job guys!.

[twilliams]

So, here's my (though somewhat belated) Christmas present to all you 2.05-FW scope owners.   It is at last possible to downgrade it!

This is GREAT news since my new scope that came from Deal Excel on Xmas eve has 2.05. I want to make sure I have all the steps right since their have been some changes to the original instructions.

1. Install hash calc, VISA drivers and Ultrascope. Verify that ultra scope can see the unmodified scope.
2. Downgrade the scope with this new 2.05 downgrade file. Does the MD hash still equal the one in the guide on page 1?
3. Use usbtool OR Shafri's tool to make the changes to the scope.
4. Upgrade the scope back to 02.04 SP1 using the version posted by d0ss.

Are these essentially the right steps?

[irsirius]

I can also confirm that killerwales downgrade file works fine.
Same procedure as described by silent3X: The 2.05 downgrade, mod,  and 2.05 SP1.
The mod was 2 mouseclicks thanks to shafri's tool.

2. Downgrade the scope with this new 2.05 downgrade file. Does the MD hash still equal the one in the guide on page 1?

I don't think the file will have the same checksum.
The MD5-hash of the downgrade file is "1fa740d1e2914651d96b96f9ff01dfc6" (it worked with this file).

Thanks everyone for you efford. I received my DS1052E yesterday and was a little disappointed that the is "no way"
to mod FW2.05. Fortunately just 2 hours later the situation had changed 

[ultrasounder]

Looks like the floodgates have just opened. Thanks to the combined efforts of all the hacker supremos we have on this discussion board.a word of caution for those who bought the ds1052E on DX, according to RigolNA, DX is not an authorized distro. So, the scope is not covered under their "1 year" Mfr warranty.

@twilliams follow the extensive guide by polossatik on page 1. For the upgrade path you could either use the 02.04Sp1 by d0ss(which is what i did) or you could use the latest 02.05Sp1 posted by killerwhale yesterday.

[killerwhale]

As for me, I've never even considered this manufacturer's warranty as a viable option should the scope fail. The price being what it is and shipping insured to China representing a considerable portion of the purchase price... Well, you get what you pay for, after all.

[Bored@Work]

according to RigolNA, DX is not an authorized distro. So, the scope is not covered under their "1 year" Mfr warranty.

That isn't new for Rigol. They like to threaten customers who are not buying from the "right" sources with bad things. At one point they were even claiming oscilloscopes not bought from the "right" sources could be fake. Threatening customers is IMHO a rather stupid, braindead concept, but Rigol apparently thinks it works.

I always find it funny when Rigol on the other hand behaves as if they play in the same league as Tektronix, Agilent or LeCroy.  Hey, just because you build some boxes for Agilent doesn't mean you are Agilent. Especially not if your "support" is such a joke.

[twilliams]

Another successful 2.05 100mhz hack!.

Took all of about 10 minutes.

[accepttheownage]

I've downgraded my 2.05 and upgraded back to 2.05 SP1, but I'm having the following issue:
When I set the trigger slope to rise and fall and the oscilloscope triggers it locks up and I have to switch it off and on to get it to work again. Can anyone verify this behavior to see if it's a firmware issue?

NOTE: Before trying this set your sweep to SINGLE and hit FORCE sweep to test it out. DO NOT set the trigger to AUTO or it will lock up immediately and every time on startup, making it very hard to recover from this problem!

[twilliams]

I've downgraded my 2.05 and upgraded back to 2.05 SP1, but I'm having the following issue:
When I set the trigger slope to rise and fall and the oscilloscope triggers it locks up and I have to switch it off and on to get it to work again. Can anyone verify this behavior to see if it's a firmware issue?

NOTE: Before trying this set your sweep to SINGLE and hit FORCE sweep to test it out. DO NOT set the trigger to AUTO or it will lock up immediately and every time on startup, making it very hard to recover from this problem!

I just tested this and it seems to work for me. I did not however do the 2.05sp1 update I stayed with the 2.04sp1.

[accepttheownage]

Is there any way I can downgrade from 2.05 SP1 or am I stuck with it? 
I'm wondering if it's a firmware issue or if it's related to the hack 

[killerwhale]

@accepttheownage:
I've just checked and I confirm that I have the same issue as you describe.

@all:

Until we find out more about the problem, DO NOT upgrade to 2.05 SP1, remain with 2.04 SP1!

[dendennis]

Darn it ... I'm in the same boat, literally minutes after installing 2.05 sp1 I see this 
Never mind I'm sure someone will crack it. 
Out of interest how exactly was the downgrade from 2.05 (non-sp1) resolved?
was it simply a matter of replacing the header ?

Keep up the good work guys

[Fraser]

Sadly there is the ugly possibility that 2.05SP1 is a modified firmware to suit a later revision of hardware as occurred with 2.04/2.04SP1.

Has anyone tried reinstalling the firmware to see if the header still triggers the update process. I would normally expect it to be possible to load 2.05SP1 over 2.05SP1 as a firmware corruption fix but that isn't to say Rigol think the same. If it is possible then using the latest modified FW2.02SP2 should still work ? You could then intstall 2.04SP1. I believe Killerwhale indicated that this was not possible though so forgive me if I am giving false hope.

As another option I would try incrementing the Hex values on the 2.05SP1 header to see if it can trigger the "new FW revision" Routine. I note that the HEX header no longer translates to ASCII for the revision no. It could just be a HEX/Binary value now or how about Chinese non ASCII characters ?