<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Chiming in from the side here...<br>
<br>
I think the proverb "A man with a watch knows what time it is. A
man with two watches is never quite sure." can apply here.<br>
<br>
There is value in having a consistent display of information between
what the driver sees on the car's display and what the OVMS is
reporting. So, having OVMS report the same value as the instrument
panel for a metric of the same name can be a good idea, even if it's
not terribly representative of what's happening inside the battery
pack or otherwise useful. The "real" value can then be presented in
a different "engineering" metric as such information is available.<br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Robin O'Leary wrote:<br>
</div>
<blockquote type="cite" cite="mid:20180501224134.GC22459@mail.ro.nu">
<pre wrap="">On Wed, May 02, 2018 at 07:39:57AM +1200, Tom Parker wrote:
</pre>
<blockquote type="cite">
<pre wrap="">We can make the SOC calculation configurable so that you can choose to use
the instrument panel SOC or an SOC based on the new car battery size. When I
took over the leaf support I wanted to use the instrument panel soc too, see
Tom Saxton's reply which convincingly dissuaded me wanting to switch:
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/pipermail/ovmsdev/2016-May/002993.html">http://lists.openvehicles.com/pipermail/ovmsdev/2016-May/002993.html</a> (this
discussion that was before I knew SOC was available so I had some no longer
relevant ideas about how to actually implement it).
Now we have the easier to configure v3 platform and more users wanting to
use the instrument panel SOC I'll make it configurable. I should be able to
get that done tonight.
</pre>
</blockquote>
<pre wrap="">
This picks up on the same discussion we started earlier when I tried to
make the same change. But we seem to be arguing as if there has to be
one ideal metric, when we really need several of different metrics for
different purposes.
There is utility in having a vehicle metric for the dash SOC% because that
is how the car reports on progress during charging---it's going to stop at
100% (or 80%) and slow down in a predictable way at the number increases.
There is also utility in having another vehicle metric which represents
the amount of available energy in the battery---though I see no good
reason why that should be expressed as a percentage of some arbitrary
number I've had to set in the first place; it seems fundamentally better
to use a standard unit like kWh. Is there a metric for that already?
Once we know available energy, we can derive other useful things like
estimated range, and those calculations can be vehicle-independent,
because they just use values in standard units like kWh, W/km etc.
It seems much more reasonable for this to be where the user can choose
to apply their own scaling preferences, rather than having that in the
code for any specific vehicle.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">And now to a different thing:
The app supports unlocking and locking of doors. The feature doesn't seem
to be implemented for the Nissan Leaf.
I have all the CAN-codes needed to make this work. Please let me know if I
can contribute.
</pre>
</blockquote>
<pre wrap="">
I'm uncomfortable doing this on my own car, but I'm very happy to have the
feature implemented. I think it should be hidden behind a configuration
option, so you can choose whether the standard functionality allows the car
to be unlocked, but that is a different and not Leaf specific conversation.
</pre>
</blockquote>
<pre wrap="">
Yes, I'm also not sure I would always want this enabled, so it would be
good to have a config option to enable it, but it's something I would
like to help work on.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
</body>
</html>