For the need of an External trigger and 2GSa/s ,
It is best to use Chan 2 and External, this is a Work around to avoid having to power-off and on for uses of Chan 1 and external Trigger .
Yes no offset if using Chan 1 and/or Chan 2 as trigger, (1GSa)
Go back to old msg for Dots at display of 2GSa/s and set to External
Does someone have 2 output function gen with phase offset to test
mmm I'm thinking of DG3062
BTW, I'm just about to upload a bug-fix for RUU (version 1.51) for you. I found one line of code with a TypeConversion mistake. When you get a chance, please download the new version, switch your Windows settings back to ',' for decimal point and try to enter 'Zoom Markers'. I think it should work fine for you now.
OK to more complete here are #1 Chan1 with EXT , dots, and Chan 2 with Ext and Dots
Yes, it works now.
Thanks!
No worries, there's no rush. Thanks for the assistance guys.
Screen saver works! FW 1.00.05 DS2202
However now I still have the initial problem.. No screensaver
Is it possible we could get one other owner with a DS2072 and FW 01.00.05 to check their screen saver? Sparky?
I can try testing the 2G Sa/s on both Ch 1 and Ch 2 with ext. trigger, as there are still questions on that issue... I have a DG4062 near by if we need two signals with phase offset.
I can try testing the 2G Sa/s on both Ch 1 and Ch 2 with ext. trigger, as there are still questions on that issue... I have a DG4062 near by if we need two signals with phase offset.
Great! There is clearly a misunderstanding about our bug report vs. what Rigol thinks the problem is/isn't.
If you could just check (using dots) what the real sample rate is when the DSO displays 1 GSa/s after choosing CH1 & Ext. Trigger - then reboot and check it again after it displays 2 GSa/s - we would know for sure if it was an actual sample rate setting bug - or a display of sample rate bug.
Test done! Seems the 2G Sa/s is the real deal when using Ext trigger (after reboot)! So, display on the scope is correct, and it is indeed bug in the firmware which requires reboot of the scope to get this 2G S/s.
Let's forward this clarified bug report to Rigol via our friend drieg!
Here are the same pictures from my scope DS2202, which Sparky sent :
From the discussions here, it appears that I should upgrade to firmware 1.00.05 when the unit arrives (assuming it is not already at that level). Can someone please let me know how I would go about getting the firmware?
Excellent! So now we have confirmed this bug for both DS2072 and DS2202! I guess single firmware fix will resolve the problem for all DS2000 series.
Be sure to read the warnings and follow instructions upgrading the firmware --- only do upgrade during BOOT! Search this thread and the above thread for details on the procedure.
It is good that there is no trigger level line on the trace as the trigger level is unrelated to the displayed signal, but it this test by connectting to the same point , we know they are the same and can realize the offset.
From the discussions here, it appears that I should upgrade to firmware 1.00.05 when the unit arrives (assuming it is not already at that level).
DS2072 FW 1.00.02
Can someone please verify .