Is a changelog available for the latest DS2000 firmware (00.02.01.00.03)?
Would someone with HW v.2 / model A like to try it as well - to see if Rigol tightened the specs up in the newer hardware?
You just need to send a > 100k sine/square wave into CH1 (edge trigger) and Trigger Out to CH2 - then use a long persistence (e.g. 2s) to get an idea of jitter. The distance between the trigger point and the (averaged) rising edge of the Trigger Out signal is the delay (plus or minus the farthest distance of other edges).
Then just switch the sine wave input (and edge trigger) to External Trigger and check again.
This is from HW2 (non A), Firmware 00.02.01.00.03:
Thanks, JDubU. It looks more or less identical with HW v.1. I'm guessing, given their general design, they couldn't make it any better without some major changes. 160 - 230ns is certainly usable; if they would allow External Trigger to be a source to the other trigger types (for cross-triggering purposes), the slightly longer-than-normal delay would matter even less.
I installed BW 300M option to my DS2202. Here are rise time tests with Tek type 284 pulse generator.
In pic 1 I have used BNC cable with 50 ohm feed through terminator. Rise time has changed from 1.4 ns to 1.2 ns and over shoot from 8 % to 10 %. It is not a big change.
In pic 2 I have used 10X probe with 50 ohm feed through terminator between probe tip and generator output connector. Rise time is about 1 ns and over shoot 17 %.
What HW version does your DS2202 have?
Anything special I should examine a used scope for ?
When you said 200M+300M do you mean you are able to set the bandwidth limit for this?
When you said 200M+300M do you mean you are able to set the bandwidth limit for this?
No, if you go from DS2072 to DS2202 the options screen shows the 200 Mhz bandwidth. If you then update to the newest fw and apply the DS2302 code you end up with both 200 Mhz and 300 Mhz in the options screen. I don't think it is a problem though.
and that's not a new bug?
dropping from 47k to 17k while nearly all other values got better?
and that's not a new bug?
dropping from 47k to 17k while nearly all other values got better?
and that's not a new bug?
dropping from 47k to 17k while nearly all other values got better?
It is quite likely that is a new bug. But they release a new Firmware again since a long time. After many new devices offers maybe they have more time to release new fixes....