VW e-Golf: working on comfort CAN / climate scheduler support
Hi all, I'm Andreas, based in Sweden, owner of a 2019 VW e-Golf. I've just joined the list to let you know I'm working on adding comfort CAN support to the e-Golf vehicle module, with climate scheduler control as the primary goal. With VW discontinuing the Car-Net app due to the decommissioning of 2G, e-Golf owners lost the ability to trigger climate controls remotely. The car's built-in e-manager timer still works, but can't be changed remotely. That's the gap I'm trying to close. The existing e-Golf module (PR #1327) reads SoC, odometer, range and charge status via the diagnostic and powertrain CAN buses at J533, but the comfort CAN has remained unimplemented. A few things I'm leaning on: - thomasakarlsen/e-golf-comfort-can has comfort CAN traces from an actual e-Golf showing BAP traffic on the climate and scheduler LSGs - MIGINC/BAP_RE documents the MQB BAP protocol structure and Climatronic ID mappings - drgrandios/ovmslogs has annotated e-Up BAP frame decoding that maps closely to what appears in the e-Golf traces Cross-referencing these makes the scheduler write path look doable, and the e-Up implementation in OVMS looks like a useful reference. I'm working in a fork (investigation branch) where I'm collecting all relevant context and building a test suite before touching any car-side code. I have an OVMS module and will be doing all testing on my own car before anything comes near a PR. If there are other e-Golf owners on the list, or anyone who has looked at this before, I'd be glad to hear from you. Fork: https://github.com/slothish/Open-Vehicle-Monitoring-System-3-VWeGolf/tree/in... Andreas
Andreas, welcome :-) find attached my unfinished analysis of the protocol. The e-Up implementation was based on this. My analysis is in german, but modern translation tools should be able to process it for you -- ask me if you encounter difficulties. Should be a better base than the e-Up code, which has quite some flaws and doesn't actually implement the protocol in a generic way. Regards, Michael Am 03.04.26 um 17:25 schrieb Andreas Jansson via OvmsDev:
Hi all, I'm Andreas, based in Sweden, owner of a 2019 VW e-Golf.
I've just joined the list to let you know I'm working on adding comfort CAN support to the e-Golf vehicle module, with climate scheduler control as the primary goal.
With VW discontinuing the Car-Net app due to the decommissioning of 2G, e-Golf owners lost the ability to trigger climate controls remotely. The car's built-in e-manager timer still works, but can't be changed remotely. That's the gap I'm trying to close.
The existing e-Golf module (PR #1327) reads SoC, odometer, range and charge status via the diagnostic and powertrain CAN buses at J533, but the comfort CAN has remained unimplemented.
A few things I'm leaning on:
- thomasakarlsen/e-golf-comfort-can has comfort CAN traces from an actual e-Golf showing BAP traffic on the climate and scheduler LSGs
- MIGINC/BAP_RE documents the MQB BAP protocol structure and Climatronic ID mappings
- drgrandios/ovmslogs has annotated e-Up BAP frame decoding that maps closely to what appears in the e-Golf traces Cross-referencing these makes the scheduler write path look doable, and the e-Up implementation in OVMS looks like a useful reference.
I'm working in a fork (investigation branch) where I'm collecting all relevant context and building a test suite before touching any car-side code. I have an OVMS module and will be doing all testing on my own car before anything comes near a PR.
If there are other e-Golf owners on the list, or anyone who has looked at this before, I'd be glad to hear from you. Fork: https://github.com/slothish/Open-Vehicle-Monitoring-System-3-VWeGolf/tree/in...
Andreas _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
participants (2)
-
Andreas Jansson -
Michael Balzer