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).