- OvmsDev - Open Vehicles

Adding v.p.satcount to the vehicle section of the status page
by Craig Leres 10 Aug '19

10 Aug '19

I'd like to see the number of satellites being tracked on the status page. Does the attached look ok or would you guys prefer something else? (For example "... (tracking 7 satellites with good GPS lock)") Craig

2 1

How to reproduce exatly the same ovms3.bin (3.2.002-151-g56116fe) build
by Bernd Geistert 09 Aug '19

09 Aug '19

Hi all, I would like to have a defined toolchain for building ovms3.bin, so that I can reproduce the same binary (for the same GIT #tag of course) from where I can start and later share own development. I have downloaded the "reference" ovms3.bin (3.2.002-151-g56116fe Thu Aug 1 16:04:20 UTC 2019 Automated build (markhk8), size = 2594192 bytes), but this is different to my own build in the mingw32 console using $ make clean $ make all Toolchain path: /opt/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc Toolchain version: crosstool-ng-1.22.0-80-g6c4433a5 Compiler version: 5.2.0 Python requirements from C:/msys32/home/.../esp/esp-idf/requirements.txt are satisfied [Python 3.7.3] App "ovms3" version: 3.2.002-151-g56116fe1 CC build/app_update/esp_app_desc.o AR build/app_update/libapp_update.a Build version is 3.2.002-151-g56116fe1 CXX build/main/ovms_version.o AR build/main/libmain.a Generating libapp_update.a.sections_info Generating libmain.a.sections_info Generating esp32.project.ld LD build/ovms3.elf $ ls -l build/ovms3.bin -rw-r--r-- 1 Matthias None 2592512 5. Aug 21:12 build/ovms3.bin At first, my ovms3.bin build was size 3036096, but I modified the make menuconfig default 'Compiler Optimization' from 'Default' to 'Release', the size inow similar to edge/ovms3.bin, but not the same. Maybe someone could tell about other important settings in "IoT Development Framework Configuration", maybe this could be the path to match exactly markhk8's setting for 'Automated build'? I described this also in https://www.openvehicles.com/node/2263 Regards Matthias

2 3

JTAG debugging
by Marko Juhanne 03 Aug '19

03 Aug '19

Hi, has anyone tried JTAG debugging with OVMS? Mainly interested in having settable breakpoints (a feature which doesn't seem to be possible with UART gdb stub in ESP32, but seems to work with ESP8266. See https://visualgdb.com/tutorials/esp8266/gdbstub/ ). There's no JTAG header on OVMS, but I'm willing to solder a JTAG connector directly to ESP32 pins. But those pins are already connected to the SD-card reader.. Is not having a sd-card in the slot enough, or does the initialization mess with the debugger connection, thus needing to disable the sd card module on firmware? Or do I have to desolder the reader? (last resort) Br, Marko

2 1

Crashes while flashing
by Craig Leres 29 Jul '19

29 Jul '19

I think there might be a new problem with the code. The most common way for me to load new firmware is via the "Flash from web" from my system at home. Several times this weekend I've gotten "Request error, please retry" when starting the flash. Just now I got one half way through the flash. I haven't been able to get a useful stack trace because my build/ovms3.elf has already been overwritten with a new image when this happens and xtensa-esp32-elf-addr2line just prints a bunch of "??:0" lines. I've had this multiple times on two different modules today and so far 3 times in a row. I finally resorted to booting from the factory partition (which I try to keep loaded with the current public release). That resulted in it completely losing its config and firing up the OVMS ssid instead of joining my network. I've attached some frame grabs. Craig

3 3

New can logging
by Michael Balzer 29 Jul '19

29 Jul '19

Mark, is there a bug in the new can monitoring or am I doing something wrong? monitor mode: OVMS# can log start monitor crtd CAN logging to MONITOR active: Type:monitor Format:crtd Filter:off Vehicle:RT Note: info logging is at debug log level, frame logging is at verbose, and errors as usual I (83919) canlog-monitor: Now logging CAN messages to monitor D (83919) canlog-monitor: 1564312407.926444 CXX OVMS CRTD OVMS# can can1 tx standard 080 010203 ets Jun 8 2016 00:22:57 rst:0x8 (TG1WDT_SYS_RESET),boot:0x3b (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:4952 load:0x40078000,len:7416 load:0x40080000,len:8344 entry 0x4008037c W (86) boot: PRO CPU has been reset by WDT. W (86) boot: WDT reset info: PRO CPU PC=0x4008aab8 W (86) boot: WDT reset info: APP CPU PC=0x4009621a vfs mode: OVMS# can log start vfs crtd /sd/logs/can.crtd ets Jun 8 2016 00:22:57 rst:0x8 (TG1WDT_SYS_RESET),boot:0x3b (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:4952 load:0x40078000,len:7416 load:0x40080000,len:8344 entry 0x4008037c W (86) boot: PRO CPU has been reset by WDT. W (86) boot: WDT reset info: PRO CPU PC=0x4008aab8 W (86) boot: WDT reset info: APP CPU PC=0x400838cc Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 5

Can message flow reproduce
by Tamás Kovács 27 Jul '19

27 Jul '19

hi, Now i get a Lexia for Peugeot iOn and I get some useful data on can network, such as SOH and another metrics. if Lexia connected and I create a OVMS can log. I see the following data: 167913.526 1R11 761 2 21 1 FF FF FF FF FF 167913.536 1R11 762 10 2E 61 1 90 8F 1 79 167913.546 1R11 761 30 8 0A FF FF FF FF FF 167913.576 1R11 762 22 0A 4C 3 1 5E 1 5D 167913.596 1R11 762 23 1 2C 0 FA 0 FB 0 167913.606 1R11 762 24 0F 0F 1 5A 0 E8 A5 167913.636 1R11 762 26 64 0 0 0 0 0 0 167914.026 1R11 762 24 0F 0F 1 5A 0 E8 A5 167914.046 1R11 762 25 FE 0 0 1 78 75 7B 167914.056 1R11 762 26 64 0 0 0 0 0 0 167914.436 1R11 761 30 8 0A FF FF FF FF FF 167914.446 1R11 762 21 0 1 78 33 0D B3 4E 167914.476 1R11 762 23 1 2C 0 F9 0 FB 0 167914.496 1R11 762 24 0F 0F 1 5A 0 E8 A5 167914.876 1R11 761 2 21 1 FF FF FF FF FF 167914.876 1R11 762 10 2E 61 1 90 8F 1 79 167914.896 1R11 761 30 8 0A FF FF FF FF FF 167914.906 1R11 762 21 0 1 79 0 0D B3 4E 167914.926 1R11 762 22 0A 4C 3 1 5E 1 5D 167914.966 1R11 762 25 FE 0 0 1 79 75 7B 167914.986 1R11 762 26 64 0 0 0 0 0 0 167915.316 1R11 761 2 21 1 FF FF FF FF FF I searching on google and find the following things the Mitsubishi Outlander PHEV ( http://www.myoutlanderphev.com/forum/viewtopic.php?f=10&t=1796) use the same PID-s. And many more useable metrics if I can resolve this communication with ECU-s

1 1

esp-idf v3.3
by Michael Balzer 26 Jul '19

26 Jul '19

FYI: I've merged the current v3.3 status and am now running the new build (toolchain still 1.22.0-93-gf6c4cdf) on my modules. I though it would be easier to merge v3.2 first, but that didn't work out. The current v3.2 status seems to have a bug, it wouldn't link due to too many segments. The segments have been introduced by a wifi blob update to support a new wifi IRAM optimization, but that needs a linker script & esptool update as well, that seems to be available only in the v3.3 branch. So I merged v3.3 directly afterwards, and that builds without issues. So far I haven't noticed any relevant problems running the new build. On stopping the wifi module, two event errors get logged, and the AP network interface remains configured as up: OVMS# wifi mode off Stopping wifi station... I (1307252) esp32wifi: Stopping WIFI station I (1307252) netmanager: Interface priority is pp3 (10.170.195.13/255.255.255.255 gateway 10.64.64.64) I (1307252) netmanager: Set DNS#2 0.0.0.0 I (1307252) netmanager: WIFI client down (with MODEM up): reconfigured for MODEM priority I (1307252) wifi: state: run -> init (0) I (1307262) wifi: pm stop, total sleep time: 1100678913 us / 1301859253 us I (1307262) wifi: new:<1,0>, old:<1,1>, ap:<1,1>, sta:<1,0>, prof:1 E (1307262) event: system_event_sta_disconnected_handle_default 294 esp_wifi_internal_reg_rxcb ret=0x3014 E (1307262) event: system_event_ap_stop_handle_default 223 esp_wifi_internal_reg_rxcb ret=0x3014 W (1307262) netmanager: CleanupConnections: can't get AP station list I (1307272) wifi: flush txq I (1307272) wifi: stop sw txq I (1307272) wifi: lmac stop hw txq I (1307292) time: Network was reconfigured: restarting SNTP client I (1307322) netmanager: Set DNS#2 0.0.0.0 I (1307322) esp32wifi: STA disconnected with reason 8 I (1307352) netmanager: Set DNS#2 0.0.0.0 I (1307392) netmanager: Set DNS#2 0.0.0.0 I (1307392) netmanager: WIFI access point is down I (1307392) esp32wifi: AP stopped OVMS# net status Interface#3: pp3 (ifup=1 linkup=1) IPv4: 10.170.195.13/255.255.255.255 gateway 10.64.64.64 Interface#2: ap2 (ifup=1 linkup=1) IPv4: 192.168.4.1/255.255.255.0 gateway 192.168.4.1 DNS: 192.168.2.1 192.168.2.1 Default Interface: pp3 (10.170.195.13/255.255.255.255 gateway 10.64.64.64) OVMS# But wifi is off, and after starting the wifi network again, everything works, so that's a minor issue. I'll do some more tests tomorrow, then push the update. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

4 15

Trying to get a new car in, CRTD, CANbus and all
by Julien “JaXX” Banchet 19 Jul '19

19 Jul '19

Hi everyone, and happy summer to all ! So, sold my Twizy a month ago, the OVMSv3.1 has left with it, got a VW e-UP! a little bit before and received a v3.2 last week. Threw away a few microSDs but got a CRTD log this afternoon. While I have the weird impression 1335 lines and 55kB ( https://pastebin.com/FAZqnzie ) for a 30 minute drive back from work seems very short, I tried reading it in SavvyQT but it “salvages” only the first 35 lines. (30 minutes kinda full left aside the wipers, ignition off, on, launch, lights, windows, reversing, and even blinkers that Parisians try to avoid using for some odd reason, so yeah, 1335 lines, that’s not even a frame per second, something is missing) No DBC found on the interwebz for volkswagen’s AA/12 platform, so I’m in for making a first probably ? That is if the sole CANBus connected got anything worthy (OBDII vehicle module used) I have understood VAG cars are a bit different in a way, I wouldn’t be surprised accessing VW busses need a bit of help :) Anybody around with a bit of knowledge with these cars ? Best, JaXX./.

4 9

That nagging wifi won't reconnect problem
by Mark Webb-Johnson 11 Jul '19

11 Jul '19

I managed to recreate this (it is very rare for me), with logging enabled to SD CARD. Here is what I saw: 2019-07-07 21:37:13 HKT I (66811669) events: Signal(location.enter.honghay) 2019-07-07 21:37:14 HKT I (66813039) events: Signal(system.event) 2019-07-07 21:37:14 HKT I (66813099) events: Signal(system.wifi.scan.done) 2019-07-07 21:37:54 HKT I (66853039) events: Signal(system.event) 2019-07-07 21:37:54 HKT I (66853099) events: Signal(system.wifi.scan.done) 2019-07-07 21:37:54 HKT I (66853159) esp32wifi: Found SSID <REDACTED> - trying to connect 2019-07-07 21:37:57 HKT I (66855679) wifi: n:13 0, o:13 0, ap:255 255, sta:13 0, prof:1 2019-07-07 21:37:58 HKT I (66856619) wifi: state: init -> auth (b0) 2019-07-07 21:37:58 HKT I (66856679) wifi: state: auth -> assoc (0) 2019-07-07 21:37:58 HKT I (66856749) wifi: state: assoc -> run (10) 2019-07-07 21:37:58 HKT I (66856809) wifi: connected with <REDACTED>, channel 13 2019-07-07 21:37:58 HKT I (66856859) wifi: pm start, type: 1 2019-07-07 21:37:58 HKT I (66856919) events: Signal(system.event) 2019-07-07 21:37:58 HKT I (66856989) events: Signal(system.wifi.sta.connected) ... 2019-07-07 21:37:59 HKT I (66858139) events: Signal(system.event) 2019-07-07 21:37:59 HKT I (66858199) events: Signal(network.interface.up) 2019-07-07 21:37:59 HKT I (66858269) events: Signal(system.wifi.sta.gotip) So, I drive home, it does a wifi.scan, finds my home AP, connects, and all is ok. Then, in the middle of the night: 2019-07-08 03:03:53 HKT I (86400639) housekeeping: 2019-07-08 03:03:53 HKT (RAM: 8b=113788-132640 32b=22276) 2019-07-08 03:03:53 HKT I (86401049) ota: AutoFlash: Update ota_0 to 3.2.002-111-gac15fe8 (api.openvehicles.com/firmware/ota/v3.1/edge/ovms3.bin) 2019-07-08 03:03:53 HKT I (86401109) events: Signal(notify.info.ota.update) 2019-07-08 03:03:53 HKT I (86401109) ovms-server-v2: Send MP-0 PINew OTA firmware 3.2.002-111-gac15fe8 is available for download 2019-07-08 03:03:54 HKT I (86401269) ota: AutoFlash: Preparing flash partition... 2019-07-08 03:04:08 HKT I (86403399) wifi: bcn_timout,ap_probe_send_start 2019-07-08 03:04:11 HKT I (86405949) wifi: ap_probe_send over, resett wifi status to disassoc 2019-07-08 03:04:11 HKT I (86406009) wifi: state: run -> init (1) 2019-07-08 03:04:11 HKT I (86406049) wifi: pm stop, total sleep time: 18482424110 us / 19572759396 us 2019-07-08 03:04:11 HKT I (86406109) wifi: n:13 0, o:13 0, ap:255 255, sta:13 0, prof:1 2019-07-08 03:04:11 HKT I (86406159) events: Signal(system.event) 2019-07-08 03:04:11 HKT V (86406159) ovms-server-v2: OvmsServerV2MongooseCallback(MG_EV_CLOSE) 2019-07-08 03:04:11 HKT I (86406159) ota: AutoFlash:: Download complete (at 5385 bytes) 2019-07-08 03:04:11 HKT I (86406219) events: Signal(system.wifi.sta.disconnected) 2019-07-08 03:04:11 HKT I (86406319) ovms-server-v2: Status: Disconnected 2019-07-08 03:04:11 HKT E (86406369) ota: AutoFlash: Download file size (5385) does not match expected (2537376) 2019-07-08 03:04:11 HKT I (86406419) netmanager: WIFI client down (with MODEM down): network connectivity has been lost 2019-07-08 03:04:11 HKT I (86406519) esp_image: segment 0: paddr=0x00410020 vaddr=0x3f400020 size=0xc9c98 (826520) map 2019-07-08 03:04:12 HKT I (86406579) esp32wifi: STA disconnected with reason 200 2019-07-08 03:04:12 HKT I (86406739) events: Signal(network.wifi.down) 2019-07-08 03:04:12 HKT I (86406829) events: Signal(server.v2.waitreconnect) 2019-07-08 03:04:12 HKT I (86406919) events: Signal(network.down) ... 2019-07-08 03:04:12 HKT I (86407379) events: Signal(server.v2.waitnetwork) 2019-07-08 03:04:48 HKT I (86443029) events: Signal(system.event) 2019-07-08 03:04:48 HKT I (86443099) events: Signal(system.wifi.scan.done) 2019-07-08 03:05:11 HKT I (86466139) event: station ip lost 2019-07-08 03:05:11 HKT I (86466189) events: Signal(system.event) 2019-07-08 03:05:28 HKT I (86483029) events: Signal(system.event) 2019-07-08 03:05:28 HKT I (86483089) events: Signal(system.wifi.scan.done) 2019-07-08 03:06:08 HKT I (86523029) events: Signal(system.event) 2019-07-08 03:06:08 HKT I (86523089) events: Signal(system.wifi.scan.done) 2019-07-08 03:06:48 HKT I (86563029) events: Signal(system.event) 2019-07-08 03:06:48 HKT I (86563089) events: Signal(system.wifi.scan.done) 2019-07-08 03:07:28 HKT I (86603029) events: Signal(system.event) 2019-07-08 03:07:28 HKT I (86603089) events: Signal(system.wifi.scan.done) 2019-07-08 03:08:08 HKT I (86643029) events: Signal(system.event) 2019-07-08 03:08:08 HKT I (86643089) events: Signal(system.wifi.scan.done) 2019-07-08 03:08:48 HKT I (86683029) events: Signal(system.event) 2019-07-08 03:08:48 HKT I (86683089) events: Signal(system.wifi.scan.done) 2019-07-08 03:09:06 HKT I (86700639) housekeeping: 2019-07-08 03:09:06 HKT (RAM: 8b=113788-144368 32b=22276) And from then on, the wifi scan cannot see the AP. It is not a solution, but a clue as to at least one cause of these problems. From what I can see, the wifi got starved of CPU during that horribly long flash erase process, then wifi connection went down, OTA update failed, and it wasn’t recoverable from there. Perhaps if the STA gets disconnected (always, or just with reason 200?) we should reset the wifi stack? The root cause of that esp_ota_begin() starving the wifi during erase of the 4MB partition would also be good to address. Regards, Mark.

1 0

BUG? in v3.2.0-1 in vehicle_mitsubishi - flood of BMS-error msg
by Michael Eric Menk 11 Jul '19

11 Jul '19

There is a bug in MIEV code, that bombs the web GUI and phone APP with BMS errors. I suspect that this is because the Peugeot and Citroen branded MIEVs have a 80 cell battery pack vs MIEVs 88cells. Sample of a message: > Voltage: SD=1mV OK > Temperature: SD=1.4C !6:+3.1C !16:+3.1C !18:+3.1C The missing cells could also be used to set the voltage gauge. There are two LEV50-4 missing in the 80 cell pack, number 06 and 12. If a flagg is set while looping the CAN massages, then the flag can be used inside OvmsVehicleMitsubishi::GetDashboardConfig to set correct voltage. The float charge voltage of the 80 cell pack is 328.4 volt

3 15