| Products > Test Equipment |
| SainSmart DDS120 & DDS140 USB Oscilloscope |
| << < (27/84) > >> |
| mmark:
Some progress: Got OpenHantek to compile on my Mac with Qt5.3 & clang and added some initial code to talk to my DDS120: Neither range setting, voltage scaling, sample rate setting or triggering works yet, but I was quite excited to see some real oscilloscope data on my screen today for the first time... It's a start! Don't know how to share this in the best way. Do you guys want a github project or should I just zip up the src and post it somewhere? Just in case someone wants to play with the code (it in rough shape..., you will need to change the OpenHantek.pro for sure to get it to compile), but I'll attach a zip just in case. mmark |
| psynapse:
MMark Well done, have just downloaded your code to play with. Your problems on scaling etc ... it is late, and I have not checked but Donut6 and I have been working on DDS140 codes and I am not sure that we have 100% verified that they are the same, similar yes, but ... so beware I have been working on getting a platform for firmware modification. Getting the tools together etc. For those that are interested "cycfx2prog" (at least in the Ubuntu repository, and source available) will download an Intel hex file into the RAM of the FX2 (if it is started with its eeprom jumper off) and from there will allow the code to execute. This is much faster than loading the eeprom each time, and more importantly gives you a fall back to a working device at the flick of a jumper. To verify this I have turned the original eeprom dump into an intel hex format file, which can be reloaded to the DDS140 and works.(attached) More importantly (for me), I have also generated annotated assembly code which is bit perfect with the original .... meaning of course that firmware additions can now be added very easily. |
| mmark:
Psynapse, I don't have any problems with the codes (I am using the codes for the DDS120 as identified by doctormord, which seem to work in my test120.cpp application as expected). It's just that the code inside openhantek is --- aehh ---- somewhat complicated to say it politely :-//. So I need to figure out how I need to scale the data in the way openhantek wants it to be scaled and add functions to actually change the gain and the sample rate of the SainSmart scopes. So far I just removed all the code for the Hantek scopes and just implemented the getSamples methode. In the meanwhile I also implemented the setCoupling methode, which seems to work correctly, but I need to find a clean way to remove options (like GND coupling) which are not supported by the SainSmart scopes... |
| doctormord:
Great work guys! ^-^^-^ |
| psynapse:
mmark, Well, that you have got good DDS120 codes is good news (so well done to Doctormord as well). I know what you mean about the openhantek code. I looked as well and decided that it would be quicker to use Donut6's code to get the data (and control the scope) and then to write a whole new front end in QT ..... that way I have a working system I can improve (by adding buffers as previously discussed, as well as extra features). That decision as to whether it is better to adapt existing code or write new code is always hugely difficult. For me (with a DDS140) the new code route seems better, because there is a second operating mode which does not exist in the basic Hantek and because some of the features I want to add exist neither in the hantek, dds120 or dds140. In particular something resembling an external trigger, or at least a signal outputted to mark beginning / end of sampling Doctormord; I have looked at your photos of the DDS120 board, and as far as I can see INT4 INT5 is not connected anywhere ..... Please could you confirm that I am right .... My intention is to use INT4 INT5 as an external trigger (of sorts). Also, what advice do you have on buffering the pin .... which series of devices gives the best isolation, do I need clamp diodes etc (Not Int4 because there is a potential clash with FIFO interrupts, although these are not currently used in the DDDS140) |
| Navigation |
| Message Index |
| Next page |
| Previous page |