- Raspberry pi obd2 reader for free#
- Raspberry pi obd2 reader Bluetooth#
- Raspberry pi obd2 reader mac#
Raspberry pi obd2 reader Bluetooth#
#!/bin/bash # BEGIN INIT INFO # Provides: elm327 # Required-Start: # Required-Stop: # Should-Start: # Should-Stop: $null # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Short-Description: Start elm327 # Description: starts the elm327 bluetooth device # END INIT INFO DevNum =99 # DevNum is depending on the rfcom settings /etc/bluetooth/rfcom.cfg case $1 in Write init script that will manage the Bluetooth connection through the /dev/rfcomm99 device.
Raspberry pi obd2 reader mac#
Add the MAC address to the Bluetooth conf file.Ĭomment "ELM327 based OBD II test tool" }.Discover the OBDII mac address or read it from the case:.Find its IP address and connect to it via SSH.Make sure it’s connected via WiFi to the mobile phone.Kingston 32GB SDHC Memory Card Class 10.By doing this I also required a USB WiFi dongle. The solution I came up was to use my phone’s tethering capabilities and get the Pi connected via WiFi. I wanted to keep cabling as clean as possible by powering the Pi from the car’s USB port so I went for another approach. After doing some reading I found out that most of these modems require external power. First thing that came to mind was getting a USB 3G modem. Since I’m a cloudy guy I’m going to run Graphite on my Openstack lab so this means I’m going to need an Internet connection on the Pi. The last step in getting the system done would be to get the Raspberry Pi connected to Graphite. Since I was going to use Bluetooth for connecting the Raspberry Pi to the OBD reader I also needed a USB Bluetooth dongle. After doing some searches I found out that there were some cheap Bluetooth OBD readers on the market and decided to go with that. I had a Raspberry Pi standing on my desk for 2 or more years without turning it on so I thought that would be the ideal time to start using it.Īt this point we have the system’s individual components but we need to connect them somehow to get functionality out of it. Now that I have the data source and destination I also needed the device that processes/forwards it. This would be the easiest task since I had already used Graphite before and knew how easy sending the data and getting the graphs done was. Once I got all the sensor data I needed to graph it somehow. I knew most of the cars have a diagnosis port called OBD which is used for reading data from most of the existing sensors in your car. So there kicked my doer spirit and I started thinking of ways of doing it. This would at least get me some more insight with historical data of the car’s working parameters. The first thought that came to mind was to turn metrics like rpm, speed and instantaneous fuel consumption into easy to read graphs. Numbers are good but, at least for me, it’s hard to interpret them as absolute values and I need to get the whole picture where they stand. Since the car board computer only provides instantaneous and average fuel consumption numbers I can’t really get to do an analysis of how it changed in time.
First thing I noticed has changed was the fuel consumption.
Raspberry pi obd2 reader for free#
While driving back from Romania to Czech Republic I was thinking that this can’t just come for free and I wanted to see how it impacts the car’s working parameters. I’ve recently changed my car’s stock air filter with a performance one which really improved the car’s responsiveness. In this post we’ll see how you can grab car sensors data and turn them into some good loking and easy to watch graphs. Graphing car metrics into the cloud with Raspberry Pi, OBD and Graphite