[Ovmsdev] New web setup

Michael Balzer dexter at expeedo.de
Sun May 13 02:54:05 HKT 2018


An annotated normal setup log:


Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console
I (2766) webserver: Launching Web Server
Firmware: 3.1.005-74-g4a100f0-dirty/factory/main
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1

I (2826) simcom: State: Enter CheckPowerOff state
I (11826) housekeeping: System considered stable (RAM: 8b=106600-109352 32b=52008)
I (16826) simcom: State timeout, transition to 13
I (16826) simcom: State: Enter PoweredOff state
I (16826) gsm-mux: Stop MUX

… (finding my tablet, connecting to AP "OVMS") …

I (62026) wifi: n:1 0, o:1 0, ap:1 1, sta:255 255, prof:1
I (62026) wifi: station: 30:75:12:f5:71:c7 join, AID=1, bgn, 20
I (62036) esp32wifi: AP station connected: id: 1, MAC: 30:75:12:f5:71:c7
I (72176) webserver: HTTP GET /
I (72636) webserver: HTTP GET /assets/style.css
I (72636) webserver: HTTP GET /assets/script.js
I (72646) webserver: HTTP GET /apple-touch-icon.png
I (73506) webserver: HTTP GET /home
I (81306) webserver: HTTP GET /cfg/init
I (81306) webserver: CfgInit enter 1

… (entering data for step 1) …

I (119606) webserver: HTTP POST /cfg/init
I (119606) webserver: CfgInit enter 1
I (119606) webserver: CfgInit1: starting test: AP 'Test1'
I (119666) webserver: CfgInitSetStep: step 1.test.start timeout 5
I (119826) webserver: CfgInitTicker: step 1.test.start timeout in 5 seconds
I (123826) webserver: CfgInitTicker: step 1.test.start timeout
I (123826) webserver: CfgInitTicker: step 1: starting wifi AP 'Test1'
I (123826) esp32wifi: Stopping WIFI station
I (123826) wifi: station: 30:75:12:f5:71:c7 leave, AID = 1
I (123826) wifi: n:1 0, o:1 0, ap:1 1, sta:255 255, prof:1
I (123846) wifi: flush txq
I (123846) wifi: stop sw txq
I (123846) wifi: lmac stop hw txq
I (124516) wifi: mode : softAP (30:ae:a4:37:25:89)
I (124516) webserver: CfgInitSetStep: step 1.test.connect timeout 300
I (124526) esp32wifi: AP station disconnected: id: 1, MAC: 30:75:12:f5:71:c7
I (124526) netmanager: WIFI access point is down
I (124526) esp32wifi: AP stopped
I (124536) netmanager: WIFI access point is up
I (124736) esp32wifi: AP started with SSID: Test1, MAC: 30:ae:a4:37:25:89, IP: 192.168.4.1
I (124736) webserver: Stopping Web Server
I (124746) webserver: Launching Web Server
I (124826) webserver: CfgInitTicker: step 1.test.connect timeout in 300 seconds
I (129826) webserver: CfgInitTicker: step 1.test.connect timeout in 295 seconds
I (134826) webserver: CfgInitTicker: step 1.test.connect timeout in 290 seconds
I (139826) webserver: CfgInitTicker: step 1.test.connect timeout in 285 seconds
I (144826) webserver: CfgInitTicker: step 1.test.connect timeout in 280 seconds
I (148176) wifi: n:1 0, o:1 0, ap:1 1, sta:255 255, prof:1
I (148176) wifi: station: 30:75:12:f5:71:c7 join, AID=1, bgn, 20
I (148186) esp32wifi: AP station connected: id: 1, MAC: 30:75:12:f5:71:c7
I (149826) webserver: CfgInitTicker: step 1.test.connect timeout in 275 seconds
I (154826) webserver: CfgInitTicker: step 1.test.connect timeout in 270 seconds
I (159826) webserver: CfgInitTicker: step 1.test.connect timeout in 265 seconds
I (161786) webserver: HTTP GET /
I (161976) webserver: HTTP GET /cfg/init
I (164826) webserver: CfgInitTicker: step 1.test.connect timeout in 260 seconds
I (169826) webserver: CfgInitTicker: step 1.test.connect timeout in 255 seconds
I (171786) webserver: HTTP POST /cfg/init
I (171786) webserver: HandleLogin: 'admin' logged in, sid 2cbdd8198308f453
I (171826) webserver: HTTP GET /menu
I (171846) webserver: HTTP GET /cfg/init
I (171846) webserver: CfgInit enter 1.test.connect
I (171846) webserver: CfgInit1: AP test succeeded
I (171846) webserver: CfgInitSetStep: step 2 timeout 0
I (171866) webserver: CfgInit next: 2

… (entering step 2 data) …

I (216836) webserver: HTTP POST /cfg/init
I (216836) webserver: CfgInit enter 2
I (216856) webserver: CfgInitSetStep: step 2.test.start timeout 5
I (217826) webserver: CfgInitTicker: step 2.test.start timeout in 5 seconds
I (221826) webserver: CfgInitTicker: step 2.test.start timeout
I (221826) webserver: CfgInitTicker: step 2: starting wifi APCLIENT 'Test1' / 'WLAN-214677'
I (221826) esp32wifi: Stopping WIFI station
I (221836) wifi: station: 30:75:12:f5:71:c7 leave, AID = 1
I (221836) wifi: n:1 0, o:1 0, ap:1 1, sta:255 255, prof:1
I (221856) wifi: flush txq
I (221856) wifi: stop sw txq
I (221856) wifi: lmac stop hw txq
I (221866) wifi: mode : sta (30:ae:a4:37:25:88) + softAP (30:ae:a4:37:25:89)
I (221876) webserver: CfgInitSetStep: step 2.test.connect timeout 20
I (221876) esp32wifi: AP station disconnected: id: 1, MAC: 30:75:12:f5:71:c7
I (221876) netmanager: WIFI access point is down
I (221876) esp32wifi: AP stopped
I (221886) netmanager: WIFI access point is up
I (222136) esp32wifi: AP started with SSID: Test1, MAC: 30:ae:a4:37:25:89, IP: 192.168.4.1
I (222136) webserver: Stopping Web Server
I (222136) webserver: Launching Web Server
I (222826) webserver: CfgInitTicker: step 2.test.connect timeout in 20 seconds
I (224586) wifi: ap channel adjust o:1,1 n:11,2
I (224586) wifi: n:11 0, o:1 0, ap:11 2, sta:11 0, prof:1
I (225246) wifi: state: init -> auth (b0)
I (225246) wifi: state: auth -> assoc (0)
I (225256) wifi: state: assoc -> run (10)
I (225266) wifi: connected with WLAN-214677, channel 11
I (225266) wifi: pm start, type: 1
I (225616) event: sta ip: 192.168.2.109, mask: 255.255.255.0, gw: 192.168.2.1
I (225626) netmanager: Interface priority is st3 (192.168.2.109/255.255.255.0 gateway 192.168.2.1)
I (225626) netmanager: Set DNS#0 192.168.2.1
I (225626) netmanager: Set DNS#1 192.168.2.1
I (225626) netmanager: Set DNS#2 0.0.0.0
I (225626) netmanager: WIFI client up (with MODEM down): starting network with WIFI client
I (225626) esp32wifi: STA got IP with SSID: WLAN-214677, MAC: 30:ae:a4:37:25:88, IP: 192.168.2.109, mask: 255.255.255.0, gw: 192.168.2.1
I (225626) time: Starting SNTP client
I (227826) webserver: CfgInitTicker: step 2.test.connect timeout in 15 seconds
I (232826) webserver: CfgInitTicker: step 2.test.connect timeout in 10 seconds
I (233866) wifi: n:11 0, o:11 0, ap:11 2, sta:11 0, prof:11
I (233876) wifi: station: 30:75:12:f5:71:c7 join, AID=1, bgn, 20
I (233876) esp32wifi: AP station connected: id: 1, MAC: 30:75:12:f5:71:c7
I (235556) webserver: HTTP GET /
I (235866) webserver: HTTP GET /cfg/init
I (235866) webserver: CfgInit enter 2.test.connect
I (237826) webserver: CfgInitTicker: step 2.test.connect timeout in 5 seconds
I (241826) webserver: CfgInitTicker: step 2.test.connect timeout
I (242616) webserver: CfgInitTicker: step 2: success, proceeding to step 3
I (242616) webserver: CfgInitSetStep: step 3 timeout 0
I (245386) webserver: HTTP GET /
I (245556) webserver: HTTP GET /cfg/init
I (245556) webserver: CfgInit enter 3

… (entering step 3 data) …

I (258926) webserver: HTTP POST /cfg/init
I (258926) webserver: CfgInit enter 3
I (258956) webserver: CfgInitSetStep: step 3.update timeout 0

… (no new hw3.0 firmware on my server) …

I (259036) webserver: CfgInit3: firmware up to date, proceeding to step 4
I (259036) webserver: CfgInitSetStep: step 4 timeout 0
I (259036) webserver: CfgInit next: 4
I (301826) housekeeping: 2018-05-12 18:42:07 GMT (RAM: 8b=94144-97772 32b=52008)

… (entering step 4 data) …

I (304896) webserver: HTTP POST /cfg/init
I (304896) webserver: CfgInit enter 4
I (304926) webserver: CfgInitSetStep: step 4.test.start timeout 3
I (305446) webserver: HTTP POST /api/execute
I (305446) webcommand: HttpCommandStream[0x3ffe9018]: 88820 bytes free, executing: vehicle status
I (305476) webserver: HTTP POST /api/execute
I (305486) webcommand: HttpCommandStream[0x3ffead00]: 82884 bytes free, executing: server v2 status
I (307826) webserver: CfgInitTicker: step 4.test.start timeout
I (307826) webserver: CfgInitTicker: step 4: setting vehicle type 'RT'
I (307826) v-twizy: Renault Twizy vehicle module
I (307826) v-twizy: battmon subsystem init
I (307836) v-twizy: pwrmon subsystem init
I (307836) v-twizy: charge subsystem init
I (307846) canopen: Worker started on can1
I (307846) v-twizy: sevcon subsystem init
I (307846) webserver: CfgInitSetStep: step 4.test.start timeout 3
I (307856) simcom: State: Enter PoweringOn state
I (307866) simcom: Power Cycle
I (309106) webserver: HTTP POST /api/execute
I (309116) webcommand: HttpCommandStream[0x3fff0a80]: 56176 bytes free, executing: vehicle status
I (310826) webserver: CfgInitTicker: step 4.test.start timeout
I (310826) webserver: CfgInitTicker: step 4: start server v2 for host 'ovms.dexters-web.de'
I (310826) ovms-server-v2: OVMS Server V2 registered metric modifier is #3
I (310826) ovms-server-v2: Status: Server has been started
I (310826) ovms-server-v2: OVMS Server v2 running
I (310836) ovms-server-v2: Connection is ovms.dexters-web.de:6867 Test1
I (310836) ovms-server-v2: Status: Connecting...
I (310856) webserver: CfgInitSetStep: step 4.test.connect timeout 0
I (310876) ovms-server-v2: Connection successful
I (310876) ovms-server-v2: Status: Logging in...
I (310886) ovms-server-v2: Sending server login: MP-C 0 yjAgaG2QpDQXhanp4QhrY5 VjNL56xFykAzPbs4HjLhAg== Test1
I (311066) ovms-server-v2: Got server response: MP-S 0 Wixs45Hmj0ovGeVGBiQChN cGdkD5TjFj4dEhNDxyvc5g==
I (311066) ovms-server-v2: Server token is Wixs45Hmj0ovGeVGBiQChN and digest is cGdkD5TjFj4dEhNDxyvc5g==
I (311076) ovms-server-v2: Status: Server authentication ok. Now priming crypto.
I (311076) ovms-server-v2: Shared secret key is Wixs45Hmj0ovGeVGBiQChNyjAgaG2QpDQXhanp4QhrY5 (44 bytes)
I (311076) ovms-server-v2: Status: OVMS V2 login successful, and crypto channel established
I (311096) ovms-server-v2: Incoming Msg: MP-0 Z0
I (311616) webserver: HTTP POST /api/execute
I (311616) webcommand: HttpCommandStream[0x3fff17b4]: 47544 bytes free, executing: server v2 status
I (311646) webserver: HTTP POST /api/execute
I (311656) webserver: HTTP POST /api/execute
I (311666) webserver: HTTP POST /api/execute
I (311676) webserver: HTTP POST /api/execute
I (311676) webcommand: HttpCommandStream[0x3fff1e38]: 22360 bytes free, executing: server v2 status
I (311676) webcommand: HttpCommandStream[0x3fff6dc0]: 20648 bytes free, executing: server v2 status
I (311686) webcommand: HttpCommandStream[0x3fff8eb8]: 23952 bytes free, executing: server v2 status
I (311646) webcommand: HttpCommandStream[0x3fff33a0]: 23952 bytes free, executing: server v2 status
I (311826) ovms-server-v2: Send MP-0 S0,K,0,0,,standard,50,50,0,0,0,0,0,0,0,0,0,0,108.00,0,0,0,0,-1,0,0,0,0,0,0,0,0.00,0.00,0
I (311826) ovms-server-v2: Send MP-0 D0,0,5,0,0,0,0,0,0,4,0,0,1,0,0,0,0,0,0,0
I (311836) ovms-server-v2: Send MP-0 L0,0,0,0,0,0,0,10000,0,0.0,0.0
I (311846) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0
I (311846) ovms-server-v2: Send MP-0 F3.1.005-74-g4a100f0-dirty/factory/main (build idf ovms-3.1.005-527-g9d8e44e0 May 11 2018 18:40:41),,0,1,RT,WLAN-214677
I (313366) webserver: HTTP POST /api/execute
I (313376) webcommand: HttpCommandStream[0x3fff33a0]: 48176 bytes free, executing: vehicle status
I (313826) simcom: State: Enter PoweredOn state
I (317376) webserver: HTTP POST /api/execute
I (317386) webcommand: HttpCommandStream[0x3fff33a0]: 47912 bytes free, executing: server v2 status
I (318366) webserver: HTTP POST /api/execute
I (318366) webcommand: HttpCommandStream[0x3fff33a0]: 47736 bytes free, executing: vehicle status
I (322366) webserver: HTTP POST /api/execute
I (322376) webcommand: HttpCommandStream[0x3fff33a0]: 47456 bytes free, executing: server v2 status
I (323376) webserver: HTTP POST /api/execute
I (323376) webcommand: HttpCommandStream[0x3fff33a0]: 47508 bytes free, executing: vehicle status

… (click "Keep & proceed") …

I (326266) webserver: HTTP POST /cfg/init
I (326266) webserver: CfgInit enter 4.test.connect
I (326276) webserver: CfgInitSetStep: step 5 timeout 0
I (326316) webserver: CfgInit next: 5
I (326326) webserver: HTTP POST /api/execute
I (326336) webcommand: HttpCommandStream[0x3fff340c]: 45652 bytes free, executing: server v2 status

… (entering step 5 data) …

I (333606) webserver: HTTP POST /cfg/init
I (333606) webserver: CfgInit enter 5
I (333626) webserver: CfgInit5: starting test
I (333626) webserver: CfgInitSetStep: step 5.test.start timeout 3
I (333846) simcom: State: Enter MuxStart state
I (333846) gsm-mux: Start MUX
I (333856) gsm-mux: Channel #0 is open
I (333866) gsm-mux: Channel #1 is open
I (333866) gsm-mux: Channel #2 is open
I (333876) gsm-mux: Channel #3 is open
I (333886) gsm-mux: Channel #4 is open
I (333916) webserver: HTTP POST /api/execute
I (333926) webcommand: HttpCommandStream[0x3fff4278]: 43024 bytes free, executing: simcom status
I (333936) webserver: HTTP POST /api/execute
I (333946) webcommand: HttpCommandStream[0x3fff627c]: 34276 bytes free, executing: simcom status
I (334826) simcom: State: Enter NetWait state
I (334826) gsm-nmea: Startup
I (334986) webserver: HTTP POST /api/execute
I (334986) webcommand: HttpCommandStream[0x3fff32b4]: 43032 bytes free, executing: simcom status
I (335826) webserver: CfgInitTicker: step 5.test.start timeout
I (335826) webserver: CfgInitTicker: step 5: modem enter state NetStart
I (335826) simcom: State: Enter NetStart state
I (336186) webserver: HTTP POST /api/execute
I (336196) webcommand: HttpCommandStream[0x3fff32b4]: 43024 bytes free, executing: simcom status
I (336866) simcom: PPP Connection is ready to start
I (337826) simcom: State: Enter NetMode state
I (337826) gsm-ppp: Initialising...
I (338226) webserver: HTTP POST /api/execute
I (338236) webcommand: HttpCommandStream[0x3fff32b4]: 37856 bytes free, executing: simcom status
I (338826) simcom: Lost network connection (NetworkRegistration in NetMode)
I (338826) simcom: State: Enter NetLoss state
I (338826) gsm-ppp: Shutting down (hard)...
I (338826) gsm-ppp: PPP is shutdown
I (338836) netmanager: Interface priority is st3 (192.168.2.109/255.255.255.0 gateway 192.168.2.1)
I (338846) netmanager: Set DNS#0 192.168.2.1
I (338846) netmanager: Set DNS#1 192.168.2.1
I (338846) netmanager: Set DNS#2 0.0.0.0
I (339176) webserver: HTTP POST /api/execute
I (339186) webserver: HTTP POST /api/execute
I (339186) webcommand: HttpCommandStream[0x3fff5680]: 29184 bytes free, executing: simcom status
I (339186) webcommand: HttpCommandStream[0x3fff51c0]: 29184 bytes free, executing: simcom status
I (344726) webserver: HTTP POST /api/execute
I (344736) webcommand: HttpCommandStream[0x3fff32b4]: 39512 bytes free, executing: simcom status
I (347826) simcom: State timeout, transition to 5
I (347826) simcom: State: Enter NetWait state
I (347826) gsm-nmea: Startup
I (348096) webserver: HTTP POST /api/execute
I (348106) webcommand: HttpCommandStream[0x3fff32b4]: 39316 bytes free, executing: simcom status
I (349826) ovms-server-v2: Send MP-0 h1,0,RT-BAT-P,1,86400,1,1,5000,10000,0,0,1000,0,-40,200,-40,0,0,0,0
I (349826) ovms-server-v2: Send MP-0 h2,0,RT-BAT-C,1,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349836) ovms-server-v2: Send MP-0 h3,0,RT-BAT-C,2,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349836) ovms-server-v2: Send MP-0 h4,0,RT-BAT-C,3,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349836) ovms-server-v2: Send MP-0 h5,0,RT-BAT-C,4,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349836) ovms-server-v2: Send MP-0 h6,0,RT-BAT-C,5,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349836) ovms-server-v2: Send MP-0 h7,0,RT-BAT-C,6,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349836) ovms-server-v2: Send MP-0 h8,0,RT-BAT-C,7,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349846) ovms-server-v2: Send MP-0 h9,0,RT-BAT-C,8,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349846) ovms-server-v2: Send MP-0 h10,0,RT-BAT-C,9,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349846) ovms-server-v2: Send MP-0 h11,0,RT-BAT-C,10,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349846) ovms-server-v2: Send MP-0 h12,0,RT-BAT-C,11,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349846) ovms-server-v2: Send MP-0 h13,0,RT-BAT-C,12,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349846) ovms-server-v2: Send MP-0 h14,0,RT-BAT-C,13,86400,1,1,0,10000,0,0,-40,200,-40,0
I (349846) ovms-server-v2: Send MP-0 h15,0,RT-BAT-C,14,86400,1,1,0,10000,0,0,-40,200,-40,0
I (350136) ovms-server-v2: Incoming Msg: MP-0 h1
I (350136) ovms-server-v2: Incoming Msg: MP-0 h2
I (350146) gsm-ppp: StatusCallBack: User Interrupt
I (350146) gsm-ppp: PPP connection has been closed
I (350146) netmanager: Interface priority is st3 (192.168.2.109/255.255.255.0 gateway 192.168.2.1)
I (350146) netmanager: Set DNS#0 192.168.2.1
I (350146) netmanager: Set DNS#1 192.168.2.1
I (350146) netmanager: Set DNS#2 0.0.0.0
I (350156) ovms-server-v2: Incoming Msg: MP-0 h3
I (350166) ovms-server-v2: Incoming Msg: MP-0 h4
I (350176) ovms-server-v2: Incoming Msg: MP-0 h5
I (350176) ovms-server-v2: Incoming Msg: MP-0 h6
I (350186) ovms-server-v2: Incoming Msg: MP-0 h7
I (350196) ovms-server-v2: Incoming Msg: MP-0 h8
I (350206) ovms-server-v2: Incoming Msg: MP-0 h9
I (350206) ovms-server-v2: Incoming Msg: MP-0 h10
I (350216) webserver: HTTP POST /api/execute
I (350226) webcommand: HttpCommandStream[0x3fff55d4]: 35288 bytes free, executing: simcom status
I (350386) ovms-server-v2: Incoming Msg: MP-0 h11
I (350386) ovms-server-v2: Incoming Msg: MP-0 h12
I (350386) ovms-server-v2: Incoming Msg: MP-0 h13
I (350386) ovms-server-v2: Incoming Msg: MP-0 h14
I (350396) ovms-server-v2: Incoming Msg: MP-0 h15
I (355736) webserver: HTTP POST /api/execute
I (355736) webcommand: HttpCommandStream[0x3fff5fd0]: 37948 bytes free, executing: simcom status
I (357846) simcom: CREG Network Registration: RegisteredRoaming
I (358826) simcom: State: Enter NetStart state
I (359166) webserver: HTTP POST /api/execute
I (359176) webcommand: HttpCommandStream[0x3fff5fd0]: 37892 bytes free, executing: simcom status
I (359846) simcom: PPP Connection is ready to start
I (360826) simcom: State: Enter NetMode state
I (360826) gsm-ppp: Initialising...
I (361026) webserver: HTTP POST /api/execute
I (361036) webcommand: HttpCommandStream[0x3fff5fd0]: 37448 bytes free, executing: simcom status
I (363566) gsm-ppp: StatusCallBack: None
I (363566) gsm-ppp: status_cb: Connected
I (363566) gsm-ppp:    our_ipaddr  = 10.170.195.13
I (363566) gsm-ppp:    his_ipaddr  = 10.64.64.64
I (363566) gsm-ppp:    netmask     = 255.255.255.255
I (363566) gsm-ppp:    our6_ipaddr = ::
I (363576) netmanager: Interface priority is st3 (192.168.2.109/255.255.255.0 gateway 192.168.2.1)
I (363576) netmanager: Set DNS#0 192.168.2.1
I (363576) netmanager: Set DNS#1 192.168.2.1
I (363576) netmanager: Set DNS#2 0.0.0.0
I (363576) netmanager: MODEM up (with WIFI client up): staying with WIFI client priority
I (363916) webserver: HTTP POST /api/execute
I (363926) webcommand: HttpCommandStream[0x3fff5fd0]: 37828 bytes free, executing: simcom status
I (368726) webserver: HTTP POST /api/execute
I (368726) webcommand: HttpCommandStream[0x3fff5fd0]: 37508 bytes free, executing: simcom status

… (click "Keep & proceed") …

I (371186) webserver: HTTP POST /cfg/init
I (371186) webserver: CfgInit enter 5.test.start
I (371316) webserver: CfgInitSetStep: step done timeout 0
I (371336) webserver: CfgInit next: done


Regards,
Michael



Am 12.05.2018 um 20:18 schrieb Michael Balzer:
>
> Am 12.05.2018 um 18:21 schrieb Mark Webb-Johnson:
>>> Did you apply the sdkconfig changes regarding SO_REUSE? I had none such problems after fixing that in my sdkconfig -- I also fixed the defaults in some
>>> commit a few days before.
>>>
>>> CONFIG_LWIP_SO_REUSE=y
>>> CONFIG_LWIP_SO_REUSE_RXTOALL=y
>>
>> Just double-checked, and yes they are there.
>>
>> It seems that after connecting to SSID, the attempt to run ‘Ota status’ is immediate, but the wifi client hasn’t settled down yet. I’ve looked in
>> web_cfg_init, but having trouble working out how it works. In the 'if (step == "2.test.connect”)’, it just seems to try to MyOTA.GetStatus as soon as the
>> ssid matches? But it doesn’t check that the wifi client is actually up (the reception of IP address may be a second or two after the SSID is connected, and
>> anyway GetSSID() just returns the configured SSID, not the connected one). Or, maybe I’m missing something?
>
> The state ticker does not check yet if it can abort a scheduled timeout. So it doesn't do the test as soon as GetSSID() returns the network.
>
> The test is done fixed 20 seconds after StartAccessPointClientMode(). That is normally plenty of time for everything to settle. In my runs, the client network
> was normally fully functional in ~10 seconds.
>
> How long does your APClient switch take? You can try raising the 20 second timeout in line 226.
>
> Regards,
> Michael
>
>
>> Regards, Mark
>>
>>> On 12 May 2018, at 11:14 PM, Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> wrote:
>>>
>>>
>>> Am 12.05.2018 um 15:42 schrieb Mark Webb-Johnson:
>>>>
>>>> Works better, but still causing me issues. I had a couple of times where it took down the whole housekeeping task (with red alerts saying event delivery
>>>> queue was full so ticker.1 messages couldn’t be delivered). I guess it is doing the wifi connectivity test in the main event task?
>>>
>>> Yes, the most time consuming task in there is the OTA.GetStatus() fetching the server version info. But I didn't get any problems from that in all my tests…
>>>
>>>> The other problem is that the bringing up/down of the APCLIENT vs AP mode doesn’t seem to work properly, so I lose connection to the station. Also, my iPad
>>>> keeps switching back to home wifi, every time the OVMS reconfigures the network. APCLIENT mode really sucks.
>>>
>>> Did you apply the sdkconfig changes regarding SO_REUSE? I had none such problems after fixing that in my sdkconfig -- I also fixed the defaults in some
>>> commit a few days before.
>>>
>>> CONFIG_LWIP_SO_REUSE=y
>>> CONFIG_LWIP_SO_REUSE_RXTOALL=y
>>>
>>> If these are missing, both the webserver and ssh cannot rebind after the switch from AP to APCLIENT.
>>>
>>> The switching takes some seconds, but my tablets (all Androids) only switched back to my home network during tests with issues. The normal process is fast
>>> enough to keep them on the AP.
>>>
>>> Regards,
>>> Michael
>>>
>>>
>>>> I’ll have another look at the wifi driver. Maybe I can improve the API a bit (based on what we have). Perhaps configure a STAtion even in AP mode (which is
>>>> what I did with my alternative approach before).
>>>>
>>>> Regards, Mark.
>>>>
>>>>> On 12 May 2018, at 12:52 AM, Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> wrote:
>>>>>
>>>>> Added another fix.
>>>>>
>>>>> Or more sort of a workaround: I just had an empty server status display on step 4 test after successful connect. I'm not sure how this can happen, I guess
>>>>> it's due to five events being processed at once after the connect (server v2 blocks the mongoose task there) and some race condition in the javascript
>>>>> code in that case.
>>>>>
>>>>> The three event based status displays now again also do periodic updates every 5 seconds, so if this happens, the status gets updated again after 5 seconds.
>>>>>
>>>>> Regards,
>>>>> Michael
>>>>>
>>>>>
>>>>> Am 11.05.2018 um 18:19 schrieb Michael Balzer:
>>>>>> OK. I really should wait for config.mounted before reading from MyConfig.
>>>>>>
>>>>>> Fix is pushed, please try.
>>>>>>
>>>>>>
>>>>>> Am 11.05.2018 um 17:49 schrieb Mark Webb-Johnson:
>>>>>>> I tried a restart. Here is what I get:
>>>>>>>
>>>>>>>     Firmware: 3.1.005-72-g8cd4d07/ota_0/main
>>>>>>>     Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1
>>>>>>>
>>>>>>>     I (1465) webserver: Launching Web Server
>>>>>>>     I (1465) ssh: Launching SSH Server
>>>>>>>     I (4185) wifi: ap channel adjust o:1,1 n:6,2
>>>>>>>     I (4185) wifi: n:6 0, o:1 0, ap:6 2, sta:6 0, prof:1
>>>>>>>     I (4945) wifi: state: init -> auth (b0)
>>>>>>>     I (4945) wifi: state: auth -> assoc (0)
>>>>>>>     I (4955) wifi: state: assoc -> run (10)
>>>>>>>     I (5055) wifi: connected with HIGHWAYS, channel 6
>>>>>>>     I (5375) sdcard: SD CARD has been inserted
>>>>>>>     I (5465) sdcard: mount done
>>>>>>>     I (6025) wpa: PTK has been installed, it may be an attack, ignor it.
>>>>>>>     I (6025) wpa: GTK has been installed, it may be an attack, ignor it.
>>>>>>>     I (8515) wifi: n:6 0, o:6 0, ap:6 2, sta:6 0, prof:6
>>>>>>>     I (8515) wifi: station: cc:44:63:89:b2:f4 join, AID=1, g, 20
>>>>>>>     I (8525) esp32wifi: AP station connected: id: 1, MAC: cc:44:63:89:b2:f4
>>>>>>>     I (9455) event: sta ip: 10.10.41.203, mask: 255.255.248.0, gw: 10.10.40.64
>>>>>>>     I (9455) netmanager: Interface priority is st1 (10.10.41.203/255.255.248.0 gateway 10.10.40.64)
>>>>>>>     I (9455) netmanager: Set DNS#0 10.10.40.64
>>>>>>>     I (9455) netmanager: Set DNS#1 0.0.0.0
>>>>>>>     I (9455) netmanager: Set DNS#2 0.0.0.0
>>>>>>>     I (9455) netmanager: WIFI client up (with MODEM down): starting network with WIFI client
>>>>>>>     I (9455) esp32wifi: STA got IP with SSID: HIGHWAYS, MAC: 30:ae:a4:43:92:c4, IP: 10.10.41.203, mask: 255.255.248.0, gw: 10.10.40.64
>>>>>>>     I (9455) time: Starting SNTP client
>>>>>>>     I (10375) housekeeping: System considered stable (RAM: 8b=106112-106940 32b=23608)
>>>>>>>     I (13565) webserver: HTTP GET /
>>>>>>>     I (13575) webserver: HTTP GET /cfg/init
>>>>>>>     I (14825) webserver: HTTP GET /
>>>>>>>     I (15135) webserver: HTTP GET /cfg/init
>>>>>>>     I (15375) simcom: State timeout, transition to 13
>>>>>>>     I (15375) simcom: State: Enter PoweredOff state
>>>>>>>     I (15375) gsm-mux: Stop MUX
>>>>>>>     I (16695) webserver: HTTP GET /
>>>>>>>     I (16705) webserver: HTTP GET /cfg/init
>>>>>>>     I (16735) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>     I (16905) webserver: HTTP GET /assets/style.css
>>>>>>>     I (16905) webserver: HTTP GET /assets/script.js
>>>>>>>     I (17345) webserver: HTTP GET /cfg/init
>>>>>>>     I (28045) webserver: HTTP POST /cfg/init
>>>>>>>     I (28045) webserver: HandleLogin: 'admin' logged in, sid 98faaa06ed8f1574
>>>>>>>     I (28085) webserver: HTTP GET /cfg/init
>>>>>>>     I (28085) webserver: CfgInit enter 2.test.connect
>>>>>>>     I (28085) webserver: HTTP GET /menu
>>>>>>>     I (40025) webserver: HTTP GET /
>>>>>>>     I (40035) webserver: HTTP GET /cfg/init
>>>>>>>     I (40035) webserver: CfgInit enter 2.test.connect
>>>>>>>     I (40045) webserver: HTTP GET /
>>>>>>>     I (40075) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>     I (40085) webserver: HTTP GET /assets/style.css
>>>>>>>     I (40185) webserver: HTTP GET /assets/script.js
>>>>>>>     I (40355) webserver: HTTP GET /cfg/init
>>>>>>>     I (40355) webserver: CfgInit enter 2.test.connect
>>>>>>>     OVMS> enable
>>>>>>>     Password:
>>>>>>>     Secure mode
>>>>>>>
>>>>>>>     I (50425) webserver: HTTP GET /
>>>>>>>     I (50425) webserver: HTTP GET /cfg/init
>>>>>>>     I (50425) webserver: CfgInit enter 2.test.connect
>>>>>>>     I (50465) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>     I (50475) webserver: HTTP GET /assets/style.css
>>>>>>>     I (50555) webserver: HTTP GET /assets/script.js
>>>>>>>     I (50675) webserver: HTTP GET /cfg/init
>>>>>>>     I (50675) webserver: CfgInit enter 2.test.connect
>>>>>>>     OVMS# ota status
>>>>>>>     Running partition: ota_0
>>>>>>>     Boot partition:    ota_0
>>>>>>>     Firmware:          3.1.005-72-g8cd4d07/ota_0/main (build idf v3.1-dev-454-gdaef4b5c May 11 2018 20:00:05)
>>>>>>>     Server Available:  3.1.005
>>>>>>>
>>>>>>>     OTA release providing minor improvements and fixes.
>>>>>>>
>>>>>>>     - Vehicle: 12V battery monitoring
>>>>>>>         vehicle [12v.alert] = 1.6       Voltage drop alert threshold in V vs. reference
>>>>>>>     - OTA: automatic daily firmware updates (wifi only)
>>>>>>>         auto [ota] = yes                Enable/disable
>>>>>>>         ota [auto.hour] = 2             Hour for daily check
>>>>>>>     - Logging: persistent configuration, file cycling, web config UI:
>>>>>>>         log [file.enable] = no          Enable/disable file logging
>>>>>>>         log [file.maxsize] = 1024       Max log file size in kB, 0 = no cycling
>>>>>>>         log [file.path] = ""            Log path, if on /sd watches sd.mounted
>>>>>>>         log [level]                     Default level
>>>>>>>         log [level.<tag>]               Component levels
>>>>>>>     - Reverse Engineering Tools enhancements
>>>>>>>     - Tesla Roadster CAC support
>>>>>>>     - Miscellaneous bug fixes and enhancements
>>>>>>>
>>>>>>>     I (61705) webserver: HTTP GET /
>>>>>>>     I (61715) webserver: HTTP GET /cfg/init
>>>>>>>     I (61715) webserver: CfgInit enter 2.test.connect
>>>>>>>     I (61745) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>     I (61755) webserver: HTTP GET /assets/style.css
>>>>>>>     I (61845) webserver: HTTP GET /assets/script.js
>>>>>>>     I (61965) webserver: HTTP GET /cfg/init
>>>>>>>     I (61965) webserver: CfgInit enter 2.test.connect
>>>>>>>     I (72035) webserver: HTTP GET /
>>>>>>>     I (72045) webserver: HTTP GET /cfg/init
>>>>>>>     I (72045) webserver: CfgInit enter 2.test.connect
>>>>>>>     I (72085) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>     I (72095) webserver: HTTP GET /assets/style.css
>>>>>>>     I (72175) webserver: HTTP GET /assets/script.js
>>>>>>>     I (73485) webserver: HTTP GET /cfg/init
>>>>>>>     I (73495) webserver: CfgInit enter 2.test.connect
>>>>>>>
>>>>>>>     OVMS# config list auto
>>>>>>>     auto (readable writeable)
>>>>>>>       wifi.mode: apclient
>>>>>>>       wifi.ssid.ap: DEVBENCH
>>>>>>>       wifi.ssid.client: HIGHWAYS
>>>>>>>
>>>>>>>     OVMS# config list module
>>>>>>>     module (readable writeable)
>>>>>>>       init: 2.test.connect
>>>>>>>
>>>>>>>
>>>>>>> Regards, Mark
>>>>>>>
>>>>>>>> On 11 May 2018, at 10:42 PM, Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> wrote:
>>>>>>>>
>>>>>>>> Do you have the earlier log, especially of the CfgInit ticker messages?
>>>>>>>>
>>>>>>>> Is the auto config correct and matching the "HIGHWAY" network?
>>>>>>>>
>>>>>>>> Please try a reboot. The ticker should take on step "2.test.connect" and proceed.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Am 11.05.2018 um 16:28 schrieb Mark Webb-Johnson:
>>>>>>>>> Trying the new web setup, but not getting very far…
>>>>>>>>>
>>>>>>>>>     I (503580) webserver: HTTP GET /
>>>>>>>>>     I (503590) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (503590) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (503610) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>>>     I (503610) webserver: HTTP GET /assets/style.css
>>>>>>>>>     I (503730) webserver: HTTP GET /assets/script.js
>>>>>>>>>     I (503880) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (503880) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (513960) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (513960) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (513960) webserver: HTTP GET /
>>>>>>>>>     I (514000) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>>>     I (514000) webserver: HTTP GET /assets/style.css
>>>>>>>>>     I (514090) webserver: HTTP GET /assets/script.js
>>>>>>>>>     I (514220) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (514220) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (524280) webserver: HTTP GET /
>>>>>>>>>     I (524290) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (524290) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (524320) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>>>     I (524340) webserver: HTTP GET /assets/style.css
>>>>>>>>>     I (524420) webserver: HTTP GET /assets/script.js
>>>>>>>>>     I (524590) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (524590) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (534620) webserver: HTTP GET /
>>>>>>>>>     I (534630) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (534630) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (534660) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>>>     I (534660) webserver: HTTP GET /assets/style.css
>>>>>>>>>     I (534760) webserver: HTTP GET /assets/script.js
>>>>>>>>>     I (534890) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (534890) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (544940) webserver: HTTP GET /
>>>>>>>>>     I (544950) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (544950) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (544980) webserver: HTTP GET /assets/style.css
>>>>>>>>>     I (544990) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>>>     I (545080) webserver: HTTP GET /assets/script.js
>>>>>>>>>     I (545250) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (545250) webserver: CfgInit enter 2.test.connect
>>>>>>>>>
>>>>>>>>>     OVMS# wifi status
>>>>>>>>>     WiFi
>>>>>>>>>       Power: on
>>>>>>>>>       Mode: Access-Point + Client mode
>>>>>>>>>
>>>>>>>>>       STA SSID: HIGHWAYS
>>>>>>>>>         MAC: 30:ae:a4:43:92:c4
>>>>>>>>>         IP: 10.10.41.203/255.255.248.0
>>>>>>>>>         GW: 10.10.40.64
>>>>>>>>>
>>>>>>>>>       AP SSID: DEVBENCH
>>>>>>>>>         MAC: 30:ae:a4:43:92:c5
>>>>>>>>>         IP: 192.168.4.1
>>>>>>>>>         AP Stations: 1
>>>>>>>>>           1: MAC: cc:44:63:89:b2:f4, IP: 192.168.4.2
>>>>>>>>>
>>>>>>>>>     OVMS# ota status
>>>>>>>>>     Running partition: ota_0
>>>>>>>>>     Boot partition:    ota_0
>>>>>>>>>     Firmware:          3.1.005-72-g8cd4d07/ota_0/main (build idf v3.1-dev-454-gdaef4b5c May 11 2018 20:00:05)
>>>>>>>>>     Server Available:  3.1.005
>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>     I (1141850) webserver: HTTP GET /
>>>>>>>>>     I (1141860) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (1141860) webserver: CfgInit enter 2.test.connect
>>>>>>>>>     I (1141890) webserver: HTTP GET /apple-touch-icon.png
>>>>>>>>>     I (1141890) webserver: HTTP GET /assets/style.css
>>>>>>>>>     I (1141990) webserver: HTTP GET /assets/script.js
>>>>>>>>>     I (1142120) webserver: HTTP GET /cfg/init
>>>>>>>>>     I (1142120) webserver: CfgInit enter 2.test.connect
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Can’t get out of that 2.test.connect.
>>>>>>>>>
>>>>>>>>> Any ideas?
>>>>>>>>>
>>>>>>>>> Regards, Mark.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> OvmsDev mailing list
>>>>>>>>> OvmsDev at lists.openvehicles.com
>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> OvmsDev mailing list
>>>>>>> OvmsDev at lists.openvehicles.com
>>>>>>> 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
>>>>>
>>>>> -- 
>>>>> 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
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.openvehicles.com
>>>> 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
>>
>>
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com
>> 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

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180512/0bf65109/attachment.htm>


More information about the OvmsDev mailing list