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.
@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: https://contact.saleae.com/hc/en-us/requests/new
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?
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.
@timreyes sorry for the veeery late reply. I have found a workaround to this problem, and that was to change my use case a bit, so instead of creating very large captures for the whole test duration (24h), I’m now creating a lot of smaller logs (~30s), and in between I’m closing the Logic SW and then start it up again and start the capture. and now it appears to be working very fine
One question: Do you plan to release Logic 2 as a standalone package, or even an installer that doesn’t require Admin rights?
The original community developr for this third party analyzer will need to update their repository to follow our new build process below:
You can attempt to update the build process using the instructions above, and using a local copy of their repository on your PC. Let us know if you run into any specific issues with that!
By the way, could you share more details about your experience with Logic2 being sluggish? If you can provide some example scenarios or PC usage statistics, that would be helpful for us to look into improving if needed.
