New gauge project...
 

EDIT: Older cruft is bellow the line

Github: https://github.com/stirobot/arduinoModularTFTgauges

Demo video: [ame="https://www.youtube.com/watch?v=JIIwZtxxgqY"]Modular arduino TFT gauge mode switching - YouTube[/ame]



Parts used:
arduino mega (I actually use a clone): $15 - $45
assorted wires: $free-$10
a button $2
a 1.8" tft (http://www.adafruit.com/products/358 or clone): $10 - $20
a micro SD card: $0-$texas
an OBD II UART thing (https://www.sparkfun.com/products/9555): $60
a case to make it look pretty: $0-$30 (if you bought a specific case or two or had your own laser cut or 3d printed)

Total: Somewhere around $90-$182

__________________________________________________ _____________

Some of you (maybe 1 or 2) may remember me from iwsti (sti robot). I had this gauge project that went in many different directions over the years. I'm considering reviving it and figuring out a way to mount in cleanly in the BRZ/FRS.

It is arduino powered, the source is open, and most of the sensor code is written. Here is the original thread from eons ago: http://www.iwsti.com/forums/gd-inter...setup-out.html

Here is the google code page: https://code.google.com/p/robotmeter/

To add to the confusion I've written various UI's for it in the past:
1. 2 line x 16 character LCD - this fit perfectly in the clock bezel of the GD impreza and the code for this is the most mature.

[ame="https://www.youtube.com/watch?v=vNwBDjoZ7mY"]robotmeter clips - YouTube[/ame]

2. A small touchscreen - this never worked out due to a very buggy api for the touchscreen.
3. A 7 segment display

[ame="https://www.youtube.com/watch?v=-bqscDTiXdY"]Simple 7 segment boost gauge - YouTube[/ame]

4. A small 1.8" LCD - nice graphics, good api, some charts written, etc. Also has a micro sd card and a good api for logging to it.

http://i.imgur.com/NJXvqgt.jpg

http://i.imgur.com/iDgbzKQ.jpg

So, questions:

-How would I go about mounting something like this in the BRZ/FRS? I was thinking that if I used the 1.8" screen, I could mold something into the corner of the cluster that occludes the analog speedo. Then I could scan it and 3d print it.
-What essential readouts is the BRZ/FRS missing? I was leaning towards oil temp, oil pressure, and accelerometer.
-I was also toying with the idea of custom making an analog look meter driven by a stepper motor. I've found several companies willing to print or etch gauge faces that I like/draw/etc.
-I also though that if I ever make this a kit of some sort I'd power it via the obd II port...although I have no plans to read from the obd II port...and no plans to make a kit...

Basically if you could make it, what would it look like and what would it do?

For the mods: I'm not selling anything (at least yet)...all of the code is open source...etc.

Oil pressure is only "ok" or "trouble", not an actual pressure sensor, so that would require more additional hardware/wiring than sensors already in the car stock.

Yes, exactly. I've written code for several off the shelf (autometer is the best) sensors to work with the arduino.

@nelsmar, you and the OP should collaborate ;) :D.

The BRZ/FR-S/GT-86 (hereto referred to as "the 86" or "the twins") isn't really missing much, but it doesn't display everything. With custom PIDs, accurate (Very accurate... the factory primary 02 sensor has turned out to be very accurate and effectively a good wideband for NA useage) AFR, coolant temp, oil temp, and (iirc) IATs are readable from the ECU. Basically, depending on powerplant application (NA, SC, or TC), you still need boost and MAYBE EGTs, and (only if you really want to) oil pressure.

For turbo: coolant and oil temps, IAT, AFR, and boost. For SC: boost with failsafe if running a wastegate, coolant and oil temps, IAT, AFR. For NA: coolant and oil temps, IAT.

Anything else is pure personal preference and DBL (das blinken lights).

I've never done OBD II...but there are several bodies of code to work from if I wanted to do that.

I'm really just looking for a project.

So would OBD-II -> analog A/F be cool, maybe OBD-II -> digital A/F?

This guy has some interesting stuff: http://arduinodev.com/

I'd be more interested in digital oil/coolant temps, digital IAT, digital afr, analog boost, analog oil pressure. But that's just me. Me staying NA, and maybe later going to SC, I'm more concerned about temps if I'm going to be running the car hard in the heat to make sure it doesn't get too hot or is cooling down properly afterwards.

I'd definitely want this screen on the right side of the gauge cluster in that blank spot on the bezel.

The nice thing with ODBII readings is that you don't need to add extra sensors and a controller to read certain items. So it eliminates clutter and complexity of install.

I'm intrigued about this spot to the right of the dash. Can you really read stuff there without the wheel getting in the way?

http://arduinodev.com/hardware/obd-kit/

The API is very very straightforward.

Yeah, you can. Not without some obstruction from the wheel, but enough to get the general idea for the data.

If I wanted a clear, unobstructed view for a guage, I'd go with A-pillar mount or defrost vent pod mount. For general "info at a glance", the space to the right of the cluster on the bezel is just fine.

One of the projects l'd love to do is to replace the clock near the gear shifter with a simple gauge display (similar to the 7 segment example). I don't need constant vision of the data but it would be nice to see AFR, G's.

I'll have to look at your code and mess around with it! Thanks for the link and your work!

Please make something to cover up the analog speedometer, it's basically useless. I've been contemplating something, two gauges or a LCD screen, to cover it up and make that space useful.

I miss the gauges my RX-7 had, four little round gauges off to the left that actually worked and showed a lot info. http://www.dragtimes.com/images-clas...1028158028.jpg

I like your idea but I suggest looking up OBDII. Most of the info you need is there. I also have a few projects in the pipeline for this car that uses OBDII. Now if I can just make a functional prototype... goodluck!

The suggested location doesn't suck. I spent some time fiddling with where it might look good in this car and that location is probably the best:

http://i.imgur.com/Wi2DnPs.jpg

I'm thinking of making this more modular this time around. How about a config file where you name your sensors per page and set warning and colors and stuff in there?

Something like this...

The library I'm considering has these PID's written into it: https://github.com/stanleyhuangyc/Ar...es/OBD/OBD.cpp

I'm sure others could be added.

Hi robot,

i'm currently doing a similar project. But I use the mbed.org platform (NXP lpc1768 ) and an adafruit oled display (currently a 0.9inch 128x32). Maybe we can share some common code. I will post my code in the next days. My prototype works fine. But I am not sure where to place the display and a display casing is missing, too.

I forked this: https://github.com/stirobot/ArduinoOBD but I'm a little unsure of how to proceed in adding nonstandard PIDs to his code. The torque app thread is sort of helpful, but lacking full info. 2101 as a code doesn't mean that much to me (although I'm guess it means OBD II mode 2 with a 0x65) and the AC-40 formula tells me it returns at least three bytes (A through C), but does it return more that I need to account for when I expand on this code I've forked?

As far as other progress goes:
-I have made it so a config file on an sd card can read and use settings.
-Splash image setting works.
-Color scheme settings work.
-I've imported functions to pull obd II data and sensor data.
-I've made it so that each page can have whatever sensor is wanted on that page.
-I've started the graphics programming to have these types of pages: 1) a round gauge with one sensor 2) a two sensor bar chart 3) an accelerometer sensor of some type 4) a logging page that displays 4 sensors and dumps them constantly to the sd card in a numbered file.

Subbed

Talk to @nelsmar, @robot on adding the nonstandard PID codes.

On phone I am. Therefore, if mistakes I make, Frank Oz blame you should.

I have some code laying around somewhere for communicating with proprietary requests such as knock, oil temp, and some other misc ones using J15765 communications using an MCP2515 & MCP2551 chipset. I never got around to finishing my setup and i was really torn between where I was going to install my display as well. I am a huge fan of having the minimal gauges in my car and figured I would just make my own setup so i could toggle things on and off for diagnostic purposes. I was looking into sticking a small 1.3" oled into the driver side vent at one point.

I never finished the code but did manage to make some progress. I also was making progress using an STN based chipset (ELM327 replacement) and was working with ST trying to resolve an issue with using raw data not coming in correctly to make a cheaper / easier solution for working with SSM like setups.

My issue right now is deciding between this:
device
http://freematics.com/store/index.ph...&product_id=30
api
https://github.com/stanleyhuangyc/ArduinoOBD
-better example code
-would have to write my own mode 2 code (I believe the 2101 PID for oil temps on the brz/frs is mode 2?)
-author of library is kind of "short" with people on his help forum...not so forthcoming...I did send him and email and posted my questions. I guess we'll wait and see.

OR

the sparkfun one

device
https://www.sparkfun.com/products/9555
api example
https://github.com/sparkfun/OBD-II_U...Quickstart.ino
-less sample code
-fairly straightforward though
-you send obd II instructions to the uart device and is dumps the hex back that it gets from obd II
-You just have to write functions to get the stuff back and do something with it (which is fairly straightforward)

I keep asking about mode 2 OBD II because of the torque pid that was ID'd a little while ago (http://www.gps-laptimer-forum.de/vie...hp?f=20&t=1364). It is 2101. I believe that means it is mode 2 0x65 . On a harry's lap timer thread someone says it returns 31 bytes which seems excessive and incorrect. Although someone did the probing and it might be right. http://www.gps-laptimer-forum.de/vie...hp?f=20&t=1364

Cool. I'd love to have a look at what you've written.

I also started looking at CAN stuff, but got discouraged due to its complexity, lack of documentation, and the amount of proprietary stuff involved.

If you don't want to look at CAN protocol, I suggest looking at the ELM327 chips that has CAN support.

Sent from my Nexus 4 using Tapatalk

From what I read you can get a handful of things from the baseline (low level?) CAN protocol. Other stuff gets complicated from there and differs widely from manufacturer to manufacturer.

I'd also love to use SSM II/III, but don't want to jump right into that right away.

For now being able to get basic OBD II stuff will be nice. Being able to get the special toyota oil temp PID working would be great. Remember that originally this family of projects and code was intended to use external sensors for things that one couldn't get off of obd II, because stuff like the torque app already exist.

I started to look into OBD II because someone suggested it, it isn't terribly expensive, and the "starter" code is already written. Also, I don't like my phone flying at my face because I did a crap job of mounting it before and autox. :bonk:

[ame]http://youtu.be/vAFlXKXZ5j8[/ame]

[ame]http://youtu.be/DdV4eeMd9aE[/ame]

(Those vertical lines are gone.)

subbed , keep it updates , really really would like a way to either put out the oiltemp right into the 7segment display (clock) or to replace it with something that shows the oiltemperature <3

A couple of thoughts here:

-OBD II oil temp to a seven segment display is trivially easy. From a sender is also easy.
-The clock location is a terrible location for a gauge. There is no way to easily glance at it while driving.
-If I could get a hold of a clock/airbag lcd area part from a wreck I could tell you how hard this might be. It could be as simple as sticking a 7 segment module back there of ones choosing (a serially controlled one would be easier to program to). Or you could just wire direct to each segment and write your own controller software (harder/more time consuming).

[ame="https://www.youtube.com/watch?v=Mp4lk7zH-tg"]Dual bar modular arduino obd gauge - YouTube[/ame]

There is an issue with color changing only changing part of the bar's color...I'm working on that now.

(Also, all of the colors are configurable...so in the config file on the sd car I can change them to whatever...maybe in my next video I'll show that.)

Okay i think i'd take this anytime over displaying it on the 7 segment clock

Gesendet von meinem HTC One mit Tapatalk

There we go:
[ame="https://www.youtube.com/watch?v=ggMrQ_KHyXE&list=UUXQz23trpy-vaCZrUAbSCTQ"]Dual bar modular arduino obd gauge themeing - YouTube[/ame]

I should give that color scheme a patriotic name.

The graphics are a little jumpy. This is probably because I'm using a random number generator to generate the values and that makes them jump around. I think i'll make a new "fake"/test harness sensor that only jumps a max of 5 units each direction each time and if it reaches the max or 0 will rest to 0.

Very nice!

I have been working on a very similar device but had no need for CAN or OBD.

Mine is for logging & displaying data in a racecar.
It also uses an Arduino Mega and a 2.8" LCD.

The basic requirements for mine are:
Log serial data (RS-232) from an Innovate system
LC-1 AFR and TC-4 4 channel EGT/CHT
Log Engine RPM from coil (old style tach signal)
Log various analogs
throttle position
oil temp
oil press
batt voltage
Control a small number of loads
Shift light
Alarm light
Display readable data to driver (oil temp/press, AFR, EGT) at low rate.
Trigger alarms and alert driver via Alarm light.

I have all of that with code working and logging data to a SDcard.
My latest upgrade was to be a 2.8 TFT Touchscreen, but I am having trouble getting it to work.

I also intend to experiment with a carbon fiber housing for my display when I am done.
If we agree on a common platform, we could coordiante some.

I chose the sparkfun arduino shields because I drive by their warehouse every day.

Do you have a link to the display you are using in the examples above?

I'm using the ebay varietal of this: http://www.adafruit.com/products/358

I'd love to incorporate your code for the LC-1. You are welcome to whatever I have on my Github repository. I'll warn you, it is messy and written by someone who decided to get a Cog Sci degree and not a CS degree.

The config file now looks like this:

My todo list includes:
-design and build accelerometer display
-clean up graphics
-buy sparkfun obd II device (And test and debug)
-decide if slowing down the animation of the displays is a good idea or not
-add peak displays
-write code to actually log to the sd card on the logging mode (I figure I'll set it up so if the user lingers on the logging page for more than 10 seconds it will start to log.)
-background all sensor check for warnings...then display and alert to those

I got button presses working for page turning tonight:
[ame="https://www.youtube.com/watch?v=JIIwZtxxgqY"]Modular arduino TFT gauge mode switching - YouTube[/ame]

Would there be a way to replace the clock by a tiny gauge ?

Sent from my SGH-I337M using Tapatalk

Sure, I don't see why not. I mean with time and $ anything is possible :D

I bet that there is one circuit board back there that does the clock, the flashers, and the airbag lights. The hard part will be cutting the clock out without harming the other stuff. After that I think it's just a small area with some tinted plex/plastic and you could always put your own thing back there.

That was my primary choice for placement as well. I'm nowhere near your development progress though. It's still on an alpha build and I'm using STM32 micros. Hopeful before the end of the year, a prototype will be done. I'm still working on an improved shift light thing for the car. :(

Sent from my Nexus 4 using Tapatalk

subd

do you have a diagram on how you wired this up to your arduino. Im not very experienced arduino, I have an uno but have barely used it. but I do know how to follow instructions and work with the code a bit.:thanks:

Wiring is all in the source code for the arduino mega to the lcd (it uses high speed SPI).

The mega is weird because it uses different pins for SPI stuff than the standard arduino. I'm using a mega because I included so many libraries that the "sketch" got over the 32k size limitation. The mega uses a bigger chip. It also has multiple serial hookups, so that means you can do uart serial stuff to something like the obd II device at the same time you log to a serial console, which is handy.

Sensors go to whatever analog input on the board you configure them for. The OBD II thing I have yet to buy wires into a Serial connection on the board (the arduino mega has more than one...I have it set at Serial1 now). The obd thing I plan on buying shortly is this: https://www.sparkfun.com/products/9555

I also just realized I didn't put the github link up before: https://github.com/stirobot/arduinoModularTFTgauges

Also, last night I got some peaks displaying on the bar charts and I started spacing stuff out for the accelerometer display.

I also started looking into using acrylic to make cases...so I can put this in my car in a prototype sort of way. Something like this:
http://madlabindustries.com/shop/pro...lic-mega-case/
or this
http://www.instructables.com/id/Home...-LED-Displays/

I also updated the first post to make more sense.