I had to pull the battery over the weekend to do some rewiring work. 1997 4Runner SR5

Went to get my state inspection done this morning and failed as OBDII computer read "not ready".

Anyone know how much time, or how many miles, I need to drive for all sensors to reset. Garage said a "couple days", but I don't feel like dropping $25 for a second failure.

Thanks
Errol

 

That happened to me and I had to drive it for like 180 miles. It's not about the miles but about the cylces. Acceleration/decceleration, cold starts etc. Do you have a ODBII code puller with the I/M monitor?

 

What vehicle is this in? Usually a drive cycle consists of 3 0-65mph trips and variable driving conditions. Stop and go and WOT acceleration. I don't know the exact procedure but I've always used a part city, part highway route for about 20 Minutes. Try asking MTL4Runner or Midiwall.

 

check OBDII terminals, a wire might not be grounded. another member here had a similar problem, but a handheld code reader was able to read it and states machine wasnt.

 

Your OBDII is working normal. When you disconnect the battery for a period of time it loses it's monitoring data. http://www.aa1car.com/obd2help/ should help out a bit. Just drive it. Alot. If you have a friend with a OBDII scanner he can run the monitor a see if all the systems are "ready". you can't have any incompletes.

 

Edited original post to add vehicle info: 97 4Runner SR5.

I don't own a OBDII code reader, but have used the one at Autozone. Guy there claims the reader they have will not show if all sensors are ready.

Thanks for posts to date.

Errol

 

Yeah some readers don't have that option in it. Thats sucks cause you won't know when your car is "ready".

 

Yes, the disconnection of the battery will fully reset your ECU and any stored codes it might have had. Yep, also as mentioned, 3 "trips" (usually 25-30 minutes min, varied driving conditions) are usually enough to ready the system for a state inspection. Do your best to vary your driving conditions between highway and stoplight driving when out and that should guarantee it is ready when you arrive at your inspection station for a retest. Without having an advanced OBD reader it is impossible for you to know exactly when your vehicle will be ready but 3-4 trips is the norm.

 

Keep in mind that some sensors have longer drive cycles than others. Here's a document that details the drivecycles for each monitor. Some of them require multiple trip detection and some seem to require everything but the driver standing on one foot and rubbing his belly.

http://www.watrd.com/work/TSB_EG003-02_(revised).pdf

When I do full reset on my rig, it generally takes 3-5 days of regular driving to get all the monitors reset, if I don't set out to specifically conduct a particular drive cycle. Keep in mind that some of the drive cycles require an overnight cool down, so if you don't get all the conditions met the first time, you are out of luck until the next day.

...and yes, some meters only read codes, not the readiness of the individual systems.

 

Will the BR3 from obdiagnostics.com provide this information?

 

That domain doesn't appear to have anything to do with code readers, so I can't say.

 

Sorry, it's www.obddiagnostics.com

 

I don't see anything on that page that indicates that package can read or display readiness indicators. Not to mention that it's not CAN compatible.

That would not be my first choice of systems to purchase.

 

WATRD,
Thanks for the TSB. Very helpful.

Errol

 

No problem. That's what we are here for