Latest version doesn't find my PicoScope

Discussion forum for the Picoscope 6 Linux software
madrang
Newbie
Posts: 0
Joined: Thu Jan 28, 2016 9:46 pm

Re: Latest version doesn't find my PicoScope

Post by madrang »

Same here, there is only a demo device and no error after launching the picoscope app.

Code: Select all

Bus 003 Device 017: ID 0ce9:1012 Pico Technology PicoScope 3000A series PC Oscilloscope

madrang@ASTitan:~$ /opt/picoscope/share/doc/libps3000a/usbtest

****************************************************************************
*                  Pico Technology Linux USB Diagnostics                   *
****************************************************************************

This script looks for Pico USB devices connected to your computer
and checks whether you are able to access them. If your user account
does not have permission to access the devices, the script will try
to suggest how to correct this for your particular Linux installation.

Press enter to continue...

Getting user and group information...
 - You are running this script as madrang.
 - You are in the following groups:
     madrang adm tty dialout cdrom sudo dip plugdev lpadmin sambashare vboxusers wireshark pico usb

Please connect your Pico USB device and press enter to continue...

Pico USB device found: /dev/bus/usb/003/017

 - It belongs to root (which is not you) who has permissions rw-
 - The members of group pico (which you are in) have permissions rw-
 - Everyone else has permissions r--
 - You can write to this device and so will be able to use it.

totalkrill
Newbie
Posts: 0
Joined: Fri Apr 11, 2014 3:57 pm

Re: Latest version doesn't find my PicoScope

Post by totalkrill »

The downgrade sure did work.

Thanks!

bortolozzo
Newbie
Posts: 0
Joined: Wed Dec 02, 2015 10:46 pm

Re: Latest version doesn't find my PicoScope

Post by bortolozzo »

download mono-4.0.4.1-1-x86_64.pkg.tar.xz
(https://archive.archlinux.org/packages/m/mono/)
and
sudo pacman -U mono-4.0.4.1-1-x86_64.pkg.tar.xz

corna
Newbie
Posts: 0
Joined: Sun Dec 20, 2015 9:33 am

Re: Latest version doesn't find my PicoScope

Post by corna »

I can confirm this bug: on Debian Testing (mono 4.2.1.102+dfsg2-5) my 2205MSO is not recognized (but it can be successfully found by /opt/picoscope/share/doc/libps2000a/usbtest) while with Stable's mono (3.2.8+dfsg-10) everything works correctly.
Please fix this bug! As reported here (https://packages.qa.debian.org/m/mono.html), mono 4.2 migrated to testing on 1/1/2016.

madrang
Newbie
Posts: 0
Joined: Thu Jan 28, 2016 9:46 pm

Re: Latest version doesn't find my PicoScope

Post by madrang »

I tried to fix it with mono parallel http://void.printf.net/~bredroll/pmono/pmono/
But now it crashes while trying to connect....

It also fails to connect to the scope from Windows 7 running in VirtualBox 5.0.14
So now i own, an expensive, usb powered paperweight....

Code: Select all

madrang@ASTitan:~$ source pmono
madrang@ASTitan:~$ mono --version
Mono JIT compiler version 3.4.0 ((no/d4511ef Wed Apr  9 09:01:34 BST 2014)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	LLVM:          supported, not enabled.
	GC:            sgen
madrang@ASTitan:~$ picoscope

(PicoScope.GTK:15131): GLib-CRITICAL **: Source ID 1 was not found when attempting to remove it

(PicoScope.GTK:15131): GLib-CRITICAL **: Source ID 2 was not found when attempting to remove it

(PicoScope.GTK:15131): GLib-CRITICAL **: Source ID 15 was not found when attempting to remove it

(PicoScope.GTK:15131): Gtk-CRITICAL **: IA__gtk_widget_map: assertion 'gtk_widget_get_visible (widget)' failed
Stacktrace:

  at  <0xffffffff>
  at (wrapper managed-to-native) Gtk.Object.gtk_object_destroy (intptr) <0xffffffff>
  at Gtk.Object.Destroy () <0x00033>
  at Gtk.Widget.Destroy () <0x00013>
  at aY.h () <0x00024>
  at k.b (System.Exception) <0x0023d>
  at k.a (System.Exception) <0x00037>
  at aY/<>c__DisplayClass7.
b__3 (GLib.UnhandledExceptionArgs) <0x0005f> at GLib.ExceptionManager.RaiseUnhandledException (System.Exception,bool) <0x00131> at Gtk.Widget.exposeevent_cb (intptr,intptr) <0x0009f> at (wrapper native-to-managed) Gtk.Widget.exposeevent_cb (intptr,intptr) <0xffffffff> at <0xffffffff> at (wrapper managed-to-native) Gtk.Application.gtk_main () <0xffffffff> at Gtk.Application.Run () <0x0000b> at aY.b () <0x002c3> at i.a (System.Collections.Generic.List`1) <0x00035> at aY.a () <0x006af> at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff> Native stacktrace: /opt/mono/bin/mono() [0x4b082a] /opt/mono/bin/mono() [0x5088af] /opt/mono/bin/mono() [0x422d87] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10) [0x7f9536cc6d10] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_type_check_instance+0x19) [0x7f9523de1e39] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_handlers_disconnect_matched+0x24) [0x7f9523dd65b4] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_accel_label_set_accel_closure+0xa7) [0x7f9529788557] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_accel_label_set_accel_widget+0xaf) [0x7f952978878f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x7182b) [0x7f952978882b] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x9f) [0x7f9523dbcf6f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2257e) [0x7f9523dcf57e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xfbc) [0x7f9523dd7dfc] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f) [0x7f9523dd812f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x158190) [0x7f952986f190] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x48) [0x7f9523dc37b8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x117822) [0x7f952982e822] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb805f) [0x7f95297cf05f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x9f) [0x7f9523dbcf6f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2257e) [0x7f9523dcf57e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xfbc) [0x7f9523dd7dfc] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f) [0x7f9523dd812f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x158190) [0x7f952986f190] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x48) [0x7f9523dc37b8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x143225) [0x7f952985a225] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb805f) [0x7f95297cf05f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x9f) [0x7f9523dbcf6f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2257e) [0x7f9523dcf57e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xfbc) [0x7f9523dd7dfc] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f) [0x7f9523dd812f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x158190) [0x7f952986f190] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x48) [0x7f9523dc37b8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x140122) [0x7f9529857122] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x9f) [0x7f9523dbcf6f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2257e) [0x7f9523dcf57e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xfbc) [0x7f9523dd7dfc] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f) [0x7f9523dd812f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x158190) [0x7f952986f190] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x48) [0x7f9523dc37b8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x143225) [0x7f952985a225] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb805f) [0x7f95297cf05f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x9f) [0x7f9523dbcf6f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2257e) [0x7f9523dcf57e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xfbc) [0x7f9523dd7dfc] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f) [0x7f9523dd812f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x158190) [0x7f952986f190] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x48) [0x7f9523dc37b8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8373a) [0x7f952979a73a] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb805f) [0x7f95297cf05f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x9f) [0x7f9523dbcf6f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2257e) [0x7f9523dcf57e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xfbc) [0x7f9523dd7dfc] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f) [0x7f9523dd812f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x158190) [0x7f952986f190] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x48) [0x7f9523dc37b8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb805f) [0x7f95297cf05f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x145) [0x7f9523dbd015] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2257e) [0x7f9523dcf57e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xfbc) [0x7f9523dd7dfc] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f) [0x7f9523dd812f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x158190) [0x7f952986f190] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x48) [0x7f9523dc37b8] [0x41dde84b] Debug info from gdb: Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. No threads. ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. =================================================================

Hitesh

Re: Latest version doesn't find my PicoScope

Post by Hitesh »

Hi madrang,

Which specific PicoScope 3000 Series device are you using and is it connected via USB 2.0 ports with a single/double-headed USB cable or via a USB 3.0 port?

It might be helpful to see the trace.xml file corresponding to the last session where your PicoScope was not detected - you can find this file in the location:

~/.local/share/Pico\ Technology/260a68f1-30f-0a5e01d65514

In your Windows virtual machine, does the device appear in the Windows Device Manager?

Regards,

madrang
Newbie
Posts: 0
Joined: Thu Jan 28, 2016 9:46 pm

Re: Latest version doesn't find my PicoScope

Post by madrang »

I modified "/opt/picoscope/bin/picoscope" to remove the console redirect, but I didn't know that at some point the logs were redirected from the console to a file by the executable.

After looking at the content of "/home/madrang/.local/share/Pico Technology/260a68f1-c314-451b-830f-0a5e01d65514/trace.xml"

Code: Select all


    Trace opened 2016-02-04.
    Running on Mono - True
    Mono Display Name - 3.4.0 ((no/d4511ef Wed Apr  9 09:01:34 BST 2014)
    Host Operating System - Linux
    64Bit Operating System - True
    64Bit Process - True
    Logical Processors - 12
    Application 'PicoScope 6 Beta' (version 6.11.8.10) starting.
    370F2EA51F5F1A734FA2D40AFA1AC1F3
    User is not Guest
    No Administrator Privileges
    Failed to detect access rights
    OS Version - Unix 4.2.0.27
    .net Version - 4.0.30319.17020
    Current Directory - /opt/picoscope/lib
    Command Line - /opt/picoscope/lib/PicoScope.GTK.exe
    Settings file version - 11.2.0
    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 ps6000.dll
    Finished loading ps6000.dll
    Opening device using DLL ps6000.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 UnitNotFound
    Attempting to load ps5000a.dll
    Finished loading ps5000a.dll
    Opening device using DLL ps5000a.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 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 ps4000.dll
    Finished loading ps4000.dll
    Opening device using DLL ps4000.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps3000a.dll
    Finished loading ps3000a.dll
    Opening device using DLL ps3000a.dll
    Opening device successful. Error NoError.
    Device opened AV700/184: PS3000A PS3204A PS3000A
    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 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 ps3000.dll
    Finished loading ps3000.dll
    Opening device using DLL ps3000.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 ps2000.dll
    Finished loading ps2000.dll
    Opening device using DLL ps2000.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 pl1000.dll
    Finished loading pl1000.dll
    Opening device using DLL pl1000.dll
    Opening device unsuccessful. Error UnitNotFound
    No of Devices Found: 1
    Device selected: PS3204A, AV700/184
    Driver: ps3000a.dll Version: PS3000A Linux Driver, 1.4.5.45
    Kernel driver: picopp.sys Version: PS3000A Linux Driver, 1.4.5.45
    Complete
    Trigger set to : NonAdvancedEdge
    Source/Channel Index Changed to 0
    Trigger Direction set to Rising
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    Probe light manager changed light state to True
    Trigger set to : NonAdvancedEdge
    Unhandled Exception:System.DllNotFoundException: gdksharpglue-2
  at (wrapper managed-to-native) Gdk.Event:gtksharp_gdk_event_get_window (intptr)
  at Gdk.Event.get_Window () [0x00000] in :0 
  at bw.a (Gdk.EventExpose , a ) [0x00000] in :0 
  at K.OnExposeEvent (Gdk.EventExpose args) [0x00000] in :0 
  at Gtk.Widget.exposeevent_cb (IntPtr widget, IntPtr evnt) [0x00000] in :0 
To fix this "Exception:System.DllNotFoundException: gdksharpglue-2"

I made sure that "/opt/mono/lib/libgdksharpglue-2.so" exist and is the right version then

In the file "/opt/mono/etc/mono/config"
I added ""
and now it works perfectly.

Maybe critical errors such as System.DllNotFoundException should also be printed in the console under linux or move the logs to /var/logs/picoscope.xml where a linux user inexperienced with the picoscope application will look for those.

Since it is now working natively i don't plan to try to understand why it is not working in a VM.

Code: Select all


    Trace opened 2016-02-15.
    Running on Mono - True
    Mono Display Name - 3.4.0 ((no/d4511ef Wed Apr  9 09:01:34 BST 2014)
    Host Operating System - Linux
    64Bit Operating System - True
    64Bit Process - True
    Logical Processors - 12
    Application 'PicoScope 6 Beta' (version 6.11.8.10) starting.
    370F2EA51F5F1A734FA2D40AFA1AC1F3
    User is not Guest
    No Administrator Privileges
    Failed to detect access rights
    OS Version - Unix 4.2.0.29
    .net Version - 4.0.30319.17020
    Current Directory - /opt/picoscope/lib
    Command Line - /opt/picoscope/lib/PicoScope.GTK.exe
    Settings file version - 11.2.0
    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 ps6000.dll
    Finished loading ps6000.dll
    Opening device using DLL ps6000.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 UnitNotFound
    Attempting to load ps5000a.dll
    Finished loading ps5000a.dll
    Opening device using DLL ps5000a.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 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 ps4000.dll
    Finished loading ps4000.dll
    Opening device using DLL ps4000.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps3000a.dll
    Finished loading ps3000a.dll
    Opening device using DLL ps3000a.dll
    Opening device successful. Error NoError.
    Device opened AV700/184: PS3000A PS3204A PS3000A
    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 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 ps3000.dll
    Finished loading ps3000.dll
    Opening device using DLL ps3000.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 ps2000.dll
    Finished loading ps2000.dll
    Opening device using DLL ps2000.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 pl1000.dll
    Finished loading pl1000.dll
    Opening device using DLL pl1000.dll
    Opening device unsuccessful. Error UnitNotFound
    No of Devices Found: 1
    Device selected: PS3204A, AV700/184
    Driver: ps3000a.dll Version: PS3000A Linux Driver, 1.4.5.45
    Kernel driver: picopp.sys Version: PS3000A Linux Driver, 1.4.5.45
    Complete
    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
    Trace Closing
closed.

Hitesh

Re: Latest version doesn't find my PicoScope

Post by Hitesh »

Hi madrang,

Good to hear that it is working now. :)

I have forwarded on your suggestions regarding the error and log file to our Development Team.

Regards,

Colonel
Newbie
Posts: 0
Joined: Thu Feb 05, 2015 7:06 pm

Re: Latest version doesn't find my PicoScope

Post by Colonel »

Hi again,

Testing with version 6.11.8.3, crashes too, here is the log

Code: Select all


    Trace opened 17/04/2016.
    Running on Mono - True
    Mono Display Name - 3.2.8 (Debian 3.2.8+dfsg-4ubuntu1.1)
    Host Operating System - Linux
    64Bit Operating System - True
    64Bit Process - True
    Logical Processors - 8
    Application 'PicoScope 6 Beta' (version 6.11.8.3) starting.
    BF057D585731703EA97FE6591F8797C3
    User is not Guest
    No Administrator Privileges
    Failed to detect access rights
    OS Version - Unix 3.16.0.38
    .net Version - 4.0.30319.17020
    Current Directory - /opt/picoscope/lib
    Command Line - /opt/picoscope/lib/PicoScope.GTK.exe
    Settings file version - 11.2.0
    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 ps6000.dll
    Finished loading ps6000.dll
    Opening device using DLL ps6000.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 UnitNotFound
    Attempting to load ps5000a.dll
    Finished loading ps5000a.dll
    Opening device using DLL ps5000a.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 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 ps4000.dll
    Finished loading ps4000.dll
    Opening device using DLL ps4000.dll
    Opening device unsuccessful. Error UnitNotFound
    Attempting to load ps3000a.dll
    Finished loading ps3000a.dll
    Opening device using DLL ps3000a.dll
    Opening device successful. Error NoError.
    Device opened CY759/028: PS3000A_USB30_PANTHER PS3403D PS3000A
    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 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 ps3000.dll
    Finished loading ps3000.dll
    Opening device using DLL ps3000.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 ps2000.dll
    Finished loading ps2000.dll
    Opening device using DLL ps2000.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 pl1000.dll
    Finished loading pl1000.dll
    Opening device using DLL pl1000.dll
    Opening device unsuccessful. Error UnitNotFound
    No of Devices Found: 1
    Device selected: PS3403D, CY759/028
    Driver: ps3000a.dll Version: PS3000A Linux Driver, 1.4.5.45
    Kernel driver: picopp.sys Version: PS3000A Linux Driver, 1.4.5.45
    Complete
    Attempting to open PS6 File, /home/user/.local/share/Pico Technology/260a68f1-c314-451b-830f-0a5e01d65514/default.PSSETTINGS
    File application version: 6.11.8.10
    Time Activating ruler
    Time Activating ruler
    Time Activating ruler
    Time Activating ruler
    Probe light manager changed light state to True
    Probe light manager changed light state to True
    Trigger set to : NonAdvancedEdge
    Source/Channel Index Changed to 0
    Trigger Direction set to Exiting
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    Device reported to application the Power Adapter being unplugged.
    Close Properties panel item clicked
    Trigger set to : NonAdvancedEdge
    Time Deactivate ruler
    Time Reset ruler
    ToggleCapture start
    Run.Pressed=True
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    LiveTrigger drag start
    Trigger set to : NonAdvancedEdge
    LiveTrigger moved to PreTrig 14,39563 : Threshold 5,056 mV
    LiveTrigger drag start
    Trigger set to : NonAdvancedEdge
    LiveTrigger moved to PreTrig 9,824213 : Threshold 5,13 mV
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    LiveTrigger drag start
    Trigger set to : NonAdvancedEdge
    LiveTrigger moved to PreTrig 10,07864 : Threshold 2,305 mV
    LiveTrigger drag start
    Trigger set to : NonAdvancedEdge
    LiveTrigger moved to PreTrig 9,984112 : Threshold 4,758 mV
    Trigger set to : NonAdvancedEdge
    Trigger set to : NonAdvancedEdge
    The application was unexpectedly closed.

Hitesh

Re: Latest version doesn't find my PicoScope

Post by Hitesh »

Hi Colonel,

I have responded via this post.

Regards,

cereal
Newbie
Posts: 0
Joined: Sun May 01, 2016 3:16 pm

Re: Latest version doesn't find my PicoScope

Post by cereal »

Another report that the app can't detect my device but the usbtest however can. I'm running Ubuntu 16.04, not sure if anyone has gotten it to work on that yet.

Code: Select all

$ /opt/picoscope/share/doc/libps2000a/usbtest

****************************************************************************
*                  Pico Technology Linux USB Diagnostics                   *
****************************************************************************

This script looks for Pico USB devices connected to your computer
and checks whether you are able to access them. If your user account
does not have permission to access the devices, the script will try
to suggest how to correct this for your particular Linux installation.

Press enter to continue...

Getting user and group information...
 - You are running this script as cereal.
 - You are in the following groups:
     cereal sudo pico

Please connect your Pico USB device and press enter to continue...

Pico USB device found: /dev/bus/usb/002/008

 - It belongs to root (which is not you) who has permissions rw-
 - The members of group pico (which you are in) have permissions rw-
 - Everyone else has permissions r--
 - You can write to this device and so will be able to use it.

Hitesh

Re: Latest version doesn't find my PicoScope

Post by Hitesh »

Hi cereal,

Which version of Mono do you have installed?

It might be helpful to see the trace.xml file corresponding to the last PicoScope session (the location is an earlier post in this thread).

Regards,

Post Reply