Rev by DevToaster is an application for the iPhone and iPod Touch that allows real-time monitoring of vehicle ECU data from the OBD-II port. Rev interfaces with a WiFi OBD-II dongle.
If your check engine light is on or flashing, REV is able to check the engine code, list all of the engine codes stored in the vehicle, and reset the stored codes or check engine light.
Rev is able to monitor real-time; vehicle speed, RPM, fuel consumption, engine coolant temp, fuel pressure, calculated engine load, throttle position, intake manifold pressure, air intake temp, timing advance, mass air flow, fuel level, barometric pressure, EVAP system vapor pressure, and fuel trim.
A brief video of REV in action is after the break.
The CAN bus, accessible through the OBD-II port, is the channel that holds all the secrets of the modern automobile. If you want to display those for your own perusal, you might consider this nifty tool from [EQMOD].
Yes, it’s an OBD-II dongle that you can build using an ESP32 WROVER module. It’s designed to read a car’s CAN bus communications and display them on a self-hosted web page, accessible over WiFi. The build relies on the dual-core nature of the ESP32, with the first core handling CAN bus duties via the SN65HVD230 CAN bus transceiver chip. The second core is responsible for hosting the web page. Data received via the CAN bus is pushed to the web user interface roughly every 60 to 100 milliseconds or so for information like RPM and speed. Less time-critical data, like temperatures and voltages, are updated every second.
It’s a neat little thing, and unlike a lot of dongles you might buy online, you don’t need to install some dodgy phone app to use it. You can just look at the ESP32’s web page for the data you seek. The graphics may be a little garish, but they do the job of telling you what’s going on inside your car. Plus, you can always update them yourself.
Getting to grips with the CAN bus is key if you want to diagnose or modify modern vehicles. Meanwhile, if you’ve been cooking up your own electronic vehicular hacks, don’t hesitate to drop us a line!
One of the best things about open source software is that, instead of being lost to the ravages of time like older proprietary software, anyone can dust off an old open source program and bring it up to the modern era. PyOBD, a python tool for interfacing with the OBD system in modern vehicles, was in just such a state with its latest version still being written in Python 2 which hasn’t had support in over three years. [barracuda-fsh] rewrote the entire program for Python 3 and included a few other upgrades to it as well.
Key feature updates with this version besides being completely rewritten in Python 3 include enhanced support for OBD-II commands as well as automating the detection of the vehicle’s computer capabilities. This makes the program much more plug-and-play than it would have been in the past. PyOBD now also includes the python-OBD library for handling the actual communication with the vehicle, while PyOBD provides the GUI for configuring and visualizing the data given to it from the vehicle. An ELM327 adapter is required.
With options for Mac, Windows, or Linux, most users will be able to make use of this software package provided they have the necessary ELM327 adapter to connect to their vehicle. OBD is a great tool as passenger vehicles become increasingly computer-driven as well, but there are some concerns surrounding privacy and security in some of the latest and proposed versions of the standard.
The widespread adoption of the CAN bus (and OBD-II) in automobiles was largely a way of standardizing the maintenance of increasingly complicated engines and their needs to meet modern emissions standards. While that might sound a little dry on the surface, the existence and standardization of this communications bus in essentially all passenger vehicles for three decades has led to some interesting side effects, like it’s usage in this project to display some extra information about an electric car’s battery.
There’s not a ton of information about it, but it’s a great proof-of-concept of some of the things CAN opens up in vehicles. The build is based on a Citroën C-Zero (which is essentially just a re-badged Mitsubishi i-MiEV) and uses the information on the CAN bus to display specific information about the state of charge of the battery that isn’t otherwise shown on the car’s displays. It also includes a build of a new secondary display specifically for this purpose, and the build is sleek enough that it looks like a standard part of the car.
While there are certainly other (perhaps simpler) ways of interfacing with a CAN bus, this one uses off-the-shelf electronics like Arduino-compatible microcontrollers, is permanently installed, and has a custom case that we really like. If you’re just starting to sniff around your own vehicle’s CAN bus, there are some excellent tools available to check out.
While we’re currently in an era of comparatively low gas prices, the last few decades have seen much volatility in the oil market. This can hit the hip pocket hard, particularly for those driving thirstier vehicles. Thankfully, modifications can help squeeze a few extra miles out of each gallon of dinosaur juice if you know what you’re doing.
The art of striving for the best fuel economy is known as hypermiling, and involves a broad spectrum of tricks and techniques to get the most out of a drop of fuel. Let’s dive in to how you can build a more efficient cruiser for getting around town.
Step 1: Know Thine Enemy
The MPGuino is a great solution for monitoring fuel consumption in older cars without a trip computer.
If you want to improve your fuel economy, the first step is to measure it. Without accurate measurement, it’s impossible to quantify any gains made or optimise for the best performance. For those with modern cars, it’s likely that there’s already a trip computer built into the dash. Using this to track your fuel economy is the easiest solution. Instantaneous modes are useful to help improve driving habits, while average modes are great for determining the car’s economy over time.
However, many older vehicles don’t have such features installed as stock. Thankfully, there’s a few ways to work around this. For those driving post-1996 vehicles outfitted with an OBD-II port, tools like Kiwi or Scangauge can often track fuel economy. Failing this, most fuel injected cars can be fitted with a device like the MPGuino that monitors fuel injection to calculate consumption. Fundamentally, all of these tools involve tracking the amount of fuel used per distance travelled. Factory tools and OBD-II gauges do it by using the car’s standard hardware, while the MPGuino splices in to speedometer signals and injector triggers to do the same thing with an Arduino. If you do decide to install a custom device, make sure you calibrate it properly, else your figures won’t bear much resemblance to what’s going on in reality.
Of course, as long as your car has a working odometer and a fuel tank that doesn’t leak, there’s always the pen-and-paper method. Simply reset the trip odometer to zero after filling the tank to the brim. Then, when refilling the tank, fill all the way to the top, and divide the miles driven by the gallons of fuel added back to the tank. This isn’t the most accurate method, as the nature of gas station pumps and automotive fuel tanks mean that tanks aren’t always accurately filled to the brim, due to air pockets and devices used to prevent overfilling. Despite this, it’s a handy way of getting some ballpark figures of your car’s performance over time.
Many cars these days come with a basic Heads Up Display, or HUD. Typically, these display speed, though some also throw in a tachometer or navigational graphics too. Of course, if your car doesn’t have one of these stock, hacking in your own is always an option.
[PowerBroker2] developed this HUD in a somewhat circuitous way, but it’s effective nonetheless. An ELM327 Bluetooth OBD-II reader is hooked up to the car, collecting data on speed and RPM. This data is passed to an ESP-32 and Teensy 3.5. From reading the code, it appears the Teensy is responsible for logging data from the CAN bus on an SD card, and running a small OLED display. The ESP32 is then charged with running the LED display that actually forms the HUD. It’s then combined with a 3D-printed housing, some plexiglass, and reflective windshield film to complete the effect.
Hackaday editors Mike Szczys and Elliot Williams sift for hacking gold from the past week. In this episode, we remember John Horton Conway’s Game of Life and its effect on novice programmers. We geek out adding screens to your car with an OBD-II hack, automating a Sharpie clicker as part of a plasma cutter, and 3D printing an incredible RC car that drives every wheel from a single motor. Plus we look at machine-learning for custom backgrounds in your video chats, take a gander at the coming generation of ePaper displays, and we get cultured about yeast.
Take a look at the links below if you want to follow along, and as always tell us what you think about this episode in the comments!
Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!
