The OBD2 plug and is my car compatible with AutoPi?
Is your car newer than 1996 (US) or 2001 (EU)? Then the short answer is YES. This is why:
History behind OBD-II
The AutoPi dongle communicates with your car through the OBD-II port of the car. OBD (On-Board Diagnostics) is a communication standard available in all cars after 1996, where it was made mandatory by law. It became mandatory in the European Union after 2001 for gasoline vehicles and 2004 for diesel vehicles. With the new port, all cars implemented a standard communication bus, which original purpose was the retrieve environmental telemetrics about the vehicle for classification.
Today the OBD port is normally used by a repair technician for debugging purposes, as a part of the OBD standard is providing real-time trouble codes from your car. This is also what some vehicle models will display in the dashboard. But the OBD protocol contains much more information than what you see in the dashboard. This is why it is such an excellent starting point for making your car smarter.
Where is the OBD port located?
The OBD port is normally located under the dashboard of your car. Sometimes directly below the dashboard, sometimes behind a small hatch or near the ashtray. It varies from model and make. You will be looking for a connector similar to this:
This is where the AutoPi is plugged in. If you have trouble locating the OBD port, you may be able to find additional help in the owner’s manual of your car.
Can I be sure my car is compatible?
If you want to be 100% sure your car is compatible with the AutoPi, you can look for a sticker similar to the one shown above (vehicle information sticker). Is normally located below your dashboard, close to the OBD port. Sometimes it’s located under the hood in the engine room, it varies from model.
If your vehicle don’t support the OBD standard, but still has an OBD port you may be able to use a subset of the features in the AutoPi dongle.
Other blog posts for further reading
New Software Release Highlights May 2020
There is always room to grow and that is just what we strive to deliver with our recent software release. In this blog, we post all the major highlights, outstanding features and functionalities with our next-generation AutoPi Telematics Unit (RPi3) at the focus, so let’s keep reading!
Switching from Raspberry Compute to Raspberry Zero
During the design phase of the AutoPi, it was decided to use the Raspberry Compute Module. The Raspberry Compute Module is small, versatile and expandable in a lot of ways, which suited the AutoPi project perfect. All the pinouts from the Broadcom BCM2835 processor is available through the SODIMM DDR2 interface on the Compute Module. This gave us a lot of possibilities during the design phase of the AutoPi and therefore the Compute module was an obvious choice for us as a main processor.
Raspberry Pi Dongle: How to Read and Reset Fault Codes From Your Vehicle
The AutoPi IoT platform is much more than your regular OBD-II dongle. But that doesn’t mean that it isn’t able to perform all of the same things a regular OBD-II dongle does (plus much more). One of the common things you would do is to read out details about fault codes in your vehicle. In this blog we will go over the details on how this is done with the AutoPi and how you can combine fault codes with triggers to make automatic alerts.