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

[killerwhale]

Hi, Aurora

Has anyone tried reinstalling the firmware to see if the header still triggers the update process.

I have: No go.

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.

Did that too: No go.
It seems to me that the first four bytes encode the version and the following bytes are some kind of hash. And you probably have to have both sides correct before update triggers.

[twilliams]

Ok so I reported earlier that I had successfully downgraded my FW 2.05 HWv58 applies the hack and then back to 2.04sp1 as supplied by d0ss.

I MAY have just discovered an issue. With no probes connected I get a fairly straight trace line all the way down to 20mv. With a probe connected I get a considerable amount of "noise" on the trace with no input signal. I have calibrated (several times) and even tried my other probe. Same thing happens on both channels. Is this the "calibration" problem a few were having with older FW's on HW58's? If so I thought the 2.04sp1 fixed it.

I can connect to the calibration terminal and get a good 3v p-p 1khz signal. I also connected a function generator and sent various waveforms with good results.

[Mechatrommer]

@twilliams: sounds normal to me, just a normal external noise problem. sometime i have that too. but you could explain your problem in more detail, probably with pictures?

[twilliams]

Ok so here is what I am seeing after the 2.05 downgrade and back to 2.04 sp1 with HWv58.

Here is the calibration tab off the front of the scope, looks good.


Here is no probe attached at 20mv, little bit of noise but mostly ok


Here is a probe attached at 20mv, what the heck is that? Is it normal?

[killerwhale]

This is normal. If you unzoom it (timebase, I mean), I bet the fundamental frequency would be 50/60 Hz depending on the country you are in.

[twilliams]

This is normal. If you unzoom it (timebase, I mean), I bet the fundamental frequency would be 50/60 Hz depending on the country you are in.

Thanks, that's a huge relief. I thought I had broken my less than a week old scope.

When I zoom all the way out I get 62.5hz as the freq and since I live in the U.S. your theory was correct.

Thanks for listening 

[Mechatrommer]

Ok so here is what I am seeing after the 2.05 downgrade and back to 2.04 sp1 with HWv58.

looks like "Peak Detect Acquisition" is activated.

[zesty]

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).

So is this (Saelig.com) one of the better locations in the US to order an upgradeable o-scope?

I see other vendors mentioned, but trying to get the best odds of being able to change the firmware.

Scott

 

[zenith1111]

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!

Hi, I've bought a ds1052e a couple of weeks ago, it came with FW2.05. I'm glad there is a method to downgrade these, I was afraid to mess around with mine (I have a warranty:P).

I've just registered to report that, with the original firmware, my unit hangs when the trigger is set to rise and fall. It is NOT because of this mod, it is a bug in 2.05 FW. After I choose rise and fall and it crashes, it hangs everytime I restart the unit, to get out of this loop I have to press the "AUTO" button on startup a couple times until it changes back to rise.

I never did any mod, it is completely stock, any more bugs in modified units to check if it also happens on stock ones?

[Bored@Work]

So with FW20.5 you get two things for the price of one, a broken trigger and more trouble hacking it. Indeed, typical Rigol.

[torch]

First of all, let me add my thanks to all the innovators that have been doggedly pursuing this hack.

I've been following this for a few weeks now, was finally about to buy one when FW 2.05 appeared and now that it's cracked I figure I better pull the trigger.

Is there actually any end-user advantage to the later firmware releases? Bug fixes? Calibration? It sounds like there's no reason to go beyond 1.04 SP1 after the downgrade from 2.05.

[killerwhale]

I haven't heard yet of any advantage of using anything higher than the 2.04 SP1 firmware on HW 58 scopes. Plus to that, 2.05 and 2.05 SP1 have that nasty trigger bug.

[xoom]

Im still with 2.02 SP2 and don't see point to go higher FW version.. is any critical differences in 2.02 SP2 and 2.04 FW?

Regards.

[fenyvesi]

FW 2.05 HWv58 : Success.

Thanks for all the clever and helpful guys who helped all of us to transfer our scopes.

[killerwhale]

@xoom:
2.04 SP1 = support for HW 58. That's my understanding.

[Fraser]

According to RigolNA FW2.04SP1 has some minor changes over FW2.04 (non SP1)  for 'housekeeping' and some minor enhancement to the PicBridge functionality.

It was also stated by RigolNA that no major changes in firmware or functionality were expected.

I suppose the old addage, 'if it ain't broke, don't fix it' applies  


 

[Mechatrommer]

getting the latest firmware (esp without knowing exactly what it does/fix for good) is a... software paradigm. the latest 2.05 FW is meant for... new eevbloggers i think. so we can keep busy... blogging.

[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!

Hi, I've bought a ds1052e a couple of weeks ago, it came with FW2.05. I'm glad there is a method to downgrade these, I was afraid to mess around with mine (I have a warranty:P).

I've just registered to report that, with the original firmware, my unit hangs when the trigger is set to rise and fall. It is NOT because of this mod, it is a bug in 2.05 FW. After I choose rise and fall and it crashes, it hangs everytime I restart the unit, to get out of this loop I have to press the "AUTO" button on startup a couple times until it changes back to rise.

I never did any mod, it is completely stock, any more bugs in modified units to check if it also happens on stock ones?

Thanks for sharing. Makes me feel better knowing it's not an issue with the modded firmware, but an issue with 2.05 firmware instead. Sounds like we need to all get onto Rigol about this so that it'll be fixed in a new FW.

[gnail]

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!

Hi, I've bought a ds1052e a couple of weeks ago, it came with FW2.05. I'm glad there is a method to downgrade these, I was afraid to mess around with mine (I have a warranty:P).

I've just registered to report that, with the original firmware, my unit hangs when the trigger is set to rise and fall. It is NOT because of this mod, it is a bug in 2.05 FW. After I choose rise and fall and it crashes, it hangs everytime I restart the unit, to get out of this loop I have to press the "AUTO" button on startup a couple times until it changes back to rise.

I never did any mod, it is completely stock, any more bugs in modified units to check if it also happens on stock ones?

I also have a stock DS1052E with FW2.05 and I cannot reproduce this lockup. Mine's perfectly happy if I set trigger to rise and fall (the up and down arrow).

[gandalfg8]

I also have a stock DS1052E with FW2.05 and I cannot reproduce this lockup. Mine's perfectly happy if I set trigger to rise and fall (the up and down arrow).

That's exactly what I've experienced, again with a stock DS1052E with FW2.05
The rise and fall triggering works fine for me and I'm able to display alternating measurements of the rise and fall times of the calibration square wave, for example, with no problem.
If I switch the scope off and on again with the signal still attached it just goes back to where it left off.
If I switch back on without the signal attached it just waits in rise/fall mode and starts again as soon as the signal is reapplied.
What I have observed is that after setting this up for either CH1 or CH2, and then switching to the other channel, all I get on the other channel is noise, with or without the cal signal applied, and I have to press the AUTO button to restore a usable trace, at which point I can set up the new channel in the same way if I so choose.
I've certainly not experienced anything that I would describe as a "crash" and as far as I can tell FW2.04SP1 behaves in the same way.

More specific details of the observed problem would be appreciated.

[killerwhale]

@gnail, gandalfg8: What's your hardware revision number? Is it HW 58?

@zenith1111: Are you sure your unit didn't come with 2.05 SP1 instead of 2.05? What is your HW revision BTW?

[gnail]

@gnail, gandalfg8: What's your hardware revision number? Is it HW 58?

Software version: 00.02.05.00.00
DSP: 00.00
FPGA: 02.00
HardVersion:58

[zenith1111]

@gnail, gandalfg8: What's your hardware revision number? Is it HW 58?

@zenith1111: Are you sure your unit didn't come with 2.05 SP1 instead of 2.05? What is your HW revision BTW?

This is my system info screen:

Model:                DS1052E
Power up times:   84
Serial No.            DS1ED125116737
Software version: 00.02.05.01.00
                         DSP:  00.00
                         FPGA:02.00
                         HardVersion:58

Screenshot: http://www.flickr.com/photos/cocasdaneve/5320723214/#

[Fraser]

Zenith1111,

You look to have a later version of 2.05 firmware so it would appear that anything later than 02.05.00.00 possibly contains a software bug.

[bsdfox]

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!

Hi, I've bought a ds1052e a couple of weeks ago, it came with FW2.05. I'm glad there is a method to downgrade these, I was afraid to mess around with mine (I have a warranty:P).

I've just registered to report that, with the original firmware, my unit hangs when the trigger is set to rise and fall. It is NOT because of this mod, it is a bug in 2.05 FW. After I choose rise and fall and it crashes, it hangs everytime I restart the unit, to get out of this loop I have to press the "AUTO" button on startup a couple times until it changes back to rise.

I never did any mod, it is completely stock, any more bugs in modified units to check if it also happens on stock ones?

I also have a stock DS1052E with FW2.05 and I cannot reproduce this lockup. Mine's perfectly happy if I set trigger to rise and fall (the up and down arrow).

I also cannot reproduce this issue on a stock HW 58 firmware 2.05 scope