October 2017 - OvmsDev - Open Vehicles

SD CARD
by Mark Webb-Johnson 09 Jan '18

09 Jan '18

Any electronics guys out there can help out with SD CARD? It is frustrating as hell. The last part of the hardware puzzle. Once we solve this, we can hit the button to start making these. China and I have been struggling with this for the last month, with little progress. We are just following the standard Espressif schematics for this. Here is Espressif’s master document on it: https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card <https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card> Our circuit has been built for 4 wire SD mode, using the standard pins and pullups (as documented by Espressif). Result is that it is unreliable. Fails to mount 90% of SD CARDS, and those that do mount fail and corrupt data when writing lots of data out. The core problem (we think) is that the GPIO2 and GPIO12 pins used for SD CARD are also required to be at specific values during boot (to select different boot modes). Espressif suggest to work around this using the transistor logic they have for controlling boot mode pins using the USB-to-serial converter and DTR + RTS async control pins. We want 4-wire, but let’s start with a simple 1-wire diagram on a breadboard (as per Espressif instructions): ESP32 pin SD card pin SPI pin Notes GPIO14 (MTMS) CLK SCK 10k pullup in SD mode GPIO15 (MTDO) CMD MOSI 10k pullup, both in SD and SPI modes GPIO2 D0 MISO 10k pullup in SD mode, pull low to go into download mode (see note below!) GPIO4 D1 N/C not used in 1-line SD mode; 10k pullup in 4-line SD mode GPIO12 (MTDI) D2 N/C not used in 1-line SD mode; 10k pullup in 4-line SD mode (see note below!) GPIO13 (MTCK) D3 CS not used in 1-line SD mode, but card's D3 pin must have a 10k pullup N/C CD optional, not used in the example N/C WP optional, not used in the example Also: Connect GPIO0 and GPIO2 using a jumper (so transistors drive GPIO2 and GPIO0 low when entering download mode (10K pullup otherwise) 3.3V connect to SDCARD GND connect to SDCARD We have a variety of ESP32 development modules to try this with. Espressif said that the original DEVKIT C had a problem with the boot pin control lines and transistor logic (but never said what exactly that problem was). With original (old) ESP32 DEVKIT C, I can’t get it to work reliably at all. Sometimes ok. Sometimes not. With OVMS test code (that writes a lot of data), it never works. With our OVMS boards, all versions, I can’t get it to work reliably at all. Sometimes ok. Sometimes not. With OVMS test code (that writes a lot of data), it never works. I don’t think it ever worked. Just before our test was so simple that it didn’t show the problem. So, I just purchased one of these: https://www.banggood.com/ESP32-Development-Board-WiFiBluetooth-Ultra-Low-Po… <https://www.banggood.com/ESP32-Development-Board-WiFiBluetooth-Ultra-Low-Po…> Geekcreit® ESP32 Development Board WiFi+Bluetooth Ultra Low Power Consumption Dual Cores ESP-32 ESP-32S Board (Very similar to DEVKIT C, but more modern) It works 100%. Although after flashing it cannot boot (waiting for download) - need to disconnect GPIO0 - GPIO2 link, reset, then reconnect GPIO0-GPIO2 link. Then perfect. I think our problem is related to that transistor auto-flash reset circuitry. GPIO2 is the line for data transfer, so if problem will cause data corruption and unreliable (like we are seeing). Espressif SD CARD notes here: https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card <https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card> Schematic for Geekcreit board is here: https://www.dropbox.com/s/jefwxxtufgwg0ex/esp32_Schematic%20Prints.pdf?dl=0 <https://www.dropbox.com/s/jefwxxtufgwg0ex/esp32_Schematic%20Prints.pdf?dl=0> Schematic for latest version of Espressif DEVKIT C board is here: http://espressif.com/sites/default/files/documentation/esp32_hardware_desig… <http://espressif.com/sites/default/files/documentation/esp32_hardware_desig…> The original DEVKIT C (v1) had 1K resistors on that circuit. This is the version I have. The Geekcreit has 10K resistors on that circuit. OVMS has 10K resistors on that circuit. The latest DEVKIT C (v3) has 12K resistors on that circuit. DEVKIT C v1 schematic is here: http://dl.espressif.com/dl/schematics/ESP32-DevKitJ-v1_sch.pdf <http://dl.espressif.com/dl/schematics/ESP32-DevKitJ-v1_sch.pdf> DEVKIT C v2 schematic is here: http://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-2.pdf <http://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-2.pdf> The latest Espressif ROVER KIT development board schematic is here: https://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-3.pdf <https://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-3.pdf> Note that they are now using 100K resistors, and a separate transistor on IO0 (to allow it to be independently controlled after boot). I am reasonably certain our SD CARD problem concerns the GPIO0-GPIO2 link. Can you look at these, and see if you can find the difference? Apart from resistor sizes (which Espressif keep messing around with), I can’t see the practical difference. Regards, Mark.

4 12

SIMCOM PPP
by Mark Webb-Johnson 15 Nov '17

15 Nov '17

That was a hell of a lot of work: OVMS > config list modem modem apn: hologram apn.password: apn.user: enable.net: yes enable.sms: yes OVMS > power simcom on Power mode of simcom is now on I (13073) simcom: State: Enter PoweringOn state I (13073) simcom: Power Cycle SIMCOM tx 41 54 0d 0a AT.. SIMCOM tx 41 54 0d 0a AT.. SIMCOM tx 41 54 0d 0a AT.. SIMCOM tx 41 54 0d 0a AT.. SIMCOM tx 41 54 0d 0a AT.. SIMCOM tx 41 54 0d 0a AT.. SIMCOM tx 41 54 0d 0a AT.. SIMCOM rx 0d 0a 53 54 41 52 54 0d 0a 41 54 0d 0d 0a 4f 4b ..START..AT...OK I (19193) simcom: State: Enter PoweredOn state SIMCOM rx 0d 0a .. SIMCOM rx 0d 0a 2b 43 50 49 4e 3a 20 52 45 41 44 59 0d 0a ..+CPIN: READY.. SIMCOM line 2b 43 50 49 4e 3a 20 52 45 41 44 59 +CPIN: READY SIMCOM rx 0d 0a 4f 50 4c 20 55 50 44 41 54 49 4e 47 0d 0a ..OPL UPDATING.. SIMCOM line 4f 50 4c 20 55 50 44 41 54 49 4e 47 OPL UPDATING SIMCOM rx 0d 0a 50 4e 4e 20 55 50 44 41 54 49 4e 47 0d 0a ..PNN UPDATING.. SIMCOM line 50 4e 4e 20 55 50 44 41 54 49 4e 47 PNN UPDATING SIMCOM rx 0d 0a 53 4d 53 20 44 4f 4e 45 0d 0a ..SMS DONE.. SIMCOM line 53 4d 53 20 44 4f 4e 45 SMS DONE SIMCOM rx 0d 0a 43 41 4c 4c 20 52 45 41 44 59 0d 0a ..CALL READY.. SIMCOM line 43 41 4c 4c 20 52 45 41 44 59 CALL READY SIMCOM rx 0d 0a 50 42 20 44 4f 4e 45 0d 0a ..PB DONE.. SIMCOM line 50 42 20 44 4f 4e 45 PB DONE SIMCOM tx 41 54 2b 43 50 49 4e 3f 3b 2b 43 52 45 47 3d 31 AT+CPIN?;+CREG=1 SIMCOM tx 3b 2b 43 54 5a 55 3d 31 3b 2b 43 54 5a 52 3d 31 ;+CTZU=1;+CTZR=1 SIMCOM tx 3b 2b 43 4c 49 50 3d 31 3b 2b 43 4d 47 46 3d 31 ;+CLIP=1;+CMGF=1 SIMCOM tx 3b 2b 43 4e 4d 49 3d 31 2c 32 2c 30 2c 30 2c 30 ;+CNMI=1,2,0,0,0 SIMCOM tx 3b 2b 43 53 44 48 3d 31 3b 2b 43 4d 45 45 3d 32 ;+CSDH=1;+CMEE=2 SIMCOM tx 3b 2b 43 53 51 3b 2b 41 55 54 4f 43 53 51 3d 31 ;+CSQ;+AUTOCSQ=1 SIMCOM tx 2c 31 3b 45 30 0d 0a ,1;E0.. SIMCOM rx 41 54 2b 43 50 49 4e 3f 3b 2b 43 52 45 47 3d 31 AT+CPIN?;+CREG=1 SIMCOM rx 3b 2b 43 54 5a 55 3d 31 3b 2b 43 54 5a 52 3d 31 ;+CTZU=1;+CTZR=1 SIMCOM rx 3b 2b 43 4c 49 50 3d 31 3b 2b 43 4d 47 46 3d 31 ;+CLIP=1;+CMGF=1 SIMCOM rx 3b 2b 43 4e 4d 49 3d 31 2c 32 2c 30 2c 30 2c 30 ;+CNMI=1,2,0,0,0 SIMCOM rx 3b 2b 43 53 44 48 3d 31 3b 2b 43 4d 45 45 3d 32 ;+CSDH=1;+CMEE=2 SIMCOM rx 3b 2b 43 53 51 3b 2b 41 55 54 4f 43 53 51 3d 31 ;+CSQ;+AUTOCSQ=1 SIMCOM rx 2c 31 3b 45 30 0d ,1;E0. SIMCOM line 41 54 2b 43 50 49 4e 3f 3b 2b 43 52 45 47 3d 31 AT+CPIN?;+CREG=1 SIMCOM line 3b 2b 43 54 5a 55 3d 31 3b 2b 43 54 5a 52 3d 31 ;+CTZU=1;+CTZR=1 SIMCOM line 3b 2b 43 4c 49 50 3d 31 3b 2b 43 4d 47 46 3d 31 ;+CLIP=1;+CMGF=1 SIMCOM line 3b 2b 43 4e 4d 49 3d 31 2c 32 2c 30 2c 30 2c 30 ;+CNMI=1,2,0,0,0 SIMCOM line 3b 2b 43 53 44 48 3d 31 3b 2b 43 4d 45 45 3d 32 ;+CSDH=1;+CMEE=2 SIMCOM line 3b 2b 43 53 51 3b 2b 41 55 54 4f 43 53 51 3d 31 ;+CSQ;+AUTOCSQ=1 SIMCOM line 2c 31 3b 45 30 ,1;E0 SIMCOM rx 0d 0a 2b 43 50 49 4e 3a 20 52 45 41 44 59 0d 0a ..+CPIN: READY.. SIMCOM line 2b 43 50 49 4e 3a 20 52 45 41 44 59 +CPIN: READY SIMCOM rx 0d 0a 2b 43 53 51 3a 20 32 31 2c 39 39 0d 0a 0d ..+CSQ: 21,99... SIMCOM line 2b 43 53 51 3a 20 32 31 2c 39 39 +CSQ: 21,99 SIMCOM rx 0a 4f 4b 0d 0a .OK.. SIMCOM line 4f 4b OK SIMCOM tx 41 54 2b 43 4f 50 53 3f AT+COPS? SIMCOM tx 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 33 AT+CMUXSRVPORT=3 SIMCOM tx 2c 31 0d 0a ,1.. SIMCOM rx 0d 0a 45 52 52 4f 52 0d 0a ..ERROR.. SIMCOM line 45 52 52 4f 52 ERROR SIMCOM tx 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 32 AT+CMUXSRVPORT=2 SIMCOM tx 2c 31 0d 0a ,1.. SIMCOM rx 0d 0a 4f 4b 0d 0a ..OK.. SIMCOM line 4f 4b OK SIMCOM tx 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 31 AT+CMUXSRVPORT=1 SIMCOM tx 2c 31 0d 0a ,1.. SIMCOM rx 0d 0a 4f 4b 0d 0a ..OK.. SIMCOM line 4f 4b OK SIMCOM tx 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 30 AT+CMUXSRVPORT=0 SIMCOM tx 2c 35 0d 0a ,5.. SIMCOM rx 0d 0a 4f 4b 0d 0a ..OK.. SIMCOM line 4f 4b OK SIMCOM tx 41 54 2b 43 4d 55 58 3d 30 0d 0a AT+CMUX=0.. SIMCOM rx 0d 0a 4f 4b 0d 0a ..OK.. SIMCOM line 4f 4b OK I (39223) simcom: State: Enter MuxMode state I (39223) gsm-mux: Start MUX I (39223) gsm-mux: StartChannel(0) SIMCOM tx f9 03 3f 01 1c f9 ..?... SIMCOM rx f9 03 73 01 d7 f9 ..s... I (39233) gsm-mux: ProcessFrame(CHAN=0, ADDR=03, CTRL=73, FCS=d7, LEN=6) I (39233) gsm-mux: ChanProcessFrame(CHAN=0, ADDR=03, CTRL=73, LEN=3, IFP=3) I (39233) gsm-mux: Channel #0 is open I (39233) gsm-mux: StartChannel(1) SIMCOM tx f9 07 3f 01 de f9 ..?... SIMCOM rx f9 07 73 01 15 f9 ..s... I (39243) gsm-mux: ProcessFrame(CHAN=1, ADDR=07, CTRL=73, FCS=15, LEN=6) I (39243) gsm-mux: ChanProcessFrame(CHAN=1, ADDR=07, CTRL=73, LEN=3, IFP=3) I (39243) gsm-mux: Channel #1 is open I (39243) gsm-mux: StartChannel(2) SIMCOM tx f9 0b 3f 01 59 f9 ..?.Y. SIMCOM rx f9 0b 73 01 92 f9 ..s... I (39243) gsm-mux: ProcessFrame(CHAN=2, ADDR=0b, CTRL=73, FCS=92, LEN=6) I (39243) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=0b, CTRL=73, LEN=3, IFP=3) I (39243) gsm-mux: Channel #2 is open I (39243) gsm-mux: StartChannel(3) SIMCOM tx f9 0f 3f 01 9b f9 ..?... SIMCOM rx f9 0f 73 01 50 f9 ..s.P. I (39253) gsm-mux: ProcessFrame(CHAN=3, ADDR=0f, CTRL=73, FCS=50, LEN=6) I (39253) gsm-mux: ChanProcessFrame(CHAN=3, ADDR=0f, CTRL=73, LEN=3, IFP=3) I (39253) gsm-mux: Channel #3 is open I (39253) gsm-mux: StartChannel(4) SIMCOM tx f9 13 3f 01 96 f9 ..?... SIMCOM rx f9 13 73 01 5d f9 ..s.]. I (39263) gsm-mux: ProcessFrame(CHAN=4, ADDR=13, CTRL=73, FCS=5d, LEN=6) I (39263) gsm-mux: ChanProcessFrame(CHAN=4, ADDR=13, CTRL=73, LEN=3, IFP=3) I (39263) gsm-mux: Channel #4 is open I (40193) simcom: State: Enter NetStart state SIMCOM tx f9 0d ff 3b 41 54 2b 43 52 45 47 3f 3b 2b 43 43 ...;AT+CREG?;+CC SIMCOM tx 4c 4b 3f 3b 2b 43 53 51 3b 2b 43 4f 50 53 3f 0d LK?;+CSQ;+COPS?. SIMCOM tx 0a cf f9 ... SIMCOM rx f9 0d ff c7 0d 0a 2b 43 52 45 47 3a 20 31 2c 35 ......+CREG: 1,5 SIMCOM rx 0d 0a 0d 0a 2b 43 43 4c 4b 3a 20 22 31 37 2f 31 ....+CCLK: "17/1 SIMCOM rx 30 2f 32 34 2c 31 34 3a 33 34 3a 32 35 2b 33 32 0/24,14:34:25+32 SIMCOM rx 22 0d 0a 0d 0a 2b 43 53 51 3a 20 32 31 2c 39 39 "....+CSQ: 21,99 SIMCOM rx 0d 0a 0d 0a 2b 43 4f 50 53 3a 20 30 2c 30 2c 22 ....+COPS: 0,0," SIMCOM rx 43 4d 48 4b 20 4a 73 79 20 54 65 6c 22 2c 32 0d CMHK Jsy Tel",2. SIMCOM rx 0a 0d 0a 4f 4b 0d 0a 72 f9 ...OK..r. I (70273) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff, FCS=72, LEN=105) I (70273) gsm-mux: ChanProcessFrame(CHAN=3, ADDR=0d, CTRL=ff, LEN=102, IFP=3) SIMCOM line 2b 43 52 45 47 3a 20 31 2c 35 +CREG: 1,5 I (70273) simcom: CREG Network Registration 5 SIMCOM line 2b 43 43 4c 4b 3a 20 22 31 37 2f 31 30 2f 32 34 +CCLK: "17/10/24 SIMCOM line 2c 31 34 3a 33 34 3a 32 35 2b 33 32 22 ,14:34:25+32" SIMCOM line 2b 43 53 51 3a 20 32 31 2c 39 39 +CSQ: 21,99 SIMCOM line 2b 43 4f 50 53 3a 20 30 2c 30 2c 22 43 4d 48 4b +COPS: 0,0,"CMHK SIMCOM line 20 4a 73 79 20 54 65 6c 22 2c 32 Jsy Tel",2 SIMCOM line 4f 4b OK SIMCOM tx f9 09 ff 5d 41 54 2b 43 47 44 43 4f 4e 54 3d 31 ...]AT+CGDCONT=1 SIMCOM tx 2c 22 49 50 22 2c 22 68 6f 6c 6f 67 72 61 6d 22 ,"IP","hologram" SIMCOM tx 3b 2b 43 47 44 41 54 41 3d 22 50 50 50 22 2c 31 ;+CGDATA="PPP",1 SIMCOM tx 0d 0a a1 f9 .... SIMCOM rx f9 09 ff 25 0d 0a 43 4f 4e 4e 45 43 54 20 31 31 ...%..CONNECT 11 SIMCOM rx 35 32 30 30 0d 0a fb f9 5200.... I (71283) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=fb, LEN=24) I (71283) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=21, IFP=3) SIMCOM line 43 4f 4e 4e 45 43 54 20 31 31 35 32 30 30 CONNECT 115200 I (71283) simcom: PPP Connection is ready to start I (72193) simcom: State: Enter NetMode state SIMCOM ppp tx 7e ff 7d 23 c0 21 7d 21 7d 21 7d 20 7d 34 7d 22 ~.}#.!}!}!} }4}" SIMCOM ppp tx 7d 26 7d 20 7d 20 7d 20 7d 20 7d 25 7d 26 7d 2d }&} } } } }%}&}- SIMCOM ppp tx 51 7d 3d 27 7d 27 7d 22 7d 28 7d 22 ca 61 7e Q}='}'}"}(}".a~ SIMCOM tx f9 09 ff 5f 7e ff 7d 23 c0 21 7d 21 7d 21 7d 20 ..._~.}#.!}!}!} SIMCOM tx 7d 34 7d 22 7d 26 7d 20 7d 20 7d 20 7d 20 7d 25 }4}"}&} } } } }% SIMCOM tx 7d 26 7d 2d 51 7d 3d 27 7d 27 7d 22 7d 28 7d 22 }&}-Q}='}'}"}(}" SIMCOM tx ca 61 7e 42 f9 .a~B. SIMCOM rx f9 09 ff 67 7e ff 7d 23 c0 21 7d 21 7d 20 7d 20 ...g~.}#.!}!} } SIMCOM rx 7d 38 7d 22 7d 26 7d 20 7d 20 7d 20 7d 20 7d 23 }8}"}&} } } } }# SIMCOM rx 7d 24 c0 23 7d 25 7d 26 c0 e5 f2 46 7d 27 7d 22 }$.#}%}&...F}'}" SIMCOM rx 7d 28 7d 22 76 fc 7e 68 f9 f9 09 ff 61 7e ff 7d }(}"v.~h....a~.} I (72243) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=68, LEN=57) I (72243) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=54, IFP=3) SIMCOM ppp rx 7e ff 7d 23 c0 21 7d 21 7d 20 7d 20 7d 38 7d 22 ~.}#.!}!} } }8}" SIMCOM ppp rx 7d 26 7d 20 7d 20 7d 20 7d 20 7d 23 7d 24 c0 23 }&} } } } }#}$.# SIMCOM ppp rx 7d 25 7d 26 c0 e5 f2 46 7d 27 7d 22 7d 28 7d 22 }%}&...F}'}"}(}" SIMCOM ppp rx 76 fc 7e v.~ SIMCOM ppp tx 7e ff 7d 23 c0 21 7d 22 7d 20 7d 20 7d 38 7d 22 ~.}#.!}"} } }8}" SIMCOM ppp tx 7d 26 7d 20 7d 20 7d 20 7d 20 7d 23 7d 24 c0 23 }&} } } } }#}$.# SIMCOM ppp tx 7d 25 7d 26 c0 e5 f2 46 7d 27 7d 22 7d 28 7d 22 }%}&...F}'}"}(}" SIMCOM ppp tx ba 7d 31 7e .}1~ SIMCOM tx f9 09 ff 69 7e ff 7d 23 c0 21 7d 22 7d 20 7d 20 ...i~.}#.!}"} } SIMCOM tx 7d 38 7d 22 7d 26 7d 20 7d 20 7d 20 7d 20 7d 23 }8}"}&} } } } }# SIMCOM tx 7d 24 c0 23 7d 25 7d 26 c0 e5 f2 46 7d 27 7d 22 }$.#}%}&...F}'}" SIMCOM tx 7d 28 7d 22 ba 7d 31 7e 82 f9 }(}".}1~.. SIMCOM rx 23 c0 21 7d 22 7d 21 7d 20 7d 34 7d 22 7d 26 7d #.!}"}!} }4}"}&} SIMCOM rx 20 7d 20 7d 20 7d 20 7d 25 7d 26 7d 2d 51 7d 3d } } } }%}&}-Q}= SIMCOM rx 27 7d 27 7d 22 7d 28 7d 22 21 7d 28 7e 8c f9 '}'}"}(}"!}(~.. I (72263) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=8c, LEN=54) I (72263) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=51, IFP=3) SIMCOM ppp rx 7e ff 7d 23 c0 21 7d 22 7d 21 7d 20 7d 34 7d 22 ~.}#.!}"}!} }4}" SIMCOM ppp rx 7d 26 7d 20 7d 20 7d 20 7d 20 7d 25 7d 26 7d 2d }&} } } } }%}&}- SIMCOM ppp rx 51 7d 3d 27 7d 27 7d 22 7d 28 7d 22 21 7d 28 7e Q}='}'}"}(}"!}(~ SIMCOM ppp tx 7e ff 03 c0 23 01 01 00 0f 09 8c 31 fd 3f fa 8d ~...#......1.?.. SIMCOM ppp tx fe 3f 30 00 79 f0 7e .?0.y.~ SIMCOM tx f9 09 ff 2f 7e ff 03 c0 23 01 01 00 0f 09 8c 31 .../~...#......1 SIMCOM tx fd 3f fa 8d fe 3f 30 00 79 f0 7e 16 f9 .?...?0.y.~.. SIMCOM rx f9 09 ff 2b 7e ff 7d 23 c0 21 7d 2b 7d 21 7d 20 ...+~.}#.!}+}!} SIMCOM rx 7d 28 c0 e5 f2 46 4e 99 7e 11 f9 }(...FN.~.. I (72283) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=11, LEN=27) I (72283) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=24, IFP=3) SIMCOM ppp rx 7e ff 7d 23 c0 21 7d 2b 7d 21 7d 20 7d 28 c0 e5 ~.}#.!}+}!} }(.. SIMCOM ppp rx f2 46 4e 99 7e .FN.~ SIMCOM rx f9 09 ff 17 7e c0 23 02 01 00 05 00 fd 30 7e 3c ....~.#......0~< SIMCOM rx f9 . I (72293) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=3c, LEN=17) I (72293) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=14, IFP=3) SIMCOM ppp rx 7e c0 23 02 01 00 05 00 fd 30 7e ~.#......0~ SIMCOM ppp tx 7e ff 03 80 21 01 01 00 1c 02 06 00 2d 0f 01 03 ~...!.......-... SIMCOM ppp tx 06 00 00 00 00 81 06 00 00 00 00 83 06 00 00 00 ................ SIMCOM ppp tx 00 55 15 7e .U.~ SIMCOM tx f9 09 ff 49 7e ff 03 80 21 01 01 00 1c 02 06 00 ...I~...!....... SIMCOM tx 2d 0f 01 03 06 00 00 00 00 81 06 00 00 00 00 83 -............... SIMCOM tx 06 00 00 00 00 55 15 7e ba f9 .....U.~.. SIMCOM ppp tx 7e ff 03 80 57 01 01 00 0e 01 0a 18 b5 9a ee fe ~...W........... SIMCOM ppp tx c2 87 ef 19 1f 7e .....~ SIMCOM tx f9 09 ff 2d 7e ff 03 80 57 01 01 00 0e 01 0a 18 ...-~...W....... SIMCOM tx b5 9a ee fe c2 87 ef 19 1f 7e f5 f9 .........~.. SIMCOM rx f9 09 ff 13 7e 00 03 01 00 04 42 f6 7e 3b f9 ....~.....B.~;. I (73353) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=3b, LEN=15) I (73353) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=12, IFP=3) SIMCOM ppp rx 7e 00 03 01 00 04 42 f6 7e ~.....B.~ SIMCOM ppp tx 7e ff 03 c0 21 08 02 00 09 00 03 01 00 04 c2 80 ~...!........... SIMCOM ppp tx 7e ~ SIMCOM tx f9 09 ff 23 7e ff 03 c0 21 08 02 00 09 00 03 01 ...#~...!....... SIMCOM tx 00 04 c2 80 7e 1f f9 ....~.. SIMCOM rx f9 09 ff 15 7e 80 21 01 00 00 04 67 c3 7e df f9 ....~.!....g.~.. I (75973) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=df, LEN=16) I (75973) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=13, IFP=3) SIMCOM ppp rx 7e 80 21 01 00 00 04 67 c3 7e ~.!....g.~ SIMCOM ppp tx 7e ff 03 80 21 03 00 00 0a 03 06 00 00 00 00 a0 ~...!........... SIMCOM ppp tx 3d 7e =~ SIMCOM tx f9 09 ff 25 7e ff 03 80 21 03 00 00 0a 03 06 00 ...%~...!....... SIMCOM tx 00 00 00 a0 3d 7e fb f9 ....=~.. SIMCOM rx f9 09 ff 21 7e 80 21 04 01 00 0a 02 06 00 2d 0f ...!~.!.......-. SIMCOM rx 01 f8 30 7e fc f9 f9 09 ff 15 7e 80 21 01 01 00 ..0~......~.!... I (75983) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=fc, LEN=22) I (75983) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=19, IFP=3) SIMCOM ppp rx 7e 80 21 04 01 00 0a 02 06 00 2d 0f 01 f8 30 7e ~.!.......-...0~ SIMCOM ppp tx 7e ff 03 80 21 01 02 00 16 03 06 00 00 00 00 81 ~...!........... SIMCOM ppp tx 06 00 00 00 00 83 06 00 00 00 00 da 82 7e .............~ SIMCOM tx f9 09 ff 3d 7e ff 03 80 21 01 02 00 16 03 06 00 ...=~...!....... SIMCOM tx 00 00 00 81 06 00 00 00 00 83 06 00 00 00 00 da ................ SIMCOM tx 82 7e e9 f9 .~.. SIMCOM rx 04 bb 99 7e df f9 ...~.. I (75993) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=df, LEN=16) I (75993) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=13, IFP=3) SIMCOM ppp rx 7e 80 21 01 01 00 04 bb 99 7e ~.!......~ SIMCOM ppp tx 7e ff 03 80 21 02 01 00 04 cd 92 7e ~...!......~ SIMCOM tx f9 09 ff 19 7e ff 03 80 21 02 01 00 04 cd 92 7e ....~...!......~ SIMCOM tx d6 f9 .. SIMCOM rx f9 09 ff 39 7e 80 21 03 02 00 16 03 06 0a 34 df ...9~.!.......4. SIMCOM rx 08 81 06 d4 09 00 87 83 06 d4 09 00 88 31 96 7e .............1.~ SIMCOM rx ee f9 .. I (76003) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=ee, LEN=34) I (76003) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=31, IFP=3) SIMCOM ppp rx 7e 80 21 03 02 00 16 03 06 0a 34 df 08 81 06 d4 ~.!.......4..... SIMCOM ppp rx 09 00 87 83 06 d4 09 00 88 31 96 7e .........1.~ SIMCOM ppp tx 7e ff 03 80 21 01 03 00 16 03 06 0a 34 df 08 81 ~...!.......4... SIMCOM ppp tx 06 d4 09 00 87 83 06 d4 09 00 88 96 6b 7e ............k~ SIMCOM tx f9 09 ff 3d 7e ff 03 80 21 01 03 00 16 03 06 0a ...=~...!....... SIMCOM tx 34 df 08 81 06 d4 09 00 87 83 06 d4 09 00 88 96 4............... SIMCOM tx 6b 7e e9 f9 k~.. SIMCOM rx f9 09 ff 39 7e 80 21 02 03 00 16 03 06 0a 34 df ...9~.!.......4. SIMCOM rx 08 81 06 d4 09 00 87 83 06 d4 09 00 88 00 08 7e ...............~ SIMCOM rx ee f9 .. I (76023) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=ee, LEN=34) I (76023) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=31, IFP=3) SIMCOM ppp rx 7e 80 21 02 03 00 16 03 06 0a 34 df 08 81 06 d4 ~.!.......4..... SIMCOM ppp rx 09 00 87 83 06 d4 09 00 88 00 08 7e ...........~ I (76053) simcom: status_cb: Connected I (76053) simcom: our_ipaddr = 10.52.223.8 I (76063) simcom: his_ipaddr = 10.64.64.64 I (76073) simcom: netmask = 255.255.255.255 I (76073) simcom: our6_ipaddr = :: That is: A power control layer to be able to reliable power on/off the simcom modem and track it’s power status. A uart layer to talk to the modem. An initialisation of the SIMCOM modem, getting things like ICCID and sim card status. A GSM 07.10 mux, run on top of the uart, to give us four virtual channels (1 for a NMEA GPS stream, 1 for a GSM PPP data connection, 1 for AT polling of status (sms, signal quality, etc), and 1 for generic AT commands). An initialisation of the network layer, to get the GSM data connection channel into PPP mode. A software PPPOS (PPP over serial) implementation, to make a PPP VPN to the GSM provider and authenticate with PAP username and password. All that to get an IP address. No error recovery at the moment, but at least I have an IP address. A network interface. Something that works the same as a Wifi link to the rest of the software. Once the ppp link is up, we can do this over it: OVMS > server v2 start Launching OVMS Server V2 connection (oscv2) I (486733) ovms-server-v2: OVMS Server V2 registered metric modifier is #1 I (486733) ovms-server: Launching OVMS Server V2 connection task (oscv2) I (486743) ovms-server-v2: OVMS Server v2 task running I (486743) ovms-server-v2: Connection is api.openvehicles.com:6867 TESTCAR/NETPASS SIMCOM ppp tx 7e 21 45 00 00 42 00 00 00 00 ff 11 fd dd 0a 34 ~!E..B.........4 SIMCOM ppp tx df 08 d4 09 00 87 b7 ff 00 35 00 2e d6 93 d4 3f .........5.....? SIMCOM ppp tx 01 00 00 01 00 00 00 00 00 00 03 61 70 69 0c 6f ...........api.o SIMCOM ppp tx 70 65 6e 76 65 68 69 63 6c 65 73 03 63 6f 6d 00 penvehicles.com. SIMCOM ppp tx 00 01 00 01 e8 c5 7e ......~ SIMCOM tx f9 09 ff 8f 7e 21 45 00 00 42 00 00 00 00 ff 11 ....~!E..B...... SIMCOM tx fd dd 0a 34 df 08 d4 09 00 87 b7 ff 00 35 00 2e ...4.........5.. SIMCOM tx d6 93 d4 3f 01 00 00 01 00 00 00 00 00 00 03 61 ...?...........a SIMCOM tx 70 69 0c 6f 70 65 6e 76 65 68 69 63 6c 65 73 03 pi.openvehicles. SIMCOM tx 63 6f 6d 00 00 01 00 01 e8 c5 7e ce f9 com.......~.. SIMCOM ppp tx 7e 21 45 00 00 42 00 01 00 00 ff 11 fd dc 0a 34 ~!E..B.........4 SIMCOM ppp tx df 08 d4 09 00 87 b7 ff 00 35 00 2e d6 93 d4 3f .........5.....? SIMCOM ppp tx 01 00 00 01 00 00 00 00 00 00 03 61 70 69 0c 6f ...........api.o SIMCOM ppp tx 70 65 6e 76 65 68 69 63 6c 65 73 03 63 6f 6d 00 penvehicles.com. SIMCOM ppp tx 00 01 00 01 41 7d 5d 7e ....A}]~ SIMCOM tx f9 09 ff 91 7e 21 45 00 00 42 00 01 00 00 ff 11 ....~!E..B...... SIMCOM tx fd dc 0a 34 df 08 d4 09 00 87 b7 ff 00 35 00 2e ...4.........5.. SIMCOM tx d6 93 d4 3f 01 00 00 01 00 00 00 00 00 00 03 61 ...?...........a SIMCOM tx 70 69 0c 6f 70 65 6e 76 65 68 69 63 6c 65 73 03 pi.openvehicles. SIMCOM tx 63 6f 6d 00 00 01 00 01 41 7d 5d 7e 38 f9 com.....A}]~8. SIMCOM ppp tx 7e 21 45 00 00 42 00 02 00 00 ff 11 fd db 0a 34 ~!E..B.........4 SIMCOM ppp tx df 08 d4 09 00 87 b7 ff 00 35 00 2e d6 93 d4 3f .........5.....? SIMCOM ppp tx 01 00 00 01 00 00 00 00 00 00 03 61 70 69 0c 6f ...........api.o SIMCOM ppp tx 70 65 6e 76 65 68 69 63 6c 65 73 03 63 6f 6d 00 penvehicles.com. SIMCOM ppp tx 00 01 00 01 cc 98 7e ......~ SIMCOM tx f9 09 ff 8f 7e 21 45 00 00 42 00 02 00 00 ff 11 ....~!E..B...... SIMCOM tx fd db 0a 34 df 08 d4 09 00 87 b7 ff 00 35 00 2e ...4.........5.. SIMCOM tx d6 93 d4 3f 01 00 00 01 00 00 00 00 00 00 03 61 ...?...........a SIMCOM tx 70 69 0c 6f 70 65 6e 76 65 68 69 63 6c 65 73 03 pi.openvehicles. SIMCOM tx 63 6f 6d 00 00 01 00 01 cc 98 7e ce f9 com.......~.. SIMCOM rx f9 09 ff 00 01 7e 21 45 00 00 f7 43 30 00 00 39 .....~!E...C0..9 SIMCOM rx 11 7f f9 d4 09 00 87 0a 34 df 08 00 35 b7 ff 00 ........4...5... SIMCOM rx e3 14 ef d4 3f 81 80 00 01 00 01 00 04 00 04 03 ....?........... SIMCOM rx 61 70 69 0c 6f 70 65 6e 76 65 68 69 63 6c 65 73 api.openvehicles SIMCOM rx 03 63 6f 6d 00 00 01 00 01 c0 0c 00 01 00 01 00 .com............ SIMCOM rx 00 29 a7 00 04 ca 34 2b 50 c0 10 00 02 00 01 00 .)....4+P....... SIMCOM rx 01 b2 28 00 14 06 64 6e 73 32 34 39 01 64 08 72 ..(...dns249.d.r SIMCOM rx 65 67 69 73 74 65 72 c0 egister. SIMCOM rx 1d c0 10 00 02 00 01 00 01 b2 28 00 0b 5b f9 f9 ..........(..[.. I (488623) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=5b, LEN=135) I (488623) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=132, IFP=4) SIMCOM ppp rx 7e 21 45 00 00 f7 43 30 00 00 39 11 7f f9 d4 09 ~!E...C0..9..... SIMCOM ppp rx 00 87 0a 34 df 08 00 35 b7 ff 00 e3 14 ef d4 3f ...4...5.......? SIMCOM ppp rx 81 80 00 01 00 01 00 04 00 04 03 61 70 69 0c 6f ...........api.o SIMCOM ppp rx 70 65 6e 76 65 68 69 63 6c 65 73 03 63 6f 6d 00 penvehicles.com. SIMCOM ppp rx 00 01 00 01 c0 0c 00 01 00 01 00 00 29 a7 00 04 ............)... SIMCOM ppp rx ca 34 2b 50 c0 10 00 02 00 01 00 01 b2 28 00 14 .4+P.........(.. SIMCOM ppp rx 06 64 6e 73 32 34 39 01 64 08 72 65 67 69 73 74 .dns249.d.regist SIMCOM ppp rx 65 72 c0 1d c0 10 00 02 00 01 00 01 b2 28 00 0b er...........(.. SIMCOM rx 09 ff e1 06 64 6e 73 31 38 32 01 63 c0 4b c0 10 ....dns182.c.K.. SIMCOM rx 00 02 00 01 00 01 b2 28 00 0b 06 64 6e 73 30 31 .......(...dns01 SIMCOM rx 33 01 62 c0 4b c0 10 00 02 00 01 00 01 b2 28 00 3.b.K.........(. SIMCOM rx 0b 06 64 6e 73 30 39 33 01 61 c0 4b c0 90 00 01 ..dns093.a.K.... SIMCOM rx 00 01 00 01 b2 28 00 04 d8 15 e7 5d c0 79 00 01 .....(.....].y.. SIMCOM rx 00 01 00 01 b2 28 00 04 d8 15 e8 0d c0 62 00 01 .....(.......b.. SIMCOM rx 00 01 00 01 b2 28 00 04 d8 15 eb b6 c0 42 00 01 .....(.......B.. SIMCOM rx 00 01 00 6c f9 f9 09 ff 19 01 ea 79 00 04 d8 15 ...l.......y.... I (488663) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=6c, LEN=118) I (488663) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=115, IFP=3) SIMCOM ppp rx 06 64 6e 73 31 38 32 01 63 c0 4b c0 10 00 02 00 .dns182.c.K..... SIMCOM ppp rx 01 00 01 b2 28 00 0b 06 64 6e 73 30 31 33 01 62 ....(...dns013.b SIMCOM ppp rx c0 4b c0 10 00 02 00 01 00 01 b2 28 00 0b 06 64 .K.........(...d SIMCOM ppp rx 6e 73 30 39 33 01 61 c0 4b c0 90 00 01 00 01 00 ns093.a.K....... SIMCOM ppp rx 01 b2 28 00 04 d8 15 e7 5d c0 79 00 01 00 01 00 ..(.....].y..... SIMCOM ppp rx 01 b2 28 00 04 d8 15 e8 0d c0 62 00 01 00 01 00 ..(.......b..... SIMCOM ppp rx 01 b2 28 00 04 d8 15 eb b6 c0 42 00 01 00 01 00 ..(.......B..... SIMCOM rx ec f9 cf 73 7e d6 f9 f9 09 ff 00 01 7e 21 45 00 ...s~.......~!E. I (488703) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=d6, LEN=18) I (488703) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=15, IFP=3) SIMCOM ppp rx 01 ea 79 00 04 d8 15 ec f9 cf 73 7e ..y.......s~ SIMCOM rx 00 f7 43 31 00 00 39 11 7f f8 d4 09 00 87 0a 34 ..C1..9........4 SIMCOM rx df 08 00 35 b7 ff 00 e3 14 ef d4 3f 81 80 00 01 ...5.......?.... SIMCOM rx 00 01 00 04 00 04 03 61 70 69 0c 6f 70 65 6e 76 .......api.openv SIMCOM rx 65 68 69 63 6c 65 73 03 63 6f 6d 00 00 01 00 01 ehicles.com..... SIMCOM rx c0 0c 00 01 00 01 00 00 29 a7 00 04 ca 34 2b 50 ........)....4+P SIMCOM rx c0 10 00 02 00 01 00 01 b2 28 00 14 06 64 6e 73 .........(...dns SIMCOM rx 32 34 39 01 64 08 72 65 67 69 73 74 65 72 c0 1d 249.d.register.. SIMCOM ppp tx 7e 21 45 00 00 2c 00 03 00 00 ff 06 dd 07 0a 34 ~!E..,.........4 SIMCOM ppp tx df 08 ca 34 2b 50 d7 8b 1a d3 00 00 19 6d 00 00 ...4+P.......m.. SIMCOM ppp tx 00 00 60 02 16 d0 96 c9 00 00 02 04 05 b4 12 f5 ..`............. SIMCOM ppp tx 7e ~ SIMCOM tx f9 09 ff 63 7e 21 45 00 00 2c 00 03 00 00 ff 06 ...c~!E..,...... SIMCOM tx dd 07 0a 34 df 08 ca 34 2b 50 d7 8b 1a d3 00 00 ...4...4+P...... SIMCOM tx 19 6d 00 00 00 00 60 02 16 d0 96 c9 00 00 02 04 .m....`......... SIMCOM tx 05 b4 12 f5 7e 6f f9 ....~o. SIMCOM rx c0 10 00 02 00 01 00 01 b2 28 00 0b 5b f9 f9 09 .........(..[... I (488773) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=5b, LEN=135) I (488783) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=132, IFP=4) SIMCOM ppp rx 7e 21 45 00 00 f7 43 31 00 00 39 11 7f f8 d4 09 ~!E...C1..9..... SIMCOM ppp rx 00 87 0a 34 df 08 00 35 b7 ff 00 e3 14 ef d4 3f ...4...5.......? SIMCOM ppp rx 81 80 00 01 00 01 00 04 00 04 03 61 70 69 0c 6f ...........api.o SIMCOM ppp rx 70 65 6e 76 65 68 69 63 6c 65 73 03 63 6f 6d 00 penvehicles.com. SIMCOM ppp rx 00 01 00 01 c0 0c 00 01 00 01 00 00 29 a7 00 04 ............)... SIMCOM ppp rx ca 34 2b 50 c0 10 00 02 00 01 00 01 b2 28 00 14 .4+P.........(.. SIMCOM ppp rx 06 64 6e 73 32 34 39 01 64 08 72 65 67 69 73 74 .dns249.d.regist SIMCOM ppp rx 65 72 c0 1d c0 10 00 02 00 01 00 01 b2 28 00 0b er...........(.. SIMCOM rx ff e1 06 64 6e 73 30 39 33 01 61 c0 4b c0 10 00 ...dns093.a.K... SIMCOM rx 02 00 01 00 01 b2 28 00 0b 06 64 6e 73 30 31 33 ......(...dns013 SIMCOM rx 01 62 c0 4b c0 10 00 02 00 01 00 01 b2 28 00 0b .b.K.........(.. SIMCOM rx 06 64 6e 73 31 38 32 01 63 c0 4b c0 62 00 01 00 .dns182.c.K.b... SIMCOM rx 01 00 01 b2 28 00 04 d8 15 e7 5d c0 79 00 01 00 ....(.....].y... SIMCOM rx 01 00 01 b2 28 00 04 d8 15 e8 0d c0 90 00 01 00 ....(........... SIMCOM rx 01 00 01 b2 28 00 04 d8 15 eb b6 c0 42 00 01 00 ....(.......B... SIMCOM rx 01 00 6c f9 f9 09 ff 19 01 ea 79 00 04 d8 15 ec ..l.......y..... I (488903) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=6c, LEN=118) I (488903) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=115, IFP=3) SIMCOM ppp rx 06 64 6e 73 30 39 33 01 61 c0 4b c0 10 00 02 00 .dns093.a.K..... SIMCOM ppp rx 01 00 01 b2 28 00 0b 06 64 6e 73 30 31 33 01 62 ....(...dns013.b SIMCOM ppp rx c0 4b c0 10 00 02 00 01 00 01 b2 28 00 0b 06 64 .K.........(...d SIMCOM ppp rx 6e 73 31 38 32 01 63 c0 4b c0 62 00 01 00 01 00 ns182.c.K.b..... SIMCOM ppp rx 01 b2 28 00 04 d8 15 e7 5d c0 79 00 01 00 01 00 ..(.....].y..... SIMCOM ppp rx 01 b2 28 00 04 d8 15 e8 0d c0 90 00 01 00 01 00 ..(............. SIMCOM ppp rx 01 b2 28 00 04 d8 15 eb b6 c0 42 00 01 00 01 00 ..(.......B..... SIMCOM rx f9 7c 99 7e d6 f9 f9 09 ff 00 01 7e 21 45 00 00 .|.~.......~!E.. I (488963) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=d6, LEN=18) I (488973) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=15, IFP=3) SIMCOM ppp rx 01 ea 79 00 04 d8 15 ec f9 7c 99 7e ..y......|.~ SIMCOM ppp tx 7e 21 45 00 00 38 00 04 00 00 ff 01 fd f3 0a 34 ~!E..8.........4 SIMCOM ppp tx df 08 d4 09 00 87 03 03 2e f6 00 00 00 00 45 00 ..............E. SIMCOM ppp tx 00 f7 43 31 00 00 39 11 7f f8 d4 09 00 87 0a 34 ..C1..9........4 SIMCOM ppp tx df 08 00 35 b7 ff 00 e3 14 ef 14 b3 7e ...5........~ SIMCOM tx f9 09 ff 7b 7e 21 45 00 00 38 00 04 00 00 ff 01 ...{~!E..8...... SIMCOM tx fd f3 0a 34 df 08 d4 09 00 87 03 03 2e f6 00 00 ...4............ SIMCOM tx 00 00 45 00 00 f7 43 31 00 00 39 11 7f f8 d4 09 ..E...C1..9..... SIMCOM tx 00 87 0a 34 df 08 00 35 b7 ff 00 e3 14 ef 14 b3 ...4...5........ SIMCOM tx 7e 7d f9 ~}. SIMCOM rx f7 43 47 00 00 39 11 7f e2 d4 09 00 87 0a 34 df .CG..9........4. SIMCOM rx 08 00 35 b7 ff 00 e3 1b e8 d4 3f 81 80 00 01 00 ..5.......?..... SIMCOM rx 01 00 04 00 04 03 61 70 69 0c 6f 70 65 6e 76 65 ......api.openve SIMCOM rx 68 69 63 6c 65 73 03 63 6f 6d 00 00 01 00 01 c0 hicles.com...... SIMCOM rx 0c 00 01 00 01 00 00 29 a7 00 04 ca 34 2b 50 c0 .......)....4+P. SIMCOM rx 10 00 02 00 01 00 01 b2 28 00 14 06 64 6e 73 30 ........(...dns0 SIMCOM rx 31 33 01 62 08 72 65 67 69 73 74 65 72 c0 1d c0 13.b.register... SIMCOM rx 10 00 02 00 01 00 01 b2 28 00 0b 5b f9 f9 09 ff ........(..[.... I (489103) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=5b, LEN=135) I (489113) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=132, IFP=4) SIMCOM ppp rx 7e 21 45 00 00 f7 43 47 00 00 39 11 7f e2 d4 09 ~!E...CG..9..... SIMCOM ppp rx 00 87 0a 34 df 08 00 35 b7 ff 00 e3 1b e8 d4 3f ...4...5.......? SIMCOM ppp rx 81 80 00 01 00 01 00 04 00 04 03 61 70 69 0c 6f ...........api.o SIMCOM ppp rx 70 65 6e 76 65 68 69 63 6c 65 73 03 63 6f 6d 00 penvehicles.com. SIMCOM ppp rx 00 01 00 01 c0 0c 00 01 00 01 00 00 29 a7 00 04 ............)... SIMCOM ppp rx ca 34 2b 50 c0 10 00 02 00 01 00 01 b2 28 00 14 .4+P.........(.. SIMCOM ppp rx 06 64 6e 73 30 31 33 01 62 08 72 65 67 69 73 74 .dns013.b.regist SIMCOM ppp rx 65 72 c0 1d c0 10 00 02 00 01 00 01 b2 28 00 0b er...........(.. SIMCOM rx e1 06 64 6e 73 31 38 32 01 63 c0 4b c0 10 00 02 ..dns182.c.K.... SIMCOM rx 00 01 00 01 b2 28 00 0b 06 64 6e 73 32 34 39 01 .....(...dns249. SIMCOM rx 64 c0 4b c0 10 00 02 00 01 00 01 b2 28 00 0b 06 d.K.........(... SIMCOM rx 64 6e 73 30 39 33 01 61 c0 4b c0 90 00 01 00 01 dns093.a.K...... SIMCOM rx 00 01 b2 28 00 04 d8 15 e7 5d c0 42 00 01 00 01 ...(.....].B.... SIMCOM rx 00 01 b2 28 00 04 d8 15 e8 0d c0 62 00 01 00 01 ...(.......b.... SIMCOM rx 00 01 b2 28 00 04 d8 15 eb b6 c0 79 00 01 00 01 ...(.......y.... SIMCOM rx 00 6c f9 f9 09 ff 19 01 ea 79 00 04 d8 15 ec f9 .l.......y...... I (489233) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=6c, LEN=118) I (489233) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=115, IFP=3) SIMCOM ppp rx 06 64 6e 73 31 38 32 01 63 c0 4b c0 10 00 02 00 .dns182.c.K..... SIMCOM ppp rx 01 00 01 b2 28 00 0b 06 64 6e 73 32 34 39 01 64 ....(...dns249.d SIMCOM ppp rx c0 4b c0 10 00 02 00 01 00 01 b2 28 00 0b 06 64 .K.........(...d SIMCOM ppp rx 6e 73 30 39 33 01 61 c0 4b c0 90 00 01 00 01 00 ns093.a.K....... SIMCOM ppp rx 01 b2 28 00 04 d8 15 e7 5d c0 42 00 01 00 01 00 ..(.....].B..... SIMCOM ppp rx 01 b2 28 00 04 d8 15 e8 0d c0 62 00 01 00 01 00 ..(.......b..... SIMCOM ppp rx 01 b2 28 00 04 d8 15 eb b6 c0 79 00 01 00 01 00 ..(.......y..... SIMCOM rx 93 50 7e d6 f9 .P~.. I (489303) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=d6, LEN=18) I (489303) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=15, IFP=3) SIMCOM ppp rx 01 ea 79 00 04 d8 15 ec f9 93 50 7e ..y.......P~ SIMCOM ppp tx 7e 21 45 00 00 38 00 05 00 00 ff 01 fd f2 0a 34 ~!E..8.........4 SIMCOM ppp tx df 08 d4 09 00 87 03 03 27 fd 00 00 00 00 45 00 ........'.....E. SIMCOM ppp tx 00 f7 43 47 00 00 39 11 7f e2 d4 09 00 87 0a 34 ..CG..9........4 SIMCOM ppp tx df 08 00 35 b7 ff 00 e3 1b e8 04 eb 7e ...5........~ SIMCOM tx f9 09 ff 7b 7e 21 45 00 00 38 00 05 00 00 ff 01 ...{~!E..8...... SIMCOM tx fd f2 0a 34 df 08 d4 09 00 87 03 03 27 fd 00 00 ...4........'... SIMCOM tx 00 00 45 00 00 f7 43 47 00 00 39 11 7f e2 d4 09 ..E...CG..9..... SIMCOM tx 00 87 0a 34 df 08 00 35 b7 ff 00 e3 1b e8 04 eb ...4...5........ SIMCOM tx 7e 7d f9 ~}. SIMCOM rx f9 09 ff 63 7e 21 45 00 00 2c 00 00 40 00 2d 06 ...c~!E..,..@.-. SIMCOM rx 6f 0b ca 34 2b 50 0a 34 df 08 1a d3 d7 8b 57 15 o..4+P.4......W. SIMCOM rx 7c c8 00 00 19 6e 60 12 16 d0 c3 3e 00 00 02 04 |....n`....>.... SIMCOM rx 05 50 8a cc 7e 6f f9 .P..~o. I (489403) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=6f, LEN=55) I (489413) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=52, IFP=3) SIMCOM ppp rx 7e 21 45 00 00 2c 00 00 40 00 2d 06 6f 0b ca 34 ~!E..,..@.-.o..4 SIMCOM ppp rx 2b 50 0a 34 df 08 1a d3 d7 8b 57 15 7c c8 00 00 +P.4......W.|... SIMCOM ppp rx 19 6e 60 12 16 d0 c3 3e 00 00 02 04 05 50 8a cc .n`....>.....P.. SIMCOM ppp rx 7e ~ SIMCOM ppp tx 7e 21 45 00 00 28 00 06 00 00 ff 06 dd 08 0a 34 ~!E..(.........4 SIMCOM ppp tx df 08 ca 34 2b 50 d7 8b 1a d3 00 00 19 6e 57 15 ...4+P.......nW. SIMCOM ppp tx 7c c9 50 10 16 d0 da 97 00 00 34 9b 7e |.P.......4.~ SIMCOM tx f9 09 ff 5b 7e 21 45 00 00 28 00 06 00 00 ff 06 ...[~!E..(...... SIMCOM tx dd 08 0a 34 df 08 ca 34 2b 50 d7 8b 1a d3 00 00 ...4...4+P...... SIMCOM tx 19 6e 57 15 7c c9 50 10 16 d0 da 97 00 00 34 9b .nW.|.P.......4. SIMCOM tx 7e 45 f9 ~E. I (489453) ovms-server-v2: Connected to OVMS Server V2 at api.openvehicles.com I (489503) ovms-server-v2: Sending server login: MP-C 0 SfOEAN1nHCviPFVNSUIHvt eadHgQ0XOb6wDFqEMNCYXQ== TESTCAR SIMCOM ppp tx 7e 21 45 00 00 68 00 07 00 00 ff 06 dc c7 0a 34 ~!E..h.........4 SIMCOM ppp tx df 08 ca 34 2b 50 d7 8b 1a d3 00 00 19 6e 57 15 ...4+P.......nW. SIMCOM ppp tx 7c c9 50 18 16 d0 98 a8 00 00 4d 50 2d 43 20 30 |.P.......MP-C 0 SIMCOM ppp tx 20 53 66 4f 45 41 4e 31 6e 48 43 76 69 50 46 56 SfOEAN1nHCviPFV SIMCOM ppp tx 4e 53 55 49 48 76 74 20 65 61 64 48 67 51 30 58 NSUIHvt eadHgQ0X SIMCOM ppp tx 4f 62 36 77 44 46 71 45 4d 4e 43 59 58 51 3d 3d Ob6wDFqEMNCYXQ== SIMCOM ppp tx 20 54 45 53 54 43 41 52 0d 0a 84 c0 7e TESTCAR....~ SIMCOM tx f9 09 ff db 7e 21 45 00 00 68 00 07 00 00 ff 06 ....~!E..h...... SIMCOM tx dc c7 0a 34 df 08 ca 34 2b 50 d7 8b 1a d3 00 00 ...4...4+P...... SIMCOM tx 19 6e 57 15 7c c9 50 18 16 d0 98 a8 00 00 4d 50 .nW.|.P.......MP SIMCOM tx 2d 43 20 30 20 53 66 4f 45 41 4e 31 6e 48 43 76 -C 0 SfOEAN1nHCv SIMCOM tx 69 50 46 56 4e 53 55 49 48 76 74 20 65 61 64 48 iPFVNSUIHvt eadH SIMCOM tx 67 51 30 58 4f 62 36 77 44 46 71 45 4d 4e 43 59 gQ0XOb6wDFqEMNCY SIMCOM tx 58 51 3d 3d 20 54 45 53 54 43 41 52 0d 0a 84 c0 XQ== TESTCAR.... SIMCOM tx 7e a5 f9 ~.. SIMCOM rx f9 09 ff 5b 7e 21 45 00 00 28 73 9f 40 00 2d 06 ...[~!E..(s.@.-. SIMCOM rx fb 6f ca 34 2b 50 0a 34 df 08 1a d3 d7 8b 57 15 .o.4+P.4......W. SIMCOM rx 7c c9 00 00 19 ae 50 10 16 d0 da 57 00 00 23 8a |.....P....W..#. SIMCOM rx 7e 45 f9 f9 09 ff cb 7e 21 45 00 00 60 73 a0 40 ~E.....~!E..`s.@ I (490203) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=45, LEN=51) I (490203) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=48, IFP=3) SIMCOM ppp rx 7e 21 45 00 00 28 73 9f 40 00 2d 06 fb 6f ca 34 ~!E..(s.@.-..o.4 SIMCOM ppp rx 2b 50 0a 34 df 08 1a d3 d7 8b 57 15 7c c9 00 00 +P.4......W.|... SIMCOM ppp rx 19 ae 50 10 16 d0 da 57 00 00 23 8a 7e ..P....W..#.~ SIMCOM rx 00 2d 06 fb 36 ca 34 2b 50 0a 34 df 08 1a d3 d7 .-..6.4+P.4..... SIMCOM rx 8b 57 15 7c c9 00 00 19 ae 50 18 16 d0 ee 08 00 .W.|.....P...... SIMCOM rx 00 4d 50 2d 53 20 30 20 7a 69 35 47 31 74 6d 73 .MP-S 0 zi5G1tms SIMCOM rx 65 64 42 72 73 4b 68 65 74 41 67 57 7a 70 20 78 edBrsKhetAgWzp x SIMCOM rx 4b 54 56 4d 51 4d 68 35 30 35 6d 73 35 4f 67 6f KTVMQMh505ms5Ogo SIMCOM rx 53 44 71 75 51 3d 3d 0d 0a 3b fb 7e b9 f9 f9 09 SDquQ==..;.~.... I (490223) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=b9, LEN=107) I (490223) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=104, IFP=3) SIMCOM ppp rx 7e 21 45 00 00 60 73 a0 40 00 2d 06 fb 36 ca 34 ~!E..`s.@.-..6.4 SIMCOM ppp rx 2b 50 0a 34 df 08 1a d3 d7 8b 57 15 7c c9 00 00 +P.4......W.|... SIMCOM ppp rx 19 ae 50 18 16 d0 ee 08 00 00 4d 50 2d 53 20 30 ..P.......MP-S 0 SIMCOM ppp rx 20 7a 69 35 47 31 74 6d 73 65 64 42 72 73 4b 68 zi5G1tmsedBrsKh SIMCOM ppp rx 65 74 41 67 57 7a 70 20 78 4b 54 56 4d 51 4d 68 etAgWzp xKTVMQMh SIMCOM ppp rx 35 30 35 6d 73 35 4f 67 6f 53 44 71 75 51 3d 3d 505ms5OgoSDquQ== SIMCOM ppp rx 0d 0a 3b fb 7e ..;.~ SIMCOM rx ff 79 7e 21 45 00 00 36 73 a1 40 00 2d 06 fb 5f .y~!E..6s.@.-.._ SIMCOM rx ca 34 2b 50 0a 34 df 08 1a d3 d7 8b 57 15 7d 5d .4+P.4......W.}] SIMCOM rx 01 00 00 19 ae 50 18 16 d0 ac 32 00 00 74 36 61 .....P....2..t6a SIMCOM rx 72 61 48 79 37 33 67 3d 3d 0d 0a 68 1d 7e 9e f9 raHy73g==..h.~.. I (490263) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=9e, LEN=66) I (490263) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=63, IFP=3) SIMCOM ppp rx 7e 21 45 00 00 36 73 a1 40 00 2d 06 fb 5f ca 34 ~!E..6s.@.-.._.4 SIMCOM ppp rx 2b 50 0a 34 df 08 1a d3 d7 8b 57 15 7d 5d 01 00 +P.4......W.}].. I (490273) ovms-server-v2: Received welcome response MP-S 0 zi5G1tmsedBrsKhetAgWzp xKTVMQMh505ms5OgoSDquQ== I (490273) ovms-server-v2: Got server response: MP-S 0 zi5G1tmsedBrsKhetAgWzp xKTVMQMh505ms5OgoSDquQ== I (490273) ovms-server-v2: Server token is zi5G1tmsedBrsKhetAgWzp and digest is xKTVMQMh505ms5OgoSDquQ== I (490273) ovms-server-v2: Server authentication is successful. Prime the crypto... I (490273) ovms-server-v2: Shared secret key is zi5G1tmsedBrsKhetAgWzpSfOEAN1nHCviPFVNSUIHvt (44 bytes) I (490273) ovms-server-v2: OVMS V2 login successful, and crypto channel established I (490273) ovms-server-v2: Sending MP-0 S I (490273) ovms-server-v2: Sending MP-0 D SIMCOM ppp rx 00 19 ae 50 18 16 d0 ac 32 00 00 74 36 61 72 61 ...P....2..t6ara SIMCOM ppp rx 48 79 37 33 67 3d 3d 0d 0a 68 1d 7e Hy73g==..h.~ SIMCOM ppp tx 7e 21 45 00 00 28 00 08 00 00 ff 06 dd 06 0a 34 ~!E..(.........4 SIMCOM ppp tx df 08 ca 34 2b 50 d7 8b 1a d3 00 00 19 ae 57 15 ...4+P........W. SIMCOM ppp tx 7d 5d 0f 50 10 16 8a da 57 00 00 3e 17 7e }].P....W..>.~ SIMCOM tx f9 09 ff 5d 7e 21 45 00 00 28 00 08 00 00 ff 06 ...]~!E..(...... SIMCOM tx dd 06 0a 34 df 08 ca 34 2b 50 d7 8b 1a d3 00 00 ...4...4+P...... SIMCOM tx 19 ae 57 15 7d 5d 0f 50 10 16 8a da 57 00 00 3e ..W.}].P....W..> SIMCOM tx 17 7e a1 f9 .~.. I (490313) ovms-server-v2: Incoming Msg: MP-0 Z0 SIMCOM tx f9 0d ff 3b 41 54 2b 43 52 45 47 3f 3b 2b 43 43 ...;AT+CREG?;+CC SIMCOM tx 4c 4b 3f 3b 2b 43 53 51 3b 2b 43 4f 50 53 3f 0d LK?;+CSQ;+COPS?. SIMCOM tx 0a cf f9 ... SIMCOM rx f9 0d ff c7 0d 0a 2b 43 52 45 47 3a 20 31 2c 35 ......+CREG: 1,5 SIMCOM rx 0d 0a 0d 0a 2b 43 43 4c 4b 3a 20 22 31 37 2f 31 ....+CCLK: "17/1 SIMCOM rx 30 2f 32 34 2c 31 34 3a 34 31 3a 32 37 2b 33 32 0/24,14:41:27+32 SIMCOM rx 22 0d 0a 0d 0a 2b 43 53 51 3a 20 32 31 2c 39 39 "....+CSQ: 21,99 SIMCOM rx 0d 0a 0d 0a 2b 43 4f 50 53 3a 20 30 2c 30 2c 22 ....+COPS: 0,0," SIMCOM rx 43 4d 48 4b 20 4a 73 79 20 54 65 6c 22 2c 32 0d CMHK Jsy Tel",2. SIMCOM rx 0a 0d 0a 4f 4b 0d 0a 72 f9 ...OK..r. I (492213) gsm-mux: ProcessFrame(CHAN=3, ADDR=0d, CTRL=ff, FCS=72, LEN=105) I (492213) gsm-mux: ChanProcessFrame(CHAN=3, ADDR=0d, CTRL=ff, LEN=102, IFP=3) SIMCOM line 2b 43 52 45 47 3a 20 31 2c 35 +CREG: 1,5 I (492213) simcom: CREG Network Registration 5 SIMCOM line 2b 43 43 4c 4b 3a 20 22 31 37 2f 31 30 2f 32 34 +CCLK: "17/10/24 SIMCOM line 2c 31 34 3a 34 31 3a 32 37 2b 33 32 22 ,14:41:27+32" SIMCOM line 2b 43 53 51 3a 20 32 31 2c 39 39 +CSQ: 21,99 SIMCOM line 2b 43 4f 50 53 3a 20 30 2c 30 2c 22 43 4d 48 4b +COPS: 0,0,"CMHK SIMCOM line 20 4a 73 79 20 54 65 6c 22 2c 32 Jsy Tel",2 SIMCOM line 4f 4b OK That is a DNS lookup, followed by a TCP/IP connection, followed by the OVMS v2 protocol. The OVMS v2 server library is just talking TCP/IP sockets. It doesn’t care whether it is over a SIMCOM GSM connection or WIFI. Pretty much proof of concept stage only, but this is the last major piece of the puzzle. Code is far from elegant. Still a hell of a lot of work to do with error detection and recovery. Cellular networks are painfully flaky. I’ve committed what I have, should anybody else want to play with it. Very very verbose on logging at the moment. I’ll now tidy up the error correction, and command control for starting and stopping this. Then, integrate to the network manager for signalling the GSM network coming up/down, and general network availability. Regards, Mark.

3 4

V3 Renault Twizy 0.1.0
by Michael Balzer 04 Nov '17

04 Nov '17

…just pushed. I've also made some minor changes & extensions to the framework, hopefully helpful. This is very basic support (~10%). It covers CAN processing and battery / power monitoring. Just metrics output for now, no commands or notifications. Free RAM is down to 36.6 K after loading the module. I've removed the "v." from the "x.rt.v." metrics names, as nearly all "x.rt" metrics are (of course) vehicle metrics. "x.rt.m.version" does not fit the scheme and breaks into the "motor" namespace, as "m." was in use before, maybe we should better use "mot." for motor metrics. Regards, Michael OVMS > config list x.rt x.rt autopower: yes autoreset: yes canwrite: no cap_act_prc: 87.4 cap_nom_ah: 108.0 chargelevel: 0 chargemode: 0 console: no kickdown: yes maxrange: 71 suffrange: 65 suffsoc: 85 OVMS > metrics list m.freeram 36644 m.hardware OVMS WIFI BLE BT cores=2 rev=ESP32/1 m.monotonic 541Sec m.net.mdm.iccid m.net.mdm.model m.net.provider WLAN-214677 m.net.sq m.net.type wifi m.serial 30:ae:a4:37:25:88 m.tasks 17 m.time.utc 546Sec m.version 3.0.0/factory/main build (idf v2.1-20-g88ab5d48) Oct 29 2017 09:15:17 s.v2.connected s.v2.peers v.b.12v.current 1.6A v.b.12v.voltage 0.527473V v.b.cac 94.392Ah v.b.current -36A v.b.energy.recd 0.000739342kWh v.b.energy.used 0kWh v.b.power -2.0224kW v.b.range.est 50Km v.b.range.full 68.2571Km v.b.range.ideal 49Km v.b.soc 71.92% v.b.soh 100% v.b.temp 15.4286°C v.b.voltage 56.2V v.c.charging yes v.c.climit v.c.current 36A v.c.duration.full 82Min v.c.duration.range 50Min v.c.duration.soc 25Min v.c.kwh 0.000739342kWh v.c.minutes 6Min v.c.mode standard v.c.pilot yes v.c.state charging v.c.substate go v.c.temp 25°C v.c.timermode v.c.timerstart v.c.type v.c.voltage 230V v.d.cp yes v.d.fl v.d.fr v.d.hood v.d.rl v.d.rr v.d.trunk v.e.alarm v.e.awake no v.e.c.config no v.e.c.login no v.e.charging12v yes v.e.cooling v.e.drivemode v.e.handbrake v.e.headlights v.e.heating v.e.hvac v.e.locked no v.e.on no v.e.parktime v.e.temp v.e.valet no v.i.temp v.m.temp 0°C v.p.altitude v.p.direction v.p.gpslock v.p.latitude v.p.longitude v.p.odometer 3456.51Km v.p.satcount v.p.speed 0Kph v.p.trip 3456.51Km v.tp.fl.p v.tp.fl.t v.tp.fr.p v.tp.fr.t v.tp.rl.p v.tp.rl.t v.tp.rr.p v.tp.rr.t v.type RT v.vin 7378280 x.rt.b.cell.01.voltage.act 4.025V x.rt.b.cell.01.voltage.max 4.025V x.rt.b.cell.01.voltage.maxdev 2.85712V x.rt.b.cell.01.voltage.min 4.02V x.rt.b.cell.02.voltage.act 4.015V x.rt.b.cell.02.voltage.max 4.015V x.rt.b.cell.02.voltage.maxdev 0.857117V x.rt.b.cell.02.voltage.min 4.01V x.rt.b.cell.03.voltage.act 4.015V x.rt.b.cell.03.voltage.max 4.015V x.rt.b.cell.03.voltage.maxdev 0.857117V x.rt.b.cell.03.voltage.min 4.01V x.rt.b.cell.04.voltage.act 4.01V x.rt.b.cell.04.voltage.max 4.015V x.rt.b.cell.04.voltage.maxdev 0.857117V x.rt.b.cell.04.voltage.min 4.005V x.rt.b.cell.05.voltage.act 4.015V x.rt.b.cell.05.voltage.max 4.015V x.rt.b.cell.05.voltage.maxdev 0.857117V x.rt.b.cell.05.voltage.min 4.01V x.rt.b.cell.06.voltage.act 4.015V x.rt.b.cell.06.voltage.max 4.015V x.rt.b.cell.06.voltage.maxdev -1.14288V x.rt.b.cell.06.voltage.min 4.005V x.rt.b.cell.07.voltage.act 4.015V x.rt.b.cell.07.voltage.max 4.015V x.rt.b.cell.07.voltage.maxdev 0.285706V x.rt.b.cell.07.voltage.min 4.01V x.rt.b.cell.08.voltage.act 4.01V x.rt.b.cell.08.voltage.max 4.01V x.rt.b.cell.08.voltage.maxdev -1.14288V x.rt.b.cell.08.voltage.min 4.005V x.rt.b.cell.09.voltage.act 4.01V x.rt.b.cell.09.voltage.max 4.01V x.rt.b.cell.09.voltage.maxdev -1.14288V x.rt.b.cell.09.voltage.min 4.005V x.rt.b.cell.10.voltage.act 4.01V x.rt.b.cell.10.voltage.max 4.01V x.rt.b.cell.10.voltage.maxdev -1.14288V x.rt.b.cell.10.voltage.min 4.005V x.rt.b.cell.11.voltage.act 4.015V x.rt.b.cell.11.voltage.max 4.015V x.rt.b.cell.11.voltage.maxdev 0.285706V x.rt.b.cell.11.voltage.min 4.01V x.rt.b.cell.12.voltage.act 4.01V x.rt.b.cell.12.voltage.max 4.01V x.rt.b.cell.12.voltage.maxdev -1.14288V x.rt.b.cell.12.voltage.min 4.005V x.rt.b.cell.13.voltage.act 4.01V x.rt.b.cell.13.voltage.max 4.01V x.rt.b.cell.13.voltage.maxdev -1.14288V x.rt.b.cell.13.voltage.min 4.005V x.rt.b.cell.14.voltage.act 4.025V x.rt.b.cell.14.voltage.max 4.025V x.rt.b.cell.14.voltage.maxdev 2.14288V x.rt.b.cell.14.voltage.min 4.015V x.rt.b.cell.15.voltage.act 0V x.rt.b.cell.15.voltage.max 0V x.rt.b.cell.15.voltage.maxdev 0V x.rt.b.cell.15.voltage.min 0V x.rt.b.cell.16.voltage.act 0V x.rt.b.cell.16.voltage.max 0V x.rt.b.cell.16.voltage.maxdev 0V x.rt.b.cell.16.voltage.min 0V x.rt.b.cell.cnt 14 x.rt.b.cmod.01.temp.act 16°C x.rt.b.cmod.01.temp.max 16°C x.rt.b.cmod.01.temp.maxdev 0.57143°C x.rt.b.cmod.01.temp.min 16°C x.rt.b.cmod.02.temp.act 15°C x.rt.b.cmod.02.temp.max 15°C x.rt.b.cmod.02.temp.maxdev -0.42857°C x.rt.b.cmod.02.temp.min 15°C x.rt.b.cmod.03.temp.act 16°C x.rt.b.cmod.03.temp.max 16°C x.rt.b.cmod.03.temp.maxdev 0.57143°C x.rt.b.cmod.03.temp.min 16°C x.rt.b.cmod.04.temp.act 15°C x.rt.b.cmod.04.temp.max 15°C x.rt.b.cmod.04.temp.maxdev -0.42857°C x.rt.b.cmod.04.temp.min 15°C x.rt.b.cmod.05.temp.act 16°C x.rt.b.cmod.05.temp.max 16°C x.rt.b.cmod.05.temp.maxdev 0.57143°C x.rt.b.cmod.05.temp.min 16°C x.rt.b.cmod.06.temp.act 15°C x.rt.b.cmod.06.temp.max 15°C x.rt.b.cmod.06.temp.maxdev -0.42857°C x.rt.b.cmod.06.temp.min 15°C x.rt.b.cmod.07.temp.act 15°C x.rt.b.cmod.07.temp.max 15°C x.rt.b.cmod.07.temp.maxdev -0.42857°C x.rt.b.cmod.07.temp.min 15°C x.rt.b.cmod.08.temp.act -40°C x.rt.b.cmod.08.temp.max -40°C x.rt.b.cmod.08.temp.maxdev 0°C x.rt.b.cmod.08.temp.min -40°C x.rt.b.cmod.cnt 7 x.rt.b.pack.1.temp.stddev.max 0.495093°C x.rt.b.pack.1.voltage.max 56.2V x.rt.b.pack.1.voltage.min 56.1V x.rt.b.pack.1.voltage.stddev.max 0.00586302V x.rt.b.pack.cnt 1 x.rt.m.version 0.1.0 Oct 29 2017 10:44:20 x.rt.p.stats.acc.dist 0Km x.rt.p.stats.acc.recd 0kWh x.rt.p.stats.acc.spdavg 0Kph/s x.rt.p.stats.acc.used 0kWh x.rt.p.stats.cst.dist 0Km x.rt.p.stats.cst.recd 0.000739342kWh x.rt.p.stats.cst.spdavg 0Kph x.rt.p.stats.cst.used 0kWh x.rt.p.stats.dec.dist 0Km x.rt.p.stats.dec.recd 0kWh x.rt.p.stats.dec.spdavg 0Kph/s x.rt.p.stats.dec.used 0kWh x.rt.p.stats.ldn.dist 0Km x.rt.p.stats.ldn.hsum 0m x.rt.p.stats.ldn.recd 0kWh x.rt.p.stats.ldn.used 0kWh x.rt.p.stats.lup.dist 0Km x.rt.p.stats.lup.hsum 0m x.rt.p.stats.lup.recd 0kWh x.rt.p.stats.lup.used 0kWh -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

2 6

RAM
by Mark Webb-Johnson 01 Nov '17

01 Nov '17

With our default menuconfig (plus memory debugging enabled), I get: I (0) cpu_start: App cpu up. I (2206) heap_alloc_caps: Initializing. RAM available for dynamic allocation: I (2229) heap_alloc_caps: At 3FFAFF10 len 000000F0 (0 KiB): DRAM I (2249) heap_alloc_caps: At 3FFCA290 len 00015D70 (87 KiB): DRAM I (2270) heap_alloc_caps: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM I (2291) heap_alloc_caps: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (2313) heap_alloc_caps: At 400955AC len 0000AA54 (42 KiB): IRAM OVMS > module memory ============================ Free 8-bit 77696/218088, 32-bit 18608/43580, numafter = 872 task=Asy total= 0 0 24972 change= +0 +0 +24972 task=tiT total= 352 0 0 change= +352 +0 +0 task=Hou total= 20192 24444 0 change= +20192 +24444 +0 task=mai total= 9488 26948 0 change= +9488 +26948 +0 task=IDL total= 72 0 0 change= +72 +0 +0 task=ipc total= 9320 0 0 change= +9320 +0 +0 task=eve total= 41440 0 0 change= +41440 +0 +0 If I turn off bluetooth in menuconfig, I get: OVMS > module memory ============================ Free 8-bit 150548/290912, 32-bit 18628/43600, numafter = 872 task=Asy total= 0 0 24972 change= +0 +0 +24972 task=tiT total= 352 0 0 change= +352 +0 +0 task=Hou total= 44592 0 0 change= +44592 +0 +0 task=mai total= 36436 0 0 change= +36436 +0 +0 task=IDL total= 72 0 0 change= +72 +0 +0 task=ipc total= 9320 0 0 change= +9320 +0 +0 task=eve total= 41468 0 0 change= +41468 +0 +0 72KB RAM seems a bit ridiculous for a bluetooth stack. I really hope this is not Espressif loading those binary blobs from libbtdm_app.a into RAM. If I configure a minimal (for our needs) bluetooth (BLE only), I get: --- Bluedroid Bluetooth stack enabled (3072) Bluetooth event (callback to application) task stack size (NEW) [ ] Bluedroid memory debug (NEW) [ ] Classic Bluetooth (NEW) [*] Release DRAM from Classic BT controller [*] Include GATT server module(GATTS) (NEW) [ ] Include GATT client module(GATTC) [*] Include BLE security module(SMP) (NEW) [*] Close the bluedroid bt stack log print (NEW) (2) BT/BLE MAX ACL CONNECTIONS(1~7) (NEW) OVMS > module memory ============================ Free 8-bit 106312/246720, 32-bit 18576/43548, numafter = 872 task=Asy total= 0 0 24972 change= +0 +0 +24972 task=tiT total= 352 0 0 change= +352 +0 +0 task=Hou total= 21840 22776 0 change= +21840 +22776 +0 task=mai total= 36436 0 0 change= +36436 +0 +0 task=IDL total= 72 0 0 change= +72 +0 +0 task=ipc total= 9320 0 0 change= +9320 +0 +0 task=eve total= 41476 0 0 change= +41476 +0 +0 With just classic bluetooth enabled: OVMS > module memory ============================ Free 8-bit 77696/218096, 32-bit 18608/43580, numafter = 872 task=Asy total= 0 0 24972 change= +0 +0 +24972 task=tiT total= 352 0 0 change= +352 +0 +0 task=Hou total= 20200 24444 0 change= +20200 +24444 +0 task=mai total= 9488 26948 0 change= +9488 +26948 +0 task=IDL total= 72 0 0 change= +72 +0 +0 task=ipc total= 9320 0 0 change= +9320 +0 +0 task=eve total= 41440 0 0 change= +41440 +0 +0 Turning off our memory and task debugging features, and enabling BLE GATT server + security (2 connections), gives me 122KB in metric m.freeram. That should include bluetooth requirements, but no wifi running yet. With wifi, it drops to 82KB. That should be what end-users of OVMS will see, and I’m happy with that, so have committed that as a default config for the moment. With memory and stack debugging enabled (as developers will most likely use), it drops 122KB-> 106KB. I did see some comments in the forums about this. For example: https://www.esp32.com/viewtopic.php?t=3139 <https://www.esp32.com/viewtopic.php?t=3139> It seems that IDF 3.0 changes the way this works (dynamic, rather than static as per menuconfig), and in the documentation for that they mention 70KB. It looks like a minimal bluetooth for us is going to cost 40KB RAM or so. Regards, Mark.

3 9

Terrible Network Manager
by Tom Parker 31 Oct '17

31 Oct '17

Hi, I've been driving around with the v3 hardware in my car for a couple of weeks using my phone's wifi hotspot. I found that it wouldn't re-connect to my phone after I turned off the hotspot and it wouldn't connect to my house wifi when the car is at home. So fixed it with a terrible network manager: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/compare/ma… This network manager is terrible: * it doesn't scan for available wifi and try to connect to only those that are available * it tries to connect to the next network once per minute, meaning it can take several minutes to connect * it iterates through a list of 3 networks, if you don't have 3 networks, you still have to wait * it's implemented using a mixture of events, scripts and terrible C++ code * it should use string concatenation to make the event names, rather than 3 hard coded names, but if it did that then the terrible C++ code wouldn't be so terrible * you can't turn it on or off except in sdkconfig. If it's compiled in, it tries to connect every minute * it doesn't connect to my office wifi, I haven't looked in to why, maybe it is because there is a space in the SSID name on that network Despite being so terrible, it's been pretty reliable for me. I'm not sure if you want a pull request for this thing, or perhaps someone could re-write it "properly". The obvious thing to do is to scan for available networks, look at the list of configured SSID-Password pairs and if any are in range, trigger the wifi connection directly rather than triggering an event that runs a script that attempts to connect to the network. If you want to try it out, I wrote some instructions: Beware that the following advice appends to files, but does not confirm they are empty before doing so, be sure you don't end up with unexpected scripts or script content, as unexpected things could happen. Store the credentials for your wifi network(s) with config set wifi.ssid <ssid> <password> Create a script to stop the v2 server when the network goes down (note the "network.down" doesn't fire, so use system.wifi.sta.disconnected): vfs mkdir /store/events/system.wifi.sta.disconnected vfs append "server v2 stop" /store/events/system.wifi.sta.disconnected/shutdown Create a script to start the v2 server client when the network comes up: vfs mkdir /store/events/network.up vfs append "server v2 start" /store/events/network.up/startmeup Create a script to select a vehicle on startup: vfs mkdir /store/events/system.start vfs append "vehicle module NL" /store/events/system.start/startmeup Create scripts to connect to your wifi network in response to the terrible network manager events: vfs mkdir /store/events/tnm.connect.0 vfs append "wifi mode client <ssid_1>" /store/events/tnm.connect.0/connect vfs mkdir /store/events/tnm.connect.1 vfs append "wifi mode client <ssid_2>" /store/events/tnm.connect.1/connect vfs mkdir /store/events/tnm.connect.2 vfs append "wifi mode client <ssid_3>" /store/events/tnm.connect.2/connect

3 3

V3 progress
by Tom Parker 29 Oct '17

29 Oct '17

Hi all, I got my USB CAN bus interface working with the OVMS v3 hardware on my desk, it turns out you need at least one terminator before the bus will work! I cargo culted (I've never written C++) my way through transposing the Leaf OVMS v2 can bus decoder into the v3 code. When I play a can bus recording I see the metrics update! I see that quite a few of the metrics used on the leaf are missing. Do I just add them to metrics_standard.cpp? None of them are particularly leaf specific, so this seems the right place. Is anyone working on the v2 server support code to send the S and D messages?

6 36

V3 CAN frames missing last four data bytes
by Michael Balzer 27 Oct '17

27 Oct '17

Is this a known problem? In all of my can1 frames bytes 5-8 are zero: OVMS > metrics list can d.can1.f.080 d.can1.f.155 07 97 cf 54 00 00 00 00 d.can1.f.196 00 ff e7 7f 00 00 00 00 d.can1.f.19f ff ff 7d 0f 00 00 00 00 d.can1.f.423 03 33 ff ff 00 00 00 00 d.can1.f.424 11 40 10 23 00 00 00 00 d.can1.f.425 2a 21 44 ff 00 00 00 00 d.can1.f.426 00 78 01 00 00 00 00 d.can1.f.436 00 07 7e d8 00 00 d.can1.f.554 36 36 36 36 00 00 00 00 d.can1.f.556 31 23 11 31 00 00 00 00 d.can1.f.557 31 03 10 31 00 00 00 00 d.can1.f.55e 31 23 12 31 00 00 00 00 d.can1.f.55f ff ff 73 00 00 00 00 00 d.can1.f.597 00 95 08 41 00 00 00 00 d.can1.f.599 00 00 b7 b2 00 00 00 00 d.can1.f.59b 20 00 64 00 00 00 00 00 d.can1.f.59e 00 00 0c 8d 00 00 00 00 d.can1.f.5d7 00 00 04 7c 00 00 00 d.can1.f.627 00 00 00 d.can1.f.628 00 00 00 d.can1.f.629 00 00 00 d.can1.f.659 ff ff ff ff d.can1.f.69f f0 82 87 37 d.can1.f.701 05 Trace mode: … CAN rx origin can1 id 080 (len:0) CAN rx origin can1 id 196 (len:8) 00 ff e7 7f 00 00 00 00........ CAN rx origin can1 id 155 (len:8) 07 97 ce 54 00 00 00 00...T.... CAN rx origin can1 id 19f (len:8) ff ff 7d 0f 00 00 00 00..}..... CAN rx origin can1 id 196 (len:8) 00 ff e7 7f 00 00 00 00........ CAN rx origin can1 id 155 (len:8) 07 97 ce 54 00 00 00 00...T.... CAN rx origin can1 id 5d7 (len:7) 00 00 04 7c 00 00 00 ...|... CAN rx origin can1 id 19f (len:8) ff ff 7d 0f 00 00 00 00..}..... CAN rx origin can1 id 080 (len:0) CAN rx origin can1 id 196 (len:8) 00 ff e7 7f 00 00 00 00........ CAN rx origin can1 id 599 (len:8) 00 00 b7 b2 00 00 00 00........ CAN rx origin can1 id 436 (len:6) 00 07 7e f2 00 00 ..~... CAN rx origin can1 id 155 (len:8) 07 97 ce 54 00 00 00 00...T.... CAN rx origin can1 id 69f (len:4) f0 82 87 37 ...7 CAN rx origin can1 id 19f (len:8) ff ff 7d 0f 00 00 00 00..}..... CAN rx origin can1 id 196 (len:8) 00 ff e7 7f 00 00 00 00........ CAN rx origin can1 id 423 (len:8) 03 33 ff ff 00 00 00 00.3...... CAN rx origin can1 id 426 (len:7) 00 78 01 00 00 00 00 .x..... … -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

7 18

V3 distance/speed units
by Michael Balzer 26 Oct '17

26 Oct '17

Trying to catch up… a) I'd love to get rid of those km→miles→km conversions in V3. How about introducing a metric "v.units" instead to hold the units used by the vehicle, and make conversions at the user level if necessary? b) Regarding the standard metrics currently defined, I'd need to introduce own copies again for higher precision. I.e. SOC, SOH, speed and ranges all are integers now, and some more I'd like to be able to set at higher precision. How about making all these be floats now? I.e. everything that can require more than integer precision. The server_v2 can output the values as integers for v2 client compatibility. c) I haven't seen a recommendation on naming vehicle specific metrics. My proposal: use the vehicle code as the prefix, then try to reuse similar paths from the standard metrics, adding detail as necessary. For example, the vehicle module version on the Twizy ("RT") is "rt.m.version", and for the min & max battery voltage I've got "rt.v.b.voltage.min" & "rt.v.b.voltage.max". OVMS > metrics list rt. rt.m.version 1.0.0 Oct 23 2017 11:45:31 rt.v.b.soc rt.v.b.temp.m1 rt.v.b.temp.m2 rt.v.b.temp.m3 rt.v.b.temp.m4 rt.v.b.temp.m5 rt.v.b.temp.m6 rt.v.b.temp.m7 rt.v.b.voltage.max 0 rt.v.b.voltage.min 0 That way a path component can be used to list all related metrics: OVMS > metrics list b.voltage rt.v.b.voltage.max 0 rt.v.b.voltage.min 0 v.b.voltage d) I think most of the temperature metrics have wrong names: v.b.temp.ambient v.b.temp.battery v.b.temp.charger v.b.temp.motor v.b.temp.pem …as "b." should be reserved for "battery". How about… v.e.temp v.b.temp v.c.temp v.m.temp v.i.temp …introducing "m." for motor and "i." for inverter? Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

5 11

Feedback request: HUD sleep behavior work-around
by Greg D. 23 Oct '17

23 Oct '17

2 4

Extended CAN Frame support on CAN2/3
by Greg D. 23 Oct '17

23 Oct '17

Hi folks, (Mark, in particular), I've tweaked the mcp2515.cpp code to support Extended CAN frames on CAN 2 & 3. Needed this for the OBD2ECU code, but it's there for anyone else who may want it. Mark - I did a bit of this by trial & error, since some of what I was doing wasn't working as I expected it would. Bits upside down, that sort of thing... So I expect some of the middle bits around the three frame flags is wrong, particularly on the transmit side, but for the PIDs I use, the results I get match what Wireshark decodes. So, I think it's close. Greg p.s. Got my first CAN 3 bus hang too... hope it's not related. :)

2 3