![]() |
OBD2 Gauge panel
Hello,
Here's an OBD2 based gauge panel I did for my BRZ that shows boost/AFR and 3 temperatures using a standard ELM327 Bluetooth-based scantool driven by a Windows Store (UWP) app. The release is on github, and open source, and also includes a template for a sheetmetal gauge face. The github page links to a youtube of me demoing it on a freeway and a few local roads, and there's a secondary link of the gauge face startup sequence in the description of that video that's a lot more clear to view the indicators on than the live video: Tinast_Public I started on this when someone put up their (IIRC, Arduino-based) OLED oil temperature sensor reader (IIRC, again) on this forum, and I also wanted to put something more unique in my car than the standard off the shelf sensors people get. Anyway, I'd be interested in knowing if anyone in the BRZ community finds this useful. Right now I'm considering whether I should put more development effort into this or move onto something else, as right now I feel like it's kind of in a completed state but there's also a few areas that I think would be useful to add functionality into. |
excellent! I seen this before and I'll probably go ahead and make one from a Raspberry Pi for the track or integrate it into the head unit somehow.
|
Here's the guide I wrote for setting up a Raspberry Pi in my car and putting an app on it.
|
i want to do a direct connect to the sending units, still researching how to interface them.
|
Quote:
All of the ones people care about are 5V reference voltages with separate supply voltages, so hooking them up to the ADC pins on a Raspberry Pi or Arduino should be no big deal. All you'd need access to is the sender data sheet for calibration purposes. Personally I'd just buy a few off the shelf examples to experiment on before I started splicing into my car. When I looked into the O2 sensor for instance, it has a ~2-4.4V band, but it's effectively a wideband sensor. You can just tap into the sense wire and hook it up to the IoT device of your choice. The Raspberry Pi uses 3.3V logic levels, so it might need a buffer, but there are plenty of those floating around. Incidentally, which is probably why almost noone uses ELM327 for sender interfacing. I found it to be pretty obtuse to write software for compared to how just hooking things up to GPIOs would be. The ECUtek logging software I use appears to just read the whole ECU memory over CAN and decode the individual registers from it as one multiframe request, but I found my solution to be almost as responsive as there's, so I don't think there's much reason for me to look into it. I doubt they'd share with anyone how they're doing that, anyway. |
| All times are GMT -4. The time now is 04:21 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
User Alert System provided by
Advanced User Tagging v3.3.0 (Lite) -
vBulletin Mods & Addons Copyright © 2026 DragonByte Technologies Ltd.