December 2019 - OvmsDev - Open Vehicles

getting started, make errors from debug options?
by Dale 20 Dec '19

20 Dec '19

Sorry, I'm still having trouble. Dabbling in many things to become dangerous, but mastering none. I'm still not able to make successfully. I'm not sure what I did to get past the previous make error. Maybe initially I didn't choose all the defaults and got something set wrong. Do I delete the sdkconfig file to get back to no settings and then it will ask all the options first time running make? I think I have openvehicles esp-idf and ovms latest versions from GIT correctly installed. I chose defaults in make menuconfig (except setting the correct USB port), and chose defaults when GENCONFIG runs from make. I changed to other OVMS versions between 3.2.000 and 3.2.008 and current master, all with same error occurring. It errors out in ovms_module, with module_tasks_data not declared in this scope. It looks like related to having debugging options selected or not? The #ifdef conditional sections contain the declaration of module_tasks_data, so it doesn't get declared, but it is still used. Am I missing setting some option for make or configuring compile options? It must be one of these? #ifndef CONFIG_HEAP_TASK_TRACKING #define NOGO 1 #endif #if configUSE_TRACE_FACILITY==0 #define NOGO 1 #endif #ifdef CONFIG_FREERTOS_ASSERT_ON_UNTESTED_FUNCTION #define NOGO 1 #endif ~/Leaf/OVMS/v3/vehicle/OVMS.V3$ make Toolchain path: /home/dklein/Leaf/OVMS/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc Toolchain version: crosstool-ng-1.22.0-80-g6c4433a Compiler version: 5.2.0 Python requirements from /homez/dklein/Documents/Projects/Leaf/OVMS/esp-idf/requirements.txt are satisfied. App "ovms3" version: 3.2.008-15-gca307f88-dirty CXX /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/build/main/ovms_module.o /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/main/ovms_module.cpp: In function 'void module_eventhandler(st d::__cxx11::string, void*)': /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/main/ovms_module.cpp:973:47: error: 'module_tasks_data' was no t declared in this scope module_tasks_data(0, NULL, NULL, 0, NULL); ^ /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/main/ovms_module.cpp: In constructor 'OvmsModuleInit::OvmsModu leInit()': /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/main/ovms_module.cpp:1048:73: error: 'module_tasks_data' was n ot declared in this scope cmd_tasks->RegisterCommand("data","Output module task stats record",module_tasks_data); ^ /homez/dklein/Documents/Projects/Leaf/OVMS/esp-idf/make/ component_wrapper.mk:289: recipe for target 'ovms_module.o' failed make[1]: *** [ovms_module.o] Error 1 /home/dklein/Documents/Projects/Leaf/OVMS/esp-idf/make/project.mk:552: recipe for target 'component-main-build' failed make: *** [component-main-build] Error 2 Thanks! Dale

2 1

getting started, make errors, path issues?
by Dale 19 Dec '19

19 Dec '19

Thanks again for this really great project and I'm looking forward to using and adding to it. Pardon my getting started with OVMS & esp-idf, I suspect I have an issue with my setup in terms of the path being correctly defined? I attempted to follow the google docs OVMS developer guide, but I must be missing something. The developer guide and the esp-idf instructions seem clear until the esp-idf instructions to run the install.sh script (setting paths, etc), but this script or similar doesn't exist in the openvehicles esp-idf branch? And the openvehicles esp-idf is a few months old, many items from the master esp-idf are different now? does that matter? Do the instructions mean to install and set up the espressif's master esp-idf, and then also clone the openvehicles esp-idf? Because I think that's what I've done. I installed the dependencies and espressif's esp-idf, and am able to flash at least hello_world on a regular esp32 board over USB and the serial terminal works with it. So that seems good. When I try to compile OVMS I get errors that look like I'm missing something. Maybe the something I'm missing is in the openvehicles esp-idf, but my paths are not including it? Is there a script in the openvehicles esp-idf that I need to run? Is it ok to have both versions of esp-idf set up at the same time? First it gives errors about the copyright text to include in the binary? dklein@___:~/Leaf/OVMS/v3/vehicle/OVMS.V3$ make Toolchain path: /home/dklein/.espressif/tools/xtensa-esp32-elf/esp-2019r2-8.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc Toolchain version: esp-2019r2 Compiler version: 8.2.0 Python requirements from /home/dklein/esp/esp-idf/requirements.txt are satisfied. App "ovms3" version: 3.2.008-15-gca307f88 CC /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/build/app_update/esp_app_desc.o AR /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/build/app_update/libapp_update.a CC /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/build/console/argtable3/argtable3.o /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c: In function 'trex_charnode': /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c:3068:7: warning: this statement ma y fall through [-Wimplicit-fallthrough=] if(!isclass) { ^ /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c:3074:4: note: here default: ^~~~~~~ At top level: /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c:273:19: error: 'rcsid' defined but not used [-Werror=unused-const-variable=] static const char rcsid[]="$Id: getopt_long.c,v 1.1 2009/10/16 19:50:28 rodney Exp rodney $"; ^~~~~ /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c: In function 'trex_compile': /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c:3466:8: warning: variable 'exp' mi ght be clobbered by 'longjmp' or 'vfork' [-Wclobbered] TRex *exp = (TRex *)malloc(sizeof(TRex)); ^~~ cc1: some warnings being treated as errors /home/dklein/esp/esp-idf/make/component_wrapper.mk:291: recipe for target 'argtable3/argtable3.o' failed make[1]: *** [argtable3/argtable3.o] Error 1 /home/dklein/esp/esp-idf/make/project.mk:610: recipe for target 'component-console-build' failed make: *** [component-console-build] Error 2 dklein@___:~/Leaf/OVMS/v3/vehicle/OVMS.V3$ If I eliminate that error, comment out the lines in argtable3, #ifndef lint static const char rcsid[]="$Id: getopt_long.c,v 1.1 2009/10/16 19:50:28 rodney Exp rodney $"; #endif /* lint */ Then I get same & other warnings, and finally a 'No rule to make target'. dklein@___:~/Leaf/OVMS/v3/vehicle/OVMS.V3$ make Toolchain path: /home/dklein/.espressif/tools/xtensa-esp32-elf/esp-2019r2-8.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc Toolchain version: esp-2019r2 Compiler version: 8.2.0 Python requirements from /home/dklein/esp/esp-idf/requirements.txt are satisfied. App "ovms3" version: 3.2.008-15-gca307f88-dirty CC /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/build/app_update/esp_app_desc.o AR /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/build/app_update/libapp_update.a CC /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/build/console/argtable3/argtable3.o /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c: In function 'trex_charnode': /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c:3068:7: warning: this statement ma y fall through [-Wimplicit-fallthrough=] if(!isclass) { ^ /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c:3074:4: note: here default: ^~~~~~~ /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c: In function 'trex_compile': /homez/dklein/Documents/Projects/Leaf/OVMS/v3/vehicle/OVMS.V3/components/console/argtable3/argtable3.c:3466:8: warning: variable 'exp' mi ght be clobbered by 'longjmp' or 'vfork' [-Wclobbered] TRex *exp = (TRex *)malloc(sizeof(TRex)); ^~~ make[1]: *** No rule to make target '/homez/dklein/Documents/Projects/vehicles/OVMS/v3/vehicle/OVMS.V3/components/console/split_argv.c', needed by 'split_argv.o'. Stop. /home/dklein/esp/esp-idf/make/project.mk:610: recipe for target 'component-console-build' failed make: *** [component-console-build] Error 2 dklein@___:~/Leaf/OVMS/v3/vehicle/OVMS.V3$ in my .bashrc # added 12/13/19, dklein, add ESP-IDF tools to path . "$HOME/esp/esp-idf/export.sh" which adds to the path as follows. Adding ESP-IDF tools to PATH... Checking if Python packages are up to date... Python requirements from /home/dklein/esp/esp-idf/requirements.txt are satisfied. Added the following directories to PATH: /home/dklein/esp/esp-idf/components/esptool_py/esptool /home/dklein/esp/esp-idf/components/espcoredump /home/dklein/esp/esp-idf/components/partition_table/ /home/dklein/.espressif/tools/xtensa-esp32-elf/esp-2019r2-8.2.0/xtensa-esp32-elf/bin /home/dklein/.espressif/tools/xtensa-esp32s2-elf/esp-2019r2-8.2.0/xtensa-esp32s2-elf/bin /home/dklein/.espressif/tools/esp32ulp-elf/2.28.51.20170517/esp32ulp-elf-binutils/bin /home/dklein/.espressif/tools/openocd-esp32/v0.10.0-esp32-20190708/openocd-esp32/bin /home/dklein/.espressif/python_env/idf4.1_py2.7_env/bin /home/dklein/esp/esp-idf/tools Done! You can now compile ESP-IDF projects. Go to the project directory and run: idf.py build Thanks! Dale

1 1

new OVMSv3 rec'd today updated OTA with .008
by Dale 18 Dec '19

18 Dec '19

Hello all, Thank you all for the great work developing OVMS, This is really neat!! I'm not sure if my new v3 hw that arrived today has the larger PSRAM. Maybe this one still has 4Mb, see below? In any case, .008 updated OTA successfully. Factory image was .002 Just connected it to home wifi. Nice job everyone! Thanks!! Dale >From USB connected simple_monitor: rst:0x1 (POWERON_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0018,len:4 load:0x3fff001c,len:4796 load:0x40078000,len:0 load:0x40078000,len:14896 entry 0x40078d74 I (882) psram: This chip is ESP32-D0WD I (882) spiram: Found 64MBit SPI RAM device I (883) spiram: SPI RAM mode: flash 40m sram 40m I (886) spiram: PSRAM initialized, cache is in low/high (2-core) mode. I (893) cpu_start: Pro cpu up. I (896) cpu_start: Application information: I (901) cpu_start: Project name: ovms3 I (906) cpu_start: App version: 3.2.008 I (911) cpu_start: Compile time: Dec 13 2019 13:04:20 I (917) cpu_start: ELF file SHA256: 900f0db86fbf6ce9... I (923) cpu_start: ESP-IDF: v3.3-beta3-772-gc3465e0 I (929) cpu_start: Starting app cpu, entry point is 0x40081668 I (0) cpu_start: App cpu up. I (1804) spiram: SPI SRAM memory test OK I (1805) heap_init: Initializing. RAM available for dynamic allocation: I (1805) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM I (1812) heap_init: At 3FFBC540 len 00023AC0 (142 KiB): DRAM I (1818) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM I (1824) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (1831) heap_init: At 40099C2C len 000063D4 (24 KiB): IRAM I (1837) cpu_start: Pro cpu start user code I (1842) spiram: Adding pool of 4096K of external SPI memory to heap allocator I (187) ovms_main: Set default logging level for * to INFO I (188) ovms_main: Pre-allocated 2MB of SPIRAM at 0x3f800028 (workaround ESP32 bug) I (192) command: Initialising COMMAND (1000) I (197) boot: Initialising BOOT (1100) I (201) boot: Power cycle reset detected I (205) events: Initialising EVENTS (1200) I (211) config: Initialising CONFIG (1400)

2 1

version 3.2.007: Crash on boot
by Greg D. 18 Dec '19

18 Dec '19

Hi folks, Well, the module updated to 3.2.007 last night. I just checked on it, and it appears that it didn't exactly survive. Crashed while running the autoconfig script. Log with two cycles attached. I tried renaming the /store/events directory to /store/was_events since it seems like Duktape was getting in the way, but that didn't resolve the crash. I manually enabled wifi so I could manage the module, and moved it back to 3.2.005 from the other partition. Seems stable again. The car is going into the Service Center tomorrow (the perennial issue with 1146 alerts), so I need to have the module stable so that I can keep an eye on it. Going to leave it on 3.2.005 for now, unless someone has a quick fix in the next few hours... Otherwise, any ideas for troubleshooting after I get the car back back (hopefully end of day)? Greg

6 26

Disabled DNS & router offer on AP DHCP
by Michael Balzer 18 Dec '19

18 Dec '19

Everyone, please test: following a user suggestion I've disabled the DNS and routing (gateway) offer sent by the Wifi AP DHCP server. Important: you also need to update the esp-idf from our repository, as the standard DHCP server has a bug that prevents disabling the DNS offer. This allows devices capable of standard network routing to connect to the OVMS AP without losing their internet connectivity (e.g. provided by cellular network), potentially solving the issue of the OVMS not acting as an internet router for AP clients. iOS supports this. Android apparently doesn't support this. As soon as it connects to any AP, it routes everything over that interface, ignoring missing router or DNS announcements. You can manually tweak the routing, but only on a rooted device. If anyone knows a trick to do this with an unrooted Android, please tell. There is an option to bind to a specific network interface. That's meant to support specifically Apps needing to connect to a Wifi network without internet access without losing the cellular connection. That could mean we can create our own browser App that binds to the OVMS wifi network. Will depend on the browser component also using that binding for all successive connections though. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0

Android App 3.14.0
by Michael Balzer 17 Dec '19

17 Dec '19

I've just released version 3.14.0 of the Android App to the Play Store. History: https://github.com/openvehicles/Open-Vehicle-Android/wiki/History#version-3… * OpenChargeMap reader: raise network timeouts, add error feedback * Whiten Tesla Roadster image (issue #88) * Twizy battery chart: synchronize cells with large time offsets * Car editor: add server selection * Notifications: disable suggestions on command input * Map settings: fix spinner style * Map: o view change => disable tracking & enable 'my location' button o fetch OCM updates for view area * OpenChargeMap API: o HTTPS support o added user agent o added API key o queue area update fetches * CarsStorage: change file format to JSON to avoid further upgrade data losses * Removed obsolete previous map layout * Map settings dialog optimized & localized * Map: inhibit autotrack camera updates during user interaction * Optimize PNG files (removed exif data) * Car editor: fix crash on start with lost/corrupted car storage * Database: sanitize user input * Allow password length up to 255 characters (issue #91) * Keep foreground ApiService alive & connected on Android >= 7 * Log class cleanup * Added 12V battery history chart * Gradle update * Minify disabled due to missing classes in APK * 12V history: tolerate D records from outdated firmware versions APK: https://github.com/openvehicles/Open-Vehicle-And...elease/OpenVehicleApp-re… Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

2 2

Alert notification history
by Mark Webb-Johnson 13 Dec '19

13 Dec '19

To try to address Greg’s concern about DMC (debug only) alerts, as well as other requests, we have: https://github.com/openvehicles/Open-Vehicle-Server/issues/1 <https://github.com/openvehicles/Open-Vehicle-Server/issues/1> I have today implemented this on api.openvehicles.com <http://api.openvehicles.com/> and set the data retention to 30 days. From now onwards, if the vehicle raises a push notification, it will be stored in the historical data table under type *-Log-Notification. This history can be retrieved either with the protocol v2 api, or http api. Perhaps @Michael can deploy this to his server as well? Regards, Mark.

2 1

ESP-WROVER-B
by Mark Webb-Johnson 12 Dec '19

12 Dec '19

Our latest wifi-only modules are coming with ESP-WROVER-B module, and that includes 8MB PSRAM/SPIRAM (not 4MB, our standard so far). I have had one report from the field that factory firmware 3.2.002 works fine, but 3.2.005 crashes on boot with an error: (824) psram: This chip is ESP32-D0WD[[0m (824) spiram: Expected 4096KiB chip but found 8192KiB chip. Bailing out.. I see we have this in our sdkconfig: Type of SPI RAM chip in use ( ) Auto-detect (X) ESP-PSRAM32 or IS25WP032 ( ) ESP-PSRAM64 or LY68L6400 Not sure when that appeared, but I guess between 3.2.002 and 3.2.005. The user experiencing this problem is knowledgeable (he managed to recover back to factory), so I am trying a 3.2.007 build with him, with that setting set to auto-detect. Regards, Mark.

2 3

3.2.006 Release to Early Access Program
by Mark Webb-Johnson 09 Dec '19

09 Dec '19

https://www.openvehicles.com/node/2346 <https://www.openvehicles.com/node/2346> Today, we are pleased to release v3.2.006 to Early Access Program. A summary of the major changes is here: 2019-11-30 MWJ 3.2.006 OTA release - Web UI: Calibration and configuration aid for 12v monitor - Log monitoring via web shell - EGPIO/MAX7317: Port input monitoring, metrics, events, documentation - Powermgmt: New automatic power management module - Scripting: OvmsMetrics.AsJSON(), OvmsEvents, and OvmsNotify added - Logging: file logging moved to dedicated task (improved performance) - SWCAN: Support for add-on SWCAN module (see https://github.com/mjuhanne/OVMS-SWCAN) - Pushover: New Pushover notification framework support - SIMCOM: Allow user to set custom SIM PIN code - Metrics: 'metric list -s' shows metric age and staleness - Others: Factory reset from web/remote shell by "module factory reset -noconfirm" - Renault Zoe: Basic Metrics and charging status added, trip notify, web config for battery capacity - Volt/Ampera: Major update (including web config, SWCAN support, etc) - Twizy: Send custom OBD2 requests, output response as hex dump - Immediate tuning metrics updates (was delegated to ticker before) For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge | eap | main', as one of: edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable) Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project.

2 5

Time for 3.2.006?
by Michael Balzer 09 Dec '19

09 Dec '19

Looking at the git log and changes.txt I'd say it's time to head for the next main release. The current build with the latest changes and tiT on core 1 is working very smoothly here. No crashes, CAN RX overflows are down to 0.25 per mille and SIMCOM overflows around 0.3 per mille. Espressif have announced they're incorporating the PSRAM fix into the official toolchain now, but there is no schedule for the release. Are there any open issues that need to be fixed for 3.2.006? Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

2 4