repo: archive legacy pico dashboard
This commit is contained in:
@@ -0,0 +1,47 @@
|
||||
# ESP32-S3 Dashboard Firmware
|
||||
|
||||
This is the placeholder for the current dashboard firmware direction.
|
||||
|
||||
## Target hardware
|
||||
|
||||
Current dashboard target:
|
||||
|
||||
- Waveshare ESP32-S3 touchscreen display
|
||||
- WiFi connection to the Cargo ESP32 access point
|
||||
- HTTP/REST communication with the Cargo ESP32 API
|
||||
- Future LVGL-based dashboard UI
|
||||
|
||||
## Responsibilities
|
||||
|
||||
The ESP32-S3 dashboard is responsible for:
|
||||
|
||||
- Touchscreen UI
|
||||
- Vehicle gauges
|
||||
- Dashboard rendering
|
||||
- Future CAN/OBD-II vehicle visualization
|
||||
- Future tilt/roll/off-road screen visualization
|
||||
|
||||
## Not responsible for
|
||||
|
||||
The ESP32-S3 dashboard does not own:
|
||||
|
||||
- Relay authority
|
||||
- BMS authority
|
||||
- Alarm authority
|
||||
- Cargo ESP configuration storage
|
||||
- Load-switching hardware control as the source of truth
|
||||
|
||||
The Cargo ESP32 remains the power-system controller and source of truth.
|
||||
|
||||
## v1 communication path
|
||||
|
||||
Dashboard ESP32-S3
|
||||
<-> WiFi / HTTP REST
|
||||
Cargo ESP32 AP
|
||||
|
||||
Not v1 dashboard communication:
|
||||
|
||||
- Pico UART
|
||||
- ESP-NOW
|
||||
- MQTT
|
||||
- CAN between controllers
|
||||
Reference in New Issue
Block a user