[Ovmsdev] MDNS crash

Mark Webb-Johnson mark at webb-johnson.net
Thu Mar 22 09:50:13 HKT 2018


And for posterity, I found the root cause:

https://github.com/espressif/esp-idf/issues/1696 <https://github.com/espressif/esp-idf/issues/1696>

mdns_free() calls function _mdns_service_task_stop()

mdns_free() --> _mdns_service_task_stop() {
MDNS_SERVICE_LOCK() --> Step 1
Post ACTION_TASK_STOP to task and wait on this while loop
while (_mdns_service_task_handle) {
vTaskDelay(10 / portTICK_PERIOD_MS);
}

MDNS_SERVICE_UNLOCK();
}

on _mdns_service_task() {

Wait on queue messages() --> Step 2
if(action == ACTION_TASK_STOP)
{
break; //exit the task
}
MDNS_SERVICE_LOCK(); --> Step 3
_mdns_execute_action(a);
MDNS_SERVICE_UNLOCK();

}

If Step 1 happens and on Step2 if there are other actions pending on queue mdns task will be stuck at Step3

This can be easily reproduced if mdns_service_remove_all() is called just before mdns_free(). (happens 1 in 10 times)

Deadlock in MDNS mdns_free() function call. Reportedly 1 in 10 times, but that would be sufficient.

We’ve worked around it now, anyway, by not calling mdns_free() any more ;-)

Regards, Mark.

> On 19 Mar 2018, at 10:34 PM, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
> 
> And MDNS is back.
> 
> I looked through the source code and found a mdns_handle_system_event() call that is used to pass all the system events through to MDNS. That then dynamically adds/removed wifi STA and AP interfaces as they come up/down. No need to init and free the mdns system the whole time. Went back to the documentation, and found it right at the bottom… Good grief.
> 
> Anyway, I migrated the code to use that. Now, MDNS starts at boot time and stays up all the time. Seems reliable to me, so I committed it.
> 
> Regards, Mark
> 
>> On 19 Mar 2018, at 12:57 PM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>> 
>> There seems to be something going on internally in lwip regarding this. It is such a dumb implementation anyway, with a separate task and static initialisation of the interface list at the time of startup; really not ideal for a dynamically changing environment. It would be much more sensible to just have a timer and every N seconds iterate through the current interface list to send out MDNS broadcasts on each active one that is suitable for MDNS (wifi only, really).
>> 
>> I think safest for the moment to just disable MDNS. I’ve done that now, and it is running live. That seems to be pretty good for me. Can you see if that works better for you?
>> 
>> I’m still seeing some issues with ssh/telnet startup that I’m looking at now.
>> 
>> Given where we are, I’m going to tell China that we need another 48 hours to confirm the firmware, before I send to them. That buys us some time to get this as stable as we can.
>> 
>> Regards, Mark.
>> 
>>> On 19 Mar 2018, at 12:27 PM, Greg D. <gregd2350 at gmail.com <mailto:gregd2350 at gmail.com>> wrote:
>>> 
>>> 
>>> Stephen Casner wrote:
>>>> Greg, the async console is a separate task that should be able to look
>>>> at some things as long as they don't depend upon the networking tasks
>>>> or objects.  Is it hung also?
>>>> 
>>> Async console?  So, not USB.  Don't have a connection for that.
>>> 
>>> So, tried it again...    Note that the wifi connection gets dropped in the middle, but I didn't turn off the hotspot!
>>> 
>>> Network status, however, says that it's still connected.  That's wrong.
>>> 
>>> Stop the server, then start, and this time instead of a hang I get a crash.
>>> 
>>> Greg
>>> 
>>> 
>>> Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console
>>> OVMS> 
>>> OVMS> 
>>> OVMS> 
>>> I (4185) wifi: n:1 1, o:1 0, ap:1 1, sta:1 0, prof:1
>>> I (4835) wifi: state: init -> auth (b0)
>>> I (4845) wifi: state: auth -> assoc (0)
>>> I (4855) wifi: state: assoc -> run (10)
>>> I (4875) wifi: connected with gregnet3, channel 1
>>> I (4985) simcom: State: Enter PoweredOn state
>>> I (5915) event: sta ip: 192.168.43.49, mask: 255.255.255.0, gw: 192.168.43.1
>>> I (5915) netmanager: Set DNS#0 9.9.9.9
>>> I (5915) netmanager: Set DNS#1 8.8.8.8
>>> I (5915) netmanager: Interface priority is st1 (192.168.43.49/255.255.255.0 <http://192.168.43.49/255.255.255.0> gateway 192.168.43.1)
>>> I (5915) time: Starting SNTP client
>>> I (5925) ovms-server-v2: Network is up, so attempt network connection
>>> I (5925) ovms-server-v2: Connection is tmc.openvehicles.com:6867 <http://tmc.openvehicles.com:6867/> ROADSTER_834/Gdbkt2017server
>>> I (5925) ovms-server-v2: Status: Connecting...
>>> I (5935) ovms-mdns: Stopped MDNS service
>>> I (5935) ovms-mdns: Started MDNS service
>>> I (5955) esp32wifi: WiFi UP with SSID: gregnet3, MAC: 30:ae:a4:37:1b:64, IP: 192.168.43.49, mask: 255.255.255.0, gw: 192.168.43.1
>>> I (6395) ovms-server-v2: Connection successful
>>> I (6395) ovms-server-v2: Status: Logging in...
>>> I (6395) ovms-server-v2: Sending server login: MP-C 0 gDAm8Tas7ISVuhmQ8zGDfh hygW8au7zuXDV5qkWYvMIA== ROADSTER_834
>>> I (6635) ovms-server-v2: Got server response: MP-S 0 ubeiHXgCpUtGX1f6XRXlQK BB2JuaR9oc8TL6Ame7qkEg==
>>> I (6645) ovms-server-v2: Server token is ubeiHXgCpUtGX1f6XRXlQK and digest is BB2JuaR9oc8TL6Ame7qkEg==
>>> I (6645) ovms-server-v2: Status: Server auth ok. Now priming crypto.
>>> I (6645) ovms-server-v2: Shared secret key is ubeiHXgCpUtGX1f6XRXlQKgDAm8Tas7ISVuhmQ8zGDfh (44 bytes)
>>> I (6645) ovms-server-v2: Status: OVMS V2 login successful, and crypto channel established
>>> I (6655) ovms-server-v2: Incoming Msg: MP-0 Z0
>>> I (7445) ovms-server-v2: Send MP-0 S0,K,0,0,stopped,standard,0,0,0,0,0,0,0,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 (7445) ovms-server-v2: Send MP-0 D0,0,5,0,0,0,0,0,0,7,0,0,0,0,0.269231,0,0,0,0,0
>>> I (7445) ovms-server-v2: Send MP-0 L0,0,0,0,0,0,0,0,0,0,0
>>> I (7445) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0
>>> I (7445) ovms-server-v2: Send MP-0 F3.0.991-87-g60cd970/factory/main build (idf v3.1-dev-429-g7f6161cd) Mar 18 2018 20:29:03,,0,1,TR,gregnet3
>>> I (12625) housekeeping: System considered stable (free: 37872 bytes)
>>> I (22225) ovms-server-v2: Incoming Msg: MP-0 Z1
>>> I (22225) ovms-server-v2: One or more peers have connected
>>> I (22445) ovms-server-v2: Send MP-0 S0,K,0,0,stopped,standard,0,0,0,0,0,0,0,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 (22445) ovms-server-v2: Send MP-0 D0,0,5,0,0,0,0,0,0,22,0,0,0,0,0.351648,0,0,0,0,0
>>> I (22445) ovms-server-v2: Send MP-0 L0,0,0,0,0,0,0,0,0,0,0
>>> I (22445) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0
>>> I (22445) ovms-server-v2: Send MP-0 F3.0.991-87-g60cd970/factory/main build (idf v3.1-dev-429-g7f6161cd) Mar 18 2018 20:29:03,,9,1,TR,gregnet3
>>> I (24475) simcom: State: Enter MuxStart state
>>> I (24475) gsm-mux: Start MUX
>>> I (24485) gsm-mux: Channel #0 is open
>>> I (24495) gsm-mux: Channel #1 is open
>>> I (24505) gsm-mux: Channel #2 is open
>>> I (24515) gsm-mux: Channel #3 is open
>>> I (24525) gsm-mux: Channel #4 is open
>>> I (25445) simcom: State: Enter NetWait state
>>> I (25745) ovms-server-v2: Incoming Msg: MP-0 Z0
>>> OVMS> metric set v.b.soc 44
>>> Metric set
>>> I (35485) simcom: CREG Network Registration: RegisteredRoaming
>>> I (36445) simcom: State: Enter NetStart state
>>> I (37585) simcom: PPP Connection is ready to start
>>> I (38445) simcom: State: Enter NetMode state
>>> I (38445) gsm-ppp: Initialising...
>>> I (40145) ovms-server-v2: Incoming Msg: MP-0 Z1
>>> I (40145) ovms-server-v2: One or more peers have connected
>>> I (40445) ovms-server-v2: Send MP-0 S44.0,K,0,0,stopped,standard,0,0,0,0,0,0,0,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 (40445) ovms-server-v2: Send MP-0 D0,0,5,0,0,0,0,0,0,40,0,0,0,0,0.28022,0,0,0,0,0
>>> I (40445) ovms-server-v2: Send MP-0 L0,0,0,0,0,0,0,0,0,0,0
>>> I (40445) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0
>>> I (40445) ovms-server-v2: Send MP-0 F3.0.991-87-g60cd970/factory/main build (idf v3.1-dev-429-g7f6161cd) Mar 18 2018 20:29:03,,9,1,TR,T-Mobile Hologram
>>> E (40645) ovms-server-v2: Status: Error: Disconnected from OVMS Server V2
>>> I (41895) gsm-ppp: StatusCallBack: None
>>> I (41895) gsm-ppp: status_cb: Connected
>>> I (41895) gsm-ppp:    our_ipaddr  = 10.170.146.142
>>> I (41895) gsm-ppp:    his_ipaddr  = 10.64.64.64
>>> I (41895) gsm-ppp:    netmask     = 255.255.255.255
>>> I (41895) gsm-ppp:    our6_ipaddr = ::
>>> I (41895) netmanager: Set DNS#0 9.9.9.9
>>> I (41895) netmanager: Set DNS#1 8.8.8.8
>>> I (41895) netmanager: Interface priority is st1 (192.168.43.49/255.255.255.0 <http://192.168.43.49/255.255.255.0> gateway 192.168.43.1)
>>> I (41895) time: Starting SNTP client
>>> I (41895) ovms-server-v2: Network is up, so attempt network connection
>>> I (41895) ovms-server-v2: Connection is tmc.openvehicles.com:6867 <http://tmc.openvehicles.com:6867/> ROADSTER_834/Gdbkt2017server
>>> I (41895) ovms-server-v2: Status: Connecting...
>>> I (60445) ovms-server-v2: Connection is tmc.openvehicles.com:6867 <http://tmc.openvehicles.com:6867/> ROADSTER_834/Gdbkt2017server
>>> I (60445) ovms-server-v2: Status: Connecting...
>>> I (62565) wifi: bcn_timout,ap_probe_send_start
>>> I (65065) wifi: ap_probe_send over, resett wifi status to disassoc
>>> I (65065) wifi: state: run -> init (1)
>>> I (65065) wifi: n:1 0, o:1 1, ap:1 1, sta:1 0, prof:1
>>> OVMS> 
>>> OVMS> 
>>> OVMS> 
>>> OVMS> 
>>> OVMS> 
>>> OVMS> 
>>> OVMS> 
>>> OVMS> 
>>> OVMS> 
>>> OVMS> server v2 status
>>> Connecting...
>>> OVMS> network   
>>> Interface#3: pp3 (ifup=1 linkup=1)
>>>   IPv4: 10.170.146.142/255.255.255.255 <http://10.170.146.142/255.255.255.255> gateway 10.64.64.64
>>> 
>>> Interface#2: ap2 (ifup=1 linkup=1)
>>>   IPv4: 192.168.4.1/255.255.255.0 <http://192.168.4.1/255.255.255.0> gateway 192.168.4.1
>>> 
>>> Interface#1: st1 (ifup=1 linkup=1)
>>>   IPv4: 192.168.43.49/255.255.255.0 <http://192.168.43.49/255.255.255.0> gateway 192.168.43.1
>>> 
>>> Interface#0: lo0 (ifup=1 linkup=1)
>>>   IPv4: 127.0.0.1/255.0.0.0 <http://127.0.0.1/255.0.0.0> gateway 127.0.0.1
>>> 
>>> DNS: 9.9.9.9 8.8.8.8
>>> 
>>> Default Interface: st1 (192.168.43.49/255.255.255.0 <http://192.168.43.49/255.255.255.0> gateway 192.168.43.1)
>>> OVMS> simcom
>>> SIMCOM
>>>   Network Registration: RegisteredRoaming
>>>   State: NetMode
>>>   Ticker: 22
>>>   User Data: 0
>>> 
>>>   Mux
>>>     Status: up
>>>     Open Channels: 4
>>>     Framing Errors: 0
>>>     Last RX frame: 19 sec(s) ago
>>>     RX frames: 18
>>>     TX frames: 18
>>> 
>>>   PPP
>>>     Connected on channel: #2
>>>     Last Error: None
>>> 
>>>   GPS
>>>     Status: disabled
>>>     Time: disabled
>>>     NMEA: GPS/GLONASS Not Connected
>>> OVMS> wifi
>>> WiFi
>>>   Power: on
>>>   Mode: Access-Point + Client mode
>>> 
>>>   STA SSID: gregnet3
>>>     MAC: 30:ae:a4:37:1b:64
>>>     IP: 192.168.43.49/255.255.255.0 <http://192.168.43.49/255.255.255.0>
>>>     GW: 192.168.43.1
>>> 
>>>   AP SSID: ovms
>>>     MAC: 30:ae:a4:37:1b:65
>>>     IP: 192.168.4.1
>>>     AP Stations: 0
>>> OVMS> server v2 stop
>>> Stopping OVMS Server V2 connection (oscv2)
>>> OVMS> server v2 status
>>> OVMS v2 server has not been started
>>> OVMS> server v2 start
>>> Launching OVMS Server V2 connection (oscv2)
>>> Guru Meditation Error: Core  1 panic'ed (LoadProhibited)
>>> . Exception was unhandled.
>>> Core 1 register dump:
>>> PC      : 0x400ee17d  PS      : 0x00060630  A0      : 0x800ef642  A1      : 0x3fff5020  
>>> A2      : 0xffffffff  A3      : 0x3fff2540  A4      : 0x00000000  A5      : 0x3fff5100  
>>> A6      : 0x3fff50e0  A7      : 0x0000000c  A8      : 0x800ee179  A9      : 0x3fff4ff0  
>>> A10     : 0xffffffff  A11     : 0x3f411528  A12     : 0x3fff5100  A13     : 0x3fff50e0  
>>> A14     : 0x0000000c  A15     : 0x3fff1ea4  SAR     : 0x00000004  EXCCAUSE: 0x0000001c  
>>> EXCVADDR: 0x00000000  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xffffffff  
>>> 
>>> Backtrace: 0x400ee17d:0x3fff5020 0x400ef63f:0x3fff5060 0x400f04c5:0x3fff50a0 0x40082c71:0x3fff50d0 0x40115696:0x3fff5120 0x401161ef:0x3fff5140 0x40116a7d:0x3fff5330 0x40116aa5:0x3fff5960 0x400eeeb2:0x3fff5980 0x400eefa9:0x3fff59b0 0x400eef9b:0x3fff59e0 0x400eef9b:0x3fff5a10 0x400eefd1:0x3fff5a40 0x400e534c:0x3fff5a60 0x400f1809:0x3fff5a80 0x400f1870:0x3fff5ae0 0x400e537b:0x3fff5b20 0x401eb64f:0x3fff5b40 0x400f0575:0x3fff5b60 0x400ebf8d:0x3fff5b90 0x400ec179:0x3fff5bc0 0x400f0421:0x3fff5be0 0x400f0430:0x3fff5c00 0x400e3295:0x3fff5c20
>>> 
>>> Rebooting...
>>> ets Jun  8 2016 00:22:57
>>> 
>>> rst:0xc (SW_CPU_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT)
>>> configsip: 156795334, SPIWP:0xee
>>> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
>>> mode:DIO, clock div:2
>>> load:0x3fff0018,len:4
>>> load:0x3fff001c,len:4560
>>> ho 0 tail 12 room 4
>>> load:0x40078000,len:0
>>> load:0x40078000,len:13176
>>> entry 0x40078d38
>>> I (647) cpu_start: Pro cpu up.
>>> I (647) cpu_start: Starting app cpu, entry point is 0x40081300
>>> I (632) cpu_start: App cpu up.
>>> I (651) heap_init: Initializing. RAM available for dynamic allocation:
>>> I (657) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
>>> I (664) heap_init: At 3FFBBAC0 len 00024540 (145 KiB): DRAM
>>> I (670) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
>>> I (676) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
>>> I (684) heap_init: At 40091FDC len 0000E024 (56 KiB): IRAM
>>> I (689) cpu_start: Pro cpu start user code
>>> I (35) ovms_main: Set default logging level for * to INFO
>>> I (35) command: Initialising COMMAND (1000)
>>> I (36) boot: Initialising BOOT (1100)
>>> I (40) boot: Boot #1 reasons for CPU0=12 and CPU1=12
>>> E (46) boot: Crash #1 detected
>>> I (49) events: Initialising EVENTS (1200)
>>> I (54) config: Initialising CONFIG (1400)
>>> I (59) time: Initialising TIME (1500)
>>> I (64) script: Initialising SCRIPTS (1600)
>>> I (68) script: Using DUKTAPE javascript engine
>>> I (74) metrics: Initialising METRICS (1810)
>>> I (78) metrics:   OvmsMetric is 28 bytes
>>> I (82) metrics:   OvmsMetricBool is 32 bytes
>>> I (87) metrics: Expanding DUKTAPE javascript engine
>>> I (97) notify: Initialising NOTIFICATIONS (1820)
>>> I (99) notify: Registered notification type info
>>> I (103) notify: Registered notification type error
>>> I (109) notify: Registered notification type alert
>>> I (114) notify: Registered notification type data
>>> I (120) location: Initialising LOCATIONS (1900)
>>> I (126) location: Expanding DUKTAPE javascript engine
>>> I (131) vehicle: Initialising VEHICLE Factory (2000)
>>> I (137) pcp: Initialising POWER (4000)
>>> I (141) max7317: Initialising MAX7317 EGPIO (4200)
>>> I (146) sdcard: Initialising SD CARD (4400)
>>> I (151) ota: Initialising OTA (4400)
>>> I (156) can: Initialising CAN (4500)
>>> I (161) simcom: Initialising SIMCOM (4600)
>>> I (165) test: Initialising TEST (5000)
>>> I (169) ovms-module: Initialising MODULE (5100)
>>> I (174) vfs: Initialising VFS (5200)
>>> I (179) ovms-server: Initialising OVMS Server (6000)
>>> I (184) ovms-server-v2: Initialising OVMS V2 Server (6100)
>>> I (190) ovms-server-v3: Initialising OVMS V3 Server (6200)
>>> I (196) obd2ecu: Initialising OBD2ECU (7000)
>>> I (202) canopen: Initialising CANopen (7000)
>>> I (207) esp32wifi: Initialising ESP32WIFI (8000)
>>> I (212) ovms-mdns: Initialising MDNS (8100)
>>> I (217) webserver: Initialising WEBSERVER (8200)
>>> I (223) telnet: Initialising Telnet (8300)
>>> I (227) ssh: Initialising SSH (8300)
>>> I (231) re: Initialising RE Tools (8800)
>>> I (236) netmanager: Initialising NETMANAGER (8999)
>>> I (242) v-track: Registering Vehicle: TRACK (9000)
>>> I (246) v-teslaroadster: Registering Vehicle: Tesla Roadster (9000)
>>> I (253) v-teslamodels: Registering Vehicle: Tesla Model S (9000)
>>> I (260) v-obdii: Registering Vehicle: OBDII (9000)
>>> I (265) v-none: Registering Vehicle: NONE (9000)
>>> I (271) v-demo: Registering Vehicle: DEMO (9000)
>>> I (276) version: Initialising Versioning (9900)
>>> I (285) cpu_start: Starting scheduler on PRO CPU.
>>> I (0) cpu_start: Starting scheduler on APP CPU.
>>> I (331) ovms_main: Executing on CPU core 0
>>> I (331) ovms_main: Mounting CONFIG...
>>> W (381) webserver: UpdateGlobalAuthFile: no password set => no auth for web console
>>> I (391) ovms_main: Registering default configs...
>>> I (391) ovms_main: Starting HOUSEKEEPING...
>>> I (391) housekeeping: Initialising HOUSEKEEPING Framework...
>>> I (451) housekeeping: Executing on CPU core 1
>>> I (451) housekeeping: reset_reason: cpu0=12, cpu1=12
>>> I (451) housekeeping: Starting PERIPHERALS...
>>> I (461) peripherals: Initialising OVMS Peripherals...
>>> I (461) peripherals:   TCP/IP Adaptor
>>> I (471) peripherals:   ESP32 system
>>> I (471) peripherals:   SPI bus
>>> I (471) peripherals:   MAX7317 I/O Expander
>>> I (481) peripherals:   ESP32 CAN
>>> I (481) peripherals:   ESP32 WIFI
>>> I (491) peripherals:   ESP32 BLUETOOTH
>>> I (491) peripherals:   ESP32 ADC
>>> I (491) peripherals:   MCP2515 CAN 1/2
>>> I (511) peripherals:   MCP2515 CAN 2/2
>>> I (521) peripherals:   SD CARD
>>> I (521) peripherals:   SIMCOM MODEM
>>> I (521) gpio: GPIO[16]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 
>>> I (531) gpio: GPIO[17]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 
>>> I (541) uart: queue free spaces: 10
>>> I (541) ext12v: Powering off external 12V devices
>>> I (551) housekeeping: Auto init ext12v (free: 112436 bytes)
>>> I (551) ext12v: Powering on external 12V devices
>>> I (561) housekeeping: Auto init wifi (free: 112436 bytes)
>>> I (561) wifi: wifi firmware version: ebd3e5d
>>> I (571) wifi: config NVS flash: enabled
>>> I (571) wifi: config nano formating: disabled
>>> I (571) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
>>> I (581) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
>>> I (601) wifi: Init dynamic tx buffer num: 16
>>> I (601) wifi: Init data frame dynamic rx buffer num: 16
>>> I (601) wifi: Init management frame dynamic rx buffer num: 16
>>> I (601) wifi: wifi driver task: 3ffe61dc, prio:23, stack:4096
>>> I (611) wifi: Init static rx buffer num: 4
>>> I (611) wifi: Init dynamic rx buffer num: 16
>>> I (611) wifi: wifi power manager task: 0x3ffe8974 prio: 21 stack: 2560
>>> I (1331) phy: phy_version: 383.0, 79a622c, Jan 30 2018, 15:38:06, 0, 0
>>> I (1331) wifi: mode : sta (30:ae:a4:37:1b:64) + softAP (30:ae:a4:37:1b:65)
>>> I (1341) housekeeping: Auto init modem (free: 90292 bytes)
>>> I (1351) simcom: State: Enter PoweringOn state
>>> I (1351) simcom: Power Cycle
>>> I (1351) ovms-mdns: Started MDNS service
>>> I (1381) webserver: Launching Web Server
>>> I (1381) esp32wifi: AP started with SSID: ovms, MAC: 30:ae:a4:37:1b:65, IP: 192.168.4.1
>>> I (1461) simcom: State: Enter PoweredOn state
>>> I (2351) housekeeping: Auto init vehicle (free: 75064 bytes)
>>> I (2351) v-teslaroadster: Tesla Roadster v1.x, v2.x and v3.0 vehicle module
>>> I (2361) housekeeping: Auto init obd2ecu (free: 69332 bytes)
>>> I (2561) housekeeping: Auto init server v2 (free: 60676 bytes)
>>> I (2561) ovms-server-v2: OVMS Server V2 registered metric modifier is #1
>>> I (2571) ovms-server-v2: Status: Starting
>>> I (2571) ovms-server-v2: OVMS Server v2 running
>>> I (2581) housekeeping: Auto init server v3 (free: 56364 bytes)
>>> I (2581) housekeeping: Auto init done (free: 56364 bytes)
>>> I (2591) housekeeping: Starting USB console...
>>> I (2591) uart: queue free spaces: 30
>>> I (2601) version: Set version
>>> 
>>> Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
>> 
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180322/6942b2e0/attachment.htm>


More information about the OvmsDev mailing list