<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Solterra,<div><br></div><div>Michael’s advice is good.</div><div><br></div><div>If it is just two names for essentially the same vehicle, I think you can refer to vehicle_voltampera (which implemented the Chevy Volt and Open Ampera vehicle support). These were essentially the same vehicle platform, but with minor bodywork differences and labelling.</div><div><br></div><div>If the two vehicles share the same platform (such as BMS, battery, etc) but are otherwise very different, then I suggest you implement a vehicle_<platform> for that platform, and derive two classes from that in the same /src/ directory (one for each vehicle type). That will allow you to put all common support code in the base platform, but have each vehicle type customisable (and individually selectable).</div><div><br></div><div>Looking at images of the cars, it seems they are closest to the Volt Ampera situation. Perhaps BZSS?</div><div><br></div><div>Regards, Mark.<br><div><br><blockquote type="cite"><div>On 28 May 2023, at 8:23 AM, Michael Geddes <frog@bunyip.wheelycreek.net> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div dir="ltr">Hey Solterra, <br></div><div>I couldn't say definitively but imho there are various options depending on HOW different.</div><div><br></div><div>1) They are exactly the same - or differences can be distinguished from responses: Register the name with both in it. Done. (This has happened with some older Kia + Hyundai even)</div><div>2) They are mostly the same. You could probably keep the one directory but have 2 wrapper classes constructing the base class with a parameter and register both in the factory Init. (Not sure if there are examples - ask the other Michael if this is ok).</div><div>3) They have a lot of commonality. You can inherit off a base class - or inherit one vehicle impl off the other... But put them in separate directories. (This happens for Ioniq 5 and a bunch of other Kia + Hyundai cars).</div><div><br></div><div>//.ichael Geddes</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 27 May 2023 at 21:19, Solterra <<a href="mailto:solterra@kezarnet.com">solterra@kezarnet.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-size:10pt;font-family:Verdana,Geneva,sans-serif"><p>Hello again,</p><p>I've finished my initial vehicle investigation and am not ready to add support to OVMS.</p><p>When creating the vehicle stub, is there guidance for situations like on this vehicle? There are two makes and models that are essentially the same. Can I create a common 'components/vehicle_toyota_bz4x' and point two vehicle selections to it somewhere else?</p><p>Thank you</p><p><br></p>
</div>
_______________________________________________<br>
OvmsDev mailing list<br>
<a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank">OvmsDev@lists.openvehicles.com</a><br>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" rel="noreferrer" target="_blank">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br>
</blockquote></div></div>
_______________________________________________<br>OvmsDev mailing list<br>OvmsDev@lists.openvehicles.com<br>http://lists.openvehicles.com/mailman/listinfo/ovmsdev<br></div></blockquote></div><br></div></body></html>