plesty-server · plesty-bench

The bench PC's own console for the PLESTY platform. It installs hub device modules, starts and supervises their device servers, runs field tests against the real instruments and keeps the logs — so a lab bench is set up and kept running from one place instead of one venv, one terminal and one hand-written uv pin per instrument.

This repository publishes two packages:

On a Windows bench, the releases carry a setup.exe (per-user, no admin); macOS and Linux have install.sh. Both install uv, run the command above and add a Start-menu / Launchpad entry — they contain no application code of their own.

Bringing up a bench

plesty-server fleet init                      # a fleet.yaml to declare into
plesty-server declare pm100d plesty-pm100d --version 0.2.1 \
    --arg --address --arg "USB0::0x1313::…::INSTR"
plesty-server start pm100d                    # installs, launches, waits until it answers
plesty-server status

The instrument is now reachable from an experiment PC at this machine's address on the port status reports. plesty-server gui opens the same bench in a window; plesty-server fleet run keeps it up headless after a reboot.

Driving it from your own machine

The bench serves an agent; the client sends it plesty-server command lines and follows the output.

plesty-bench -b lab-bench-03 status
plesty-bench -b lab-bench-03 field-test pm100d --gates connect,drain
plesty-bench -b lab-bench-03 control pm100d          # a control panel per device

Documentation

Full documentation — start there if anything below is unfamiliar. It is in two parts.

Using a bench, in the order you meet it:

Design and internals is the other part: the architecture, the process model, the port rules, the installer, the agent protocol, the platform differences and the release machinery — for contributors, and for anyone debugging behaviour that only makes sense once the mechanism is visible.

New to the platform? The PLESTY quickstart runs a whole experiment against a bench and is the gentlest way in.