<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Mark,<br>
<br>
if the Mitsubishi code does not use the new polling hooks, poll0()
will not be called if the polling code is compiled in.<br>
<br>
I had the same problem for the Twizy, that's why I introduced the
OVMS_POLLER compiler switch.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 22.01.2014 02:18, schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote
cite="mid:9C72CDE8-FF26-4120-A9C1-025B34ABEA29@webb-johnson.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Thomas,
<div><br>
</div>
<div>Strange. So far, I see 4 cars using 2.6.2, but only one
(presumably yours) is showing authentication errors.</div>
<div><br>
</div>
<div>I also can't see any changes to the vehicle_mitsubishi.c code
that would cause poll0 to stop working. It is certainly working
in other vehicle modules.<br>
<div><br>
</div>
<div>I'll keep looking, but would be grateful if you could try
to narrow down the poll0 problem.</div>
<div><br>
</div>
<div>Regards, Mark.</div>
<div><br>
<div>
<div>On 22 Jan, 2014, at 5:00 am, Thomas Bergo <<a
moz-do-not-send="true"
href="mailto:thomas.bergo@gmail.com">thomas.bergo@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">Mark,
<div><br>
</div>
<div>Was testing the new 2.6.2 code on i-Miev today. </div>
<div><br>
</div>
<div>Two observations:</div>
<div>- Lots of restarts and "Vehicle authentication
failed" messages in the iOS app </div>
<div>- No CAN bus messages form PID in poll0, while
messages in poll1 is working OK.</div>
<div><br>
</div>
<div>Programmed the OVMS module with a version, and
verified that the module was OK.</div>
<div><br>
</div>
<div>Regards, Thomas</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2013/10/30 Thomas Bergo <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:thomas.bergo@gmail.com"
target="_blank">thomas.bergo@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Matt,
<div><br>
</div>
<div>Please report back when you have done some
testing on the QC.</div>
<div><br>
</div>
<div>If the car report 0A while QC, the current
code will not detect that we are charging. So
then we need to rely on the estimated range
reported as 255 to detecting that the car is QC.</div>
<div><br>
</div>
<div>Regards, Thomas </div>
</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2013/10/30 Matt Beard
OVMS <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:smvo@mxf.org.uk"
target="_blank">smvo@mxf.org.uk</a>></span><br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>Hi Thomas,<br>
<br>
</div>
During QC you don't get valid values
reported in 0x389 - it seems to be
constant 255V, 0A during QC.<br>
<br>
</div>
My code is relying on the fact that
the estimated range only ever seems to
be reported as 255 during QC (except
for the first few messages at startup,
but those are easy to filter out). In
my testing so far this seems to work
for detecting the start and end of QC.
I am going to be doing 3 more tests
today with my latest code and will
report back later.<span><font
color="#888888"><br>
<br>
</font></span></div>
<span><font color="#888888">Matt<br>
<br>
</font></span></div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div>On 27 October 2013 20:13, Thomas
Bergo <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:thomas.bergo@gmail.com"
target="_blank">thomas.bergo@gmail.com</a>></span>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div>
<div dir="ltr">Hi Matt
<div><br>
</div>
<div>I have started to look into
the QC code. And i have one
concern. </div>
<div>
Have you seen if the voltage
and charging current (PID
0x389) is reported during QC? </div>
<div>If not, we are not able to
detect that the car is
charging during QC with
current code.</div>
<span><font color="#888888">
<div><br>
</div>
<div>Thomas</div>
<div class="gmail_extra"><br>
<br>
</div>
</font></span></div>
<br>
</div>
<div>_______________________________________________<br>
OvmsDev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OvmsDev@lists.teslaclub.hk"
target="_blank">OvmsDev@lists.teslaclub.hk</a><br>
<a moz-do-not-send="true"
href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev"
target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br>
<br>
</div>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
OvmsDev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OvmsDev@lists.teslaclub.hk"
target="_blank">OvmsDev@lists.teslaclub.hk</a><br>
<a moz-do-not-send="true"
href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev"
target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
OvmsDev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
</pre>
</body>
</html>