Alright so here's the deal. I was driving up to work yesterday afternoon after driving about 20 miles. About 2 miles from work, I notice that the check engine light has come on. I pull into work and shut my 4runner off. I immediatly go to start it, and it won't start. The starter will no even engage, and I can just hear that slight ticking sound from the right engine compartment. I let it sit for a couple of minutes, and it starts right up, even though the check engine light is still on. I V6drove it the 20miles home, and let it sit overnight. I checked all my fluids, fuses, etc... etc... looked for any loose wires etc. The batteries blue light glow appropriatly, even though I probably should have put a volt meter on it. I unplugged the batter thismorning for a minute to reset the computer, and wallah, the check engine light had kicked off. I drove the car about 2 miles, and it didn't come back on. The only thing that came to my mind when the car wouldn't turn over iniitially was maybe the fact that the battery was dieing, but that wouldn't explain why it started later? My second thought is maybe one of the battery connections going somewhere might also be loose as well, but would that explain the check engine light coming on while I was driving. Any thoughts would be appreciated.


By the way its a 2000 SR5 V6 5spd. I've already bought another car to replace it with, and I will be selling it in another 3 weeks. Leather sport package, towing package etc. etc. if anyone was interested.

 

Next time try this before you reset the computer to see what the problem is.

http://www.off-road.com/toyota/tech/codes/

 

Jumping the connector like it says in that link is fine for an OBD-I vehicle, but I don't think it can be done on OBD-II (1996-up) or OBD-III (newest). In fact, I heard that this can fry the computer. OBD-II and higher vehicles need to have a code reader to get codes.

There's a thread going on ODW right now about this, sorry I don't have the direct link to it.