Nissan Leaf OBD-II manual

Nissan Leaf OBD-II manualRelease 2021.2.25+ddc9fcc

Seth Fischer

Feb 25, 2021

Contents

1 Reference 11.1 Diagnostic connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 Parameter identifiers 52.1 358 turn signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 5B3 SoH, GID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.3 5C5 odometer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Tutorials 113.1 Monitoring the Nissan Leaf using an ELM327 diagnostic tool . . . . . . . . . . . . . . . . . . . 11

A Related material 17

B Glossary 19

C Disclaimer 21

D License 23D.1 Trade marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23D.2 Prose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23D.3 Code listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Bibliography 25

Index 27

i

Chapter 1

Reference

1.1 Diagnostic connector

The Nissan Leaf is fitted with a Type A diagnostic connector as defined in ISO 15031-3 or its equivalentSAE J1962. Type A diagnostic connectors have 16 pins arranged in two rows of eight. Nine of the pins havea mandated designation - with use of the remaining pins being at the discretion of the vehicle manufacturer.

1.1.1 Location

The Leaf ’s diagnostic connector is located beneath the steering column as is seen in Figure 1.1.

1.1.2 CAN buses

The Leaf has three CAN buses commonly referred to as: AV-CAN, EV-CAN, and Car-CAN. The CAN proto-col used in the Leaf is ISO 15765-4 CAN (11-bit ID, 500 kBd) which is often abbreviated to “ISO 15765-4(CAN 11/500).”

Each CAN bus carries messages relating to a different aspect of the vehicle’s operation:

AV-CAN

Messages related to the display screen.

Car-CAN

Messages related to general vehicle operation including EV related messages.

EV-CAN

Messages related to the battery and drive system.

1.1.3 Contact designation

Figure 1.2 depicts the mating-end view of the OBD-II vehicle diagnostic connector. Colours of the CAN bussymbols are selected to correspond with the colour code of four-pair ethernet cable.

As depicted in Table 1.1, the Leaf uses five contacts with a mandated designation: chassis ground, signal ground,Car-CAN high, Car-CAN low, and permanent +12 V DC. Designation of the remaining pins is specific to theLeaf : AV-CAN low, +12 V DC when vehicle powered on, AV-CAN high, EV-CAN low, and EV-CAN high.

1

Nissan Leaf OBD-II manual, Release 2021.2.25+ddc9fcc

Figure 1.1: Nissan Leaf OBD-II vehicle diagnostic connector (mating-end view)

Figure 1.2: Nissan Leaf OBD-II diagnostic connector contact designation (mating-end view)

2 Chapter 1. Reference


Table 1.1: Nissan Leaf vehicle diagnostic connector contact designationPin Symbol1 Designation1 No connection2 No connection2

3 AV-CAN low3

4 Chassis ground2

5 Signal ground2

6 Car-CAN high2

7 No connection2

8 +12 V DC when vehicle powered on3

9 No connection10 No connection2

11 AV-CAN high3

12 EV-CAN low3

13 EV-CAN high3

14 Car-CAN low2

15 No connection2

16 Permanent +12 V DC2

1 CAN bus symbol colours correspond to 4-pair ethernet cable colour code.2 Mandated allocation defined in ISO 15031-3.3 [myn10].

1.1. Diagnostic connector 3


4 Chapter 1. Reference

Chapter 2

Parameter identifiers

2.1 358 turn signal

PID 0x358

Name Turn signal

2.1.1 AZE0

Table 2.1: PID 0x358 – transmit frequenciesBus Frequency (Hz)Car-CAN 10

Table 2.2: PID 0x358PID Byte Bits Description Formula Unit Min Max358 B 1:1 turn signal

left1 ==active;0 ==inactive

2:2 turn signalright

1 ==active;0 ==inactive

Adapted from [DanielOster].

5


ELM327 console

Listing 2.1: Read PID 0x358 – turn signal status (ELM327 console)

1 > ATZ2 > ATI3 > ATL14 > ATH15 > ATS16 > ATAL7 > ATSP68 > ATCRA 3589 > ATMA

10 358 00 08 80 00 00 00 00 0011 358 00 08 80 00 00 00 00 0012 358 00 08 80 00 00 00 00 0013 358 00 08 82 00 00 00 00 0014 358 00 08 82 00 00 00 00 0015 358 00 08 82 00 00 00 00 0016 358 00 08 80 00 00 00 00 0017 358 00 08 80 00 00 00 00 0018 358 00 08 80 00 00 00 00 0019 358 00 08 84 00 00 00 00 0020 358 00 08 84 00 00 00 00 0021 358 00 08 84 00 00 00 00 00

Read PID 0x358 - turn signal status (ELM327 console)

ELM327 Python

Listing 2.2: Read PID 0x358 – turn signal status (ELM327 Python script)

1 #!/usr/bin/env python2

3 """358 turn signal4

5 Query the turn signal status of a Nissan Leaf using an ELM327 compatible diagnostic6 tool.7

8 Tested on the following vehicles:9

10 * AZE011 """12

13 import serial14

15 elm = serial.Serial("/dev/ttyUSB0", 38400, timeout=5)16

17 elm.write(b"ATZ\r") # reset all18 print(elm.read_until(b"\r\r>").decode())19

20 elm.write(b"ATI\r") # print version ID21 print(elm.read_until(b"\r\r>").decode())22

23 elm.write(b"ATL1\r") # line feeds on24 print(elm.read_until(b"\r\n>").decode())25

26 elm.write(b"ATH1\r") # headers on27 print(elm.read_until(b"\r\n>").decode())28

29 elm.write(b"ATS1\r") # print spaces on(continues on next page)

6 Chapter 2. Parameter identifiers


(continued from previous page)

30 print(elm.read_until(b"\r\n>").decode())31

32 elm.write(b"ATAL\r") # allow long messages33 print(elm.read_until(b"\r\n>").decode())34

35 elm.write(b"ATSP6\r") # set protocol ISO 15765-4 CAN (11/500)36 print(elm.read_until(b"\r\n>").decode())37

38 elm.write(b"ATCRA 358\r") # set CAN receive address39 print(elm.read_until(b"\r\n>").decode())40

41 elm.write(b"ATMA\r") # monitor all messages42

43 try:44 while True:45 print(elm.read_until(b"\r\n").decode(), flush=True)46 except KeyboardInterrupt:47 print("Keyboard interrupt")48

49 elm.close()

Read PID 0x358 - turn signal status (ELM327 Python script)

2.2 5B3 SoH, GID

PID 0x5B3

Name SoH, GID

2.2.1 AZE0

Table 2.3: PID 0x5B3 – transmit frequenciesBus Frequency (Hz)Car-CAN 2

Table 2.4: PID 0x5B3 – responsePID Byte Bits Description Formula Unit Min Max3B3 B 7:1 Traction battery state of health (SoH) 0 100

F 7:0 Traction battery stored energy4

𝐹 · 80

Wh 0

Adapted from: [ope], [DanielOster].

4 Raw value of byte F is often referred to as being measured in GIDs, where 1 GID = 80 Wh.

2.2. 5B3 SoH, GID 7


ELM327 console

Listing 2.3: Read PID 0x5B3 – GID (ELM327 console)

1 > ATZ2 > ATI3 > ATL14 > ATH15 > ATS16 > ATAL7 > ATCRA 5B38 > ATMA9 5B3 64 A2 12 CA 30 7B D0 8B

Read PID 0x5B3 - GID (ELM327 console)

Equations

Traction battery stored energy Equation (2.1):

𝐺𝑖𝑣𝑒𝑛 :

𝑏𝑦𝑡𝑒𝐹 = 𝐸616 = 12310

𝑇ℎ𝑒𝑛 :

𝐸𝑠𝑡𝑜𝑟𝑒𝑑 = 𝑏𝑦𝑡𝑒𝐹10 · 8010 𝑊 ·ℎ= 12310 · 8010 𝑊 ·ℎ= 984010 𝑊 ·ℎ

(2.1)

Traction battery state of health (SoH) Equation (2.2):


𝑏𝑦𝑡𝑒𝐵 = 𝐴216 = 101000102

𝑇ℎ𝑒𝑛 :

𝑆𝑜𝐻 = 𝑏𝑦𝑡𝑒𝐵2 >> 1

= 101000102 >> 1

= 010100012

= 8110%

(2.2)

2.3 5C5 odometer

PID 0x5C5

Name Odometer

2.3.1 AZE0

Table 2.5: PID 0x5C5 – transmit frequenciesBus Frequency (Hz)Car-CAN 10



Table 2.6: PID 0x5C5PID Byte Bits Description Formula Unit Min Max358 B 7:0

odometerbyte 1(high)

𝐵(216) + 𝐶(28) +𝐷

kmmi

0 16777215

C 7:0

odometerbyte 2

D 7:0

odometerbyte 3(low)

Adapted from [DanielOster].

ELM327 console

Listing 2.4: Read PID 0x5C5 – odometer (ELM327 console)

1 > ATZ2 > ATI3 > ATL14 > ATH15 > ATS16 > ATAL7 > ATCRA 5C58 > ATMA9 5C5 44 00 9B DC 00 0C 00 00

Read PID 0x5C5 - odometer (ELM327 console)

Equations

Odometer reading Equation (2.3):


𝑏𝑦𝑡𝑒𝐵 = 016 = 02

𝑏𝑦𝑡𝑒𝐶 = 9𝐵16 = 100110112

𝑏𝑦𝑡𝑒𝐷 = 𝐷𝐶16 = 110111002

𝑂𝑑𝑜𝑚𝑒𝑡𝑒𝑟 𝑟𝑒𝑎𝑑𝑖𝑛𝑔 = 02(216) + 100110112(2

8) + 110111002

= 10011011 110111002 = 9𝐵𝐷𝐶16

= 39900 𝑘𝑚

(2.3)

2.3. 5C5 odometer 9

Chapter 3

Tutorials

3.1 Monitoring the Nissan Leaf using an ELM327 diagnostic tool

An introduction to reading the Car-CAN bus of the Nissan Leaf using an ELM327 compatible diagnostic tool.

3.1.1 Requirements

1. ELM327 compatible OBD-II diagnostic tool.

2. Terminal application running on a mobile or laptop.

3. Nissan Leaf.

The examples in this tutorial use a Vgate Wi-Fi diagnostic tool and Serial Wi-Fi Terminal5 for Android by KaiMorich6. The same developer has also written Serial USB Terminal and Serial Bluetooth Terminal for Android.

The vehicle used in this tutorial is:

Vehicle Nissan Leaf

Year 2013

Model AZE0-0 G-spec

CAN protocol ISO 15765-4 (CAN 11/500)

ELM327 OBD-II diagnostic tool

ELM327 diagnostic tools are available supporting either wireless or wired communication protocols. Wirelesscommunication protocols include:

• BT (Bluetooth)

• BTL (Bluetooth Low Energy)

• Wi-Fi

Wi-Fi diagnostic tools have the disadvantage that while in use your mobile or laptop is unable to connect to anyother Wi-Fi network.

The most common wired communication protocol is USB (Universal Serial Bus).

5 https://play.google.com/store/apps/details?id=de.kai_morich.serial_wifi_terminal6 https://play.google.com/store/apps/developer?id=Kai+Morich

11

https://play.google.com/store/apps/details?id=de.kai_morich.serial_wifi_terminal

https://play.google.com/store/apps/developer?id=Kai+Morich

https://play.google.com/store/apps/developer?id=Kai+Morich


Note: Unfortunately the market is flooded with counterfeit ELM327 microcontrollers which have made theirway into inexpensive diagnostic tools. Often these devices do not fully support the ELM327 specification7

[JRPollock17].

Genuine ELM327 microcontrollers are supplied by ELM Electronics Inc.8 who recommend seeking the assurancefrom the device vendor that they use genuine ELM parts [elm20].

Terminal application

Select a terminal application that can be configured to connect to your diagnostic tool via the appropriate commu-nication protocol.

Nissan Leaf

The Leaf has three CAN buses commonly referred to as: Car-CAN, EV-CAN, and AV-CAN. The diagnostic con-nector CAN pin assignments are depicted in Figure 3.1 and listed in Table 3.1. The CAN protocol used in theCar-CAN bus of the Leaf is ISO 15765-4 CAN (11-bit ID, 500 kBd) which is often abbreviated to “ISO 15765-4(CAN 11/500).”

Figure 3.1: Nissan Leaf ISO 15031-3 diagnostic connector pin assignment (mating-end view)

Table 3.1: Nissan Leaf ISO 15031-3 diagnostic connector CAN bus pinassignments

CAN bus Diagnostic connector pinsCAN high CAN low

Car-CAN

6

14EV-CAN

12

13AV-CAN

3

11

Standard OBD-II diagnostic tools connect to the Car-CAN bus on pins 6 and 14.

The Leaf does not support any the standard PIDs which are mandated for internal combustion engine vehicles.This is despite having a OBD-II diagnostic connector in compliance with ISO 15031-3, and the CAN protocolscomplying with ISO 15765-4.

In addition to the Leaf not supporting standard PIDs there can be PID variations between Leaf models.

7 https://www.elmelectronics.com/wp-content/uploads/2016/07/ELM327DS.pdf8 https://www.elmelectronics.com/

12 Chapter 3. Tutorials

https://www.elmelectronics.com/wp-content/uploads/2016/07/ELM327DS.pdf

https://www.elmelectronics.com/


3.1.2 Set up

Set up involves connecting the diagnostic tool to the vehicle and configuring the terminal application which runson your mobile or laptop.

Warning: Using a poor quality diagnostic tool may cause the vehicle to behave unexpectedly.

Connect the diagnostic tool

Insert the diagnostic tool into the vehicle’s OBD-II diagnostic connector – which is found beneath the steeringcolumn. Then power-on the vehicle to activate the Car-CAN bus.

Configure the terminal application

Configuration of the terminal application depends on the communication protocol supported by your diagnostictool and the terminal software being used.

Wi-Fi:

1. Connect to the diagnostic tool as you would connect to a Wi-Fi access point.

2. Configure the terminal application with the host and port of the diagnostic tool according to the user guide.Common configuration is:

Host 192.168.0.10

Port 35000

Protocol Raw

Bluetooth and Bluetooth Low Energy:

1. Pair the diagnostic tool with your mobile or laptop.

2. Once paired the tool is available for selection in the terminal application.

3.1.3 Diagnostic tool commands

The ELM327 is instructed by sending a series of AT commands from the terminal application.

AT commands

Commands used in this tutorial are listed in table Table 3.2. The complete ELM327 command set can be found inthe ELM327 specification9.

9 https://www.elmelectronics.com/wp-content/uploads/2016/07/ELM327DS.pdf

3.1. Monitoring the Nissan Leaf using an ELM327 diagnostic tool 13



Table 3.2: ELM327 AT commands used in this tutorial [elm:elm327]Command DescriptionATZ reset allATI print the ELM327 firmware version IDATL1 line feed onATH1 header control onATS1 print spaces onATAL allow long messagesATSP6 set CAN protocol to ISO 15765-4 CAN (11/500)ATCRA 358 filter message with PID 0x358ATMA monitor all

Read turn signal status

In Listing 3.1 the status of the vehicle’s turn signal is read. Commands on lines 1 to 7 initialise the ELM327.Command ATCRA 358 on line 8 filters messages with the PID 0x358.

Listing 3.1: Read PID 0x358 – turn signal status

1 > ATZ2 > ATI3 > ATL14 > ATH15 > ATS16 > ATAL7 > ATSP68 > ATCRA 3589 > ATMA

10 358 00 08 80 00 00 00 00 0011 358 00 08 80 00 00 00 00 0012 358 00 08 80 00 00 00 00 0013 358 00 08 82 00 00 00 00 0014 358 00 08 82 00 00 00 00 0015 358 00 08 82 00 00 00 00 0016 358 00 08 80 00 00 00 00 0017 358 00 08 80 00 00 00 00 0018 358 00 08 80 00 00 00 00 0019 358 00 08 84 00 00 00 00 0020 358 00 08 84 00 00 00 00 0021 358 00 08 84 00 00 00 00 00

ELM327 session 0x358 turn signal status

The output is displayed following the command ATMA on lines 10 to 21. As the turn signal leaver is operated thethird byte changes correspondingly:

off 8016 = 100000002

left signal 8216 = 100000102

right signal 8416 = 100001002

A screenshot of the serial terminal session prior to executing ATMA is shown in Figure 3.2.

See also:

Diagnostic connector (page 1) Detailed description of the Leaf OBD-II diagnostic connector.

358 turn signal (page 5) PID 0x358 Turn signal.



Figure 3.2: ELM327 serial terminal session on an Android-powered device [KaiMorich]

3.1. Monitoring the Nissan Leaf using an ELM327 diagnostic tool 15

Appendix A

Related material

Nissan Publications10 Nissan service manuals.

Open Vehicle Monitoring System 311 An open source vehicle monitoring, diagnosis, and control system.

10 https://www.nissan-techinfo.com/11 https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3

17

https://www.nissan-techinfo.com/

https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3


18 Appendix A. Related material

Appendix B

Glossary

AT commands A command language supported by the ELM327 with “AT” meaning “attention.”

AV-CAN Name of the Nissan Leaf CAN bus which carries predominantly infotainment data. Exposed on pins 3and 11 of the diagnostic connector.

CAN Abbreviation for controller area network.

CAN protocol Transport protocol (layer 4) and network (layer 3) protocol implemented on a CAN bus. TheOBD-II protocol used by the Nissan Leaf is ISO 15765-4 CAN (11-bit ID, 500 kBd).

Car-CAN Name of the Nissan Leaf CAN bus exposed on pins 6 and 14 of the diagnostic connector.

communication protocol A system of rules that allow two or more entities of a communications system to trans-mit information.

controller area network A vehicle bus standard designed to allow microcontrollers and devices to communicatewithout a host computer.

diagnostic connector A physical connector used to access on-board diagnostics and data streams. The OBD-IIdiagnostic connector (defined in ISO 15031-3) is a 16-pin connector which, on a Nissan Leaf, is locatedbeneath the steering column.

diagnostic tool An electronic device that interfaces with a vehicle’s diagnostic connector.

ELM327 A proprietary, pre-programmed, microcontroller produced by ELM Electronics Inc.1216 for communi-cating with a vehicle’s on-board diagnostics interface. The ELM327 command protocol is one of the mostpopular PC-to-OBD interface standards and is also implemented by other vendors.

ELM327 compatible Used to describe a device capable of translating the on-board diagnostics interface andwhich supports the ELM327 command set.

EV-CAN Name of the Nissan Leaf CAN bus which carries data related to the traction battery and electric motordrive system. Exposed on pins 3 and 11 of the diagnostic connector.

GID Unit named after Gary Giddings who is credited with discovering the significance of 5B3 SoH, GID (page 7)byte F.

ISO 15031-3 Document published by the International Organization for Standardization1317 (ISO) titled Roadvehicles — Communication between vehicle and external equipment for emissions-related diagnostics —Part 3: Diagnostic connector and related electrical circuits: Specification and use.

ISO 15765-4 Document published by the International Organization for Standardization1417 (ISO) titled Roadvehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 4: Requirements foremissions-related systems.

12 https://www.elmelectronics.com/16 https://www.elmelectronics.com/13 https://www.iso.org/17 https://www.iso.org/14 https://www.iso.org/

19


https://www.iso.org/





kBd Abbreviation for kilobaud where 1 kBd = 1000 Bd (baud).

OBD-II Abbreviation for revision two of the on-board diagnostics standardised interface.

on-board diagnostics A term referring to a vehicle’s self-diagnostic and reporting capability.

parameter ID A hexadecimal code used to identify data on a CAN bus.

PID Abbreviation for parameter ID.

SAE J1962 Document published by SAE International1518 titled Diagnostic Connector Equivalent to ISO/DIS15031-3:December 14, 2001. This document specifies the functional requirements for the physical OBD-IIdiagnostic connector. The equivalent international standard is ISO 15031-3.

SoH State of Heath. Measure of the ability of a battery to store and deliver electrical energy relative to a newbattery.

terminal application Application that sends and receives text data over a serial interface.

Type A diagnostic connector A diagnostic connector defined in Figure A.1 of ISO 15031-3.

15 https://www.sae.org/18 https://www.sae.org/

20 Appendix B. Glossary

https://www.sae.org/

https://www.sae.org/

Appendix C

Disclaimer

Note: This project is neither maintained nor endorsed by Nissan.

Advisory issued by Nissan

An advisory issued by Nissan states that an after market diagnostic tool should never be connected to the diagnosticconnector.

About mounting external communication equipment on the OBD-II connector

Do not attach an aftermarket communication device to the OBD-II connector.

External communication equipment attached to the OBD-II connector may affect the control of thevehicle engine, brakes, steering, etc., and may not operate normally, leading to unexpected troubles.

—Advisory issued by Nissan [nis15] English translation by Google Translate

Source of translation:

OBD-IIコココネネネクククタタタへへへののの社社社外外外品品品ののの通通通信信信機機機器器器装装装着着着にににつつついいいててて

OBD-IIコココネネネクククタタタににに社社社外外外品品品ののの通通通信信信機機機器器器ををを取取取りりり付付付けけけななないいいでででくくくだだださささいいい

OBD-IIコネクタへ取り付けた社外品の通信機器が、車両のエンジン・ブレーキ・ステアリング等の

制御に影響を与え、正常に作動せず、思わぬトラブルにつながるおそれがあります。

—Advisory issued by Nissan [nis15]

21


22 Appendix C. Disclaimer

Appendix D

License

D.1 Trade marks

Nissan and Leaf are trade marks of Nissan Jidosha Kabushiki Kaisha (also trading as Nissan Motor Co., Ltd.).

D.2 Prose

19 This work is licensed under a Creative Commons Attribution 4.0 InternationalLicense20.

D.3 Code listings

Code listings are licensed under the MIT License21:

MIT License

Copyright (c) 2021 Seth Fischer

Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in allcopies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,

(continues on next page)

19 https://creativecommons.org/licenses/by/4.0/20 https://creativecommons.org/licenses/by/4.0/21 https://opensource.org/licenses/MIT

23

https://creativecommons.org/licenses/by/4.0/



https://opensource.org/licenses/MIT


(continued from previous page)

OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THESOFTWARE.

24 Appendix D. License

Bibliography

[ope] Open Vehicle Monitoring System 3. Version: 3.2.015. URL: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3.

[myn10] LEAF CANbus decoding. (Open discussion). 2010. Accessed: 11 October 2020. URL: https://www.mynissanleaf.com/viewtopic.php?t=4131#p97509.

[nis15] About mounting external communication equipment on the OBD-II connector. 2015. Accessed: 17September 2020. URL: http://www.nissan.co.jp/RECALL/DATA/info151224chui.html.

[elm16] ELM327 OBD to RS232 Interpreter. 2016. Accessed: 2 August 2020. URL: https://www.elmelectronics.com/wp-content/uploads/2016/07/ELM327DS.pdf.

[elm20] FAQs. 2020. Accessed: 20 September 2020. URL: https://www.elmelectronics.com/help/faqs/.

[DanielOster] Daniel Öster. Nissan LEAF CAN bus messages. Accessed: 20 September 2020. URL: https://github.com/dalathegreat/leaf_can_bus_messages.

[JRPollock17] J R Pollock. LeafSpy Help. 2017. Version: 1.1.1, Accessed: 27 November 2020. URL: http://www.leafspypro.com/wp-content/uploads/2017/09/LeafSpy-Help-1.1.1.pdf.

[KaiMorich] Kai Morich. Serial WiFi Terminal. Version: 1.21. URL: https://play.google.com/store/apps/details?id=de.kai_morich.serial_wifi_terminal.

25



https://www.mynissanleaf.com/viewtopic.php?t=4131#p97509

https://www.mynissanleaf.com/viewtopic.php?t=4131#p97509

http://www.nissan.co.jp/RECALL/DATA/info151224chui.html



https://www.elmelectronics.com/help/faqs/

https://github.com/dalathegreat/leaf_can_bus_messages

https://github.com/dalathegreat/leaf_can_bus_messages

http://www.leafspypro.com/wp-content/uploads/2017/09/LeafSpy-Help-1.1.1.pdf

http://www.leafspypro.com/wp-content/uploads/2017/09/LeafSpy-Help-1.1.1.pdf




26 Bibliography

Index

AAT commands, 19AV-CAN, 19AZE0, 11

CCAN, 19CAN protocol, 19Car-CAN, 19communication protocol, 19controller area network, 19

Ddiagnostic connector, 19diagnostic tool, 19

EELM327, 19ELM327, 11ELM327 compatible, 19EV-CAN, 19

GGID, 19

IISO 15031-3, 19ISO 15765-4, 19

KkBd, 20

OOBD-II, 20on-board diagnostics, 20

Pparameter ID, 20PID, 20

SSAE J1962, 20SoH, 20

Tterminal application, 20Type A diagnostic connector, 20

27

Nissan Leaf OBD-II manual

Documents

Transcript of Nissan Leaf OBD-II manual