8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHABS PSM
Reported or suspected cause
rear suspension out of alignment
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
Agree on buying Scanning device or code Reader, Mine turned out to be Rear Suspension out of alignment, which threw Steering wheel sensor out of spec.
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
Finally, I removed the ECU to check for visible faults on the PCB (which was a possibility according to research I had done) - while I didn't find any obvious faults, I believe the process of removing the board to check it out wound up wiping some sort of stored memory that was causing the code to be continually triggered.
Leading evidence: 'rear suspension out of alignment' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'rear suspension out of alignment' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check visible faults' (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
Disconnect battery - touch the positive and negative cables together, leave them disconnected for an hour so.
Disconnect right rear one and sure enough the code
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.
Performed · outcome unconfirmed · Original poster
I disconnected the right rear one and sure enough the code for it appeared and I was able to clear it once reconnected.
Install about the time this occurred, i unplugged them
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.
Performed · outcome unconfirmed · Original poster
I also have LED taillights and they were installed about the time this occurred, I unplugged them but since the schwaben is pointing to the wheel speed sensor my gut says its still in that circuit.
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
I had already replaced the brake switch and wheel speed sensor to that wheel.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Check visible faults
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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
Finally, I removed the ECU to check for visible faults on the PCB (which was a possibility according to research I had done) - while I didn't find any obvious faults, I believe the process of removing the board to check it out wound up wiping some sort of stored memory that was causing the code to be continually triggered.
Install about the time this occurred, i unplugged them
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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
I also have LED taillights and they were installed about the time this occurred, I unplugged them but since the schwaben is pointing to the wheel speed sensor my gut says its still in that circuit.
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.
8 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: 20261027T005001Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I have an 02 C4S with the ABS PSM light on. Having read many forums I replaced the brake switch which did nothing. Felt the MAF is probably fine as the car runs perfectly. I bought a Schwaben scanner and found a fault code for the left rear wheel speed sensor. I replaced it and although I have tried to clear it the code re appears without as much as starting or moving the car. I disconnected the right rear one and sure enough the code for it appeared and I was able to clear it once reconnected. I also have LED taillights and they were installed about the time this occurred, I unplugged them but since the schwaben is pointing to the wheel speed sensor my gut says its still in that circuit. I was about to order a replacement kit for the connection to the wheel speed sensor but mice have eaten away at a couple wires elsewhere so i'm wondering if there is a way to test the circuit before I cut into the harness? I was going to try a continuity test but read that doesn't work plus I don't know which pins to use .
Wheel sensor Part #5 here
http://www.autoatlanta.com/porsche-p...=99660640600#a
I don't think you have to cut the harness to replace the speed sensor, unless the mice chewed up further on the wiring. It by itself is a plug and play sensor.
Try doing a "hard reset" on your ECU. Disconnect battery - touch the positive and negative cables together, leave them disconnected for an hour so. See if that does anything to clear your codes (you may have to go through a few start/drive cycles). A few years ago I got a CEL that was related to cam deviation. I did a bunch of engine work that included vario-cam tensioner pads. Upon putting everything back together, the CEL was still illuminated regardless of the deviations now being well within spec. I reset the codes several times, but couldn't get rid of the CEL. Finally, I removed the ECU to check for visible faults on the PCB (which was a possibility according to research I had done) - while I didn't find any obvious faults, I believe the process of removing the board to check it out wound up wiping some sort of stored memory that was causing the code to be continually triggered. Once I put everything back together, the CEL disappeared after about 25 miles of driving, and I never had a problem with it again. Good luck - this stuff can be maddening.
When he says "disconnect" the battery he means
BOTH
terminals. Completely disconnect the battery terminals and then touch the positive and negative leads together.
I was about to replace the wiring harness that feeds the wheel sensor on that wheel as I�ve read they are a known problem where they attach to the wheel. Having pulled the seats and carpet to check the wiring prior to ordering one I found a wire chewed
off. Fixed! Yahoo! I had already replaced the brake switch and wheel speed sensor to that wheel. I should have swapped wheel speed sensors prior to buying one but was following the advice of a local Porsche mechanic as he read the code originally. I bought a Schwaben to clear the code myself after replacing the sensor. My suggestion to anyone working on one of these is to buy a code reader before replacing parts that are known to be troublesome. I was worried sick thinking it was my $1k LED lights or worse the ABS pump @ $3K.
Agree on buying Scanning device or code Reader, Mine turned out to be Rear Suspension out of alignment, which threw Steering wheel sensor out of spec. One I had it aligned again, I reset Wheel position calibration.
Couldn't have done it w/o durametric.
Only replaced brake switch first....
