Author Topic: Sniffing the Rigol's internal I2C bus  (Read 1840982 times)

0 Members and 5 Guests are viewing this topic.

Offline Mark_O

  • Frequent Contributor
  • **
  • Posts: 939
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3150 on: April 09, 2014, 05:18:55 am »
I think I've come across some sort of tamper-counter, ...

Nice way to spread FUD!   :-+
 

Offline MTD

  • Newbie
  • Posts: 3
  • Country: mk
Re: Sniffing the Rigol's internal I2C bus
« Reply #3151 on: April 09, 2014, 05:25:47 am »
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..

Hmm, if you haven't tried already, I'm wondering.
How about uninstalling all the options?
:SYSTem:OPTion:UNINSTall

MTD
 

Offline Arkku

  • Contributor
  • Posts: 12
Re: Sniffing the Rigol's internal I2C bus
« Reply #3152 on: April 09, 2014, 07:14:06 am »
How about uninstalling all the options?
:SYSTem:OPTion:UNINSTall

In addition to this it might be a good idea to reinstall the firmware (it can even be the official firmware since the keys were already dumped).
 

Offline hooverphonique

  • Contributor
  • Posts: 23
  • Country: dk
Re: Sniffing the Rigol's internal I2C bus
« Reply #3153 on: April 09, 2014, 09:40:34 am »
Hmm, if you haven't tried already, I'm wondering.
How about uninstalling all the options?
:SYSTem:OPTion:UNINSTall

you mean uninstalling the trial licenses that came with it? because that's all that's installed.. I never succeeded in installing any licenses myself.. It kept saying "license is unavailable" until it stopped reacting at all...

I also tried reflashing it with official firmware, but it still doesn't respond to any license key entry, meaning I can enter the key, but when pushing apply, nothing happens at all, and it's the same using :SYST:OPT:INST over SCPI..

thanks for any suggestions, guys...
 

Offline hooverphonique

  • Contributor
  • Posts: 23
  • Country: dk
Re: Sniffing the Rigol's internal I2C bus
« Reply #3154 on: April 09, 2014, 11:46:39 am »
so I tried ':SYST:OPT:UNINST', but there was no reaction on the screen (is there supposed to be?) and after reboot, all the trial options is still there and I still can't get a reaction by doing e.g. ':SYST:OPT:INST SY5ZYQFV4KG7DDZXC27D6Q5RU25M' ... It responds to the '*IDN?' command, so the connection should be fine..

is there some sort of master reset one may apply by some magic key combination or something?

this is really puzzling...
« Last Edit: April 09, 2014, 11:48:24 am by hooverphonique »
 

Offline neslekkim

  • Super Contributor
  • ***
  • Posts: 1305
  • Country: no
Re: Sniffing the Rigol's internal I2C bus
« Reply #3155 on: April 09, 2014, 11:52:52 am »
I newer got an answer when i did the syst:opt:inst xxx, but when I checked on the scope, everything was ok.
 

Offline hooverphonique

  • Contributor
  • Posts: 23
  • Country: dk
Re: Sniffing the Rigol's internal I2C bus
« Reply #3156 on: April 09, 2014, 12:41:08 pm »
I newer got an answer when i did the syst:opt:inst xxx, but when I checked on the scope, everything was ok.

hmm... that's funny - everybody else says there's supposed to be a progress bar...

regarding uninstall, I just found that issuing ':SYST:OPT:UNINST' provokes no reaction from the scope, but if I issue ':syst:opt:uninstall', a message appears on screen saying all official licenses have been removed  :o
it doesn't change anything regarding installing licenses, though..
« Last Edit: April 09, 2014, 12:53:20 pm by hooverphonique »
 

Offline alank2

  • Super Contributor
  • ***
  • Posts: 2185
Re: Sniffing the Rigol's internal I2C bus
« Reply #3157 on: April 09, 2014, 01:15:35 pm »
I think there may have been a timer added if you try to add too many licenses, at least I saw some evidence of this in some of the text strings in one of the newer firmware versions.  You may have to leave it on for awhile to get out of that timer (which may also deplete your trial options).
 

Offline mrflibble

  • Super Contributor
  • ***
  • Posts: 2051
  • Country: nl
Re: Sniffing the Rigol's internal I2C bus
« Reply #3158 on: April 09, 2014, 02:05:37 pm »
I think there may have been a timer added if you try to add too many licenses, at least I saw some evidence of this in some of the text strings in one of the newer firmware versions.  You may have to leave it on for awhile to get out of that timer (which may also deplete your trial options).
And while you are at it ... take notes and write down times and stuff. If in fact Rigol did add some counter measures (unconfirmed hypothesis AFAIK), chances are fairly good that you still have a 100% usable instrument. As alank2 suggests, just leave it powered for a while to let it time out.

Not a direct solution to your problem, but more of a hint when controlling Rigol gear through SCPI. Take both the documentation and implementation with a grain of salt. I like Rigol goodies for the very nice price/performance ratio, but in the department of consistency they are not quite there yet. Basically, don't always belief what the docs say a command should be. In case of doubt best to use the full command in upper case.

And whenever you run into a  :wtf: situation where you are not sure if a command just did what you expected you can check status + logs messages.

 

Offline Teneyes

  • Frequent Contributor
  • **
  • Posts: 498
  • Country: ca
Re: Sniffing the Rigol's internal I2C bus
« Reply #3159 on: April 09, 2014, 03:17:12 pm »
I think there may have been a timer added if you try to add too many licenses, at least I saw some evidence of this in some of the text strings in one of the newer firmware versions.  You may have to leave it on for awhile to get out of that timer (which may also deplete your trial options).
Try this old trick ,
Set the System Time  to 2099-12-31   23:59;55   and let the Clock roll over.
Then do a Self-Cal.  ( a state that it is in the Factory)
IiIiIiIiIi  --  curiosity killed the cat but, satisfaction brought it back
 

Offline Tilman

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #3160 on: April 09, 2014, 03:39:07 pm »
Hello,


300MHZ dosen´t work for my DS2072A only 200MHZ works, any solution?

Thanks
 

Offline Teneyes

  • Frequent Contributor
  • **
  • Posts: 498
  • Country: ca
Re: Sniffing the Rigol's internal I2C bus
« Reply #3161 on: April 09, 2014, 03:46:00 pm »
Hello,
300MHZ dosen´t work for my DS2072A only 200MHZ works, any solution?
Thanks
Do you mean you can not Install 300Mhz option?
Try uninstall first, then just Install  300MHz
IiIiIiIiIi  --  curiosity killed the cat but, satisfaction brought it back
 

Offline hooverphonique

  • Contributor
  • Posts: 23
  • Country: dk
Re: Sniffing the Rigol's internal I2C bus
« Reply #3162 on: April 09, 2014, 03:49:40 pm »
And whenever you run into a  :wtf: situation where you are not sure if a command just did what you expected you can check status + logs messages.

and where do I find those? the DS2000 programming guide doesn't list commands for that, as far as I could see (I didn't read it fully, though)..

Try this old trick ,
Set the System Time  to 2099-12-31   23:59;55   and let the Clock roll over.
Then do a Self-Cal.  ( a state that it is in the Factory)

Thanks for the suggestion.. unfortunately, it didn't make a difference..
 

Offline mrflibble

  • Super Contributor
  • ***
  • Posts: 2051
  • Country: nl
Re: Sniffing the Rigol's internal I2C bus
« Reply #3163 on: April 09, 2014, 04:03:37 pm »
And whenever you run into a  :wtf: situation where you are not sure if a command just did what you expected you can check status + logs messages.

and where do I find those? the DS2000 programming guide doesn't list commands for that, as far as I could see (I didn't read it fully, though)..
Related SCPI commands :

Code: [Select]
*CLS
*STB?
*SRE?
*SRE <val>
:STATUS
:SYSTEM:ERROR?

Don't have a DS2000. Rigol tends to not document everything, so testing a general SCPI command sometimes gives a useful result, 100% depending on what Rigol decided to implement today.
 

Offline amr

  • Contributor
  • Posts: 17
  • Country: es
Re: Sniffing the Rigol's internal I2C bus
« Reply #3164 on: April 09, 2014, 08:53:03 pm »
Hello

I've just tried these codes with my new DS1074Z:

DSAB - Advanced Triggers
DSAC - Decoders
DSAE - 24M Memory
DSAJ - Recorder
DSEA - 100MHz

All options have been installed successfully, but 100 Mhz bandwidth option (DSEA) is not shown in the "Installed Options" screen. Is it right?
The firmware version is 00.02.03.SP5

Thanks.

« Last Edit: April 10, 2014, 05:35:53 am by amr »
 

Offline Suffer1981de

  • Contributor
  • Posts: 23
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #3165 on: April 09, 2014, 09:01:13 pm »
Look under Utility -> System -> Sytem Info. If it says its a DS1104Z then congratulations. I used the option DSER which gave me all of the options altogether.

Greetings from Germany
 

Offline amr

  • Contributor
  • Posts: 17
  • Country: es
Re: Sniffing the Rigol's internal I2C bus
« Reply #3166 on: April 09, 2014, 09:15:52 pm »
Look under Utility -> System -> Sytem Info. If it says its a DS1104Z then congratulations. I used the option DSER which gave me all of the options altogether

Yes!!!! DS1104Z  :) :) :)

I have not used DSER because "DSBA - 500uV Vertical" seems that can cause some software problems...
 

Offline Suffer1981de

  • Contributor
  • Posts: 23
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #3167 on: April 09, 2014, 09:24:41 pm »
DSER is all options without the 500uV.  ;)
 

Offline amr

  • Contributor
  • Posts: 17
  • Country: es
Re: Sniffing the Rigol's internal I2C bus
« Reply #3168 on: April 09, 2014, 09:58:03 pm »
DSER is all options without the 500uV.  ;)

Sorry, I meant "DSFR - all options". I didn't know that code (DSER)... :palm:
« Last Edit: April 10, 2014, 05:08:24 am by amr »
 

Offline LIV2

  • Contributor
  • Posts: 17
  • Country: au
Re: Sniffing the Rigol's internal I2C bus
« Reply #3169 on: April 10, 2014, 02:20:30 am »
So am I the only one with a 1074z with the inability to use some codes?

Are there any other generators besides the riglol online one perhaps?
 

Offline toni31

  • Contributor
  • Posts: 19
Re: Sniffing the Rigol's internal I2C bus
« Reply #3170 on: April 10, 2014, 03:37:04 am »
is there any guide of how i install the DSER code?
 

Offline amr

  • Contributor
  • Posts: 17
  • Country: es
Re: Sniffing the Rigol's internal I2C bus
« Reply #3171 on: April 10, 2014, 05:46:25 am »
Have you tried to install option by option?

I followed these steps (Reply #1345):

https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/1335/
 

Offline LIV2

  • Contributor
  • Posts: 17
  • Country: au
Re: Sniffing the Rigol's internal I2C bus
« Reply #3172 on: April 10, 2014, 09:28:57 am »
Yeah, I've installed everything except Recording and the 500uv vertical codes.

Don't want 500v, but do want Recording.

When I enter a code for the Recording it tells me the key is invalid, I also noticed that the first two sections of this key differ from all the others which were the same.

What firmware are you running? Maybe something's been changed by rigol.
 

Offline amr

  • Contributor
  • Posts: 17
  • Country: es
Re: Sniffing the Rigol's internal I2C bus
« Reply #3173 on: April 10, 2014, 09:59:22 am »
When I enter a code for the Recording it tells me the key is invalid, I also noticed that the first two sections of this key differ from all the others which were the same.

In my case I have been able to activate that function.

What firmware are you running? Maybe something's been changed by rigol.

The firmware version is 00.02.03.SP5
 

Offline Tilman

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #3174 on: April 10, 2014, 11:00:48 am »
Hello,
300MHZ dosen´t work for my DS2072A only 200MHZ works, any solution?
Thanks
Do you mean you can not Install 300Mhz option?
Try uninstall first, then just Install  300MHz

Yes it Shows "License unavailable", tried uninstalling an installing too.
Had a second one (had an defect) and there the 300MHZ works like a charm
 
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf