September 2020 - OvmsDev

Highcharts help
by Derek Caudwell 06 Sep '20

06 Sep '20

Hi all, Appreciate some help on the best way to initialise Highcharts when developing a web plugin - I am wanting to extend the bms/cellmon to include shunt state and an extra chart showing charge rate, SOC, battery temp etc. I started by copying the js code from bms/cellmon page however I could not replicate the initialisation which calls a separate javascript if Highcharts is not loaded before initialisation. I also tried a cut down version of the Trip Power Chart (without history) initialising in the main script code with: chargechart = $('#chargechart').chart({ chart: { type: 'line', events: { load: function () {$('#chgreceiver').on("msg:metrics", function(e, update){ if (update["v.b.soc"] != null) { updateChart(); } }); } etc however in updateChart() I cannot reference chargeChart to addPoints? Cheers Derek

2 1

Android App 3.17.1
by Michael Balzer 06 Sep '20

06 Sep '20

Everyone using Android, please test the new Android App release: https://github.com/openvehicles/Open-Vehicle-Android/raw/master/release/Ope… https://github.com/openvehicles/Open-Vehicle-Android/wiki/History This includes migration to the new Android Studio 4 and the new AndroidX support libraries, so I'd prefer some test feedback before actually uploading this to the Play store… Thanks & regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 3

OvmsMetricVector<string> causing console.log error
by Derek Caudwell 06 Sep '20

06 Sep '20

Hi, I am trying to resolve the ovms web interface throwing an "undefined" error because the following metric is defined with OvmsMetricVector<string> and does not get quoted when parsed to JSON.parse(ev.data) in ovms.js. Output from console error log: "xnl.v.c.duration.label":[full.l2,full.l1,full.l0,range.l2,range.l1,range.l0] However, when using JSON.print(OvmsMetrics.GetValues("xnl.v.c.duration.label")) a properly formed json string is returned: "xnl.v.c.duration.label": [ "full.l2", "full.l1", "full.l0", "range.l2", "range.l1", "range.l0" ] Can this be corrected at the ev.data source or use JSON.print on ev.data before parsing it? Kind regards Derek

2 1

OVMS not booting normally (CPU0=12 and CPU1=12)
by sharkcow 06 Sep '20

06 Sep '20

Hi all, I hope this is the right place to ask... Since flashing a new build yesterday, my OVMS doesn't boot normally anymore. What I see in the USB console are 5 early crashes (reason 12 for both CPUs), then the module falls back to running without auto init. What I have tried: switching to previously working ota, flashing & booting factory images 3.2.15 and 3.2.14 from dexter. Removed SD card since reason 12 may point to a vfs problem. What else can I try? In my understanding it doesn't make sense to do a full reflash incl. boot loader, since booting as such works... or am I mistaken? Is any other information necessary to tell what's wrong? Thank you! sharkcow --- dump from 3.2.14: I (121) boot: Initialising BOOT (1100) I (125) boot: Boot #4 reasons for CPU0=12 and CPU1=12 I (131) boot: Reset reason Exception/panic (4) E (136) boot: Early crash #4 detected I (141) events: Initialising EVENTS (1200) ... I (3250) housekeeping: Auto init vehicle (free: 133748 bytes) Guru Meditation Error: Core 1 panic'ed (StoreProhibited). Exception was unhandled. Core 1 register dump: PC : 0x401642d9 PS : 0x00060530 A0 : 0x801643a7 A1 : 0x3ffc3050 A2 : 0x3ffb8190 A3 : 0x3ffc30e0 A4 : 0x00000001 A5 : 0x3ffc30a8 A6 : 0x3ffc3090 A7 : 0x3ffb732c A8 : 0x801642d3 A9 : 0x3ffc3020 A10 : 0x00000000 A11 : 0x3ffc30e0 A12 : 0x3ffc3050 A13 : 0x0000ff00 A14 : 0x00ff0000 A15 : 0xff000000 SAR : 0x00000008 EXCCAUSE: 0x0000001d EXCVADDR: 0x0000000e LBEG : 0x4008be55 LEND : 0x4008be65 LCOUNT : 0xfffffffb ELF file SHA256: 01e6f0fccd1fb186 Backtrace: 0x401642d9:0x3ffc3050 0x401643a4:0x3ffc3090 0x400f7e83:0x3ffc3110 0x400f7a92:0x3ffc3180 0x400f8eb6:0x3ffc31c0 0x400f9051:0x3ffc31f0 0x400f9138:0x3ffc3240 0x400f9199:0x3ffc3270

4 5

RTC slow memory and persistent metrics limits
by Craig Leres 06 Sep '20

06 Sep '20

With the recent bump in persistent metrics size I did some testing to see what the actual limit is. First I found that if you make the persistent_metrics struct too large you get linker errors (which is nice): ... section `.rtc_noinit' will not fit in region `rtc_slow_seg' ... ld: RTC_SLOW segment data does not fit ... region `rtc_slow_seg' overflowed by 8272 bytes The documentation says there is 8K but I see less than 4K is actually available to us. This limit is set in esp-idf in components/esp32/ld/esp32.ld: rtc_slow_seg(RW) : org = 0x50000000 + CONFIG_ULP_COPROC_RESERVE_MEM, len = 0x1000 - CONFIG_ULP_COPROC_RESERVE_MEM (0x1000 = 4096). Testing shows 348 bytes are in use by other code. I can account for only 8 bytes of this in esp-idf exposed code so I assume the other 340 bytes are used in an esp32 library we don't get source for. Regarding the 8K vs. 4K discrepancy, I found this thread about rtc_slow_mem: https://www.esp32.com/viewtopic.php?t=3338 If I understand right, the RTC_SLOW_SEG is 8K not 4K. Am I missing something? [...] I think the higher 4k are reserved for future use by the WiFi driver. In the current versions (latest git), you can modify the size to 8k if you need. I do not see this (a way to adjust the size) in the github version of esp32.ld, it looks the same as what we're using. The bottom line is we're currently limited to 155 persistent floats (20+24*155 = 3740 < 3748) without making the persistent metrics code fancier (or trying to use more of the 8K of rtc slow memory). Craig

1 0

WiFi connect to non-broadcast SSID broken
by Greg D. 05 Sep '20

05 Sep '20

Hi folks, Looks like one of the updates broke the ability of OVMS to connect to a WiFi AP that isn't broadcasting its SSID. Was this a known side effect of the WiFi refactoring? Is there a parameter that I need to set on the module to allow the connection? Working around the issue by broadcasting my home SSID is NOT what I want to do. Greg

2 4

Issues since latest update (3.2.0.14)
by Sébastien Darveau 01 Sep '20

01 Sep '20

Hello, Anyone else is having connection issues since latest update? I’m constantly loosing contact with the device and haven’t been able to open a console with USB but this time, I can still access it with the Web interface and noticed it can’t connect to server. E (72178423) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address E (72178423) ovms-server-v2: Status: Error: Connection failed W (72180093) simcom: UART hw fifo overflow W (72192873) gsm-mux: Frame overflow (2048 bytes) E (72238423) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address E (72238423) ovms-server-v2: Status: Error: Connection failed E (72298463) ovms-server-v2: mg_connect(api.openvehicles.com:6870) failed: cannot parse address E (72298463) ovms-server-v2: Status: Error: Connection failed Address looks good though. Sebastien Darveau sebastien.darveau(a)synnoetic.com

3 6