User avatar
TickTock
Posts: 1701
Joined: Sat Jun 04, 2011 10:30 pm
Delivery Date: 31 May 2011
Leaf Number: 3626
Location: Queen Creek, Arizona
Contact: Website

Re: LEAF CANbus decoding. (Open discussion)

Sat Oct 05, 2013 6:17 am

Making progress:

5fa:D3>>3 = day
5fa:D6>>4 = month
5fb:D2,D3>>2 = year

5fc:D2[7:2] = seconds
5fc:D2[1:0],D3[7:4] = minutes

User avatar
garygid
Gold Member
Posts: 12469
Joined: Wed Apr 21, 2010 8:10 am
Delivery Date: 29 Mar 2011
Leaf Number: 000855
Location: Laguna Hills, Orange Co, CA

Re: LEAF CANbus decoding. (Open discussion)

Sat Oct 05, 2013 6:42 am

TT, you do really good work!
Sincerely, Gary
See SOC/GID-Meter and CAN-Do Info
2010 Prius
2011 LEAF, 2014 Tesla S85
2018 & 2019 Tesla Model 3
PU: SDG&E
Solar PV: 33 x 225W -> 7 kW max AC
Craigslist: Xm5000Li Electric Motorcycle

User avatar
TickTock
Posts: 1701
Joined: Sat Jun 04, 2011 10:30 pm
Delivery Date: 31 May 2011
Leaf Number: 3626
Location: Queen Creek, Arizona
Contact: Website

Re: LEAF CANbus decoding. (Open discussion)

Sat Oct 05, 2013 7:06 am

Thanks Gary. :-)

5fc:D2[7:2] = seconds
5fc:D2[1:0],D3[7:4] = minutes
5fc:D1[7:3] = hour
5fa:D3[7:3] = day
5fa:D6[7:4] = month


[edit: year failed further tests - still looking..]
Last edited by TickTock on Sat Oct 05, 2013 10:30 am, edited 1 time in total.

User avatar
TonyWilliams
Posts: 10091
Joined: Sat Feb 19, 2011 1:48 am
Location: San Diego
Contact: Website

Re: LEAF CANbus decoding. (Open discussion)

Sat Oct 05, 2013 8:04 am

garygid wrote:If it is really the Capacity, it should be CAP, rather than "health", right?

The BAD news:
One must lose 4 bars to be eligible for the new capacity warranty, right?

Lose 1st at 85% (approximate values) 11 showing
lose 2nd at 77.5% 10 bars showing
lose 3rd at 70% 9 bars showing
lose 4th at 62.5% 8 (less than 9) bars showing.

So, the warranty kicks in when you lose the 9th bar, at
8 bars showing, or about 2 months after 62%, not 70%, right? :o
The dash display of Battery Capacities per the first Nissan LEAF service manual are as follows:

53.75% - 59.99% - 7 segments of 12 illuminated
60.00% - 66.24% - 8 segments of 12 illuminated
66.25% - 72.49% - 9 segments of 12 illuminated
72.50% - 78.74% - 10 segments of 12 illuminated
78.75% - 84.99% - 11 segments of 12 illuminated
85.00% - 100.0% - 12 segments of 12 illuminated

Turbo3
Gold Member
Posts: 2011
Joined: Mon Jul 19, 2010 8:34 pm
Delivery Date: 12 May 2011
Leaf Number: 002191
Location: San Jose, CA

Re: LEAF CANbus decoding. (Open discussion)

Sat Oct 05, 2013 10:47 am

My year shows 0x1FE3>>2 = 2040

User avatar
TickTock
Posts: 1701
Joined: Sat Jun 04, 2011 10:30 pm
Delivery Date: 31 May 2011
Leaf Number: 3626
Location: Queen Creek, Arizona
Contact: Website

Re: LEAF CANbus decoding. (Open discussion)

Sat Oct 05, 2013 11:11 am

TickTock wrote:
5fc:D2[7:2] = seconds
5fc:D2[1:0],D3[7:4] = minutes
5fc:D1[7:3] = hour
5fa:D3[7:3] = day
5fa:D6[7:4] = month
:| Nothing is ever easy. I cannot find anything that gives the year and furthermore, these messages are not present in 2013 Leaf logs.

User avatar
JeremyW
Posts: 1545
Joined: Sun Nov 13, 2011 12:53 am
Delivery Date: 23 Jun 2012
Leaf Number: 19136
Location: San Gabriel, CA

Re: LEAF CANbus decoding. (Open discussion)

Sat Oct 05, 2013 2:55 pm

TickTock, would be interesting to see if that timestamp changes if you change the eyebrow or nav clock.
Former 2012 SL leasee 6/23/12 - 9/23/15
Former Fit EV leasee.
Now driving Spark EV and Model 3.

User avatar
TickTock
Posts: 1701
Joined: Sat Jun 04, 2011 10:30 pm
Delivery Date: 31 May 2011
Leaf Number: 3626
Location: Queen Creek, Arizona
Contact: Website

Re: LEAF CANbus decoding. (Open discussion)

Sat Oct 05, 2013 4:01 pm

Turbo3 wrote:My year shows 0x1FE3>>2 = 2040
Yeah - I get the same. I get the same on 2012 logs and it returns 1fe2 on my 2011 log. Doesn't make sense. Problem is I only have one 2011 carcan log (at that time I was only able to log one can bus at a time and usually chose to log the evcan).

Good idea Jeremy, I did start to test this. I wanted to change the year to see if it would help me find the year. However, it only seems to let you change the time - not the date so I aborted the experiment. I will go back and see if the hour changes the value - would be interesting to know if they are related.

User avatar
TickTock
Posts: 1701
Joined: Sat Jun 04, 2011 10:30 pm
Delivery Date: 31 May 2011
Leaf Number: 3626
Location: Queen Creek, Arizona
Contact: Website

Re: LEAF CANbus decoding. (Open discussion)

Sat Oct 05, 2013 8:24 pm

No luck finding a date on the 2013 logs. Looks like they changed quite a bit of the traffic. I was able to find the time in the 2013, though:
  • 509:d3[7:2] = seconds
    5f9:d5 = minutes
    5f9:d6[7:3] = hour
However, this only works on the 2013's (at least it works for the two I have log files from and doesn't work on my 2011).

My technique to find the date on the 2011 came up empty on the 2013 - I queried for all message bytes that never changed in a log and then looked for which of those changed from logs on different days. Essentially all the bytes that never changed within a log on the 2013 also never changed from day to day. So if there is a date embedded in the 2013 data, it is overloaded onto a message that also outputs different information on the same byte. Makes it a lot harder to find...

User avatar
TickTock
Posts: 1701
Joined: Sat Jun 04, 2011 10:30 pm
Delivery Date: 31 May 2011
Leaf Number: 3626
Location: Queen Creek, Arizona
Contact: Website

Re: LEAF CANbus decoding. (Open discussion)

Sun Oct 06, 2013 10:40 am

JeremyW wrote:TickTock, would be interesting to see if that timestamp changes if you change the eyebrow or nav clock.
Just tried it. Changing the time on the eyebrow has no effect on the time reported on the canbus but off-setting the navigation clock does.

I have added a option to auto-sync the CANary with the car time but need to add code to support the different 2013 messages before I publish. Anyone know of a message that conclusively identifies the model year? I could add it as a config option or even deduce it based on the missing 59a/59b/a9c messages but this may change with a sw update so it would be nice if there was a more direct indicator.

Return to “LEAF CANBus”