<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Mark,<br>
<br>
Um, I'm still on the original ESP IDF 2.1 branch from Expresif from
when I first got going, not our clone branch. When did they apply
the patch (i.e. do I already have it)? I'm assuming not.<br>
<br>
I'm heading out of town for a few days, so probably won't be able to
switch branches until mid-late next week. Could you remind me how
to switch IDF branches, for eggnog mitigation purposes? Do I need
to remove the old ESP code and fetch / unpack the new, or is it a
simple matter of a git command to a different github location? It
was a while ago that I set this up.<br>
<br>
Thanks, and Happy Holidays, all,<br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Mark Webb-Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:B94C6E9C-2F44-445D-93AE-BC44A2504DBF@webb-johnson.net">I
found this patch from Espressif:
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class=""><a
href="https://github.com/espressif/esp-idf/pull/1100/commits/6dd48547adbdaf89e43b680dc027e5aa786d9c0e"
class="" moz-do-not-send="true">https://github.com/espressif/esp-idf/pull/1100/commits/6dd48547adbdaf89e43b680dc027e5aa786d9c0e</a></div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>They had only applied it to ‘master’, and not the ‘2.1’
branch we use. It seems to resolve the problem.</div>
<div><br class="">
</div>
<div>I also made some changes to the ovms_server_v2 to try to
tear down the connection _before_ the ppp link goes down (but
I now think these are unnecessary, although probably
beneficial).</div>
<div><br class="">
</div>
<div>Can you guys try updating both your ESP IDF (based on open
vehicles 2.1 repo) and ovms v3 firmware. See if it is more
reliable? I will leave mine running now, to see if there is
any improvement for long-lived connections.</div>
<div><br class="">
</div>
<div>Regards, Mark.</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 19 Dec 2017, at 5:14 AM, Greg D. <<a
href="mailto:gregd2350@gmail.com" class=""
moz-do-not-send="true">gregd2350@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi folks,<br class="">
<br class="">
I left my module running with the modem connected (WiFi
client off) for<br class="">
a couple of days. V2 server configured and connected,
but the phone<br class="">
client was not running. The module was sitting on my
desk (not in a<br class="">
car), powered from the high-power USB port on my laptop.
It was<br class="">
blinking happily last night when I went to bed, but dark
this morning. <br class="">
Apparently had crashed and rebooted during the night. <br
class="">
<br class="">
Here's the trace-back from the screen. Looks like a link
drop was the<br class="">
trigger, or perhaps the result of something else.<br
class="">
<br class="">
Hope this helps,<br class="">
<br class="">
Greg<br class="">
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>