Products > Test Equipment
REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol
marmad:
--- Quote from: JDubU on December 17, 2013, 06:23:38 pm ---Do these waveform update rates change if you change the frequency of the input signal (change the trigger rate)?
--- End quote ---
I always use a 1MHz sine - but I've noticed there is some variation (maybe +/- 5%?) based on the trigger frequency - just as there is based on the input levels (and virtually anything else). I've never done extensive testing, but feel free to work it out if you'd like ;)
Galaxyrise:
--- Quote from: NikWing on December 17, 2013, 05:14:06 pm ---and that's not a new bug?
dropping from 47k to 17k while nearly all other values got better?
--- End quote ---
I find it more likely that the old figure was caused by a bug (billed as a feature), since it was such a discontinuity. But like marmad says, it's hard for us to know what's an intended consequence of balancing features and what's an unintended drop in wfrm/s. Hopefully someone at Rigol knows :)
marmad:
Found a bug in the new firmware - incorrect setting of the sample rate in DOTS mode at certain time bases it appears to be a bug between sample and display memory.
It seems to affect AUTO/14M/56M memory settings while in DOTS mode @ time bases >= 5us/div.
If someone still has FW v.01.01.00.02 installed, could they please double-check to make sure this bug is NOT present in that FW?
To test:
Single channel on; DOTS mode; test signal input (e.g. 1MHz sine); AUTO memory setting.
Go from 100us/div to 200us/div - and watch the image change. The sample rate appears to be wrong for the displayed image (it's supposed to be 2GSa/s):
marmad:
Following up on the bug discovered: problems in DOTS mode @ >= 5us/div.
This waveform chart shows how the update rates for DOTS mode are always better than VECTORS until 5us/div, at which point they get drastically worse. Something is definitely wrong here:
JDubU:
--- Quote from: marmad on December 17, 2013, 07:07:46 pm ---Following up on the bug discovered: problems in DOTS mode @ >= 5us/div.
This waveform chart shows how the update rates for DOTS mode are always better than VECTORS until 5us/div, at which point they get drastically worse. Something is definitely wrong here:
--- End quote ---
HW2, latest firmware.
I can confirm your waveform update findings in Dots vs. Vector mode at timebases >= 5us/div.
In regards to your previous post: Dots mode 100us --> 200us. The 200us setting does produce a display with unique dot artifacts at that one setting but, if I stop the sampling and zoom in, the sampling rate does match what is displayed at the top of the screen (by counting the dots per horizontal division).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version