NorCal FJs

FJ Cruisers of Northern California

Hi, I am writing a program to read out the OBD-2 info out of the FJ and display on a computer, using a 13$ interface bought on ebay. I now have various parameters like speed, RPM, temperatures of intake and coolant, MAF etc etc

Do you know if there is any non-standard PID that may be of specific to the FJ (or Toyota) that can deliver interesting information?

I am NOT trying to do an application do "clear codes" or deal with any engine malfunction. Only to get and display data as if it was an "extended" dashboard.

Thanks!



Views: 154

Reply to This

Replies to This Discussion

Weekends are good. Let's discuss again in a few days to see what's best. Anybody that is interested may join of course (I live in Redwood City and it would be just so much easier to meet here).

Calimero "il pulcino nero" (the black chick) is extremely well known in Italy. "Ava, come lava!" (Ava, how it washes!) is the famous line this chick became famous for in the '60s in a detergent (Ava) commecial. It gives me so nice memories anyway, when in the early 80s I was little and I stayed at my grandma's... :)
Awesome, lets keep the meetup in mind maybe for the next weekend or the following one. Redwood would be fine for me.

Although we are working on different platforms, looks like there's a lot of overlap between what you are trying to do and what I'm just beginning to dive to. I'm in touch with the main developer at goLink and I'm trying to see if I can grab an SDK for the iPhone from him.

Lol, you definitively have lived through Calimero. That toon was awesome.
I only got to know about it during my years in Tokyo, it wasn't playing on TV that often anymore, but it was one of those cartoons that people would reference all the time. It was pretty big in the 80's there as well:
http://www.youtube.com/watch?v=s6f3jEygFvA
Hey Alessio you might want to take a look the device I have on my FJ, it might help you with
your creation..it's called REV by devtoaster.

here is a video link..iREV
Yeah the graph capability is interesting indeed. Actually I made another application few weeks ago to read from a 3D accelerometer (and, theoretically, calculate the inclination etc) that makes a graph. Unfortunately my accelerometer is defective and I am waiting for a new one to continue development, but I have a screenshot here:

http://www.manoweb.com/alesan/temp/screenshot01.png

As you can see the graph is too unstable, due to the defective part, but that should give an idea.
FYI, using the goLink adapter + iPhone, below is all the readable sensors I got on my first test right now.
All data comes in in pretty much *almost* realtime ( there's what seems to be a 300ms + - delay ).

Cool thing about this adapter and iPhone combination, is that all your recorded data, together with GPS coordinates gets posted to fuzzyluke.com under your account, so you have historical access to all that from a web browser.
The app then grabs all that data and calculates an approximate MPG, which for me keeps on changing a lot, ranging from 17 to 25MPG. I will confirm accuracy once I fill up my tank sometime this week.

Personally, all this data is a bit too much to handle for me, it definitively feels like a total info overload, so I think there is still some space to improve both the iPhone app and the web app making design and UI simpler in the surface, and letting you drill down into the detail if needed.

------- Detected Sensors - Protocol: CAN 11-bit 500 Kb -------

01 - MIL Active / Number of DTCs / Tests Supported
03 - Fuel system status
04 - Calculated engine load value
05 - Engine coolant temperature
06 - Short term fuel trim Bank 1
07 - Long term fuel trim Bank 1
08 - Short term fuel trim Bank 2
09 - Long term fuel trim Bank 2
0C - Engine RPM
0D - Vehicle speed
0E - Timing advance
0F - Intake air temperature
10 - Mass Air Flow
11 - Throttle position
13 - Oxygen sensors present
15 - Oxygen voltage: bank 1, sensor 2 / Short term fuel trim: bank 1, sensor 2
19 - Oxygen voltage: bank 2, sensor 2 / Short term fuel trim: bank 2, sensor 2
1C - OBD standards to which this vehicle conforms
1F - Run time since engine start
21 - Distance traveled with malfunction indicator lamp (MIL) on
24 - Equivalence Ratio: O2S1 / Voltage: O2S1
28 - Equivalence Ratio: O2S5 / Voltage: O2S5
2E - Commanded evaporative purge
30 - # of warm-ups since codes cleared
31 - Distance traveled since codes cleared
33 - Barometric pressure
34 - Equivalence Ratio: O2S1 / Current: O2S1
38 - Equivalence Ratio: O2S5 / Current: O2S5
3C - Catalyst Temperature: bank 1, sensor 1 / Catalyst Temperature: bank 2, sensor 1
3D - Catalyst Temperature: bank 1, sensor 2 / Catalyst Temperature: bank 2, sensor 2
41 - Absolute load value
42 - Command equivalence ratio
43 - Relative throttle position
44 - Absolute throttle position B
45 - Absolute throttle position C
47 - Accelerator pedal position E
49 - Commanded throttle actuator
This list matches mine. Yes many of those values seem not so important but when you learn what they are for then you want to keep them monitored. Difficult task to design an UI for this.
Keep # 33 - Barometric pressure that would be handy when camping
I have it on the program. I want to check against a barometer (?) to see the accuracy of the reading. I have one I just have to find it
Great job, can't wait to see the finished product. Is there a parameter for automatic transmission temp? I'd love to be able to monitor that.
Unfortunately I do not think that information is available with standard PIDs. Toyota may have a sensor and a proprietary code for that, but I do not know it. If you find any info, please let me know... (PS I have a MT myself so I would not be able to check if it works)

bye
as

RSS

Badge

Loading…

NorCal FJ Twitter Feed

The NorCal FJ Shop

The Black Bear Bag
Use it for school, as a bug-out bag, or for your spy gear that only you know about.

SHOP NOW!

NorCal FJ Network Status

© 2024   Created by NorCal FJs.   Powered by

Badges  |  Report an Issue  |  Terms of Service