6 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPIWIS newbie
Leading reported evidence
Replace preemptively
Suggestion or failed attempt
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 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
Both will leave you stranded, maybe replace preemptively.
Leading evidence: 'Replace preemptively' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Replace preemptively' (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 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
Also run the actual values and print a copy for later reference so you will know what normal values are.
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
I would suggest you run a complete VAL (Vehicle Analysis Log), it will list all control unit part numbers,hours of operation, number of programming operations, Vin numbers, software versions, over revs, all fault codes, codeing settings,and lots of other information that can come in handy later on.
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 · Original poster
The aim is to keep her running hard, and stock ( 110,000 miles).
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
I would suggest you run a complete VAL (Vehicle Analysis Log), it will list all control unit part numbers,hours of operation, number of programming operations, Vin numbers, software versions, over revs, all fault codes, codeing settings,and lots of other information that can come in handy later on.
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.
6 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: 20261026T133652Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I have found a full PIWIS system for my recently acquired 2002 996 C2 Tip.
Can someone tell me where I can find the camshaft deviation information to track cam chain wear?
Any other tips or things I can track or use this tool for (no current faults showing, but original O2 sensors not responding well to PIWIS)?
The aim is to keep her running hard, and stock ( 110,000 miles).
Previous owner did IMS, RMS, water pump and coolant header tank.
I'm doing: new thermostat, engine mounts, oil sender, temp sensor, O2 sensors, header tank sensor, plus all fluids (incl DT40)
and filters.
Plus a DIY Fister mod, because I can.......
You will find the cam deviations in 996/DME/Actual Values...
I would suggest you run a complete VAL (Vehicle Analysis Log), it will list all control unit part numbers,hours of operation, number of programming operations, Vin numbers, software versions, over revs, all fault codes, codeing settings,and lots of other information that can come in handy later on. Also run the actual values and print a copy for later reference so you will know what normal values are.
Don't be afraid to explore the functions, you will hurt nothing and can always change it back if you keep up with what you are doing, just stay out of "programming functions"..you have to really know what you are doing in there. The other functions are informational and coding /settings...
There is also a "simulator function" where you can explore things without even being hooked up to a car..
