10 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHWhat's up with my Brake Wear light?
Leading reported evidence
Install track pads and have had the light
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
I had one get worn through and I took them off when I installed track pads and have had the light on the dash since.
Leading evidence: 'Install track pads and have had the light' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check pads' (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.
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
The sensors are a PITA, I just check the pads visually now.
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.
10 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: 20261027T061840Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I was driving to Richmond this past weekend in heavy rain, and the brake wear light came on. No big deal, since water on the brake sensor(s) causes it to come on sometimes.
Normally it turns back off after a couple days at the most, but it stayed on this time - though my brakes have plenty of pads left.
Last night, I turned the ignition to the on position, but didn't start it, and left it there for a few seconds before starting the car, and when I started the car, the Brake Wear light turned off. Hmm.. When I started the car again the light came on - so I turned the car off and decided to leave the ignition switch in the on positon for a few secs first, then I started it - and presto the light turned off again (?).
This morning the same thing happened- I managed to turn the light off, but on the way to work the warning light came back on again. When I arrived to work, I restarted the car - after leaving the ignition in the on position - and the light turned off again.
What the heck?
Where do I look to fix this thing? Why would this issue crop up after a normal drive through the rain?
You probably just have a break in the sensor somewhere. It's not completely broken and is making intermittent contact. I had similar symptoms. I got got lucky and found it on the first sensor I checked. Replace it with a new one ($11) and you're all set.
+1
I had similar symptoms. I pulled the sensors out of the pads and even though there was 3+mm left one of the sensors had started to wear and there was copper wire exposed but the wire was not broken yet. That was enough to cause intermittent warning lights in the wet. I just taped up the sensors and zip tied all the sensors off the pads. Then I changed the pads. The sensors are a PITA, I just check the pads visually now.
Me too. Found the broken sensor wire on the first wheel I checked (L Fr), spliced the wires together and zipped tied all the sensors up. It's no big deal to check pads.
Maybe this is a stupid question - but where are the sensor wires? I guess I've never really looked at/for them - I just take it to the shop and have never had a need to mess with them.
Anyone have pics of them, and pics of how they fit into the pads? I can't get to my car right now - will have to wait until after work sometime.
Are they easy to get to and monkey around with?
While we're on this topic. I had one get worn through and I took them off when I installed track pads and have had the light on the dash since. My impressions from reading here were that if they were unplugged they would not trigger the light? Do I need to plug in a good pad sensor into the one that had failed prior to pulling them in order to kill that darn dash light?
yes.... or just cut your old one and sodder the 2 wires together. I cut mine 1" from the plug and shrink wrapped it.
That light will be on as long as there is a break in one of the sensor.
So I need to solder the broken one and re-install it on the car to get rid of the light? Currently none of them are plugged into the car....they're all in the tool box right now.
Andy
