# Sporadic crashes when using the tool for extended time periods **URL:** \ **Category:** Logic 1.x (Legacy) Software\ **Created:** [May 30, 2022, 2:21pm UTC](https://discuss.saleae.com/t/sporadic-crashes-when-using-the-tool-for-extended-time-periods/1614 "2022-05-30T14:21:52Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![alex.balan](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@alex.balan](https://discuss.saleae.com/u/alex.balan)\ **Post date:** [May 30, 2022, 2:21pm UTC](https://discuss.saleae.com/t/sporadic-crashes-when-using-the-tool-for-extended-time-periods/1614/1 "2022-05-30T14:21:52Z")
Hello, 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](https://github.com/saleae/python-saleae-cli) 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? ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [May 31, 2022, 10:29pm UTC](https://discuss.saleae.com/t/sporadic-crashes-when-using-the-tool-for-extended-time-periods/1614/2 "2022-05-31T22:29:04Z")
@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](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? - Can you share your crash logs with me? (instructions below) [https://support.saleae.com/troubleshooting/crash-logs](https://support.saleae.com/troubleshooting/crash-logs) 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. ---
**Author:** ![alex.balan](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@alex.balan](https://discuss.saleae.com/u/alex.balan)\ **Post date:** [September 19, 2022, 8:00am UTC](https://discuss.saleae.com/t/sporadic-crashes-when-using-the-tool-for-extended-time-periods/1614/3 "2022-09-19T08:00:55Z")
@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? Thank you in advance! ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [September 20, 2022, 10:47pm UTC](https://discuss.saleae.com/t/sporadic-crashes-when-using-the-tool-for-extended-time-periods/1614/4 "2022-09-20T22:47:41Z")
@alex.balan It’s great to hear from you again! Glad to hear you’ve got a workaround for it. We don’t have official plans to release Logic 2 as a standalone package, however, I’ll be happy to generate one on request for now. Here is the latest standalone version below: [https://logic2-dev.saleae.com/app/Logic-2.4.0-master-win.zip](https://logic2-dev.saleae.com/app/Logic-2.4.0-master-win.zip) By the way, since we last spoke, we’ve released automation support for Logic 2! More details below: > **[Logic2 Automation](https://www.saleae.com/automation/)** > > Automate Logic2 We recommend porting over your automation script since this will be the version we will officially support moving forward. ---
**Author:** ![alex.balan](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@alex.balan](https://discuss.saleae.com/u/alex.balan)\ **Post date:** [September 21, 2022, 11:32am UTC](https://discuss.saleae.com/t/sporadic-crashes-when-using-the-tool-for-extended-time-periods/1614/5 "2022-09-21T11:32:01Z")
Thank you for the suggestion @timreyes , but I gave a try to Logic2 and it looks a lot sluggish compared to Logic1. Also some of the analyzers are not present in the Logic2 [GitHub - kasjer/saleae\_spiflash: SPI flash protocol analyzer for Saleae Logic](https://github.com/kasjer/saleae_spiflash). And compared to the already existing one [GitHub - adafruit/Logic2-SPIFlash: Basic SPI Flash command decoder for Saleae Logic 2](https://github.com/adafruit/Logic2-SPIFlash) I see some differences on how the data is presented and unexpected crashes when larger SPI transactions are decoded. I will keep an eye on the Logic2 and give it a try if the resource consumption (RAM, CPU) and overall behavior improves. Thank you for the support and the work that you guys have put on Saleae 2! ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [September 22, 2022, 10:07pm UTC](https://discuss.saleae.com/t/sporadic-crashes-when-using-the-tool-for-extended-time-periods/1614/6 "2022-09-22T22:07:57Z")
@alex.balan Thanks for giving Logic 2 a try. For the analyzer you mention below: [GitHub - kasjer/saleae\_spiflash: SPI flash protocol analyzer for Saleae Logic](https://github.com/kasjer/saleae_spiflash) The original community developr for this third party analyzer will need to update their repository to follow our new build process below: > > > Hi! I'm a Product Manager at Saleae and we’ve made improvements to our analyzer …build process. Specifically, we cleaned up the build system, and switched to cmake, so there aren't multiple project files anymore. By implementing the changes outlined \[here\](https://github.com/saleae/SampleAnalyzer/#updating-an-existing-analyzer-to-use-cmake--github-actions) you will be able to provide the community automatic builds in addition to a simplified build system. Let us know if you think you can make the changes or if you’d like us to make the changes for you. > > Additionally, if you would like to update your analyzer so that results appear in Logic 2’s data table you can follow the steps outlined \[here\](https://support.saleae.com/saleae-api-and-sdk/protocol-analyzer-sdk/framev2-hla-support-analyzer-sdk). Note that if you upgrade your analyzer to FrameV2 it will not be backward compatible with Logic 1. > > We really appreciate your time and effort! Please let us know if you have any feedback or questions. Thanks! 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.