rjmcmahon
/
FiWiControl
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(readme): Pi5 fleet as controllers and actuators (not lab rig controllers) 

Made-with: Cursor
This commit is contained in:
Robert McMahon 2026-04-10 19:09:24 -07:00
parent 2db7d822cc
commit b99157a2a8
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -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) ## 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) ## ESP32, IEEE 802.11, and advanced telemetry (planned)