Introduction: Arduino Car Display

I built an on-board diagnostics (OBD-II) based display using a 7" TFT LCD from Adafruit, a Teensy 3.6, the Freematics OBD-II I2C Adapter, and some cheep backup sensors I found on Amazon. The display has two pages: one for when my Honda Accord is in drive and one for when it is in reverse.

When my car is in drive, the RPM, MPH, engine load percentage, battery voltage, cabin temperature, and engine coolant temperature are displayed (there are several other vehicle statistics available to display if one does not want these).

When my car is in reverse, the Arduino IDE compatible Teensy 3.6 reads an animated bitmap image of my car I found online, displays it, and then reads the backup sensors. The four sensors each have their distance in feet plus an animation behind the car that changes color based off of how close the object is to the car (just green means < 5 feet, green and yellow means < 2.6 feet, and green, yellow, and red means < 1 foot).

Finally, I added the capability to dim the display at night.

The end result looks great and functions very well in my car. I even ended up installing it in the center console, which was a whole other process that I won't get into in this instructable. The list of parts that I used to create this LCD display are below.

1) Freematics OBD-II Adapter - $35

2) Backup Sensors - $30

3) 7" TFT LCD Display - $38

4) SPI based LCD Display Driver - $35

5) Teensy 3.6 - $30

6) Level Shifter - $4

7) 74HC125 Tri State Buffer IC -$6 for 2 pack (I'm sure you could find this cheeper elsewhere)

8) MicroSD Card >= 1 GB - $4

9) Wire, capacitors, and resistors.

10) (optional): DS18B20 Temperature Sensor - $8

11) (optional): OBD-II Splitter - $10

12) (optional): Add a circuit fuse cord - $8 for pack of 5

Step 1: Reading the Backup Sensors

This step is tricky because these backup sensors communicate to a transceiver and then to a small LCD as seen in the picture above. I wanted a way to get rid of their display and use my own. With the help of a website I found after some googling (Hacking reverse parking sensors), I was able to read the proprietary communication protocol that the transceiver sends to the LCD screen. For some reason, the communication protocol is not a typical one such as I2C, UART, CAN, USB, etc. and the protocol differs depending on the supplier. I highly recommend that you purchase the set I linked above if you are going to use my code because it was specifically written for those sensors.

Before disconnecting the LCD they provided, I probed the three wires joining the transceiver and the LCD. There was +5V red wire, ground black wire, and a blue wire. After hooking up my oscilloscope to the blue wire and ground, I saw a trace similar to the picture seen above but not exactly (I used the picture from the website linked above). My trace had a HIGH longer duration start bit, followed by 17 more shorter duration bits. The bits 0-5 after the start bit did not have useful information. Bits 6-8 correspond to sensor A, B, C, or D. Bits 9-16 corresponded to the length in meters. I included an Arduino IDE sketch that reads the sensors and outputs the data over the serial console.

Step 2: Creating the Bitmap Image and Putting It on a MicroSD Card

I used a free photo editing software called GIMP to crop and resize an image of my car from the top view. I then exported the image as a 24 bit bitmap image named "car.bmp" that is 110 pixels by 250 pixels. I uploaded this to a microSD card and put the microSD card in my Teensy 3.6 microcontroller.

The main reasons I went with the Teensy 3.6 instead of an UNO was the speed at which the Teensy could read an SD card and display the image using the RA8875 display driver. Using an UNO, the process took about 8 seconds, while a Teensy 3.6 took 1.8 seconds.

Step 3: Connecting the Hardware

Adafruit has a really good looking 7" TFT LCD that is driven by an IC called the RA8875. I chose this display and display driver for two reasons. First, there are extensive libraries prewritten for the display. Second, the display driver can talk to any microcontroller over SPI, meaning there aren't that many wires connecting the microcontroller to the RA8875.

There are two downsides to this setup. First is the fact that there is a hardware bug with the RA8875 board from Adafruit requiring the use of the 74HC125 tri-state buffer IC if you want to use any SPI based device such as a SD card. To more fully understand the hardware bug, please read the following forum. Second, is the relatively long amount of time it takes for images to be sent to the LCD. Also, the long amount of time it takes for an image to be sent to the LCD is due to the SPI connection, which is limited by the microntrollers' clock speed and the large amount of data that has to be sent to the display driver over very few wires.

I created a Fritzing schematic so that anyone that would like to create this display can easily read what pins on the Teensy 3.6 connect to. I included a .frz file below. The only two components that aren't labeled are the capacitors, which are a 1F 16V electrolytic capacitor and a 100μF ceramic capacitor. I included these to make sure the power to the Teensy microcontroller was steady DC +5V and did not contain any voltage spikes (may not be necessary but I included them because a car's voltage supply can fluctuate quickly depending on the load on the battery).

A few things to mention about the components. First, the level shifter takes any 5V signal and turns it into a 3.3V Teensy 3.6 safe voltage. This is necessary for the OBD I2C adapter as well as the backup sensor transceiver. Second, the I2C lines of the teensy require 4.7kΩ pull up resistors. Third, the four resistors connecting the "night time wire" (the dimming wire) and the "backup engage wire" are necessary to serve as a voltage divider to bring the 12V-13V signals down to about 2.5-3V signals.

NEW 7/22: I found the internal temperature sensor of the OBD-I2C module to be outputting very strange numbers. Sometimes it would work, but most of the time, the module was outputting temperatures above 400 degrees F. Because of this, I decided to add my own ds18b20 temperature sensor. You are more than welcome to use any type of temperature sensor here, but you will have to edit the Arduino code.

Step 4: RA8875 Display Driver and Graphics Design

The RA8875 display driver has a library called the Adafruit_RA8875, which I utilized when creating the shapes that are seen on the first page and second page. The library for the RA8875 can only create lines, rectangles, rounded rectangles, triangles, ellipses, and circles, so the graphics have to be designed in a clever way to create more complex shapes. For example, the gray ring on the first page is actually a full gray circle of a larger diameter followed by a full black circle of a smaller diameter. Also, one small section of the backup sensor page contains 2 triangles arranged in such a way that they make a polygon shape. I did this so that I could change the color of an individual section of the backup sensor page. The Arduino file for the display contains an array of points that I used to keep track of where the triangles and other shapes were.

I used this great website to pick RGB565 colors and define them in the sketch so I could use non-default colors already pre-defined in the Adafruit_RA8875 library.

In terms of fonts, the Adafruit_RA8875 library only supports one unless you comment out a section of the library, which allows you to use the fonts the Adafruit_GFX library. I included the modified Adafruit_RA8875 library below. I just commented out a few lines of code and was then able to use the fonts in the Adafruit_GFX library. Also, to use the 7 segment font that I used in this project, please make sure the "FreeSevenSegNumFont.h" file that I is in the fonts folder in the Adafruit_GFX library.

Step 5: Uploading the Sketch

To upload the sketch to a Teensy 3.6, you will need to install Teensyduino. Then you will need to replace the Adafruit_RA8875 and Adafruit_GFX libraries in the teensy library location (not your typical location in documents). On Mac, I had to right click on the Arduino application icon in applications, and then navigate to /Contents/Java/hardware/teensy/avr/libraries. On windows, I am pretty sure it is under your C drive in Program files x86, Arduino, and then the hardware folder in there. Once you do that, you will need to change the sketchbook location in the Arduino application by editing it in preferences to where ever your teensy libraries are (i.e. /Applications/

NEW 7/22: Because of the internal temperature sensor issue I talked about earlier, I had to install a DS18B20 module temperature sensor. You will see 4 arduino sketches in the zip file. Please upload the display_code sketch if you want to use the internal temperature sensor of the OBD-II I2C module. Please upload the display_code_with_new_temperature_sensor sketch if you want to use the DS18B20 module I linked above.

Then, use the picture I have above to make sure your teensy settings match the picture. I found overclocking the teensy to 240MHz did not allow the I2C OBD-II adapter to communicate with the teensy. Finally, just click upload.

I wrote pretty extensive comments in the arduino sketch files. Please look there for an explanation of how the software works. Please feel free to contact me with any questions. I will try to answer them to the best of my ability. Good luck!

Step 6: 3D Print a LCD Case

I created a 3D printed LCD top and bottom cover to protect the 7" display. I have attached the .IPT inventor part files as well as the .STL files.

I also included a part called backup_sensor_ring.ipt, which is a ring that fits around those backup sensors I linked above. My car already had pre-drilled backup sensor holes that were too big for the backup sensors I bought on Amazon, so I had to create a ring that would fit onto the backup sensors. If you are going to drill into your bumper with the included circular drill piece in the set, you won't need this part.

Step 7: Splitting OBD-II Port So Arduino Only Has Power When Car Is Running

I realized shortly after installing my display that the display was always on, even when the car was off. Looking into the OBD-II pinout, I found that the 12V power line to the OBD-II connector is always connected directly to the battery.

To get around this, I purchased an OBD-II splitter, cut the wire going to pin 16 on one of the two connectors on the splitter, and then connected that cut wire to an add a circuit wire.

Then, using my multimeter, I went to the driver's side fuse box and tested the existing fuses to see which fuse got power after the key was turned into the ignition.

Finally, I connected the add a circuit wire to the fuse that I located so that the display now only turns on when my car is running. Please do some research into how to properly add a circuit to your car. I found this youtube tutorial to be a good one.


Ruzrox (author)2017-07-20

Hello,very nice project!!!
Can this project made with a raspberry?(especially the gauges)
Thank you for posting!!

RyanM415 (author)Ruzrox2017-07-20

I do not think you could do this project with a rasperry pi. This is an Arduino based project so none of the code I wrote could be used. You would have to basically redesign everything. The reason I went for Arduino over rasperry pi is due to the 10-60 second startup time before a raspberry pi is able to run a python program. I wanted this display to turn on almost instantly.

If you would like to still try to use the raspberry pi, I would look at the python module pygames. It can draw shapes and also fonts in python. You would also have to use a different display since this display's library is only written for Arduino. Finally, you would have to email the Freematics OBD module creator to see if there is a library written for rasperry pi. I do not think there is, so I am not sure how you would get OBD data (rpm, speed, etc.).

MyN14 (author)RyanM4152017-07-31

It does indeed take up to 30 seconds to boot with a raspberry pi 2 and raspbian for instance.

However, when you compile your operating system with buildroot, you can reduce the 30 seconds delay down to 3 seconds.

RyanM415 (author)MyN142017-08-01

Very interesting! So this video is showing a python program being run using a buildroot instead of rasbian? Any good instructables on how to do this?

ArtemyN (author)RyanM4152017-07-25

You should use Ardu as intermediate (interface) device. Leaving controls and visualization to RPi. Ardu will work as acquisition and calculation module (in real time).

IanU5 (author)2017-07-23

Fantastic build. You know you could do away with the OBDII interface as the Teensy has CAN capability and the library is available?

RyanM415 (author)IanU52017-07-25

Thats a really interesting point! I knew the Teensy has CAN capability, but I didn't look hard enough to find a library. The only extra thing you would have to add if you took away the Freematics module is a 12V to 5V DC-DC converter since the Freematics module has one built in.

Wrrr 10-G (author)2017-07-24

Very, very fine piece of work. Hat's off to you sir.

Dram229 (author)2017-07-22

Nice Instructable. Good level of detail. I think I'll try this one. Thanks so much for posting it!!!!

Raphango (author)2017-07-20

Great! Congratulations!

DougM95 (author)2017-07-20

This is awesome. One quick question...Does it create an animation of an object that is behind you when you backup? I don't mean the actual object, but something visual that shows it getting closer to your car as you back up?

RyanM415 (author)DougM952017-07-20

I don't exactly know what you mean, but the reverse mode draws either a green, yellow, or red shape behind each one of the backup sensors depending on how close the object is. The video that I have at the top of the page probably will be the best way to understand what the reverse mode can do. That video shows what happens as a person approaches the back of the car at the center.

rnmerchant (author)2017-07-20

I like this! Puts a number of things together.

I have an older honda, though, without backup cameras so that would be a barrier... But I was rather interested in the first, 'forward', page with car data. Does the OBD output include enough data that it could give fuel consumption and engine efficiency data too? Thanks.

RyanM415 (author)rnmerchant2017-07-20

I found that my honda accord only supported a few OBD commands. The most interesting ones I chose to display on the main page. I also wanted a MPG reading or fuel %, but apparently most hondas do not support those commands over the OBD port. According to the Freematics OBD adpater, there are a lot more possibilities, however, not all car manufacturers support reading the commands. This is the list of pre-defined PID commands from the Freematics website:

Some commonly used PIDs are defined in OBD library as following.


  • PID_RPM – Engine RPM (rpm)
  • PID_ENGINE_LOAD – Calculated engine load (%)
  • PID_COOLANT_TEMP – Engine coolant temperature (°C)
  • PID_ENGINE_LOAD – Calculated Engine load (%)
  • PID_ABSOLUTE_ENGINE_LOAD – Absolute Engine load (%)
  • PID_TIMING_ADVANCE – Ignition timing advance (°)
  • PID_ENGINE_OIL_TEMP – Engine oil temperature (°C)
  • PID_ENGINE_TORQUE_PERCENTAGE – Engine torque percentage (%)
  • PID_ENGINE_REF_TORQUE – Engine reference torque (Nm)


  • PID_INTAKE_TEMP – Intake temperature (°C)
  • PID_INTAKE_PRESSURE – Intake manifold absolute pressure (kPa)
  • PID_MAF_FLOW – MAF flow pressure (grams/s)
  • PID_BAROMETRIC – Barometric pressure (kPa)


  • PID_SPEED – Vehicle speed (km/h)
  • PID_RUNTIME – Engine running time (second)
  • PID_DISTANCE – Vehicle running distance (km)


  • PID_THROTTLE – Throttle position (%)
  • PID_AMBIENT_TEMP – Ambient temperature (°C)

Electric Systems

  • PID_CONTROL_MODULE_VOLTAGE – vehicle control module voltage (V)
  • PID_HYBRID_BATTERY_PERCENTAGE – Hybrid battery pack remaining life (%)

Additional defines can be added to access all OBD-II PIDs which the car’s ECU provides.

You will have to run the OBD test sketch on the Freematics website to test what your car can output.

squirrelsnuts (author)2017-07-20

Wow. This is impressive! And well documented and explained. Good work!

arthur_muh (author)2017-07-18

Very nice!

RyanM415 (author)arthur_muh2017-07-18

Thank you!

MikeG303 (author)RyanM4152017-07-20

Wish I was smart enough to pull it off. Cool project.

UncleEd (author)2017-07-20

Definitely looking like big boy toy time at my house.

Fyreye (author)2017-07-20

This is a serious level of cool.

DejayRezme (author)2017-07-20

Wow, pretty awesome! Nice project!

jwzumwalt (author)2017-07-18

This great! I was planning on something simular using engine sensors but I had not thought of using the existing OBD output. Thanks for the great insperation :)