nick/overland-controller
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

repo: archive legacy pico dashboard

Browse Source
This commit is contained in:
nick
2026-06-09 00:52:00 -06:00
parent 9cb06b86ff
commit f5e2c5fd24
38 changed files with 107 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CHATGPT_HANDOFF.md
+11
View File
@@ -156,3 +156,14 @@ Current Cargo ESP32 GPIO plan:
- v1 dashboard communication is WiFi/HTTP REST only.
- ESP-NOW, MQTT, UART dashboard link, and CAN-between-controllers are not v1 architecture.
- Load-switching hardware is not finalized. Bosch relays, WUPP-style fused distribution, smart high-side switching, and custom PCB options remain implementation choices until explicitly selected.
## Legacy Pico Dashboard Archive
The old Pico dashboard implementation has been archived at `archive/legacy-pico-dashboard/`.
Do not treat it as active firmware. It may be referenced for old HTTP/state/alarm/UI ideas, but new dashboard work should target the ESP32-S3 dashboard path.
Default validation should use the repo-local virtual environment:
source .venv/bin/activate
python run_tests.py
docs/README.md
+3
View File
@@ -35,3 +35,6 @@ Archived documents are kept for history, but the primary documents above should
- `PARITY_MATRIX.md` - Command parity across USB serial, UART JSON, and HTTP API
- `controller-roles.md` - Cargo ESP vs Dashboard ESP32-S3 responsibility boundaries
- `../archive/legacy-pico-dashboard/` - Archived Pico dashboard implementation kept for reference only.
- `../firmware/esp32-s3-dashboard/` - Current ESP32-S3 dashboard firmware placeholder.
docs/project-state.md
+8
View File
@@ -214,3 +214,11 @@ Summary:
- v1 communications: Dashboard connects to Cargo ESP AP over WiFi/HTTP REST.
- Not v1 communications: ESP-NOW, MQTT, UART dashboard link, or CAN between controllers.
- Load-switching hardware is still an implementation choice, not frozen architecture.
## Pico Dashboard Archive Cleanup
The old `pico-dashboard/` implementation has been moved to `archive/legacy-pico-dashboard/`.
It is retained as reference material only. It is not active firmware and is no longer part of the default validation path.
Current dashboard work should target the ESP32-S3 dashboard direction documented in `docs/dashboard-esp32s3.md` and the placeholder at `firmware/esp32-s3-dashboard/`.