[tonyevans]

I just need to check that I have got this right - Most likely not

Turn the ign on and the light comes on.
Start engine and light goes off if all is well.
If problem is sensed light flashes a code sequence such as 4 flashes delay 1 flash repeated = code 41.

If the engine does not start because there is a problem it just stays on and does nothing useful

Is this correct? If so what bloody use is it when you have a engine won't start problem like I do?

[atari4x4]

you need to bridge the diagnostic plug to retrieve the code, it won't do it with the just the ignition on, i'm not 100% sure where the plug is located on the G16b, but on mine it's near the air filter in the engine bay.

1/2 way down this page i have attached a word document on how to pull the codes from a j20a vitara. viewtopic.php?f=5&t=6451&hilit=j20a+error+codes

if you disconnect the battery it will clear the codes.

[tonyevans]

OK - Downloaded and read that - All/any codes I had will now be gone so - When I put the battery back in and try to start it again will it re-write any codes if there are any found in the pre-flight test?

On that list I guess the PD numbers will only show if you have the plugin tool thingy?

[atari4x4]

as far as i know there is no "pre-flight test"... usually it needs to have been running for it to log the codes.

[tonyevans]

atari4x4 wrote:

as far as i know there is no "pre-flight test"... usually it needs to have been running for it to log the codes.

The manual suggests there is one and there is a noticeable delay while it tests and turns the power mode and OD lights on/off etc. So I thought the computer was checking things

[atari4x4]

ahh yeah that sounds about right.

[tonyevans]

I guess the best way to find out is put the battery in (when charged) turn it over a bit and then check the codes - If any - with the jumper wire................................ If I can find the plug - I think it is near the battery, I seem to remember seeing a plug with a cover on it there abouts.

[fordem]

The ECU will detect any failed sensors within seconds after the ignition is switched on, and many of them without cranking, starting or running - stuff like temp & airflow are checked for over or under voltage conditions which would indicate short or open circuits, as well as values that are improbable. Other sensors - cam position, crank position and so on, need the engine to be cranked before it will sense - yet others like the vehicle speed sensor, need it to be driven, before it will detect a failure

Rhinoman's web pages are about the best source of reliable information on how this stuff works.

Put the battery in & put the jumper in, you get a 12 flash (to say the ECU has not detected any failures), if there are any codes detected, the light will flash them, next crank the engine with the jumper in place - some ignition related failures will only show if you do it this way.

Last but not least, you can, under certain circumstances, have a failed ECU - injector drivers - or injector wiring - and you'll never get a start or an error code, the only way to pick that up is with a NOID light.

[tonyevans]

Thank you for that information - Where are the Rhinoman's web pages?

[JrZook]

http://www.rhinopower.org/diag/cel.html