Welcome to Ultimate Subaru Message Board, my lurker friend!
|Welcome to Ultimate Subaru Message Board, an unparalleled Subaru community full of the greatest Subaru gurus and modders on the planet! We offer technical information and discussion about all things Subaru, the best and most popular all wheel drive vehicles ever created.
We offer all this information for free to everyone, even lurkers like you! All we ask in return is that you sign up and give back some of what you get out - without our awesome registered users none of this would be possible! Plus, you get way more great stuff as a member! Lurk to lose, participate to WIN*!
* The joy of participation and being generally awesome constitutes winning
** Not an actual guarantee, but seriously, you probably won't regret it!
Serving the Subaru Community since May 18th, 1998!
Drive Cycle and CEL
Posted 15 August 2007 - 01:59 PM
I did some internet searching a few weeks back to better understand how the CEL gets turned on and off. I assumed that it was the same process for any code that could be set in any OBD-II make/model.
I didn't dig very deep, but I found that it takes a fault to be present for 3 drive cycles before the CEL is turned on. I also saw mention that it took 40 drive cycles to turn off the CEL. The definition of a drive cycle was from cold-start to full operating temperature.
My reason for writing this, is that I'm questioning the "generic" information that I found.
My CEL came on yesterday (haven't check what it's for yet). And went out just this afternoon. I've only driven the car 3 or 4 times in between, and didn't stop for gas at all.
How is it possible for the light to go on and off in such a short time? Are there different drive cycle/thresholds for different error codes?
Posted 15 August 2007 - 02:34 PM
Right and then if it doesn't see the problem for a certain number of trips or however that code is setup then the CEL/MIL may go out by itself. Some codes get stored in history, so even if the CEL/MIL isn't on now, it may be possible to get it with a code reader by going to 'code history'.
Posted 15 August 2007 - 02:46 PM
Posted 17 August 2007 - 10:34 AM
Turns out my short-lived code was P1507 (IAC). I've seen this before, it's time for a cleaning.
Posted 17 August 2007 - 11:04 AM
Posted 17 August 2007 - 11:12 AM
The ECU wasnt ready for inspection.
Posted 17 August 2007 - 11:17 AM
The evap seems to take the longest, probably because of the fair number of conditions that have to be met for it to run that test. Not sure if the scanguage will show the I/M readiness status, but most code readers will.
Posted 17 August 2007 - 03:42 PM
40 drive cycles is for the ECU to ERASE the code, not turn off the MIL. Depending on the code, it can turn on immediately, or after 2 or 3 occurranced, and the ECU will turn the light off after reaching the same circumstance that set the code 3 or so times. The code will still be retained in memory as a "history" code for future refefence until erased (either ECU cleared or the aforementioned 40 cycles).
I gotcha, very cool information. I didn't realize that the ECU would respond that quickly (relatively speaking) to an error condition (excluding critical stuff like misfire, etc).
Posted 18 August 2007 - 10:00 AM
I just ran into this with inspection. They put 30 miles on the car and they still couldnt get it inspected, so they said to use the car and bring it back tuesday.
The ECU wasnt ready for inspection.
I know the frustration Nipper. I went through this same thing when I had to renew my registration some time back. I wasn't driving the car enough and the battery was dead so the ECU was reset. It took me 3 trips to the shop to get enough monitors set so I could pass the test.
During this incident the IM tech told me each model car has a procedure to follow in order to get all the monitors to set fairly quickly. He showed me the procedure for my '01 OB in a manual he had and I copied it down. I left the shop trying to follow the procedure as best I could. There were about 11 steps I had to do that included a number of speed changes along with stops and other manuvers. By the time I got back from my 20 mile trip I had set just enough moitors to pass the test. I also learned that when you clear the ECU error codes with a scan tool that it includes the monitors also. I didn't know that then and though it was just the error codes that were being erased. After learning that I am more cautious now when thinking about resetting the ECU.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users