Sporadic crashes when using the tool for extended time periods


I’m trying to use the tool for capturing SPI communication for an extended time period (max 48h).
And for that I’m using a Saleae Logic Pro16 with Logic+1.2.27+Win+32+Standalone (also tested Logic-1.2.40-Windows) together with the Python library for triggering captures of 25s long at 50MS/s. To ease the python scripting part, I’m using GitHub - saleae/python-saleae-cli: basic command line utility to automate the Saleae Logic software using the ppannuto python-saleae library for the actual control of the SW.

The observed behavior is that sometimes, two things might happen: Saleae SW crashes and the script hangs, or the script is throwing the exception: CommandNAKedError.

How can I overcome this? What are your hints?

@alex.balan Oh no! Sorry to hear that… First off, I’d recommend sticking to version 1.2.40 if you plan on using automation. Version 1.2.27 is quite old and contains bugs that 1.2.40 has since solved.

With regards to captures that span several hours, we’ve been discussing this topic internally. The big-picture problem here is that we don’t test our hardware and software with recordings anywhere nearly this long. From a product testing point of view, we focus most of our attention on captures that are up to 15 minutes in length.

Having said that, I’d like to look into what might be causing those crashes in the first place, as well as perform a review of your automation source code with the team here to see if we can catch any obvious issues.

In case you’d prefer not to share your information and source code publicly, feel free to send an email to me (along with your source code attached) using the link below and we can continue our discussion privately if you prefer:

In your message, just provide a link to this discuss forum post so I know it’s you when it arrives.

I would also be interested in understanding the following (you can send this using the link above as well):

  • Do you happen to know when exactly the software crashes, and what it’s doing while it crashes? Or is it seemingly random?
  • Is it consistently and easily reproducibe using your automation source code? Or is it seemingly random?
  • Can you share your crash logs with me? (instructions below)

The first step on our end would be to attempt to reproduce the crash using your automation script, review your code for any obvious issues, and look into your crash logs once you send that all over.