Posts: 6
Joined: Tue Jan 03, 2017 2:53 pm
Delivery Date: 03 Feb 2015

How does Nissan Connect wake a 2016 or later car?

Sun Jun 04, 2017 10:40 pm

Hi all,

I've found that the OVMS remote climate control activation does not work on a friends JDM 2016 30kWh Leaf. The OVMS sends a message on the EV bus with ID 0x68c and payload 0x00 to wake the car up, and then it sends 0x56e with payload 0x4e to turn on climate control. This works on Gen 2 cars but it doesn't wake up my friend's 2016 model.

Does anyone know how the new cars are woken up? Is the TCU still connected to the EV CAN bus?

Can anyone make a recording of the EV CAN bus during a Nissan Connect remote climate control activation on a 2016 or later Leaf?

Your help would be greatly appreciated because in New Zealand we cannot use the Nissan Connect service to do this ourselves -- the imported SIM cards don't work here, and when you change the SIM, the Nissan Connect server can't wake the car up because it uses an SMS and the phone number changes with the new SIM so the SMS never arrives.


Posts: 27
Joined: Tue Jun 02, 2015 1:46 pm
Delivery Date: 05 Jan 2016
Leaf Number: 301722
Location: Toronto, Canada

Re: How does Nissan Connect wake a 2016 or later car?

Mon Jun 05, 2017 5:57 pm

On my Canadian 2016 30 kW•h Leaf that wake-up command does reliably wake-up the Car CAN bus.

I don't believe the TCU is connected to the EV CAN bus, the TCU is only connected to the Car CAN bus.

If the Leaf has a TCU then putting a Climate Control start message onto the Car CAN bus must be done repeatedly as the messages you put onto the Car CAN bus are competing with conflicting messages from the TCU.

I posted some detail on starting the Climate Control in my post here (in point 2, after the text "Now for the three 'buttons'").

So while the Carloop is asking for the Climate Control to start, the TCU is sending a message (every 100 ms) to the Climate Control to not change, and the Leaf's VCM would not be expecting to receive such conflicting messages. After much testing I found that it usually works to send the 0x56E messages more often than the TCU, and send them for longer than the TCU would when it starts the Climate control. I settled on sending the bus wake-up (0x68C 00) , followed 50 ms later by 0x56E 4E 08 12 00 to turn on Climate Control, then delaying another 20 ms and repeating this Climate Control command another 45 times at 60 ms intervals.
2016 Leaf SL, grey, received 20160105, OpenEVSE

Return to “LEAF CANBus”