Threw a code, looking for help
Thread Starter
Intermediate
Joined: Dec 2008
Posts: 34
Likes: 0
Threw a code, looking for help
So my '93 6 speed has been running really well recently (finally). Last night after a short highway cruise, the CEL comes on for a few minutes then turns off. A short while later, it comes back and stays on until I get home 20 minutes later. The entire time the car still ran fine, no major issues. I haven't pulled the codes yet (autozone was closed by the time I got back) but I did notice a loud popping noise from the (factory) exhaust when I would back off the throttle after acceleration, almost like a backfire but not quite the same. I will usually get the some popping sounds from the exhaust under normal conditions, but they got much more frequent and louder after the CEL came on which is why I think they may be related. Manifold gaskets and cats are new. Obviously, I'll know more after I pull the codes tonight but, on a preliminary basis, does that sound like anything anyone has dealt with before? I'm thinking O2 or maybe a MAF issue could be the culprit but I'm not sure. I'll post the codes tonight, but if anyone has initial thoughts, I'd be interested to hear.
Thanks!
Doug
Thanks!
Doug
Le Mans Master
Joined: Mar 2001
Posts: 7,999
Likes: 14
From: Life is just one big track event. Everything before and after is prep and warm-up and cool-down laps
Cruise-In III Veteran
Cruise-In IV Veteran
St. Jude Donor '12
Do a search on how to pull the codes with a paper clip.
Just a guess is something in the EGR system since it comes on at highway speeds.
I've got to fix my vaccum lines or clean my 2 year old EGR valve cause mine comes on now.
In the past I had a knock sensor code that would come on soon after start up and then go off. Last maintenance I put in new knock sensors and have not had that intermittent code again.
Just a guess is something in the EGR system since it comes on at highway speeds.
I've got to fix my vaccum lines or clean my 2 year old EGR valve cause mine comes on now.
In the past I had a knock sensor code that would come on soon after start up and then go off. Last maintenance I put in new knock sensors and have not had that intermittent code again.
Thread Starter
Intermediate
Joined: Dec 2008
Posts: 34
Likes: 0
i had no idea about pulling codes with a paperclip, that's really interesting.
It was throwing code 32 maybe three or 4 months ago, so I had the EGR valve replaced with no CELs since until last night. I guess it could be a vacuum line or maybe the new valve is junk...
It was throwing code 32 maybe three or 4 months ago, so I had the EGR valve replaced with no CELs since until last night. I guess it could be a vacuum line or maybe the new valve is junk...
Thread Starter
Intermediate
Joined: Dec 2008
Posts: 34
Likes: 0
Yeah i hear you, and i'll post what i pull off the scanner (or paperclip) tonight. I just though someone may have had similar problems in the past and could give me an idea of what to expect.
Le Mans Master
Joined: Mar 2001
Posts: 7,999
Likes: 14
From: Life is just one big track event. Everything before and after is prep and warm-up and cool-down laps
Cruise-In III Veteran
Cruise-In IV Veteran
St. Jude Donor '12
i had no idea about pulling codes with a paperclip, that's really interesting.
It was throwing code 32 maybe three or 4 months ago, so I had the EGR valve replaced with no CELs since until last night. I guess it could be a vacuum line or maybe the new valve is junk...
It was throwing code 32 maybe three or 4 months ago, so I had the EGR valve replaced with no CELs since until last night. I guess it could be a vacuum line or maybe the new valve is junk...
I'll be doing that tonight as I get the 92 ready for emissions testing.
Thread Starter
Intermediate
Joined: Dec 2008
Posts: 34
Likes: 0
ok so i pulled H25, H23, H64 and H61 and i have no idea where to find out what those mean lol. did a search for a list, but didn't see anything...
edit: found a list. 25 and 23 are air intake temps high and low. 64 was the O2 and I couldn't find 61 but im guessing thats the other O2
edit: found a list. 25 and 23 are air intake temps high and low. 64 was the O2 and I couldn't find 61 but im guessing thats the other O2
Last edited by Serial Chiller; Aug 17, 2010 at 08:23 PM.
Drifting
Joined: Jun 2010
Posts: 1,853
Likes: 8
From: Westerly RI
Codes 23 and 25 both indicate out-of-range readings in the IAT (Intake Air Temp.) sensor circuit. There are test procedures for both in the FSM but the fact that both codes appeared together could mean that the sensor is at fault. Code 64 is right O2 sensor indicating lean exhaust, which could be resulting from a IAT problem. Code 61 is not in my FSM, but the left O2 codes are 44 and 45. If you have access to a scanner you can test the IAT.
Corvette Stories
The Best of Corvette for Corvette Enthusiasts
Top 10 Most Expensive Corvettes Ever Sold on Bring A Trailer
Brett Foote
10 Things Every Corvette Owner Needs (2026 Edition)
Michael S. Palmer
8 Most "Only Corvette Owners Understand" Quirks and Problems
Pouria Savadkouei
10 Reasons the C6 Z06 is Still A Performance Benchmark After 20 Years
Joe Kucinski
How Much Horsepower Every Corvette Engine "LOST" in 1972
Joe Kucinski
Top 10 DOs and DON'Ts for Protecting Your Convertible Top!
Michael S. Palmer
Top 10 Most Explosive Corvettes Ever Made: Power-to-Weight Ratio Ranked!
Joe Kucinski
150 hp to 1,250 hp: Every Corvette Generation Compared by the Specs That Matter
Joe Kucinski
8 Coolest Corvette Pace Cars (and Replicas) of All Time
Verdad Gallardo
Thread Starter
Intermediate
Joined: Dec 2008
Posts: 34
Likes: 0
Codes 23 and 25 both indicate out-of-range readings in the IAT (Intake Air Temp.) sensor circuit. There are test procedures for both in the FSM but the fact that both codes appeared together could mean that the sensor is at fault. Code 64 is right O2 sensor indicating lean exhaust, which could be resulting from a IAT problem. Code 61 is not in my FSM, but the left O2 codes are 44 and 45. If you have access to a scanner you can test the IAT.
i do have access to a scanner at my buddy's shop so i'll test the sensor and see what happens. so at that point, assuming the sensor is the issue and is replaced, i guess i'll clear the existing codes and see if i get the O2 codes again. could a faulty IAT sensor cause the exhaust popping/backfiring/power loss i'm getting? i would think so right?
Drifting
Joined: Jun 2010
Posts: 1,853
Likes: 8
From: Westerly RI
The IAT could indirectly cause those symptoms by sending erroneous info to the ECM which then makes incorrect adjustments to the air/fuel ratio. This could then cause the O2 sensor to report a lean mixture. It is also possible that the ECM is ailing, but, as usual, don't just throw parts at the problem.
Thread Starter
Intermediate
Joined: Dec 2008
Posts: 34
Likes: 0
the ecm is new (and was a major PITA to get) so i hope thats not the problem...
i'll definitely test the sensor before i put another one in but, worst case, they look pretty cheap to replace. $20 or so.
i'll definitely test the sensor before i put another one in but, worst case, they look pretty cheap to replace. $20 or so.
Thread Starter
Intermediate
Joined: Dec 2008
Posts: 34
Likes: 0
so i had my buddy at the shop run a test with his scanner on the IAT and it turns out it was in fact cooked. I pulled it, threw in another, cleared the codes and no SES lights since. I'm putting some highway miles on it this afternoon so we'll see if it trips anymore codes, but I would imagine that did the trick.
Drifting
Joined: Jun 2010
Posts: 1,853
Likes: 8
From: Westerly RI
so i had my buddy at the shop run a test with his scanner on the IAT and it turns out it was in fact cooked. I pulled it, threw in another, cleared the codes and no SES lights since. I'm putting some highway miles on it this afternoon so we'll see if it trips anymore codes, but I would imagine that did the trick.
Team Owner
Joined: Oct 2000
Posts: 96,443
Likes: 9
From: Fort Knox, KY
Cruise-In IV Veteran
Cruise-In VI Veteran
Cruise-In VII Veteran
Cruise-In VIII Veteran
so i had my buddy at the shop run a test with his scanner on the IAT and it turns out it was in fact cooked. I pulled it, threw in another, cleared the codes and no SES lights since. I'm putting some highway miles on it this afternoon so we'll see if it trips anymore codes, but I would imagine that did the trick.