<html><head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><div>For the VW e-Up all is fine by me. The blocking by T26 as hypothetical protection for triggering the extended 12v charging is still in the code. That is, from my point of view, the way to go, as long is this behaviour is still not completely understood.</div><div><br></div><div>Regards</div><div><br></div><div>Chris</div><div><br></div><div><br></div><div><br></div><div><br></div><div>Am Samstag, den 27.02.2021, 16:47 +0100 schrieb Michael Balzer:</div><blockquote type="cite">
As the other thread got off-topic: I'd still like to get forward
regarding release 3.2.016.<br>
<br>
We identified three open issues:<br>
<ol>
<li>VW e-Up sometimes stays awake for 4-5 hours.</li>
<li>Wifi AP connection is unstable with some devices.</li>
<li>More frequent location flatbed theft false alerts.<br>
</li>
</ol>
My current status on these is:<br>
<ol>
<li>…is probably not a bug on the OVMS but rather a real behaviour
of the e-Up performing an extended 12V trickle charge.</li>
<li>…has only been reported by Steve Davies and seems (?) to have
been solved by the default scan timings – Steve?</li>
<li>…seems to be a Heisenbug, i.e. hasn't had any reports since we
added extended logging.<br>
</li>
</ol>
Is my status correct? If so, I think these should no longer stop us
from releasing 3.2.016.<br>
<br>
Regards,<br>
Michael<br>
<br>
<pre>_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre></blockquote></body></html>