Arduino Obd-ii Tft Screen

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 = 1 GB - $49) Wire, capacitors, and resistors.10) - $211) (optional): - $812) (optional): - $1013) (optional): - $8 for pack of 5.

1. Arduino Obd Simulator
2. Arduino Tft Touch Screen Code

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, 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.

Arduino Obd Simulator

The TFT driver (ST7735R) can display full 18-bit color (262,144 shades!). And the LCD will always come with the same driver chip so there's no worries that your code will not work from one to the other.

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.

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. 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 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 100xCExBCF 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.7kxCExA9 pull up resistors.

Arduino Tft Touch Screen Code

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.UPDATE 7/22/18: 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.UPDATE 3/1/19: Teensy 3.6 does not start when it is extremely cold. I added a power on reset circuit to make sure it boots properly. The RA8875 display driver has a library called the AdafruitRA8875, 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 to pick RGB565 colors and define them in the sketch so I could use non-default colors already pre-defined in the AdafruitRA8875 library.In terms of fonts, the AdafruitRA8875 library only supports one unless you comment out a section of the library, which allows you to use the fonts the AdafruitGFX library. I included the modified AdafruitRA8875 library below. I just commented out a few and was then able to use the fonts in the AdafruitGFX 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 AdafruitGFX library. To upload the sketch to a Teensy 3.6, you will need to install. Then you will need to replace the AdafruitRA8875 and AdafruitGFX 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/Arduino.app/Contents/Java/hardware/teensy/avr).UPDATE 7/22/16: 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 displaycode sketch if you want to use the internal temperature sensor of the OBD-II I2C module. Please upload the displaycodewithnewtemperaturesensor sketch if you want to use the DS18B20 module I linked above.UPDATE 11/17/17: I fixed several bugs in the software including the DS18B20 outputting a temperature of 185 Fahrenheit, the display not turning on at all in cold weather, and pixels getting stuck in the wrong color when the display is dimmed.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. 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 backupsensorring.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.

I realized shortly after installing my display that the display was always on, even when the car was off. Awesome project! Thank you so much for posting such a detailed explanation on this project. I am also trying to do a car project with a Teensy 3.6(now that I've seen yours I'm wanting to do it as well, i have a 2008 accord) My current one is much simpler with only a hall effect sensor, 10 DOF IMU and a IR temp sensor at the moment. You used multiple different resisters and 2 capacitors, how did you know which ones to use?

Are they all pull-up resistors? And would you post your fritzing file?

Thanks again for this great project! I've updated the fritzing breadboard page and schematic page and attached it above as 'SchematicInstructables.fzz.' The capacitors in the circuit are bypass capacitors or part of the power on reset circuitry. In the schematic update I just released, I deleted one of the two bypass capacitors because only one is really needed to ensure the power supply to the teensy is mostly noise free. The 4.7k ohm resistors are pull-up resistors, which the I2C communication protocol requires. If you want to know why 4.7k ohm, here is a good forum post: Similarly, the 10k ohm resistors are pull up resistors.

10k ohm is a standard pull-up value for non-I2C. They are required for the 74HC125 circuit, which allows the use of the SD card and RA8875 display on the same SPI bus (see this note on the RA8875 adafruit page: ). Finally, the 100k and 22k ohm resistors are used to translate the +12V signals in the fritzing schematic called 'Night Time Wire' and 'Backup Engage Wire' coming directly from your car to +3.3V signals using a voltage divider. Hope this answers all your questions!

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.).