I have a 1996 Honda Accord 2.2L VTEC engine M/T with just a bit above 200,000 KMs. This is a Philippines-spec Honda Accord, so no OBD-II, unlike the US variant. Which I wish it had, this will be much easier, lol.
Anyway, the car runs fairly well. But recently I noticed the Check Engine Light comes on during longer trips, usually on highway cruising speeds. The Check Engine Light would turn off, as soon as I shut the engine down and start it up again. It doesn't stay on. I could literarily turn off the engine on the next red light, and start it up again no problem, and the CEL would go away. (I know it probably isn't wise to do that until I got to wherever I'm going. What would I do if it didn't start right? Just did that test one time)
On shorter trips like grocery runs though, the CEL doesn't light up. When it does happen though, I don't notice, feel, nor hear, anything off.
I know of the trick on older Honda's, where you would short one of the OBD1 connectors. Then the check engine light would flash on a certain way telling you the code.
How To Read Honda/Acura OBD1 Trouble Codes - YouTube here's what I'm talking about.
My question is, since the check engine light disappears when the car is turned off, when I turn it ON to hopefully capture the code (by this time the CEL would be "cleared"), would it actually tell me anything? Does the Check Engine light needs to stay ON for OBD1 to give me something useful? I guess my concern is it wont give me the code, or all the codes, that points to the problem triggering the CEL, unless the CEL is persistent.
I have a newer car, and i know OBD-II can get you past tripped codes, but i'm not so sure for OBD-1.
It's probably just from it being old, but I cant help but get worried it has something is failing that will leave me stranded some time in the future {black}:pray:
Well anything I can say is when that light is on either go to a mechanic that has an OBdone scan tool or learn how to read the codes by using the paper clip Google it you see there's tons of videos showing you how to do it
Thanks Scotty! When I do the paperclip method, all I get is code 17. Which from my own research, is a broken Vehicle Speed Sensor. This I already know though, because the speedo on my dash is not working, for some time now. I just didn’t think the speed sensor would trip the engine light On while already driving.
I have a replacement speed sensor coming in, and I’ll see how it goes.