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