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

0 Members and 2 Guests are viewing this topic.

Offline egonotto

  • Regular Contributor
  • *
  • Posts: 246
Re: Sniffing the Rigol's internal I2C bus
« Reply #225 on: June 28, 2013, 03:48:36 pm »
Hello marmad,

thanks.

Best regard,

egonotto
 

Offline f_richter

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #226 on: June 28, 2013, 03:54:34 pm »
The code DSA9LLL and VSA9LLL does also work on DS4014.
Thank you!
 

Offline marmad

  • Super Contributor
  • ***
  • Posts: 2979
  • Country: aq
    • DaysAlive
Re: Sniffing the Rigol's internal I2C bus
« Reply #227 on: June 28, 2013, 03:57:38 pm »
The code DSA9LLL and VSA9LLL does also work on DS4014.
Thank you!

Oh boy! The shit has really hit the fan now  ;D
 

Offline f_richter

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #228 on: June 28, 2013, 04:08:20 pm »
All options enabled, bandwidth options not avail an DS4000. ?!
The keys are lost on powercycling.
 

Offline marmad

  • Super Contributor
  • ***
  • Posts: 2979
  • Country: aq
    • DaysAlive
Re: Sniffing the Rigol's internal I2C bus
« Reply #229 on: June 28, 2013, 04:09:50 pm »
Someone who owns a DG4000 series should give it a try it as well.

I just looked at the programming manual for the DG4000, and the INSTALL/UNINSTALL SCPI commands are not listed - but they may be undocumented (since it doesn't have purchasable options).

But it can be tested by just using the sequence I posted above for Ultra Sigma (but without the UNINSTALL command). After running the INSTALL command (if you don't get the 'Unsupported command' message), check the model number in System Info.
« Last Edit: June 28, 2013, 04:23:57 pm by marmad »
 

Offline marmad

  • Super Contributor
  • ***
  • Posts: 2979
  • Country: aq
    • DaysAlive
Re: Sniffing the Rigol's internal I2C bus
« Reply #230 on: June 28, 2013, 04:18:35 pm »
All options enabled, bandwidth options not avail an DS4000. ?!
The keys are lost on powercycling.

Did you check your model number in System Info after applying the code?
 

Offline cybernet

  • Regular Contributor
  • *
  • Posts: 247
  • Country: 00
  • pm deactivated, use the search function ...
Re: Sniffing the Rigol's internal I2C bus
« Reply #231 on: June 28, 2013, 04:22:01 pm »
All options enabled, bandwidth options not avail an DS4000. ?!
The keys are lost on powercycling.

Did you check your model number in System Info after applying the code?

is the DS4/6 bandwith upgradeable at all ? - "DSA9" enables 5 options, on the ds2 thats the default 3 + 2x bandwith (100+200).
___________________
"all rights reversed :-)"
R0=-0x18;
UNLINK;
RTS;
 

Offline Wim13

  • Regular Contributor
  • *
  • Posts: 225
  • Country: nl
Re: Sniffing the Rigol's internal I2C bus
« Reply #232 on: June 28, 2013, 04:23:29 pm »
Someone who owns a DG4000 series should give it a try it as well.

I just looked at the programming manual for the DG4000, and the INSTALL/UNINSTALL SCPI commands are not listed - but they may be undocumented (since it doesn't have purchasable options).

But it can be tested by just using the sequence I posted above for Ultra Sigma (but without the UNINSTALL command). After running the INSTALL command, reboot the AWG and check the model number in System Info.

No, does not work, gives remote command error, in the key is has DS twice, so i think it is only for DS...
did change it in DG but no luck
 

Offline mikeselectricstuff

  • Super Contributor
  • ***
  • Posts: 12068
  • Country: gb
    • Mike's Electric Stuff
Re: Sniffing the Rigol's internal I2C bus
« Reply #233 on: June 28, 2013, 04:25:01 pm »
Someone who owns a DG4000 series should give it a try it as well.

I just looked at the programming manual for the DG4000, and the INSTALL/UNINSTALL SCPI commands are not listed - but they may be undocumented (since it doesn't have purchasable options).

But it can be tested by just using the sequence I posted above for Ultra Sigma (but without the UNINSTALL command). After running the INSTALL command, reboot the AWG and check the model number in System Info.
Can you clarify which string you propose trying via SCPI on the DG?  With the DG, it's presumably a model no., not a license thing
Youtube channel:Taking wierd stuff apart. Very apart.
Mike's Electric Stuff: High voltage, vintage electronics etc.
Day Job: Mostly LEDs
 

Offline marmad

  • Super Contributor
  • ***
  • Posts: 2979
  • Country: aq
    • DaysAlive
Re: Sniffing the Rigol's internal I2C bus
« Reply #234 on: June 28, 2013, 04:26:32 pm »
is the DS4/6 bandwith upgradeable at all ? - "DSA9" enables 5 options, on the ds2 thats the default 3 + 2x bandwith (100+200).

I don't think so - and only fully-implemented on the DS2000 in FW.03.
 

Offline cybernet

  • Regular Contributor
  • *
  • Posts: 247
  • Country: 00
  • pm deactivated, use the search function ...
Re: Sniffing the Rigol's internal I2C bus
« Reply #235 on: June 28, 2013, 04:26:50 pm »
DS4K owners could try

LLLLLLL-RLGLLDS-DSB9LLL-LLLLLLL - enable 6 options
LLLLLLL-RLGLLDS-DSD9LLL-LLLLLLL - enable 7 options
LLLLLLL-RLGLLDS-DSH9LLL-LLLLLLL - enable 8 options

(typos fixed, argh ...)
« Last Edit: June 28, 2013, 04:28:47 pm by cybernet »
___________________
"all rights reversed :-)"
R0=-0x18;
UNLINK;
RTS;
 

Offline marmad

  • Super Contributor
  • ***
  • Posts: 2979
  • Country: aq
    • DaysAlive
Re: Sniffing the Rigol's internal I2C bus
« Reply #236 on: June 28, 2013, 04:28:19 pm »
Can you clarify which string you propose trying via SCPI on the DG?  With the DG, it's presumably a model no., not a license thing

No need, it's just been checked on the DG - and doesn't work (SCPI command unsupported). But the code changes the model number on the DS2000 (in FW.03).
 

Offline f_richter

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #237 on: June 28, 2013, 04:45:35 pm »
All options enabled, bandwidth options not avail an DS4000. ?!
The keys are lost on powercycling.

Did you check your model number in System Info after applying the code?
The modelnumber does not change.
DSB9LLL,DSD9LLL,DSH9LLL code works also.

@cybernet
really nice work !
 

Offline cybernet

  • Regular Contributor
  • *
  • Posts: 247
  • Country: 00
  • pm deactivated, use the search function ...
Re: Sniffing the Rigol's internal I2C bus
« Reply #238 on: June 28, 2013, 05:05:15 pm »
DSA9 - 5 options is the maximum my DS accepts

as DS4 accepts

LLLLLLL-RLGLLDS-DSB9LLL-LLLLLLL - enable 6 options
LLLLLLL-RLGLLDS-DSD9LLL-LLLLLLL - enable 7 options
LLLLLLL-RLGLLDS-DSH9LLL-LLLLLLL - enable 8 options

you could try

LLLLLLL-RLGLLDS-DSR9LLL-LLLLLLL - enable 9 options
LLLLLLL-RLGLLDS-DS99LLL-LLLLLLL - enable 10 options
LLLLLLL-RLGLLDS-DT99LLL-LLLLLLL - enable 11 options
LLLLLLL-RLGLLDS-DV99LLL-LLLLLLL - enable 12 options

as well - this exhausts the available bits, so imho no more than 12 options are possible with their algos  ...
___________________
"all rights reversed :-)"
R0=-0x18;
UNLINK;
RTS;
 

Offline f_richter

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #239 on: June 28, 2013, 05:44:49 pm »

you could try

LLLLLLL-RLGLLDS-DSR9LLL-LLLLLLL - enable 9 options
LLLLLLL-RLGLLDS-DS99LLL-LLLLLLL - enable 10 options
LLLLLLL-RLGLLDS-DT99LLL-LLLLLLL - enable 11 options
LLLLLLL-RLGLLDS-DV99LLL-LLLLLLL - enable 12 options

as well - this exhausts the available bits, so imho no more than 12 options are possible with their algos  ...
lower codes doesnt work unfortunately.
 

Offline alank2

  • Super Contributor
  • ***
  • Posts: 2003
Re: Sniffing the Rigol's internal I2C bus
« Reply #240 on: June 28, 2013, 08:24:18 pm »
I have done the following:
- Update to FW 03
- Enter code LLLLLLL-RLGLLDS-DSA9LLL-LLLLLLL
- Downgrade to FW 05
A big thank you to cybernet

So, does this mean that you can permanently change it to a 2202?

And back again to a 2072?

Does this enable all of the trial options too?
 

Offline bluesmoke

  • Contributor
  • Posts: 24
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #241 on: June 28, 2013, 09:10:03 pm »
Looks like Christmas came early this year!
 

Offline Carrington

  • Super Contributor
  • ***
  • Posts: 1201
  • Country: es
Re: Sniffing the Rigol's internal I2C bus
« Reply #242 on: June 28, 2013, 09:25:27 pm »
Another future owner of a DS2072, thanks to your work.
And repentant user of a SDS8102V, thanks to OWON work.  :-DD
My English can be pretty bad, so suggestions are welcome. ;)
Space Weather.
Lightning & Thunderstorms in Real Time.
 

Offline Spark

  • Newbie
  • Posts: 3
  • Country: gb
Re: Sniffing the Rigol's internal I2C bus
« Reply #243 on: June 28, 2013, 09:38:28 pm »
I have done the following:
- Update to FW 03
- Enter code LLLLLLL-RLGLLDS-DSA9LLL-LLLLLLL
- Downgrade to FW 05

Now 20Mhz, 100Mhz and OFF is available in the menu. Also, can I use the 2ns time base.
I see no difference to a DS2202.
Even after rebooting.

A big thank you to cybernet

Very interesting. One thing to consider - it would be worthwhile to discover a key to change the model numbers BACK to original numbers (2072 or 2102), since this could clearly be used as an indicator for voided warranty.

With firmware 03 on a DS2102 I entered your code and then did a self cal. Change to a 2202 seems to stay after a reboot and tested bandwidth is 200Mhz but the options are not retained.
A very big thank you to you all, although new to posting I have been following the DS2000 threads for a while and learnt a lot.
Measure it twice cut it once.
 

Offline orbiter

  • Frequent Contributor
  • **
  • Posts: 618
  • Country: gb
  • -0 Resistance is Futile
Re: Sniffing the Rigol's internal I2C bus
« Reply #244 on: June 28, 2013, 10:03:54 pm »
This is correct, however a simple re-entry of the code will re-enable the option goodness again.

AFAIK the FW code is still being prodded by some awesome people here :)

Offline mickpah

  • Regular Contributor
  • *
  • Posts: 148
  • Country: au
    • Yeti Hacks
Re: Sniffing the Rigol's internal I2C bus
« Reply #245 on: June 28, 2013, 11:27:27 pm »
Please excuse my total ignorance of SCPI, so I may have this wrong.
It looks like a pretty simple task to make a USB dongle to enter the code a boot.

ie wait 15 sec after powerup for boot to complete send SCPI string - gross over simplification but you get the idea.

I have Tweeny 2.0 sitting here just waiting to do something really useful

http://www.pjrc.com/store/teensy.html
 
 

Offline marmad

  • Super Contributor
  • ***
  • Posts: 2979
  • Country: aq
    • DaysAlive
Re: Sniffing the Rigol's internal I2C bus
« Reply #246 on: June 28, 2013, 11:41:33 pm »
Please excuse my total ignorance of SCPI, so I may have this wrong.
It looks like a pretty simple task to make a USB dongle to enter the code a boot.

ie wait 15 sec after powerup for boot to complete send SCPI string - gross over simplification but you get the idea.

I think some people are still hoping for a hack of the official option keys - thus not requiring anything at boot-up. Meanwhile, I hope to release a version of RUU shortly which will send the code automatically on connect (as one temporary measure).
 

Offline mickpah

  • Regular Contributor
  • *
  • Posts: 148
  • Country: au
    • Yeti Hacks
Re: Sniffing the Rigol's internal I2C bus
« Reply #247 on: June 28, 2013, 11:58:10 pm »
Please excuse my total ignorance of SCPI, so I may have this wrong.
It looks like a pretty simple task to make a USB dongle to enter the code a boot.

ie wait 15 sec after powerup for boot to complete send SCPI string - gross over simplification but you get the idea.

I think some people are still hoping for a hack of the official option keys - thus not requiring anything at boot-up. Meanwhile, I hope to release a version of RUU shortly which will send the code automatically on connect (as one temporary measure).
that would be great ! but as a fall back I could live with a dongle. Rainy weekend here, if I can finish running cables in the ceiling ( ready for the NBN Whoo hooo -100/40 Mb on the way) I will have a hack
 

Offline Harvs

  • Super Contributor
  • ***
  • Posts: 1162
  • Country: au
Re: Sniffing the Rigol's internal I2C bus
« Reply #248 on: June 29, 2013, 01:02:18 am »
Please excuse my total ignorance of SCPI, so I may have this wrong.
It looks like a pretty simple task to make a USB dongle to enter the code a boot.

ie wait 15 sec after powerup for boot to complete send SCPI string - gross over simplification but you get the idea.

I have Tweeny 2.0 sitting here just waiting to do something really useful

http://www.pjrc.com/store/teensy.html

Actually it's not that much of an over-simplification at all.  I've been using a RPi to control my DS2000 to have a set of extra hot buttons.  I wrote all the comms stuff for it using pyUSB and the USBTMC class is actually very simple to implement.  However I've been using a RPi because I wanted a button to that when pushed, it would dump a BMP to a network drive and record audio from a USB mic until the button was released, and store the MP3 with the BMP.  As a single button record capture if you will.

But it would be basic to port what I've done across to something like the Microchip USB framework, then any PIC with a USB OTG port could do this.  I don't have any experience with the Atmel USB framework, so it's unlikely that I'd port it across to that (and I don't have any usb OTG AVRs.)

Tell you what, I'll add it into my RPi code and post this afternoon.  There's probably way too many RPi's sitting around doing nothing at the moment anyway.
 

Offline mickpah

  • Regular Contributor
  • *
  • Posts: 148
  • Country: au
    • Yeti Hacks
Re: Sniffing the Rigol's internal I2C bus
« Reply #249 on: June 29, 2013, 01:08:11 am »


Actually it's not that much of an over-simplification at all.  I've been using a RPi to control my DS2000 to have a set of extra hot buttons.  I wrote all the comms stuff for it using pyUSB and the USBTMC class is actually very simple to implement.  However I've been using a RPi because I wanted a button to that when pushed, it would dump a BMP to a network drive and record audio from a USB mic until the button was released, and store the MP3 with the BMP.  As a single button record capture if you will.

But it would be basic to port what I've done across to something like the Microchip USB framework, then any PIC with a USB OTG port could do this.  I don't have any experience with the Atmel USB framework, so it's unlikely that I'd port it across to that (and I don't have any usb OTG AVRs.)

Tell you what, I'll add it into my RPi code and post this afternoon.  There's probably way too many RPi's sitting around doing nothing at the moment anyway.

Thanks Harv, I'll have a look when you post. The Tweeny is actually nice in that you can use arduino code for quick prototyping or C, plenty of GPIO for a button. I thnk it may well be overkill even for this. Let's hope I don't get stuck in the ceiling and get to it :)
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf