<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 25.04.2020 20:24, Tamás Kovács
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGpaXUsbuVDZWnZUb9mR-DxXcj2gU+ZMqkL4di2mQXz3Om7VGw@mail.gmail.com">Thanks
the log, now i modified the AC charge detection code.
<div><br>
</div>
<div>If you want to try add the following to config / firmware /
flash from web : <a
href="http://kommykt-nas.ddns.net:22289/ovms3.bin"
moz-do-not-send="true">kommykt-nas.ddns.net:22289/ovms3.bin</a></div>
<div>This is my NAS, the internet speed is not very high. </div>
<div><br>
</div>
</blockquote>
It now works
<div> <br>
</div>
OVMS# stat<br>
Type1 - Charging<br>
234.0V/5.7A<br>
SOC: 95.5%<br>
Ideal range: 73km<br>
Est. range: 92km<br>
ODO: 82155.0km<br>
CAC: 41.8Ah<br>
SOH: 87%<br>
AC charge: 0.070kWh kWh<br>
<p>DC charge: 0.040kWh kWh</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAGpaXUsbuVDZWnZUb9mR-DxXcj2gU+ZMqkL4di2mQXz3Om7VGw@mail.gmail.com">
<div>Should I rewrite the old RR display during quick charging?</div>
</blockquote>
<p>Its better that its empty than 255.<br>
<br>
So, the Est. range in OVMS should not be updated if the CAN bus
claims 255, or sett to null.<br>
<br>
<br>
<b>Future improvments</b><br>
</p>
But lets us see what numbers we have.<br>
<br>
The car calculates RR from the last 24 km. When driving downhill
this can be a bit optimistic, and pessimistic while driving uphill.<br>
<br>
* We have the Ah of the battery<br>
* We have the wh/km from 'xmi trip' (test if it has a valid range
first)<br>
<br>
RR is 0 when CAN SOC is 10% (0% on display)<br>
<br>
So RR can CAC and xmi.v.bat.cac.rem to calculate a RR.<br>
<br>
When tha calculation is done, the lowest number of est range and
ideal range is shown (in order to prevent error from downhill
driving).<br>
<br>
With this method, you will get the heater usage inn to the
calculation and over-optimistic range due to downhill driving.<br>
<br>
</body>
</html>