I think I may have discovered an issue with the ps2000aRunBlock() API function and the segmentIndex parameter. I've been utilizing the pico-python project which provides a Python interface to the PicoScope C API. The wrapper function which calls ps2000aRunBlock was failing with PICO_SEGMENT_OUT_OF_R...

Try running it as root with "sudo picoscope", as mentioned in my previous post. Works for me.

After using the PicoScope application more on Linux, I just wanted to reiterate that it does look like running the picoscope application as root (with sudo for example) fixes this issue. So I would assume there is some sort of resource or API which is being affected by the difference in user permiss...

It seems like running picoscope as root (using sudo) does indeed fix the issue, from what I have seen so far. I have not tested this enough yet to know for sure, but the times where I started up picoscope and it stopped working after enabling triggers, if I quit the application and started it with s...

I've done both. After it broke again, I attempted to use "strace" to see if there was any sort of I/O errors happening which would cause the scope to disconnect. The application quit immediately unless I ran it as root, when using strace. When I did this, it started working again and has worked ever...

My PicoScope was working great for over a week without issue. This morning unfortunately, the issue has returned. I tried purging the PicoScope related packages again and re-installed them, without success. Every time I enable triggers, the scope LED goes out and I'm forced to go to File->Connect De...

After trying a bunch of things it seems to be working again. I'm not sure what fixed it or if it is fixed permanently, time will tell. Here is what I did: - Uninstalled picoscope with "sudo apt remove picoscope" - Uninstalled dependencies with "sudo apt autoremove" - Installed older version of Picos...

I spoke too soon. The issue is still occurring, seems it just worked a couple times and is now back to doing the same thing again. I also noticed that even when it did work and captured some data on a trigger, the scope would suddenly disconnect and stop working. It seems it also does this with anal...

See below for a solution to this problem.. I've been using a 2205MSO PicoScope in Linux for over 18 months and it has worked well. However, I just tried using it and am now running in to what I think is this same issue. I uninstalled all PicoScope related packages and reinstalled them, without any i...