Closed Ploppz closed 4 years ago
First -- apologies for having missed this and never replied :(. This is a pretty stale issue at this point, so I'm going to close it, but feel free to re-open if there's still something to be looked at here.
It's weird / problematic that Logic required sudo
, that shouldn't be a thing (likely misconfigured udev rules allowing access to the USB peripheral?). I would look at fixing that first and then seeing if not running Logic as root doesn't fix other issues.
I have checked "Enable scripting socket server" in
Logic
. Using Arch Linux.In python3 shell, when I first run
s = saleae.Saleae()
,Logic
opens up, but the python line never returns (not even after closingLogic
).When I
Ctrl-C
in python shell, I get this error:Earlier, I changed
/usr/bin/logic
to/usr/bin/Logic
. I'm using thesaleae-logic
package in Arch Linux (from AUR) - version 1.2.11.Now, if I run
sudo Logic
in advance,s = saleae.Saleae()
returns immediately.After running
s.capture_start_and_wait_until_finished()
, thens.export_data2
always makes a file that has this content:Here is a sequence of function calls that has some problematic output as well:
It might be relevant that I have to run
Logic
withsudo
in order for it to be able to find the logic analyser device. But since I already have to runsudo Logic
in advance to makes = saleae.Saleae()
return, I guess this is fine.