[Ovmsdev] Leaf EV CAN messages

Mark Webb-Johnson mark at webb-johnson.net
Sat Jul 26 23:37:59 HKT 2014


Fantastic. Thanks for sharing.

I checked what you wrote against the EVCAN bus dumps we took, and they seem to match well.

For example, a carwings HVAC on shows:

1405412687.875 R11 56e 46
1405413246.983 R11 56e 4E
1405454415.582 R11 56e 46
1405472495.666 R11 56e 86

and HVAC off shows:

1405800125.677 R11 56e 86
1405801551.786 R11 56e 46
1405810295.435 R11 56e 56
1405827846.735 R11 56e 46
1405842751.818 R11 56e 86

These were on a 2012 leaf (I think), so I’m not seeing any 68C messages from carwings - although I did see the 68C 00 message when the car was switched on.

Makes me glad that we recently decided to switch to using the EV-CAN bus.

For the hardware mod necessary for 2011/2012 Leafs, any ideas how this could be done? Anyone got the 2012 service manual that they can send to me? We have a bunch of 5V TTL level outputs in the OVMS module that could be used as the basis for this.

Regards, Mark.

On 26 Jul, 2014, at 3:46 pm, Jeremy Whaling <jeremy.whaling at gmail.com> wrote:

> Hi All-
> Over the last few days a few of us on the mynissanleaf forum have been working on getting the TCU (telematics module) CAN messages for the various modes of operation (remote CC, status, charge). Here's what we know now:
> To wake up the VCM (Main controller), the TCU sends a msgID of 68C on the EV CAN bus with one byte of 00. On 2013 and newer models wake up solely on the CAN message.  
> For 2011 or 2012 models the TCU will bring a logic line high that connects to the VCM briefly as well to wake it up. Page 64 of the "AV" section of the 2012 service manual shows the pinout of the TCU. You will need to splice into Pin 11 (light green? wire) on the large connector going to the TCU and make an appropriate circuit to pull it high briefly when the OVMS module sends the 68C message. When doing non "remote charge" testing you might be able to hit the charge override button (which uses another line to wake the VCM) then send 68C. I think that might work for testing. :-)
> Once the VCM is awake it looks to the TCU status message to see what's up. The status message has a msgID of 56E and the first byte determines the status (the 6 other bytes are FF). The 56E message repeats every 100ms whenever the EV CAN bus is active. The various modes are:
> hex   binary   state
> 46   01000110   status
> 86   10000110   idle
> 4E   01001110   cc on
> 56   01010110   cc off
> 66   01100111   remote charge
> That's all we have so far. Haven't tried pulling the TCU yet and duplicating it's messages but I'm reasonably confident this is all there is to it as far as remote activation.
> For more info, see this Google Doc with the Leaf's CAN message info here
> For the latest developments Leaf CAN wise, check out the thread on MNL here
> Take care,
> Jeremy
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20140726/94e04ee3/attachment.htm>

More information about the OvmsDev mailing list