[Ovmsdev] OVMS v2 crashing module

Mark Webb-Johnson mark at webb-johnson.net
Mon Dec 29 07:49:26 HKT 2025


Aaron,

I see that you don’t have DNS configured. Best to set that as 8.8.8.8 to avoid issues with switching between wifi and cellular dns providers.

Please also check to ensure that you don’t have any custom scripts configured.

Regards, Mark.

> On 28 Dec 2025, at 12:24 AM, Aaron Carson <aaron at aaroncarson.co.uk> wrote:
> 
> Hi both,
> 
> Thanks very much for getting back to me so quickly!
> 
> I have now tried turning off TLS/SSL - and unfortunately it crashed immediately upon hitting start server.
> 
> Module summary is below. If anything obviously wrong sticks out, I’d be very appreciative if you could spare the time to check and let me know.
> 
> I’ll catch the USB logs as soon as I can - same with a NONE vehicle, haven’t tried any of that yet. It might well be that any issues make themselves obvious at that point! 
> 
> Thanks again - really excited for the potential of OVMS!
> 
> Aaron
> 
> ———
> 
> OVMS MODULE SUMMARY
> 
> Module
>   Version:  3.3.005-536-g20a42926/ota_1/edge (build idf v3.3.4-851-gfa4f07fb3b Dec 25 2025 16:43:35)
>   Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600
>   Free RAM: 8bit=57212-58652 32bit=12128 SPIRAM=3225048-3244984 bytes
>   12V:      11.9V
> 
> Storage
>   /store:  Size:    976 kB  Avail:    896 kB  Used:   9%
>   
> WIFI Status
>   Power: on
>   Mode: Access-Point + Client mode
>   
>   STA SSID: **redacted** (-78.2 dBm) [fixed]
>     MAC: 00:4b:12:...
>     IP: 10.75.0.247/255.255.0.0
>     GW: 10.75.0.1
>     AP: ba:fb:e4:c4:1b:6f
>   
>   AP SSID: **redacted** (20 MHz, channel 6)
>     MAC: 00:4b:12:...
>     IP: 192.168.4.1
>     AP Stations: 0
>   
> MODEM Status
>   Model: SIM7600
>   Revision: 
>   Network Registration: Unknown
>     Provider: 
>     Signal: 0 dBm
>     Mode: 
>   State: PoweredOn
>     Ticker: 0
>     User Data: 0
>   UART:
>     FIFO overflows: 0
>     Buffer overflows: 0
>     Parity errors: 0
>     Frame errors: 0
>     Driver Buffer overflows: 0
>     State Timeout Goto: PoweringOn (in 40 seconds)
>   Mux: Not running
>   PPP: Not running
>   GPS: Not running
> 
> Configuration
>   [auto]
>     dbc: no
>     egpio: no
>     ext12v: no
>     init: yes
>     modem: yes
>     obd2ecu: 
>     ota: yes
>     scripting: yes
>     server.v2: no
>     server.v3: no
>     vehicle.type: SQ
>     wifi.mode: apclient
>     wifi.ssid.ap: **redacted**
>     wifi.ssid.client: **redacted**
>   [can]
>   [dbc]
>   [egpio]
>     monitor.ports: 
>   [http.plugin]
>   [http.server]
>   [locations]
>     Home: **redacted**
>   [log]
>   [modem]
>     apn: hologram
>     apn.password: 
>     apn.user: 
>     enable.gps: yes
>     enable.gpstime: yes
>     enable.net: yes
>     enable.sms: yes
>     gps.parkpause: 600
>     gps.parkreactawake: yes
>     gps.parkreactivate: 50
>     gps.parkreactlock: 5
>     net.type: auto
>     pincode: 
>   [module]
>     cfgversion: 2022121400
>     init: done
>   [network]
>     dns: 
>     modem.sq.bad: -103
>     modem.sq.good: -93
>     type: 4G
>     wifi.ap2client.enable: yes
>     wifi.sq.bad: -95
>   [notify]
>   [obd2ecu]
>   [obd2ecu.map]
>   [ota]
>     auto.allow.modem: no
>     auto.hour: 2
>     http.mru: https://ovms.dexters-web.de/firmware/ota/v3.3/edge/ovms3.bin
>     server: https://ovms.dexters-web.de/firmware/ota
>     tag: edge
>   [password]
>     module: **redacted**
>     pin: **redacted**
>     server.v2: **redacted**
>     server.v3: **redacted**
>   [plugin]
>   [plugin.disabled]
>   [plugin.enabled]
>   [plugin.repos]
>   [power]
>   [pushover]
>   [sdcard]
>     maxfreq.khz: 20000
>   [server.v2]
>     port: 
>     server: ovms.dexters-web.de
>     tls: no
>     updatetime.connected: 
>     updatetime.idle: 
>     workaround.ios_tpms_display: no
>   [server.v3]
>     events.legacy_topic: yes
>     metrics.exclude: 
>     metrics.exclude.immediately: 
>     metrics.include: 
>     metrics.include.immediately: 
>     metrics.priority: 
>     port: 8883
>     queue.modified: 
>     queue.sendall: 
>     server: ovms.dexters-web.de
>     tls: yes
>     topic.prefix: 
>     updatetime.awake: 
>     updatetime.charging: 
>     updatetime.connected: 
>     updatetime.idle: 
>     updatetime.immediately: no
>     updatetime.keepalive: 1740
>     updatetime.on: 
>     updatetime.priority: no
>     updatetime.sendall: 
>     user: **redacted**
>   [ssh.info]
>     fingerprint: wNr7F8DCIPXn12my8kyX3W/E9Zl9CqeiMf/eYRjWdn8
>   [ssh.keys]
>   [ssh.server]
>     key: **redacted**
>   [system.adc]
>     factor12v: 195.7
>   [tpms]
>   [usr]
>   [vehicle]
>     12v.alert: 0.8
>     12v.ref: 
>     12v.shutdown: 
>     12v.shutdown_delay: 
>     12v.wakeup: 
>     12v.wakeup_interval: 
>     flatbed.alarmdistance: 
>     flatbed.alarminterval: 
>     id: **redacted**
>     name: Momo
>     stream: 10
>     timezone: GMT0BST,M3.5.0/1,M10.5.0
>     timezone_region: Europe/London
>     tpms.fl: 0
>     tpms.fr: 1
>     tpms.rl: 2
>     tpms.rr: 3
>     units.accel: miphps
>     units.accelshort: ftpss
>     units.consumption: mipkwh
>     units.distance: M
>     units.distanceshort: feet
>     units.speed: miph
>     valet.alarmdistance: 
>     valet.alarminterval: 
>   [wifi.ap]
>     **redacted**: **redacted**
>   [wifi.ssid]
>     **redacted**: **redacted**
>   [xsq]
>     12v.charge: yes
>     bcvalue: no
>     canwrite: yes
>     cfg.preset.ver: 7
>     extended.stats: yes
>     full.km: 126
>     led: no
>     modem.check: no
>     rebootnw: 0
>     reset.notify: yes
>     resettotal: no
>     resettrip: no
>     tpms.alert.enable: yes
>     tpms.front.pressure: 225
>     tpms.rear.pressure: 255
>     tpms.value.alert: 50
>     tpms.value.warn: 30
>     unlock.warning: yes
> 
> REPORT ENDS
> 
>> On 27 Dec 2025, at 14:50, Michael Balzer via OvmsDev <ovmsdev at lists.openvehicles.com> wrote:
>> 
>>  Welcome, Aaron.
>> 
>> Sorry, no idea about the crash, the V2 client is normally very stable and tolerates all kinds of misconfigurations.
>> 
>> Please catch the USB console log during a crash, which will likely show crash details. We try to carry crash details over the reboot in SRAM, but that doesn't work under all circumstances.
>> 
>> Check the log for any warnings or error indicators. Possibly try log level debug or verbose to see more details.
>> 
>> Also, do you actually need the car connection to reproduce the crash, and does it only occur with the SQ vehicle, or does it also happen with e.g. the NONE vehicle on your desk?
>> 
>> Regards,
>> Michael
>> 
>> 
>> Am 27.12.25 um 14:33 schrieb Aaron Carson via OvmsDev:
>>> Hi folks,
>>> 
>>> Hope you’re all keeping well and that your holidays have been lovely so far! 
>>> 
>>> I’ve been watching the OVMS project for just over a year since Mercedes announced they were going to shut down the Smart EQ servers (UK 453 Brabus). Then, we got my mum a module for Christmas so finally getting to play with it properly 😄 
>>> 
>>> However, I’m having some trouble with the V2 server. I’m using Dexter’s cloud server for now (thank you for hosting it!) with the aim to set Mum up with the Quarz iOS app (https://apps.apple.com/gb/app/quarz/id6740280553). 
>>> 
>>> If I start V2 on the module, it either crashes instantly or does so within a few minutes. If I enable autostart on it, it boot loops for a minute and then needs a manual reboot. Not so bad in the summer but having to go back outside to the car in 1°C weather isn’t my idea of fun 😂 
>>> 
>>> Problem is: when it crashes, there’s no crash data.
>>> 
>>> Last crash: IllegalInstruction exception on core 0
>>>  
>>> Registers:
>>>  
>>> PC : 0x00000000
>>> PS : 0x00000000
>>> A0 : 0x00000000
>>> A1 : 0x00000000
>>> A2 : 0x00000000
>>> A3 : 0x00000000
>>> A4 : 0x00000000
>>> A5 : 0x00000000
>>> A6 : 0x00000000
>>> A7 : 0x00000000
>>> A8 : 0x00000000
>>> A9 : 0x00000000
>>> A10 : 0x00000000
>>> A11 : 0x00000000
>>> A12 : 0x00000000
>>> A13 : 0x00000000
>>> A14 : 0x00000000
>>> A15 : 0x00000000
>>> SAR : 0x00000000
>>> EXCCAUSE: 0x00000000
>>> EXCVADDR: 0x00000000
>>> LBEG : 0x00000000
>>> LEND : 0x00000000
>>> LCOUNT : 0x00000000
>>>  
>>> Backtrace: 
>>>  
>>> Version: 3.3.005-536-g20a42926/ota_1/edge (build idf v3.3.4-851-gfa4f07fb3b Dec 25 2025 16:43:35)
>>>  
>>> Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600
>>> 
>>> Despite all this, I’m having no such issues with V3/MQTT. I’m happy to use that - and I intend to integrate it with Home Assistant so probably would aim for that in general, but the data usage is *so* much lower on V2 - and with a Hologram SIM, that’s pretty important - that I’d have preferred to go down that path.
>>> 
>>> Any ideas as to why it could be crashing?
>>> 
>>> Best wishes and kind regards,
>>> 
>>> Aaron
>>> 
>>> Aaron Carson (he/him)
>>> ✉️ : aaron at aaroncarson.co.uk <mailto:aaron at aaroncarson.co.uk>
>>> 💻 : aaroncarson.co.uk <https://www.aaroncarson.co.uk/>
>>> 🔑 : 715E 0332 F7E1 E0F1 <https://keys.openpgp.org/vks/v1/by-fingerprint/45982EB56486CED008DAED0D715E0332F7E1E0F1>
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>> 
>> -- 
>> Michael Balzer * Am Rahmen 5 * D-58313 Herdecke
>> Fon 02330 9104094 * Handy 0176 20698926
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>> <OpenPGP_signature.asc>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20251229/cb7cf5b5/attachment-0001.htm>


More information about the OvmsDev mailing list