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

[EECrAZY]

successfully updated 1052e to 1102e, rise time went down to < 3ns. HW version 58, downgraded firmware, then hacked, then upgraded to 02.04.01.02 and recalibrated.
Many many thanks to everyone who contributed to this hack

[mvh]

Like many others, I've a good HW ver 58 hack to report. I haven't got anything but a signal generator to measure at the moment, but I haven't seen any adverse effects from the hack. Good stuff!

[velikigrizli]

Hi all!

My scope arrived with this version : 02.04.00.01 HW 57

I did press CH1 twice CH2 Twice and math, and got this version info : Some pages before I read that it may alter flash memory directly? Many people used this method for HW version identification. Does this apply only if you press other button combination, and should I be worried here ?

Anyone here who made above version modification. Usually HW 57 ships with 02.04.00.03

After modification can I upgrade to 02.04.00.03 ?

[Fraser]

velikigrizli,

You can only harm your Rigol configuration if you press other buttons after you have entered the "Ch1/Ch2/Math" information page.
If you just exit the page following the on screen instructions you will be fine.

To the best of my knowledge, the Rigol firmware is backwards compatible so you can use the latest available. I personally would use the version known to work with HW57 which is 02.04.00.03. The later 2.04 SP1 firmware should also work but I have not heard of anyone using it with HW57.

[just]

Hi all!

My scope arrived with this version : 02.04.00.01 HW 57

I did press CH1 twice CH2 Twice and math, and got this version info : Some pages before I read that it may alter flash memory directly? Many people used this method for HW version identification. Does this apply only if you press other button combination, and should I be worried here ?

Anyone here who made above version modification. Usually HW 57 ships with 02.04.00.03

After modification can I upgrade to 02.04.00.03 ?

Only dimlow reported problems entering that mode, but he already had some problems with the serial number before. Maybe there are more hidden menus ...

https://www.eevblog.com/forum/index.php?topic=30.msg3665#msg3665

[velikigrizli]

Hmm, now I have to decide to proceed with hack or not. Currently dont have money for another scope if something goes wrong

So far did anyone reported bricked scope HW 57 using USB hack so far ? what about voltage levels and abolute calbiration levels ? for example voltage source of 10.2V will be 10.2V after hack ? and with same waveform

I did used Ultrascope BEFORE firmware change, and I also used demoIDN on original 02.04 firmware to check firmware version "*IDN?"

After "IDN"  command I closed the program , scope stopped responding, some letters were written in top right side of screen. I turn off , turn on ,it works fine.

Now can this procudure above mess up "original" procedure.

Whne I decide to "hack" I will flash to 02.02 SP2_patched, follow instructions from first page, than flash to 02.04.00.03_original

[Mechatrommer]

Hmm, now I have to decide to proceed with hack or not. Currently dont have money for another scope if something goes wrong

now thats the thought! if i were u, i wont make the hack, unless...
1) be prepared to scrap it if its broken, or bother drieg a call.
2) really in need of 100MHz bandwidth, and be prepared to do the (1)
the feeling of having a good 50MHz scope is alot better than having a 100MHz hacked broken. just from experience

[velikigrizli]

Hmm, now I have to decide to proceed with hack or not. Currently dont have money for another scope if something goes wrong

now thats the thought! if i were u, i wont make the hack, unless...
1) be prepared to scrap it if its broken, or bother drieg a call.
2) really in need of 100MHz bandwidth, and be prepared to do the (1)
the feeling of having a good 50MHz scope is alot better than having a 100MHz hacked broken. just from experience

But man from other thematics can repar the flash rom. reprogram it manually

So ok, so far I will store all this data for future use
what about hardware modification , removing varicap diode ? min software resoluton will be 5nS, but what about actuall rise fall time limit , how much will it change ?

[Mechatrommer]

So ok, so far I will store all this data for future use
what about hardware modification , removing varicap diode ? min software resoluton will be 5nS, but what about actuall rise fall time limit , how much will it change ?

man! you should run the whole pages of this thread and another companion rigol1052e thread. that varicap diode is obsolete, but another way of doing it, physically.

[Fraser]

velikigrizli,

I know exactly where you are in your thoughts about the hack.... I've been there too.

My 2 cents worth.... I had concerns about hacking my scope because it has the  HW58 motherboard and challenging 2.04 SP1 firmware. You are fortunate to have the earlier hardware version but there is always the risk of the scope being corrupted in a firmware flash operation. The common sense rule is that if a firmware is fit for purpose and you cannot afford to brick your scope, don't mess with flash upgrades and hacks.

If you can afford to lose the scope and are adventurous.... go for it ! and enjoy the improved performance. Many users will find the 50MHz+ bandwidth plenty for daily work though. What I am saying is don't mess with your scope if you are happy with it's standard spec performance. You can always hack it later if the NEED arises.

Regarding the hardware mod..... it is well documented in this forum but is not for those unfamiliar with working on pretty small SMD components. You would need to remove an SMD capacitor and this provides the 100MHz+ bandwidth but loses the 20MHz LPF facility in the process. I was about to carry out this modification as I knew that I could both do it and, if necessary, reverse it at a later date without the risk of bricking the scope. For me it was the lowest risk strategy..... until 2.04 SP1 firmware got into the public domain  

At that point I followed the well documented path of many others and, with some trepidation, carried out the firmware downgrade, hacked the scope and then upgraded to 2.04 SP1. All was well and I breathed a sigh of relief. For me it was well worth the effort and risk. I have found no disadvantages to the upgrade hack and calibration remains excellent.

[dimlow]

Only dimlow reported problems entering that mode, but he already had some problems with the serial number before. Maybe there are more hidden menus ...

https://www.eevblog.com/forum/index.php?topic=30.msg3665#msg3665

Ah yes, but I pressed every button! I was curious.

[velikigrizli]

Only dimlow reported problems entering that mode, but he already had some problems with the serial number before. Maybe there are more hidden menus ...

https://www.eevblog.com/forum/index.php?topic=30.msg3665#msg3665

Ah yes, but I pressed every button! I was curious.

lol

and you messed up just serial number ? After that did scope work correctly? And have you managed to hack it to 100mhz version ?

[velikigrizli]

Regarding the hardware mod..... it is well documented in this forum but is not for those unfamiliar with working on pretty small SMD components. You would need to remove an SMD capacitor and this provides the 100MHz+ bandwidth but loses the 20MHz LPF facility in the process. I was about to carry out this modification as I knew that I could both do it and, if necessary, reverse it at a later date without the risk of bricking the scope. For me it was the lowest risk strategy..... until 2.04 SP1 firmware got into the public domain  

So scope has at the imput 20Mhz LPF ? and all "for example sine" signals above that frequency have amplitude drop. But if we remove that filter, what is disadvantage of not having this LPF?
Hardware mod seems much safer, if you don't physically  destroy something it will work fine every time..

what is the reason why currently it is not possible to modify original firmware? For example change what ever you want(for those familiar with programming)

[dimlow]

lol

and you messed up just serial number ? After that did scope work correctly? And have you managed to hack it to 100mhz version ?

Yep Scope still worked, well it was already broken from a previous upgrade, but drieg fixed it and now its 100%

[dimson]

I got ds1052e oscilloscope with firmware 2.05. Is it possible convert it to 100 MHz version?

[Fraser]

Dimson,

2.05 sounds to be a new firmware version so you probably won't get a straight yes or no answer to your question.

You need to check your hardware version to see if it's higher than HW58. If you have HW58 still you should be OK as that is the hardware that I upgraded. My 1052E runs firmware 2.04 SP1 and that is available via this thread if you look back through the messages.
If Rigol have written firmware 2.05 to actively block the hack method you will be stuck and likely unable to carry out the hack until some clever person identifies a work around. That will become obvious if/when you insert the firmware downgrade USB stick. It will either go into firmware change mode or not.

Before carrying out the upgrade, I recommend that you read all of this thread to understand the procedure and risk that you are taking.

The method of checking hardware version is also detailed in this thread.

Good Luck !

[ceut]

I got ds1052e oscilloscope with firmware 2.05. Is it possible convert it to 100 MHz version?

Just after I order mine on DX, the DS1052E has coming out of stock, so I think that now they certainly received new one too.

Which Hardware Revision have you got?

[Helix70]

Hi all, new user here, what a great source of info.

Thanks to everyone involved in creating this guide. I have owned my 1052E for 3 days, now it is an 1102E. It was 2.04Sp1 HW58, downgraded to the patched 2.02SP2, ran shafri's excellent utility, upgraded firmware back to 2.04SP1 and recalibrated. Excellent! I was a little nervous, but it went according to plan. Thanks again guys!

[Fraser]

I haven't heard of anyone bricking their Rigol recently....it looks as though the current upgrade process via USB is a lot more reliable and robust than the early days of hacking the unit. Long may that situation continue. I have to admit that I was very nervous about flashing down to a firmware version that I knew was not 100% compatible with Hardware version 58....but I did as this guide said and all was well ... phew ! As others have advised in the past, there is always a risk of an error during a firmware flash. I would also advise that after downgrading to the FW 2.02SP2, use Shafri's utility and don't 'play' with your scope whilst running this old firmware. i.e. don't do a self calibrate whilst running a possibly incompatible firmware. Return the DSO to it's correct firmware as soon as possible. The risk of unexpected negative consequences due to running old firmware is then limited.

Good luck to all those who choose this upgrade path....... I have not regretted it but have chosen not to go for the 150MHz hack yet.

[Polossatik]

I got ds1052e oscilloscope with firmware 2.05. Is it possible convert it to 100 MHz version?

adapting the "hacked" firmware to downgrade from 2.05 should not be an issue (by this i mean, if it doesn't work it should not brick your scope),
if this is a new hardware revision I would wait until someone can provide the 2.05 firmware (might take a while), so that you can do the hack and go back to 2.05 afterwards
if it's not a new hardware version ( HW58 ), then you can try and go to 2.04Sp1 but of course there is always a risk

[Polossatik]

Here is the 2.02SP2 "hack" firmware patched to appear as 02.08.02.

the MD5 of DS1000EUpdate.RGL is d819839edf239fa98ee8197e8a1c097d
the MD5 of DS1000DUpdate.RGL is 03685177c85d619bea382c154aab2d3a

edit: I get "Your attachment couldn't be saved. This might happen because it took too long to upload or the file is bigger than the server will allow." when trying to attach it, , it's to big i'll upload it somewhere else

Edit2: it's here: http://rapidshare.com/files/430375313/02.02.SP2_patched_to_02.08.02.zip

If someone confirms this works on 2.0.5 scopes, i'll add it to the first page

[dimson]

I checked the version of Hardware, is HW58.
I think we should wait until version 2.05 can be downloaded (in case something goes wrong)

[Fraser]

Dimson,

Please be aware that RigolNA were expecting to have 2.04SP1 for download.... but it has not happened to date and only an older version is on their web site. The 2.04SP1 that is now in the public domain was released to a member of this forum who very kindly shared it with the community (Hero status  ). FW 2.04SP1 was written to meet the revised requirements of the newly released HW58 and did not contain significant updates except for a minor Pictbridge patch. HW58 should operate correctly with 2.04 SP1 but I understand your caution.... few of us can afford to brick our new scope. If anyone decides to take the risk and upgrade a DS1053E that was supplied with FW 2.05, you will know if 2.04 SP1 works as that will be the FW that will have to be reloaded.

[swperk]

Hello all,

I just got my 1052E on Friday. It's h/w version 58 and (unfortunately) f/w version 2.05. No matter what I try, I can't get the scope to recognize that there is a firmware file on the USB stick even when using the 2.02.SP2 firmware file that was altered to appear to be 2.08.02. I assume this means there's some additional file checking going on with the 2.05 firmware. I'm anxiously awaiting a workable solution so I can upgrade my bandwidth!

Regards,
Stan

[Fraser]

Hi Swperk,

Have you tested the USB memory stick to see if the Rigol DS1052E will save waveform files and reload from it?
It has been found that not all USB memory sticks will work with the DS1052E so you may just have an incompatability problem ? It is worth trying another brand of memory stick. I used a really old Sandisk Cruzer 128Mb ....yes 128Mb