Hi PE1FZQ,

This may have something to do with USB host controller / libusb / hcd kernel driver. Is device plugged into USB3.0 port? Can USB2.0 port be tested for the same? Are there any USB related messages in kernel/system logs? (dmesg).

Mario

Hi Simon, libopencv problems took us by surprise. We are preparing next release to address this issue by providing static compilation removing requirements for libopencv. Also on that subject, integrated performance primitives library (which is libopencv in case of ARM base releases) is one of the d...

Hi vogi,

Can you run the following to check whether the permissions are granted for the device: Mario

Hi Simon, If you're trying to run PicoScope 6 for Linux on Raspberry Pi 2 - it will not work. Release PicoScope is not ready yet to run on ARM devices, and frankly, hard to say if it ever going to be. About the drivers, first you need use correct repository. You can run ordinary Debian (Jessie) on R...

Hi vogi,

What are result of following commands? The results should match If not, try reinstalling: Mario

Hi,

Yes, you need to install a package providing this dependency. Since CentOS 5 doesn't have it in standard repositories you need to search for it in your favorite search engine. One of the examples found is here. Download it and install by running rpm -i .


Mario

Hi aLondon, Drivers for USB PT-104 are in the libusbpt104 package. Configure repository as explained here https://www.picotech.com/downloads/linux and install it. Then navigate to /opt/picoscope/share/doc/libusbpt104 to find an C example. Note that communicating via ethernet your Linux application w...

Hi Tobiasz, Port type should not matter, libusb guards the driver from those variations. Good news btw, I managed to get exception 11 - which is segment not found. And when it occurs, virtual memory of the process is close to hardware available. It was harder for me to observe it, as I'm running 64b...

Works for me... [2015-01-30 15:48:35] Loop 64 [2015-01-30 15:48:35] Connecting to picoscope with serial number AO483/035... OK [2015-01-30 15:48:39] Connecting to picoscope with serial number AV987/021... OK [2015-01-30 15:48:44] Connecting to picoscope with serial number CX012/015... OK [2015-01-30...

Hi obbe, We have just released new version built and tested on 10.10. See if it resolves your issues. There is one other thing we have noticed during the tests - sometimes it takes around 10 seconds for device to be available in the system after plugging it in (especially USB3.0 device). It seems li...

We have produced another version of PicoScope 6 for MacOSX - 6.10.1.37, which can be now downloaded from download section of our website. It provides support for new 3000 devices and also start up speed has been improved. The persistent issue of UI being sticky is now less frequent - but only after ...

Hi Tobiasz, I have run suggested test on my desk for several hours, to the amusement of my colleagues - constant click-clacks are quite annoying. The problem wasn't observed though. Maybe it has something to do with specific devices? I used PS3206B, PS3207B (USB3) and PS3406B with power supply plugg...

New release - PicoScope 6.10.1.36 - has been uploaded to the repository. Hopefully all USB issues were addressed with this one. Also with this version we have added support for new PS3000a devices and start-up time has been dramatically improved.

Mario

Hi Martin,

You are probably experiencing the same problems with USB stability as described in main thread.
Have look in this post topic13191-90.html#p44431 and also previous entries in case you'd like to try latest release candidate.

Hi All, There is a way to come back to old version, as described below. Before you do though, you can try the latest release candidate that made it to the debfix repository - includes numerous USB related fixes, but crashes on usbdrdaq :( To use version from August (the last one before numerous USB ...