Will injectors from a 7mge fit in a 7mgte?

cfurlan

New Member
Nov 2, 2010
19
0
0
Indiana
I wanted to snatch some extra injectors from the local junk yard for my car and all they have are 7mge's, so will those also work in a 7mgte? Thanks
 

cfurlan

New Member
Nov 2, 2010
19
0
0
Indiana
Well then does anyone know how to test the injectors while the car is running. Here's the symptoms, I rebuilt the engine due to overheating it. It ruined the main and rod bearings so I replaced those along with a new head gasket. When it overheated, it started running really rough with a miss and initially dieing if not given a little throttle. I put it all back together and also installed new ngk spark plugs. Now it starts but misses really bad. It idles around 350-400 rpm's and eventually dies if not given throttle. Spark plug wires seem to be good still, so I'm thinking its the injectors but I don't know. Any help would be great.
 

cfurlan

New Member
Nov 2, 2010
19
0
0
Indiana
Also would like to add that it's throwing code 52. I reset it once and it popped back up one I restarted the car.
 

shaeff

Kurt is FTMFW x2!!!!
Staff member
Super Moderator
Mar 30, 2005
10,589
10
38
Around
The code 52 has nothing to do with your low idle. It will, however, retard the timing in an effort to prevent detonation. The side effect of retarded timing is running rich(er).

Whenever I'm working on a motor, I will first fix any error codes that are stored, clear the ECU memory, and start with a clean slate. Fix that code 52, double check the mechanical timing (cam/crank), and recheck the ignition timing. We'll go from there.
 

cfurlan

New Member
Nov 2, 2010
19
0
0
Indiana
With the car off the timing is set at 0. With a timing light and the car on running about 700 rpm's, it's at about 10 btdc. When I got the car I noticed that the po already did the rewire for the knock sensors so I'm thinking its just running so bad that it's triggering the sensor. I cleared the codes two times in a row with no change to the way the engine ran and within ten seconds the code was back on with the wire still in the diag box. Thanks
 

shaeff

Kurt is FTMFW x2!!!!
Staff member
Super Moderator
Mar 30, 2005
10,589
10
38
Around
cfurlan;1636222 said:
With the car off the timing is set at 0. With a timing light and the car on running about 700 rpm's, it's at about 10 btdc. When I got the car I noticed that the po already did the rewire for the knock sensors so I'm thinking its just running so bad that it's triggering the sensor. I cleared the codes two times in a row with no change to the way the engine ran and within ten seconds the code was back on with the wire still in the diag box. Thanks

The car running bad isn't causing your code 52. Code 52 means there's a short in your wiring, have bad knock sensor(s), or the ECU is fried. Chances are it's the wiring. Easy way to check is to pull the ECU connector where the KS wires run into, grab a DVOM and click it on continuity check. Touch one probe to a knock sensor pin in the ECU connector, and one to ground. If you get a beep (continuity), you have a bad wire. Do that for both.

Sometimes it won't show up if it's an intermittent short, but that's a good place to start. When the knock sensor(s) operate, it's pretty much invisible. You can't really tell they're working. A poorly running engine won't result in code 52, though.
 

cfurlan

New Member
Nov 2, 2010
19
0
0
Indiana
Well if the knock sensor isn't causing it to run like crap, then that's the least of my worries. Also notice today my new battery died so I jumped the car. It ran for 20 min and then turned it off and the battery was still dead. I must have hooked the alternator up wrong so I'll take a look at it. But I do not think that would cause it to misfire and not idle. Thanks for the help
 

cfurlan

New Member
Nov 2, 2010
19
0
0
Indiana
Well I checked it with the engine off and the cams in line and crankshaft at 0. Then I ran it with a timing light and it was at 10. Thanks
 

cfurlan

New Member
Nov 2, 2010
19
0
0
Indiana
Yeah I did. I know the timing is correct, so I don't know what else to look at. Whatever it was, it was caused when it overheated and rebuilding it didn't fix that problem. Thanks