I have found a reproducible error when communicating with the Saleae.
I have a short capture set up of 0.2S in a loop (it happens in the same way with longer captures of 5 seconds). The following error happens after around 1900 iterations (it varies, sometimes as low as 1850 or as high as 1930).
INFO:saleae.automation.manager:sub ChannelConnectivity.CONNECTING
INFO:saleae.automation.manager:sub ChannelConnectivity.TRANSIENT_FAILURE
Traceback (most recent call last):
File “test_saleae1.py”, line 73, in
test_the_saleae()
File “test_saleae1.py”, line 44, in test_the_saleae
capture.save_capture(filepath=capture_filepath)
File “C:\Python37\lib\site-packages\saleae\automation\capture.py”, line 391, in exit
self.close()
File “C:\Python37\lib\site-packages\saleae\automation\capture.py”, line 347, in close
self.manager.stub.CloseCapture(request)
File “C:\Python37\lib\site-packages\grpc_channel.py”, line 946, in call
return _end_unary_response_blocking(state, call, False, None)
File “C:\Python37\lib\site-packages\grpc_channel.py”, line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = “failed to connect to all addresses; last error: UNAVAILABLE: ipv4:127.0.0.1:10430: WSA Error”
debug_error_string = “UNKNOWN:failed to connect to all addresses; last error: UNAVAILABLE: ipv4:127.0.0.1:10430: WSA Error {grpc_status:14, created_time:“2024-05-03T16:14:13.794837763+00:00”}”
Just looking at the error message you showed above:
nick.smith:
debug_error_string = “UNKNOWN:failed to connect to all addresses; last error: UNAVAILABLE: ipv4:127.0.0.1:10430: WSA Error {grpc_status:14, created_time:“2024-05-03T16:14:13.794837763+00:00”}”
It seems like the gRPC server connection was intermittently failing:
The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff. Note that it is not always safe to retry non-idempotent operations.
Are you starting & running Logic.exe locally as a standard process natively on Windows 10 desktop/laptop console, or are doing something more elaborate (e.g., using a virtual machine or container, running remotely, etc.)?
Finally, if the issue is more like a race condition internal to the Saleae Logic 2 software itself vs. some type of local networking issue on the PC, you might be able to work around it by adding some delays between automation API calls: like inserting a time.sleep() call before each capture.command in your script?
Note: the line numbers in the quoted error message don’t appear to line up exactly with the attached saleae_test.py script (as the attached file was only 58 lines):
nick.smith:
Traceback (most recent call last):
File “test_saleae1.py”, line 73, in
test_the_saleae()
File “test_saleae1.py”, line 44, in test_the_saleae
capture.save_capture(filepath=capture_filepath)
However, the traceback suggests it might be something between the capture.export_raw_data_csv() and capture.save_capture() API calls? If so, perhaps the ‘export csv’ didn’t completely finish and the gRPC server is still busy when the ‘save capture’ is called – so you could try adding a time.sleep() of a few seconds in between those calls first?
One last clue – there was another post about exporting raw data CSV sometimes failing, which might be related to your issue:
nick.smith: