11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCamshaft variance 1999 model
Leading reported evidence
Check pins
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
Maybe someone needs to take a multimeter and check the pins on the OBDII diagnostic port.
Leading evidence: 'Check pins' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check pins' (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
I've used generic scanners on my car - you should get something (even if not as detailed as Durametric)...
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
Sounds like he is just using a regular OBD II scanner.
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: 20261026T063944Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi All,
I've been budgeting for the eventual IMS/RMS/Clutch on my 1999 996. I took it to my mechanic so he could check the cam variance as well so I can decide if I wanted to drop the engine and take care of the Cam pads as well as AOS/IMS/RMS/Clutch.
However, he said that when he plugged in his scanner, nothing came up. No data points. Nothing detected. Is this typical in 1999 models or is this something to worry about. Engine date is 1998 is that makes a difference.
Try a different mechanic/scanner, or a Porsche dealer with PIWIS system. A 99 has data (mine is 7/98 build sold as a 99). I read mine all the time with Durametric software.
Certainly not "typical"... Has the car been stored? If so where? It's possible that rodents have chewed wires, and that's why he's getting no readings (I'm assuming that the mechanic knows his scanner works...). Good luck
Sounds like he is just using a regular OBD II scanner. If they are out of spec it will throw a code. But, as stated above, he should be able to read the actual variance with PIWIS or Durametric.
The mechanic said he got "nothing" - as in no readings at all. I've used generic scanners on my car - you should get something (even if not as detailed as Durametric)... It seems like there's something wrong with the OBDII output.
Huh. Maybe someone needs to take a multimeter and check the pins on the OBDII diagnostic port. I take the car runs so not the DME. Also, someone can drop the OBDII port and check that the wires and contacts are all in place on the back side of the connector.
I went out and bought myself a Durametric and was able to see the the variance values. Looks like I'm within spec
Curious if there are any resources on what all the values mean and what is the "good" ranges.
