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
Hi Andreas,
Good catch on the Kconfig. I’ll add depends on OVMS_COMP_POLLER to the e-Golf entry before doing anything with the poller.
One update on the FCAN side: on my fork branch egolf-seat-heating-test (https://github.com/nickb24/Open-Vehicle-Monitoring-System-3/commits/egolf-se...) I’ve re-enabled FCAN, and it’s been working so far. I know #1524 dropped it because of CPU load, so I’m watching for that specifically before suggesting it goes upstream. With FCAN back, 0x191 gives me v.b.current / v.b.power again while charging. UDS polling could still be the better long-term fix for the charging gap if FCAN turns out to be too heavy for some setups.
On Jona’s alarm point, I agree with gating the poll on charging / ignition-on only.
The reason for my UDS polling questions is because I want to implement some of the data from this project: http://obd-amigos.linuxtech.net/
I'm interested in reading the real battery SOH (like ODIS does) and possibly the battery cells. But I was wondering how best to do it in OVMS. This shouldn't be something that is done often (and isn't needed to either). I'm thinking only once per charge session maybe? Or should it be on a per-request basis, meaning the user needs to ask for it and then it will read it on the next charge for example?
What I'm also working on is reverse engineering the code from my infotainment system's JXE file (done) and the OCU firmware I found online 'FL_5QE035284A_ocu_PROD_all_0545_HW07_MQB_EU_E.frf'. I have found some missing BAP channel definitions from the JXE file already. The OCU decompile has been the most interesting but the longest. I haven't spent too much time (and I keep running out my Claude session limits anyways) but so far I have found some good information I plan to test out.
Nick
Hi Nick, Jona,
First, the split thread is my fault. My last mail went out as a new message instead of a reply, so that's why there are two. Sorry about that.
On history: there's no lessons-learned reason UDS was left out. In my fork it worked fine, it just never went upstream because the broadcast frames covered what we needed. Nothing broke.
On when to poll: in my fork the poll only ran while charging (gated on 0x594) and with ignition on. Off and awake-only didn't poll at all. For SoH I agree with Jona. Read it once near the end of a charge session, when the pack has settled. It barely moves, so more often doesn't buy you anything. I'd also add an xvg command to read it on demand. Then nobody has to wait for the next charge to get a value. Cell voltages could use the same schedule.
One thing worth knowing: metrics are persistent, so if you only set SoH on a real read (no default in the constructor, which dexterbg will also ask for) it just holds the last value between reads. That works well for something this slow.
On FCAN: on my car 0x191 is FCAN only. I found it zero times in about 2.5M KCAN frames over 40 captures, so if you want it you do need FCAN. Unfiltered FCAN is heavy, though. In one short unfiltered capture I saw around 1700 frames/s, the poller queue overflowing and the logger dropping frames. It didn't crash, but I wouldn't run that every day. I used the mcp2515 hardware acceptance filter to cut it down to the IDs we used, which is the other way to keep under Jona's 75% CPU target. That PR (#1404) is closed now since #1524 removed FCAN, but the filter code is in tag archive/pr-1404 on my fork if you want to look.
On the BAP channels you're pulling out of the JXE: check https://github.com/thomasakarlsen/e-golf-comfort-can before you test them. It's the best KCAN/BAP reference I've found for the e-Golf and was my main source for the clima work, so some of what you're finding may already be confirmed there. If you find channels it doesn't have, I'd be interested.
Andreas
On 2026-10-26T08:24:16+01:00, Andreas Jansson wrote:
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
participants (2)
-
Andreas Jansson -
Nicholas Berlingieri