Skip to content

Commit fb39f7b

Browse files
malysclaude
andcommitted
docs(firmware): point to the EVProfile SOC sources tool (CR-044)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 parent d6103c7 commit fb39f7b

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

‎FIRMWARE.md‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,8 +43,11 @@ per-signal split.
4343
Owners on SWI69 R45 report every upload refused with HTTP 400. ABRP requires `soc`, so
4444
since CR-044 a sample without SOC is not posted. The in-app log says
4545
"SOC not readable on SWI69 — not sent" instead. A read path for those generations needs an
46-
`EV_HW` log from the car before it is added (the Diagnostic tab's property probe already
47-
lists the standard `EV_BATTERY_LEVEL` and `INFO_EV_BATTERY_CAPACITY`).
46+
`EV_HW` log from the car before it is added. EVProfile's unstable Diagnostic has a **SOC
47+
sources** tool for that (EVHardware `VendorSurfaceProbe`). It reads each candidate side by side:
48+
the charging service, the vendor ID, the standard `EV_BATTERY_LEVEL` / `INFO_EV_BATTERY_CAPACITY`
49+
pair and the vendor setting getters. Its before/after capture taken across a SOC change finds a
50+
property that is not named anywhere.
4851

4952
## Emulator fidelity
5053

0 commit comments

Comments
 (0)