<html><head><style>pre,code,address {
margin: 0px;
}
h1,h2,h3,h4,h5,h6 {
margin-top: 0.2em;
margin-bottom: 0.2em;
}
ol,ul {
margin-top: 0em;
margin-bottom: 0em;
}
blockquote {
margin-top: 0em;
margin-bottom: 0em;
}
</style></head><body><div>Hi Erick,</div><div><br></div><div>good to see that you have started to get the e-Golf up and running with OVMS. </div><div><br></div><div>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.</div><div><br></div><div>Could you create a "docs" folder with an "index.rst" like in the "vehicle_demo"?</div><div><br></div><div><a href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/components/vehicle_demo/docs/index.rst">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/components/vehicle_demo/docs/index.rst</a></div><div><br></div><div>This will make the progress steps clearer to those following your progress with the project.</div><div><br></div><div>Regards</div><div><br></div><div>Chris</div><div><br></div><div><br></div><div>Am Montag, dem 02.02.2026 um 16:27 +0100 schrieb Michael Balzer via OvmsDev:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Erick, welcome :)<br></div><div><br></div><div>An initial PR for the initial vehicle support is OK.<br></div><div><br></div><div>For later extensions, try to keep each PR concentrating on a specific <br></div><div>feature/extension.<br></div><div><br></div><div>Split up further on any critical change that may need to be quickly <br></div><div>revertable.<br></div><div><br></div><div>Keep framework and vehicle specific changes strictly separate, only <br></div><div>include vehicle changes in framework commits if they need to be changed <br></div><div>for the framework change.<br></div><div><br></div><div>Use concise but clear commit messages.<br></div><div><br></div><div>Do not submit unvalidated AI results.<br></div><div><br></div><div>More: <br></div><div><a href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3?tab=readme-ov-file#development-and-contributions">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3?tab=readme-ov-file#development-and-contributions</a><br></div><div><br></div><div>Regards,<br></div><div>Michael<br></div><div><br></div><div><br></div><div>Am 02.02.26 um 04:23 schrieb Erick Fuentes via OvmsDev:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Hello!<br></div><div><br></div><div>I recently bought a 2019 eGolf and I'm interested in getting support <br></div><div>for it in the project. Some folks on the OVMS Discord server have code <br></div><div>that appears to work and I've volunteered to try to merge it. I've yet <br></div><div>to run the code myself (I'm still waiting on a harness), but I thought <br></div><div>I'd ask what the process might look like. Do you want small pull <br></div><div>requests where each one covers a single, small feature? Are you okay <br></div><div>with merging everything at once, provided it doesn't break other vehicles?<br></div><div><br></div><div>Erick<br></div><div><br></div><div>_______________________________________________<br></div><div>OvmsDev mailing list<br></div><div><a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a><br></div><div><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br></div></blockquote><div><br></div><div>-- <br></div><div>Michael Balzer * Am Rahmen 5 * D-58313 Herdecke<br></div><div>Fon 02330 9104094 * Handy 0176 20698926<br></div><div><br></div><div><br></div></blockquote><div><br></div><div><span></span></div></body></html>