Check engine light won't register
#1
Registered User
Thread Starter
Join Date: Sep 2014
Location: Dover AFB
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
Check engine light won't register
The car is a 2005 with an AEM CAI and a berk headerback. About a day or two after the exhaust install/spark plug change/oil change, I got the CEL. Went to AutoZone, but they had no luck reading the code.
Any ideas?
Edit: Car seems to drive fine. VTEC engages. Gas mileage seems on par. My other car is a big turbo STi, so it's hard to say if the s2k is down on power or not since it always feels that way in a straight line compared to the other car.
Any ideas?
Edit: Car seems to drive fine. VTEC engages. Gas mileage seems on par. My other car is a big turbo STi, so it's hard to say if the s2k is down on power or not since it always feels that way in a straight line compared to the other car.
#2
I would reset the battery first . See if the cel reappears. Since u did ur exhaust I'm wondering if the o2 sensor maybe got damaged . U said u did a headerback? As in u removed the cat? Or did u mean a Catback exhaust ? If ur cat was removed there's ur cel right there . If the cel comes back u gotta get it read
#3
Registered User
Thread Starter
Join Date: Sep 2014
Location: Dover AFB
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
I'll reset the battery and go from there. o2 sensor is a likely culprit. It's a Berk headerback(catless) that has a "built in CEL fix" and I didn't get a CEL on my last S2000.(same exhaust)
Thanks for the advice.
Thanks for the advice.
#5
Registered User
Thread Starter
Join Date: Sep 2014
Location: Dover AFB
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
Okie doke. I'll look more into it on my days off. The part that confuses me is the fact that the CEL wouldn't register on AutoZone's code reader. Not sure why that would happen.
#6
Registered User
Join Date: Mar 2007
Location: KAIZENSPEED, WA
Posts: 270
Likes: 0
Received 0 Likes
on
0 Posts
Would their scanner not power up or just not connect to the ecu?
If it's the first one you may have no power or ground at the OBDII port.
If it's the second one...possibly a JDM ecu?
If it's the first one you may have no power or ground at the OBDII port.
If it's the second one...possibly a JDM ecu?
#7
Registered User
Thread Starter
Join Date: Sep 2014
Location: Dover AFB
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
I forget the actual message the scanner produced, but it was along the lines of "cannot read". The guy tried multiple times. I'm really not sure what it could be, as I've never had an issue like this before.
Thread
Thread Starter
Forum
Replies
Last Post