12 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHbrake wear sensor
Reported or suspected cause
front pads were down
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
I had an erratic sensor and it turned out that the front pads were down to their limits.
Leading evidence: 'front pads were down' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'front pads were down' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Replace "' (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 · Original poster
I thought as the pads wore down, the indicator shorted out and signaled the "time to replace".
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
If you do a search on brake sensors you will find recommendations to zip tie the sensor back or replace with a jumper when you track.
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
My track pads, Hawk DCT-60, are too squeaky for the street and I replace with OEM if I plan on doing extensive street driving.
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 have been running Pagid Yellows on the street and track forever.
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
That's most people that do a lot of track time end up just using a jumper to keep the light off.or use track pads with no sensors then switch back to street pads with sensors.
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
That's most people that do a lot of track time end up just using a jumper to keep the light off.or use track pads with no sensors then switch back to street pads with sensors.
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.
12 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: 20261027T000231Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
My '98 C2 coupe's brake wear sensor came on during a DE last week. Was on during the drive home but the next morning when I went to work it was off. So I am thinking it was an erroneous reading. Two days later on the way to work, it comes back on and remains on for the drive home and the drive to work on day 3. On the way home, day 3, the light is off. I have ordered new pads and sensors because at 120000km I think they have lived a good life, but what is the deal with the indicator? I thought as the pads wore down, the indicator shorted out and signaled the "time to replace". Why do I get a light randomly?
Here is a picture because diagnosis is always easier with a picture!
You didn't really need to have bought new sensors but now you have use them on the new pads. You will find more wear on the front pads than the rear but go ahead and change them all around the car. .
De and track days usually overheat the sensors and they become erratic. I've seen brand new pads and sensors start acting up after just 1 De day. That's most people that do a lot of track time end up just using a jumper to keep the light off.or use track pads with no sensors then switch back to street pads with sensors.
I had an erratic sensor and it turned out that the front pads were down to their limits. Somehow it was a small enough change in thickness that it started to occasionally trigger the sensor. I didn�t think it was possible either. I did a full brake job with new Sebro sensors and all is well.
I had a similar issue. I looked at all of the sensors and none of them were worn through. The problem continued intermittently. Eventually I removed each sensor completely to examine them. One of them had a broken wire on the end that plugs into the car - not the end that plugs into the pads. I replaced that one sensor and all is good.
If you do a search on brake sensors you will find recommendations to zip tie the sensor back or replace with a jumper when you track. I had a replacement set of sensors on the front with my track pads that started to melt from the heat, not rotor contact, so tied back. My track pads, Hawk DCT-60, are too squeaky for the street and I replace with OEM if I plan on doing extensive street driving. Are you using OEM pads for DE?
A lot of folks don't use sensors if they track their car. Especially handy to those that change it to racing pads just for the event. As someone here mention that it is easy to disable them by just shorting the leads. I disabled the sensors too and found just eye-balling the thickness of the pad material works just as good.
i was on my stock pads for this DE. I probably do 1-2 track days a year so having a dedicated set of track pads isn�t on my radar. Good info about tying back the sensors, I will do this next time. Once my new sensors show up I will pull all the wheels and figure out which one is having an issue.
Yeah , I know this is an old thread, but it popped up when I did a search.
I have new brakes at all four corners with less than 200 miles on them. This night when I hit a bump in the road, the light came on. Maybe the sensor is kaput? I'll have to take a closer look in the AM.
FWIW, I removed my sensors back in 2004 and haven't thought about them until reading this thread. They were doing the same thing that yours are doing. If you do remove them, you will need to pay attention to your pad wear. As a side note, there may be a time that you decide to run track pads year round. I have been running Pagid Yellows on the street and track forever. One less thing to worry about.
