[Ovmsdev] Poor wifi performance

Mark Webb-Johnson mark at webb-johnson.net
Wed Aug 15 19:49:54 HKT 2018


I haven’t seen any new problems, so will be tagging a 3.1.009 now, and releasing it to EAP tonight. 90+ changes since 3.1.008 is too many.

Regards, Mark.

> On 4 Aug 2018, at 3:38 PM, Michael Balzer <dexter at expeedo.de> wrote:
> 
> Greg, Mark,
> 
> It would be nice if it had a direct effect, would be reproducable then… :-)
> 
> Every crash event of this kind I had and got reported involved some sort of poor wifi situation. But the module still resolves >99% of those situations without a crash.
> 
>> Feature wise it is fine. Just trying to find out the cause of these crashes, and if they are worse in recent edge builds vs main 3.1.008.
> 
> From my crash statistics (*-OVM-DebugCrash = 1 month):
> 3.1.008: 30 cars, 878 crashes => 29 crashes per car
> >= 3.1.008-73 (idf v3.2): 13 cars, 39 crashes => 3 crashes per car
> There should be more data available on your server.
> 
> My crash statistics query:
> SELECT v.version, v.cars, c.crashes, c.crashes/v.cars AS crashratio
> FROM
> (
>  SELECT LEFT(m_msg, INSTR(m_msg,'/')-1) AS version, COUNT(*) AS cars
>  FROM ovms_carmessages
>  WHERE m_code='F' AND m_msg LIKE '%build idf%'
>  GROUP BY version
> ) v
> LEFT JOIN
> (
>  SELECT LEFT(h_data, INSTR(h_data,'/')-1) AS version, COUNT(*) AS crashes
>  FROM ovms_historicalmessages
>  WHERE h_recordtype='*-OVM-DebugCrash' AND h_data LIKE '%build idf%'
>  GROUP BY version
> ) c
> ON c.version = v.version
> GROUP BY v.version
> Regards,
> Michael
> 
> 
> Am 03.08.2018 um 03:26 schrieb Greg D.:
>> My feeling is that we don't have enough information to really know, and
>> what we know is inconsistent.  I had a couple of wireless and internet
>> "burps" yesterday and today (my router rebooted itself, and separately,
>> the modem dropped link a time or two), yet no further issues from the
>> OVMS module.  So, I am skeptical what direct effect wi-fi has on the
>> reboots.
>> 
>> I think the best bet is to push 3.1.009 out, when it is otherwise ready,
>> and gather more information on the issue. 
>> 
>> Greg
>> 
>> 
>> Mark Webb-Johnson wrote:
>>> Feature wise it is fine. Just trying to find out the cause of these crashes, and if they are worse in recent edge builds vs main 3.1.008.
>>> 
>>> Regards, Mark
>>> 
>>>> On 2 Aug 2018, at 2:54 PM, Stephen Casner <casner at acm.org> <mailto:casner at acm.org> wrote:
>>>> 
>>>> Michael,
>>>> 
>>>> Will 009 be ready for main soon?  I could switch to edge, but my
>>>> friend in Santa Barbara needs it too, and edge would not be good for
>>>> him.
>>>> 
>>>>                                                        -- Steve
>>>> 
>>>> On Wed, 1 Aug 2018, Michael Balzer wrote:
>>>> 
>>>>> Steve, Greg,
>>>>> 
>>>>> you're both still on the 3.1.008 main release, please check out the edge build.
>>>>> 
>>>>> Your crashes look very familiar to me, I assume they are wifi related. The "esf_buf" error log Steve had is coming from within the wifi blob, and the latest
>>>>> edge build includes many fixes to that. That build reduced those crashes in the Twizy community by about 90%.
>>>>> 
>>>>> Regarding logging, this is my base config:
>>>>> 
>>>>>  level: debug
>>>>>  level.gsm-ppp: debug
>>>>>  level.simcom: debug
>>>>>  level.time: info
>>>>>  level.v-twizy: verbose            ← change accordingly
>>>>>  level.webserver: debug
>>>>> 
>>>>> If I need more detail I simply switch the default level to verbose.
>>>>> 
>>>>> Regards,
>>>>> Michael
>>>>> 
>>>>> 
>>>>> Am 01.08.2018 um 08:40 schrieb Greg D.:
>>>>>> Well, we seem to be on a roll...  Got another one.
>>>>>> 
>>>>>> I just realized that I have an SD card in the module, but am not logging anything.  What logging should I be setting up to capture additional information?
>>>>>> 
>>>>>> Greg
>>>>>> 
>>>>>> Last boot was 2153 second(s) ago Time at boot: 2018-07-31 23:01:39 PDT This is reset #20 since last power cycle Detected boot reason: Crash (12/12) Crash
>>>>>> counters: 2 total, 0 early Last crash: Alloca exception on core 0 Registers: PC : 0x40081b96 PS : 0x00060634 A0 : 0x80081d61 A1 : 0x3ffafa60 A2 : 0x3ffb43e4
>>>>>> A3 : 0x00000001 A4 : 0x00000050 A5 : 0x00000001 A6 : 0x000000fe A7 : 0x000000a0 A8 : 0x00000081 A9 : 0x00000001 A10 : 0x0000cdcd A11 : 0x00000000 A12 :
>>>>>> 0x3f40819c A13 : 0x3f407ebe A14 : 0x000000fe A15 : 0x00060023 SAR : 0x00000000 EXCCAUSE: 0x00000005 EXCVADDR: 0x00000000 LBEG : 0x40097664 LEND : 0x40097692
>>>>>> LCOUNT : 0xffffffff Backtrace: 0x40081b96 0x40081d5e 0x400db815 0x40174f95 0x400e73be 0x400e4699 0x40085149 0x40128bc2 0x40128df7 0x401287b4 0x400ea22d
>>>>>> 0x400eac7a 0x400ead09 0x400ead19 0x402207d6 0x400e9ece 0x400e9f79 0x400e45f5 0x400e4604 0x400f5c09 0x400f035d Version: 3.1.008/ota_1/main (build idf
>>>>>> v3.1-dev-986-g1a1a544a Jun 26 2018 09:30:21)
>>>>>> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>>>> Running partition: ota_1 Boot partition: ota_1 Firmware: 3.1.008/ota_1/main (build idf v3.1-dev-986-g1a1a544a Jun 26 2018 09:30:21)
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Greg D. wrote:
>>>>>>> Hi Steve,
>>>>>>> 
>>>>>>> Ok, so, still a puzzle as to why the crashes.  Fortunately, I've only
>>>>>>> had the one.  I've not had any trouble losing wifi connectivity, either
>>>>>>> when the car's been sitting in the garage for a few days, or coming and
>>>>>>> going on errands (so, transitioning to cell and back).  Prior to this, I
>>>>>>> think the last boot was the upgrade to 3.1.008.  Oh, perhaps the car's
>>>>>>> recent near death experience (*) cycled power?  Not sure, but probably
>>>>>>> did.  Anyway, in general, I've not had trouble with connectivity in a
>>>>>>> long time.
>>>>>>> 
>>>>>>> The only thing I've noticed is that sometimes I have a rather long delay
>>>>>>> between an event (e.g. when the car starts charging) and having it show
>>>>>>> up on my cell phone.  Usually I get it immediately, but some time it's
>>>>>>> delayed several minutes, and once in a while it never shows up (e.g.
>>>>>>> charging started but never finished).  It might simply be packet loss on
>>>>>>> my Internet connection (it's fast, but sometimes leaky), not related to
>>>>>>> wi-fi.  I get delays at times on the PC going to websites too.
>>>>>>> 
>>>>>>> {shrug}
>>>>>>> 
>>>>>>> Greg
>>>>>>> 
>>>>>>> (*)  For some reason, the VMS lost connectivity to the VDS, and the car
>>>>>>> locked up.  Fortunately it was in the garage, and the windows were
>>>>>>> rolled down since the door opening switches stopped working too.  Had to
>>>>>>> unplug the cables to the VMS under the dash and plug them back in to
>>>>>>> force a reboot.  {phew!}
>>>>>>> 
>>>>>>> 
>>>>>>> Stephen Casner wrote:
>>>>>>>> On Sun, 29 Jul 2018, Greg D. wrote:
>>>>>>>> 
>>>>>>>>> Hi Steve,
>>>>>>>>> 
>>>>>>>>> Interesting...? I just got a very cryptic "event" from my car:?
>>>>>>>>>      Not charging
>>>>>>>>>      SOC:-
>>>>>>>> I believe it is expected to get that event when OVMS boots while the
>>>>>>>> car is idle since "not charging" is an accurate description of the
>>>>>>>> state.
>>>>>>>> 
>>>>>>>> I received a "not charging" notification on Sunday as well,
>>>>>>>> coincidentally as we were approaching home in our RAV4-EV.  This
>>>>>>>> resulted from another "Alloca exception on core 0" crash and reboot of
>>>>>>>> OVMS:
>>>>>>>> 
>>>>>>>>    Last boot was 170458 second(s) ago
>>>>>>>>    Time at boot: 2018-07-29 21:41:32 GMT
>>>>>>>>    This is reset #7 since last power cycle
>>>>>>>>    Detected boot reason: Crash (8/14)
>>>>>>>>    Crash counters: 2 total, 0 early
>>>>>>>> 
>>>>>>>>    Last crash: Alloca exception on core 0
>>>>>>>> 
>>>>>>>> This is not the same time as yours (2018-07-29 17:55:36 PDT) so it
>>>>>>>> does not appear that the crashes are synchronized by some external
>>>>>>>> event.
>>>>>>>> 
>>>>>>>> Then today I looked at the iPhone app and saw that my OVMS had not
>>>>>>>> communicated with the v2 server for 15 hours.  So I connected to the
>>>>>>>> USB cable again and found that the wifi was again in trouble.  This
>>>>>>>> time there were many instances of a new error message from wifi that I
>>>>>>>> had not seen before, as shown in the log below.
>>>>>>>> 
>>>>>>>> Again I was able to restore operation of both server v2 and http by
>>>>>>>> "wifi mode off" then "wifi mode client".
>>>>>>>> 
>>>>>>>>                                                        -- Steve
>>>>>>>> 
>>>>>>>> E (170324792) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170325752) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170328632) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address|
>>>>>>>> E (170328632) ovms-server-v2: Status: Error: Connection failed
>>>>>>>> E (170329542) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333742) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333742) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333742) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333752) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333752) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333752) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333752) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333752) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333752) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170333762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170335592) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> I (170335672) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
>>>>>>>> I (170335672) ovms-server-v2: Status: Connecting...
>>>>>>>> E (170335672) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170336312) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170337272) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170338232) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170339192) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170340152) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170341112) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170342072) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170343032) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> OVMS> ena
>>>>>>>> Password:
>>>>>>>> E (170343992) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170344702) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170345912) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170346232) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170346872) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170347262) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> OVMS#
>>>>>>>> E (170347832) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170348792) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address|
>>>>>>>> E (170348792) ovms-server-v2: Status: Error: Connection failed
>>>>>>>> E (170348792) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170349752) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170350832) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353802) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353802) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353802) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353802) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353812) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353812) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353812) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353812) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353812) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353812) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353812) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353822) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353822) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353822) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353822) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353832) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353832) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353832) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170353832) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> I (170355672) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
>>>>>>>> I (170355672) ovms-server-v2: Status: Connecting...
>>>>>>>> E (170355672) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170356472) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170357432) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170358392) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170359352) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170359842) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170360862) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170362232) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170362922) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170363192) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170364152) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170365112) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170366072) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170368952) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address|
>>>>>>>> E (170368952) ovms-server-v2: Status: Error: Connection failed
>>>>>>>> E (170372022) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373762) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373772) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373782) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373782) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373782) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373782) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373782) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170373782) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170374992) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170375672) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170375672) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> I (170375672) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
>>>>>>>> I (170375672) ovms-server-v2: Status: Connecting...
>>>>>>>> E (170376632) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170377592) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170378062) wifi: esf_buf: t=7 l=1600 max:16, alloc:16 no eb
>>>>>>>> E (170378552) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170379512) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170380472) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170381432) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> E (170382392) wifi: esf_buf: t=7 l=110 max:16, alloc:16 no eb
>>>>>>>> OVMS# wifi mode off
>>>>>>>> Stopping wifi station...
>>>>>>>> I (170383222) esp32wifi: Stopping WIFI station
>>>>>>>> I (170383222) wifi: state: run -> init (0)
>>>>>>>> I (170383222) wifi: pm stop, total sleep time: 47593209375 us / 59459320714 us
>>>>>>>> I (170383222) wifi: n:1 0, o:1 1, ap:1 1, sta:1 0, prof:1
>>>>>>>> I (170383232) wifi: flush txq
>>>>>>>> I (170383232) wifi: stop sw txq
>>>>>>>> I (170383232) wifi: lmac stop hw txq
>>>>>>>> E (170389112) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address|
>>>>>>>> E (170389112) ovms-server-v2: Status: Error: Connection failed
>>>>>>>> I (170389112) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64)
>>>>>>>> I (170389112) netmanager: Set DNS#0 8.8.8.8
>>>>>>>> I (170389112) netmanager: Set DNS#1 8.8.4.4
>>>>>>>> I (170389112) netmanager: WIFI client down (with MODEM up): reconfigured for MODEM priority
>>>>>>>> I (170389122) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64)
>>>>>>>> I (170389122) netmanager: Set DNS#0 8.8.8.8
>>>>>>>> I (170389122) netmanager: Set DNS#1 8.8.4.4
>>>>>>>> I (170389122) esp32wifi: STA disconnected with reason 8
>>>>>>>> W (170389122) netmanager: CleanupConnections: can't get AP station list
>>>>>>>> I (170389122) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64)
>>>>>>>> I (170389122) netmanager: Set DNS#0 8.8.8.8
>>>>>>>> I (170389122) netmanager: Set DNS#1 8.8.4.4
>>>>>>>> I (170389132) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64)
>>>>>>>> I (170389132) netmanager: Set DNS#0 8.8.8.8
>>>>>>>> I (170389132) netmanager: Set DNS#1 8.8.4.4
>>>>>>>> I (170389132) netmanager: WIFI access point is down
>>>>>>>> I (170389132) esp32wifi: AP stopped
>>>>>>>> I (170389132) netmanager: CleanupConnections: closing conn 3f81dbbc: interface/link down
>>>>>>>> I (170389142) netmanager: CleanupConnections: closing conn 3f81dbbc: interface/link down
>>>>>>>> I (170389142) time: Network was reconfigured: restarting SNTP client
>>>>>>>> I (170389142) ovms-server-v2: Network was reconfigured: disconnect, and reconnect in 10 seconds
>>>>>>>> I (170389142) ovms-server-v2: Status: Network was reconfigured: disconnect, and reconnect in 10 seconds
>>>>>>>> I (170389152) netmanager: CleanupConnections: closing conn 3f81dbbc: interface/link down
>>>>>>>> I (170398672) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
>>>>>>>> I (170398672) ovms-server-v2: Status: Connecting...
>>>>>>>> I (170401312) housekeeping: 2018-07-31 21:01:32 GMT (RAM: 8b=113788-152956 32b=28252)
>>>>>>>> I (170402032) ovms-server-v2: Connection successful
>>>>>>>> I (170402032) ovms-server-v2: Status: Logging in...
>>>>>>>> I (170402032) ovms-server-v2: Sending server login: MP-C 0 xR/s7da9YTwJ+uKH0C2zRl VXtWmVfsQQjJCe4+AwK74w== US33
>>>>>>>> I (170402852) ovms-server-v2: Got server response: MP-S 0 1uDt9VTVDl5jzvSqsIwmtN isXmd3Gy2AcrvhQVrX3LAA==
>>>>>>>> I (170402852) ovms-server-v2: Server token is 1uDt9VTVDl5jzvSqsIwmtN and digest is isXmd3Gy2AcrvhQVrX3LAA==
>>>>>>>> I (170402852) ovms-server-v2: Status: Server authentication ok. Now priming crypto.
>>>>>>>> I (170402852) ovms-server-v2: Shared secret key is 1uDt9VTVDl5jzvSqsIwmtNxR/s7da9YTwJ+uKH0C2zRl (44 bytes)
>>>>>>>> I (170402852) ovms-server-v2: Status: OVMS V2 login successful, and crypto channel established
>>>>>>>> I (170402872) ovms-server-v2: Incoming Msg: MP-0 Z0
>>>>>>>> I (170403672) ovms-server-v2: Send MP-0 S70.0,M,65535,127,stopped,standard,166,146,32,0,0,2100,7,21,0,0,0,0,0.00,0,0,0,0,-1,0,0,0,0,0,0,0,0.00,0.00,0
>>>>>>>> I (170403672) ovms-server-v2: Send MP-0 D65,0,5,23,23,24,587,516256,0,170403,24,0,1,1,11.63,0,12.6,0,23,0
>>>>>>>> I (170403672) ovms-server-v2: Send MP-0 L37.346340,-122.037308,206,64,1,1,0,0,0.0,0,0
>>>>>>>> I (170403682) ovms-server-v2: Send MP-0 F3.1.008/ota_0/main (build idf v3.1-dev-986-g1a1a544a Jun 26 2018 09:30:21),5YJRE11B181000033,7,1,TR1N,AT&T Hologram
>>>>>>>> OVMS# wifi mode client Revelstoke
>>>>>>>> Starting WIFI as a client to Revelstoke...
>>>>>>>> I (170432062) wifi: mode : sta (30:ae:a4:43:9c:28)
>>>>>>>> I (170434462) wifi: n:1 0, o:1 0, ap:255 255, sta:1 0, prof:1
>>>>>>>> I (170435152) wifi: state: init -> auth (b0)
>>>>>>>> I (170435162) wifi: state: auth -> assoc (0)
>>>>>>>> I (170435162) wifi: state: assoc -> run (10)
>>>>>>>> I (170435202) wifi: connected with Revelstoke, channel 1
>>>>>>>> I (170435202) wifi: pm start, type: 1
>>>>>>>> I (170438872) event: sta ip: 192.168.1.82, mask: 255.255.255.0, gw: 192.168.1.254
>>>>>>>> I (170438872) netmanager: Interface priority is st4 (192.168.1.82/255.255.255.0 gateway 192.168.1.254)
>>>>>>>> I (170438872) netmanager: Set DNS#0 8.8.8.8
>>>>>>>> I (170438872) netmanager: Set DNS#1 8.8.4.4
>>>>>>>> I (170438872) netmanager: WIFI client up (with MODEM up): reconfigured for WIFI client priority
>>>>>>>> I (170438872) esp32wifi: STA got IP with SSID: Revelstoke, MAC: 30:ae:a4:43:9c:28, IP: 192.168.1.82, mask: 255.255.255.0, gw: 192.168.1.254
>>>>>>>> I (170438882) time: Network was reconfigured: restarting SNTP client
>>>>>>>> I (170438882) ovms-server-v2: Network was reconfigured: disconnect, and reconnect in 10 seconds
>>>>>>>> I (170438882) ovms-server-v2: Status: Network was reconfigured: disconnect, and reconnect in 10 seconds
>>>>>>>> I (170439082) ovms-server-v2: Status: Disconnected
>>>>>>>> I (170451362) webserver: HTTP GET /
>>>>>>>> I (170451572) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>> I (170451842) webserver: HTTP GET /status
>>>>>>>> I (170458672) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
>>>>>>>> I (170458672) ovms-server-v2: Status: Connecting...
>>>>>>>> I (170458902) ovms-server-v2: Connection successful
>>>>>>>> I (170458902) ovms-server-v2: Status: Logging in...
>>>>>>>> I (170458902) ovms-server-v2: Sending server login: MP-C 0 zSgUQypXKd9tYDq7XuHf8m Raby/geQppSUPG5l9NRztw== US33
>>>>>>>> I (170458922) webserver: HTTP POST /status
>>>>>>>> I (170458922) webserver: HandleLogin: 'admin' logged in, sid 6ea0f4c3207e3328
>>>>>>>> I (170459342) ovms-server-v2: Got server response: MP-S 0 ooMhIGTk/0ZEvxVpwoHZ4d 4d+RTkaUZ1onzxLyxVwYEQ==
>>>>>>>> I (170459342) ovms-server-v2: Server token is ooMhIGTk/0ZEvxVpwoHZ4d and digest is 4d+RTkaUZ1onzxLyxVwYEQ==
>>>>>>>> I (170459342) ovms-server-v2: Status: Server authentication ok. Now priming crypto.
>>>>>>>> I (170459342) ovms-server-v2: Shared secret key is ooMhIGTk/0ZEvxVpwoHZ4dzSgUQypXKd9tYDq7XuHf8m (44 bytes)
>>>>>>>> I (170459342) ovms-server-v2: Status: OVMS V2 login successful, and crypto channel established
>>>>>>>> I (170459352) ovms-server-v2: Incoming Msg: MP-0 Z0
>>>>>>>> I (170459352) webserver: HTTP GET /status
>>>>>>>> I (170459392) webserver: HTTP GET /menu
>>>>>>>> _______________________________________________
>>>>>>>> OvmsDev mailing list
>>>>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>>>> 
>>>>>> _______________________________________________
>>>>>> OvmsDev mailing list
>>>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>>>> --
>>>>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>>>>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>>>> 
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
> 
> -- 
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180815/53119852/attachment-0001.html>


More information about the OvmsDev mailing list