Jump to content

Brake Pad Life System not updating after front NEW brakes, rotor and sensor

Ranger473
 Share

Recommended Posts

Ranger473 Enthusiast

Ranger473

Posted
Posted

2020 GMC 3500HD SLT L5P SRW

I replaced the front rotors, brake pads, and brake pad life sensor (GM Part # 84702752) on my truck but the Brake Pad Life information screen is not updating.  The owner's manual says it should sense the new sensor and brake pads and give me the option to reset to 100% but both front and rear brakes are greyed out and not responsive when I try and select one or the other.

 

I have driven the truck around 40 miles with multiple starts and stops, including turning the truck off then back on thinking perhaps it takes time and cycles to update but there is no change.

 

I pulled the tire and pads back off and verified the new sensor is installed correctly, I think.  It seems like there is only one way to install it on the pad.  I  installed R1 Concepts OPTIMUM OE Brake Pads from Rock Auto.  They seem to be a perfect match to the ones I removed (I have no idea if the old pads are OE).

 

However, the pad on the sensor that (should) contact the rotor is about .25" from actually touching the rotor. - Like the pads are thicker than what the sensor is designed for.  Does anyone have any thoughts??  I assume that when the brakes wear down to around 60 or 70% the sensor will finally contact the rotor and the system will start working...

kylant Enthusiast

kylant

Posted
Posted

i know the end user cannot reset the monitor, even though it appears we can. dealer only. 
why the readings are greyed out...??

gemarsh Senior Enthusiast

gemarsh

Posted
Posted
5 hours ago, kylant said:

i know the end user cannot reset the monitor, even though it appears we can. dealer only. 
why the readings are greyed out...??

Dealer only, unless a person buys a scanner that has the capabilities. Paid less than 4 bills for a Launch. 

 

20230918_151627.jpg.596fa6481b1edd973ddc933e556b2a8f.thumb.webp.10ac3252a4795bb2ad6cc35affc3bb83.webp

  • 3 weeks later...
bowtie2007 Enthusiast

bowtie2007

Posted
Posted

I went through the same thing. I finally bought the GM specific X431 Launch bi-directional scan tool. It is currently on Amazon for $180 with a $40 off coupon bringing it down to $140. With that tool, I was able to reset my brake pad life. I would rather pay that and have a new toy than pay the dealer to do it.

  • Like 1
  • 10 months later...
mrjulian416 Enthusiast

mrjulian416

Posted
Posted
On 10/12/2023 at 6:04 PM, bowtie2007 said:

I went through the same thing. I finally bought the GM specific X431 Launch bi-directional scan tool. It is currently on Amazon for $180 with a $40 off coupon bringing it down to $140. With that tool, I was able to reset my brake pad life. I would rather pay that and have a new toy than pay the dealer to do it.

 

Bowtie, can you share which specific model you bought?  There are a ton of Launch readers on Amazon, but I don't see any X431 in that price range.

 

The link gemarsh provided above seems to be broken.

tonto340 Enthusiast

tonto340

Posted
Posted

This may be the one Bowtie was referring to:

https://www.amazon.com/LAUNCH-X431-Elite-2-0-fit/dp/B0CRT4GJMX/ref=sr_1_10?crid=1J29CDUTXLEG3&dib=eyJ2IjoiMSJ9.UVq5HAn5fc5LV7BEXV8v5hz9TTQSdNnuPWez43A9ApDMplaM5NN-5xacI0-YEfSEwQa9mE2r9HQ00SfPthhaSeOP8CpmLZuCc1AoOJBhrVKR0eXtNO7lGaWjYuDUycnVGVa-tBSNZnem1uZLWmpqZbq-Ft009snGT7OUZutMEf1lB3_X5-BNxyz97kbG7FsrZc6kdul8SWJWZ7Xw3ym30CdngEWH377ArIP3-qZd1J5jw5GUU5zPGeb4yGTatcCO-lMeJbl1cexherpKn_LoYQORgHPK6rDq5AwJ2CL9Txs.Z5_fq4iPwU50oJYWccbr4fNe8pf2pKf72d4JSeRCxKc&dib_tag=se&keywords=x431+launch+scan+tool&qid=1724934983&sprefix=x431%2Caps%2C226&sr=8-10

  • Like 1
mrjulian416 Enthusiast

mrjulian416

Posted
Posted

I am happy to report that the Launch reader in my link just above was able to reset the brake pad wear indicator.  It also has the capability to change the TPMS target pressure and adjust the tire size if needed.

 

Of course it is a full code reader, able to access all modules/codes, perform ABS bleed, etc. etc.

 

 

  • Like 2
  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,770
    Total Members
    8,960
    Most Online
    Paul8556
    Newest Member
    Paul8556
    Joined

  • Who's Online   5 Members, 0 Anonymous, 596 Guests (See full list)

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...