[Ovmsdev] OVMS v2 crashing module

[Michael Balzer]

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
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Am Rahmen 5 * D-58313 Herdecke
Fon 02330 9104094 * Handy 0176 20698926


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20251227/a99476ff/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20251227/a99476ff/attachment-0001.sig>