From b99157a2a88665909deb56319a78def0e8122fdb Mon Sep 17 00:00:00 2001 From: Robert McMahon Date: Fri, 10 Apr 2026 19:09:24 -0700 Subject: [PATCH] docs(readme): Pi5 fleet as controllers and actuators (not lab rig controllers) Made-with: Cursor --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a33a46e..beaccbc 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ That work fails if the bench is informal—wrong port, wrong power path, or no s ## Lab fleet: Raspberry Pi 5 and iperf 2 (planned) -We expect a **fleet of Raspberry Pi 5** boards as the primary **lab rig controllers**: remote **`fiwicontrol`** install, discovery over SSH, PCIe / Fi‑Wi harness hosts (docs already assume Pi-class rigs). Those Pi 5s will run **iperf 2** as **synthetic traffic** endpoints—controlled load and measurement during Fi‑Wi and bring-up experiments, not one-off manual runs. **None of this is automated in-repo yet** beyond what you can already drive by hand over **`ssh_node`**; first-class orchestration and reporting are roadmap. +We expect a **fleet of Raspberry Pi 5** boards to act as **controllers and actuators** in the lab: remote **`fiwicontrol`** install, discovery over SSH, PCIe / Fi‑Wi harness hosts (docs already assume Pi-class rigs). Those Pi 5s will run **iperf 2** as **synthetic traffic** endpoints—controlled load and measurement during Fi‑Wi and bring-up experiments, not one-off manual runs. **None of this is automated in-repo yet** beyond what you can already drive by hand over **`ssh_node`**; first-class orchestration and reporting are roadmap. ## ESP32, IEEE 802.11, and advanced telemetry (planned)