I like the idea of the v.s.* namespace. 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. 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. //.ichael On Sat, 5 Nov 2022 at 18:32, Michael Balzer <dexter@expeedo.de> wrote:
Michael,
I also had some thoughts on this, some first feedback from these on yours:
- 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. - 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. - The "driver" metric may then also be assigned to a special value to represent autonomous driving modes. - I also think about arrays instead of fixed geometric layouts, as vehicles come in a variety of door & seat arrangements.
Regards, Michael
Am 05.11.22 um 11:07 schrieb Michael Geddes:
Hi all, I started this thought following up on my Ioniq 5 thread - but figured it might be worth a new conversation.
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).
The Door Locked series is obviously a good start - the candidate names being pretty straight forward imho. v.d.l.fl v.d.l.fr v.d.l.rl v.d.l.rr Most cars these days would have seatbelt sensors - so they might also be a candidate. v.sb.fl etc.
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.
Sooo.. I was considering some of the issues:
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. 2) In general scared scripts, we probably care more about whether it is drive/passenger side rather than left/right!
Could we have some metric alias's for left/right metrics that would be drive/passenger that would allow * Setting via either metric * Reading via either metric * Adding events based on either metric. For eg v.d.l.fl links to * v.d.l.fd (front driver) for Left-hand drive and * v.d.l.fp (front passenter) for Right-hand drive cars. I mean we could set both metrics.. but would that work?
Thoughts on this? //.ichael
_______________________________________________ OvmsDev mailing listOvmsDev@lists.openvehicles.comhttp://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev