15 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHABS fault
Reported or suspected cause
brake pedal switch pt no996.613.113.02
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
My 996 had a abs warning light turned out to be brake pedal switch pt no996.613.113.02
Leading evidence: 'brake pedal switch pt no996.613.113.02' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'brake pedal switch pt no996.613.113.02' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Use piwis or an auto logic unit' (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.
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'm a porsche mechanic so what we use regards to testers is the original porsche equipment ..
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.
15 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 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: 20261026T191851Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
ABS fault
How Can fault codes be retrieved from the ABS?
Have the dash warning light on - came on while in the garage for 6 months or so - nothing on the OBDII
Brakes have never felt up to porsche standards and probably need a pressure bleed. Which is on my todo list.
Also does anyone now the tread type of the bottom ball joint ?
Sensor in the hub has failed? They can be prone to this. Can be tricky to changed if the retaining screw shears, also the old sensor can need drilling out.
Ball joint thread fine M10 IIRC. Requires 18mm spanner. Replacement coffin arms, if after market, typically come with a new nut.
Obviously the wheel sensor is always most likely but I was hoping to find what is wrong before attempting to fix it, ABS gone wrong while it's sat in the garage.
Thanks for the Nut information, doesn't need a new arm and I would probably go genuine for a part like that, especially with the number of failures I have seen on forums. - if you keep fitting Chinese parts might as well buy a Chinese car! Not knocking Chinese cars but they are not porsche.
I might buy a Lotus next seems my old Esprit and even my VW Splitscreen was more reliable
If the abs light is on constantly when driving then there will be a fault code saying what the issue is or the area it relates to .
If your scanner can't read abs fault codes then take the car to an INDY .. get them to read the fault codes and if required diagnose the issue ... we can see the values of the sensors , voltage inputs etc etc .
Guessing at parts that could cause this is pointless .. i could probably come up with over ten items .. fault code readout is first point of call .
Give me a fault code and i can tell you what's wrong and explain it if needed .
EDIT .. you have driven the car and still have this fault ?
ABS should put fault codes on the diagnostic connector- looks like I just need a new code reader?
So what code readers are you using and getting ABS codes ?
I use a Piwis or an auto logic unit .. thats a trade only unit .. piwis can be bought but not cheap .. for your car a piwis 2 will be fine .. this is a porsche tester .
I take it you have driven the car and still have a constant fault ?
steering angle sensor will drop out with a flat battery and needs a drive over 6 mph to reset .
Slow speed ( 5 mph ) braking and a judder on the brake pedal .. that's going to be a reluctor ring and you wont get a fault code ..
fault codes are for something outside of normal operation .. corroded rings and the car is reacting to what it sees .. corroded ring means the pulse signal is constant over the corrosion .. the car thinks the wheel has locked up so applies abs ... you won't have a constant light though if it is this .
I'm a porsche mechanic so what we use regards to testers is the original porsche equipment .. currently a Piwis 3 but that's not needed for your car .
I picked up my ABS sensor failure on my iCarsoft POR v1.0 (around £100) , v2.0 does have more tools on it for about £50 more or Foxwell NT530 for about £165..
Back off the road again!
Drove home bit of wheel bearing noise, next day a new harsh knocking on the first couple of seconds applying power, like a gear cog jumping or grinding against something.
Off the power and back on the same thing happened a few times.
Bearings and a Hydraulic press ordered - one of the few tools I don't yet own.