<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Probably the most useful output, at the time when the modem couldn’t recover would be:<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">simcom status</div><div class="">network status</div><div class="">module memory</div><div class="">module tasks</div></blockquote><div class=""><div><br class=""></div><div>I’m only running with the DEMO vehicle module, Server V2, Wifi AP, and SIMCOM. No GPS enabled. The network seems stable to me (although I am getting one general crash about once a day).</div><div><br class=""></div><div>Regards, Mark.</div><div><br class=""><blockquote type="cite" class=""><div class="">On 15 Mar 2018, at 6:18 PM, Tom Parker <<a href="mailto:tom@carrott.org" class="">tom@carrott.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 15/03/18 13:28, Mark Webb-Johnson wrote:<br class=""><blockquote type="cite" class="">This (and the subsequent work to do this globally, irrespective of the state) seems to be working well in my car for the past couple of days.<br class=""><br class="">How is it working out for you? Are you still getting cases where the SIMCOM loses connectivity and it can’t recover?<br class=""></blockquote><br class="">It's much much better, but it's still broken :( Yesterday, with the first half of your changes, it had very poor connectivity but was able to reconnect several times. Today, with the second half of your changes, it didn't seem to reconnect by itself. Unfortunately I haven't had a data logger on it with your improvements so I don't have a lot of information about what is wrong. I went and investigated it's current state this evening and while the CLI user interface was working well, nothing simcom related was being logged. I guess there's something that wedges that task.<br class=""><br class="">I wasn't able to make it connect by rebooting with the button. Stuff happened, but it didn't talk to the v2 server. It's possible the signal strength is too weak at this location? I tried two OVMS antennas with no luck. I've attached the log. I've testing a Spark m2m simcard, and the last few days have been using that. I have access to their m2m monitoring facility, that reported a 3 minute session with 1457 bytes up and 5321 bytes down. After failing to reconnect after rebooting with the button, I put the 2degress consumer simcard back in and it connected immediately. You can see the last thing I do in the log is change the apn. I haven't included the log of the working session.<br class=""><br class="">Thank you for finding the mux bugs, I'm sorry I haven't had time to debug it myself. I'll try to get some minor leaf improvements in before the firmware is locked in but my weekend is looking busy again :(<br class=""><br class="">In other New Zealand news, 2degrees turned off their 2g network early this morning. Vodafone are apparently going to keep theirs up until 2025. I've got a new simcard for my v2 module but I haven't switched it over yet.<br class=""><span id="cid:048A4BD0-125D-4B8C-AD60-848B13E89802"><ovms_2018-03-15T09_21_02+0000.log.bz2></span>_______________________________________________<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></div></blockquote></div><br class=""></div></body></html>