So, this morning when I got up for work, and started up my car like i do every morning, everything was fine, left work about 45 minutes later to visit a job site about 4 blocks away, everything was fine, then about 3 hours later, i started my car, and it struggled. Thats when the check engine light came on, so I thought maybe it could be a glitch, so I turned off the engine and turned it back on, it turned over no problem, but the check engine light still on. Sigh, I don't know what could be wrong, the car seems to run fine, and everything's quiet. It's at 64.8k miles, 2004, 6MT. Has anyone else had a check engine light before the 100k mark?

 

if out of warranty, take it to autozone and have them read the code for free.

 

I have--but it went away soon after that.
Then it came on again after I installed my AEM CAI and P2R TB Spacer/Gasket---but that went away too.
Unfortunetely I don't really know what could be wrong with your vehicle as to my TL has almost 99,000KMs[not miles]. Try driving a bit see what happens--or visit your dealership.
Did you by chance tighten the gas cap too much? Or not even close it at all?

 

Hmm, alright, thanks for your input csmeance and o4Komodo, kind of a bummer to just start my car up and see the light on, makes me sad I'll get it looked at if it doesnt go away after a couple days.

 

You may want to consider this OBD II scanner. Amazon has them for $46 (w/ free shipping). You can get the error code and even reset it. Of course, make sure you research the code before deciding not to take it to the shop. It will pay for itself if it saves you one trip to the shop. This one is pretty much the cheapest, simplest scanner out there, but easily good enough for home use.

Interestingly enough, I bought mine two weeks ago because my wife's car had the check engine light on. When the scanner arrived in the mail, the light went off on its own (before I had a chance to use the scanner). But, I'm glad I now have it around for the next time I see the light.

Actron PocketScan at Amazon

 

I thought codes were stored, even if it does away, plug it in and see if you can read anything

 

CRAP! I think you're right about that. Since the light went off, I kind of just put the scanner down. I knew I needed to use it soon just to make sure it is not broken (within the return period), but I forgot the code should still be in there.

You 'da man! Thanks aznboi!

 

Hmm so the scanner reads a code off and you just research the code? or how does it work?

 

Yeah - this cheap one will only read the codes out for you. You have to write them down, and then look in the book they give you with the scanner (or use the included CD in your PC). The instruction book that comes with the scanner tells you exactly what to do - it seems really simple (although I haven't done it yet). I am actually on travel for work right now so I won't be able to try it out until this weekend. You can also clear the check engine light, but it will just come right back if you have a real problem.

The more expensive scanners have memory and the code descriptions stored so you can immediately understand what a particular code means and you don't have to write them down (you can cycle back and forth after you disconnect from the vehicle since the codes are stored in the memory). This scanner doesn't do any of that, but if you're not in a shop and only use it infrequently, it's perfect.

 

Mine came on due to a faulty sensor (replaced under warranty)

Also if you dont tighten your gas cap correctly, it will cause the light to come one. And takes 3 cold start cycles to turn off.

Acura Tech says "Driving around for a while with the check engine light isn't harmful since it automatically makes the car function on a safe base map"

 

I had a check engine light at 30k it was a faulty O2 sensor, I drove it for a week trying to see if it goes away... the car runs ok w/o problem except that check engine light. Dealer replace it... then the same thing happen again at 42k.

 

yea the codes are stored.

 

So I finally used my scanner this weekend and my wife's car gave me no error codes. I think she drove the car too many miles after the MIL light went off, and the car reset the codes. So, I have no idea why the light went on in the first place. But, if it comes on again, I know I can quickly figure out why.

I had another strange problem though. I connected the scanner to the port no problem. Then when I tried to remove it, the damn plug wouldn't come out. I did this last night so I had a biitch of a time figuring out why - had to get the flashlight and all. I finally realized it was the little notch on the plug that was mated perfectly to a little tab on the port. The only problem is, neither the notch nor the plug has a way to depress it. I ended up getting a screwdriver, wedged it in there and finally released the plug from the OBD port (total pain in the ass in the dark). After I got it off, I took a good look at everything and it just doesn't make sense to me. Why would the plug and connector lock together without a clean way to remove it? What am I missing? It just makes no sense to have to wedge a tiny screwdriver in the notch/tab to pull the scanner off. I hope this makes sense. If you have used the PocketScan before, you probably know what I'm talking about.

 

my dealer told me it was oxygeniated gas so i switched from SHELL to EXXON dealers advice" and honestly i havnt had a check engine light since n its been almost 4 months since i visited the dealer