libpicoipp installation error on linux and Raspberry Pi

[AndrewA]

When trying to install
https://labs.picotech.com/debian/pool/m ... _armhf.deb
on an raspbian, You may get an error message saying

Code: Select all

dpkg: error processing archive libpicoipp_1.1.2-4r56_armhf.deb (--install):
conffile name 'etc/ld.so.conf.d/picoscope.conf' is not an absolute pathname

Seems like recently dpkg do not accept relative pathnames in DEBIAN/conffiles so a quick fix would be to do:

Remove any Pico drivers installed (sudo apt get remove libpXXXX... etc)
NOTE: Steps 1-5 below are not required for dataloggers, goto step 6. (libpicoipp is not required)

Download the file above (libpicoipp_1.1.2-4r56_armhf.deb) into /home/pi/ for example
1.

Code: Select all

mkdir tmp

2.

Code: Select all

dpkg-deb -R libpicoipp_1.1.2-4r56_armhf.deb tmp

3. Edit tmp/DEBIAN/conffiles
and remove the first line-
"etc/ld.so.conf.d/picoscope.conf"

4. Rebuild the deb file

Code: Select all

dpkg-deb -b tmp libpicoipp_1.1.2-4r56_armhf_fixed.deb

5. Install rebuilt file-

Code: Select all

sudo apt install /home/pi/libpicoipp_1.1.2-4r56_armhf_fixed.deb

This removes the first line in conffiles
I have created a bug relating to this issue.

6. Install the required Pico driver-
You need to manually download and install the scope driver (libpsXXXXx.deb) for your model PicoScope/PicoLogger.
(See the Programmer guide selected for your model on www.picotech.com/downloads to know the correct driver/API to install)
Driver packages are found here- https://labs.picotech.com/debian/pool/main/
In either the /libp or /libu folder.

Choose the latest *armhf.deb file in the directory.
For example for the libps2000a driver to use-
https://labs.picotech.com/debian/pool/m ... _armhf.deb

To install the deb file use-

Code: Select all

sudo dpkg --force-depends -i ./libps2000a_2.1.110-5r3464_armhf.deb

Replace "./libps2000a_2.1.110-5r3464_armhf.deb" with your path and name of the deb file to install.
You may see some ERROR messages these can be ignored.

7. I suggest you also remove or rename the picoscope sources file if you did this step before. This stops your package manager from over writing any of these packages.

Code: Select all

mv /etc/apt/sources.list.d/picoscope.list /etc/apt/sources.list.d/picoscope.listbu

[potto]

Thanks Andrew. That solved my problem when trying to install libps2000a on a Raspberry Pi 3. Below is what was happening before I used your instructions to rebuild and install libpicoipp. Is Pico Technology planning on fixing this so the command "sudo apt install libps2000a" works without error on the Raspberry Pi? When I installed "libps2000" I did not have the same problem. Thanks for supporting the Pi. Cheers, Paul

=====Error before manually installing libpicoipp====
$ sudo apt install libps2000a
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libps2000a : Depends: libpicoipp (>= 1.1.2-4r52) but it is not installable
E: Unable to correct problems, you have held broken packages.

[jade]

fyi Andrew: This is now affecting Debian Buster on x86_64 as well.
I appreciate that Linux is probably not considered an important platform compared to others, but is there any progress on the bug? It would be nice to have working/fixed packages available in the repositories as currently having the picoscope repositories enabled breaks system updates for me unless I remove the packages.

[jb2717]

Hello,

Am also having this problem on Pop!_OS 20.10

[RandomRDP]

This may be obvious but I just spent an hour trying to fix this problem on Ubuntu 20.10 on my laptop.

If you're on an x86 machine then download "libpicoipp_1.3.0-4r78_amd64.deb" instead.

https://labs.picotech.com/debian/pool/m ... _amd64.deb

[IvanSB]

Well actually the x86 newer version has still the same bug.

Preparing to unpack .../libpicoipp_1.3.0-4r78_amd64.deb ...
dpkg: error processing archive /var/cache/apt/archives/libpicoipp_1.3.0-4r78_amd64.deb (--unpack):
conffile name 'etc/ld.so.conf.d/picoscope.conf' is not an absolute pathname

[AndrewA]

Update for libpicoipp issues.
Installation on x86 should be fixed now. Or if not be available on the next release of PicoScope 6 for linux.
You can try installing PicoScope 7 version if wish to - https://labs.picotech.com/rc/picoscope7 ... _amd64.deb

Unfortunately libpicoipp for armhf is still stuck at version 1.1.2-4r56. This would change until a build issue is resloved.

For now here is are some steps to use the shared libraries files ("drivers") from PicoLog 6 software.
PicoLog 6 software is widly used so drivers are more tested than the SDK packaged versions.
I have tested the below steps using 6.2.1 of PicoLog.
Current version can be download from https://www.picotech.com/downloads/_lig ... 6-raspbian

1. Extract the shared libraries files from PicoLog 6 installer-
Extact the contains of this path in the installer-

Code: Select all

/picolog-6.2.1-armhf.deb/data.tar.gz/data.tar/./opt/PicoLog/resources/

to

Code: Select all

/home/pi/picolog621drivers

As an example.

2. In the terminal you are going to run your executable from issue the following command-

Code: Select all

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/pi/picolog621drivers

Note this setting will only apply to this terminal, so for a new terminal or reboot you need to reissue the command.
You could can add this to part of a script to call you program.

I did try another method to make this a global change-
Add the folder path to this file (on a new line)-
/etc/ld.so.conf
save the the file
Then reloading the list of system-wide library paths using-
ldconfig
But this did not work, even through they where listed when using the command-
ldconfig -v

[kpizzolatto]

Briefly:
I want to use a python script to collect data from a 5244D in Block mode with a raspberry pi 4b.
Can I use libps5000a-2.1.40 instead of 2.1.75 to do that? What features will I lose by using the older driver? Will libpicoipp be brought forward for raspberry pi?

Details:

I would like to use a 5244D MSO to collect some diagnostic data triggered around an event.
The large number of samples 256/512 MS and greater resolution are important.

The scope and the raspberry pi 4b that controls it would be left in the cabinet for days or weeks waiting for the event to occur. The "A" input will capture the signal of interest. A PLC will normally apply 24V to the "B" input & when the event occurs, the "B" input will go low. The sample buffer will then be retrieved from the scope and saved to disk by the raspberry pi.

I've purchased a 2204A and downloaded the python wrappers to try all this out with a less expensive unit before purchasing the 5244D MSO.
The 2204A works great for this idea! After a couple parameter changes and adding a couple lines to export to csv, ps2000BlockExample.py does exactly I want.
So now I want to buy the 5244D in order to get the buffer size and vertical resolution I need.

My concern is that the latest libps5000a runs into the libpicoipp issue:

Code: Select all

$ sudo apt install ./libps5000a_2.1.75-5r2957_armhf.deb
... 
The following packages have unmet dependencies:
 libps5000a : Depends: libpicoipp (>= 1.3.0-4r78) but 1.1.2-4r56 is to be installed

So, I have installed instead version 2.1.40

Code: Select all

 $ apt-cache policy libps5000a
libps5000a:
  Installed: 2.1.40-5r2131
  Candidate: 2.1.75-5r2957
  Version table:
     2.1.75-5r2957 500
        500 https://labs.picotech.com/debian picoscope/main armhf Packages
 *** 2.1.40-5r2131 100
        100 /var/lib/dpkg/status

Questions:

• Is there a changelog for the driver libs?
• What features do I lose by using version 2.1.40 rather than 2.1.75?
• Will libpicoipp get an update for raspberry pi so we can use current drivers?
• Is my application supported by libps5000a-2.1.40?

[tahasaddiki]

hello community ,

I encountered while trying to install the "libps5000a" driver on my Raspberry Pi 3.
I am developing a project that involves using the PicoScope 5244D. I have followed the provided instructions and attempted to install "libps5000a" using the (picotech.com/support/topic40928.html), but I encountered dependency issues during the installation process. Specifically, it reported unsatis-fied dependencies "libpicoipp (>= 1.4.0-4r161) but 1.1.2-4r56 Needs to be Installed".
I need your help guys .

Best regards,
Taha SADDIKI

[AndrewA]

Another customer has reported that downgrading the kernel to version 5.10 fixes this issue see-
viewtopic.php?p=149605#p149605
I have not tested this myself but believe the issue is caused by the OS as I tried old version of the driver which
has always worked.

[swarup2906]

Hello @AndrewA,

with which build of raspbian os (and which kernel version) did you try to install the picoscope driver?
Could you please provide the details?

[AndrewA]

Good News!
All related bugs and issues for 32-bit Raspberry Pi OS (armhf) have now been fixed and are available!
Please follow the steps at the bottom of this page-
https://www.picotech.com/downloads/linux

armhf packages are in the PicoScope 7 early access Repo-
https://labs.picotech.com/rc/picoscope7/debian/