Hacking OBD II

Expensive? Not if you go to the library and copy it. I don't know where you are; I took a 10-minute subway ride here in Toronto just yesterday and walked an additional 3 minutes; this put me smack in front of the entire

The whole point of OBDII is standardized diagnostic codes; there should be none "specific to the Jeep".

What sorts of things are you hoping to do/change/achieve?

DS

Thanks, I use the SF Library a lot and it somehow never occured to me that the SAE Handbook would be there and would contain this!

In addition to the "generic" OBD II pollution control system codes, I have read on line that OBD II also supports manufacturer-specific codes often used for engine diagnostic and performance measurements.

I am hoping to gain access to this information so that I can perhaps display and log it on a laptop or Linux handheld device. There appears to be a small set of OBD hackers already playing with this.

PRS

Are any of these freeware or shareware?

There will most likely be some vehicle-specific codes (P1xxx codes), which are for diagnostics or failures that have no standard code equivalent..

|There will most likely be some vehicle-specific codes (P1xxx codes), which |are for diagnostics or failures that have no standard code equivalent..

Also, I think that once you get away from the govt-specified items like drivetrain, the peripherals are more manufacturer-specific. for example, traction-control codes are likely specific to make.

That's true, there are no standardized codes for those kinds of components, I don't think that non-emissions-related DTCs even have to be retrievable by a standard OBD II scanner..