Cheap OBD2 Communications on K-line (ISO 9141-2 and ISO 14230-4)

24,778

138

65

Posted

Introduction: Cheap OBD2 Communications on K-line (ISO 9141-2 and ISO 14230-4)

This is just another OBD2 solution for monitoring the sensors in a verhicle. It supports the K-line OBD2 serial communication between a verhicle and a microcontroller. This K-line communication is also known as ISO 9141-2 or ISO 14230-4 (also known as Keyword Protocol 2000 or KWP). Both ISO's are almost similar. This solution differs from the rest that is low cost (for less than 10 euro!!). It is low cost in the way that you don't need an arduino, raspberry pi or smart phone. Just a microcontroller and LCD display so you can use your smartphone for other purposes.

Main features:

  • Shows verhicle engine load, temperature, speed and RPM on a LCD display
  • Optically displaying the engine load via a LED by changing the intensity using the microcontroller PWM module
  • When temperature exceeds 93 degrees a buzzer will be triggered
  • A watchdog will quard communication problems between microcontroller and verhicle ECU

To do:

  • Display stored diagnostic trouble codes in mode 0x03 (routine is included but I have to wait till my car gets troubles)
  • Clear trouble codes / Malfunction indicator lamp (MIL) / Check engine light (routine is included but untested)
  • Support "fast init"

It is tested with a Citroen C1 gasoline (2013) and VW Touran gasoline (2003). Probably it will work for a Peugeot 107 and Toyota Aygo of 2013 as well since they are technically identical. From what I read on the internet there are many flavours on K-line around so there is a possibility it will not suit your car. Maybe some changes are needed to make it work. The source code is provided so you can investigate and change when needed. Maybe you can help extending this list of cars to help others!

Have fun!



Found this site where you can check if your car supports K-line:

http://www.outilsobdfacile.com/vehicle-list-compatible-obd2/citroen

Step 1: Parts

1 x OBD2 Connector 16 Pin Male

1 x Microchip 16f886 microcontroller

1 x 16x2 LCD HD44780 or compatible

1 x BC547 or 2N3940 transistor

1 x LM7805 1A regulator

1 x 330nF ceramic capacitor

1 x 100nF ceramic capacitor

1 x 510 Ohm resistor

1 x 2.2K Ohm resistor

1 x 47K Ohm resistor

1 x 33K Ohm resistor

1 x 100 Ohm resistor, optional (for blue led, please use appropriate resistor for other colors)

1 x LED, optional

2 x 10K Ohm trim resistor

1 x Buzzer 5 volt (< 20mA), optional

Step 2: K-line Initialization and Response

Both ISO's 9141 and 14230 knows a 5 baud initialization sequence. The microcontroller must start this init by transmitting byte 0x33 to the verhicle at 5 bits per second. The total transmit time for transmitting byte 0x33 takes about 2 seconds. After this initialization it is expected to continue communicating at 10k4 baud.

ISO 9141-2 initialization response:

For ISO 9141-2 the verhicle ECU will respond with synchronization byte 0x55. After this, the verhicle will respond with key bytes 0x08 and 0x08 or 0x96 and 0x96. The sync byte with key bytes of the verhicle must be acknowledged by the microcontroller by inverting the second key byte. This will end the initialization part of ISO 9141-2.

ISO 14230 initialization response:

The response of ISO 14230 is slightly different. The verhicle ECU will also respond with synchronization byte 0x55. Only the key bytes are different. In case of a VW Touran of 2003 the key bytes are 0xef and 0x8f. Also here the second key byte must be acknowledged by the microcontroller by inverting it.

Step 3: Stimulus Response

After the initialization process it is possible to submit a request to the verhicle ECU. A request is a sequence of bytes where adressing, a mode, a PID and a checksum is present. The following are example requests:

For ISO 9141-2 this sequence of bytes is 0x68, 0x6a, 0xf1, 0x01, 0x0d and 0xd1.

For ISO 14230 this sequence of bytes is 0xc2, 0x33, 0xf1, 0x01, 0x0d and 0xf4.

The first three bytes are for addressing. The fourth is the mode field. The fifth byte is the data field with the PID and the last byte is the checksum.

In this example mode 1 is used. This mode will show "current data" as how it is at this moment. This mode is perfect for displaying actual information. The data field contains the PID. In this case 0x0d which is the verhicle speed. The checksum is the sum of the bytes with mod 256. See this link for a list of PIDs:

https://en.wikipedia.org/wiki/OBD-II_PIDs

The response is almost similar. The data field reflects actual data which will probably change every request. The following are example responses with 0x00 as data (which is verhicle speed 0).

For ISO 9141-2 : 0x48, 0x6b, 0x10, 0x41, 0x0d, 0x00, 0x11.

For ISO 14230 : 0x83, 0xf1, 0x10, 0x41, 0x0d, 0x00, 0xd2.

This OBD2 solution displays the calculated engine load (PID 0x04), engine
coolant temperature (PID 0x05), verhicle speed (PID 0x0d) and engine RPM (PID 0x0c) on a LCD display.

Step 4: Schematic

The verhicle will supply the circuit with 12 volt via pins 5 and 16 of the ODB2 connector. The voltage regulator will create 5 volt out of this for the microcontroller and LCD.

K-line signals of pin 7 will be converted to appropriate levels via an interface of resistors and a transistor.

The two trimm resistors are used to control the contrast and backlight of the LCD.

On port RC1 you can connect a LED (optional). With help of the PWM module of the microcontroller the intensity of the LED will be controlled by the calculated engine load (PID 0x04).

On port RC7 you can connect a buzzer (optional). When the engine coolant temperature (PID 0x05) exceeds the 93 degrees this port will be enabled.

Step 5: Code

The Microchip XLCD peripheral routines with some small changes are used for the external LCD module (less blurry result with fast changing data compared with other LCD routines).

A routine for displaying and clearing stored diagnostic trouble codes is included. This can be initiated by pressing the switch for 2 seconds. This routine is untested and will most probably not work. Feel free to try if you have a car with trouble codes.

The 5 baud init is also called "slow init". There is also a "fast init". The fast init does not use the 5 baud init as descibed above but starts directly at 10.4 kbps. A StartCommunication request 0xc1, 0x33, 0xf1, 0x81, 0x66 must be submitted prior submitting requests. I don't have a car which supports this fast init so maybe someone can help including it in this code to help others.

You can easily change the code if you want to have miles instead of km.

For simplicity no checksum is checked.

The code can be imported in Microchip MPLAB X IDE v3.20 with compiler XC8 v1.36. For programming the 16f886 microcontroller you need a programmer like pickit2 or pickit3.

A hex file is included in case you want to program the 16f886 with your own programming software/device.

Step 6: Have Fun

I hope you like this project. Have lots of fun building it and monitoring your verhicle!

If you are interested but not able to buid yourself just contact me. Maybe I can help with a programmed microcontroller or complete kit.

"This most beautiful system of the sun, planets and comets,
could only proceed from the counsel and dominion
of an intelligent and powerful Being."

~ Isaac Newton, Principia

2 People Made This Project!

  • milani1387 made it!

  • BadisS made it!

Recommendations

  • Remote Control Contest 2017

    Remote Control Contest 2017
  • Arduino Contest 2017

    Arduino Contest 2017
  • LED Contest 2017

    LED Contest 2017

We have a be nice policy.
Please be positive and constructive.

Tips

Questions & Answers

62 Comments

And picture with fast init sequence:

Hi.

1396amir and milani1387:

I have Sagem S2000-1 on the table and it "IS OBD compliant", but it has errors in implementation in some ways.
(ECU is 9643786680-01, hope it comes from 6FZ/EW7J4 engine, but I am not sure about it.)

first problem:
There is a long time (longer than standard allows) between a tester command and an ECU answer.
ECU answers (just after fast init pattern) after 130ms, but ISO14230 says max. 50ms. Due this, for example Bosch tester model 560 is not able to connect it (it waits for an answer for cca 80ms). See picture.

second problem:
I must have unconnected L-line (pin B3 on ecu).
Once I have it connected to L-line (+12Volt from tester 510ohm resistor), ECU does not
response to fast init patter at all.
Really don't know why. Maybe due to my wiring on the table without any sensors ???

If you will have any news, pls. leave an info here.

Hi this is for milani1387

The ecu's you are trying to connect are NOT OBDII at all but if you use peugeot 206 bosch ecu with automatic transmission (gearbox) you can connect to ecu and see some data

hi bro. why is your last bit of 0x33 is low. in other document, 0x33 is send in 5 baud of speed that include 1 start-low 8 bit 0x33 and 1 stop bit- high. it 's usart frame too.

Hi, will be possible to send data from chip to Raspberry pi by i2c?

Thanks

hi,which software you use to see the byte transmitting and receiving ?

Hi Phanhust,

I use the debugger in the mplabx software. Here I see the received data of the mcu in an array.

Kind regards,

Richard

hi richard

how i can define 3 byte of car 's address?

in my case. i use for motorbike so what is different between car and motor bike??

majority of motorbike in asia also using communication on iso 9141 and iso 14230

thanks

Hi Phanhust,

The best way is to read specifications about your motorbike. Somewhere there must be described how to communicate with the ecu.

Kind regards,

Richard

Hi,

Could i use a 16f628 chip?