Closed drchopper closed 4 years ago
I don’t think this is an issue with this library. It sounds like for some reason the saleae software can’t handle the command you’re sending at that time. Depending on your needs, perhaps your script can catch the exception and retry the command.
If you have some evidence that there’s an actual bug in this library, please feel free to reopen this issue. Thanks!
The following code is not stable. Could you give me an advice how to get them stable?
I have an issue which occures randomly (sometimes once in 2000 boots). Catching a and retry would lose maybe the 1 failed boot. I want to avoid try, expections.
Thanks
#!/usr/bin/env python
import saleae
import time
dir = os.path.dirname(os.path.abspath(__file__))
s = saleae.Saleae()
s.set_capture_seconds(1)
while True:
file_path = os.path.join(dir, 'mySaleaeFile')
if os.path.isfile(file_path):
os.remove(file_path)
s.capture_to_file(log_file)
time.sleep(1)
Again I do not think this is a problem that this library can solve — I think this is an issue with the Saleae Logic software. All that this library does is send commands to the Logic software. You (or perhaps Saleae) need to diagnose why the Logic software periodically fails to save the file.
I created a small python application which shall sample my hardware during boot. Therefore, I start the board every second overnight. Unfortunately, my application raise a CommandNAKedError already after my approx. 10 reboots. Until the error occurs, the script works as expected.
Any idea how to get them stable?