Can speed and rev pulses be taken from any of the pins in the OBD II diagnostics socket?

Also, does anyone have the map of what pins are in the OBD II socket?

Nope - use the ECU outputs. OBDII is a data stream.

Cheers
Heath Young

Correct me if I'm wrong but I don't think that the 3rd gens have ODBII sockets. The 380
has.

Wiring diagrams for 3rd gen indicates OBD2 wired for ISO
Even 2nd gen EFI have an OBD/ALDL data stream,& possibly 1st gen EFI

could you hook the OBD2 up to a carputer?

not directly :cry:
needs an interface unit and some software which comes in various flavours, some of it freeware
plenty of info on these sites :D

http://www.scantool.net/

http://www.motorscan.com.au/

They all have connectors to access onboard information. However, 3rd gens and prior are
not OBDII compliant. Also OBD was not a strict standar. Hence the US enforced a more
strick standard with OBDII. The 380, based on the US Galant is OBDII compliant.

My TJ II 2003 is compliant to OBDII has plug near foot rest on the floor. I have an OBDII reader for the car. Interprets 1000 codes.

Mitsi also use it to recode new keys and remote.

Hope this helps

My TJ II 2003 is compliant to OBDII has plug near foot rest on the floor. I have an OBDII reader for the car. Interprets 1000 codes.

Mitsi also use it to recode new keys and remote.

Hope this helps

Ooppss...... :redface: I meant to say pre 3rd gen. The 3rd gens needed to be OBDII compliant as
we were exporting them to the US :redface:

crazy..im doing a carputer soon :D

even the pre-OBD2 2nd gen vehicles can be accessed thanks the work done by the DSMTuner guys in the US.
With their MMCd freeware and interface design your 2nd gen EFI has to reveal its secrets.
I've built one and it works great on a PDA :D

My TJ II 2003 is compliant to OBDII has plug near foot rest on the floor. I have an OBDII reader for the car. Interprets 1000 codes.

Mitsi also use it to recode new keys and remote.

Hope this helps



Could you specify what OBDII reader you are using?

OBD II code reader. Auto Scanner u380. I bought mine on ebay, a chance buy at $41 to the front door

Hope this helps

Okay the U380 is only an auto scanner which reads logged trouble codes, which is half of what OBDII is capable of doing, which brings us back to the fact that 3rd gens are not 100% OBDII compliant.

So far: Yes we can read trouble codes, but no one has been able to read realtime telemetric data which is what we really want.


Personally I think the OBDII stream is there, but the base signal is not OBDII, and from past research it is also not ALDL. However I'm sure if we can work out what the signal type is, then its home run fom there. It may just be a difference in TTL voltage levels. I have yet had the time (nor motivation) to hook up an analyser (or scope for the old skool analogue guys) and see what is coming out.

Sorry I went all technical here, but it might someone out there interested in figuring out how to get data out of that port.

If the OBDII was 100% compliant in the 3rd Gen i'd love to have a ScanGauge II in my car: www.scangauge.com

http://www.scangauge.com/assets/graphics/IMG_2009_withdims.jpg

SCAN TOOL
The ScanGaugeII allows you to troubleshoot your own car, read error codes, and the conditions present when the error occurred. You can also turn off the “Check Engine” light and avoid those costly trips to the mechanic.

* Reads Trouble Codes
* Reads conditions that set the Trouble Code
* Clears Trouble Codes
* Turns off the "Check Engine" light
* Tells you when vehicle is "Ready" to pass OBDII testing
* Make and store up to 10 rewritable special codes to send to the vehicle computer

DIGITAL GAUGES
Display 4 gauges at a time from the 12 built-in digital gauges. the information is presented in Real-time!

* Fuel Economy
* Fuel Rate
* Battery Voltage
* Coolant Temperature
* Intake Air Temperature
* Engine Speed (RPM)
* Vehicle speed (MPH)
* Manifold Pressure (not available on some vehicles)
* Engine Load
* Throttle Position
* Ignition Timing
* Open/Closed Loop

TRIP COMPUTER
Automatically tracks four sets of trip data - Each with 11 individually stored parameters.

* Maximum Speed
* Average Speed
* Maximum Coolant Temperature
* Maximum RPM
* Driving Time
* Driving Distance
* Fuel Used
* Trip Fuel Economy
* Distance to Empty
* Time to Empty
* Fuel to Empty

Hi guys
That's interesting that so far only DTC info has been accessed on the 3rd gen OBD2 port.
Might be useful to plug in a protocol interpreter like an ElmScan and use a PC terminal emulator to see if we can talk to the vehicle at command line level. If it responds then we might be able to get it to tell us what parameters it supports.
I've got the hardware but unfortunately being a 2nd gen person I can't try it :cry:

Guys - you can get a scan too that is a proper data logger as well - 300Hours logging (plus you can clear SOME codes) for $265.

In this months edition of silicon chip magazine - http://www.siliconchip.com.au/cms/A_107695/article.html

Conclusion
The CarChip E/X costs $286 plus $7.70 postage. A cheaper version (the CarChip), with a shorter 75-hour logging capability, is available for $217.80.

For your money you get an effective and small data logger that can remain plugged into the car semi-permanently. It will clearly show how the car is being driven on each trip. It also reads fault codes and is able to clear some of them. Furthermore, if you need to monitor sensor outputs (useful if the car is being modified), then the CarChip will do that as well.

For further information, contact Ecowatch on (03) 97617040 or browse to their website at www.davisinstruments.com.au

The CarChip works with the following OBD protocols: J1850-41.6, J1850-10.4, ISO9141, KWP2000 and CAN.

Hmmm....