Picoscope 7 / 2204A device not visible

Post any questions related to the new PicoScope 7 software
Post Reply
jamescarlyle
Newbie
Posts: 0
Joined: Wed Nov 23, 2022 3:50 pm

Picoscope 7 / 2204A device not visible

Post by jamescarlyle »

Hi

I'm trying to run a Picoscope 2204A on Debian on a Chromebook (where I have to approve USB devices).

Code: Select all

Operating System: Debian GNU/Linux 11 (bullseye)
            Kernel: Linux 5.10.142-19743-gd301e86c39f7
      Architecture: x86-64
I can see the usb device using

Code: Select all

lsusb

Code: Select all

Bus 001 Device 016: ID 0ce9:1007 Pico Technology PicoScope 2000 series PC Oscilloscope
I'm running

Code: Select all

PicoScope 7 T&M Early Access - PC oscilloscope software 
version: 7.0.113.13201
but when I start it only shows a demo device and "PicoScope 2000 .... searching"

My trace.xml shows

Code: Select all


    Trace opened 11/23/2022.
    Application 'PicoScope 7 T&M Early Access' (version 7.0.113.13201 X64) starting.
    2966D0D28EE892F10F5455575B95DAA2
    User is not Guest
    No Administrator Privileges
    OS Version - Linux Debian GNU/Linux
    .net Version - 4.0.30319.42000
    Settings file version - 11.5.1
    Preferences file version - 2.0.0
    Probes file version - 1.0.0
    Data file binary header version - 1
    Loaded libusb-1.0 ver. 1.0.24.11584
    USB Hotplug available
    Using default culture: English (United States).
    Attempting to load ps2000.dll from '/opt/picoscope/lib/libps2000.so'
    Checking driver '/opt/picoscope/lib/libps2000.so' exists in executable path '/opt/picoscope/lib/
    Finished loading ps2000.dll
    Attempting to load ps2000.dll from '/opt/picoscope/lib/libps2000.so'
    Checking driver '/opt/picoscope/lib/libps2000.so' exists in executable path '/opt/picoscope/lib/
    Finished loading ps2000.dll
    Opening device using DLL ps2000.dll
    NoData
    GlobalDeviceManager.Close()
Can anyone provide some pointers about what might be wrong or where I should go next? Annoyingly, one time I could see the Picoscope device listed but greyed out, and the OK/Cancel buttons were also disabled.

Many thanks
James

jamescarlyle
Newbie
Posts: 0
Joined: Wed Nov 23, 2022 3:50 pm

Re: Picoscope 7 / 2204A device not visible

Post by jamescarlyle »

I've got my scope working with a dedicated Linux machine, so I'm guessing my problem was related to the fact that Chromebook exposes Linux in a container (and I assume the USB data is somehow being mangled). So this request is no longer urgent, but I'd be happy to be a guinea pig if Chromebook compliance is desired.

Martyn
Site Admin
Site Admin
Posts: 4491
Joined: Fri Jun 10, 2011 8:15 am
Location: St. Neots

Re: Picoscope 7 / 2204A device not visible

Post by Martyn »

This is probably related to the two step start up process for a PicoScope. Initially they are identified as a simple PicoTech USB device as seen by your Chromebook, but then when opened by the software the firmware is loaded onto the device, it then disconnects and reconnects on the USB bus, and re enumerates. The timing of this process may be the issue on the Chromebook.
Martyn
Technical Support Manager

Tony Garland
Newbie
Posts: 0
Joined: Sat Feb 04, 2023 12:13 am

Re: Picoscope 7 / 2204A device not visible

Post by Tony Garland »

I'm seeing something similar. I'm running Picoscope T&M Early Access 7.0.117.13870. My picoscope is a 2204B MSO (serial # JZ232/0116).

I have two MacBook Pro laptops. One is an Intel-based 2016 (running Monterey 12.6.3) and the other an M1MAX-based 2021 (running Ventura 13.1)

The Intel-based machine can recognized and load the scope when directly connected and most of the time when through a USB hub -- but not always.

The M1-based machine has more difficulty. It recognizes and load the scope after a fresh reboot when directly connected -- no intervening hub. I've rarely seen it identify the scope through a hub.

After booting and using it with a direct connection, then exiting the app, it becomes increasingly unlikely it will successfully load after being identified. When a hub is connected, it typically doesn't even identify -- although I have seen it work once or twice (identify and successfully load) with a hub.

Generally, if I futz around enough, I can get things working going back to direct connection and after rebooting. That's often when I have many windows up and am deeply nested in a trouble-shooting context so it makes for some pain to have to reboot.

I'm now to Picoscope and if there is anything I should be doing to collect helpful data or help make this work more reliably. on my newer machine -- and through hubs in generally -- do let me know.

Thanks - Tony

Tony Garland
Newbie
Posts: 0
Joined: Sat Feb 04, 2023 12:13 am

Re: Picoscope 7 / 2204A device not visible

Post by Tony Garland »

An update: I recently upgraded to version 7.0.120.14428 and have been able to connect to the 2204A successfully on my M1 Mac. Haven't done a bunch of testing, but where I wasn't able to connect with version 7.0.117.13870, by merely upgrading to the latest version (no other changes, no reboot) it successfully gets past the "loading" stage and establishes a fully-operational connection.

Will report back if I see any problems going forward.

Post Reply