Page 1 of 1

OBD-2?

Posted: Fri Dec 01, 2006 3:30 pm
by physh
What is the connection for all the on board diagnostics stuff on a 2002 FZJ105R GXL auto Landcruiser?

Is it OBD-2?

What protocol does it use?

What is the best sort of hardware/software combo to enable me to:
- Read all trouble codes
- Get live data from engine to my laptop (eg temps, revs, A/F ratio etc)
- Log data over a trip
- Clear codes / make changes back to the ECU

I want it to be USB, and be able to connect to multiple vehicles.

Cheers
Nick

Posted: Fri Dec 01, 2006 10:07 pm
by InSanE
yes your cruiser will have an OBD2 connector it because an industry standard a years ago but i cant help you with the other stuff all i know is we have an ultra scan at work and that is great but not suitable to your needs.

Re: OBD-2?

Posted: Sat Dec 02, 2006 8:49 am
by Ruffy
physh wrote:What is the connection for all the on board diagnostics stuff on a 2002 FZJ105R GXL auto Landcruiser?

Is it OBD-2?

What protocol does it use?

What is the best sort of hardware/software combo to enable me to:
- Read all trouble codes
- Get live data from engine to my laptop (eg temps, revs, A/F ratio etc)
- Log data over a trip
- Clear codes / make changes back to the ECU

I want it to be USB, and be able to connect to multiple vehicles.

Cheers
Nick
As far as i am aware there is no legitimate way of installing any software onto your PC to read any OBD II vehicle information. Every manafacturer utilises a different format for this very reason. One of the reasons that aftermarket scanners are so expensive is because the manafacturers of the scan tools either need to develope the programs or purchase rights from the vehicle manufacturers.
If you are savvy enough you may be able to develope somethnig yourself but i doubt you would be able to produce something to be able to do multiple vehicles without having those vehicles and developing a program for each vehicle.
This is done specifically so that people cannot do exactly what you are trying to do.
Cheers.

Re: OBD-2?

Posted: Sat Dec 02, 2006 3:55 pm
by DamTriton
physh wrote:What is the connection for all the on board diagnostics stuff on a 2002 FZJ105R GXL auto Landcruiser?

Is it OBD-2?

What protocol does it use?

What is the best sort of hardware/software combo to enable me to:
- Read all trouble codes all commercial readers and software will do this
- Get live data from engine to my laptop (eg temps, revs, A/F ratio etc) some software will do this. Specialised readers will do this (inbuilt screens)
- Log data over a trip "Black boxes" are available, but not cheap. Most software should do this in the short term (10 mins-60 mins)
- Clear codes most readers, most software make changes back to the ECU no readers, and limited software. Totally dependant on the design of the ECU and usually VERY well protected from tampering via checksums/CRC. May need to lift memory chip off board to reprogram.

I want it to be USB, and be able to connect to multiple vehicles.

Cheers
Nick
Unless you already know what you want to do to the ECU (allow for turbo boost, modify ignition mapping) there is really not much point in tampering with it. You will get nowhere by playing with the fuel management (fuel injection timing BTDC) and everything else is pretty much designed to work in an efficient closed loop, or very inefficient open loop (warm up), and worse limp home modes.

They have already been optimised to their best efficiency and will work well under all but the most extreme modifications with simple substitution of some hardware (injector size, fuel pump GPH capacity, MAF size, etc).

The only real thing you can do is change the ignition mapping to suit our 91/95/98 octane fuel versus the generic 87 octane mapping (ignition retarded) that the vehicles are normally supplied with. This is what Powerchip/Unichip and all the other suppliers do when they "chip" your vehicle. The "free power" comes from effectively advancing the ignition timing (cranking the distributor in the old days) to a point that suits the higher octane fuel, no real magic there. The problem comes when you have to look into the contents of a 128 kB ECU memory chip to work out where the ignition map is actually located.