Products > Test Equipment
REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol
ted572:
Thanks, Ted. Regardless of the 2014 date on the cover, it seems slightly dated (there's a 2012 copyright inside), although I imagine the verification routines are (mostly) still valid. It keeps referring to the model as DS2000 (the DS2000 exists no longer; there is now only the DS2000A) and it doesn't mention the 300MHz BW DS2302A.
[/quote]
Hi marmad:
Yes it is for the DS2000 (non A) that we have. They are still working on the newer DS2000A document.
Circlotron:
My DS2072, did a single shot trace this morning at 2 sec/div. Waited till it said "WAIT" (confusing, means scope is waiting for trigger, not for you to wait...) then switched my cct on and this caused a trigger because it said "TRG" or suchlike, can't remember now, then eventually after maybe 20 seconds or so it said "STOP" in red. After about five minutes there was still nothing displaying on the screen so I moved the time/div kob back and forth one click and BYU there was my trace! Interestingly, it didn't start right on the trigger point but about 2.5mm to the right.
This display not showing up immediately only seems to happen at slower sweep speeds; high speed ones appear as soon as the scan is finished. Not sure what the borderline between high and low speed is yet though. Just that at 2 sec/div it acted up. Any ideas?
Teneyes:
Not sure what the borderline between high and low speed is yet though. Just that at 2 sec/div it acted up. Any ideas?
[/quote] You notice the delay when at about 2 seconds, the DS2000 collects data point before the trigger event. the trace is not displayed until the trigger occurs, so I put the trigger point on the left side of the display for slow scan rates. Try putting the trigger point on the Right and time the delay from the "RUN" indication until the trace is displayed at 500ms/div.
marmad:
--- Quote from: Circlotron on September 19, 2014, 01:21:29 am ---My DS2072, did a single shot trace this morning at 2 sec/div. Waited till it said "WAIT" (confusing, means scope is waiting for trigger, not for you to wait...) then switched my cct on and this caused a trigger because it said "TRG" or suchlike, can't remember now, then eventually after maybe 20 seconds or so it said "STOP" in red. After about five minutes there was still nothing displaying on the screen so I moved the time/div kob back and forth one click and BYU there was my trace! Interestingly, it didn't start right on the trigger point but about 2.5mm to the right.
This display not showing up immediately only seems to happen at slower sweep speeds; high speed ones appear as soon as the scan is finished. Not sure what the borderline between high and low speed is yet though. Just that at 2 sec/div it acted up. Any ideas?
--- End quote ---
The length of time it takes to be ready for a trigger (WAIT) and then display the acquisition is a function of the time base setting * 14 -OR- memory depth * sample speed, whichever is longer. The trigger position affects the division of that length of time. Did you ever wonder what that display graphic at the top center of the screen was for?
Examine the following 5 images - all made at 1s/div. Pay attention to memory depth, the graphic at the top center of screen, and the WAIT/DISPLAY times which I have scribbled in:
1) 14k sample size and center trigger position.
2) 14M sample size and center trigger position.
3) 14M sample size and left trigger position.
2) 56M sample size and center trigger position.
3) 56M sample size and left trigger position.
EDIT: BTW, posting USB screen captures when you have problems would help us point out what mistake you're making.
Teneyes:
--- Quote from: marmad on September 19, 2014, 03:18:12 pm ---BTW, posting USB screen captures when you have problems would help us point out what mistake you're making.
--- End quote ---
@Circlotron
Yes, Screen displays are helpfull ,and I like using Marmad's RUU software;
as it is fast and can create GIFs to show recorded displays, with Menu on side to show settings
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version