PicoScope 6.13.7.707 on Ubuntu 18.04 no device detected

Discussion forum for the Picoscope 6 Linux software
Post Reply
n6rob
Newbie
Posts: 0
Joined: Fri Jul 19, 2019 11:18 pm

PicoScope 6.13.7.707 on Ubuntu 18.04 no device detected

Post by n6rob »

Greetings,

I am using Ubuntu 18.04 and just downloaded PicoScope 6.13.7.707.

The computer does not detect the PicoScope 6403A. From the output listed below I interpret it to mean there is a permissions problem.

Can you advise how to correct this? Thank you.

The output of the usbtest script is -

Code: Select all

Pico USB device found: /dev/bus/usb/001/030

 - It belongs to root (which is not you) who has permissions rw-
 - The members of group pico (which you are not in) have permissions rw-
 - Everyone else (this is you) has permissions r--
 - You CANNOT write to this device and so will NOT be able to use it.
   Please see the driver installation instructions for assistance in 
   resolving this problem 
The trace.xml file contents are -

Code: Select all


    Trace opened 7/19/2019.
    Application 'PicoScope 6 Beta' (version 6.13.7.707) starting.
    EB428642D69BC15A24BEA26253932F83
    User is not Guest
    No Administrator Privileges
    Failed to detect access rights
    Host Operating System - Linux
    OS Version - Unix 4.15.0.54
    .net Version - 4.0.30319.42000
    Running on Mono - True
    Mono Display Name - 4.6.2 (Stable 4.6.2.16/ac9e222 Thu Apr 20 10:05:37 BST 2017)
    Current Directory - /opt/picoscope/lib
    Processor Count - 4
    64Bit Operating System - True
    64Bit Process - True
    Command Line - /opt/picoscope/lib/PicoScope.GTK.exe
    Settings file version - 11.3.1
    Preferences file version - 2.0.0
    Probes file version - 1.0.0
    Data file binary header version - 1
    Using default culture: English (United States).
    Begin
    Begin
    Complete
    Attempting to load ps2000.dll
    Finished loading ps2000.dll
    Opening device using DLL ps2000.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps6000.dll
    Finished loading ps6000.dll
    Opening device using DLL ps6000.dll
    Opening device unsuccessful. Error UnknownDeviceError [FpgaFail(78)]
    Attempting to load ps4000a.dll
    Finished loading ps4000a.dll
    Opening device using DLL ps4000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps4000a.dll
    Finished loading ps4000a.dll
    Opening device using DLL ps4000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps3000a.dll
    Finished loading ps3000a.dll
    Opening device using DLL ps3000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps3000a.dll
    Finished loading ps3000a.dll
    Opening device using DLL ps3000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps4000a.dll
    Finished loading ps4000a.dll
    Opening device using DLL ps4000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps5000a.dll
    Finished loading ps5000a.dll
    Opening device using DLL ps5000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps5000a.dll
    Finished loading ps5000a.dll
    Opening device using DLL ps5000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps5000a.dll
    Finished loading ps5000a.dll
    Opening device using DLL ps5000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps3000.dll
    Finished loading ps3000.dll
    Opening device using DLL ps3000.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps5000.dll
    Finished loading ps5000.dll
    Opening device using DLL ps5000.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps4000.dll
    Finished loading ps4000.dll
    Opening device using DLL ps4000.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps6000.dll
    Finished loading ps6000.dll
    Opening device using DLL ps6000.dll
    Opening device unsuccessful. Error UnknownDeviceError [FpgaFail(78)]
    Attempting to load pl1000.dll
    Finished loading pl1000.dll
    Opening device using DLL pl1000.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load usbdrdaq.dll
    Finished loading usbdrdaq.dll
    Opening device using DLL usbdrdaq.dll
    usbdrdaq.dll OpenUnit returned 3
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps3000a.dll
    Finished loading ps3000a.dll
    Opening device using DLL ps3000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps2000a.dll
    Finished loading ps2000a.dll
    Opening device using DLL ps2000a.dll
    Opening PS2000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps3000a.dll
    Finished loading ps3000a.dll
    Opening device using DLL ps3000a.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps4000a.dll
    Finished loading ps4000a.dll
    Opening device using DLL ps4000a.dll
    Opening device unsuccessful. Error UnitNotFound
    No of Devices Found: 0
    Complete
    Opening device using DLL Demo Device
    Opening device successful. Error NoError.
    Device opened Demo:  PSGeneric Demo
    Device selected: PSGeneric, Demo
    Driver: Demo Device Version: 6.13.7.707
    Kernel driver: picopp.sys Version: 6.13.7.707
    Trigger set to : NonAdvancedEdge
    Source/Channel Index Changed to 0
    Trigger Direction set to Rising
    Probe light manager changed light state to True
    Trigger set to : NonAdvancedEdge
    GlobalDeviceManager.Close()
    Trace Closing

n6rob
Newbie
Posts: 0
Joined: Fri Jul 19, 2019 11:18 pm

Re: PicoScope 6.13.7.707 on Ubuntu 18.04 no device detected - SOLVED

Post by n6rob »

I offer this in the hope that it will help others...

I was able to solve this problem. The root cause was the power supply I was using. My PicoScope unit is surplus and I lack the original accessories (power supply, probes, USB cable, etc.). I substituted a power supply that did not supply enough current.

In the process of diagnosing this, I attempted to use the scope in Windows and got the same results as I did when trying Linux. The device would enumerate in Windows (10, 64 bit) just fine, but when I loaded PicoScope 6, it couldn't find the device. However, when I reviewed the trace file in the Windows installation I noticed an "FpgaFail (78)" error in the log (I can see the same error in the Linux trace file). Googling this led me to a post about how this is a failure of the scope to download the firmware to the FPGA during initialization and was frequently caused by power supply problems. This led me to investigate, which resulted in discovering the root cause. After further analysis, I notice that my unit draws just under 2 amps at 12 volts when not measuring a trace. When measuring a simple signal using one channel, I see it draws about 2.5 amps with some variation.

I am running the scope in Linux as I write this, and it seems to work just fine, so far.

Post Reply