maginnovision, assuming I will be using sigrok, what are the issues you are seeing with this combo? From what I read the current version supports external clock, and has most of the features implemented already, or am I wrong? Where do you feel it falls short compared to other options?
One more thing has to do with operating it on an external clock. Any idea how fast this clock can actually be? I see this mode is much slower for most devices, but I can't see a note of this mode in the spec for the Hantek.
The external clock is most useful only if you can match your clock rate to the sample rate pulldown selection.
If that isn't the case then for me it crashes 100% of the time otherwise. That includes if I forget to deselect one line as trigger before selecting another, I don't need to start an acquisition. The external clock is most useful only if you can match your clock rate to the sample rate pulldown selection. Although potentially useful as well for capturing a lot of serial data. Again it may just be me but it crashes when using decoders and trying to scan through the data before they're fully decoded. With 64M samples that can take a while though. It doesn't save the setup on restart/crash, so if you have line A13 following A15 once it restarts it resorts back to numerical order. If you start sigrok before the LA is connnected and powered on you again lose your entire setup including labels and added decoders. The one saving grace there is typically when you re-add the decoders the lines are still set but you still lose your labels. Even without decoders if I try to scan through data during an acquisition or shortly after it crashes.
While I appreciate your honest criticism, I would like to point out that no problems will ever be fixed that the team doesn't know about. PulseView works just fine for a whole lot of people, and when something doesn't work for you, it's worth creating a bug report in bugzilla.
One more vote for DSLogic Plus, it was around 130USD
long list of decoders (I am familiar with 5 or 6 different decoders), ability to stack them (useful for work with low speed USB devices, fox example), ability to write your own encoders (python), cursor measurements, buffering and streaming data acquisition modes (USB2 speed limit)
Bad things: the GUI (sigrok fork/ or "being inspired by sigrok") DSView v0.9.7.1 (2 or so years old) was the last public release (but I still prefer ti very much to the original sigrok GUI).
That is exactly what I did, the 4032L is in the supported devices list and seems like the most capable device there
Only problem is that "supported" is a wide term, so I'd like to get more real world comments from users of this combo.
Thank you for this comment. Regarding external clock, I have no need to know exactly what it is in the software time stamps, as long as I can export all the data to CSV and process it in MATLAB. The question there was about the clock frequency the HW can support - I can't find a straight answer in the device datasheet about the maximum clock frequency I can use in this mode, this will probably be limited by the speed of the IO buffers and comparator they use. I'd guess 150MHz BW as they claim should support 150MHz clock, but one can never be sure unless its in the datasheet or someone else can test it
Of which exactly $0 went towards sigrok, by the way. Not even a single line of usable code because they not only didn't want to work with us, they actively sabotaged any effort of upstreaming anything.
...which are all features that the sigrok team (and community, in the case of protocol decoders) is responsible for - including the Cypress FX2 firmware that the DSLogic uses.
Seriously? You applaud them for taking our work, making the UI look "fancy", making money off of it of which we see exactly zero, adding some minor features here and there and then crap on us for having neither the man power nor the time to do the same? Hint: none of us gets paid and we support a wide range of devices - not just one. Making things work for one device is easy, making stuff work for *all* devices is not.
SMB784, this device is not meeting my desired spec as I've described above. The 50MHz limitation isn't a function of sample rate for most devices, its about the speed of the comparator and timing constraints of the digital logic. Therefore its impossible to look at the maximum sample rate and understand what the maximum frequency it can sample will be. As I mentioned above, this model (the pro) is my plan B (or maybe C), since it isn't what I really want in a LA. Bang for bug isn't the parameter I'm looking for, I'm looking for something that can technically do what I want, which out of the devices I've seen so far only the Hantek can.
If I come to the conclusion I can't use the Hantek due to software limitation I'll get the DSlogic Pro, and live with the fact it can only due the more basic things I need. But so far it seems the Hantek isn't "dead" yet. Especially considering the SW will keep improving.
I'm still on the fence here though, the two users who have experience with this combo (abraxa and maginnovision) agreeing that it can do what I want, but if I understand correctly there are bugs at the moment that might make it a not so pleasant experience
I'll try sending DreamSourceLab an email and ask them about the external clock mode. I'd like to understand if there are any other limitation to it and if the threshold voltage is indeed constant for 3.3V CMOS levels. If the threshold level is fixed this will be somewhat of a PITA for me to do this myself every time.
SMB784, do you have any way of feeding a clock into this pin and testing one (or both) of these parameters (maximum frequency it can run at, and threshold level adjustment support)?