Products > Test Equipment
Sniffing the Rigol's internal I2C bus
extide:
Depends on how you mod it.
So, I have a question of my own. Has anyone actually done quantitative tests on the DS4000 series regarding upgraded b/w? Has anyone looked at the mobo in a DS4014 vs a DS4024/DS4034/DS4054 to see if they are actually the same or any different? I think I saw some rise time tests on a modded DS4k, but I can;t remember, and is that really sufficient enough?
I am going to be getting a DS4014 here in the next few weeks, and will probably hack to unlock the decoding options and whatnot, but I am a bit iffy on upgrading the b/w .. Plus, 100Mhz is plenty for what I am doing at the moment anyways so I will probably leave the b/w alone.
ted572:
Free EMI Software for the DSA815 and other Rigol Spectrum Analyzers. And of course provides for a Linear or Log frequency display (as required for EMI reports): https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg545685/#msg545685
EE-digger:
--- Quote from: extide on November 07, 2014, 01:53:27 am ---Depends on how you mod it.
So, I have a question of my own. Has anyone actually done quantitative tests on the DS4000 series regarding upgraded b/w? Has anyone looked at the mobo in a DS4014 vs a DS4024/DS4034/DS4054 to see if they are actually the same or any different? I think I saw some rise time tests on a modded DS4k, but I can;t remember, and is that really sufficient enough?
I am going to be getting a DS4014 here in the next few weeks, and will probably hack to unlock the decoding options and whatnot, but I am a bit iffy on upgrading the b/w .. Plus, 100Mhz is plenty for what I am doing at the moment anyways so I will probably leave the b/w alone.
--- End quote ---
I'm interested in the answer to this also. The minimum timebase changes across these models from 5ns to 2ns to 1ns. Getting the 2ns or 1ns would be a definite plus (if you need it).
Den
H.O:
Hi,
When I upgraded my unit I did some very rudimentary tests - please take it for what it is.
Using a DG4162 to generate and feed a 100MHz, 100mVp-p sinewave my Tekronix 2465B (400MHz bandwidth) measured the signal (using cursors) to 100.5mV while the DS4014 reported 85mV - which is well above the 100MHz bandwidth specification of the DS4014.
After uppgrading the DS4k measured the exact same 100MHz 100mVp-p signal as 98mV.
Sparky:
In this post I reiterated the "License is unavailable!" message that sometimes accompanies attempts to install 300 MHz keys on Rigol DS2072A or MSO2072A models. I have been attempting to install the 300MHz "NS8H" key on an MSO2072A without success, and called out to some folks here for info, insight and testing. So far my tests and outcomes are:
1) Look for physical differences (e.g. "Hardware revision" resistor settings on the mainboard (DS2000_MB_V02.02)) between identical MSO2072A units (same hardware/firmware revisions from factory), of which one unit would and the other would not accept a 300 MHz key. No differences could be found.
2) Recompile rigup 0.4 from source code (on Linux machine) to see if any keys generated were different. Identical keys were generated.
3) Recompile rigup 0.4 with different (non-zero) "k_offset" so as to generate different valid keys. 200 MHz key can install. 300 MHz cannot install and gives the same "License is unavailable!" message.
4) Compare keys generated on my system with those generated by someone else (and for which the 300 MHz key did work) for the same memory dump. Differences in the PCs (32-bit and 64-bit) did not yield any differences in the keys. The above few tests effectively ruled out operator error, 32-bit/64-bit machine differences, or other similar issues.
The last outcome is that there are several license related messages stored in the firmware:
License invalid
License had installed
License has been used
License has been expried << yes, "expried" and not "expired"
License is unavailable!
License is none!
Despite the range of messages, the only message displayed when an invalid license is entered is "License is unavailable!". Given the range of messages available Rigol could check and distinguish between "invalid" and "unavailable" keys. But, as the same message is always returned (for an invalid key) it is not possible be sure the reason the license was rejected.
It is possible there is a firmware level check that detects the 300 MHz key and rejects it, but if this were true the 300 MHz key would be rejected on all MSO2072A units. Furthermore, whatever the type of check in place (firmware or hardware), it would seem Rigol could duplicate it for rejecting 200 MHz and other options, but this hasn't been done. So, a firmware or hardware related check doesn't seem likely.
I can think of two possibilities:
1) The 300 MHz key is sometimes incorrect, and the DS/MSO detects and rejects it as such, just like any "made up" (wrong) license key. That is, there is a "fence-post" type bug somewhere in rigup/riglol/miracl etc. or a misunderstanding with some aspect of the key generation that is occasionally exposed.
2) There is a bug in the scope firmware, causing sometimes valid 300 MHz keys to be rejected.
Anyone have further thoughts?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version