Mark and all,
Thanks so much for all your work on OVMS. It's allowing me to limit the maximum battery charge on my Leaf and save my battery. I'm quite happy with it.
That said, I have a crash in the vehicle module history, and thought you might want it. It's possible it was due to an electrical disconnect or something else--my vehicle was at the mechanic's when this happened. Wanted you to have it, in case it would help!
Last boot was 1423983 second(s) ago Time at boot: 2024-08-12 09:54:58 CDT This is reset #3 since last power cycle Detected boot reason: Crash (12/12) Reset reason: Exception/panic (4) Crash counters: 3 total, 0 early Last crash: LoadProhibited exception on core 1 Registers: PC : 0x401328fd PS : 0x00060530 A0 : 0x80167f2c A1 : 0x3ffc87f0 A2 : 0x3f8b7bd0 A3 : 0x3f8b7b44 A4 : 0x000000b2 A5 : 0x0000ff00 A6 : 0x00ff0000 A7 : 0xff000000 A8 : 0x05706374 A9 : 0xbaad5678 A10 : 0x66ba2232 A11 : 0x41d9ae88 A12 : 0x0000001f A13 : 0x66ba2232 A14 : 0x7ff00000 A15 : 0x7ff9ae88 SAR : 0x00000001 EXCCAUSE: 0x0000001c EXCVADDR: 0x0570637c LBEG : 0x400029ac LEND : 0x400029cb LCOUNT : 0x00000000 Current task on core 0: IDLE0, 524 stack bytes free Current task on core 1: OVMS Events, 3932 stack bytes free Backtrace: 0x401328fd 0x40167f29 0x40169f09 0x4016c44a 0x40167a0e 0x4011f1da 0x4011f3a9 0x4011f490 0x4011f519 Event: ticker.1@ovms-server-v2 0 secs Version: 3.3.004-4-gab8f16b7/ota_0/main (build idf v3.3.4-849-g6e214dc335 Mar 30 2024 08:08:21) Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3
My vehicle module stopped communicating with the server. The app said it hadn't checked in 12 hours, so I went to look at its status page and the website for the vehicle module would not load.
My router said its IP address was allocated to Expressif Inc.
I power cycled the unit and it came right up. Checked in with my server and the vehicle module website is working as expected.
I have automatic power management disabled, the 12v shutdown voltage is 11.5, the wakeup voltage is 11.9, and my 12v battery is reading 13v. I calibrated the battery, so I don't think it was a low voltage shutdown.
Any ideas?
Device just crashed again. Although I have the charge limit set to 69%, the car charged to 100% overnight. Checking on the module it wasn't checking into the server and the vehicle module webpage wasn't responding.
Is it normal for modules to crash this much?
Last boot was 117193 second(s) ago
Time at boot: 2024-10-13 15:26:20 CDT
This is reset #69 since last power cycle
Detected boot reason: Crash (12/12)
Reset reason: Exception/panic (4)
Crash counters: 69 total, 0 early
Any way to stop the crashing?
Not sure if this helps find a root cause, but my module just crashed again when I hit stop v2 and start v2:
Last boot was 9 second(s) ago
Time at boot: 2024-10-15 00:15:24 CDT
This is reset #70 since last power cycle
Detected boot reason: Crash (12/12)
Reset reason: Exception/panic (4)
Crash counters: 70 total, 0 early
Maybe it's related to this issue? https://www.openvehicles.com/node/4234
The module wasn't working, online, or doing anything, so I connected via USB. Specifically:
The LothOVMS wireless network was not appearing on my phone (the wifi SSID that the OVMS broadcasts)
The OVMS was not available on its dedicated IP address on my local network
The moment I connected via USB, I got the following output:
ets Jul 29 2019 12:21:46
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 (1137) psram: This chip is ESP32-D0WD
I (1137) spiram: Found 64MBit SPI RAM device
I (1137) spiram: SPI RAM mode: flash 40m sram 40m
I (1140) spiram: PSRAM initialized, cache is in low/high (2-core) mode.
I (1148) cpu_start: Pro cpu up.
I (1151) cpu_start: Application information:
I (1156) cpu_start: Project name: ovms3
I (1161) cpu_start: App version: 3.3.004-4-gab8f16b7
I (1167) cpu_start: Compile time: Mar 30 2024 08:08:20
I (1173) cpu_start: ELF file SHA256: e535c0258e142c2b...
I (1179) cpu_start: ESP-IDF: v3.3.4-849-g6e214dc335
I (1186) cpu_start: Starting app cpu, entry point is 0x400818d8
I (0) cpu_start: App cpu up.
I (2063) spiram: SPI SRAM memory test OK
I (2064) heap_init: Initializing. RAM available for dynamic allocation:
I (2064) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (2070) heap_init: At 3FFC1ED8 len 0001E128 (120 KiB): DRAM
I (2077) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (2083) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (2090) heap_init: At 4009CCC8 len 00003338 (12 KiB): IRAM
I (2096) cpu_start: Pro cpu start user code
I (2101) spiram: Adding pool of 4096K of external SPI memory to heap allocator
I (151) ovms_main: Set default logging level for * to INFO
I (152) ovms_main: WATCHDOG already initialized...
I (152) ovms-duktape: Initialising DUKTAPE Registry (1000)
I (159) command: Initialising COMMAND (1010)
I (164) command: Expanding DUKTAPE javascript engine
I (169) boot: Initialising BOOT (1100)
I (173) boot: Power cycle reset detected
I (178) events: Initialising EVENTS (1200)
I (183) config: Initialising CONFIG (1400)
I (188) time: Initialising TIME (1500)
I (193) script: Initialising SCRIPTS (1600)
I (197) ovms-duk-http: Installing DUKTAPE HTTP (1710)
I (203) ovms-duk-util: Installing DUKTAPE Utilities (1710)
I (209) ovms-duk-vfs: Installing DUKTAPE VFS (1710)
I (214) metrics: Initialising METRICS (1810)
...
Now it's online, communicating with my server, pingable at its IP address, and broadcasting its own access point. It looks like connecting via USB caused it to reboot. 12V is 12.3V. Any ideas what could be going on?
Its status is this:
Last boot was 531 second(s) ago
Time at boot: 2024-10-22 23:28:40 CDT
This is reset #0 since last power cycle
Detected boot reason: PowerOn (1/14)
Reset reason: Unknown/unset (0) Crash counters: 0 total, 0 early
12v shutdown is 11.5
12v alert is 1.6 below a reference of 12.6
12v wakeup is 11.9
Wakeup test interval is 240s
Battery is showing 12.4 according to multimeter and OVMS (I calibrated the 12v battery)
Serial connector is screwed in, so it's getting power both from USB and from serial. I disconnected the USB and it's still staying on now.