<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The ovms server v3 is very experimental, and not complete. In particular, there is currently no rate limiting of metric output. Really just a proof of concept at the moment. It is fine for the DEMO vehicle module, for me, but with a real vehicle module I think the output stream would be quickly overwhelmed. Perhaps that is the reason for the mongoose fault adding to a buffer?<div class=""><br class=""></div><div class="">I remember that mqtt message when I was playing with server v3 before. Something about mongoose going back and modifying the headers to the MQTT message, after it has prepared the message itself, but mg_send having already sent those headers out. Have a look back in this mailing list for subject 'Transition to new esp-idf’ around 19th through 22nd January. But I thought we had rolled back the changes to mongoose that caused that.</div><div class=""><br class=""></div><div class="">I can’t really work on server v3 at the moment, until we have a very stable base for ovms v3.1, using server v2. We’re going to have real users soon, and I need to ensure they have a workable system. This will also give us a lot of real world experience with the modules in cars (which we are missing).</div><div class=""><br class=""></div><div class="">Let’s revisit this in a month or so, once v3.1 hardware is out and running ok.</div><div class=""><br class=""></div><div class="">Regards, Mark.<br class=""><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On 24 Mar 2018, at 7:59 PM, Julien “JaXX” Banchet <<a href="mailto:jaxx@jaxx.org" class="">jaxx@jaxx.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<title class=""></title>
<div class="">
<div name="messageReplySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;" class=""><br class="">
On 24 Mar 2018 at 12:03 +0100, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net" class="">mark@webb-johnson.net</a>>, wrote:<br class="">
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #1abc9c;" class="">I have my phone’s wifi hotspot on the module as well. So, even on the road I can just turn that on, the module connects to my phone, then I can get back into it directly.
<div class=""><br class=""></div>
<div class="">I think AP is fine now - just trying to minimise the number of things I am using so as to get a very stable base. Then can enable other things and if it breaks I know where to check.</div>
<div class=""><br class=""></div>
<div class="">Regards, Mark. </div>
</blockquote>
<br class="">
<div class="">Yes, you can scratch what I said earlier, the very last commits made AP non-blocking.</div>
<div class=""><br class=""></div>
<div class="">Before switching to AP, I had client mode on, and I did have v2 and v3 enabled at the same time which crash looped a few times on a very steady "assertion "nc->send_mbuf.len >= len" failed: file "/Users/jaxx/Projects/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/mongoose/mongoose/mongoose.c", line 10573, function: mg_mqtt_prepend_header” during "v3 TX(all) metrics", and even with v2 disabled… Swapped v3 for v2, rock stable, from my desk</div>
<div class=""><br class=""></div>
<div class="">But, in AP mode, v3 (alone in auto) doesn’t connect once PPP comes online:</div>
<div class=""><a href="https://pastebin.com/EjCyfvLS" class="">https://pastebin.com/EjCyfvLS</a><br class=""></div>
<div class=""><br class=""></div>
<div class="">(I have tried this multiple times, v3 upon startup hangs the module if I ever try to restart, either v2 or v3 btw)</div>
<div class=""><br class=""></div>
<div class="">If started with v2 only, all goes fine, and I can even stop start both without any real hiccup:</div>
<div class=""><a href="https://pastebin.com/G0357xQW" class="">https://pastebin.com/G0357xQW</a><br class=""></div>
<div class=""><br class=""></div>
<div class="">Anyone who wants to play with mqtt in Europe for v3 can use:</div>
<div class=""><a href="http://libre.jaxx.org" class="">libre.jaxx.org</a> being Fiber@home near Paris, mqtt on a virtual container in my lab</div>
<div class=""><a href="http://mqtt.jaxx.org" class="">mqtt.jaxx.org</a> is a small server in the Netherlands</div>
<div class="">Both mosquitto 1.4.10 with simple authentication<br class=""></div>
<div class=""><br class=""></div>
<div class="">config set server.v3 server <a href="http://libre.jaxx.org" class="">libre.jaxx.org</a></div>
<div class="">Or</div>
<div class="">config set server.v3 server <a href="http://mqtt.jaxx.org" class="">mqtt.jaxx.org</a><br class=""></div>
<div class="">config set server.v3 user ovmsdev</div>
<div class="">config set server.v3 password 0vmsd3v</div>
<div class=""><br class=""></div>
<div class="">#(I will take it out one day or another, but will most certainly forget it unless it gets hacked :-) )<br class=""></div>
<div class=""><br class=""></div>
<div class="">JB./.</div>
<div class=""></div>
</div>
</div>
_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>