dashboard: expand CAN diagnostics
This commit is contained in:
@@ -75,3 +75,14 @@ The dashboard uses field-filtered `/api/v1/status` calls:
|
||||
- Slow poll: `/api/v1/status?fields=network,system,config`
|
||||
|
||||
This keeps the endpoint model simple while reducing payload size, JSON parsing, and UI churn.
|
||||
|
||||
## OBD-II / CAN Diagnostics
|
||||
|
||||
The hidden diagnostics overlay distinguishes raw CAN traffic from parsed
|
||||
OBD-II coolant responses. It reports request successes and failures, total
|
||||
raw frames received, the last frame identifier and DLC, TWAI queue depth,
|
||||
controller error counters, missed or overrun frames, arbitration losses,
|
||||
and bus errors.
|
||||
|
||||
Raw RX activity confirms that the display is receiving CAN frames even when
|
||||
the vehicle does not return a matching Mode 01 PID 05 coolant response.
|
||||
|
||||
Reference in New Issue
Block a user