Running->Stopped bug

Discussion forum for the new Picoscope Linux software
tonyhb
Newbie
Posts: 0
Joined: Mon Jul 18, 2016 3:49 pm

Running->Stopped bug

Post by tonyhb » Mon Jul 18, 2016 3:55 pm

After stopping the capture, it is usually impossible to return to "running" without restarting the application.
However, maybe one time in twenty or thirty, it does actually work on the first attempt.
If it doesn't work on the first attempt (clicking or otherwise), it never goes back to "running"

Otherwise, the scope is superb.

Details:

Model: PicoScope 2405A
Serial Number: DX092/0012
USB Version: 2.0
Calibration Date: 29 March 2016
Hardware Version: 1
Driver Version: PS2000A Linux Driver, 1.1.6.18
Firmware Version: 1.3.3.0 / 1.0.32.0

OS: Ubuntu Mate 16.04 fully up-to-date

Hitesh
Site Admin
Site Admin
Posts: 2829
Joined: Tue May 31, 2011 3:43 pm
Location: St. Neots, Cambridgeshire

Re: Running->Stopped bug

Post by Hitesh » Thu Jul 21, 2016 2:23 pm

Hi tonyhb,

Does the problem occur on any other PCs running Ubuntu or a Windows PC?

Could you please save a data file or settings file from the File menu so that your settings can be tested here.

A trace.xml file corresponding to a session where this problem occurs would be helpful - this can be found in the following location:

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

Regards,
Hitesh

Technical Support Engineer

tonyhb
Newbie
Posts: 0
Joined: Mon Jul 18, 2016 3:49 pm

Re: Running->Stopped bug

Post by tonyhb » Tue Jul 26, 2016 11:23 pm

Hi Hitesh,

Here are the settings and trace.xml (attached). Not possible to test on another Linux box at present.
Attachments
trace.xml
(18.09 KiB) Downloaded 214 times
20160727-0001.pssettings
(3.71 KiB) Downloaded 211 times

Hitesh
Site Admin
Site Admin
Posts: 2829
Joined: Tue May 31, 2011 3:43 pm
Location: St. Neots, Cambridgeshire

Re: Running->Stopped bug

Post by Hitesh » Wed Jul 27, 2016 2:07 pm

Thanks tonyhb,

I've run the software on Ubuntu 14.04 using the settings file but am unable to reproduce the problem.

Are you using the supplied blue USB cable, and if you are using a desktop PC, are you using the front or rear USB ports? Are the USB ports USB 2.0 or USB 3.0?

If you do experience another occasion where the software only starts again after 20 or so clicks, please close the software, capture the trace.xml file and post it here, or e-mail it to support@picotech.com.

Regards,
Hitesh

Technical Support Engineer

tonyhb
Newbie
Posts: 0
Joined: Mon Jul 18, 2016 3:49 pm

Re: Running->Stopped bug

Post by tonyhb » Wed Jul 27, 2016 5:13 pm

Hi Hitesh,

The PC is a Macbook Air 7.2. Running lsusb and lsusb -D shows that USB 2.0 is being used. The same problem occurs regardless whether other devices are connected, or if it is run via a hub (various permutations tested).

The problem is nearly 100% consistent, and only once out of maybe fifty times, did the scope restart today. IIRC, the problem wasn't present when I first used it a couple months ago, and it may be due to an Ubuntu upgrade (or possibly some complication with the MB hardware). I would recommend trying it out on Ubuntu 16.04, as this is going to be an increasingly widely used Linux distribution anyway.

As a temporary work-around, I have found that clicking the "Home" button will reliably restart the scope (obviously the current settings are lost, but it's better than closing the app and restarting).

Hitesh
Site Admin
Site Admin
Posts: 2829
Joined: Tue May 31, 2011 3:43 pm
Location: St. Neots, Cambridgeshire

Re: Running->Stopped bug

Post by Hitesh » Thu Aug 04, 2016 10:59 am

Hi Tony,

I have been able to reproduce the problem on an Ubuntu 16.04 install and have reported this to our Development Team.

You could try storing the settings via the File menu and then loading them via the Start-up settings sub-menu as a workaround for now.

Regards,
Hitesh

Technical Support Engineer

tonyhb
Newbie
Posts: 0
Joined: Mon Jul 18, 2016 3:49 pm

Re: Running->Stopped bug

Post by tonyhb » Thu Aug 04, 2016 1:35 pm

Hi Hitesh,

Greatly appreciated.

element
Newbie
Posts: 0
Joined: Sat Jan 31, 2015 9:13 pm

Re: Running->Stopped bug

Post by element » Fri Aug 05, 2016 12:19 am

See below for a solution to this problem..

I've been using a 2205MSO PicoScope in Linux for over 18 months and it has worked well. However, I just tried using it and am now running in to what I think is this same issue. I uninstalled all PicoScope related packages and reinstalled them, without any improvement.

To reproduce the problem:
1. Enable D0 and D1 logic lines
2. Set Trigger to Repeat

At that point it goes into the Stopped state and cannot be restarted without restarting the program or clicking the Connect Device option on the File menu (which resets all the trigger settings).

My system is Ubuntu 16.04 on a 64 bit system.

I'm happy to say though I resolved the issue for now. After looking through my APT log I discovered that the picomono package was updated back in June. I downgraded this package to 2.10.8-1r01 (instead of r02), which can be found here:
https://labs.picotech.com/debian/pool/m ... _amd64.deb

It is now working again. So there is something wrong with the newer r02 version of this package and Ubuntu 16.04.

Best regards,

Element Green

element
Newbie
Posts: 0
Joined: Sat Jan 31, 2015 9:13 pm

Re: Running->Stopped bug

Post by element » Fri Aug 05, 2016 12:49 am

I spoke too soon. The issue is still occurring, seems it just worked a couple times and is now back to doing the same thing again. I also noticed that even when it did work and captured some data on a trigger, the scope would suddenly disconnect and stop working. It seems it also does this with analog triggering (falling edge for example).

I tried it on another Linux system also with Ubuntu 16.04 and a slightly older version of PicoScope. I was able to get it to work somewhat, but it also suffers from the disconnect issue.

I hope this gets fixed soon.

Best regards,

Element Green

Hitesh
Site Admin
Site Admin
Posts: 2829
Joined: Tue May 31, 2011 3:43 pm
Location: St. Neots, Cambridgeshire

Re: Running->Stopped bug

Post by Hitesh » Fri Aug 05, 2016 8:53 am

Hi element,

Thank you for your posts. I have added your comments to the bug report.

Regards,
Hitesh

Technical Support Engineer

emandersson
Newbie
Posts: 0
Joined: Sun Aug 14, 2016 11:21 am

Re: Running->Stopped bug

Post by emandersson » Sun Aug 14, 2016 11:43 am

I also have this problem, Here is how I reproduce it:
Start PicoScope
Set trigger to single
Fire my signal (which is captured nicely)
Click the start button (the green one with an arrow on in the lower left corner) (the scope starts to run again)
Fire my signal (which again is captured nicely)
Click the start button and it wont start.

So basically I can capture two signals before I have to restart the program.

Toshiba L750, Pentium B960, 4GB ram, Debian 8
Picoscope version 6.11.13.3 (installed with apt-get 2016-Aug-10)

Edit: Forgot to tell it is a PicoScope 2203
Last edited by emandersson on Sat Aug 27, 2016 2:37 pm, edited 1 time in total.

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

Re: Running->Stopped bug

Post by Martyn » Mon Aug 15, 2016 6:23 am

Can you post a psdata file for this, we can then run it here to see what the issue is. If you are using the siggen for the signal it will be included in the file, if not please describe what the signal is.
Martyn
Technical Support Manager

emandersson
Newbie
Posts: 0
Joined: Sun Aug 14, 2016 11:21 am

Re: Running->Stopped bug

Post by emandersson » Sat Aug 27, 2016 2:34 pm

Oh sorry it took so long, I didn't have "Notify me when a reply is posted" -checkbox filed in : -)

It was just an ordinary square puls, 0 to 5V.

Hitesh
Site Admin
Site Admin
Posts: 2829
Joined: Tue May 31, 2011 3:43 pm
Location: St. Neots, Cambridgeshire

Re: Running->Stopped bug

Post by Hitesh » Wed Aug 31, 2016 11:25 am

Hi emandersson,

The issue is reproducible on Ubuntu 16.04 LTS so I have updated the existing bug report.

Regards,
Hitesh

Technical Support Engineer

DBlueman
Newbie
Posts: 0
Joined: Thu Sep 01, 2016 8:56 am

Re: Running->Stopped bug

Post by DBlueman » Thu Sep 01, 2016 9:01 am

I too have been experiencing the exact same issue since purchasing my PicoScopw 3206DMSO 9 months ago, costing a fair a mount of hassle.

I'm running Picoscope 6.11.13.3, driver 1.4.6.17, firmware 1.4.0.0/1.0.44.0 on stock Ubuntu 16.04, however the issue also occurs on Ubuntu 15.10.

Please reproduce and fix, Picotech!

Daniel

Post Reply