26 Oct
2026
26 Oct
'26
3:24 a.m.
Hi Nick,
I had UDS polling running on my own e-Golf (2020) in my fork for a couple of months, so some of the groundwork is done. It never went upstream, mostly because the broadcast frames covered what we needed at the time.
What I found, all on my car:
- BMS is reachable at 0x7E5 / 0x7ED on can1 (diag CAN, from the J533 harness, so all three buses need to be wired)
- DID 0x1E3B = pack voltage, u16 / 4
- DID 0x1E3D = pack current, (u16 - 2044) / 4, negate for discharge-positive
- That's the e-Up scaling, and it holds on the e-Golf. Against the FCAN broadcast (0x191) it agrees within ~0.5 A typically, 2 A worst, voltage exact. Small sample though, and only -80..+4 A, so not tested at high DC charge current.
- DID 0x74CB SoH reads about 10x the e-Up scale here. raw / 500 gave me 86.35%, which looks plausible but I never checked it against VCDS/ODIS. Treat it as a guess.
- CAC: I couldn't work out the scaling, the e-Up formula gives nonsense (430 Ah).
Two practical things:
- The e-Golf entry in main/Kconfig doesn't have "depends on OVMS_COMP_POLLER" like the e-Up does. You'll want that before using the poller.
- Since FCAN was dropped (#1524), current master doesn't set v.b.current / v.b.power during charging at all, so pack current over UDS while charging would fill a real gap, not just add cell detail.
On Jona's alarm point: I only polled while charging and with ignition on, never with the car off or just awake. So I can't confirm or rule it out. I'd gate the poll on those states anyway.
Code is in my fork, tag archive/vwegolf-20260815 on github.com/slothish/ovms3-VWeGolf (commits 32e29846a and 2c99b2724). It's on an old dev line so don't cherry-pick it, but the DID handling and the native tests (test_uds_poll.cpp) should be easy to lift.
Andreas