<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Craig,<br>
<br>
I strictly vote against re-interpretation of the SOC metric. Where
metrics have clear semantics we should not make them dependent on
some context.<br>
<br>
A battery is not a fuel tank, and vehicles may have both. "v.b." is
the namespace "vehicle battery" and shall not be populated with
non-battery metrics.<br>
<br>
That's what I meant by adding technology specific metrics: if the
vehicle has a fuel tank, additional standard metrics describing that
fuel tank shall be present.<br>
<br>
Fuel tank specific metrics might e.g. get the namespace "v.ft.", ICE
engine specific metrics might get "v.ice.", fuel cell metrics
"v.fc.", rocket thruster metrics "v.rt." … you get the idea.<br>
<br>
Make a proposition for the metrics sets you need. Try to define them
as generalized as possible.<br>
<br>
That will probably include duplicates of some metrics, like the
ranges & consumption. That's necessary to be able to describe a
hybrid, and some units among those will also need to be different
(e.g. consumption in litres / m³ per km).<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 14.06.20 um 18:59 schrieb Chris van
der Meijden:<br>
</div>
<blockquote type="cite"
cite="mid:1592153973.13853.18.camel@arachnon.de">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>Thank you for considering my thoughts.</div>
<div><br>
</div>
<div>I believe it is a good idea to use a v.tech variable and not
using gas or gazoline. That gives OVMS enough flexibility and is
also a (little) statement.</div>
<div><br>
</div>
<div>I'm also looking forward to rocket propulsion add ons :-))</div>
<div><br>
</div>
<div>Greetinx</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div><br>
</div>
<div>Am Sonntag, den 14.06.2020, 08:21 -0700 schrieb Craig Leres:</div>
<blockquote type="cite">
<pre>On 2020-06-13 08:31, Michael Balzer wrote:
<blockquote type="cite">
How about adding an array or set metric like "v.ext" or "v.tech", for
defined technology codes. A tag present in the metric means the
additional metrics, commands & configs for that technology are available.
</blockquote>
My goal is to make it possible for the app to depict soc with something
other than a battery graphic when the energy source is not a battery.
How about v.tech with "battery" and "other" as the initial two possible
values?
Craig
_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>