Automation export issue: session can´t be closes while export

[timreyes]

@dominic.styblo I wasn’t able to reproduce the error message you described below in my attempt to run multiple captures one after another in one script (saving/exporting data after each capture). I’ve attached the script I used to test this below.

saleae_example_multi_capture.py (2.6 KB)

@dominic.styblo

My problem is that when I run multiple captures after each other. I get an error message in the Logic 2 UI telling me that I can’t close a capture while exporting files.

1. Are you able to share a Python script that can reproduce this error? I’d like to try running it on my end. Perhaps your provided script is able to trigger some kind of edge case that I’m not able to reproduce.
2. Can you share an image of the error message you get in the Logic 2 UI?

By the way, I’d like to share a sample script below that can help with using a separate thread to save, export and close the capture while the next capture is already starting. Our sample here demonstrates how to do it:

Automating long recordings? Using multiprocessing for the saves?

Hi @bu5, Good news, we did test that this can be done with Logic 2. We recommend using the python main thread to perform the captures, and use threads to take care of saving and closing finished captures. Here is an example I tested a while ago which allows you to export, save, and close captures in the background while the next capture is running. Let me know if you have any trouble with it! from saleae import automation import os import os.path from datetime import datetime import threading …

In summary, this would allow you to start your next capture while you are saving/exporting the previous capture, thereby reducing the delay between captures.