Skip to content

PixelPulse2 Linux AppImage

Set up Pixelpulse2 in minutes! No need to fumble with dependencies before class

Credits and Greetings

Setup Instructions

TIP

I maintain the SoarPkgs entry for Pixelpulse2! This means that running Pixelpulse2 will be a breeze for linux users. See SBUILD configuration and SoarPkgs page

Automatic Method 😎

  • Install Soar

    bash
    wget -qO- https://soar.qaidvoid.dev/install.sh | sh

    or

    bash
    curl -fsSL https://soar.qaidvoid.dev/install.sh | sh
    • Run the App without installing
      bash
      soar run pixelpulse2 -- --getudev

WARNING

Remember to connect your Adalm1000 Board only after the app opens for the first time and udev rules are installed.

  • Install the App(Optional)
    bash
    soar install pixelpulse2
  • Run the App
    bash
    pixelpulse2 --getudev

NOTE

The getudev flag tells it to generate and install udev rules into your OS, so that your Adalm1000 is detected without problems. It is recommended to run it with that the first time you open it.

Manual Method 💪

Show Manual Installation Method
  • Remove Previous versions of the AppImage(Optional, replace with correct path as needed)
    bash
    rm Downloads/Pixelpulse2*.AppImage
  • Download the version compatible with your system from above
  • Go to the folder you saved it to(replace with correct path)
    bash
    cd Downloads
  • Give it executable permissions
    bash
    chmod +x Pixelpulse2*.AppImage
  • Run the AppImage
    bash
    ./Pixelpulse2*.AppImage --getudev
    • The getudev flag tells it to generate and install udev rules into your OS, so that your Adalm1000 is detected without problems. It is recommended to run it with that the first time you open it.
If you're debugging udev rules and crashes upon device plug, see this

Delete Existing rule

bash
sudo rm -rf /etc/udev/rules.d/53-adi-m1k-usb.rules

WARNING

Remember to unplug your device.

Run the AppImage with --getudev flag again

bash
./Pixelpulse2*.AppImage --getudev

After it opens, you can reconnect your device.

Known Issues:

  1. The app is known to crash if you plug in the device without configuring udev rules
    • Do that, and ensure the device is unplugged.
    • reload
  2. The app is known to crash after being open for some time
  • This can be replicated on some distros by connecting a device and letting it run for a while

    • This happens on:
      • OpenSUSE Tumbleweed(Jan 2025, x86_64 build)
      • Fedora(Testimony by @vishal-ahirwar (issues/266))
  • This is likely not an issue caused by my packaging

  • There is an issue opened upstream (issues/266) that tracks this problem

Notes:

Tested on:

  • OpenSUSE tumbleweed on Jan 2025(x86_64 build)

Old Versions(not recommended):