11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCEL & fault code...
Leading reported evidence
Check gas cap, and it wasnt even
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Leading evidence: 'Check gas cap, and it wasnt even' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check gas cap, and it wasnt even' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
But the reason I asked was because I while back I got a MAF code so I cleaned it out and to get rid of the CEL I disconnected the battery.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Do *not* ever disconnect the battery with the engine running, the key on, or the key even in the ignition!
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
Yes, I filled the tank earlier the same day, then drove about half a tank, and the light came on just as I got home.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
yeah if it didnt come back, topping it off probably filled a vent line causing the code
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
The engine controller can keep track of how many miles (km actually, though limited to 65535km) the car was driven since the check engine light was cleared (and this may be reset when battery power is removed too).
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
11 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T044418Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
The check engine light came on a few days ago. Today I hooked up the Durametric scan tool and this is what came up:
P0446 - Factory fault code 95
Evap Cannister shut-off valve function (below limit)
I cleared the code, and it has not re-appeared after starting the engine and running it a bit. However, I have not driven the car any distance yet.
Here's the question: Is this something to be concerned about?
Thanks.
...Rickker
Yes, I filled the tank earlier the same day, then drove about half a tank, and the light came on just as I got home. I'm pretty sure I turned the gas cap for about 3 or 4 clicks after refueling.
Sorry to derail the conversation here but if you were to clear up this code by disconnecting the battery, will the history of the code still be stored and therefore read by the Durametric? Or is it gone forever?
The code is erased when 12V battery power is removed from the engine controller such as would be the case when the battery was disconnected.
Do *not* ever disconnect the battery with the engine running, the key on, or the key even in the ignition!
Anyhow, the code can not be retrieved once battery power is removed and reapplied (or the code is erased by the use of a code reader/eraser tool).
However, there can be a record of sorts that something was 'cleared'... The engine controller can keep track of how many miles (km actually, though limited to 65535km) the car was driven since the check engine light was cleared (and this may be reset when battery power is removed too). There is another km counter than is used to count the number of km the car has driven since the check engine light came on.
A sophisticated code reader (Durametric should qualify) can read these values if the engine controller supports them. (The are Mode 1 Pids 0x21 and Pid 0x31 IIRC.)
Sincerely,
Macster.
Thanks for the explanation. Yeah I've never disconnected the battery when the car is on or the key is in the ignition. But the reason I asked was because I while back I got a MAF code so I cleaned it out and to get rid of the CEL I disconnected the battery.
It never came back but I was wondering if when the time comes that I hook it up to the Durametric, would I still be able to see the history of the codes?
I guess not so at least I know now.
Thanks again!
This is a source reference. Confirm exact model applicability in the original material.
