9 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHabs and psm error code 996
Reported or suspected cause
harness
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
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 report identifying a cause
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.
Reported cause · Original poster
my prior mechanic says sometimes it's not module as was caused by bad harness.
Leading evidence: 'harness' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'harness' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Clean maf, the codes were cleared' (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
After changing switch AND cleaning MAF, the codes were cleared.
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.
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
After changing switch AND cleaning MAF, the codes were cleared.
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.
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.
9 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.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
I bought a non-OEM model cheaply ($60) but can't tell you how well it worked as my 996 issue ended up being the brake switch, so I swapped the original MAF sensor back in and retained the cheap one as a backup.
Hi all,
Loving my 03 C4S but recently got error code that goes on sometimes. My regular Porsche mechanic on the phone said it could be as simple as a brake light, but this new local mechanic said he plugged it into computer and it is either brake switch or psm module.
How much are either problems to fix?
Thx everyone.
PL
I had two problems - brake light switch, and MAF. I was definitely having intermittent brake lights, and would trigger the PSM and ABS lights. But also, a wonky MAF can cause these lights. After changing switch AND cleaning MAF, the codes were cleared.
Brake light switch. Not much for the part - $18 from SunCoast - and a hour of my time upside down in the footwell and we are all good again takes some fiddling.
Old switch dismantled to find one of the copper contacts worn through - that was the culprit!
Sent from my iPhone using Rennlist
Both are easy DIY fixes. Brake switch is cheaper, so I'd start with that. Over the years, I've had brake switches go out on at least 3 different makes & models of European cars. If not brake switch, then replace MAF sensor. MAF sensors can be a bit pricey. I bought a non-OEM model cheaply ($60) but can't tell you how well it worked as my 996 issue ended up being the brake switch, so I swapped the original MAF sensor back in and retained the cheap one as a backup. I started with the MAF sensor first, and because it ended up being the brake switch, wasted money buying the MAF sensor. Brake switches are way cheaper than MAF sensors.
big bummer - replaced brake light switch and it didn't solve problem.
mechanic says a place in virginia can rebuild the PSM module for $600-$1,000, depending on the model.
add in $200 labor.
any other thots here?
my prior mechanic says sometimes it's not module as was caused by bad harness.
also, how do i know it's not MAF?
thx all.
PL
