sometimes picoscope is not detected

[GoogleCodeExporter]

Sometimes picoscope is not detected. and acquisition fails to create a valid 
instance.

Note that in Picotech's sample application there is a retry.

But from my testings, seems like only plugging/unplugging the device solves the 
issue.

Original issue reported on code.google.com by vincent....@gmail.com on 27 Feb 2013 at 9:46

[GoogleCodeExporter]

Original comment by vincent....@gmail.com on 27 Feb 2013 at 9:53

• Changed title: [BUG] - sometimes picoscope is not detected

[GoogleCodeExporter]

Original comment by vincent....@gmail.com on 27 Feb 2013 at 9:54

• Changed title: sometimes picoscope is not detected
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I also have issue with the device detection with QPicoscope.
My picoscope 2105 was unable to use without root authority.
Running QPicoscope with sudo command detects the device.
$sudo QPicoscope

Is there any possibility to run QPicoscope without root authority?

Besides, I really appreciate your great work with this project, vincent!

Here are what I did so far below.

I installed qpicoscope using terminal.
$svn checkout http://qpicoscope.googlecode.com/svn/trunk/ qpicoscope-read-only
$cd ~/qpicoscope-read-only
$./autogen.sh
$./configure
$make
$sudo make install

Then I ran QPicoscope from terminal without root authority.
$QPicoscope

The QPicoscope window came up but the device was not detected.
I tried several times plugging/unplugging but it was never detected.

I executed
$lsusb

the message was;
...
Bus 001 Device 009: ID 0ce9:1007 pico Technology

I also executed the usbtest of the driver.
$cd ~/qpicoscope-read-only/lib/libps2000-2.0.7.7-1.x86_64/
~/qpicoscope-read-only/lib/libps2000-2.0.7.7-1.x86_64$ ./usbtest > log.txt

the message was;

****************************************************************************
*                  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.

Getting user and group information...
 - You are running this script as takashi.
 - You are in the following groups:
     takashi adm cdrom sudo dip plugdev lpadmin sambashare pico

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

 - It belongs to root (which is not you) who has permissions rw-
 - The members of group root (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 

   Pico USB device not found. Please try again
(end of the message)

Finally, it was successful running QPicoscope using sudo command;
$sudo QPicoscope

-------------------------------------------------------
Device;
PicoScope 2105

OS;
Ubuntu 12.04 LTS 64bit precise
clean install into SSD

kernel;
3.2.0-39-generic

Hard;
lenovo X220
CPU Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz

Thank you

Original comment by takashi....@gmail.com on 27 Mar 2013 at 10:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi,

I can see 3 possible issues why you are only seeing the device as root:
1- the Picotech's udev rule /etc/udev/rules.d/95-pico.rules is not good. Just 
try to modify the rule with this one:
ATTRS{idVendor}=="0ce9", ATTRS{idProduct}=="1007", MODE="664",GROUP="pico"
Note taht on my machine I don't specify the product id, in order to support 
several devices. So my rule is the following:
ATTRS{idVendor}=="0ce9", MODE="664",GROUP="pico"

2 - the group "pico" doesn't exist. As root run "addgroup pico"

3- your user doesn't belong to the "pico" group. Try "usermod -a -G pico 
<your_uername>"

Tell me if this helps.

Regards,

Vincent

Original comment by vincent....@gmail.com on 28 Mar 2013 at 8:24

[GoogleCodeExporter]

Hello, Vincent.

Thank you for your quick reply.

>1- the Picotech's udev rule /etc/udev/rules.d/95-pico.rules is not good. Just 
try to modify the rule with this one:
>ATTRS{idVendor}=="0ce9", ATTRS{idProduct}=="1007", MODE="664",GROUP="pico"
>Note taht on my machine I don't specify the product id, in order to support 
several devices. So my rule is the following:
>ATTRS{idVendor}=="0ce9", MODE="664",GROUP="pico"

I modified /etc/udev/rules.d/95-pico.rules with
ATTRS{idVendor}=="0ce9", ATTRS{idProduct}=="1007", MODE="664",GROUP="pico"

I followed your tips 2 and 3. Then it worked without root permission.

Thank you again for your help!

Regards,

Takashi

Original comment by takashi....@gmail.com on 28 Mar 2013 at 12:41

[GoogleCodeExporter]

Hi,
I can't get my 2205MSO to recognize at all

it keeps repeating the following message:
"acquisition2000.cpp    - Acquisition2000:  [51]    DEBUG: Opening the device...
acquisition2000.cpp - Acquisition2000:  [55]    DEBUG: Handle: 0
acquisition2000.cpp - Acquisition2000:  [58]    DEBUG: Unable to open device
acquisition.cpp - get_instance: [76]    DEBUG: No Picoscope 2000 series found.
acquisition2000.cpp - ~Acquisition2000: [95]    DEBUG: Device destroyed
search-for-acquisition-device-worker.cpp    - 
searchForAcquisitionDevice: [56]    ERROR: Acquisition::get_instance returned 
NULL."

It seems irrelevant if I have the scope plugged in or not. Picotech's usbtest 
and the example program run just fine. Have I perhaps done something wrong 
while compiling the software? I used the autotools method.

"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."

Thank you for developing this software.

Original comment by juuso.me...@gmail.com on 6 Aug 2013 at 9:10

[GoogleCodeExporter]

Hi,

It looks like the 2205MSO is not using libps2000 but libps2000a, with a 
different API (even if it looks similar).

For now QPicoscope is only using libps2000 and libps3000.

You can try to run your 2205MSO using the 2205 driver (libps2000) but for sure 
digital signal inputs won't work.

On my side I will have a look at libps2000a to see if I can integrate it in 
QPicoscope.

Thanks for using QPicoscope.

Vincent

Original comment by vincent....@gmail.com on 6 Aug 2013 at 9:26