Products > Test Equipment
REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol
marmad:
--- Quote from: Xyphro on July 06, 2013, 10:32:25 pm ---If the spec says true 500uv/div support it is actually wrong due to this bug, because the main purpose should be in most cases to look at the trace on the screen.
--- End quote ---
Sorry, this is NOT a bug. It just has to do with sample -> display scaling. As I mentioned before, the data in display memory is heavily manipulated - via decimation, interpolation (if on) and display scaling (the display is 400 pixels high - so ALL sample data is scaled for the display height). If you set the vertical scale to 550uV/div, you again have LSBs with 0 and 1 in display memory.
I repeat: THIS IS NOT A BUG.
Teneyes:
--- Quote from: Xyphro on July 06, 2013, 10:37:32 pm ---I agree, it is not a serious issue :-)
Just a funny fact.
--- End quote ---
Just a specific setting on the Scope
Check out this display in DOTS , Lots of resolution here
A Capture of the change of frequency from 2.2Mhz up to 52.2 MHz (manually )
with persistance set to 10 sec ,then freeze with a "Stop"
zibadun:
--- Quote from: marmad on July 06, 2013, 11:38:48 am ---
How to do it? It's not rocket science - over-sample, then randomly decimate for the 'required' sample speed = stochastic sampling. Done.
--- End quote ---
If it's so simple why don't you implement it in RUU marmad?
Chalky:
--- Quote from: Xyphro on July 06, 2013, 09:08:01 pm ---I found a new bug while programming this here: http://www.xyphro.de/blog/index.php?entry=entry130705-223439
The DS2072 does not accept an INITIATE_CLEAR class command over the USB interface. This command is a required command according to the USBTMC specification. The Scope does not react at all to it, and the USB transfer times out.
--- End quote ---
Yeah also doesn't implement some of the LXI 1.3 stuff over TCP/IP, such as 10.2 rule get XML ID document via '<hostname>/lxi/identification'
marmad:
--- Quote from: zibadun on July 07, 2013, 04:19:06 am ---If it's so simple why don't you implement it in RUU marmad?
--- End quote ---
There's no way I could get sample data fast enough from the DSO to do it in real time. I could do it slowly - but what good would that be?
Anti-alias is ideally something you want to have while probing unknown signals at slower horizontal speeds - but once you figure out what you're looking at and adjust your settings accordingly - it becomes a bit irrelevant. But it's something that needs to take place between the sampling and the display of the data - and so even though the basic implementation (in terms of math) is not complex - it DOES have it be done quickly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version