Do I have a code 22???

pure_e · 09-30-2009, 07:54 AM

Hi all, appreciate any help given

Just out of interest I decided to check to see if my ECU was giving any error codes by doing the paper clip in the diag port (thanks kick-fix.com for the instructions

).

My car is 94 Vitara, 5spd, 4x4, 3dr ragtop. The jumper worked perfect and I only tested the "key on" codes (did not start car).

What I'm not sure of is whether I got a 22 first, then a 12 (I can count to 2...

)

Here's the thing... as soon as key is set to ON or IGN the CEL flashes very quickly twice then pause then 2 more flashes but not as quick. Then big pause, and gives code 12 and repeats 12 on and on...

If i was to describe, it would go like this (commas are a pause):
(key on) flashflash,,,,flash,,flash,,,,,,,,,flash,,,,flash, ,flash,,,,,,repeat...

given the first 2 flashes has a much shorter pause than the second 2, I read that code as: first flash because ign is on CEL lights up and second flash meaning 1, longer pause, then next flashes meaning 2 - given a code 12.

Sorry if Im sounding like a cabbage, but i want to know if this is ok or do I have a TPS issue. BTW, This was done out of curiousity and not because i think there is something wrong too.

Bex · 09-30-2009, 11:52 AM

The code will keep repeating itself (giving you the chance to race back from the engine to look at the codes on the dash), so I would say you are getting a 12. Maybe I did mine backwards, but I put the key on first, then did the paperclip thing, then went back to the dashboard, so by the time I got back to the dashboard, it was just repeating codes, and you didn't get the first cel light from when the key turns on.

Bex · 09-30-2009, 11:54 AM

And code 12 is normal. FSM says to put the ignition on (engine off), check that CEL comes on as it should, and THEN jump the terminals. Maybe that's what was confusing....

kick-fix · 09-30-2009, 02:54 PM

key on CEL , should not flash. just come on with clip out.

if you key on with jumper, it will just spool out all codes stored.

never seen one hickup but others have and the Caps in ecu were bad.
marginal it was.

IMO, it will flash 1 time then 2 then repeat if happy.

forever.

you can jumper before, after and even while running and it will just do the expected
show live fails and stored codes.

on this car , if one bad code is stored , you while never get a code 12 just that one code.
if 2 codes are stored it will spool out both and repeat but will not ever put out code 12.
unless, you cycle dome power fuse. (out count to 30- 60 seconds back in)

then key on see 12, now start car if error re-occures, then the code will come back.

obradleyo · 10-01-2009, 12:16 PM

hey bud I know exactly what you mean I went threw the processe and actuall bought a new tps. On mine it does like a test flash frist. every one on here said it doesn't do it but it does. if you keep letting it flash code you will notice it won't do the 22 again. also the frist flash is like a half flash right....

kick-fix · 10-01-2009, 02:34 PM

that is strange.

you say you have fresh 2 main capacitors in ECU?
usually if they've been changed 1 time they are good.
if they Rubycon on the side (black plastic sleeve ) they are no good.

does this anomaly happen not running , just key on?
running the alternator can be a noise generator. and make ECU go nuts.
c103 needs to be fresh and full value.

http://www.kick-fix.com/ECU/ECU-16v-92w.JPG

shackwrrr · 10-02-2009, 01:54 AM

mine does it to when I was getting that 53 code after I had the computer rebuilt it would

**-*-*-*-*--*-*-* then repeat 2 more times

pure_e · 10-02-2009, 03:08 AM

Quote:

Originally Posted by Bex

And code 12 is normal. FSM says to put the ignition on (engine off), check that CEL comes on as it should, and THEN jump the terminals. Maybe that's what was confusing....

I'm going to go with this and just put the first flash down to the fact that the key was switched on when jumper was already in. Logic says the CEL will always illuminate on key on, then i guess the second flash was just the first flash in the code 12 sequence.

However, if you have key on, then did the jumper, you're going to miss the first code sequences (perhaps this is supposed to be a 2 person job?) Anyway, I'm going to do it that order and get the wife to watch the CEL when I jump it and see if its gives a 12 or a 22.

Quote:

Originally Posted by kick-fix

on this car , if one bad code is stored , you while never get a code 12 just that one code.
if 2 codes are stored it will spool out both and repeat but will not ever put out code 12.
unless, you cycle dome power fuse. (out count to 30- 60 seconds back in)

then key on see 12, now start car if error re-occures, then the code will come back.

This is good to know, so in theory, you should only see a repeating 12 right?
therefore what I thought could be a 22 was most likely 12.

I did pull the Tail/Dome fuse, and then switched key on again (not sure if it was for the 30 - 60 secs) and same result. Jumper was left in too so not sure if that could have had an effect. I didnt try at any stage to check when starting/cranking the car over.

If it was TPS, would that be noticable in the drive/idle/fuel consumption. Although I've only had mine a little while and I'm the 4th owner, mine seems pretty good on performance and MPG (until I put 9R15 tyres on)

Also, this forum is awesome - am seriously considering premium membership - especially since the NZD is strong right now

kick-fix · 10-02-2009, 02:08 PM

tell truth i never look at CEL, as it first starts to flash.
i look at the train , in total. ( what and how many codes stored.)

it may in fact flash out , 1/2 a code as it boots. (software issue there ,deep) years?

pull dome ,kills memory wire.and the delay is to discharge large capactors.

just like your PC. huge CAPS in there.
most memories forget below 4v. (normal is 5v) ( i used to test them long ago)

there are situations a full 5min might help. (latch up that is called and takes longer)