| Products > Test Equipment |
| SainSmart DDS120 & DDS140 USB Oscilloscope |
| << < (81/84) > >> |
| 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. --- Quote ---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/ --- End quote --- |
| 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. --- Quote ---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 --- End quote --- Can someone host a valid .sys file or help me get around this? Greatly appreciated |
| savvej:
--- Quote from: bplaa.yai on June 19, 2017, 05:23:17 pm --- --- Quote from: bplaa.yai on June 18, 2017, 06:08:16 pm ---I'd like to make sure I've not made/forgotten anything silly first. --- End quote --- --- Quote from: doctormord on June 19, 2017, 03:43:46 pm ---OpenBuudai was never tested with the DDS140, so it needs complete implementation of the different command set. (As the DDS140 uses an FPGA) --- End quote --- Well, that's exactly the kind of "silly" I was expecting :D 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, --- End quote --- 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 |
| Navigation |
| Message Index |
| Next page |
| Previous page |