Using Logic Pro 16 for Power Sequencing

Sharing a video using the Logic Pro 16 for power sequencing verification. We’ve seen a few international teams using the hardware in this way and I wanted to share. This forum is mostly expert users, so I thought you might have suggestions or best practices.

Let me know if you have an application or use case that I can feature in an upcoming video.


@erik this is cool as and an interesting way to use the device.

1 Like

And if need be, you can look at enables to the regulators, and I2C comms to the PMIC, all on tool.

Strange to think 5 years ago I was looking at my Saleae as a “poor mans LA”, and now I regard it as an essential tool. Having previously had access to MSOs with 4 analog and 16 digital, I never thought I’d migrate to a 2 channel scope, and a Saleae Pro 16 as my tool kit.

1 Like

I totally agree – I was an early adopter of the pro series (my first Logic is Revision 0.0.0), and I now cringe when having to switch back to a bench oscilloscope. You can really get spoiled with a ‘capture everything and just post-process it’ development method vs. iteratively tweaking the capture & trigger settings to catch everything within a single snapshot on a scope. Do you prefer more range or resolution? … BOTH, and I’d like a few seconds or more before and after that, too, please :wink: I definitely love all the digital decoding, extensibility & automation features, but I’m still hoping Saleae will (eventually) update the analog filtering capabilities.

Ultimately, I see it as a difference between one ‘ultra hi-res’ snapshot (oscilloscope) vs. capturing a ‘high-enough-res’ continuous stream of everything (Saleae Logic). As long as the capture resolution is ‘good enough’, then it’s so much better to just capture everything. Yes, DSLR cameras (scopes) have their use cases, but digital video cameras (Logic analyzers) usually give you more information about real-time activities – unless you need ultra-fine details of one ‘frame buffer’ of information and you can take it at the right moment with the right settings. I’ve found it’s a lot easier to just hit ‘record’ and then rewind/single-step/zoom through the captured video vs. tweaking camera settings and trying to trigger the shutter with just the right timing.

Meanwhile, Tek has long since ‘discontinued’ my $cope, while Saleae still fully supports even my v0.0.0 hardware (purchased in circa 2014). As far as I know, they still support the original Logic/Logic16 devices that were discontinued a while ago :slight_smile:


I think there is one thing I need to learn how-to, or is missing from the Saleae. Long term interrupt latency testing. I would set up my Tektronix scope to trigger when an Interrupt line was held “too long”, save that to a file, email me a notification, and then carry on with next capture. I’d kick it off Friday afternoon, and by Monday I’d have three or four events in my inbox to review.

I have yet to find the kind of auto save, and re-arm capture on my Saleae, but for those once a day, once a weekend, three times a week timing issues. Maybe I can play with scripting, but my hours are better spent using tools that “just work” versus making ad hoc tools in a language like Python which is not my main language.

That said, Saleae is doing 80% of my serious testing. My portable 2 channel scope is faster to set up (when the Saleae is packed away) but only really gets pulled out for the odd occasion when I know that is the tool.

Advanced triggering is definitely a weakness of Saleae within the native UI – especially for analog-related triggers. You can trigger on an edge or a basic high/low digital pulse, but to do everything you outlined you’d need to use the Automation API w/ python – which is what you said you’d prefer not to do. As far as I know, that’s the only published method supported to automatically save/restart the capture engine. So, pretty much any advanced/automated user-defined functions would require python scripts and/or custom low-level analyzers (typically in C++).

Meanwhile, it sounds like Tek scopes have added some nicer ‘built-in automation’ features in the last 10 years since I last got a new one :wink:

[Edit: I also confirmed, the Analyzer SDK doesn’t allow access to analog data]


The Automation API is really easy to use and the great folks at Saleae provide you a basic script to get your started on your quest to capture the data as you need. I’ve written a few Analyzers in C++ to meet my aims, and there are links to each kind of Analyzer that has been shared within the community. What I am sayin is that one should have a look and you just may find someone has already written an analyzer for the function you desire.

The basic script is easy to modify and to add additional functionality to, its not that daunting. This has turned into a great thread.

1 Like