December 2017 - OvmsDev - Open Vehicles

Nissan Leaf 2016 Remote Climate Control
by Tom Parker 24 Dec '17

24 Dec '17

Hi, I got remote climate control working on my 2016 Nissan Leaf with OVMS v3. In the 2016 model year Nissan moved the TCU from the EV CAN bus to the Car CAN bus and they change the remote climate control messages slightly. The Leaf - OBDII cables that were sold with OVMS v2 were future proofed and when used with the OVMS v3 have the EV bus wired to m_can1 and the CAR bus to m_can2. Mark mentioned this a while back and I'm happy to confirm that it works. A "standard" OBDII cable only exposes the CAR bus. Sending the right message to the m_can2 bus with a Leaf cable starts up the climate control. I must thank Mitchell on My Nissan Leaf for providing the updated can frame, see http://www.mynissanleaf.com/viewtopic.php?t=24053#p496393 I haven't worked out how to turn remote climate control off and I haven't tested remote charge start yet. This certainty encourages me to look at the cellular situation -- we've got a bit of a heat wave going on in NZ at the moment. When I last tried the cellular data, it worked moderately well for a day or so and then stopped because it had used all of the free 1MB allocation for the month on the Hologram SIM. I see less than 1MB per month using the OVMS v2 on a local carrier. I haven't looked at whether the v3 data usage was caused by excessive communications with the server, Hologram counting data differently to what I'm used to, or the v3 code reconnecting to the cellular network often. Nearly at feature parity with v2!

3 14

Modem LED control?
by Greg D. 21 Dec '17

21 Dec '17

Hi folks, The "real" module's case is black, but how well does it block light? I'm thinking about the modem's LED, which flashes pretty brightly in the proto (white) case. In a dark parking lot, it could attract unwanted attention. (Or, perhaps simulate a car alarm, which wouldn't necessarily be bad...) If the LED is visible externally, is there a way to disable it? Greg

3 3

Android App 3.12.2 beta
by Michael Balzer 18 Dec '17

18 Dec '17

Beta build of the next Android App release: https://dexters-web.de/f/tw-beta/OpenVehicleApp-debug-3.12.2.apk This supports the new float values sent by the new V2 server (hopefully got them all) so can again be used to connect to a V3 module. Float displays are not yet optimized but should do for now. Please note the Intent extras also have changed from int to float accordingly, so you may need to update your listeners. I'll prepare a new set of Automagic examples later on. There are also some optimizations regarding the ApiService stability and the layout, and some fixes. Please send me a logcat if you encounter crashes. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

2 4

MMI/USSD commands
by Michael Balzer 18 Dec '17

18 Dec '17

…done & pushed: _hologram:_ OVMS > level debug simcom Logging level for simcom set to debug I (141948) ovms-server-v2: Incoming Msg: MP-0 C41,*100# D (141948) simcom: tx mcmd ch=4 len=22 : AT+CUSD=1,"*100#",15|| I (141948) ovms-server-v2: Send MP-0 c41,0 D (141968) simcom: rx line ch=4 len=2 : OK D (143758) simcom: rx line ch=3 len=15 : +CUSD: 0,"IMSI: D (143758) simcom: rx line ch=3 len=19 : 234507098581638",15 D (143758) simcom: rx line ch=4 len=15 : +CUSD: 0,"IMSI: D (143758) simcom: rx line ch=4 len=35 : +CUSD: 0,"IMSI:|234507098581638",15 I (143758) simcom: USSD received: IMSI:|234507098581638 I (143758) events: Signal(system.modem.received.ussd) I (143758) ovms-server-v2: Send MP-0 c41,0,IMSI:|234507098581638 _congstar (Telekom Germany):_ I (66394) ovms-server-v2: Incoming Msg: MP-0 C41,*100# D (66394) simcom: tx mcmd ch=4 len=22 : AT+CUSD=1,"*100#",15|| I (66394) ovms-server-v2: Send MP-0 c41,0 D (66454) simcom: rx line ch=4 len=2 : OK D (68444) simcom: rx line ch=3 len=44 : +CUSD: 0," Aktuelles Guthaben: 8.29 EUR.",15 D (68444) simcom: rx line ch=4 len=44 : +CUSD: 0," Aktuelles Guthaben: 8.29 EUR.",15 I (68454) simcom: USSD received: Aktuelles Guthaben: 8.29 EUR. I (68454) events: Signal(system.modem.received.ussd) I (68454) ovms-server-v2: Send MP-0 c41,0, Aktuelles Guthaben: 8.29 EUR. "*100#" is the account balance check on prepaid SIMs by congstar. I haven't found any list of USSD commands supported by hologram. "*100#" obviously returns the current IMSI id. I tested some commands for JT global, but without success. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0

GitHub - igrr/libnmea-esp32: ESP-IDF component for libnmea, NMEA parser
by Mark Webb-Johnson 17 Dec '17

17 Dec '17

Not sure if this is any use for us, but it is out there now: https://github.com/igrr/libnmea-esp32

1 0

Some Bugs
by Tom Parker 17 Dec '17

17 Dec '17

Hi all, Master doesn't compile with the default sdkconfig when you answer no to all the questions: /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_ota.cpp: In member function 'void OvmsOTA::AutoFlashSD(std::__cxx11::string, void*)': /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_ota.cpp:432:18: error: 'class Peripherals' has no member named 'm_sdcard' If you add in CONFIG_OVMS_COMP_SDCARD=y then it compiles. There is a buffer overflow in the v2 command handling because we call strncpy with the length of the string not the (larger) length of the receiving buffer and so the null terminator is not copied. Later we read beyond the copied buffer because there is no null terminator. This often crashes the android client as it's not expecting junk data after the reply. The following encryption code doesn't include the null terminator either but I think that might be ok? I've sent a pull request to fix the strncpy. I've found the SIMCOM modem is very unstable when connected to my laptop via an unpowered USB hub. I see under-voltage warnings so I wonder if there isn't enough power? It seems stable when connected directly to my laptop. When it the modem reboots, the esp32 crashes too. I'm not sure if this is because it also ran out of power or because it is sad the network went away: (77496) SIMCOM ppp rx: 4b e5 0a aa c7 0f 1a d3 90 1f 26 03 4c 1c 00 00 K.........&.L... D (77506) SIMCOM ppp rx: 19 ac 50 18 39 08 05 3c 00 00 6d 2f 47 45 71 44 ..P.9..<..m/GEqD D (77506) SIMCOM ppp rx: 78 41 78 51 3d 3d 0d 0a d6 17 7e xAxQ==....~ I (77536) ovms-server-v2: Incoming Msg: MP-0 Z2 I (77536) ovms-server-v2: One or more peers have connected I (77536) 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 (77546) ovms-server-v2: Send MP-0 D64,0,5,0,0,0,0,0,0,77,0,0,0,0,0.967033,0,0,0,0,0 I (77556) ovms-server-v2: Send MP-0 L0,0,0,0,0,0,0,0,0,0,0 I (77566) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0 I (77576) ovms-server-v2: Send MP-0 F3.0.0/factory/main build (idf v2.1-20-g88ab5d4) Dec 16 2017 09:23:50,,12,1,NL,VodafoneNZ Hologram D (77936) SIMCOM rx: f9 0d ff 4b 0d 0a 55 4e 44 45 52 2d 56 4f 4c 54 ...K..UNDER-VOLT D (77936) SIMCOM rx: 41 47 45 20 57 41 52 4e 4e 49 4e 47 20 50 4f 57 AGE WARNNING POW D (77946) SIMCOM rx: 45 52 20 44 4f 57 4e 0d 0a 9b f9 f9 11 ff 4b 0d ER DOWN.......K. D (77946) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff, FCS=9b, LEN=43) D (77946) gsm-mux: ChanProcessFrame(CHAN=3, ADDR=0d, CTRL=ff, LEN=40, IFP=3) D (77946) SIMCOM line: 55 4e 44 45 52 2d 56 4f 4c 54 41 47 45 20 57 41 UNDER-VOLTAGE WA D (77946) SIMCOM line: 52 4e 4e 49 4e 47 20 50 4f 57 45 52 20 44 4f 57 RNNING POWER DOW D (77946) SIMCOM line: 4e N D (77946) SIMCOM rx: 0a 55 4e 44 45 52 2d 56 4f 4c 54 41 47 45 20 57 .UNDER-VOLTAGE W D (77946) SIMCOM rx: 41 52 4e 4e 49 4e 47 20 50 4f 57 45 52 20 44 4f ARNNING POWER DO D (77946) SIMCOM rx: 57 4e 0d 0a 96 f9 f9 0d ff 45 0d 0a 73 74 61 72 WN.......E..star D (77946) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff, FCS=96, LEN=43) D (77946) gsm-mux: ChanProcessFrame(CHAN=4, ADDR=11, CTRL=ff, LEN=40, IFP=3) D (77946) SIMCOM line: 55 4e 44 45 52 2d 56 4f 4c 54 41 47 45 20 57 41 UNDER-VOLTAGE WA D (77946) SIMCOM line: 52 4e 4e 49 4e 47 20 50 4f 57 45 52 20 44 4f 57 RNNING POWER DOW D (77946) SIMCOM line: 4e N D (77946) SIMCOM rx: 74 69 6e 67 20 70 6f 77 65 72 20 6f 66 66 20 74 ting power off t D (77946) SIMCOM rx: 68 65 20 6d 6f 64 75 6c 65 21 0d 0a 71 f9 f9 11 he module!..q... D (77946) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff, FCS=71, LEN=40) D (77946) gsm-mux: ChanProcessFrame(CHAN=3, ADDR=0d, CTRL=ff, LEN=37, IFP=3) D (77946) SIMCOM line: 73 74 61 72 74 69 6e 67 20 70 6f 77 65 72 20 6f starting power o D (77946) SIMCOM line: 66 66 20 74 68 65 20 6d 6f 64 75 6c 65 21 ff the module! D (77946) SIMCOM rx: ff 45 0d 0a 73 74 61 72 74 69 6e 67 20 70 6f 77 .E..starting pow D (77946) SIMCOM rx: 65 72 20 6f 66 66 20 74 68 65 20 6d 6f 64 75 6c er off the modul D (77946) SIMCOM rx: 65 21 0d 0a 7c f9 e!..|. D (77946) gsm-mux: ProcessFrame(CHAN=4, ADDR=11, CTRL=ff, FCS=7c, LEN=40) D (77946) gsm-mux: ChanProcessFrame(CHAN=4, ADDR=11, CTRL=ff, LEN=37, IFP=3) D (77946) SIMCOM line: 73 74 61 72 74 69 6e 67 20 70 6f 77 65 72 20 6f starting power o D (77946) SIMCOM line: 66 66 20 74 68 65 20 6d 6f 64 75 6c 65 21 ff the module! D (78216) SIMCOM ppp tx: 7e ff 03 80 57 01 01 00 0e 01 0a 85 b9 57 2f be ~...W........W/. D (78216) SIMCOM ppp tx: 63 a0 85 80 17 7e c....~ D (78216) SIMCOM tx: f9 09 ff 2d 7e ff 03 80 57 01 01 00 0e 01 0a 85 ...-~...W....... D (78216) SIMCOM tx: b9 57 2f be 63 a0 85 80 17 7e f5 f9 .W/.c....~.. D (78566) SIMCOM rx: f9 09 ff cb 7e 21 45 00 00 60 92 81 40 00 2d 06 ....~!E..`..@.-. D (78566) SIMCOM rx: e0 ed bc 8a 4b e5 0a aa c7 0f 1a d3 90 1f 26 03 ....K.........&. D (78566) SIMCOM rx: 4b e4 00 00 19 ac 50 18 39 08 79 ae 00 00 4d 50 K.....P.9.y...MP D (78576) SIMCOM rx: 2d 53 20 30 20 6a 79 30 32 65 51 6b 7a 55 52 4d -S 0 jy02eQkzURM D (78576) SIMCOM rx: 70 73 49 41 36 56 59 48 6e 39 59 20 58 72 5a 6b psIA6VYHn9Y XrZk D (78576) SIMCOM rx: 64 71 48 7a 54 38 6a 77 74 44 47 46 66 6a 52 73 dqHzT8jwtDGFfjRs D (78576) SIMCOM rx: 79 77 3d 3d 0d 0a 58 bf 7e b9 f9 yw==..X.~.. D (78576) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=b9, LEN=107) D (78576) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=104, IFP=3) D (78576) SIMCOM ppp rx: 7e 21 45 00 00 60 92 81 40 00 2d 06 e0 ed bc 8a ~!E..`..@.-..... D (78576) SIMCOM ppp rx: 4b e5 0a aa c7 0f 1a d3 90 1f 26 03 4b e4 00 00 K.........&.K... D (78586) SIMCOM ppp rx: 19 ac 50 18 39 08 79 ae 00 00 4d 50 2d 53 20 30 ..P.9.y...MP-S 0 D (78586) SIMCOM ppp rx: 20 6a 79 30 32 65 51 6b 7a 55 52 4d 70 73 49 41 jy02eQkzURMpsIA D (78586) SIMCOM ppp rx: 36 56 59 48 6e 39 59 20 58 72 5a 6b 64 71 48 7a 6VYHn9Y XrZkdqHz D (78586) SIMCOM ppp rx: 54 38 6a 77 74 44 47 46 66 6a 52 73 79 77 3d 3d T8jwtDGFfjRsyw== D (78596) SIMCOM ppp rx: 0d 0a 58 bf 7e ..X.~ D (78596) SIMCOM ppp tx: 7e 21 45 00 00 28 00 08 00 00 ff 06 e1 9e 0a aa ~!E..(.......... D (78596) SIMCOM ppp tx: c7 0f bc 8a 4b e5 90 1f 1a d3 00 00 1a 32 26 03 ....K........2&. D (78596) SIMCOM ppp tx: 4c 2a 50 10 16 8a 87 cf 00 00 22 59 7e L*P......."Y~ D (78596) SIMCOM tx: f9 09 ff 5b 7e 21 45 00 00 28 00 08 00 00 ff 06 ...[~!E..(...... D (78596) SIMCOM tx: e1 9e 0a aa c7 0f bc 8a 4b e5 90 1f 1a d3 00 00 ........K....... D (78596) SIMCOM tx: 1a 32 26 03 4c 2a 50 10 16 8a 87 cf 00 00 22 59 .2&.L*P......."Y D (78596) SIMCOM tx: 7e 45 f9 ~E. D (78986) SIMCOM rx: f9 09 ff 23 7e ff 7d 23 c0 21 7d 25 7d 23 7d 20 ...#~.}#.!}%}#} D (78986) SIMCOM rx: 7d 24 85 72 7e 1f f9 f9 0d ff 2f 0d 0a 2b 50 50 }$.r~...../..+PP D (78986) gsm-mux: ProGuru Meditation Error of type LoadProhibited occurred on core 1. Exception was unhandled. Register dump: PC : 0x4017fd75 PS : 0x00060b30 A0 : 0x8017fdb6 A1 : 0x3ffcf030 0x4017fd75: ip4_route at /home/ubuntu/esp/esp-idf/components/lwip/core/ipv4/ip4.c:250 (discriminator 2) A2 : 0x0000f01d A3 : 0x00000000 A4 : 0x3ffeb04c A5 : 0x3f429a88 A6 : 0x00000008 A7 : 0x3ffcf258 A8 : 0x8017fd69 A9 : 0x3ffcf010 A10 : 0x00000000 A11 : 0x00000000 A12 : 0x3ffdcd3c A13 : 0x3ffcf240 A14 : 0x00000004 A15 : 0xab9423a7 SAR : 0x00000018 EXCCAUSE: 0x0000001c EXCVADDR: 0x0000f0d2 LBEG : 0x4000c349 LEND : 0x4000c36b LCOUNT : 0x00000000 Backtrace: 0x4017fd75:0x3ffcf030 0x4017fdb3:0x3ffcf050 0x4017dfa2:0x3ffcf070 0x40178617:0x3ffcf0b0 0x40178639:0x3ffcf0e0 0x401786da:0x3ffcf100 0x40178b38:0x3ffcf120 0x4017c272:0x3ffcf140 0x4017c2b3:0x3ffcf160 0x40184cdd:0x3ffcf180 0x401850a1:0x3ffcf1a0 0x401850e8:0x3ffcf1c0 0x401894f9:0x3ffcf1e0 0x40184fd8:0x3ffcf200 0x4018c9ce:0x3ffcf220 0x4018ca0a:0x3ffcf240 0x401880dd:0x3ffcf260 0x40189b19:0x3ffcf280 0x40189bc4:0x3ffcf2a0 0x40187eff:0x3ffcf2c0 0x40184b05:0x3ffcf2e0 0x401a2be8:0x3ffcf310 0x401a2d35:0x3ffcf330 0x401731c9:0x3ffcf350 0x4017fd75: ip4_route at /home/ubuntu/esp/esp-idf/components/lwip/core/ipv4/ip4.c:250 (discriminator 2) 0x4017fdb3: ip4_route_src at /home/ubuntu/esp/esp-idf/components/lwip/core/ipv4/ip4.c:159 0x4017dfa2: tcp_rst at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp_out.c:1336 (discriminator 4) 0x40178617: tcp_abandon at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1630 0x40178639: tcp_abort at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1630 0x401786da: tcp_netif_ipv4_addr_changed_pcblist at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1630 0x40178b38: tcp_netif_ipv4_addr_changed at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1947 0x4017c272: netif_set_ipaddr at /home/ubuntu/esp/esp-idf/components/lwip/core/netif.c:452 0x4017c2b3: netif_set_addr at /home/ubuntu/esp/esp-idf/components/lwip/core/netif.c:330 0x40184cdd: cifaddr at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ppp.c:704 0x401850a1: ipcp_clear_addrs at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ipcp.c:2192 0x401850e8: ipcp_down at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ipcp.c:2156 0x401894f9: fsm_lowerdown at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/fsm.c:146 0x40184fd8: ipcp_lowerdown at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ipcp.c:687 0x4018c9ce: upper_layers_down at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/auth.c:715 0x4018ca0a: link_down at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/auth.c:701 0x401880dd: lcp_down at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/lcp.c:2341 0x40189b19: fsm_rtermreq at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/fsm.c:597 0x40189bc4: fsm_input at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/fsm.c:369 0x40187eff: lcp_input at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/lcp.c:513 0x40184b05: ppp_input at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ppp.c:704 0x401a2be8: pppos_input at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/pppos.c:578 0x401a2d35: pppos_input_sys at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/pppos.c:460 (discriminator 3) 0x401731c9: tcpip_thread at /home/ubuntu/esp/esp-idf/components/lwip/api/tcpip.c:474 Rebooting... ets Jun 8 2016 00:22:57

4 3

Instability on GSM
by Tom Parker 17 Dec '17

17 Dec '17

Hi, I let my ovms run on GSM for a while and it's not very stable. I'm not sure if wifi is better or worse but here's a log starting from a reboot with the button, connecting, disconnecting and crashing. My esp-idf looks up to date: commit 88ab5d4830e2eeb24fbae1d5f7d66a2e33bdbde0 Author: Stephen Casner <casner(a)acm.org> Date: Sun Oct 22 00:25:10 2017 -0700 Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console I (605) simcom: State: Enter PoweringOn state I (605) simcom: Power Cycle D (1485) SIMCOM tx: 41 54 0d 0a AT.. D (1495) SIMCOM rx: 41 54 0d AT. I (1495) simcom: State: Enter PoweredOn state D (1495) SIMCOM rx: 0d 0a 4f 4b 0d 0a ..OK.. D (1505) SIMCOM line: 4f 4b OK Launching OVMS Server V2 connection (oscv2) Logging level for * set to debug Power mode of simcom is now on OVMS > level info Logging level for * set to info I (11485) simcom: State timeout, transition to 2 I (11485) simcom: State: Enter PoweringOn state I (11485) simcom: Power Cycle I (17475) simcom: State: Enter PoweredOn state I (36485) simcom: State: Enter MuxStart state I (36485) gsm-mux: Start MUX I (36495) gsm-mux: Channel #0 is open I (36505) gsm-mux: Channel #1 is open I (36505) gsm-mux: Channel #2 is open I (36515) gsm-mux: Channel #3 is open I (36515) gsm-mux: Channel #4 is open I (37485) simcom: State: Enter NetWait state I (47525) simcom: CREG Network Registration: RegisteredRoaming I (48485) simcom: State: Enter NetStart state I (49555) simcom: PPP Connection is ready to start I (50485) simcom: State: Enter NetMode state I (50485) gsm-ppp: Initialising... I (77405) gsm-ppp: StatusCallBack: None I (77405) gsm-ppp: status_cb: Connected I (77405) gsm-ppp: our_ipaddr = 10.170.199.15 I (77405) gsm-ppp: his_ipaddr = 10.64.64.64 I (77405) gsm-ppp: netmask = 255.255.255.255 I (77405) gsm-ppp: our6_ipaddr = :: I (80505) ovms-server-v2: Status: Network connectivity established I (80505) ovms-server-v2: Connection is redacted I (81905) ovms-server-v2: Connected to OVMS Server V2 at ovms.dexters-web.de I (81905) ovms-server-v2: Status: Connected to server I (81905) ovms-server-v2: Status: Logging in... I (81905) ovms-server-v2: Sending server login: MP-C 0 redacted I (101915) ovms-server-v2: Server response is incomplete (0 bytes) E (101915) ovms-server-v2: Status: Error: Server response is incomplete I (107445) simcom: CREG Network Registration: Searching I (107485) simcom: Lost network connection (NetworkRegistration in NetMode) I (107485) simcom: State: Enter NetLoss staGuru Meditation Error of type LoadProhibited occurred on core 0. Exception was unhandled. Register dump: PC : 0x40180151 PS : 0x00060830 A0 : 0x80180192 A1 : 0x3ffcf080 0x40180151: ip4_route at /home/ubuntu/esp/esp-idf/components/lwip/core/ipv4/ip4.c:250 (discriminator 2) A2 : 0x0000f01d A3 : 0x00000000 A4 : 0x3ffeae94 A5 : 0x3f429c7c A6 : 0x3ffd18c0 A7 : 0x00000000 A8 : 0x80180145 A9 : 0x3ffcf060 A10 : 0x00000000 A11 : 0x00000000 A12 : 0x3ffdcd3c A13 : 0x3ffc09a0 A14 : 0x00000003 A15 : 0x00060023 SAR : 0x00000010 EXCCAUSE: 0x0000001c EXCVADDR: 0x0000f0d2 LBEG : 0x4000c2e0 LEND : 0x4000c2f6 LCOUNT : 0xffffffff Backtrace: 0x40180151:0x3ffcf080 0x4018018f:0x3ffcf0a0 0x4017e37e:0x3ffcf0c0 0x401789f3:0x3ffcf100 0x40178a15:0x3ffcf130 0x40178ab6:0x3ffcf150 0x40178f14:0x3ffcf170 0x4017c64e:0x3ffcf190 0x4017c68f:0x3ffcf1b0 0x401850b9:0x3ffcf1d0 0x4018547d:0x3ffcf1f0 0x401854c4:0x3ffcf210 0x401898d5:0x3ffcf230 0x401853b4:0x3ffcf250 0x4018cdaa:0x3ffcf270 0x4018cde6:0x3ffcf290 0x401884b9:0x3ffcf2b0 0x401898d5:0x3ffcf2d0 0x401893fc:0x3ffcf2f0 0x40184fa1:0x3ffcf310 0x401a2aac:0x3ffcf330 0x40173589:0x3ffcf350 0x40180151: ip4_route at /home/ubuntu/esp/esp-idf/components/lwip/core/ipv4/ip4.c:250 (discriminator 2) 0x4018018f: ip4_route_src at /home/ubuntu/esp/esp-idf/components/lwip/core/ipv4/ip4.c:159 0x4017e37e: tcp_rst at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp_out.c:1336 (discriminator 4) 0x401789f3: tcp_abandon at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1630 0x40178a15: tcp_abort at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1630 0x40178ab6: tcp_netif_ipv4_addr_changed_pcblist at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1630 0x40178f14: tcp_netif_ipv4_addr_changed at /home/ubuntu/esp/esp-idf/components/lwip/core/tcp.c:1947 0x4017c64e: netif_set_ipaddr at /home/ubuntu/esp/esp-idf/components/lwip/core/netif.c:452 0x4017c68f: netif_set_addr at /home/ubuntu/esp/esp-idf/components/lwip/core/netif.c:330 0x401850b9: cifaddr at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ppp.c:704 0x4018547d: ipcp_clear_addrs at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ipcp.c:2192 0x401854c4: ipcp_down at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ipcp.c:2156 0x401898d5: fsm_lowerdown at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/fsm.c:146 0x401853b4: ipcp_lowerdown at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ipcp.c:687 0x4018cdaa: upper_layers_down at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/auth.c:715 0x4018cde6: link_down at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/auth.c:701 0x401884b9: lcp_down at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/lcp.c:2341 0x401898d5: fsm_lowerdown at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/fsm.c:146 0x401893fc: lcp_lowerdown at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/lcp.c:485 0x40184fa1: ppp_close at /home/ubuntu/esp/esp-idf/components/lwip/netif/ppp/ppp.c:704 0x401a2aac: pppapi_do_ppp_close at /home/ubuntu/esp/esp-idf/components/lwip/api/pppapi.c:355 0x40173589: tcpip_thread at /home/ubuntu/esp/esp-idf/components/lwip/api/tcpip.c:474 Rebooting... ets Jun 8 2016 00:22:57 rst:0xc (SW_CPU_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT) configsip: 156795334, SPIWP:0x00 clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0008,len:8 load:0x3fff0010,len:4392 load:0x40078000,len:11080 load:0x40080000,len:252 0x40080000: _WindowOverflow4 at ??:? entry 0x40080034 0x40080034: _WindowOverflow4 at ??:? I (46) boot: ESP-IDF v2.1-20-g88ab5d4 2nd stage bootloader I (46) boot: compile time 11:13:21 I (79) boot: Enabling RNG early entropy source...

2 1

Hidden WiFi SSID connection?
by Greg D. 17 Dec '17

17 Dec '17

4 10

Network Manager Ideas
by Mark Webb-Johnson 13 Dec '17

13 Dec '17

I’ve had lwip pppos (via SIMCOM) running on my desk overnight, and it seems stable. Of course, we’ll need to do some fine tuning based on feedback in the field, but at least PPP connections can be brought up and down cleanly, and that is the base capability needed for more sophistication to be built on top. The OVMS v2 client code also seems good. With DEMO car, it is not producing too much data, and seems roughly comparable to v2 usage. For example, here is the start of one of my recent sessions (log level info): I (17600) simcom: State: Enter PoweringOn state I (17600) simcom: Power Cycle I (23660) simcom: State: Enter PoweredOn state I (42770) simcom: State: Enter MuxStart state I (42770) gsm-mux: Start MUX I (42780) gsm-mux: Channel #0 is open I (42780) gsm-mux: Channel #1 is open I (42790) gsm-mux: Channel #2 is open I (42800) gsm-mux: Channel #3 is open I (42810) gsm-mux: Channel #4 is open I (43750) simcom: State: Enter NetWait state I (53830) simcom: CREG Network Registration: RegisteredRoaming I (54750) simcom: State: Enter NetStart state I (55890) simcom: PPP Connection is ready to start I (56750) simcom: State: Enter NetMode state I (56750) gsm-ppp: Initialising... I (59770) gsm-ppp: StatusCallBack: None I (59770) gsm-ppp: status_cb: Connected I (59770) gsm-ppp: our_ipaddr = 10.52.223.8 I (59770) gsm-ppp: his_ipaddr = 10.64.64.64 I (59770) gsm-ppp: netmask = 255.255.255.255 I (59770) gsm-ppp: our6_ipaddr = :: I (62570) ovms-server-v2: Status: Network connectivity established I (62570) ovms-server-v2: Connection is api.openvehicles.com:6867 TESTCAR/... I (63430) ovms-server-v2: Connected to OVMS Server V2 at api.openvehicles.com I (63430) ovms-server-v2: Status: Connected to server I (63440) ovms-server-v2: Status: Logging in... I (63440) ovms-server-v2: Sending server login: MP-C 0 ... ... TESTCAR I (64030) ovms-server-v2: Received welcome response MP-S 0 ... ... I (64030) ovms-server-v2: Got server response: MP-S 0 ... ... I (64040) ovms-server-v2: Server token is ... and digest is ... I (64040) ovms-server-v2: Status: Server auth ok. Now priming crypto. I (64040) ovms-server-v2: Shared secret key is .../... (44 bytes) I (64040) ovms-server-v2: Status: OVMS V2 login successful, and crypto channel established I (64040) ovms-server-v2: Status: Connected and logged in I (64050) ovms-server-v2: Send MP-0 S50,K,0,0,done,standard,200,160,0,0,0,0,13,4,0,0,0,0,160.00,0,0,0,0,-1,0,0,0,0,0,400,0,0.00,400.00,100 I (64050) ovms-server-v2: Send MP-0 D0,0,5,22,30,25,0,1000000,0,61,22,0,0,0,0,0,0,0,22,0 I (64060) ovms-server-v2: Send MP-0 L22.280869,114.160599,10,30,1,0,0,0,0.0,0,0 I (64070) ovms-server-v2: Send MP-0 W30,33,40,34,30,33,40,34,0 I (64080) ovms-server-v2: Send MP-0 F3.0.0/factory/main build (idf v2.1.1-8-g5ae2c0d0) Dec 12 2017 07:55:27,DEMODEMODEMO,9,1,DEMO,CMHK Jsy Tel I (64100) ovms-server-v2: Incoming Msg: MP-0 Z0 I (665100) ovms-server-v2: Send MP-0 S50,K,0,0,done,standard,200,160,0,0,0,0,13,4,0,0,0,0,160.00,0,0,0,0,-1,0,0,0,0,0,400,0,0.00,400.00,100 I (665110) ovms-server-v2: Send MP-0 D0,0,5,22,30,25,0,1000000,0,662,22,0,0,0,0,0,0,0,22,0 I (665120) ovms-server-v2: Send MP-0 F3.0.0/factory/main build (idf v2.1.1-8-g5ae2c0d0) Dec 12 2017 07:55:27,DEMODEMODEMO,7,1,DEMO,CMHK Jsy Tel OVMS > server v2 status Connected and logged in I (1266130) ovms-server-v2: Send MP-0 S50,K,0,0,done,standard,200,160,0,0,0,0,13,4,0,0,0,0,160.00,0,0,0,0,-1,0,0,0,0,0,400,0,0.00,400.00,100 I (1266140) ovms-server-v2: Send MP-0 D0,0,5,22,30,25,0,1000000,0,1263,22,0,0,0,0,0,0,0,22,0 I (1266150) ovms-server-v2: Send MP-0 F3.0.0/factory/main build (idf v2.1.1-8-g5ae2c0d0) Dec 12 2017 07:55:27,DEMODEMODEMO,8,1,DEMO,CMHK Jsy Tel OVMS > charge start Charge has been started I (1744160) ovms-server-v2: Send MP-0 S50,K,220,32,charging,standard,200,160,0,0,0,0,3,1,0,0,0,0,160.00,0,0,0,0,-1,0,0,0,0,0,400,0,-0.00,400.00,100 I (1744170) ovms-server-v2: Send MP-0 D28,0,5,22,30,25,0,1000000,0,1741,22,0,0,0,0,0,0,0,22,0 I (1867180) ovms-server-v2: Send MP-0 S51,K,220,32,charging,standard,200,160,0,2,0,0,3,1,0,0,0,0,160.00,0,0,0,0,-1,0,0,0,0,0,400,0,-0.00,400.00,100 I (1867190) ovms-server-v2: Send MP-0 D28,0,5,22,30,25,0,1000000,0,1864,22,0,0,0,0,0,0,0,22,0 I (2468200) ovms-server-v2: Send MP-0 S57,K,220,32,charging,standard,200,160,0,12,0,0,3,1,0,0,0,0,160.00,0,0,0,0,-1,0,0,0,0,0,400,0,-0.00,400.00,100 I (2468210) ovms-server-v2: Send MP-0 D28,0,5,22,30,25,0,1000000,0,2465,22,0,0,0,0,0,0,0,22,0 I (3069220) ovms-server-v2: Send MP-0 S63,K,220,32,charging,standard,200,160,0,22,0,0,3,1,0,0,0,0,160.00,0,0,0,0,-1,0,0,0,0,0,400,0,-0.00,400.00,100 I (3069230) ovms-server-v2: Send MP-0 D28,0,5,22,30,25,0,1000000,0,3066,22,0,0,0,0,0,0,0,22,0 I (3670240) ovms-server-v2: Send MP-0 S69,K,220,32,charging,standard,200,160,0,32,0,0,3,1,0,0,0,0,160.00,0,0,0,0,-1,0,0,0,0,0,400,0,-0.00,400.00,100 I (3670250) ovms-server-v2: Send MP-0 D28,0,5,22,30,25,0,1000000,0,3667,22,0,0,0,0,0,0,0,22,0 That is one set of messages every 10 minutes (the numbers in brackets after the “I” seem to be millisecond timestamps). So, now to think about how to manage this in general. To make it easier for the end user. Here are some notes/thoughts: We continue to use events and scripting for fine-tuned control. For configuration, we offer options to set values and have those automatically actioned at startup. Examples: If a vehicle type is configured, then automatically start a vehicle module of that type. If a v2 configuration is present, then automatically start a ovms server v2 connection. For networking, we have the network manager component. The idea here is to extend that to provide network link logic. Examples: If wifi comes up, then sleep the simcom modem If wifi goes down, then wake up the simcom modem The above configuration settings can be simply mapped to v2 protocol features/parameters. While Config parameters are currently registered and visible (MyConfig.RegisterParam), instances are not. That makes it tricky to see what config instances are available. In some of the code, we document the instances as comments after the parameter is registered. My suggestion here is to add a MyConfig.RegisterInstance to allow for instance registration (with a default value). If the instance does not exist, then it would be created with the value set as per the default. That would then make it visible to the user. The only downside to this is that the default value can’t later be changed. What do people think? Does that make sense as an approach? Implementation should not be difficult. Regards, Mark.

3 14

Emacs
by Mark Webb-Johnson 13 Dec '17

13 Dec '17

Working with Steve and Greg, we’ve got a very minimal emacs style editor running in the latest code just committed. It is based on the openemacs project (which is based on another project called kilo). Both attempt to get an editor into 1024 lines (ours is 1458; but we put braces on lines of their own). As a side-requirement of this, Steve has now implemented a way for executing commands to switch into a mode where they can get raw keyboard input. That is useful for several other things (other than WYSIWYG editors). Command is: vfs edit <filepath> A few caveats: I haven’t implemented search yet. It should come at some stage. Log messages currently screw up the screen. @Steve will try to work out a way to suppress/discard these during input feedback mode. In the meantime, Control-L (screen refresh) is your friend. Control-X Control-S doesn’t work on the async console. I think something is swallowing the Control-S. But Control-X S/s works just fine. Control-X Control-C sometimes crashes the ssh console. I get "Bad packet length 3324299854” and then all goes to hell. Telnet behaves very well, and seems to support both Control-S and Control-C properly. CR/LF handling seems wrong. Behaves strangely when pasting. It is pretty slow to paste characters. OK for writing/changing small scripts, but painful for much more. It works on my terminal (OSX iTerm2). It might not work on yours. ANSI/VT100 is a mess. The way we get terminal size (rows, columns) is kludgingly elegant. Memory usage is about 2 to 3 times the size of the file being edited. Seems ok for script files, but beware. Syntax highlighting does work. Very cool. Of course, this means we need syntax highlighting for ovms scripts. Enjoy, Mark

1 0