I use four (identical) setups consisting of a PicoScope 5444B with a Linux-Laptop. The PicoScope is externally supplied with 5V. I'm doing some 24/7 measurements and "sometimes" (in the last 5 days it happened about 1 to 5 times on the different machines) I get an error 0x07 from the library (PICO_NOT_RESPONDING).
I have used the same setup (same PicoScope and self written software, but different Laptops and "older" Linux software / PicoScope driver) about two years ago and I did measurements over months without a single failure...
I've also seen some entries in the kernel log, maybe they are related to my problem:
from the "journalctl":
Oct 10 07:25:50 plc2 kernel: usb 1-4: USB disconnect, device number 12
Oct 10 07:25:51 plc2 kernel: usb 1-4: new high-speed USB device number 13 using xhci_hcd
Oct 10 07:25:51 plc2 kernel: usb 1-4: New USB device found, idVendor=0ce9, idProduct=1019
Oct 10 07:25:51 plc2 kernel: usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 10 07:25:51 plc2 kernel: usb 1-4: Product: PicoScope 5000
Oct 10 07:25:51 plc2 kernel: usb 1-4: Manufacturer: Pico Technology
My program told me at 07:25:52 - two seconds after the initial kernel-log entry - that the error occurred:
ERROR Mon Oct 10 07:25:52 CEST 2016 in picoscope_thread.tcl(25): Background Error: 'picoScope: couldn't program AWG - got error: 0x7'
So maybe, the PicoScope got a "USB-reset" and therefore the library got the timeout...?
My problem is - even if the above written is correct - WHY did the "USB-reset" occur in the first place? Any clues?
Has anybody seen something similar?