Hi Mark,
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.
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.
Thanks, and Happy Holidays, all,
Greg
Mark Webb-Johnson wrote:
I
found this patch from Espressif:
They had only applied it to ‘master’, and not the ‘2.1’
branch we use. It seems to resolve the problem.
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).
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.
Regards, Mark.
Hi folks,
I left my module running with the modem connected (WiFi
client off) for
a couple of days. V2 server configured and connected,
but the phone
client was not running. The module was sitting on my
desk (not in a
car), powered from the high-power USB port on my laptop.
It was
blinking happily last night when I went to bed, but dark
this morning.
Apparently had crashed and rebooted during the night.
Here's the trace-back from the screen. Looks like a link
drop was the
trigger, or perhaps the result of something else.
Hope this helps,
Greg