Leaf 2016-2017

I've passed on your message to the Leaf developers.

It would be helpful to see logs from a 2016 Leaf; I've only looked closely at MY2015.
Most of the metrics are picked up by passive reading of existing bus traffic, e.g. SOC is calculated from the most significant 10 bits in 0x5bc. The code applies some scaling factors you will probably need to customize to get the right output.

btw, I have just been looking at the charge-port messages and see that two bits in the last-but-one byte of 0x50d change before the charge port door opens. I don't see any indication that the car knows when it is actually open.

Hi meiniac,

I'm very sorry I haven't updated the Leaf parts of the OVMS manual. 2016 Leafs are supported with some configuration. It looks like you might have a 30kWh battery which, in theory, is also supported but you're probably the first to test it. I have a 2016 24kWh Leaf and everything works for me (almost).

Set the configuration option xnl.modelyear to 2016 to enable 2016 compatible remote commands:

config set xnl modelyear 2016

However you also have to unplug the TCU if fitted or it will override the OVMS module's messages. In previous model year cars, this hasn't caused any problems but in the 2016 model year they routed the handsfree microphone through the TCU and the microphone stops working when you unplug the TCU. You assistance in this matter is appreciated as I haven't had time to try to override the TCU using the OVMS.

Set the configuration option xnl.maxGids to the appropriate maximum gids for a 30kWh Leaf:

config set xnl maxGids 356

I have observed the SOC flapping with a v2 module in a 30kWh Leaf but we never got to the bottom of the problem, we found that the module was sending the SOC correctly and the server was not always sending the correct value to the app. It's possible the server doesn't like SOC above 100% and it will go away when you configure the maxGids correctly?

The xt_set_error_handler_callback error is because your esp_idf is out of date. You need the latest from https://github.com/openvehicles/esp-idf.git

Please join us on the mailing list if you can (I don't know why you would get permission denied).

Hi there,

Just got my OVMS setup, still need to upgrade to edge as the current main doesn't seem to be very stable on the 2016 Leaf despite configurations.

Remote AC with the Nissan app used to work even when the charging cable was not connected, so there must be a way.
Currently, OVMS docs say that Remote AC is limited to when charging and I can confirm this is how it works.

I'd like to add to the system so that we can activate Remote AC regardless of the charging cable.
Is this ongoing somewhere, anything I can do to help?

Does OVMS interface with the CAR CAN bus that apparently the AC control was moved in 2016?
Do we just need the right CAN message or does this require hardware changes?

Hi there,

Just got my OVMS setup, still need to upgrade to edge as the current main doesn't seem to be very stable on the 2016 Leaf despite configurations.

Remote AC with the Nissan app used to work even when the charging cable was not connected, so there must be a way.
Currently, OVMS docs say that Remote AC is limited to when charging and I can confirm this is how it works.

I'd like to add to the system so that we can activate Remote AC regardless of the charging cable.
Is this ongoing somewhere, anything I can do to help?

Does OVMS interface with the CAR CAN bus that apparently the AC control was moved in 2016?
Do we just need the right CAN message or does this require hardware changes?

Suggest moving to `edge` as older versions do not support using both buses for polling and this can cause issues on Leaf. 

Have you unplugged TCU? Also tried using `wakeup` command prior to initiating AC?

I have plugged my TCU back in because otherwise you lose the handsfree microphone but recall this worked.

In my 2016 car unplugging the TCU doesn't seem to affect the handsfree microphone.
I originally left the TCU connected since everything worked as described. (that you can turn AC on only when actively charging for the 2016-2017 Leaf is stated in OVMS docs)
I have since unplugged the TCU but this didn't have any effect on anything (other than the car showing error on the media screen - Nissan services were already non-working) .

The .14 firmware crashed often, so I did upgrade to .15 but that seems to crash every day and require unplugging. I'll have to install a switch...
I'm yet to try .16 edge if such exists. It's propably quite young if .15 was just released.

Unplugging the TCU had no effect on my 2016 30kWh Leaf.
I would very much like to solve this issue for 2016-2017 30kWh Leafs - Nissan has fixed my remote heating as of yesterday (after 3 months), so is there now something I can do to help with this?
Can I log the traffic with OVMS in order to see what happens when the AC is turned on with Nissan's app?

I also have Dala's CAN bridge, apparently some logging can be done with that as well. I haven't yet dared to splice it into the CAN wires though...  (unplugging made the car undriveable)

At the moment, it requires two attempts to start charging (the first one wakeups the car, I think it also works if you try to turn on AC and then start charging).
As described in the docs AC can only be started when the car is actively charging. Otherwise it wakeups the car (I can hear contactors clicking) but doesn't start it.

Now Nissan's original solution is able to start AC, so it has to be possible - can we mimic that somehow?

The funny thing is that I did unplug my TCU as per instructions and it gave me the red-cross-car-disconnected icon plus 'update stations' doesn't work anymore, but start AC and getting the battery SOC work with Nissan's original system nevertheless!

Which mailing list? I'd like to get on it too.

If you can sniff the CAN/EV bus packets from the official app, isolate those that wake-up the bus and remotely switch on the AC, then confirm with an ovms shell script by replaying the sequence it would be easy enough to add to the code base from there.

Ovms is connected to both and can read/write.

A couple of us are based in NZ where the Nissan app does not work. So we've relied on what's in the public domain and some guesswork 

Definitly can confirm the app in a 2016 Leaf SV can start the climate control from the app even if the car is not plugged in.  Either pushing "start climate" or scheduling it in the app (earlest scheduling time was always 5 min ahead).  Scheduling was much more reliable and didn't usually timeout due to "poor connection" or whatever other error the app would bring up.

Scheduling climate control from the in car screen only worked if the car was plugged in.

Of course, now that 3G is gone, so is that ability.

I have a 2016 leaf SL. I have unplugged the TCU as remote heating cooling was not working. Now hands-free mic,  text messages, and voice calling is not working. According to documentation they should still work. What is wrong?