Sniffing the Rigol's internal I2C bus

[asrc1978]

I don't recall that anyone has ever reported that having all 3 BW's listed actually caused any operational problems?  Just uses a bit more screen space, in the list.

I.e., the scope isn't "confused" about it's "true identity", and behaves improperly.  Does it?

I'm just wondering why people care, unless there's a functional disadvantage I missed reading about.  Always a possibility in this thread.

(And yes, I'm aware of the potential issues that can arise, simply by enabling 300 MHz.  And thus why it's not recommended.)

Hi Mark,

I can tell you that the hardware is the same for 70MHz, 100MHz, 200MHz. In the new models (DS2xxxA) the only one difference is the selectable input impedance (between 50ohm and 1Mohm) and this only to improve the measurement at high frequencies (in the case of DS2303A at 300MHz). In this case the hardware is Rev. 2.

At the end of the day is the same, you can use hardware to achieve BTW of 300MHz using a inpedance of 1Mohm with certain disadvantages in the measurement.

Thanks.

BR.

Seba.

[sacherjj]

Thanks for the heads up. Just submitted a request in highly efficient and easy to use Rigol firmware update retireval system. 

Just realized that my sarcastic post about getting updated Rigol firmware is post 666. Yeah seems appropriate.

Guess I need to take up for Rigol service, after my snide comment.  Less than 24 hours after asking through the form, I had both DSA815 and DS4k series firmware updates.  Not as good as downloading from a site, but not terrible.  Although, from the future I'll just download from the EEVblog firmware repository.  That seems simpler.   

[ch.onillon]

really really excellent this blog ... i never heard about rigol oscilloscope before but since i know we can upgrade it so easilly i want buy the 2072 ... and now up to 300 MHz , it s a must to have. i think since rigol won in delivery ..

the most difficult is now to follow allthe post on this thread .....
i learn Every days on this site.
 
next buy ? one 2072 of course :-)

[menkelis]

Just wanted to say that because of the high level of excellent information in this blog
I just purchased a 2072A (with $50 discount) from TEquipment.

I have been a long time Tektronix user (and ex employee) and was quite impressed
with the comments made. I can also say that the option of 'unlocking' extended options
fits in very well with me, as this is something that even Tek did/does with common hardware.

So now my two Tek digital scopes (222 & 224) have been donated to the Vintage Tek museum
where I volunteer as there IT  administrator.

[NYG]

I bought a DS2072A myself and just received it a few days ago. I really wasn't sure if I should get this or the DS1074z. I'm just a hobbyist getting back into it again. I dusted off my old TWD120 the other day and was surprised the windows '98 laptop that controls it still worked.

In any event the scope looks and feels like a piece of quality gear. A lot more functionality than I'm used to and more than I'm sure I'll ever need.

The last 20 pages or so should really give you all the information you need for plugging a new key in.

Some very smart people on this board. I'm glad to have stumbled upon it and happy to have this as a resource now.

[Laertes]

Please don't shout at me if that's a stupid question, but quick googling turned up nothing much...
Is the DS1000Z-Series hack capable of upgrading a 70MHz-Version to 100MHz or can you not get that?
Otherwise, I probably just have to get the 100MHz version.

Great stuff, though! 

[Rigby]

Is the DS1000Z-Series hack capable of upgrading a 70MHz-Version to 100MHz or can you not get that?

Yes.  You cannot later hack in the signal generator, though, so if you'll ever need an entry level signal generator in this scope, get it at purchase-time.

[MrAureliusR]

Yet another sale because of this hack for Rigol --

Going to purchase the DS2072A as soon as possible. I'm assuming that the DS2072A-S (with the signal gen) will work the same? Or is the firmware different enough that it doesn't work?

Thanks a million guys -- let me know if there's somewhere I can contribute to your further work!

[Rigby]

I'm assuming that the DS2072A-S (with the signal gen) will work the same? Or is the firmware different enough that it doesn't work?

On the DS1074Z-S hacking the extra features on (thus making it a DS1104Z) does not disable the signal generator.

[Laertes]

Is the DS1000Z-Series hack capable of upgrading a 70MHz-Version to 100MHz or can you not get that?

Yes.  You cannot later hack in the signal generator, though, so if you'll ever need an entry level signal generator in this scope, get it at purchase-time.

Yay! Thanks a bunch, mighty rigol hacker gods

[AndersAnd]

Going to purchase the DS2072A as soon as possible. I'm assuming that the DS2072A-S (with the signal gen) will work the same? Or is the firmware different enough that it doesn't work?

If you had read the topic you would know. They use the same FW and neslekkim has already successfully hacked his DS2202A-S.
Read here: https://www.eevblog.com/forum/testgear/sniffing-the-rigol%27s-internal-i2c-bus/msg381430/#msg381430
And here: https://www.eevblog.com/forum/testgear/sniffing-the-rigol%27s-internal-i2c-bus/msg383529/#msg383529

[anson80]

I've been trying to generate the "300 MHz, all options" license key for my DS2072A with the command "rigup license keyfile.txt NS8H" but the license that is returned is not valid. I substituted "0x1C0C7" for "NS8H" and got the identical invalid license. However, I have used the same command with the NSEQ argument to generate a license for "200 MHz, all options" and that key works as it should. Can anyone help me to figure out the problem?

Thanks,
Stan

I have the same problem,You solve the problem?
the rigup license keyfile.txt 0x1C0C7(NS8H) key that was generated was rejected by the scope with the message "License is unavailable!".
the rigup license keyfile.txt 0x1C097(NSEQ) argument to generate a license for "200 MHz, all options" is OK.
I was DS2102A

[NYG]

I've been trying to generate the "300 MHz, all options" license key for my DS2072A with the command "rigup license keyfile.txt NS8H" but the license that is returned is not valid. I substituted "0x1C0C7" for "NS8H" and got the identical invalid license. However, I have used the same command with the NSEQ argument to generate a license for "200 MHz, all options" and that key works as it should. Can anyone help me to figure out the problem?

Thanks,
Stan

I have the same problem,You solve the problem?
the rigup license keyfile.txt 0x1C0C7(NS8H) key that was generated was rejected by the scope with the message "License is unavailable!".
the rigup license keyfile.txt 0x1C097(NSEQ) argument to generate a license for "200 MHz, all options" is OK.
I was DS2102A

I'm guessing you used the firmware that uses the non-A version key algorithm? There are two versions of keying that can be used. They both work, but I focused on the "A" version so the rigup command I used was different.

I also had to modify the rigup source to have it display the NS8H key. The information on that is on page 195 I believe.

[anson80]

I've been trying to generate the "300 MHz, all options" license key for my DS2072A with the command "rigup license keyfile.txt NS8H" but the license that is returned is not valid. I substituted "0x1C0C7" for "NS8H" and got the identical invalid license. However, I have used the same command with the NSEQ argument to generate a license for "200 MHz, all options" and that key works as it should. Can anyone help me to figure out the problem?

Thanks,
Stan

I have the same problem,You solve the problem?
the rigup license keyfile.txt 0x1C0C7(NS8H) key that was generated was rejected by the scope with the message "License is unavailable!".
the rigup license keyfile.txt 0x1C097(NSEQ) argument to generate a license for "200 MHz, all options" is OK.
I was DS2102A

I'm guessing you used the firmware that uses the non-A version key algorithm? There are two versions of keying that can be used. They both work, but I focused on the "A" version so the rigup command I used was different.

I also had to modify the rigup source to have it display the NS8H key. The information on that is on page 195 I believe.

I use the new version of the A firmware,the Rigup license keyfile.txt 0x1C097 (NSEQ) is normal work of the.
I have reference corax articles change the NSFH code to NS8H on line 21 of luxury.c.But no effect under my Windows 7 64 bit

[NYG]

That's interesting. I'm using the "A" code, but I ran ./rigup ds2072a mykeyfile .
After doing that it just listed the keys for me. The NS8H key installed without a problem.

BTW I used Linux to modify/run rigup but I would expect the same results in windows.

[anson80]

That's interesting. I'm using the "A" code, but I ran ./rigup ds2072a mykeyfile .
After doing that it just listed the keys for me. The NS8H key installed without a problem.

BTW I used Linux to modify/run rigup but I would expect the same results in windows.

Thank you, I will try at Linux

[anson80]

I seem to find NS8H (0x1C0C7) position is not in the correct 300M KEY on my device.
NSEQ (0x1C097) position is correct, and can be used Rigup license keyfile.txt 0x1C097 (NSEQ) is normal work
Its DS2102A sequence number is DS2D1549... Seems to be 49 weeks of products

[MrAureliusR]

Just a quick question (I have already read through almost the whole thread)

Has anyone run into problems using the 300MHz unlock?

And is it better to generate all the keys individually instead of just using the "ALL" option? (ie, generate 300MHz, serial, mem, etc and then enter them one by one?)

EDIT: Dear God this thread is confusing. Someone REALLY needs to write a summary. I'm a pretty experienced software guy and I kept getting lost.

It seems there are two different ways to unlock features, depending on whether or not you have the A version. Though I can't find it stated explicitly, I've inferred that if you try to use the keygens with the new A models they won't work unless you first install the patched firmware.

Am I correct in that? When I receive my DS2072A in the next month or so, I should use a USB stick to install the patched firmware, and THEN generate the keys using the keygen, and install? It seems that the patched firmware is an older version -- obviously upgrading to a newer firmware will disable the upgrades, correct? Never mind, apparently it's the latest firmware, but patched.

[hari]

Just a quick question (I have already read through almost the whole thread)

then you would probably not ask these questions..

EDIT: Dear God this thread is confusing. Someone REALLY needs to write a summary. I'm a pretty experienced software guy and I kept getting lost.

better read the thread again :-) Scroll back some pages, there is a nice summary.

It seems there are two different ways to unlock features, depending on whether or not you have the A version. Though I can't find it stated explicitly, I've inferred that if you try to use the keygens with the new A models they won't work unless you first install the patched firmware.

both approaches for the A version involve custom firmware. One allows to use the old keys, and the other spits out the keys needed for the new keygen via SCPI. The latter method allows to use stock firmware after the keys have been extracted.

[MrAureliusR]

I have read most of the thread, but it's 61 pages!! It's crazy. And where is the summary? I can't find a summary that includes both methods and the steps required.

I'd be happy to write one myself, or even start a separate thread with all the instructions, plus a video showing me doing it with my scope. I just need to understand which method is better, and figure out which firmware is which etc. I guess I'll try and slug through the whole thread.

[hari]

Summary for the 2xxxA version:

Variant a (patched firmware):

- get the patched firmware that enables to use old keys
- load it onto the scope
- use the old key

Variant b:

- get the patched firmware that reads out the keys from the scope
- load it onto the scope
- use SCPI to read out the keys
- load official firmware on the scope
- use new keygen with the keys extracted via SCPI


ps: the guy who wrote the keygen said "no pain, no gain". The easier this is, the more effort will be taken from rigol to make unlocker's life harder..

[MrAureliusR]

That's true. Thanks for the summary though, that's all I needed to understand!

EDIT: Is there a re-host for the official firmware somewhere? I thought I saw a link in the thread but now I can't find it... the Rigol downloads are horrifically slow. I was trying to download the Ultra Sigma software and then realized Batronix not only hosts it but they have a newer version than on the Rigol website!!

[hari]

you can use telnet on port 5555 to talk SCPI, no need for ultra sigma..

stock firmware: https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg342994/#msg342994
sha: ddf1d511823eaf31f1d05af2ba845543d97c6d3a

[MrAureliusR]

you can use telnet on port 5555 to talk SCPI, no need for ultra sigma..

another proof that you didn't read the thread :-p

stock firmware: https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg342994/#msg342994
sha: ddf1d511823eaf31f1d05af2ba845543d97c6d3a

Actually, I DID READ THE THREAD, it's really annoying that you're trying to 'prove' that I didn't. I know I could use telnet, but I figured I'd end up downloading the Rigol software anyway, and so why not just use it?

If that fails I'll use realterm or PuTTY and use telnet.

Like, why would you assume that because I'm downloading Ultra Sigma I didn't read the thread? They actually mention a couple posts apart both methods.

[hari]

it's really annoying that you're trying to 'prove' that I didn't.

I realised that this was unqualified right after posting, so I've already edited my post.

Like, why would you assume that because I'm downloading Ultra Sigma I didn't read the thread?

Just for the records, this was referring to the firmware file, not telnet.