pigg - Raspberry Pi GPIO GUI

An app for Raspberry Pi GPIO Output control and Input visualization, built in rust using the Iced GUI toolkit and rppal GPIO crate.

The GUI binary (Pi Gpio GUI - PIGGUI) is affectionately known as "piggy".

Currently, when run on a Pi, you can configure the Pi's GPIO hardware Inputs or Outputs, controlling the level of the Outputs and view the level of the Inputs.

It runs on macOS/Linux/Windows. When we add networking support, this will allow you to control the Pi GPIO hardware remotely.

What's new in Release 0.5.0 - Pi Pico W Support!

The pigg project now has initial Raspberry Pi Pico W support!!!

It's a first version and is missing a few things we have planned on the roadmap, but it's a great start!

Pi Pico support includes:

• Embedded application porky for running on the Pi Pico W
• UF2 Image provided as part of release to aid programming Pi Pico W devices with porky
• Ability to build porky yourself with default SSID information so all devices with built binary connect automatically to Wi-Fi
• USB direct connection between piggui and porky that allows you to:
  • Discover USB connected porky devices
  • View information about the device
  • Determine if it is connected to the Wi-Fi network and if it is, get its IP and Port for remote GUI use
  • Program an "override" Wi-Fi network it will use to connect to, instead of the default one as part of the build. This is persisted in Flash memory, so it is used again on restart/reboot.
  • Reset the "override" Wi-Fi (removing it) so that on restart the device will connect to the default one if it exists. If not, it will restart, connect to USB and wait to be programmed with a Wi-Fi network to connect to.
• Remote network access to the (headless) Pico W's GPIO, in the same GUI as remote access to Raspberry Pis (not Pico).
• Pi Pico specific pin layout and numbering displayed in GUI

NOTE: Support for Pi Pico (not W), Pi Pico 2 (not W) and Pi Pico 2 W is planned for next releases.

Other Features

• Pre-built images for different OS and CPU architecture, along with installers. See INSTALLING.md for details.
• Visual representation of the GPIO pins in two layouts, a "Board Pin Layout" that mimics the physical layout of the Pi's GPIO connector/header, or a "BCM Pin Layout" with only the programmable GPIO pins, ordered by BCM pin number
• Each pin has its board pin number, name and function.
• Drop down selector to config each pin (Currently as an Input with or without pull-up/pull-down, or as an Output)
• Inputs have a visualization like an LED to show its current level (Black is unknown, Red is off, Green is on), plus a waveform view that shows you the recent history of the level detected on the input.
• Outputs have a toggle switch that can be used to change the stable value of the output, plus a "clicker" for quick inversions of the stable level, plus a waveform view showing the recent history of the level set on the Output.
• GPIO configurations can be loaded at startup with a command line filename option, or loaded via file-picker from the UI or saved to file via file picker.
• The GUI (piggui) can connect to a Pi (that is running piglet) over the network, to control and view the GPIO hardware from a distance. The GUI can run on Mac, Linux, Windows or Raspberry Pis. Events are timestamped at source (as close to the hardware as possible) so network delays should not affect the waveforms displayed. Provide us feedback and ideas related to networking in Discussions or GH issues.
• The data required to connect to a remote node via iroh-net is called the nodeid. piglet prints this out for you if it is started in the foreground. When piglet has been started as a system service, start another instance in the foreground and this will detect the background instance and display its nodeid for you then exit.
• Take the nodeid and either supply it as a command line option to piggui (--nodeid $nodeid, prefixed with -- if using cargo run) or enter it into the GUI. To connect to a remote instance from the GUI, click on the "hardware menu" in the left of the info bar at the bottom of the screen and select the "Connect to remote Pi..." menu item. Then enter the nodeid into the field provided and hit "Connect"
• Here are two videos showing the two ways to use it, with piglet running on a RPi shown via VNC.
  • Video with Dialog: https://youtu.be/aToJ1aT7NeM
  • Video using CLI argument: https://youtu.be/zcEa_Oke014

You can see more gifs and videos of features here

Piggui (pronounced "Piggy")

piggui is a GUI for configuring pins, observing input levels and controlling output levels. On Raspberry Pi it has a real GPIO hardware backend (via rppal). On macOS, Linux and Windows it uses a fake hardware backend (mainly for development) or can connect to a remote hardware backend that is running piglet.

Piglet

piglet is a "headless" command line utility that interacts with the GPIO hardware, and can either apply a config supplied from file and stop, or can listen for config changes from a remote piggui and report input level changes to the GUI.

If built on the Pi (with the "pi_hw" feature), then it has a real GPIO hardware backend.

It can be built on macOS/Linux/Windows/Pi with the "fake_hw" feature for a fake hardware backend, mainly used for development.

It takes an optional config file as a command line option. It will load the GPIO configuration from the file (like piggui can) and it will apply it to the hardware then stop.

It offers the ability to interact with the hardware from a remote pigguiinstance. It will print out connection info at startup and start listing for Iroh network connections from piggui instances, then the user can interact with it and visualize inputs level changes from the piggui GUI.

Porky

porky is an embedded application developer for the Raspberry Pi Pico (Pi Pico W only currently, but I plan to add support for Pico, Pico 2 and Pico 2 W soon) for remote interaction with the Pi Pico's GPIO hardware. It can be connected to remotely over TCP, just like to a piglet running on a Pi.

For more details see porky's README.md

Input from Raspberry Pi users wanted

We would like input from Raspberry Pi users to help us decide the order of things to work on in the future, and input on how integrate new functionalities (e.g. I2C buses, SPI, UART, etc.).

Please let us know what you think, and suggestions, via Discussions or GH issues.

Roadmap

We have identified a number of areas to work on in future releases, but we would really appreciate your input on what could be most useful or just the coolest, many have GH issues.

See issues in milestones 0.6.0 and 0.7.0 for the entire up-to-date list and progress.

• Extend Pi Pico support:
  • Persisting of GPIO config to flash and recovery at reboot/restart so that the GPIO continues to work as before
  • Full functionality over USB, not just getting hardware details and Wi-Fi config as in 0.5.0
  • Support for Pi Pico (not W) using USB above
  • Support for Pi Pico 2 and Pi Pico 2 W
• Discovery of compatible Pi and Pi Pico devices on the local network
• Expand support beyond Inputs and Outputs ( e.g. Clocks, PWM, I2C, UART, SPI etc.). Issue #53, #52, #5
• True logical layout, grouping pins by function Issue #94
• Allow connections between pins Issue #95
• Trigger a script or WebAssembly plugin on an input event (edge, level, etc.)

Installing

TODO

Building from Source

See BUILDING.md

Running Piggui and Piglet

For details on running piglet and piggui in the foreground or as a system service, on the same machine or with a remote GUI to Pi hardware, see RUNNING.md

Contributing

See CONTRIBUTING.md

License

See LICENSE

Code of Conduct

See CODE_OF_CONDUCT.md

Security

See SECURITY.md