<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Tom,<br>
<br>
Not a problem! Changes made.<br>
<br>
One question... The two vehicle-specific metrics, are they ones
that can be mapped to an OBDII PID? I.e., are they a simple 16-bit
numeric value?<br>
<br>
Thanks for your help,<br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Tom Parker wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f27dab2a-059f-40fc-959c-43c9d1b22e2e@carrott.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>On 28/04/18 04:58, Greg D. wrote: </p>
<blockquote type="cite"
cite="mid:5fe8f8d6-5fae-1cbb-f2e5-21488be06e0a@gmail.com">
<pre wrap="">User doc is at
<a class="moz-txt-link-freetext" href="https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oEWRHw/" moz-do-not-send="true">https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oEWRHw/</a>
</pre>
</blockquote>
<br>
Sorry Greg I should have attended to this earlier!<br>
<br>
In addition to those that Robin has identified we currently have:<br>
<br>
v.b.voltage<br>
v.b.current<br>
v.b.range.ideal<br>
v.c.voltage (however this is battery side voltage for both AC and
DC charging) <br>
v.c.current (however this is battery side current for both AC and
DC charging)<br>
v.c.climit<br>
v.c.charging<br>
v.c.type<br>
v.p.speed<br>
v.b.soh<br>
v.b.cac<br>
<br>
I'm not explicitly setting v.type, do we need to in the vehicle
code or is that done by the framework?<br>
<br>
The Leaf also has a couple of specific metrics:<br>
<br>
m_gids = MyMetrics.InitInt("xnl.v.bat.gids", SM_STALE_HIGH, 0);<br>
m_hx = MyMetrics.InitFloat("xnl.v.bat.hx", SM_STALE_HIGH, 0);<br>
<br>
<br>
You can probably just call these gids and hx in your table as this
is the common parlance in Leaf circles.<br>
<br>
Can you also add to the Leaf documentation the following
paragraphs:<br>
<br>
The Leaf support has a number of configuration options:<br>
<br>
<font size="+2">Remote Commands:</font><br>
<p>In model year 2016 Nissan changed how remote commands are
handled, switching from the EV bus to the Car bus and changing
the messages. The OVMS defaults to pre-2016 behaviour. Set the
xnl modelyear configuration option to change to the newer
behaviour:</p>
<p>config set xnl modelyear 2016</p>
<p>Note that if a CARWINGS, Nissan Connect or the TCU hardware is
fitted, the OVMS messages will be overridden by the TCU and when
the OVMS tries to wake the car, it will wake up and then go back
to sleep. To make remote commands work, the TCU needs to be
unplugged if fitted. In model years prior to 2016, this doesn't
cause any obvious problems but in the 2016 model year Nissan
routed the hands free microphone through the TCU and the
microphone stops working when you unplug the TCU.</p>
<p>Assistance is appreciated as I haven't had time to try to
override the TCU using the OVMS or find an alternative solution
to prevent the TCU overriding the messages while still allowing
the hands free microphone to work.<br>
</p>
<p><font size="+2">Battery Size:</font></p>
<p>The OVMS defaults to a 24kWh battery. 30kWh batteries can be
accommodated by changing the xnl maxGids configuration option:</p>
<p>config set xnl maxGids 356</p>
<p><font size="+2">Range Calculation:</font></p>
<p>The OVMS uses 2 configuration options to calculate remaining
range, whPerGid (default 80Wh/gid) and kmPerKWh (default
7.1km/kWh). The range calculation is based on the remaining gids
reported by the LBC and at the moment does not hold 5% in
reserve like LeafSpy. Feedback on this calculation is welcomed.<br>
</p>
<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>