SainSmart DDS120 & DDS140 USB Oscilloscope

[luminary6]

Thank You for binary! Windows 7 x64, DDS120 from SainSmart worked.

[swedgin]

So I got this working before on ubuntu. I did however a reinstall and tried to install openbuudai again. There isn't a specific guide for linux, only bits and peaces across several files. I tried to document while I was installing for future references but I couldn't complete it. I don't know where to find the drivers for DDS120 so I can extract them with extractfw.

This is what I did to install it. I can open the program but my oscilloscope can't be recognized.

sudo apt-get install libqt4-dev libfftw3-dev libbfd-dev

cd /directory/of/choice
git clone https://github.com/doctormord/OpenBuudai

cd Source

nano OpenHantek.pro
uncomment line 11 and 15, comment line 10 and 14

qmake
make
make install

Download dsoextractfw from https://sourceforge.net/projects/openhantek/files/

tar xvjf openhantek-extractfw-0.7.0.tar.bz2
cd dsoextractfw
./configure
make
make install
cp 90-hantek-dso.rules /etc/udev/rules.d/

[swedgin]

So I forgot the .sys file. But I have still problems. I've installed the driver on a windows 10 machine and copied the winusb.sys file to my ubuntu 16.04 laptop. When trying to extract the firmware I get the following error.

speklap:openhantek-extractfw$ ./openhantek-extractfw winusb.sys
BFD: winusb.sys: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .text
BFD: winusb.sys: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .rdata
BFD: winusb.sys: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .data
BFD: winusb.sys: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .pdata
BFD: winusb.sys: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .idata
Section .data found (starting at 0xfc00, 512 bytes)
Symbol _firmware found (offset 0xffffffffffff0400, 0 bytes)
Symbol _loader found (offset 0xffffffffffff0400, 512 bytes)
Can't get firmware contents: Bad value

Can someone host a valid .sys file or help me get around this?

Greatly appreciated

[savvej]

I'd like to make sure I've not made/forgotten anything silly first.

OpenBuudai was never tested with the DDS140, so it needs complete implementation of the different command set. (As the DDS140 uses an FPGA)

Well, that's exactly the kind of "silly" I was expecting

Regarding the command set, and based on PapaLukas' Logic140, it looks almost identical between the 120 and the 140 (OpenBuudai types vs. Logic140 init code).

Anyway, time to do my homework

Regards,

Hi,

As far as the Logic140 code is concerned, I was able to compile it under Linux-Ubuntu using neatbeans and gcc compiler.The JNI library had to be ported to call corresponding functions from libusb available in Linux, compared to the winusb implementation provided.
The gui seems to work and connect to the DDS140 scope when invoked as a root. See snapshot attached, for the case when the test signal from the scope is probed in CH1.Though I think the GUI as well as the implementation is not great especially for the oscilloscope version, since there is lot of data loss happening (The red region which is seen in the gui) . Also zooming/panning function seem to be dsyfunctional.

Thus,I wanted to tryout OpenBuddai.I was able to compile it on linux and run it. The device was detected  but data capture is failing with similar error as you posted. Since the initialization works fine in Logic140, we should be able to port it in OpenBuddai and a quick glance of the code seems like the sequence is similar. Maybe some minor difference here and there. Let me know if you want to assist me in the bringup.

Regards,
Shabbar

[savvej]

Hi All,

Just an update.

I was able to edit the OpenBuddai code and edited initialization sequence and the getSamples sequence as per the Logic140 code.
The getSamples sequences polls until receiveing a 0x21 before reading the buffer, as in Logic140 code and this seems to resolve the timeout issue. And, surprisingly, I was able to get something on the scope when probing the scope's signal. See attached below.Though I am unable to capture the square wave test source train properly.

May be, many of the other settings related to voltage /sampling/timebase settings too will need to be updated.I think we are not too far from getting this working.

@doctormord and or @papalukas, if we can have a quick skype call, we can figure out what is missing or needs to be tweaked and get it functioning properly.

Regards,
Shabbar

[UnSeen]

Hello guys
The vendor's software drives me crazy. And I can't find any working link to versions newer than 1.2. Could someone post it please?
Have anybody managed to run OpenBuddai with DDS140 yet?
I've just built it and it prints "Getting sample data failed: Operation timed out" as supposed

I was able to edit the OpenBuddai code and edited initialization sequence and the getSamples sequence as per the Logic140 code.
The getSamples sequences polls until receiveing a 0x21 before reading the buffer, as in Logic140 code and this seems to resolve the timeout issue.

If would be cool if you could share your modified code. Thanks

[keropi]

anyone has a working link for windows software 1.50 ?
thanks!!!

edit:
I have uploaded the ISO that contains 1.50 + drivers + videos , suitable for both DDS120 and DDS140

https://www.mediafire.com/file/4bkw7vsc7fy9755/SainSmart-DDS120-DDS140.rar/file

[mmark]

Just a heads up: I spend the last couple of days adding support for the Sainsmart DDS120 to the new and improved OpenHantek6022. It uses the sigrok firmware for the DDS120.
Works already pretty good (tested on MacOS 10.14 and Ubuntu 18.04 with qt5!).

Source is here: https://github.com/msiegert/OpenHantek6022 for now and hopefully will get merged into Ha-Ro's original repository.

Since there also is a sigrok firmware for the DDS140, I expect that after adding the firmware (or running sigrok-cli first to upload the firmware to the scope) and adding the USB PID/VIDs for the DDS140, it should also work.

[kimbergirl]

does somebody want my dds-120 before i smash it to bits?
or is there a solution to get old old crappy version of .NET to install on win 10?

tried everything....

[mmark]

Try https://github.com/OpenHantek/OpenHantek6022/releases/download/v2.17-rc5/OpenHantek-Win-x64-Release-b169.zip (64 bit) or https://github.com/OpenHantek/OpenHantek6022/releases/download/v2.17-rc5/OpenHantek-Win-x86-Release-b169.zip (32 bit).

DDS120 support has been integrated into OpenHantek6022...

 

[kimbergirl]

thanks for the quick reply
i still dont regret the nastygram that is in the Sainsmart inbox
back to work on the electric car......

[Rio]

@mmark: Thanks for your effort. I used the DDS120 easily with the last version of OpenHantek6022 in Win7...

[kimbergirl]

thanks
someday i will get frustrated enough to get a stand alone O scope not tied to the strange fleeting whims of programmers and a separate compute box

[luminary6]

Have problem with DDS120 and OpenHantek6022 (b188)
I try use my DDS120 again, find new software OpenHantek6022 (b188) and try configure all again.
I see that OpenHantek6022 not read calibration data from DDS120 and zero is not in zero and gain wrong.
This is normal?
Anybody try use OpenHantek6022 with DDS120?
Your device is calibrated?

I make calibration file C:\Users\USER\.config\OpenHantek\modelDDS120.conf
with content (for my DDS120):

Code: [Select]

; OpenHantek calibration file
; individual calibration values for DDS120
; will be read by .../src/hantekdso/modelDDS120.cpp

; filename is modelDDS120.conf
; copy into ~/.config/OpenHantek (Linux)
; copy into %USERPROFILE%\.config\OpenHantek (Windows)

; multiply channel to get the correct gain
[gain]

ch0\20mV=1.250
ch0\50mV=1.244
ch0\100mV=1.241
ch0\200mV=1.298
ch0\500mV=1.164
ch0\1000mV=1.199
ch0\2000mV=1.205
ch0\5000mV=1.203

ch1\20mV=1.231
ch1\50mV=1.235
ch1\100mV=1.252
ch1\200mV=1.322
ch1\500mV=1.193
ch1\1000mV=1.219
ch1\2000mV=1.221
ch1\5000mV=1.224

; add offset values
[offset]

ch0\20mV=6
ch0\50mV=6
ch0\100mV=6
ch0\200mV=5
ch0\500mV=6
ch0\1000mV=5
ch0\2000mV=5
ch0\5000mV=5

ch1\20mV=5
ch1\50mV=5
ch1\100mV=5
ch1\200mV=5
ch1\500mV=5
ch1\1000mV=5
ch1\2000mV=5
ch1\5000mV=5


I write this message for any who want use OpenHantek6022 software with SainSmart DDS120 and will face the same problem.

[horo]

Hello luminary6,

Thx for providing your conf file. OpenHantek6022 already does provide a template for this file, but with gain = 1.0. I had a quick look into the input gain selection there and there in this thread and will update the model file accordingly, so that even without a conf file the gain error will not become too big, a rough estimation would be:

Code: [Select]

specification.voltageLimit[0] = { 32 , 80 , 160 , 155 , 170 , 165 , 330 , 820 };
specification.voltageLimit[1] = { 32 , 80 , 160 , 155 , 170 , 165 , 330 , 820 };
If you build your own binary, please check, otherwise I will put it into my source later today.
If you're on windows, you can get a binary of every commit from appveyors artifacts. There are also the older builds available.

Martin

EDIT:
I've created a new issue #39 on github.

EDIT2: Closed issue, luminary6 please check if the scope behaves better when used without conf file.

[horo]

Hello luminary6,

I updated the DDS120 handling again, please check the latest build:
https://ci.appveyor.com/project/Ho-Ro/openhantek6022/build/artifacts
If you want to test older Win builds, there's also a history:
https://ci.appveyor.com/project/Ho-Ro/openhantek6022/history

Martin

[luminary6]

1) I download b205 version.
2) I rename my calibration config file (disable).
3) Connect DDS-120 to USB (probes are disconnected).
4) Run old version (b188, x64) and get zero at:
CH1 = -0.62 Volt
CH2 = -0.41 Volt
5) Reconnect DDS-120 to USB.
6) Run new version (b205, x64) and get zero at:
CH1 = 5.96 Volt
CH2 = 6.01 Volt

Changes in software is wrong.
Also i think you can not set calibration data for all users (if different models of DDS-120 have different electronic parts etc ...)
May be good way is revert calibration data to 1.0
But official software is working normally and measure is precise, how it working i do-not know. May be official software read calibration data from device?

[luminary6]

I read your message at github and understand that you correct only "gain", but "offset" value you remove from source.

"Ok, no problem, I've just removed your 1.18 : 1.21 correction if there is no conf file and therefore adjusted the specification values accordingly, so it should give a +- 5% accuracy for 1st time users - only offset has to be adopted individually."

I was remove gain section in my config file, and run new version (b205) with only offset in my config file.

EDIT2: Closed issue, luminary6 please check if the scope behaves better when used without conf file.

Voltage gain is fine, measured values close to real.

But becouse voltageLimits is divided by calibration value (how i understand after see source code), my old calibration data is not valid for new version of program, and need recalculation.

[konkdekilo]

I wanted to inform you for those who still have a DDS140 that I am running it in the lotto OS802  software and that it works perfectly on w10 without the need for a driver.
I leave capture and link for those who may be interested greetings.



https://drive.google.com/drive/folders/1ST3awUa5HEMRMAV_RmmmOf8mwPNBn1TI