Skip to content

VW UP very often "failed to start charge" with 3.3.005-3-g4f3f7688 #1264

@magicWF

Description

@magicWF

Hello.

after the OTA firmware update from 08.09.2025 I get very often the response "failed to start charge" when I will start charging. After a reboot of the OVMS the charging starts immediately.

`Last boot was 13684 second(s) ago
Time at boot: 2025-11-20 19:41:05 CET
This is reset #142 since last power cycle
Detected boot reason: Crash (12/12)
Reset reason: Unknown/unset (0)
Crash counters: 3 total, 0 early

Last crash: abort() was called on core 1
Current task on core 0: IDLE0, 516 stack bytes free
Current task on core 1: OVMS Events, 3636 stack bytes free
Backtrace:
0x4008ddae 0x4008e277 0x400ed6ed 0x400ef45c 0x4011758f 0x401720cd 0x4016d5b2 0x4012255e 0x40122979 0x40122d68 0x40122ded
Event: ticker.1@ovms-server-v2 5 secs
Version: 3.3.005-3-g4f3f7688/ota_1/main (build idf v3.3.4-851-gfa4f07fb3b Sep 7 2025 08:02:51)

Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600
Firmware: 3.3.005-3-g4f3f7688/ota_1/main (build idf v3.3.4-851-gfa4f07fb3b Sep 7 2025 08:02:51)
Running partition: ota_1
Boot partition: ota_1
Factory image: 3.3.001-33-g58d01654
OTA_O image: 3.3.005-2-g40245d7b
OTA_1 image: 3.3.005-3-g4f3f7688`

Perhaps someone has some idea.

Today I switched to OTA_O Image. I will observe it the next time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions