I recently purchased a Logic MSO. I was impressed with the industrial design, build quality, user interface, and overall attention to detail, but I was disappointed in the lack of functionality of the oscilloscope. Features that are available on less expensive Chinese oscilloscopes, such as those from Siglent, are absent in the MSO. For example:
- There are no math functions.
- There is no FFT.
- There is no intensity grading (aka “virtual phosphor”).
- There is no X-Y mode.
- Only rudimentary trigger conditions are supported.
For me, the saving grace is the extensibility through APIs, but I do hope that these shortcomings will be addressed in future updates.
@watkins.robert Sorry about the missing features you’ve listed, though, I’m glad to hear you’ve been enjoying other aspects of our Logic MSO so far! This feedback is helpful.
I can say that math channels and FFT are on the list. Having said that, I can’t provide a timeline as to when we’d be able to start working on these. We’ve got a couple other projects lined up beforehand. Also, FFT and XY mode are both things that we would like our python measurement API to support, even if we build first-class versions of these features as well.
For intensity grading, are you looking for something eye-diagram like (e.g. persistence view + either edge trigger)?
Also, what kind of trigger conditions would you be interested in using?
We’d love to learn more about your use cases!
Thanks for the response, Tim. I’m glad to hear that you are working on some of these features.
For intensity grading, I’m looking for something that (optionally) emulates an analog scope. I would like to see faster transitions, such as the edges of a square wave or the higher-amplitude portions of a modulated AM carrier, displayed with less intensity.
Check out the user manual for the Siglent SDS2000X series for a list of trigger conditions that they support. Of these, I’m mainly interested in the ones that detect anomalous conditions: Runt, Dropout, and Interval — possibly Slope as well.
Aside: I’m glad to see that one-shot will soon be supported for digital triggers. In the meantime, I noticed something that appears to be a bug. I monitored the same signal with both a digital and an analog channel, and I triggered on the analog channel. This worked fine as long as I kept the (redundant) analog channel visible. If I hid it, the scope failed to trigger, even though the channel was still active in the Device Settings sidebar and set as the trigger source in the Recording Settings sidebar.