- OvmsDev - Open Vehicles

Valid Vehicle ID characters?
by Greg D. 09 Mar '18

09 Mar '18

Just noticed... The Webserver restricts the vehicle ID to "upper case letters and digits". I thought underscores and dashes are allowed (seems to work); my car's ID contains an underscore... Is this additional restriction new (server v3, perhaps)? Greg

4 7

3.0.991
by Mark Webb-Johnson 08 Mar '18

08 Mar '18

New version, tagged and in the repository now: 2018-03-05 MWJ 3.0.991 OTA release support OTA updates over HTTP - Update ovms_module to use new API for per-task heap info. - Commands "time status" and "time set" for access to real-time clock. - Time zone support in config vehicle/timezone See GNU LIBC documentation for details on format https://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html - Auto start/init for wifi, modem, vehicle type, server v2 & v3 - Fix to SDCARD component to free SD_DATA1, SD_DATA2, and SD_DATA3 in 1-line mode (in particular so SD_DATA1/GPIO4 and SD_DATA3/GPIO13 can be used for UART to simcom modem for OVMS v3.1 hardware). https://www.esp32.com/viewtopic.php?f=13&t=4838 - Record statistics for CAN bus interrupts (per controller) and show in status. - Don't issue network.reconfigured event when network is down. - Auto start for ext12v & obd2ecu - Web config for timezone & distance units - Twizy web UI for features, battery properties & charge control - Support ESP IDF v3 style OTA updates over http This version is available via OTA (for both 3.0 and 3.1), but unfortunately you’ll need this version running to be able to do an http OTA ;-) If you want to try, then first flash it (as normal), then start wifi, then do ‘ota flash http’. Next version will be 3.0.992. Example: OVMS > ota flash http Current running partition is: factory Target partition is: ota_0 Download firmware from api.openvehicles.com/firmware/ota/v3.1/main/ovms3.bin to ota_0 Expected file size is 1970944 Preparing flash partition... Downloading... (100208 bytes so far) Downloading... (200216 bytes so far) Downloading... (300324 bytes so far) Downloading... (400744 bytes so far) Downloading... (500752 bytes so far) Downloading... (600960 bytes so far) Downloading... (701068 bytes so far) Downloading... (801388 bytes so far) Downloading... (901396 bytes so far) Downloading... (1001604 bytes so far) Downloading... (1102024 bytes so far) Downloading... (1202132 bytes so far) Downloading... (1302140 bytes so far) Downloading... (1402248 bytes so far) Downloading... (1502668 bytes so far) Downloading... (1603088 bytes so far) Downloading... (1703296 bytes so far) Downloading... (1803304 bytes so far) Downloading... (1903724 bytes so far) Setting boot partition... OTA flash was successful Flashed 1970944 bytes from api.openvehicles.com/firmware/ota/v3.1/main/ovms3.bin Next boot will be from ‘ota_0' OVMS > ota status Firmware: 3.0.991-dirty/factory/main build (idf v3.1-dev-453-g0f978bcb) Mar 5 2018 13:34:10 Running partition: factory Boot partition: ota_0 OVMS > metrics list m.ve m.version 3.0.991-dirty/factory/main build (idf v3.1-dev-453-g0f978bcb) Mar 5 2018 13:34:10 This is using the ESP IDF v3.x way of doing OTA binary images. The last 32 bytes of the image contains a sha256 checksum of the image (up to but not including the last 32bytes). The ESP IDF bootloader checks that. Seems to work, but a little bit flaky. Sometimes I can’t get DNS resolution. Anyway, OTA updates are available now, and I’ll try to improve on it over the next few days. Longer term, we want this to happen automatically, so long as module is on wifi. Perhaps once a day. We can worry about that later; for the moment, connect to the web interface then run ‘ota flash http’ from the console there. Regards, Mark.

4 15

Fwd: [openvehicles/Open-Vehicle-Monitoring-System-3] 9a68e2: Tesla Model S basic vehicle support
by Mark Webb-Johnson 07 Mar '18

07 Mar '18

No, I don’t consider Tesla Model S to be a high priority car to support OVMS. However: It is the car I currently drive I am interested in seeing how usable OVMS v3 is as a CAN bus reverse engineering tool The Model S can bus is relatively high volume, so will stress the system I can put OVMS v3 into it, and monitor it on a daily basis to get the bugs out (particular modem stability, and modem/wifi switch) https://github.com/openvehicles/CAN-RE-Tool/blob/master/rules/teslamodels <https://github.com/openvehicles/CAN-RE-Tool/blob/master/rules/teslamodels> I’ve committed a stub at the moment. Just need to put it into my car, make sure the CAN bus parameters are fine, then I’ll flesh it out. Looks like the Tesla Roadster cable should work fine for this (I’ve got a ‘classic’ 2014 Model S). Regards, Mark. > Branch: refs/heads/master > Home: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3 > Commit: 9a68e225969e45bafa0accc604305c6b17de4971 > https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/9a6… > Author: Mark Webb-Johnson <mark(a)webb-johnson.net> > Date: 2018-03-06 (Tue, 06 Mar 2018) > > Changed paths: > M vehicle/OVMS.V3/changes.txt > A vehicle/OVMS.V3/components/vehicle_teslamodels/component.mk > A vehicle/OVMS.V3/components/vehicle_teslamodels/src/vehicle_teslamodels.cpp > A vehicle/OVMS.V3/components/vehicle_teslamodels/src/vehicle_teslamodels.h > M vehicle/OVMS.V3/main/Kconfig > > Log Message: > ----------- > Tesla Model S basic vehicle support

3 5

OVMS v3 Pre-Launch Announcement
by Mark Webb-Johnson 06 Mar '18

06 Mar '18

The first batch of production OVMS v3 modules and modems is being produced now. We estimate availability on Fasttech late this month (March 2018). Specifications and Pricing follow. OVMS v3.1 module: US$90 Black injection-moulded plastic enclosure ESP32 WROVER processor (16MB flash, 4MB SPI RAM, 520KB SRAM, dual core 160/240MHz Xtensa LX6 processor) WIFI 802.11 b/g/n Bluetooth v4.2 BR/EDR and BLE 3x CAN buses 1x Micro USB connector (for flash download and serial console) 1x Micro SD card slot 1x Internal expansion slot 8x EGPIO, 2x GPIO 1x GSM antenna connector 1x GPS antenna connector 1x DB9 vehicle connector 1x DB26 expansion connector OVMS v3.1 SIM5360E 3G modem module (either US or EU edition): US$60 Modem is an optional plug-in module, that can be changed in future (to allow for new technology) 3G (EV-DO/HSPA+) dual band modem Includes 2G (GSM/GPRS) and 2.5G (EDGE) quad band GPS/GNSS Nano (4FF) SIM slot HOLOGRAM.IO nano sim US edition is SIM5360A (Dual-Band UMTS/HSPA+ 850/1900MHz, Quad-Band GSM/GPRS/EDGE 850/900/1800/1900MHz) EU edition is SIM5360J(E) (Dual-Band UMTS/HSPA+ 900/2100MHz, Quad-Band GSM/GPRS/EDGE 850/900/1800/1900MHz) Bundle (OVMS v3.1 module + v3.1 modem): US$150 A time-limited special discount of US$20 off this bundle price will be provided for existing OVMS v2 owners (making this bundle offer US$130). This first production batch is intended for experienced OVMS v2 users and v3 developers. Please note: Firmware is not complete, and should be considered beta Functionality is approximately equivalent to basic OVMS v2 firmware, but some advanced features (such as ACC, SMS control, etc) are not available yet Firmware is far in advance of v2 in other aspects (such as built in web server, metrics, console, tcp/ip support, diagnostics, geofencing, scripting, etc) Firmware can be updated either Over The Air (OTA), by Micro SD card, or over USB interface Vehicle support currently includes: Kia Soul EV, Nissan Leaf, Renault Twizy, Tesla Roadster The antenna and vehicle connectors for OVMS v3 are the same as for OVMS v2, and existing cables/antennas can generally be re-used for OVMS v3. Note, however, that the frequency ranges supported by individual 3G networks may be different than 2G, so may benefit from an antenna specifically designed for the 3G frequency ranges used.

1 1

OVMS v3 pricing
by Mark Webb-Johnson 06 Mar '18

06 Mar '18

I’m trying to get pricing for OVMS v3 down, but with the large up-front costs we’ve had to pay (injection moulding, prototypes, etc), it has been hard. At launch, this is the best we can do: OVMS v3.1 module: US$90 Black injection-moulded plastic enclosure ESP32 WROVER processor (16MB flash, 4MB SPI RAM, 520KB SRAM, dual core Xtensa LX6 processor) WIFI 802.11 b/g/n Bluetooth v4.2 BR/EDR and BLE 3x CAN buses 1x Micro USB connector (for flash download and serial console) 1x Micro SD card slot 1x Internal expansion slot 8x EGPIO, 2x GPIO 1x GSM antenna connector 1x GPS antenna connector 1x DB9 vehicle connector 1x DB26 expansion connector OVMS v3.1 SIM5360E 3G modem module (either US or EU edition): US$60 Modem is an optional plug-in module, that can be changed in future (to allow for new technology) 3G (EV-DO/HSPA+) dual band modem Includes 2G (GSM/GPRS) and 2.5G (EDGE) quad band GPS/GNSS Nano (4FF) SIM slot HOLOGRAM.IO nano sim US edition is SIM5360A (Dual-Band UMTS/HSPA+ 850/1900MHz, Quad-Band GSM/GPRS/EDGE 850/900/1800/1900MHz) EU edition is SIM5360J(E) (Dual-Band UMTS/HSPA+ 900/2100MHz, Quad-Band GSM/GPRS/EDGE 850/900/1800/1900MHz) Bundle (OVMS v3.1 module + v3.1 modem): US$150 Discount: Time-limit offer of US$20 for existing OVMS v2 owners First production batch is intended for experienced OVMS v2 users and v3 developers. General availability of the bundles should be late March 2018 at FastTech. Please note: Firmware is not complete, and should be considered beta Functionality is approximately equivalent to basic OVMS v2 firmware, but some advanced features (such as ACC, SMS control, etc) are not available yet Firmware is far in advance of v2 in other aspects (such as built in web server, metrics, console, tcp/ip support, diagnostics, geofencing, scripting, etc) Firmware can be updated either Over The Air (OTA), by Micro SD card, or over USB interface Vehicle support currently includes: Kia Soul EV Nissan Leaf Renault Twizy Tesla Roadster Please have a read through the above, and let me know if you see any problems. It will form the basis of an end-user announcement to go out to forums, mailing lists, and all current users. Regards, Mark.

3 9

System date set?
by Stephen Casner 03 Mar '18

03 Mar '18

Does the sytem date get set anywhere (presumably from GPS)? This question occurred to me as I'm working on a side project using the DEVKIT-C module which won't have access to GPS so I added the code to set the data using SNTP. -- Steve

4 13

Stack overflow: What is task "itT"?
by Greg D. 01 Mar '18

01 Mar '18

Hi folks, I just updated to the latest (7 commits), and am having trouble with a stack overflow in a task named "tiT". Not sure if that's real, or if the task name has been corrupted. My startup script enables both simcom and wifi. Turning off wifi doesn't prevent the crash. Turning off simcom does (I get all the way to the server connecting), so it's apparently somehow related to the modem and ppp stack. Thoughts? Greg W (10404) wifi: incorrect scan type: 1073533448 I (11404) simcom: State timeout, transition to 2 I (11404) simcom: State: Enter PoweringOn state I (11404) simcom: Power Cycle I (11894) housekeeping: System considered stable, auto init re-enabled I (17034) simcom: State: Enter PoweredOn state I (36404) simcom: State: Enter MuxStart state I (36404) gsm-mux: Start MUX I (36414) gsm-mux: Channel #0 is open I (36424) gsm-mux: Channel #1 is open I (36424) gsm-mux: Channel #2 is open I (36434) gsm-mux: Channel #3 is open I (36434) gsm-mux: Channel #4 is open I (37404) simcom: State: Enter NetWait state I (47484) simcom: CREG Network Registration: RegisteredRoaming I (48404) simcom: State: Enter NetStart state I (49494) simcom: PPP Connection is ready to start I (50404) simcom: State: Enter NetMode state I (50404) gsm-ppp: Initialising... W (50404) wifi: incorrect scan type: 1073533448 OVMS > ***ERROR*** A stack overflow in task tiT has been detected. abort() was called at PC 0x4008f024 on core 1 0x4008f024: vApplicationStackOverflowHook at /home/greg/esp/esp-idf/components/esp32/./panic.c:648 Backtrace: 0x4008ee34:0x3ffca170 0x4008f00b:0x3ffca190 0x4008f024:0x3ffca1b0 0x4008b52c:0x3ffca1d0 0x4008d534:0x3ffca1f0 0x4008d4ea:0x3ffb15dc 0x4008ee34: invoke_abort at /home/greg/esp/esp-idf/components/esp32/./panic.c:648 0x4008f00b: abort at /home/greg/esp/esp-idf/components/esp32/./panic.c:648 0x4008f024: vApplicationStackOverflowHook at /home/greg/esp/esp-idf/components/esp32/./panic.c:648 0x4008b52c: vTaskSwitchContext at /home/greg/esp/esp-idf/components/freertos/./tasks.c:4837 0x4008d534: _frxt_dispatch at /home/greg/esp/esp-idf/components/freertos/./portasm.S:406 0x4008d4ea: _frxt_int_exit at /home/greg/esp/esp-idf/components/freertos/./portasm.S:206 Rebooting...

3 5

Igor Medvedev
by Mark Webb-Johnson 27 Feb '18

27 Feb '18

I got a ‘hello’ eMail from a new developer interested in helping out with OVMS. His name is Igor, and for the last 17 years he has been working on embedded projects. He drives a Nissan Leaf, and has a background with 3G modems and CAN protocols like CANOPEN. He is asking what tasks he can help out with. Perhaps reviewing the SIMCOM modem support (for reliability) and/or helping Tom out with Nissan Leaf support? Anybody else got any suggestions for Igor? Regards, Mark.

4 6

OVMS v3.1 Release Candidate
by Mark Webb-Johnson 27 Feb '18

27 Feb '18

I fixed the issue with SIMCOM UART. It was another compatibility issue with SDCARD. The GPIO4 and GPIO13 we are using for v3.1 simcom modem are SD_DATA1 and SD_DATA3. Even though I had set SDCARD to 1-line mode, the ESP IDF driver was still reserving all those GPIO pins for itself (at hardware controller level). A 1-line (sic) change to our SD-CARD component fixes this and frees SD_DATA1, SD_DATA2, SD_DATA3 for our other uses. With firmware fix made, I can mount the SD CARD, and run ‘test sd’ while talking to simcom modem. All ok. CAN2 is now also ok. I re-flowed the solder on that part of the board, and all looks good now. OVMS > can can1 start active 1000000 Can bus can1 started in mode active at speed 1000000Kbps OVMS > can can2 start active 1000000 Can bus can2 started in mode active at speed 1000000Kbps OVMS > can can3 start active 1000000 Can bus can3 started in mode active at speed 1000000Kbps OVMS > can log trace CAN logging active: Type:trace; Path:''; Filter:off; Vehicle:; Note: info logging is done at log level debug, frame logging at verbose OVMS > log level verbose Logging level for * set to verbose OVMS > can can1 tx standard 100 01 02 03 04 V (66710) canlog: TX can1 id 100 len 4: 01 02 03 04 | .... V (66710) canlog: RX can2 id 100 len 4: 01 02 03 04 | .... V (66710) canlog: RX can3 id 100 len 4: 01 02 03 04 | …. OVMS > can can2 tx standard 100 01 02 03 04 V (73230) canlog: TX can2 id 100 len 4: 01 02 03 04 | .... V (73230) canlog: RX can1 id 100 len 4: 01 02 03 04 | .... V (73230) canlog: RX can3 id 100 len 4: 01 02 03 04 | .... OVMS > can can3 tx standard 100 01 02 03 04 V (80380) canlog: TX can3 id 100 len 4: 01 02 03 04 | .... V (80380) canlog: RX can1 id 100 len 4: 01 02 03 04 | .... V (80380) canlog: RX can2 id 100 len 4: 01 02 03 04 | .... OVMS > can can1 status CAN: can1 Mode: Active Speed: 1000000 Interrupts: 4 Rx pkt: 2 Rx err: 0 Rx ovrflw: 0 Tx pkt: 2 Tx delays: 0 Tx err: 0 Tx ovrflw: 0 Err flags: 0 D (88210) canlog: Status can1 intr=4 rxpkt=2 txpkt=2 errflags=0 rxerr=0 txerr=0 rxovr=0 txovr=0 txdelay=0 OVMS > can can2 status CAN: can2 Mode: Active Speed: 1000000 Interrupts: 4 Rx pkt: 3 Rx err: 0 Rx ovrflw: 0 Tx pkt: 1 Tx delays: 0 Tx err: 0 Tx ovrflw: 0 Err flags: 0 D (90770) canlog: Status can2 intr=4 rxpkt=3 txpkt=1 errflags=0 rxerr=0 txerr=0 rxovr=0 txovr=0 txdelay=0 OVMS > can can3 status CAN: can3 Mode: Active Speed: 1000000 Interrupts: 4 Rx pkt: 3 Rx err: 0 Rx ovrflw: 0 Tx pkt: 1 Tx delays: 0 Tx err: 0 Tx ovrflw: 0 Err flags: 0 D (92910) canlog: Status can3 intr=4 rxpkt=3 txpkt=1 errflags=0 rxerr=0 txerr=0 rxovr=0 txovr=0 txdelay=0 So 16MB Flash, 4MB SPIRAM, ESP32, modem, CAN, EGPIO, and SDCARD are all ok. I will test the remaining few peripherals tonight (need 12v power). I think we are going to be ok now. Component orders have been placed. I’m going to order a first batch of 120 modules tonight (assuming no issues with the last few peripherals). Regards, Mark.

3 4

Awfully quiet out there
by Stephen Casner 25 Feb '18

25 Feb '18

It's been several days since I've seen any messages on this list. I suppose that Mark has been occupied by the hardware changes. Myself, I've finished the things I was working on (with the possible exception of adding an immediate-send option back into Mongoose), but I've entered a PR to get the code I added to esp-idf to support the per-task heap allocation commands accepted into the mainline and have been refining the code in response to change requests. -- Steve

5 49