A PLESTY module is a Python package; it does not run itself. PLESTY Bench is the application that turns one into a running instrument — it installs modules from the hub, launches their device servers, supervises them, runs their field tests, and keeps the logs and the job history. It is what goes on a lab bench PC, and this is where you get it.
Install the bench
The current release is v0.3.3.
Windows
Download plesty-server-v0.3.3-windows-setup.exe and run it. It installs per user and asks for no administrator rights.
macOS and Linux
curl -LsSf https://gitlab.com/api/v4/projects/85550357/packages/generic/plesty-server/v0.3.3/install.sh | sh
With uv already installed
uv tool install "plesty-server[gui]==0.3.3"
All three do the same thing. The two installers add uv if the machine lacks it, install the
bench from PyPI, and leave an entry in the Start menu or Launchpad — which is why uv is not a
prerequisite. Open the console from that entry, or with:
plesty-server gui
Upgrade a bench later with uv tool upgrade plesty-server.
The remote client
plesty-bench drives a bench from another machine — install a module, run a field test, follow
the job — over the same wire the device servers speak. The CLI is the API.
uv tool install plesty-bench
plesty-bench -b lab-bench-03 field-test pm100d
All releases
Each release publishes its own installer, pinned to that version. The latest release is always the newest one, whatever this page says.
Older releases
Full notes are on each release page; the running account is in the CHANGELOG.
Before you install
- Windows, macOS or Linux. No Python needed —
uvfetches an interpreter if the machine has none. gitis what the bench uses to fetch a module from a repository rather than a release. The Windows installer downloads a portable copy for itself; on macOS and Linux, install one ifgit --versionsays you have none.
New to the platform? The Quickstart builds a working bench on your own PC with no hardware at all, and The Bench explains what the console is doing underneath.