<div dir="ltr"><div dir="ltr">I like the idea of the v.s.* namespace.<br></div><div dir="ltr"><br></div><div>We could just have 'v.driver' = Left/Right/Auto - since really it's the Driver roll that is possibly the one that would be scripted on. I'm still not sure how you would then easily get at the 'driver-side-door' or 'driver-side-seatbelt' values.</div><div><br></div><div>How would you manage the arrays and make it easy to work with in extracting left/right/centre front/back etc? Associative array could work .. though that's not that different from the current *.fl *.fr etc.</div><div><br></div><div>//.ichael</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 5 Nov 2022 at 18:32, Michael Balzer <<a href="mailto:dexter@expeedo.de">dexter@expeedo.de</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>
Michael,<br>
<br>
I also had some thoughts on this, some first feedback from these on
yours:<br>
<ul>
<li>I'd place seatbelt sensors in a new name space "v.s." for
vehicle safety & security related metrics. That would also
become the place for airbag & emergency braking sensors,
traction control & emergency lights and the like.</li>
<li>I'd decouple the "driver" & "passenger" roles from the
physical allocation, because this may become a property that can
be changed on the fly even during driving, as soon as all
vehicle controls are digital.</li>
<li>The "driver" metric may then also be assigned to a special
value to represent autonomous driving modes.<br>
</li>
<li>I also think about arrays instead of fixed geometric layouts,
as vehicles come in a variety of door & seat arrangements.<br>
</li>
</ul>
Regards,<br>
Michael<br>
<br>
<br>
<div>Am 05.11.22 um 11:07 schrieb Michael
Geddes:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi all,
<div>I started this thought following up on my Ioniq 5 thread -
but figured it might be worth a new conversation.<br>
<div><br>
</div>
<div>Michael B talked about having some new standard metrics
(and also some consistent metric names in my i5 code: patch
coming now that I understand a bit better why those exist).</div>
<div><br>
</div>
<div>The Door Locked series is obviously a good start - the
candidate names being pretty straight forward imho.</div>
<div>v.d.l.fl<br>
<a href="http://v.d.l.fr" target="_blank">v.d.l.fr</a><br>
v.d.l.rl<br>
v.d.l.rr<br>
</div>
<div>Most cars these days would have seatbelt sensors - so
they might also be a candidate. v.sb.fl etc.</div>
<div><br>
</div>
<div>That being said, I have some issues related to
'right-hand-drive' vehicles which are quite popular in
Australia ;). For a start, there's no metric for it;
obviously some cars implementations will have a setting.
For the Hyundai this is important as it seems many
left/right settings are actually based on drive/passenger
side in the OBD bits.</div>
<div><br>
</div>
<div>Sooo.. I was considering some of the issues:</div>
<div><br>
</div>
<div>1) When it's on a diagram or in a user message, we want
left/right because that's how we want to deal with it.</div>
<div>2) In general scared scripts, we probably care more about
whether it is drive/passenger side rather than left/right!</div>
<div><br>
</div>
<div>Could we have some metric alias's for left/right metrics
that would be drive/passenger that would allow</div>
<div>* Setting via either metric</div>
<div>* Reading via either metric</div>
<div>* Adding events based on either metric.</div>
<div>For eg</div>
<div>v.d.l.fl links to<br>
</div>
<div>* v.d.l.fd (front driver) for Left-hand drive and</div>
<div>* v.d.l.fp (front passenter) for Right-hand drive cars.</div>
<div>I mean we could set both metrics.. but would that work?</div>
<div><br>
</div>
<div>Thoughts on this?</div>
<div>//.ichael</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</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>