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

[Expired]

....

1)upgraded to 03.01 to 04.00
2)downgraded from 04.00 to 02.02 sp2 (they said the fw works 04.00 to 02.02 sp2 so i prefered to update to 04 before doing the downgrade)
....

Any differences between the downgrade from 4.00 and from 2.05 in OP?

EDIT: Ok , I was able to downgrade to 2.02 SP2 but now i can't see the SN or the Model. Any Idea?
https://www.dropbox.com/s/7y0vyeb7pi7nqz9/20121128_021700.jpg

[blackknife]

I didn't notice any difference between 03.01 and 04.00. Anyway for the serial number you can reprogram it with DemoIDN, i hope you wrote it somewhere before downgrading....

[KeBeNe]

EDIT: Ok , I was able to downgrade to 2.02 SP2 but now i can't see the SN or the Model. Any Idea?
https://www.dropbox.com/s/7y0vyeb7pi7nqz9/20121128_021700.jpg

Hello,

no problem, the is serial number see backwards of DSO (SN DS1ED########),
you must write in demoIDN for conversion to 100Mhz DSO:
1. ":INFO:MODEL DS1102E"
2. ":INFO:SERIAL DS1EB########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

or for conversion to 150Mhz
1. ":INFO:MODEL DS1152E-EDU"
2. ":INFO:SERIAL DS1EF########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

for default DS1052e
1. ":INFO:MODEL DS1052E"
2. ":INFO:SERIAL DS1ED########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

regards René

[blackknife]

150 MHz???  Have you tried if it really works up to that frequency? i seriously doubt that the frequency response would be flat up to 150 MHz....

[KeBeNe]

i have don´t tested yet, i doubt also that it works fine, but try out...
https://www.eevblog.com/forum/general-chat/ds1052e-up-to-150mhz/

[Expired]

EDIT: Ok , I was able to downgrade to 2.02 SP2 but now i can't see the SN or the Model. Any Idea?
https://www.dropbox.com/s/7y0vyeb7pi7nqz9/20121128_021700.jpg

Hello,

no problem, the is serial number see backwards of DSO (SN DS1ED########),
you must write in demoIDN for conversion to 100Mhz DSO:
1. ":INFO:MODEL DS1102E"
2. ":INFO:SERIAL DS1EB########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

or for conversion to 150Mhz
1. ":INFO:MODEL DS1152E-EDU"
2. ":INFO:SERIAL DS1EF########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

for default DS1052e
1. ":INFO:MODEL DS1052E"
2. ":INFO:SERIAL DS1ED########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

regards René

Thanks for the answer. (Sorry for my english).
Now I have a problem with the USB connection to PC.
When I click on "USB::0x1AB1::0x0588::DS1.........." I got " Device not found!" , the letters "Rmt" appear in the upper
 right corner and the screen is locked.
I used windows 8 and windows 7, now i am trying windowx xp.
I just can't  understand  i got

EDIT: XP give me the same error.
I used NI-VISA 4.6.2 and 5.2.0

[KeBeNe]

Hello,

what you see on the screen when you typing or set "*IDN?" in the lower drop down  menue?

[Expired]

Hello,

what you see on the screen when you typing or set "*IDN?" in the lower drop down  menue?

If I just open demoIDN "Rmt" appears and screen is locked. 

[blackknife]

Hello,

what you see on the screen when you typing or set "*IDN?" in the lower drop down  menue?

If I just open demoIDN "Rmt" appears and screen is locked. 

Your pc screen? that's really strange...

[Expired]

Hello,

what you see on the screen when you typing or set "*IDN?" in the lower drop down  menue?

If I just open demoIDN "Rmt" appears and screen is locked. 

Your pc screen? that's really strange...

No. The DSO screen.

[blackknife]

That's normal...just reboot it and it's fine!

[Expired]

OK, I know what my problem is.
I have upgraded to  4.00 and I have got again the model and a SN (not the first one).
Now I can connect the DSO with Ultrascope. No more "Device not found!".
I tried to change model and SN with fw 2.02 using demoIDN, but is always the same "Rigol Technologies,,,00.02.02.02.00".
https://www.dropbox.com/s/7y0vyeb7pi7nqz9/20121128_021700.jpg

@blackknife, when you have downgraded from 4.00 to 2.02 did it happen the same?

PS:thank you for the aswer.

EDIT: I'm so stupid. Now it's working.

[netlander]

Just tried with version 00.03.01 and worked perfectly!

Now I've a "DS1102E" 100Mhz scope!

THANKS A LOT! I know this (03.01 hack) originated in a german forum, great work!

Just some things:
1) When updated to version 4, screen flicked sporadically. Would be unusable if stayed on that version.
2) When downgrade to 00.02.02.02.00 hardware version, serial number and model got lost! (not an issue, don't panic)
3) DSP version changed from 00.01 to 02.15 and FPGA went from 03.07 to 02.00. Not saying it's a problem, just reporting.

Finally I upgraded to 00.02.04.01.02 without a problem. Now showing model DS1102E, hardware version 58, dsp 02.20 and fpga 02.00.

I read some people saying to get back to version 4 after the hack, but I had some issues with the screen on that version. So won't try it again.
 

EDIT: Ok , I was able to downgrade to 2.02 SP2 but now i can't see the SN or the Model. Any Idea?
https://www.dropbox.com/s/7y0vyeb7pi7nqz9/20121128_021700.jpg

Hello,

no problem, the is serial number see backwards of DSO (SN DS1ED########),
you must write in demoIDN for conversion to 100Mhz DSO:
1. ":INFO:MODEL DS1102E"
2. ":INFO:SERIAL DS1EB########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

or for conversion to 150Mhz
1. ":INFO:MODEL DS1152E-EDU"
2. ":INFO:SERIAL DS1EF########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

for default DS1052e
1. ":INFO:MODEL DS1052E"
2. ":INFO:SERIAL DS1ED########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

regards René

[blackknife]

1) When updated to version 4, screen flicked sporadically. Would be unusable if stayed on that version.

I read some people saying to get back to version 4 after the hack, but I had some issues with the screen on that version. So won't try it again.
 

EDIT: Ok , I was able to downgrade to 2.02 SP2 but now i can't see the SN or the Model. Any Idea?
https://www.dropbox.com/s/7y0vyeb7pi7nqz9/20121128_021700.jpg

Hello,

no problem, the is serial number see backwards of DSO (SN DS1ED########),
you must write in demoIDN for conversion to 100Mhz DSO:
1. ":INFO:MODEL DS1102E"
2. ":INFO:SERIAL DS1EB########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

or for conversion to 150Mhz
1. ":INFO:MODEL DS1152E-EDU"
2. ":INFO:SERIAL DS1EF########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

for default DS1052e
1. ":INFO:MODEL DS1052E"
2. ":INFO:SERIAL DS1ED########"   '######### your serial number
3. ":INFO:HARDVERSION **"   '** your Hardversion e.g. 58

regards René

I've been using version 04.00 for some days..without any problem! 

[Arp]

Woho did it! That was simple :-) I was worried that my new 3.0.1 oscilloscope wouldnt be able to make it.


*edit* I upgraded to 4 and everything seems to work fine so far.

[jh15]

I have an untouched 1052e and it has v 2.06 stock.

Does this mean I can now go from 2.06 to 4.0?

So many pages and evolution of the unit to read through.

[netlander]

Looks like you forgot to set your hardware version.

Don't know what possible ramifications could be, but you might want to set it right before going further.

Woho did it! That was simple :-) I was worried that my new 3.0.1 oscilloscope wouldnt be able to make it.


*edit* I upgraded to 4 and everything seems to work fine so far.

[netlander]

I've been using version 04.00 for some days..without any problem! 

Could you tell me where you got that version from?

Is it the one provided by Renè on this thread? An MD5 or SHA of the file would help as well.

Thanks,

[blackknife]

I used the one linked by renè, "4.0to20.2.zip". The md5 of the firmware file is: 52688624C7A461D50F02432CD32511CC (DS1000EUpdate.RGL 4097 Kb)

[Arp]

*edit* Fixed it and ran another upgrade too 4. Works  *

Looks like you forgot to set your hardware version.

Don't know what possible ramifications could be, but you might want to set it right before going further.

Woho did it! That was simple :-) I was worried that my new 3.0.1 oscilloscope wouldnt be able to make it.


*edit* I upgraded to 4 and everything seems to work fine so far.

[drieg]

I'm afraid, you will experience issues with trigger delay with this method, can anybody test?

[KeBeNe]

@ Arg
you create the hardware version with the demoIDN tool by command ":INFO:HARDVERSION 58"

@drieg
I have witnessed so far no problems, how I can  test it?

[drieg]

Get some square or pulse signal with fast edges and check whether you see some delay between trigger point mark "T"on display and real trigger event (e.g. rising edge).

The thing is, that older firmwares reads these model-specific information (model, sn, hardversion and also other calibration constants and bits) from another part of flash memory. The new firmwares (3.01 and above) reads both model-spec blocks, so if you create this old-type data block, the new firmware primarily reads this one and misses some other constants and bits (for example trigger delay, LA bit,..). Unfortunately some of them cannot be recreated with SCPI commands. So this might also downgrade DS1000D to DS1000E 

[blackknife]

Get some square or pulse signal with fast edges and check whether you see some delay between trigger point mark "T"on display and real trigger event (e.g. rising edge).

The thing is, that older firmwares reads these model-specific information (model, sn, hardversion and also other calibration constants and bits) from another part of flash memory. The new firmwares (3.01 and above) reads both model-spec blocks, so if you create this old-type data block, the new firmware primarily reads this one and misses some other constants and bits (for example trigger delay, LA bit,..). Unfortunately some of them cannot be recreated with SCPI commands. So this might also downgrade DS1000D to DS1000E 

I tried and it's still working well, maybe what's important it's just to avoid "self-calibration" while using 2.02 firmware?
(right now i'm using the 04.00 firmware)

[KeBeNe]

It worked out well, so do not delay