The host(pc) issues a "go code" of 33h, periodically checks the status of the FIFO with command 50h, which returns 2Ch for fifo not full. In fact, once the scope is setup (permit USB interrupt data transfer gain,ACDC etc) the sequence of events is incredibly simple. And low, I see the command set I've already seen in the firmware, the only code I was missing is E7. Which of course it is not All: After days of negative feelings as to progress, I finally got round to Wiresharking the USB stream. Ganzuul: The point? perhaps just to be able to say it is an "open" interface. Are there elements that you are searching for? I guess you are not planning on rewriting the DLL! But thanks for the BS204 heads up anyway. I am still making progress on the code, but ask myself whether there is anybody wanting it. the BS204 is exactly what I need in terms of functionality. (JV) * The glitches (discontinuities) in the capture data recurring at around 2KB (combined byte count for both channels) boundaries seems to be a HW/FW limitation of the DDS120 that would be difficult to workaround.Doctormord: Argh! seems like I brought my DDS140 two weeks too early. (JV) * The trigger position sliders now work separately and only the trigger source channel controls the trigger position. ![]() (JV) * Keep the start of displayed waveform (trigger source channel) in level with the trigger position on the slider control. (JV) * Improvement in the robustness of rising/falling edge detection prior to locating the trigger position offset, especially, for slow signals (e.g 100ms, 200ms timebases). (JV) * Eliminate the "rolling buffer" problem and fix the segmentation fault issue. ![]() This is an important requirement for signals that are generally different (in shape and phase) across the channels. Only the trigger source channel determine the trigger position. Quote * Version 0.3.1 * Support for SainSmart/Buudai DDS120 (mmark) * Better support for SainSmart/Buudai DDS120 (CW) * Trigger Support for DDS120 (CW) * Markerslidersteps 0.2 -> 0.1 of DIV (CW) * Select triggervoltage in < 0.05V steps (CW) * Improve trigger stability by excluding false positive cases (JV) * Added falling edge trigger support (controlled by GUI button) (JV) * The other channel now use the same trigger position as the trigger source channel, ensuring that the timing relationship between the channels is maintained. Anyone care to sum it up for newcomers to the thread? C'mon, pimp your badass programs and tell me which one I should be using! :-P ninja edit: it looks like SanSmart has a Logic Analyzer add-on that's only another few $. (also need something digital) I'd be willing to spend the ~$90 US or so for a dds-140 but I'm kind of at a loss for what software is the best / most developed. Honestly, vertical accuracy isn't too important for this app, I just need something that can reasonable capture signals, and my trusty Tek 2445 is starting to fritz. Looking for something cheap but most importantly the software has to not be total rubbish. it's like the DX but only 8 channels) but it just doesn't play nice with some ICD devices etc. Basically I just want something to check timings on uC projects. So I read through the thread but there's been a lot of programs going back and forth, I'm not sure what I should be looking for software-wise if I'm considering picking one of these up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |