lorenfb
Posts: 2223
Joined: Tue Dec 17, 2013 10:53 pm
Delivery Date: 22 Nov 2013
Leaf Number: 416635
Location: SoCal

Re: LEAF CANbus decoding. (Open discussion)

Wed May 29, 2019 10:01 pm

ybpvin wrote:I wonder, thank you. how can I read the byte eeprom dashboard?


Seriously doubt it can be read via any CAN bus, i.e. the cluster processor's flash memory (EEPROM). Most likely you'll need to pull the cluster,
and even then without knowing the processor type (unlikely separate EEPROM), not easy.
#1 Leaf SL MY 9/13: 74K miles, 48 Ahrs, 5.2 miles/kWh (average), Hx=70, SOH=78, L2 - 100% > 1000, temp < 95F (35C), min discharge (DOD) > 20 Ahrs
#2 Leaf SL MY 12/18: 115 Ahrs, 5.5 miles/kWh (average), Hx=98, SOH=99, DOD > 25%, temp < 105F

ybpvin
Posts: 9
Joined: Fri Aug 24, 2018 4:55 am
Delivery Date: 24 Aug 2018
Leaf Number: 022135

Re: LEAF CANbus decoding. (Open discussion)

Thu May 30, 2019 2:43 am

There is a sTool software product which on obd2 adjusts nissan leaf speedometer.

mux
Posts: 190
Joined: Sat Jan 13, 2018 3:52 am
Delivery Date: 13 Oct 2011
Leaf Number: 6177

Re: LEAF CANbus decoding. (Open discussion)

Thu May 30, 2019 3:55 am

which one? we might be able to buy one and reverse engineer it!

ybpvin
Posts: 9
Joined: Fri Aug 24, 2018 4:55 am
Delivery Date: 24 Aug 2018
Leaf Number: 022135

Re: LEAF CANbus decoding. (Open discussion)

Thu May 30, 2019 4:05 am


mux
Posts: 190
Joined: Sat Jan 13, 2018 3:52 am
Delivery Date: 13 Oct 2011
Leaf Number: 6177

Re: LEAF CANbus decoding. (Open discussion)

Thu May 30, 2019 5:41 am

Ah, it literally just adjusts the odometer. That is not very useful, I was hoping it was a proper scan tool. This is just a tool to mess with odometers to make the car look younger...

cwpaynter
Posts: 4
Joined: Tue May 28, 2019 9:06 pm
Delivery Date: 29 May 2019

Re: LEAF CANbus decoding. (Open discussion)

Wed Jun 05, 2019 2:04 pm

caederus wrote:
virol wrote:have 2018 leaf tekna 40kw, can you explain exactly how to send an active request on 7xx addresses with a ELM module over the OBD plug.

LEAF active queries and replies use UDS over ISO-TP. Unfortunately the wikipedia documentation is incomplete, and the addresses and data bytes are not defined by the standard anyway, so are all informed guesswork.

A simple example would be reading the odometer, where both query and reply each fit in single packets:

Code: Select all

Query: 743#022119FFFFFFFFFF
Reply: 763#056119005D6AFFFF

743 is the query address for the instrument cluster
The first data byte 02 is the ISO-TP header:
- 0 in the upper 4 bits means that this is a single ISO-TP packet.
- 2 in the lower 4 bits means there are two UDS data bytes (21 19):
- - 21 is the UDS service ID "Read data by local ID", which takes one parameter
- - 19 is the local ID, which the instrument cluster interprets as odometer.
The remaining FF bytes are padding.

763 is the reply address (for the instrument cluster)
The first byte 05 is the ISO-TP header:
- 0 in the upper 4 bits means that this is a single ISO-TP packet.
- 5 in the lower 4 bits means there are five UDS data bytes (61 19 00 5D 6A)
- - 61 19 is the same as in the query, with 0x40 added to the service ID to indicate it is a reply.
- - 005D6A is the odometer reading.
The remaining FF bytes are padding.


@cadreus, I have a working CAN transceiver now, and confirm there's nothing happening on the bus, until I activate LeafSpy. I can sniff both sides of that conversation, and am seeing various requests and responses, and can decode the ISO-TP packets to reassemble the UDS messages. I can blindly send those commands over my own interface, and I get the responses, including the VIN number in one case. This is all good, but I'm not seeing much info on the canmsgs spreadsheet about those UDS commands. Are you aware of a list of what those commands mean?

ybpvin
Posts: 9
Joined: Fri Aug 24, 2018 4:55 am
Delivery Date: 24 Aug 2018
Leaf Number: 022135

Re: LEAF CANbus decoding. (Open discussion)

Sat Jun 08, 2019 11:26 pm

I repeated the Celeron55 project with zapuky the engine Nissan a bodice of 2013. The engine powered from the socket 220 volts)).
Now I want to program a power generation algorithm the engine, but I cannot find can codes of management of command of the inverter.
What Id operates this funtion?

NiallDarwin
Posts: 42
Joined: Thu Jul 09, 2015 1:58 am
Delivery Date: 12 Dec 2015
Leaf Number: 004321
Location: New Zealand

Re: LEAF CANbus decoding. (Open discussion)

Wed Jun 12, 2019 3:10 pm

caederus wrote:
virol wrote:have 2018 leaf tekna 40kw, can you explain exactly how to send an active request on 7xx addresses with a ELM module over the OBD plug.

LEAF active queries and replies use UDS over ISO-TP. Unfortunately the wikipedia documentation is incomplete, and the addresses and data bytes are not defined by the standard anyway, so are all informed guesswork.

A simple example would be reading the odometer, where both query and reply each fit in single packets:

Code: Select all

Query: 743#022119FFFFFFFFFF
Reply: 763#056119005D6AFFFF

743 is the query address for the instrument cluster
The first data byte 02 is the ISO-TP header:
- 0 in the upper 4 bits means that this is a single ISO-TP packet.
- 2 in the lower 4 bits means there are two UDS data bytes (21 19):
- - 21 is the UDS service ID "Read data by local ID", which takes one parameter
- - 19 is the local ID, which the instrument cluster interprets as odometer.
The remaining FF bytes are padding.

763 is the reply address (for the instrument cluster)
The first byte 05 is the ISO-TP header:
- 0 in the upper 4 bits means that this is a single ISO-TP packet.
- 5 in the lower 4 bits means there are five UDS data bytes (61 19 00 5D 6A)
- - 61 19 is the same as in the query, with 0x40 added to the service ID to indicate it is a reply.
- - 005D6A is the odometer reading.
The remaining FF bytes are padding.


"005D6A is the odometer reading."...and decoding that gives us 23,914kms?

caederus
Posts: 12
Joined: Sun Mar 20, 2016 9:34 am
Delivery Date: 01 Mar 2016

Re: LEAF CANbus decoding. (Open discussion)

Thu Jun 13, 2019 8:21 am

NiallDarwin wrote:"005D6A is the odometer reading."...and decoding that gives us 23,914kms?
Yes, that's correct, and unlike some other distance and speed values whose units can change depending on region of manufacture or user display preference, this one always seems to be in km.

User avatar
JeremyW
Posts: 1541
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)

Sun Jun 16, 2019 9:44 am

It looks like the 2019 Leaf has a different electrical configuration than the earlier cars. What I would do is go to https://www.nissan-techinfo.com and pay for a one day subscription for $20 to get the 2019 service manual. The 2011/2012 manuals that I have had a whole section on the CAN bus architecture of the vehicle.

It's likely the CAR CAN bus has been removed from the OBD connector, and replaced with a new "diagnostic bus" that talks just to the VCM, which can relay the message onto the requested module by decoding the query address and sending it onward to the appropriate bus where the module is located. Older leaf VCMs do this already on the CAR can bus to the EV CAN bus. It's how an ELM327 can talk to modules on the EV CAN bus (BMS, Inverter, HVAC, etc.). When leafspy first came out Turbo3 was requiring modified ELM327s which looked at the EV bus directly, which quickly ended when this phenomenon was discovered. I think Nissan's official diagnostics tools take the same approach as LeafSpy does today, just querying for info instead of looking at the values being shot around by the various modules.

Is EV CAN still present on pins 12 and 13?
Former 2012 SL leasee 6/23/12 - 9/23/15
Former Fit EV leasee.
Now driving Spark EV and Model 3.

Return to “LEAF CANBus”