-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
THD measurement #132
Comments
Thank You very much! |
Did you read the monster thread from "down under"? It shows some HW mods. |
Yes, I did. Thanks. P.S. |
I see. I didn't visit eevblog for a longer time - you have a nice collection of data!
Also this is a no-go. The input voltage of the ADC (Ain=-0.5V..+0.5V, /Ain=0) is far outside the specification (common mode voltage: +0.7V..+1.1V). I saw that you thought about the AD8138 - in the end it would be easier to buy a better scope. The easiest solution for this redesign would be to use a cheap EzUSB board as digital backend and build a separate analog front end. It will run mostly without SW change, only the gain and AC/DC switching must move from port C and E to port A, which would lead to a new firmware. Just my 2 ¢ Martin
I implemented massive oversampling (up to 200x) to get down to 100 Samples/s while the min samplerate from firmware is 20 kS/s, please have a look at the source. |
Hi! If we add another AD8065 like schematics below Can You comile a version for Windows without restriction of samplerate (48MB)? |
This will not work as the data sheet tells: Low and full speed data rate: 1.5 Mbps and 12 Mbps and Hantek6022 uses High speed 480 Mbps.
32 and 64 bit versions for testing (available for 6 months):
I have no access to this file :( |
Super! Yes, ADuM4160 is slow. OWON in other hand use it + additional power isolator. If You use LTSpice, here (available for 1 month) are sim files for schematics above P.S. Schematic of AD8065 is mess, but I was curious to see what behavior such a configuration will have. After all AD8065 is cheap :) P.S2 |
... because OWON is USB 1.1 while Hantek is USB 2.0 high speed, this is described in EEVBLOG: "Where the Hantek just uses an EzUSB micro for interfacing the ADC to USB, the Owon includes a Silicon Labs SiM3U156 32 bit ARM Cortex-M3 CPU together with a Xilinx Spartan-3 FPGA. There's clearly a lot more happening on-board than in the Hantek. Presumably the triggering is all handled on board (especially as there is a Trigger-out), together with data compression needed to pipe the data via USB1.1 at decent refresh rate. It also results in very low PC overhead with minimal impact on running other applications even on a low-end PC. The 5k memory depth is clearly a less desirable side effect. |
Seems I have missed this post... |
The scope uses high speed 480 Mbps bulk transfer, defined by the firmware. |
Thanks! |
Hi!
Great work, big thanks!
Would it be possible to implement a THD measurement (audio amplifiers, etc.)?
The text was updated successfully, but these errors were encountered: