Sniffing the Rigol's internal I2C bus

[CHaTRail]

Hi,

I have tried to download Zombie28's modified FW (with the *IDN? key view mod) but the link to the Mega site in post #2791 just reports the URL as out of date.

Is there an alternate link? Or if Zombie28 reads this can you send me a copy of the GEL file please?

Many Thanks!

[mrflibble]

Is there an alternate link?

See previous page:

check in the mirror here http://www.gotroot.ca/rigol/

[CHaTRail]

Ah, sorry didn't spot that.

Perfect - thank you Mrflibble.

[Rigby]

I realize it's a lot to ask, but carefully reading the entire thread will indeed benefit you.

Of course, the people I'm talking to will never read this comment.

[Gallymimus]

I realize it's a lot to ask, but carefully reading the entire thread will indeed benefit you.

Of course, the people I'm talking to will never read this comment.

It's really not that much to ask.  Let's say they spend 10 hours reading the thread to save $2k.  That's a pretty good hourly rate for reading and learning.

[Dave Turner]

I've read this whole thread several times. (10 hours is far too short an estimate for one read through)

Truth is that it is so long and contains so many comments, thanks, adulation, side issues (such as this post) and repetitions that is almost impossible to make sense of.

I'm not sure what the best way forward is to clarify the current position and allow for future developments. Are sub threads possible? For example - new info, thanks, details of hack etc under the various headings.

[jdoshier]

Truth is that it is so long and contains so many comments, thanks, adulation, side issues (such as this post) and repetitions that is almost impossible to make sense of.

It should be renamed "The Rigol Megathread".

[Rigby]

I'm not sure what the best way forward is to clarify the current position and allow for future developments. Are sub threads possible? For example - new info, thanks, details of hack etc under the various headings.

this thread needs a wiki page that we can refer people to.

[true]

I've still got to find time to get a working serial reset procedure, so I can post it and have it get lost in this thread....

[Gallymimus]

I've still got to find time to get a working serial reset procedure, so I can post it and have it get lost in this thread....

Post it in a new thread!

[Rigby]

yeah, this thread is a hell of a mess and needs a curator.  this information needs to go into a wiki somewhere and be maintained, and then that maintainer needs to let this thread know so that we can update the wiki page and/or point question askers to the page for the FAQ and distilled information.

This is another example of why this style of forum software is just so absolutely terrible at information dissemination.

[AndersAnd]

didnt someone did some kind of blog page? with a guide?

http://rigol.avotronics.co.uk

But unfortunately it looks like Avotronics stopped halfway through creating the site. So most upgrade info is still missing.

[madcrow]

Hello New Owners of DS2000A DSOs,

If you are searching for an easy way to upgrade your units, take a look at this topic:
https://www.eevblog.com/forum/testgear/ds2000a-upgrade-utility/
Enjoy

[Fagear]

I have a question. For DS2000A the "new" procesure with uploading modified FW, getting some keys out of it, generating new with NSER/NSEQ/... codes is well known. But for DS2000 there were possibility to turn on "trial" keys (DSAZ -> VSAZ and so on).
Are there any codes for DS2000A (with FW 00.02...) that can add "trial" and not "official" options?

I've tried to add "trial" keys buy downgrading my DS2072A to old FW (00.01...) and applying "old" VSAH/VSAZ - that worked. But after returning to FW 00.02... trial options dissapeared.

[Fagear]

yes i remember there is a another set of commands that refreshes trial instead of activated "official" ... but im sorry to say ... i cant remember which post it was 

If you are talking about "LLLLLLL LLLLLLL-RLGLLDS-VSAZLLL-LLLLLLL" and others - they don't work with FW 00.02... 

[LIV2]

I am unable to activate the recorder feature or use the DSER code on my 1074Z, using these codes i get "Invalid License key"

However I was able to add everything else, Triggers, Decoders, 24M Depth and 100Mhz

I do notice that for the codes that work, the first two sections of the license code are the same, but not for the ones that don't. is that normal?

I'm running Firmware version 00.02.03.SP5 and the riglol key generator

[MTD]

Hello,

Another happy DS2072A-S owner, unlocked All Options + 300MHz. Not being religious per se, but it must be said, God bless whoever made the pdf Unlocking Guide (hack went smoothly). Also God bless Rigol, they certainly changed the game in favour of the customers, especially those with not a high financial capabilities.

Owner of DS1052E (not being hacked, yet) for few years already, didn't have the best experience with it as it broke down. But it must be said that Rigol did step up. On DS1052E issue, first communication was with Rigol Europe, from there being forwarded to Rigol North America, and from there to Rigol China. The Rigol China was very responsive, DS1052E was send to China where it was fixed and send back.

Considering not having the best experience with DS1052E, compared with scopes used from other vendors (Tektronix and Agilent), I was looking (and saving) into those options (Agilent most likely) for the new scope. During that though, the option for hacking DS2000A was identified, and it was just hard to resist. Now DS2072A-S, upps!!! sorry, DS2302A-S is on the bench, .

Further, eventual acquiring of Spectrum Analyzer was considered, or more precisely put, wished for. But after the hack of DS2072A-S was done, order for DSA815-TG was put in place. Because of DS2000A, eventual Rigol offering for the spectrum analyzer was checked, and DSA815-TG was discovered. Woow, it was not quite easy to believe what DSA815-TG is offering for the price tag on it. Actually, more precisely, the price tag on DSA815-TG was not quite easy to believe. Looking forward to add it on the bench.

[Arkku]

I figured my unlocked scope needed a new nameplate to reflect the features…

[hooverphonique]

Hi,

I successfully unlocked all the features on my DS2072A with the instructions in this thread. In case it is helpful to others who may have trouble digging up all the relevant info in this long thread (especially since much of it seems Windows-specific), the process I found easiest on the *nix command line (OS X, Linux, BSD, etc) was:

I tried this (excellent looking) guide, but my scope ends up saying "license is unavailable"..

the scope is a DS2072A and the original fw was 02.01.00.03 and after flashing DS2000(DSP)update_00.02.01.00.03 (license keys dump).zip from gotroot.ca, it spits out a long sequence of bytes after the serial number as expected..

I then used rigup-0.1.zip from the same site on linux to generate the NS8H key using a binary file generated by the ruby script, and I then try to install it using :SYST:OPT:INST EU4PV96RHF3XTUG73KVCCM5FTP8M

any idea what is happening/what I'm doing wrong?

cheers,
hoover

[MTD]

any idea what is happening/what I'm doing wrong?

cheers,
hoover

Did you read the DS2072A Unlocking Guide.pdf on that same site: http://www.gotroot.ca/rigol/

MTD

[Arkku]

I then used rigup-0.1.zip from the same site on linux to generate the NS8H key using a binary file generated by the ruby script, and I then try to install it using :SYST:OPT:INST EU4PV96RHF3XTUG73KVCCM5FTP8M

any idea what is happening/what I'm doing wrong?

The guide I wrote on page 208 of this thread is pretty much a direct copypaste of what I did, the only difference being that I've obscured my serial numbers. Check the screen of the scope after you enter the :syst:opt:inst and look for a progress bar. If you don't get one, maybe try and restart the scope… Of course you could just enter the license manually on the scope screen if the :system:option:install doesn't work.

[rowifi]

DS2000A Firmware update 00.03.00 is available.

[hooverphonique]

Did you read the DS2072A Unlocking Guide.pdf on that same site: http://www.gotroot.ca/rigol/

I did.. I just used info from Arkku's guide since it omits installing viva? drivers (I am on linux at the moment) and fiddling with a text editor.

The guide I wrote on page 208 of this thread is pretty much a direct copypaste of what I did, the only difference being that I've obscured my serial numbers. Check the screen of the scope after you enter the :syst:opt:inst and look for a progress bar. If you don't get one, maybe try and restart the scope… Of course you could just enter the license manually on the scope screen if the :system:option:install doesn't work.

The scope says 'license is unavailable!' (no progress bar) when using the onscreen editor as well.. restarting doesn't change anything.. I suspect something is wrong with the generated key.. Why, I don't know... I will see if I can find a windows box and try the precompiled version of rigup  (does anyone know if the 02 version generates the same keys as 01?), because when I compiled it, I got some warnings about uninitialized variables.. otherwise something probably goes wrong when applying the ruby script..

[hooverphonique]

I think I've come across some sort of tamper-counter, because now the scope has stopped responding to any license I throw at it, both over LAN and in the user interface (no 'license is unavailable' message anymore, no reaction whatsoever).. power off, etc, doesn't help..

another discovery is that the windows exe from the gotroot.ca rigup02.rar archive does *not* produce the same licenses as the home-built one from rigup-0.1.zip (built just by issuing 'make'), i.e. the two versions produce different output when doing e.g. 'rigup license scopekeys.txt NS8H'.
They do produce the same licenses when invoked using 'rigup ds2072a scope.bin', however..

[Gallymimus]

I think I've come across some sort of tamper-counter, because now the scope has stopped responding to any license I throw at it, both over LAN and in the user interface (no 'license is unavailable' message anymore, no reaction whatsoever).. power off, etc, doesn't help..

another discovery is that the windows exe from the gotroot.ca rigup02.rar archive does *not* produce the same licenses as the home-built one from rigup-0.1.zip (built just by issuing 'make'), i.e. the two versions produce different output when doing e.g. 'rigup license scopekeys.txt NS8H'.
They do produce the same licenses when invoked using 'rigup ds2072a scope.bin', however..

There are multiple solutions to a valid license so it isn't necessarily a big deal that you get two different outputs.