7 posts / 0 new
Last post
3.2.014 Very unstable

Anyone having stability problems? I find the module often freezes up, requiring unplugging to get it to reset. Seen many restarts due to crashes as well, but at least it recovers from these. Wondering if maybe I could have a bad module or cable. Seems to be completely stable with the car off - can connect and completely reliable. I've tried disabling the wifi and modem independently, as it usually seems to freeze as soon as I leave home. Makes it seem like it has something to do with the networking, but seems to happen with either disabled.

Is this unusual, or known problems? I don't see much in the way of bugs for it freezing up, which makes me wonder if it's something to do with my module or setup. I also see TONS of can2 errors while the car is running, but not sure if that's even related.

The car is a 2015 Leaf, and all the config looks to be set correctly.

sdarveau's picture
Same problem with same car

Same problem with same car here. I finally decided to revert the firmware to previous version and it's working fine again. This issue has been introduced in

There are a number of fixes

There are a number of fixes now in the latest 'edge' version to improve stability, including the ability to turn off canwrites (previous versions would still send TX writes irrespective of whether this was unticked). Let me know how you get on as I can only test on a 30kWh 2016 Leaf.

markwj's picture
3.2.015 (in EAP) should

3.2.015 (in EAP) should resolve this issue affecting Nissan Leaf vehicle module.

Thanks, it does resolve the

Thanks, it does resolve the freezing, which was the worst. Still get semi-frequent reboots, but since it automatically recovers those aren't that big of a problem. Guess there's still a lot of work and moving pieces in play.

3.2.015 stable still freezes with my 2016 30kWh Leaf

Should I try a pre-14 version?  14 was the first that I tried, I've only had this for a month or so.

It's quite irritating to having to remember to unplug OVMS every evening. Otherwise it won't connect in the morning - or if it amazingly does after one night, it won't after another.
I have the 4G SIM paused due to a lot of data usage (another thread, still haven't figured where I should log what) , is this part of the problem?

Since the wifi doesn't work with any of my three routers (a third thread), I turn the hotspot on from my phone and when OVMS has not yet crashed it connects nicely through the phone. So I can turn on first charging two times (the first propably wakes up the car) and then heating. As documented for the 2016 model the heating cannot be started without charging, which sucks but maybe there will be a solution to that some day. I could try and find the time to look at it myself, but I'm not sure I understand enough of CAN traffic. The original Nissan system was able to start heating even without the cable, but Nissan can't get it working for me anymore... and OVMS would be much faster and better if only it would work. :)

Now it seems that OVMS doesn't crash completely, it just fails to connect to my phone wifi hotspot and also the AP is not working (I keep it in the apclient mode to have options). So the car wifi network doesn't show up in a wifi scan when the crash has occurred.

However, when I connect through the USB cable I am able to connect with the console, also this seems to put OVMS back together as it works after connecting with the console.
The output on the console is:

W (3510) script: DuktapeDispatch: msg type 3 lost, queue full
W (3510) script: DuktapeDispatch: msg type 3 lost, queue full
I (3520) ovms-mdns: Starting MDNS
Firmware: 3.2.015/ota_0/main
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1

I (3530) script: Duktape: Creating heap
W (3540) script: DuktapeDispatch: msg type 3 lost, queue full
I (3540) webserver: Launching Web Server
I (3550) ssh: Launching SSH Server
W (3560) script: DuktapeDispatch: msg type 3 lost, queue full
I (3640) script: Duktape: Initialising module system
I (11070) housekeeping: System considered stable (RAM: 8b=98336-99760 32b=9576)


Now how to make this a bit more robust?

Is there a 'cron' in OVMS that could start this Duktape-skript once an hour, or once in 12 hours or whatever so that the box would stay available?

I've been thinking about a hardware 12V timer to cut the voltage, but those seem a bit expensive and complicated. I have a manual switch, but I haven't bothered installing it yet since the cabling is a bit hard to reach - the ODB cable in the car is very short. Maybe I'll have to get an extension or a splitter, to even allow for the use of Leafspy simultaneously.

dexter's picture
3.2.015 stable still freezes with my 2016 30kWh Leaf

3.2.015 is generally more stable than the previous versions. Leaf issues need to be addressed by the Leaf developers.

Your console log is a boot log, i.e. the module just rebooted. You can see that from the timestamps and the line "housekeeping: System considered stable", which is logged ~ 10 seconds after the system init. So that looks like you somehow triggered a reboot by connecting, which also means reinit of the Wifi subsystem.

On how to install "cron" scripts, see: https://docs.openvehicles.com/en/latest/userguide/events.html

But I think you'd better provide details (i.e. module summary + daily logs) to the Leaf team, so they can see what's going wrong first place.


Log in or register to post comments