Products > Test Equipment
SainSmart DDS120 & DDS140 USB Oscilloscope
mmark:
--- Quote from: merbanan on April 02, 2016, 06:59:33 pm ---Here it is. This firmware might be compatible with the Hantek 6022BE software.
--- End quote ---
Merbanan,
how do you get the firmware into the DDS120? Does sigrok/pulseview download it automatically when you start or do you have to download it manually? If so, could you tell us how to do this? I am still trying to get pulseview compiled on my macbook...
Thanks a lot,
M.
doctormord:
Here's the possible trigger approach:
EDIT: Obsolete
Compiled: https://dl.dropboxusercontent.com/u/5641160/DDS120_OpenHantek_Trigger_V1.zip
Source: https://dl.dropboxusercontent.com/u/5641160/DDS120_OpenHantek_Trigger_V1-SOURCE.zip
See: https://www.eevblog.com/forum/testgear/sainsmart-dds120-usb-oscilloscope-(buudai-bm102)/msg911658/#msg911658
for actual code
It is implemented in buudai_control.cpp
Works for rising signals.
CHANGES:
- setup highest voltage-divider on start (5V)
- implemented trigger-hack
BUGS/FIXES needed:
- Make trigger work with slope-function (QT button action)
- Make trigger work on start up (it is not working on the first start or when changing trigger source channel, you always have to click on the small trigger-level-arrow once to make it work)
- Disable/Hide Buffersize Menu (action is actually commented out), as Buffersize is set according to timebase
- Make trigger more solid to noise (dunno how)
- Make trigger work with fast risetimes/transients (triggering on square-wave is not really working well)
I added some comments to the parts i changed.
Regards,
doc
doctormord:
--- Quote from: mmark on April 03, 2016, 02:49:15 pm ---But the 1k buffer glitch / restart / discontinuity still seems to be there, see attached screen shot. I believe that we need an updated firmware on the DDS120/140 to fix this issue correctly, so I'll try to get merbanan's firmware running with openhantek or pulseview.
M.
--- End quote ---
There isn't on mine. As far as i know, this problem is on the 6022 as well:
https://github.com/OpenHantek/openhantek/issues/7#issuecomment-168538575
The latest source/binary reintroduced some glitching, so this finally needs to be fixed. Skipping just 1024(*2) bytes from the data received did not fixed it in any way. I actually use the "readmulti" to get bigger blocks - so to have valid 1k data per channel you'll need to read 4k overall and drop the first 2k, would guess. :-//
Edit:
I don't know how to make a proper "release" build. I did a "release" to get the .exe and then copied all missing .dll files to that folder until it started. :-/O
doctormord:
Just ran some USBPcap to see what's going with the trigger in original Buudai software, the triggering is done in their USBInterface.dll in software. :-//
Edit:
Hooking up the scope on a dedicated USB-hub removed (nearly) all glitches, triggering on squarewave works then. :D
Changes for next version:
- Markerslidersteps 0.2 -> 0.1 of DIV - DONE
- Move Waveform by Triggerpositionslider - DONE
- Select triggervoltage in 0.01V steps - DONE
merbanan:
--- Quote from: mmark on April 03, 2016, 02:56:21 pm ---
how do you get the firmware into the DDS120? Does sigrok/pulseview download it automatically when you start or do you have to download it manually? If so, could you tell us how to do this? I am still trying to get pulseview compiled on my macbook...
--- End quote ---
When starting pulseview, libsigrok will scan for usb devices registered to a driver. The hantek6xxx driver will try to load the firmware and after that it is go time. So if you are compiling everything yourself you need to get my 1 patch to libsigrok and build and install my firmware package.
FX2load should be able to manually load the firmware also. I did not test it myself but it should work in theory. Upon loading the firmware the device should renumerate as a new usb device.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version