Products > Test Equipment
Sniffing the Rigol's internal I2C bus
MrsR:
I forgot to add,
I lost my trial versions I don't know what I did but I didn.t use the scope for about a month and when I switched it back on the Trial versions came back The funny thing is I have used the scope for more than 2 hours and the trial version time hasn't changed started at 2032 and still at 2032.????????
THANKS
Rachael
cidcorp:
Well I personally can't explain the suspended time trials, but I'm guessing if you are going to do a full unlock that this isn't going to be an issue.
I have a DS2102, all I did was upgrade to the new 00.02.01.00.03 firmware via the boot upgrade (ie. USB Key, Power, Help Key), not the process where the scope sees the newer firmware
on the USB key and asks if you want to upgrade. Made sure to reset to factory settings during first boot with newer firmware using the Left F6 key (repetitively pushing during boot). Then used the CAN & 300Mhz key codes generated by key generator (rigLOL website, you can link from here: http://rigol.avotronics.co.uk/mirrors/riglol/) to preserve the existing codes I already had (as with your 56M).
To generate a key, simply add your serial number (for your scope) to the text box called serial: DS12345678901, then add the option you want a key for, let's say DSHH for all options, leave the private key box empty, then hit the GENERATE key - Use this key in the Options Setup Screen on the scope.
I 'assume' you can use the DSHH code with your Scopes serial and be up and running with all the options without having any effect on the 56M option.
Just my 0.02
Chris
staze:
Okay, just upgrade my formerly 2072->2202 to the 2302 via uninstall, then clear FRAM, upgrade (via help), clear FRAM, install new key.
One thing interesting... I'm seeing weird "glitches" with the 1ns timebase, where it will show persistence, but then every once half second (or less) flick to no persistence for a frame or two, then back to persistence.
Scope is HW2, non-A. Key seemed to work just great. And now that I look at it, several of the timebases are showing this behavior. Looks like it might just be a function of the lower persistence times. Is that what others see? What do others leave their's at normally?
tlu:
I was have Marmad check it out and send it to Drieg as a bug if this is really the case.
MrsR:
--- Quote from: cidcorp on December 18, 2013, 03:12:22 am ---Well I personally can't explain the suspended time trials, but I'm guessing if you are going to do a full unlock that this isn't going to be an issue.
I have a DS2102, all I did was upgrade to the new 00.02.01.00.03 firmware via the boot upgrade (ie. USB Key, Power, Help Key), not the process where the scope sees the newer firmware
on the USB key and asks if you want to upgrade. Made sure to reset to factory settings during first boot with newer firmware using the Left F6 key (repetitively pushing during boot). Then used the CAN & 300Mhz key codes generated by key generator (rigLOL website, you can link from here: http://rigol.avotronics.co.uk/mirrors/riglol/) to preserve the existing codes I already had (as with your 56M).
To generate a key, simply add your serial number (for your scope) to the text box called serial: DS12345678901, then add the option you want a key for, let's say DSHH for all options, leave the private key box empty, then hit the GENERATE key - Use this key in the Options Setup Screen on the scope.
I 'assume' you can use the DSHH code with your Scopes serial and be up and running with all the options without having any effect on the 56M option.
Just my 0.02
Chris
--- End quote ---
Thanks Chris, Could you tell me where I can get a copy of the FW 00.02.01.00.03.
Rachael :-+
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version