[Ovmsdev] Adding support for eGolf

[Chris van der Meijden]

Hi Erick,

that index.rst is an old one for the VW e-UP. For the e-Golf only a few
things worked "out of the box". Nothing really exiting though, it was
quite rudimentary (SOC, km, ... can't remember well what else).

Regards

Chris

Am Donnerstag, dem 05.02.2026 um 06:53 -0500 schrieb Erick Fuentes:
> Michael - Thank you for the feedback. I'll work on getting things
> into better shape. I asked Mikus for a harness and it should arrive
> in about a week, so in the meantime, I'll be working at my desk. I
> don't think I saw any, but is there any infrastructure for unit
> testing?
> 
> Chris - Michael mentioned your previous attempt. I took a quick look
> and it seems like you got pretty far. Do you remember what was left
> to do? I found the following in the docs folder, but I wasn't sure if
> it was up to date. I understand if you can't remember, I don't even
> remember what I had for breakfast yesterday, let alone what I was
> doing a few years ago. Regardless, Mikus and I will add some
> documentation.
> 
> Thank you,
> Erick
> 
> =========================== ==============
> Function                    Support Status
> =========================== ==============
> Hardware                    Any OVMS v3 (or later) module.
> Vehicle Cable               Comfort CAN / OBD Gateway
> GSM Antenna                 T4AC - R205 with fakra_sma adapter cable
> or 1000500 Open Vehicles OVMS GSM Antenna (or any compatible antenna)
> GPS Antenna                 T4AC - R50 with fakra_sma adapter cable
> or 1020200 Universal GPS Antenna (or any compatible antenna)
> SOC Display                 Yes
> Range Display               Yes
> Cabin Pre-heat/cool Control Yes
> GPS Location                Yes (from modem module GPS)
> Speed Display               Yes
> Temperature Display         Yes (see list of metrics below)
> BMS v+t Display             Yes
> TPMS Display                tba
> Charge Status Display       Yes
> Charge Interruption Alerts  Yes (per notification on the charging
> state)
> Charge Control              tba
> Lock/Unlock Vehicle         No 
> Valet Mode Control          No 
> =========================== ==============
> 
> 
> On Thu, Feb 5, 2026 at 2:47 AM Chris van der Meijden via OvmsDev
> <ovmsdev at lists.openvehicles.com> wrote:
> > Hi Erick,
> > 
> > good to see that you have started to get the e-Golf up and running
> > with OVMS. 
> > 
> > I have tried it a few years ago too based on my expierences with
> > the e-UP. Though I have to say without very much success. The e-
> > Golf and e-UP behave in great parts different on the CAN-bus. But
> > there seems to be more insight on the e-Golf nowadays, so a new
> > approach seems to be more promissing now.
> > 
> > Could you create a "docs" folder with an "index.rst" like in the
> > "vehicle_demo"?
> > 
> > https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/components/vehicle_demo/docs/index.rst
> > 
> > This will make the progress steps clearer to those following your
> > progress with the project.
> > 
> > Regards
> > 
> > Chris
> > 
> > 
> > Am Montag, dem 02.02.2026 um 16:27 +0100 schrieb Michael Balzer via
> > OvmsDev:
> > > Erick, welcome :)
> > > 
> > > An initial PR for the initial vehicle support is OK.
> > > 
> > > For later extensions, try to keep each PR concentrating on a
> > > specific 
> > > feature/extension.
> > > 
> > > Split up further on any critical change that may need to be
> > > quickly 
> > > revertable.
> > > 
> > > Keep framework and vehicle specific changes strictly separate,
> > > only 
> > > include vehicle changes in framework commits if they need to be
> > > changed 
> > > for the framework change.
> > > 
> > > Use concise but clear commit messages.
> > > 
> > > Do not submit unvalidated AI results.
> > > 
> > > More: 
> > > https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3?tab=readme-ov-file#development-and-contributions
> > > 
> > > Regards,
> > > Michael
> > > 
> > > 
> > > Am 02.02.26 um 04:23 schrieb Erick Fuentes via OvmsDev:
> > > > Hello!
> > > > 
> > > > I recently bought a 2019 eGolf and I'm interested in getting
> > > > support 
> > > > for it in the project. Some folks on the OVMS Discord server
> > > > have code 
> > > > that appears to work and I've volunteered to try to merge it.
> > > > I've yet 
> > > > to run the code myself (I'm still waiting on a harness), but I
> > > > thought 
> > > > I'd ask what the process might look like. Do you want small
> > > > pull 
> > > > requests where each one covers a single, small feature? Are you
> > > > okay 
> > > > with merging everything at once, provided it doesn't break
> > > > other vehicles?
> > > > 
> > > > Erick
> > > > 
> > > > _______________________________________________
> > > > OvmsDev mailing list
> > > > OvmsDev at lists.openvehicles.com
> > > > http://lists.openvehicles.com/mailman/listinfo/ovmsdev
> > > 
> > > 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20260206/7de3a750/attachment.htm>