Nissan Leaf Climate Control command not working #804
Comments
|
I just reverted to the main firmware and I can also confirm that the issue is resolved by reverting to the main firmware version. When I switch it back to the newest firmware, the problem comes back. Also, I tried setting in the car when sending the command, and I can hear the car close and then open some relays, but the HVAC system never illuminates or does anything on the dash like it normally would when you use the remote command. |
|
|
Factory firmware image that works; 3.3.001-33-g58d01654 After switching between all of the firmware types to get the firmware info, it seems to work now, but that's with the network awake. Every time I've had an issue, it's been with it asleep. I'll try it again after it goes to sleep. I've never seen any crash details as I haven't seen a crash per-se. When you would send the command, the car just wouldn't respond appropriately. This is the log I have from just now, but as I said, it "failed to fail" this time. I'll try again later. |
|
Hi, I see the last change to NL code was over a year ago. But it could be that the users usually dont use OTA feature and this got unnoticed. I will verify it myself and check at which change it stopped working. Meanwhile @nismoman240sx, have you tried to change model year in settings to like 2013 or 2018 to see if that helps? |
|
The vehicle is a 2015, but was built in 2014, so I did try to change it to 2014, but at that time, it didn't change anything. I didn't try any other years. I will try that. |
|
I just sent the command from the app after letting the car and app set unused from yesterday and it's worked fine. I tried rebooting the module multiple times before posting here and it didn't fix the issue, but yesterday was the first time I tried reloading the firmware. I wonder if something about the most recent OTA update didn't load correctly? I've had the issue for quite a while, I just didn't know I had to post here to get it resolved until yesterday. I'll keep an eye on it and keep this post updated if anything changes, but as of right now, the firmware reloading seems to have resolved the issue. |
|
Good to hear that it works now! There were no changes to the Nissan Leaf funcitonality for over a year, so no recent changes could have caused than. Most liekely something with the firmware itself got corrupted so hard reset cleared the issue. |
|
Remote CC failed to work this morning from my app. I then logged in via the wifi network and attempted to send the command directly from the shell editor. It still failed to activate. I tried again with no effect. I then sent the command from the app a couple of times. Same result. I then tried to send the wakeup command from the app. The car won't wake up. Here is the log; |
|
I see the " OLD TCU on EV Bus" line repeated. Could it mean that I don't have the TCU properly unplugged? I thought I just unplugged everything, but maybe I'm remembering incorrectly? |
|
I see similar behaviour as described. Dropped back to main and it worked well the first time, but never worked again. Soft resets didn't recover it, but a hard power reset did. Another 2015 model. |
|
I tried to get in to it again today to try messing with it again, and now the car's wifi network is gone. I've tried on my phone, my laptop, and my PC. None of them can find it now. I'm going to go get an SD card today and start logging to it to try to get more debugging information. |
|
There are others having issues as well now. Not with just the HVAC controls, but the OVMS unit no longer communicating via cellular or Wi-Fi. One user seemed to think that the EDGE firmware caused the issue and that moving to EAP resolved the issue. |
|
@nismoman240sx, I don't have my Leaf currently. Will have it back in a week so can retest. I recently also had some strange issues with OVMS. I did a hard reset and installed Latest |
|
I finally found time to get the OVMS unit pulled out so I could do a factory reset on it. So far, it seems to be working again, but we'll see how long it lasts. I'll come back and close this if it doesn't act up again. |
|
Annnd it's not working again. I didn't bother downloading the logs again, as it's the EXACT same log output as before. What it appears to be trying to do is to get the car to wake up so it can activate the climate control, but the car just seems to refuse to wake up. Even sending the wakeup command by itself will not wake up the car. I'm starting to lean towards a hardware issue, but the fact that rebooting gets it to work for a bit makes me question that. |
|
I have some different information now. I've got the issue narrowed down to something repeatable. First of all, the firmware versions I've tested this with are the same as above. The issue is repeatable across firmware versions. If you reboot and then watch the log monitor you can see something odd happening. So the first few times you send the climatecontrol on and off commands, it will work, but there are "errors" reported in the log. Then the commands stops working, but the errors also stop. It appears to me to be associated with the Wakeup Frame. This log happens to be with the latest main firmware, but it's the same for all version. This log is immediately after a reboot. Log Monitor |
|
I don't know if that's related to your Leaf issue, but the CAN1 error flags switching from 0x8… to 0x4… indicates a permanent bus-off state. I'm having the very same CAN1 issue after switching Wifi AP mode off. Did you change anything about your Wifi config lately? I posted my findings on the developer list and implemented a workaround, which is included in the current edge build. The workaround detects the issue and performs a bus reset to solve it. Please try. See also http://lists.openvehicles.com/pipermail/ovmsdev/2023-January/016070.html |
|
I haven't made any changes before the issue started. The module has been set to WiFi AP + client mode since the day it was installed and I've never changed that. I installed the latest edge version firmware and tested. Here's the log from the shell monitor after updating firmware; As you can see, the only issue occurs when the first "climatecontrol on" command is sent, and it's different than the other errors seen when using the "main" firmware version. After that first set of errors, no errors are ever reported again. Also, I noticed today, that if the car is plugged in, there are never error codes when the command is sent, but when it's unplugged is when the errors are reported. I'm going to leave it set on "edge" firmware for now and see how it does. I'll report back in a week or so regardless of how it's acting to keep everyone updates. So far, this latest firmware seems to resolve the issue. |
|
Still not working right. I went to start the car today as it's cold and icy out. Remote CC command would not work. I even restarted the module and it still wouldn't work. I had to go out to the car and just start it to get it going to melt the ice off the car and warm up. Here are the logs; Then, I restarted the module and tried again. It still wouldn't start the climate control, but the error logs were different this time. I can see where the bus reset command from the edge update, but it's not working right. I (214649) webserver: HTTP GET /shell |
|
As of this morning the OVMS unit has stopped all communication with the app again and I can't log into it via wifi. My wife has the car right now, but when she get back I'll do another hard reset. Is it possible that I have a hardware issue? |
|
Doing another factory reset today to get it working again. I pulled this off of the SD card I had installed. It was inside a file called "can.crtd" Whatever is wong seems to be with the write process to the can. Assuming I can get it working again with a factory reset, I'm not going to send the ClimateControl command and see if the issue comes back or not. |
|
I got the OVMS module working again. I didn't have to factory reset, a power cycle was able to get it communicating again. I also got the micro SD card set up so that it's giving verbose logs on everything now. I also altered some other settings. I noticed that it wasn't staying connected to wifi because I had the connections limits set too tightly. I loosened them up to see if that will keep it from switching back and forth between wifi and cellular. Somehow my 12v offset was wrong too, so I got that fixed as well. I also updated to the update that went out today. I don't think any of the updates have anything to do with the Leaf, but I figured it couldn't hurt. I went ahead and sent the climate control command and I didn't see any errors in the logs this time, so we'll see if I've somehow fixed it. If it happens again, I should have very complete logs now instead of what I was just able to pull from the shell monitor from my phone. |
|
You can trace back the changes made to the CAN interface and Leaf adapter here:
I don't see any changes there that could explain your issue, but maybe your new logs can will show something helpful. Btw, you can attach files instead of copying them into the text. |
|
I'm also still seeing the issue. Today I was able to get out and spend a bit of time with the car... add an SD card to the OVMS module, and then also give the leaf a proper power cycle just in case that helped (it didn't). I have noticed recently that when the climate command does work, the it stays running (doesn't timeout after 15 mins when on battery - it used to). I always thought this 15 minute timer was done by the car, not OVMS... so not quite sure why it's being tricky. Hopefully when it happens again the logs will show it. |
|
I'm still trying to catch it on the logs. I thought I had it logging correctly, but I screwed up a setting and ended up with close to a hundred files, so finding the fault in the logs was too much work. I deleted everything, got the settings right, and started over again, and now it's working fine. I'm sure it'll mess up again, but when it does, it'll be easier to find it in the logs. Also, it hasn't been consistent, but I did have a couple of times that the CC didn't shut off as well. Again, all of this is relatively recent behavior. |
|
Another failure catching it in the logs. I can't see any reason why, but the OVMS stopped logging about a day before I got the failed "climatecontrol on" command. I had the file size set pretty high, so I cycled the power and changed the log file size to about half of what I had it. I'm keeping my fingers crossed that I'll be able to catch it this time. |
|
What options are you using for logging? I've put an 8GB uSD card in so should have plenty of space. I've currently got everything set to verbose and a 1mb file size. It's working, but catching a lot of irrelevant things so trying to narrow it down to the more useful items. |
|
The logging has failed again. It stopped logging on 3/11 and I tried to send the CC command this morning, 3/13. I'm using a 4GB uSD card. I initially had all of the settings set to default and the logs set to verbose. It created a BUNCH of log files so it made digging through all of them to find the faults a PITA. I increased the file size to 100MB from the default 1MB. It got to around 90MB and then stopped logging. I dropped it down to 50MB and it failed again. I've just reset everything back to factory settings again. It was at least working then. |
|
Hi guys, Also getting the "OLD TCU on EV Bus" messages. Climate control fires up, but no indication of running climate control on the Android OVMS app. I also note the "Auto Disable Climate Control" at the end of the attempts. I get similar results when trying to use the app based central locking (further research indicates that the OVMS central locking only works on later e-NV200s). I'll get an SD card and also attempt to log. I'm new to OVMS, so am in for a steep learning curve. Interestingly, if I start the remote climate control on the e-NV200 with the key fob button, and then try and kill it with OVMS, it won't. Likewise, if I turn it on with OVMS (and get no indication it's on w/ Android app - but it runs), then try and kill it with the fob, it won't. It's like the fob climate control is completely different to the OVMS climate control. The dash-top flashing LED works for both fob-initiated, and for OVMS-initiated climate control. I've just done an OVMS-initiated climate control on my van, and will see if it shuts off automatically in 15min. FW: |
|
OVMS initiated climate control time is the same as in the official Nissan app: 15 minutes when the car is unplugged and 2 hours if the car is plugged in. |
|
Just adding to this thread that I am getting the same issue on my 2013 Nissan Leaf with the TCU unplugged. I get the same output in the shell as everyone else in this thread. I bought this OVMS specifically for Climate Control support, so hoping this can be fixed. |
|
Don't know that I have a lot to add but I'll relate what I'm seeing on this particular issue. So I can, seemingly 100% reliably, get the climate to come on if I issue the command shortly after physically pulling it out and plugging the OVMS system back in. This is obviously not ideal. After remembering to stop by and see if I was the only one seeing this (and tripping over this issue thankfully), I tried from the app to start the climate control and was seeing the same thing that's reported above right down to the logs, so I won't repeat that. On a whim, and I feel like I've tried this before successfully, I rebooted the module from the web interface (since I'm home and that's not hard), waited a bit and for it to reconnect to my server and then issued the I haven't tried a newer firmware than the stock OTA 3.3.003 yet, but a hard pull and/or a module reboot both seem to get it back to a working state. It's unclear if that just causes a different signal on boot to wake up the appropriate CAN bus as it reconnects, or if this is something from a software perspective that can settle itself out. I will note that when I looked at |
|
(following subscribed) darn was about to purchase but noticed users reporting this bug on forum if fixed will purchase 4G kit for Leaf |
|
Adding that I have similar issue with my 2013 Nissan Leaf. Except I have never gotten it to work regardless of what firmware I’m on or if I’ve just rebooted etc… OVMS# climatecontrol on some other error codes i got other times: continued: |
|
Just adding a bit more to this... I'm still running Main... and the issues eventually returned as the weather got colder. It's been a frustrating winter with this. Another issue - which may or may not be part of this issue - is that the CC once enabled will sometime stay on permanently. I've bought a new SD card to start logging again - I had some very strange errors with my old card. |
I've had all of the exact same issues. I've stopped using the OVMS completely. I just need to remove it from the car at this point. After it ran the battery completely dead because it never turned off, I gave up on it ever working correctly. It's been over a year since I started posting about this and nothing has ever changed. I'd love for it to work correctly, as it wasn't exactly cheap, but I've written it off at this point that it will ever work correctly again. |
So, the CC being stuck on is what's prompted me to look further at this, knowing a bit about how the Leaf works. I'm running 3.3.001 now, and no errors so far. I also recall this was the case after flashing back to Main and it was a few days later before it started occurring. I don't know if it's an issue with the CAN part of my board or the firmware - but it was only flashing the firmware which would give me a few days grace. A power reset either soft or hard didn't have the same length of effect. |
|
I had the same experience. hard and soft resets wouldn't get it to work. Only a firmware update, and then it would only work for a short amount of time before not working anymore. I'm also sure from when I was still trying to get it to work, that it's nothing to do with the phone app, as I could recreate the same issues sending the CC command from the web interface. I am not a computer programmer by any means, but I have a firm enough grasp of how computers work that I think that, like you said, the OVMS is doing something that's causing the cars CAN bus to stop responding to certain messages. That being said, I'm not sure why an OVMS firmware update gets it to work again for a while. Though now that I'm thinking more about it, I feel like maybe that stopped working eventually too. I could be wrong on that. I gave up on it close to a year ago. |
|
After a few weeks of it working OK, the problem reoccurred this morning 3.3.001. I attempted to start CC with the car plugged in (but charger NOT active at that time of day, approx 08:05). This didn't work, so I rebooted the unit and CC worked upon reboot. The module responds in the OVMS app, but nothing from the car. I've managed to get the logfiles, it looks like there was a time drift issue before - you'll see the unit reboot then the time goes back about 20 mins. The 2nd half of the log is the correct time. |
|
As soon as sending the command this morning, the MCP2515 errors started. I wonder if it's hardware related, but seems unlikely at this stage? |
|
Is there a way to emulate a command coming from Nissan to the TCU instead of trying to emulate that command onto the bus? It seems like the commands that are being put into the bus aren't correct and it's causing the CC system to start ignoring them. I removed the OVMS this last weekend. I'll hang on to it for a bit to see if the developers can find a solution, but it doesn't look like this is even on their radar. |
|
It's bizarre that so many reports of this issue, however I've never once experienced any issues with my UK built 2014 AZE0. I use CC almost daily in winter. I'm running main 16th Jan 2022 FW. I wonder if there is some subtle variation between different countries? Assuming TCU is unplugged? |
|
Yes, TCU is unplugged (big connector, not the little one). UK based, 2015 UK built AZE0-1. The logs are definitely showing something is not happy on the car2 can. I really don't know if it's hardware - is there a way to loan a module to see if it reoccurs? I updated back to main last night - as the issues were clearly evident on 3.3.001 and 3.3.002 as well. Nissan have announced today the sunset of the original remote services from 1st April 2024 (what a date to pick!) so hopefully a few more OVMS modules will join the club (but not have these issues!). |
|
My TCU was completely unplugged. USA 2015. We lost our 3G network needed for communication about 2 years ago, which is why I got the OVMS system in the first place. My OVMS is now removed from the car. I would love to send it to someone who is NOT having problems to see if the issue occurs on their vehicle or not. If the issue doesn't occur on another vehicle, then I know it's something specific to my car. If it does occur, then it's likely I have a bad OVMS module. My hope is that it's the latter, as I feel like that's an easier to resolve issue. |
|
I've just installed OVMS in my 2014 Tekna, I unplugged the big white connector for the TCU and cant get climate control working with either the factory (3.3.001-33) or OTA images (3.3.003). When I try and turn on climate control via OVMS I hear audible clunk 3 times (relay?) and then nothing. Weirdly I can still turn on climate control via the app still (I thought removing the white connector would prevent it). Pretty sure I've unplugged the right module (under/right of drivers side steering wheel on RHS in the UK). Similar errors: Edit: So it turns out that in my RHD 2014 Tekna there are two big white connectors held in place by a central clip plugged into units right next to each other in the footwell. I had unplugged one that had the feed from the cameras (clue was reversing camera not working and the remote climate still working), not the TCU. The video linked from OVMS website doesn't appear to have the camera unit so its easy to confuse them. For clarity, the TCU connector pulls out towards the front of the car/engine bay it is very tricky to get out due to its placement - if it was easy you probably have the wrong connector. The camera connector pulls out downwards to the ground, this is fairly easy to remove. They are 90 degrees apart and close together (held in place on the same support bracket). With the right unit unplugged climate control is working at the moment, using the firmware build 3.3.001. Dont pull out this connector (not a video):
|
|
Can you take an updated video for Teka models? The current video was from an Acenta model |
|
Annoyingly I have video of the camera connector but not the TCU. Will have a look at the weekend if I can brave the dirt in the wife's foot well again 😱
|
|
So, it's been about a week and I'm still hesitant to post this, but... After a full module reset, then setup from scratch (no backup) - enabling only the bare minimum (WiFi, LTE, Server V2, Leaf) - I've not yet had an issue. Previously I absolutely would have seen the issue at some point over the course of a week, so I'm cautiously optimistic. Running main, not Edge. I've not calibrated the 12v, nor the cabin temp, nor setup Server v3, nor any logging - but I've tried to use remote CC as much as possible and so far so good. I'm also not logging, so no real means of keeping an eye for Can2 errors. Now, it's not been super cold just yet, but I'm still doubtful it was a weather-related issue. It was just that's when I've relied upon it the most - so most frustrated with it. I have attached my OVMS backup zip, excluding SSH files and redacting passwords, just incase it was config related that can be traced - Backup_redacted.zip |
|
Another 2 weeks down the line and all remains operational. I've never had this level of success before... I'm hesitant to start adding features back, as I'm just super happy it's working again! |
|
I did try that, with the same bare minimum setup you just described. IIRC it worked for a while, but failed eventually. |
|
Has anyone got remote climate working on a ZE1 2018+ 40kWh+ LEAF? |
I have a 2015 Nissan leave with the OVMS module. Recently, the CC command has stopped working. Someone else is having the same problem. All other functions seem fine. The other user reset the OVMS module back to it's original firmware and says the CC function is now working properly. I'm updated to the most recent update that came out on 01/17/2023, but the issue persists. I tried contacting OVMS about it, but they said to post the issue here. Any help or updates would be greatly appreciated.
The text was updated successfully, but these errors were encountered: