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

[cicastol]

I don't understand much of your calculation...

+1

To my knowledge bw=0.35:Tr 

http://www.tek.com/Measurement/scopes/selection/risetime.html
http://www.i9t.net/fast-pulse/fast-pulse.html

[reqwired]

I bring a present to all HW ver 58 owners firmware version 02.04.01.02 (2.04 SP1). I've attached the firmware below and confirm it fixes the noise issue after self-calibration.

Firmware attached, confirmed to work with HW 58 scope can't say much else.

EDIT:

Hashes for DS1000EUpdate.RGL

CRC3: 3B44DEE5
MD5: BCF73565352391935F3A9651D30776EE
SHA-1: B2DDB481F8A71CF7037C93AF9C45CEBBE97C71A2

When I download the file then check with Hashcalc I get different numbers. I've read the past history and downloaded and checked the other firmware files with Hashcalc and gotten matching numbers. I'm just clicking the the link to download ,am I missing a step, or ??  Suggestions?   Thanks

[d0ss]

I bring a present to all HW ver 58 owners firmware version 02.04.01.02 (2.04 SP1). I've attached the firmware below and confirm it fixes the noise issue after self-calibration.

Firmware attached, confirmed to work with HW 58 scope can't say much else.

EDIT:

Hashes for DS1000EUpdate.RGL

CRC3: 3B44DEE5
MD5: BCF73565352391935F3A9651D30776EE
SHA-1: B2DDB481F8A71CF7037C93AF9C45CEBBE97C71A2

When I download the file then check with Hashcalc I get different numbers. I've read the past history and downloaded and checked the other firmware files with Hashcalc and gotten matching numbers. I'm just clicking the the link to download ,am I missing a step, or ??  Suggestions?   Thanks

I've just downloaded and checked the file has the correct hashes, my only guess is that you calculating the hash for the 7zip file.

The file needs extracting first, I recommend 7-zip http://www.7-zip.org/.

Hashes for the 204SP1.7z are as follows;

CRC32: EAE60568
MD5: DC5DF0AF15431465C945353BC1EA830E
SHA-1: 88A31204DAA1A62B27C2DB6CAF3397B5ECC90958

[M84AB1]

I bring a present to all HW ver 58 owners firmware version 02.04.01.02 (2.04 SP1). I've attached the firmware below and confirm it fixes the noise issue after self-calibration.

Firmware attached, confirmed to work with HW 58 scope can't say much else.

EDIT:

Hashes for DS1000EUpdate.RGL

CRC3: 3B44DEE5
MD5: BCF73565352391935F3A9651D30776EE
SHA-1: B2DDB481F8A71CF7037C93AF9C45CEBBE97C71A2

When I download the file then check with Hashcalc I get different numbers. I've read the past history and downloaded and checked the other firmware files with Hashcalc and gotten matching numbers. I'm just clicking the the link to download ,am I missing a step, or ??  Suggestions?   Thanks

I have already successfully hacked my scope with that firmware file (DS1000EUpdate.RGL) and when I read your post I went again to double check the file and it indeed showed different numbers. I then closed hashcalc, reloaded the firmware and then it was showing the correct numbers. I have now closed and reloaded the same firmware file that I used for the hack about 10-20 times and the numbers always match. I am curious why that one time the numbers didn't match. Maybe a glitch in the hashcalc software?

[reqwired]

The file needs extracting first, I recommend 7-zip http://www.7-zip.org/.

Hashes for the 204SP1.7z are as follows;

CRC32: EAE60568
MD5: DC5DF0AF15431465C945353BC1EA830E
SHA-1: 88A31204DAA1A62B27C2DB6CAF3397B5ECC90958

Thats got to be where I messed up, these are the same hash numbers I'm getting.  Thanks,Thanks

[EricF]

Thanks people, another successful upgrade of a hardware 58 model with 2.04SP1 due to the help from this thread. Just received it yesterday from Riko instruments via Amazon. Downgraded to 2.02SP2_patched and then used shafri's program. Upgraded back to 2.04SP1. Process was a piece of cake, took about 30 minutes only because I was extremely methodical and anal about the whole thing. Really appreciate it, and highly recommend it to anyone considering it.

Thanks again!

EricF

[teixeluis]

Just to confirm that I have a scope originally shipped with firmware 2.02 SP2 (probably hacked by the supplier - dealextreme) and having serial Nr DS1ED12391xxxx, here is a photo from its back, and a photo from the SMPS which apparently doesn't have the HV supply (did the best I could to shoot it through the 3 mm hole).

lteixeira

[Zyvek]

Another successful upgrade, I received mine just yesterday from Amazon/Riko_Instruments

Firmware was 2.04 and HW=57.  SNDS1ED122XXXXXX

The Rigol wont fully replace my Tektronix 2467B, but I think it may allow me to retire the Tek2430A.

I only have a 50Mhz pulse generator (Philips PM5715) so more testing is in order..

Thanks for the info, this is fun stuff!

[akisnas]

Hi everybode, i'm trying to download this
DS1052_to_DS1102.zip : the DS1052_to_DS1102.zip is available here on Rapidshare (9Mb)
but without success can anyone help me?
"Rapidshare server is full of quotes"
I 've found the FW VERSION 00.02.04.01.02
Rigol Technologies,DS1052E,DS1ED123xxxxx,00.02.04.01.02
How to find the HW version of the scope?
Kind Regards
 

[eldis]

Hi, I also recently bought DS1052E with firmware 2.05
Seller says, that 2.04 is discontinued. Any progress with modifying this firmware release?
Is there anything I can do to help? perhaps some JTAG dump.. HW is 58

[Polossatik]

Tested the zip file, works fine, must be rapidshare overload or so.

Added to the first post
* warning that currently 02.05 scopes cannot be hacked
* the way to see your HW version with a nice big fat warning to not mess around.

[reqwired]

Hi everybode, i'm trying to download this
DS1052_to_DS1102.zip : the DS1052_to_DS1102.zip is available here on Rapidshare (9Mb)
but without success can anyone help me?

I had trouble with the zip file also, I was using older web browser,after I installed firefox and had high speed access it downloaded fine.   Just a thought.

[akisnas]

My scope is updated, wow nice, sweet success.
Oh yes the radip server was very busy.
Very nice tutorial for dummies
Thanks for all.
Kind Regards

[M84AB1]

Added to the first post
* warning that currently 02.05 scopes cannot be hacked

But didn't one of the forum users report that whilst his firmware was 02.05, the HW was actually 58. By now, we know that HW 58 scopes also came with FW 2.04 SP1 (like mine). So why cant 02.05 downgrade to 2.02 SP2, perform the hack and then upgrade to 2.04 SP1 instead of 2.05?

Unless I missed something along the lines that there is no "patched" FW to make the scope think it is higher and prompt the downgrade?

[Fraser]

From what I have read here, it would appear that Rigol have changed the way in which the DS1052E recognises a valid firmware update package. The old method was easily fooled by changing the version number in the update package header. That technique no longer appears to work on FW2.05. The missing knowledge at the moment is how to get the DS1052E into firware update mode in order to accept 2.02SP2. I agree that FW2.05 scopes with HW58 should accept FW2.04SP1 but only after the above problem has been solved.

[accepttheownage]

Added to the first post
* warning that currently 02.05 scopes cannot be hacked

But didn't one of the forum users report that whilst his firmware was 02.05, the HW was actually 58. By now, we know that HW 58 scopes also came with FW 2.04 SP1 (like mine). So why cant 02.05 downgrade to 2.02 SP2, perform the hack and then upgrade to 2.04 SP1 instead of 2.05?

Unless I missed something along the lines that there is no "patched" FW to make the scope think it is higher and prompt the downgrade?

My 02.05 scope will not recognize any of the older hacked firmware. Either we somehow dump the new firmware, find out what the scope is looking for in the firmware, or wait until Rigol releases the new firmware, which probably won't happen

[AgeyevAV Russia]

Good time of the day What hear version HW if firmware 02.05 &

[Zyvek]

After the hack don't forget to upgrade your probes as well.

When comparing the upgraded Rigol to a bunch of older Tektronix scopes (2236, 2340A, 2445 & 2467B) I noticed a bit more detail using a Tex P6138 vs the included Rigol probes:

The 2467B image is just for reference.

[Fraser]

When comparing the upgraded Rigol to a bunch of older Tektronix scopes (2236, 2340A, 2445 & 2467B) I noticed a bit more detail using a Tex P6138 vs the included Rigol probes:

Can you clarify which Rigol probes you received with your scope please. Mine were RP2200's that claim to be 200MHz bandwidth.

Cheers

[teixeluis]

Mine were RP2200's that claim to be 200MHz bandwidth.

According to the datasheet from my RP2200, these are rated to 150 MHz at 10 x attenuation.

lteixeira

[Mechatrommer]

After the hack don't forget to upgrade your probes as well.
When comparing the upgraded Rigol to a bunch of older Tektronix scopes (2236, 2340A, 2445 & 2467B) I noticed a bit more detail using a Tex P6138 vs the included Rigol probes:

good info! new aspect to tinker.

[Fraser]

Mine were RP2200's that claim to be 200MHz bandwidth.

According to the datasheet from my RP2200, these are rated to 150 MHz at 10 x attenuation.

Interesting.... it appears that even rigol don't know the specification of their RP2200 probes. They are advertised as 150MHz or 200MHz bandwidth depending upon where you buy. A Google search on Rigol RP2200 can make for confusing reading 

Take a look here:
http://www.aidetek.com/New_products_info/Photo/RIGOL/RP2200_Manual.pdf

YET in the Rigol Catalogue (Page 6) they are clearly shown as 150MHz. The 200MHz spec may just be an error but this doesn't inspire much confidence in the specs.

http://www.rlx.sk/pdf/RIGOL2010No3.pdf

[teixeluis]

Yes. Here is the spec of my RP2200.

[Zyvek]

When comparing the upgraded Rigol to a bunch of older Tektronix scopes (2236, 2340A, 2445 & 2467B) I noticed a bit more detail using a Tex P6138 vs the included Rigol probes:

Can you clarify which Rigol probes you received with your scope please. Mine were RP2200's that claim to be 200MHz bandwidth.

Cheers

Sure thing, they are the RP2200 model.

[teixeluis]

One interesting feature in a custom firmware would be to allow direct selection of the bandwidth limit from the same CHx > BW Limit command. Instead of just enabling the 20 MHz filter, one could switch between the several hardware filters: 20 MHz, 50 MHz, 100 MHz or the entire 150 MHz vertical BW (if it is in fact the true maximum BW).

lteixeira