<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body><div>Perfect! Thanx.</div><div><br></div><div>I'm back on track on monday.</div><div><br></div><div>Regards</div><div><br></div><div>Chris</div><div><br></div><div>Am Samstag, den 19.09.2020, 13:12 +0200 schrieb Michael Balzer:</div><blockquote type="cite">
Chris,<br>
<br>
I've now set up a test environment for CAN2 & 3 and have begun
investigating the issue.<br>
<br>
I'll come back to you when I've fixed it.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 18.09.20 um 19:51 schrieb Michael
Balzer:<br>
</div>
<blockquote type="cite" cite="mid:8f97817f-a70b-6e4e-909e-4456844d9f84@expeedo.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Chris,<br>
<br>
the fix isn't meant to eliminate bus errors, it just should solve
the log errors.<br>
<br>
I.e. you should now see exactly those frames in the TX log, that
you transmit.<br>
<br>
TX_Fail log entries can result from actual bus errors as well as
from TX queue overflows.<br>
<br>
TX queue overflows are counted separately, see <tt>can can3
status</tt>. If you have TX overflows, you need to raise the
queue size.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 18.09.20 um 19:38 schrieb Chris
van der Meijden:<br>
</div>
<blockquote type="cite" cite="mid:1600450714.2288.5.camel@arachnon.de">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div>I did a first test with mixed results.</div>
<div><br>
</div>
<div>I don't see the Asynchronous Errors anymore, but I see
TX_FAIL messages and neither unlocking nor climate control
works with the patch.</div>
<div><br>
</div>
<div>I will continue on monday with some deeper checks and I
hope I can produce some</div>
<div> log output then.</div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<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" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<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="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
<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>