I have about 1400 miles on my TL. The other day, I decided to get on it and hit the gas hard (quick full throttle). About 2 seconds later, the check engine light began flashing and continued for about 20 seconds even after I let off the gas. Any idea why? Anyone else ever experience this ?

 

Try searching the forum on "check engine light". Quite a few posts on this. If you have an earlier build, it could be a software issue, or an O2 sensor. For me personally, it was the O2 sensor.

 

From the fuel cap to the sensors, there could be dozens of reasons out there. Please have an appoinetment with your dealer, they should be able to tell you the answer...

 

they will hook up the OBDII reader to get the codes. If they get something like just a "misfire" ask them to test drive it with the portable OBDII reader still hooked up, then have them floor it out of a light or from a stop, then they'll capture the code as it occurs. that was the only way they could find mine when I first got it.

 

I've learned this from you a long time ago... this could help those whose dealers say "they can't replicate the issue..."

 

rets: ee-ZACTLY. And all the shops have them.

But honestly, and I'll credit the shop on this one (did I really just say that) They couldn't duplicate my initial MIL problem. I gave them permission to take the thing out and just beat the snot out of it for a minute from a dead stop, that's when the MIL flashes. They promptly did and the light promptly came on and they captured the correct error (crank position sensor malfunction).

We're about to buy one for the house since me and the roomie both work on our cars. www.autoxray.com I think it was.. we're getting the EZ-Scan 5000.. go to the site, english, products, scanners, EZScan 5000.

It prints not just the OBD code #, but the description as well. There are cheaper ones on the site that do just the code #, but then ya gotta go reference what the heck it means. We have a 89 Iroc-Z, 95 Dodge Ram V10, my 98 Accord, and my 04 TL that we can use it on.

 

Mine was a software issue. It would radomly come on and go off. The dealer downloaded a new software update and the problem went away. Acura told the dealer that the original software was too slow and was picking up an erroneous mis-fire code. Almost always happened on start-up.

 

I just had this problem. Frist they updated the software. It did not fix the problem. Then they replace the crank position sensor malfunction. No problems since then, but it did take them 3 times to get it right.

 

Does it read earlier OBD's as well becuase as far as I know, the 89 camaro should not have OBD II in it, unless there was an engine swap.

 

tlguy99: yes.. the EZScan5000 goes all the way back to OBDI and the other computers back to 86 or something, but we did check and it covers GM in 1989, hence why we were happy to be looking at it.

OBDII started in 1996 if I recall, but there were earlier hookups before it was standardized. And it comes with all the necessary cables. It's a pretty thorough unit... heh heh.. he said unit..