rough idle/dying after warm, runs good cold. have code 24 31 42 43 and 52

TurboTarga

TurboTarga

New Member
Sep 12, 2012
16
0
0
Tumwater, WA
okay so i've done quite a bit of research but figured i would ask just to be safe since a lot of the threads i looked at just kinda died and didn't give too clear answers, or many possible issues...

i drove my car approx. 150 miles, by the time i got to where i was going whenever i put her in neutral or let off the gas, she died. started right back up, but only stayed running if i had my foot in it. let her cool down, started her up again, and the idle was shaky at about 500. tried again in the morning after being completely cold, idle went right back up between 650 and 800 and sounded fine. i did hear a little "put put put" sound on the freeway when i barely had my foot on the gas.

engine has no major mods, most everything is stock besides head work, MHG, studs, clutch, bov...
engine was also just recently put in (2 weeks ago)
throwing
code 24 (air intake temp)
code 31 (MAF sensor)
code 42 (speed sensor)
code 43 (starter/ignition electronics)
code 52 (knock sensor)

my research has led me to believe i have a bad MAF sensor, but why would it suddenly act up after working fine for nearly 2 weeks?? i also believe this is for the codes 24 and 31 being thrown
my speedometer does not work in my current dash, so im swapping that out, to hopefully fix the code 42.
i don't know anything about the code 43, but it always starts up just fine, never had issues
i also don't know how to go about the knock sensor to clear that code..

my main concern is why it's running so bad and wanting to die.. i think its the MAF sensor but not completely certain

sorry for the long post, but just wanted to let you guys know everything that i do, that i could think of anyway..
just wanna be better safe then sorry before i go throwing money at something that's not broken...

thanks in advance guys
 
bad88mk3

bad88mk3

Banned
Apr 14, 2013
92
0
0
Somewhere in florida
What i would do is start looking in the tsrm for diagnostic procedures since you have so many codes and its better to make sure something is bad before you replace it cause it can be costly otherwise and code 52 is more than likely the knock sensor wiring there is a thread on here on rewiring them.The search button is your friend and here is links to the tsrm have a multimeter handy cause you'll need it. www.cygnusx1.net/Supra/Library/TSRM/MK3/ www.turboninjas.com/mk3supra/
 
T

tweedermk3

New Member
May 12, 2013
7
0
0
arlington,texas
Knock sensor code could be caused by the rough idle and missing from the hesitation stalling. I'd test the sensor before replacing or rewiring. I ran into this on my supra and fixed the maf code the Iat code and the knock code allby replacing a bad maf
 
T

tweedermk3

New Member
May 12, 2013
7
0
0
arlington,texas
I knock code can be cause by anything that vibrates the block enough to be outside the sensors normal operating range I can cause a knock code with a ratchet on the side of the block on a perfect running car
 
T

tweedermk3

New Member
May 12, 2013
7
0
0
arlington,texas
Us bickering isn't helping the op at all so I'm gonna leave it alone at u really need to research what and how the knock sensor is and works. To the op: I personally remedied mine by only replacing my maf
 
jetjock

jetjock

creepy-ass cracka
Jul 11, 2005
9,439
0
0
Redacted per Title 18 USC Section 798
Even though I'm intimately familiar with how the knock control system and its diagnostics work bickering was never my intention. I corrected your post for the benefit of other members. That includes those whose ego gets in the way of them learning.
 
D

din904

New Member
Oct 25, 2010
76
0
0
Jacksonvile,FL.
whats the point of having a knock sensor that just gives a code every time it knocks from my understanding your knock code is picking up some type of malfunction with the sensor. always check the basics fuel,spark,compression before you start chasing problems with your electronics.
 
B

BryanDyer

New Member
Jun 13, 2012
654
0
0
Georgia
the point of the knock sensor isn't to pop a code up everytime you have knock
it's like a little speaker that picks up vibrations and based on the vibrations it recieves it retards/advances the timing to reduce the knock to where it is supposed to be
code 52 does not mean Knock it means there is a wiring issue just like 99% of the supra owners get
all it takes is a simple rewire from the clip to the ecu
so all it is a wiring issue man I myself have repaired mine
 
B

BryanDyer

New Member
Jun 13, 2012
654
0
0
Georgia
tweedermk3;1938376 said:
Knock sensor code could be caused by the rough idle and missing from the hesitation stalling. I'd test the sensor before replacing or rewiring. I ran into this on my supra and fixed the maf code the Iat code and the knock code allby replacing a bad maf
Click to expand...

you my friend are wrong and you obviously don't know what code 52 means on the supras..as jetjock said it does not mean knock and it doesn't
 
T

tweedermk3

New Member
May 12, 2013
7
0
0
arlington,texas
I understand what the sensor does how it works and what problems our cars are commonly prone to I wasn't denying that it could be that issue I was simply stating that a knock sensor doesn't just code when the sensor is bad it will code for several things not just the wiring or the sensor failure.
 
T

tweedermk3

New Member
May 12, 2013
7
0
0
arlington,texas
Then I ask you to educate me either of u how was replacing my maf the only thing I had to fix to do away with my codes.. All 3 of them 24 31 and 52? Not being a contrary or anything I'd honestly like to know. I've built 3 of these cars and haven't ever not figured out an issue and if I did by accident I'd like to know how
 
You must log in or register to reply here.
Top Bottom