Third time to emissions still no pass, no fail
Third time to emissions still no pass, no fail For the past three times now ive tried to get emissions done and they keep telling me that the computer hasnt logged enough data with the emissions codes or equipment to allow me to pass. they always ask, has the car had work done, battery dead, unplugged, and so on and its never the case. Then the tell me i have to drive it and come back after a minimum of 8 days. now i have got codes deleted for taking my cats off but its passed every time before without the codes. But with the amount of driving ive done with the car it should of had more then enough time to run the diagnostics but it keeps coming back that there's not enough data. Anyone have this problem or have an idea of how to fix it? thanks.
If this is the "readiness" tests being incomplete, you
can see which ones with a scan tool and then you
have to dope out what's keeping them from completing.
The Helm manuals have good info on these details. It
is possible that your "code killing" has been done in a
way that doesn't set a light, but also makes it
impossible to complete one of the readiness tests
(Enabled, No Error means the particular test "passes"
and feeds the Readiness rollup with "all is well";
Disabled gives you no light, but the Readiness test
that looks to that test gets nothing so cannot get
to its happy place).
So, find the failing Readiness, get the list of code
dependencies, check the each of the relevant code
modes for unhelpful "kill" mode instead of happy
"enabled, no error", and then drive the hell out of it
(might read up on the Drive Cycle to get more for
less).
can see which ones with a scan tool and then you
have to dope out what's keeping them from completing.
The Helm manuals have good info on these details. It
is possible that your "code killing" has been done in a
way that doesn't set a light, but also makes it
impossible to complete one of the readiness tests
(Enabled, No Error means the particular test "passes"
and feeds the Readiness rollup with "all is well";
Disabled gives you no light, but the Readiness test
that looks to that test gets nothing so cannot get
to its happy place).
So, find the failing Readiness, get the list of code
dependencies, check the each of the relevant code
modes for unhelpful "kill" mode instead of happy
"enabled, no error", and then drive the hell out of it
(might read up on the Drive Cycle to get more for
less).
Staging Lane
Joined: Aug 2012
Posts: 55
Likes: 0
From: Massachusetts
As dumb as it sounds, check the ground cable on the battery.
I had a 2000 Ws6 do this same exact thing. It ran and drove, but every now and then the computer would reset. I went to get a sticker, and it said the same thing. It turns out the ground cable had a break in it, and was only grounding itself partially. I replaced it, and everything went back to normal.
I had a 2000 Ws6 do this same exact thing. It ran and drove, but every now and then the computer would reset. I went to get a sticker, and it said the same thing. It turns out the ground cable had a break in it, and was only grounding itself partially. I replaced it, and everything went back to normal.
