Products > Test Equipment
Sniffing the Rigol's internal I2C bus
<< < (404/899) > >>
mightyzen:
I just had to do some testing on the bandwidth of my v2 ds2072. It still runs the original firmware unlocked to 200MHz, simply because I am not ready to lose the 50 ohm termination. May be upgrading it later though.

I have looked at the output of a 125MHz crystal oscillator via:

1. 3300A probe with the ground lead (no bw limit)
2. 3300A probe with spring clip (no bw limit)
3. Coax 20MHz limit
4. Coax 100MHz limit
5. Coax no limit
6. Coax on a crusty hantek dso5072p hacked to 200MHz

The different probing/coax testing was inspired by Mike's excellent video series on the nano lcd reversing. Just shows again that at these frequencies the way you are probing makes a lot of difference.
m-joy:
Is it True that there was an 200Mhz trial on the ds2072?Because i can not Find that on my ds2072A.if this option has been removed, maybe there can not be keys for activating higher bandwidth on A-models...?
JDubU:

--- Quote from: m-joy on December 16, 2013, 10:20:24 pm ---Is it True that there was an 200Mhz trial on the ds2072?Because i can not Find that on my ds2072A.if this option has been removed, maybe there can not be keys for activating higher bandwidth on A-models...?

--- End quote ---

There was no 200MHz trial on a new DS2072.
marshallh:
gaijin:
I have a 2072 non A 1.0 hardware FW v.02.01.00.03 upgraded to a 2302 with DSHH.
Was wondering if anyone else tried accessing the CAN trigger/decode by SCPI

Querying the current trigger with :TRIGger:MODE? works for all but CAN.
Trying to set the trigger to CAN with :TRIGger:MODE CAN pops a message on the scope "Input is invalid"
:BUS1:MODE? will return CAN and :BUS1:MODE CAN will select CAN.
But I couldn't access anything under :BUS1:CAN like :OFFSet
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod