MIL on time at startup
#1
MIL on time at startup
My 2005 MCS failed a state inspection the other day for "KOER" ...apparently Key On Engine Running. The MIL goes out after 3 - 4 seconds (has been like this since I've owned it - 2 years) of the engine running and there are no codes stored or pending. I'm wondering if the state OBD computer is looking for a quicker MIL off time after engine start as my VW CC MIL turns off in about a second.
Basically just looking for confirmation that a 3 - 4 second delay is "normal" for an R53? If anyone is willing to count "Mississippis" while watching the MIL go from on to off between the key on position and engine start I'd greatly appreciate it!
On a side note, the guy at the testing station asked if I had replaced the battery recently. I have not, but did have it disconnected while doing some work on the car last month. He failed to point out the KOER on the inspection form, but told me the battery disconnect was likely the reason for failure, and that I would have to drive for an hour or so to set the OBD system to "ready". I found the KOER failure on the report and can't imagine that completing a "drive cycle" or 3 would have any effect on a KOER failure.
Thanks in advance!
Basically just looking for confirmation that a 3 - 4 second delay is "normal" for an R53? If anyone is willing to count "Mississippis" while watching the MIL go from on to off between the key on position and engine start I'd greatly appreciate it!
On a side note, the guy at the testing station asked if I had replaced the battery recently. I have not, but did have it disconnected while doing some work on the car last month. He failed to point out the KOER on the inspection form, but told me the battery disconnect was likely the reason for failure, and that I would have to drive for an hour or so to set the OBD system to "ready". I found the KOER failure on the report and can't imagine that completing a "drive cycle" or 3 would have any effect on a KOER failure.
Thanks in advance!
#2
#5
Get a good OBD scanner like Blue Driver. You can do a smog check and it'll tell you if the computer is ready or not and if it isn't ready, what components are causing it to no be ready. My R50 was in a not ready state for a couple of months until I figured out it was the purge valve that had gone bad. Swapped it out and it went ready on the next startup.
#6
Get a good OBD scanner like Blue Driver. You can do a smog check and it'll tell you if the computer is ready or not and if it isn't ready, what components are causing it to no be ready. My R50 was in a not ready state for a couple of months until I figured out it was the purge valve that had gone bad. Swapped it out and it went ready on the next startup.
It turns out all monitored OBD flags were signalling ready...confirmed at home with my scanner. The only issue was that the guy doing the test apparently failed the car because the MIL didn't turn off instantly when the engine started. When I took it back for the re-test yesterday and explained my findings and concern that the tech. should perhaps be a bit more patient...well it miraculously passed.
The following users liked this post:
ssoliman (05-02-2020)
Thread
Thread Starter
Forum
Replies
Last Post
drrigg
R50/R53 :: Hatch Talk (2002-2006)
4
02-12-2018 10:38 AM
minidave07
R56 :: Hatch Talk (2007+)
4
11-17-2014 03:42 AM