<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
My 2 cents:<br>
<br>
We shouldn't generally exclude alternative propulsion technologies.
Battery based electric propulsion will cover the majority of future
transportation and mobility, but it won't fit every use case and
every kind of vehicle.<br>
<br>
We should keep the core support to be for (battery) electric
propulsion, and add support for alternative technologies on a strict
add-on base.<br>
<br>
If for example a vehicle has a hydrogen based range extender, that
should be signaled by the vehicle adapter, and the system should
only then add the set of standard metrics for this particular
technology.<br>
<br>
A metric "v.m.gas" would be confusing (what kind of gas? what kind
of energy conversion?), would favorize a specific technology by it's
name, and would not be sufficient to describe arbitrary combinations
of technologies (e.g. a BEV with rocket thrusters…).<br>
<br>
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.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix"> 13.06.20 um 07:57 schrieb Chris van
der Meijden:<br>
</div>
<blockquote type="cite"
cite="mid:1592027829.2567.4.camel@arachnon.de">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>Hi Craig,</div>
<div><br>
</div>
<div>I think this question could be thin ice :-)</div>
<div><br>
</div>
<div>We could start a highly political and emotional discussion on
this. Question is, do we want to support fossil fuel burning
technology, or do we want to make the statement, that the
burning stuff aera is over and if you want to use cool
technology like OVMS, then come into the future and buy an
electric vehicle?</div>
<div><br>
</div>
<div>Now I'm definitly aware that there will be various different
points of view on this topic and that it is a hot topic. It is
easy to drift into arguing about how political or not OVMS
should or could be and political discussions in a large
community mostly leed to emotional discussions.</div>
<div><br>
</div>
<div>I would like to go the way Robert Llewellyn (Youtube channel
Fullycharged) went, when he started to disagree with Johnny
Smith on wether to test hybrids on the channel or not. Robert
decided not to do so, because that would be the wrong signal to
the viewers. But that decission went to the point that Johnny
left the show. So, as I said, these discussions can be thin ice
:-)</div>
<div><br>
</div>
<div>I'm interested to see where we will be going on this.</div>
<div><br>
</div>
<div>Greetinx</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div>Am Freitag, den 12.06.2020, 16:09 -0700 schrieb Craig Leres:</div>
<blockquote type="cite">
<pre>I'd like to add a boolean metric for gas vehicles as a prelude to the
phone apps having this info. Would this be ok?
#define MS_V_MOT_GAS "v.m.gas"
ms_v_mot_gas = new OvmsMetricBool(MS_V_MOT_GAS);
The default to false. The other way would be via OvmsMetricInt and an
enum (or defines):
typedef enum : uint8_t
{
Battery = 0,
Gasoline = 1,
} metric_vehicle_t;
#define MS_V_MOT_TYPE "v.m.type"
ms_v_mot_type = new OvmsMetricInt(MS_V_MOT_TYPE);
which would allow for more than two types.
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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-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>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>