Notices
86-95 Trucks & 4Runners 2nd/3rd gen pickups, and 1st/2nd gen 4Runners with IFS
Sponsored by:
Sponsored by: DashLynx

im getting a code 12....

Thread Tools
 
Search this Thread
 
Old 11-10-2009, 11:19 PM
  #1  
Registered User
Thread Starter
 
HAWAIIANSTYLE's Avatar
 
Join Date: Jan 2007
Posts: 69
Likes: 0
Received 0 Likes on 0 Posts
im getting a code 12....

(94 4runner v6).. jumpered t1 and e1 and got a code 12 (knock control sensor signal/rpm signal)... could this be a symptom of why i have lack of power and poor mileage. afterall, i've already tried narrowing down my first to do list,.. blew the gaskets earlier this year and had everything rebuilt. spark plugs and wires, dist. cap n rotor, fuel filter, fuel pump, vacuum leaks, compression, timing, injectors, seafoam, cat, o2 sensor,.. all changed. oops, i overlooked changing the knock sensor pigtail when doing the headgaskets. does this mean i have to do the timing all over again after i change it out?...
Old 11-09-2010, 12:57 PM
  #2  
Registered User
 
125rmodel's Avatar
 
Join Date: Feb 2010
Location: Atlanta, GA
Posts: 8
Likes: 0
Received 0 Likes on 0 Posts
I have the same problem with my 93. did you ever get it solved
Old 11-09-2010, 04:42 PM
  #3  
Registered User
 
MudHippy's Avatar
 
Join Date: Jan 2007
Posts: 6,106
Likes: 0
Received 23 Likes on 20 Posts
O.k., the first thing that needs cleared up, before we can get you started on this, is clarification on the true description of the code.

Code 12 is an RPM signal related code. It has nothing to do with the knock sensor.

FSM page EG2-176 from the link below describes the nature of the trouble as being "No G or NE signal is input to the ECM for 2 sec or more after starter turns 4N." Which in laymans terms means that the ignition return signal to the ECM, which it uses to calculate engine rpm, is shorted somewhere between the distributor and the ECM.
http://personal.utulsa.edu/~nathan-b...85diagnosi.pdf

The ECM pin out locations of the G and NE signals, and their respective resistance values(hot and cold), can be found on page EG2-256.
http://personal.utulsa.edu/~nathan-b...e/102engin.pdf

But as is also described on page EG2-176 of the FSM(from the first link provided above)it can also mean there's a short somewhere in the STA(starter signal)circuit between the battery and the ECM. To troubleshoot the STA circuit follow the instructions given on page EG2-193 from the link below. The ECM pin out location and voltage specifications for the STA circuit can also be found on page EG2-255 in the link directly above.
http://personal.utulsa.edu/~nathan-b...86troubles.pdf

If all checks out with those two circuits, then the ECM itself could be faulty.

The entire FSM can be accessed from the link below.
http://personal.utulsa.edu/~nathan-buchanan/93fsm/

Fair warning, I have no clue what would be causing the issue. But I can point you in the right direction, hopefully. Any more help from me on it is by no means guaranteed. I've never heard of anyone having this code come up untill today, let alone have any specific details on how to resolve it. I'll try and do what I can though.

Good luck!

Last edited by MudHippy; 11-09-2010 at 04:44 PM.
Old 11-09-2010, 05:26 PM
  #4  
Registered User
 
125rmodel's Avatar
 
Join Date: Feb 2010
Location: Atlanta, GA
Posts: 8
Likes: 0
Received 0 Likes on 0 Posts
humm good info im going to look at this stuff in the morning
Old 11-10-2010, 07:20 AM
  #5  
Registered User
 
125rmodel's Avatar
 
Join Date: Feb 2010
Location: Atlanta, GA
Posts: 8
Likes: 0
Received 0 Likes on 0 Posts
everything checks out with the wiring and distributor and starter. I also replaced the ignitor, knock sensor and wiring, coil, tune up stuff, and the distributor still same code 12. Also food for thought when i reset the computer it will flash that there is no codes until i try and crank it up then light comes on immediately and it will start and run ok after the third or fourth time trying to start it. but it will never start the first time, like it has to go into a limp home mode to start and run
Old 11-10-2010, 10:30 AM
  #6  
Registered User
 
sb5walker's Avatar
 
Join Date: Jan 2008
Location: Connecticut
Posts: 1,085
Likes: 0
Received 6 Likes on 5 Posts
The G & Ne signals are not "ignition return", they're the rpm signals from the distributor's signal coils. It sounds like you may have already checked the resistance and air gaps of those, but if not, the specs are here:
http://personal.utulsa.edu/~nathan-b...12onvehicl.pdf

(The "ignition return" signal is the IGF, which goes from the igniter back to the ecu. It provides confirmation to the ecu of the spark. If there is no IGF signal, the ecu will stop firing the injectors. But you would get a code 14 if the ecu were complaining about that.) On 3vze vehicles, the signal coils connect directly to the ecu as Mudhippy mentioned, but on 22re trucks there's only one signal coil and it connects to the igniter, and from there the signal is passed to the ecu.)

If the signal coil resistances and air gaps are okay, check the wiring between the distrib and ecu, and the ecu grounds. For the grounds, verify almost no ohms between ecu term E1 and a good chassis ground, between E01/E02 and the engine block & head, and between chassis and neg batt post and engine and neg batt post. I think the ignition system uses the E1 ground, and it happens that there's an E1 terminal in the check connector, so very easy to check ohms between that and the neg batt post. If more than, say, about 3 ohms, I would clean up the ecu terminal E1 ground point (which is supposed to be on the driver side post) and also clean up the battery cables and posts.

Last edited by sb5walker; 11-10-2010 at 10:34 AM.
Old 11-10-2010, 12:49 PM
  #7  
Registered User
 
125rmodel's Avatar
 
Join Date: Feb 2010
Location: Atlanta, GA
Posts: 8
Likes: 0
Received 0 Likes on 0 Posts
I have replaced the wires between the dist and the ecu since they were in that shielding jacket and to be positive there was no problems with it even though they ohmed out good i replaced that part of the harness with some new stuff i got from aircraft spruce and specialty. I went throught the FSM basic voltage checks and will go back and recheck the connections and such you mentioned and get back with you. Everything seems to check out good so I am starting to think I may actually have a bad ecu, but thats not the normal case so an ecu will def be the last ditch effort.
Old 11-10-2010, 02:39 PM
  #8  
Registered User
 
MudHippy's Avatar
 
Join Date: Jan 2007
Posts: 6,106
Likes: 0
Received 23 Likes on 20 Posts
Originally Posted by sb5walker
The G & Ne signals are not "ignition return", they're the rpm signals from the distributor's signal coils. It sounds like you may have already checked the resistance and air gaps of those, but if not, the specs are here:
http://personal.utulsa.edu/~nathan-b...12onvehicl.pdf

(The "ignition return" signal is the IGF, which goes from the igniter back to the ecu. It provides confirmation to the ecu of the spark. If there is no IGF signal, the ecu will stop firing the injectors. But you would get a code 14 if the ecu were complaining about that.) On 3vze vehicles, the signal coils connect directly to the ecu as Mudhippy mentioned, but on 22re trucks there's only one signal coil and it connects to the igniter, and from there the signal is passed to the ecu.)
O.k., yeah that sounds right. Sorry for the confusion. I'm still trying to wrap my head around it. But that makes a bit more sense, I guess. When I said I didn't have a clue as to what would be causing the issue, that was no understatement.

I gave it my best shot though. Kinda figured it couldn't hurt too much to. The poor OP never even got a reply at all. I was worried nobody was gonna bother even trying to help this guy either.

Thanks for jumping on board to lend a helping hand, and straightening out the misunderstanding!
Old 11-10-2010, 03:48 PM
  #9  
Registered User
 
125rmodel's Avatar
 
Join Date: Feb 2010
Location: Atlanta, GA
Posts: 8
Likes: 0
Received 0 Likes on 0 Posts
thanks for the feedback anyways i am stumped too ha ha but i think i will try an ecu they run about $250, I have made worse investments
Old 11-10-2010, 04:10 PM
  #10  
Registered User
 
sb5walker's Avatar
 
Join Date: Jan 2008
Location: Connecticut
Posts: 1,085
Likes: 0
Received 6 Likes on 5 Posts
Originally Posted by 125rmodel
thanks for the feedback anyways i am stumped too ha ha but i think i will try an ecu they run about $250, I have made worse investments
If not the wiring, grounds or ecu, it may be the distributor. My veezy had a persistent pinging problem for many years; checked everything I could think of including the signal coils and could never solve the problem. Then a few years ago I replaced the distributor because the bearings were going bad & squealed terribly when very cold. With the new distrib, the pinging issue completely disappeared. Probably the G or Ne signals were not being generated properly, even tho the resistance of the coils checked out. My best guess is that the bad bearings caused the shaft to move around enough to mess up the rpm signals. You might try wiggling the shaft side-to-side - there should be no movement.

MudHippy, thanks for the - glad to help when I can.
Old 11-10-2010, 04:18 PM
  #11  
Registered User
 
125rmodel's Avatar
 
Join Date: Feb 2010
Location: Atlanta, GA
Posts: 8
Likes: 0
Received 0 Likes on 0 Posts
my old dist checked out fine and i bought a reman unit and it did not make a difference :-( it passed the FSM checks and I did it anyways with no luck
Old 11-10-2010, 04:29 PM
  #12  
Registered User
 
sb5walker's Avatar
 
Join Date: Jan 2008
Location: Connecticut
Posts: 1,085
Likes: 0
Received 6 Likes on 5 Posts
Originally Posted by 125rmodel
my old dist checked out fine and i bought a reman unit and it did not make a difference :-( it passed the FSM checks and I did it anyways with no luck
Oh well, just a thought. Good luck with it.
Old 03-18-2011, 03:37 PM
  #13  
Registered User
 
93YotaGuy's Avatar
 
Join Date: Jul 2009
Location: Denver, Colorado
Posts: 319
Likes: 0
Received 0 Likes on 0 Posts
Any luck figuring this out? I'm having the same problem with my truck and am stumped.
Old 03-19-2011, 02:57 PM
  #14  
Registered User
 
125rmodel's Avatar
 
Join Date: Feb 2010
Location: Atlanta, GA
Posts: 8
Likes: 0
Received 0 Likes on 0 Posts
I finally figured out that the distributor connector had been replaced before I bought it and the dummy that replaced it put the wires back in the connector in the wrong order. Also im not sure if I mentioned that I bought my truck running like that. 93yotaguy what have you tried on yours?
Old 03-19-2011, 04:44 PM
  #15  
Registered User
 
93YotaGuy's Avatar
 
Join Date: Jul 2009
Location: Denver, Colorado
Posts: 319
Likes: 0
Received 0 Likes on 0 Posts
https://www.yotatech.com/forums/f199/back-grave-231390/
Old 03-26-2011, 12:52 PM
  #16  
Registered User
 
93YotaGuy's Avatar
 
Join Date: Jul 2009
Location: Denver, Colorado
Posts: 319
Likes: 0
Received 0 Likes on 0 Posts
Well my code 12 turned into a code 13. I ended up finding that the wires that went from the igniter to the alternator had burned up somehow. I replaced the harness and the code went away.
Old 08-31-2011, 05:48 PM
  #17  
Registered User
 
ToyotaViejo's Avatar
 
Join Date: Jun 2011
Posts: 97
Likes: 0
Received 1 Like on 1 Post
Hate to be a pain, but I'm wondering if you might snap a pic of the ignitor and wires you fiddled with to fix the problem?
Old 09-01-2011, 09:50 AM
  #18  
Registered User
 
93YotaGuy's Avatar
 
Join Date: Jul 2009
Location: Denver, Colorado
Posts: 319
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by ToyotaViejo
Hate to be a pain, but I'm wondering if you might snap a pic of the ignitor and wires you fiddled with to fix the problem?
Maybe you should look at my above post and click the link that explains it all
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
moparbay
86-95 Trucks & 4Runners
5
10-06-2015 09:24 AM
bradahman
86-95 Trucks & 4Runners
8
10-01-2015 09:24 AM
charlie_fong
General Vehicle Related Topics (Non Year Related)
0
09-27-2015 10:06 PM
Odin
86-95 Trucks & 4Runners
3
09-26-2015 06:56 PM
Draven023
Newbie Tech Section
3
09-26-2015 12:41 PM



Quick Reply: im getting a code 12....



All times are GMT -8. The time now is 01:37 AM.