I am integrating to my setup Saleae basic 8 and Logic 2.4.10.
First of all, when I call manager.connect, GUI pop-up and close back. Is there a way to supress the gui pop-up?
I thought maybe manager.launch() as in the example code, would connect without GUI, however If I call it when GUI is closed, I get some error below. If I open the GUI first and execute, it works
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: Connection refusedâ
debug_error_string = âUNKNOWN:failed to connect to all addresses; last error: UNAVAILABLE: ipv4:127.0.0.1:10430: Connection refused {created_time:â2023-11-03T13:46:47.2443136+00:00â, grpc_status:14}â
So what is the difference between connect and launch APIs?
We do not currently support running automation without the GUI. This is something we want to support, but we are not currently working on it.
launch() will start the Logic 2 process and close it when the manager is destroyed. connect() will not launch Logic 2, and connects to an already-running instance.
Has there been any progress on this on the saleae end? We are finding that Manager.launch isnât working when run from our CICD environment but does work on our local tests.
@atakahashi At the moment, our Automation API still requires the GUI to be running.
I added a comment for you to the feature request post below so we can track your need for this:
In case it helps, weâve found some success with running the Logic 2 software in a headless environment on Ubuntu. More information on this can be found below.
The --disable-gpu command line argument when launching our software was provided as a workaround for when the software (with GUI) fails to launch (more info on that below).
Since my previous message on this forum thread, we havenât made any updates to our Linux headless suggestions via XVFB below.