Products > Test Equipment
Sniffing the Rigol's internal I2C bus
whotopia:
Just got a new DS2072A. I converted to DS2202A with all options (via old FW and old private key).
Will the scope function correctly with the old firmware? Has anyone noted any problems?
Also, I 'lost' the serial number in the process, and the scope is now using default value. On the DG4000 via cengen (see elsewhere on this forum) you can generate a license.GEL file through which one can also apparently mod the serial number. Is such a thing possible for the DS2000? Is there anyway to restore the serial number ? Is there any real harm in having the default?
The scope doesn't ever try call Rigol if ethernet connected right?
Thanks
Steven
AndersAnd:
--- Quote from: Fagear on December 30, 2013, 11:59:18 am ---
--- Quote from: EV on December 30, 2013, 11:39:18 am ---
--- Quote from: marmad on December 30, 2013, 03:46:26 am ---
--- Quote from: poida_pie on December 30, 2013, 03:34:25 am ---BUG in latest f/w, 02.01
Delayed sweep malfunctions.
To reproduce:
Ch2 must be enabled, Ch1 optional
acquire: 7M samples, normal
trigger: ch1 or not important, Auto or Normal seems to have no effect
main timebase 500us/div, delayed t.b. 100 us/div or something
Then when you move the delayed t.b. towards 1 ns/div all seems well until you select 1 ns/div..
It locks up for about 10 seconds, no waveform update, no response to keys.
Then it comes good and lets you go back to 2ns/div
--- End quote ---
I see what you're talking about, but as mentioned earlier in the thread in regards to problems with the 1ns time base:
It's another error (and there's a few of them) in an, as yet, officially unimplemented - and perhaps unfinished? - portion of firmware. As far as I know, Rigol has not started selling BW updates - but if/when someone on the forum has a DS2302A (or DS2302A-S), we can find out if the error(s) exist in the 'official' working version - and if so, report it to Rigol.
I suggest disabling 300MHz on non-A HW v.1 models. Not only is it buggy (I've had a couple of crashes from it), but it's not really perfectly implemented in the input stage.
--- End quote ---
How is it possible to uninstall only BW option?
--- End quote ---
Do ":SYSTem:OPTion:UNINSTall" and then generate new keys without 300 MHz option (with 200 MHz for example) and install them.
It can be two keys: DSAZ (200 MHz, MEM, DC, AT) then DSEA (CAN).
--- End quote ---
Or simply use DSEZ instead as the only key, to combine CAN with all the options included in DSAZ (200 Mhz, Mem, Dec and Trig) into a single key.
Combining the two tables below DSEZ should install CAN, 200 Mhz, Mem, Dec and Trig.
So DSEZ should be the one key solution to use for non A DS2000 with HW 1 and the latest FW if you want 200 MHz with all available options including CAN but without 50 ohm which is not implemented on HW 1 anyway.
EZ derived from the two tables for y (3rd letter) and x (4th letter) below (DSyx):
--- Code: ---y CAN, 300, 50ohm | x 200, 100, Mem, Dec, Trig
E on == == | Z on == on on on <- All 2202
--- End code ---
Table for 3rd letter (y):
--- Quote from: Carrington on December 11, 2013, 01:59:54 am ---Is this correct?
IMHO would be interesting know the entire table, and thus activate the desired options with a single key.
--- Code: ---Code table: Use DSYX for a official key, and use VSYX for a trial key.
Y CAN, 300, 50ohm
A none
B == == on
C == on ==
D ?? ?? ??
E on == ==
F ?? ?? ??
G ?? ?? ??
H on on on
J ?? ?? ??
K ?? ?? ??
L ?? ?? ??
M ?? ?? ??
N ?? ?? ??
P ?? ?? ??
Q ?? ?? ??
R ?? ?? ??
S ?? ?? ??
T ?? ?? ??
U ?? ?? ??
V ?? ?? ??
W ?? ?? ??
X ?? ?? ??
Y ?? ?? ??
Z ?? ?? ??
--- End code ---
--- End quote ---
E instead of A as 3rd letter enables CAN but still leaves out the 300 MHz BW and 50 ohm which is not implemented on HW 1 anyway.
Table for 4th letter (x):
--- Quote from: Carrington on December 10, 2013, 03:16:35 pm ---Cybernet has done it, again! *ole* :-+
Now I'm very busy and I can't test anything (check the BW for example).
Anyway. How is the new table?
--- Quote ---Code table: Use DSAx for a official key, and use VSAx for a trial key.
x 200, 100, Mem, Dec, Trig
A none
B == == == == on
C == == == on ==
D == == == on on
E == == on == ==
F == == on == on
G == == on on ==
H == == on on on
Note: keys A..H wont change the model, only ADD an option.
2102:
J == on == == ==
K == on == == on
L == on == on ==
M == on == on on
N == on on == ==
P == on on == on
Q == on on on ==
R == on on on on <- All 2102
2202:
S on == == == ==
T on == == == on
U on == == on ==
V on == == on on
W on == on == ==
X on == on == on
Y on == on on ==
Z on == on on on <- All 2202
DONT USE BELOW Not recommended, as activates 2102 and also 2202:
2 on on == == ==
3 on on == == on
4 on on == on ==
5 on on == on on
6 on on on == ==
7 on on on == on
8 on on on on ==
9 on on on on on
--- End quote ---
--- End quote ---
Z as 4th letter for 200 Mhz, Mem, Dec and Trig.
And here's the table to convert between binary values and letters: https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg322495/?topicseen#msg322495
zombie28:
--- Quote from: NikWing on December 30, 2013, 12:39:10 am ---ok, I found out about the 0x before I read your reply lol
it says licence is unavailable
--- End quote ---
It appears that Rigol changed not only ECC keys, but also license code format.
PA0PBZ:
I tried option DSBA on my non-A model with the latest firmware, it said "option installed" but I can't find any changes, certainly not the 50 Ohm option. Would there be a key for that since it is build into all A models as a standard?
marmad:
--- Quote from: PA0PBZ on December 30, 2013, 04:08:03 pm ---I tried option DSBA on my non-A model with the laters firmware, it said "option installed" but I can't find any changes, certainly not the 50 Ohm option. Would there be a key for that since it is build into all A models as a standard?
--- End quote ---
I think it's unlikely. It's a standard feature on new A-models (and so one of their new selling points vs. non-A models), so it I doubt it would ever be sold as an 'option' specifically for HW v.2 non-A owners - thus no key. But perhaps the FW can be patched to enable it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version