one92rs
09-11-2005, 08:33 AM
It's time to explain the OBDII drive cycle. This is an important topic, once we demystify the drive cycle, you'll understand why the check engine light doesn't necessarily turn on immediately when there's a fault, or turn back off immediately once the problem is repaired.
The drive cycle is the sequence of events that must happen for the various system test programs to run on your car's computer. The drive cycle involves a cold start, and a certain amount of driving time at a variety of different loads. More details on those cycles later.
When is the drive cycle important?
First, to understand why the check engine light takes a while to come on. Not only must the appropriate test monitor run, in many cases, it must run twice, detecting the failure each time. If the test runs successfully two more times, it can turn the light back off.
Second, remember from a few emails ago that these system monitors must be complete to pass OBDII based emissions testing (early model years often allow a couple exceptions). If you ever get sent home from an emissions test and told to come back after some driving, you can get the job done faster by understanding the drive cycles. Remember, you can use AutoTap or another scantool to check the drive cycle status.
Unfortunately, drive cycles vary slightly from manufacture to manufacture. We've documented the Ford and GM drive cycles. Since they're both about a page long, and can be a bit dry to read, I'm just going to link to our write-ups on our informational web site, www.obdii.com.
Ford Drive Cycle http://www.obdii.com/drivecycleford.html
For those of you awake enough to have read both, you'll see a lot of similarities. If you have another make vehicle, the information in either of the drive cycles above will at least get you close.
An interesting (and very dangerous - trust me) exercise is to use AutoTap to watch the various monitors change from "incomplete" to "complete" as you go through the various sections of the drive cycle. (Of course the safer way would be to use AutoTap to log the data to a file then check it out back in your garage).
The drive cycle is the sequence of events that must happen for the various system test programs to run on your car's computer. The drive cycle involves a cold start, and a certain amount of driving time at a variety of different loads. More details on those cycles later.
When is the drive cycle important?
First, to understand why the check engine light takes a while to come on. Not only must the appropriate test monitor run, in many cases, it must run twice, detecting the failure each time. If the test runs successfully two more times, it can turn the light back off.
Second, remember from a few emails ago that these system monitors must be complete to pass OBDII based emissions testing (early model years often allow a couple exceptions). If you ever get sent home from an emissions test and told to come back after some driving, you can get the job done faster by understanding the drive cycles. Remember, you can use AutoTap or another scantool to check the drive cycle status.
Unfortunately, drive cycles vary slightly from manufacture to manufacture. We've documented the Ford and GM drive cycles. Since they're both about a page long, and can be a bit dry to read, I'm just going to link to our write-ups on our informational web site, www.obdii.com.
Ford Drive Cycle http://www.obdii.com/drivecycleford.html
For those of you awake enough to have read both, you'll see a lot of similarities. If you have another make vehicle, the information in either of the drive cycles above will at least get you close.
An interesting (and very dangerous - trust me) exercise is to use AutoTap to watch the various monitors change from "incomplete" to "complete" as you go through the various sections of the drive cycle. (Of course the safer way would be to use AutoTap to log the data to a file then check it out back in your garage).