Jump to content

2020 SLT brake pedal vibration & AC noise HELP

Sierra20-20
 Share

Recommended Posts

Sierra20-20 Enthusiast

Sierra20-20

Posted
Posted (edited)

Spanking new 2020 SLT. At low and higher speed. When I feather the brake pedal, coming to a slow/stop, I can feel the pedal quickly vibrating on my foot. It’s only happened a few times in the last week or so and it’s very hard to recreate. When I can get it to do it, if I hold it steady on that sweet spot where it started, it’ll vibrate for a few seconds but as soon as pressure let’s off or goes harder, it goes away and I can get it to do it again immediately after. It’s strange. And I also have a noisy AC compressor. It’s like a whirling sound. If the fan is on and compressor is off, I don’t hear it. Then the compressor kicks on and it’s whirling again. I’ve got into two same trucks. 1 did the same, 1 was much quieter and hardly noticeable at all. I’ve messed with the vents, speeds, everything but it’s only when the compressor is on. Maybe GMC newer trucks make this sound and it’s a design issue ? I don’t know, it’s my first GmC truck. Nice truck but wtf over. I have an appointment in a couple weeks but still. Any ideas where they could start ? 
 

update: went for a drive around town. I can feel the vibration / hear is chattering slowing from 40 mph to around 35. Barely any pressure on the brake pedal. Will chatter in the sweet spot for a few seconds. If steady pressure is put coming from any speed or 40, no issue and no chatter.. I don’t freaking get it. 

Edited by Sierra20-20
  • 4 months later...
Crow0722 New Member

Crow0722

Posted
Posted
On 6/24/2020 at 7:07 PM, Sierra20-20 said:

Spanking new 2020 SLT. At low and higher speed. When I feather the brake pedal, coming to a slow/stop, I can feel the pedal quickly vibrating on my foot. It’s only happened a few times in the last week or so and it’s very hard to recreate. When I can get it to do it, if I hold it steady on that sweet spot where it started, it’ll vibrate for a few seconds but as soon as pressure let’s off or goes harder, it goes away and I can get it to do it again immediately after. It’s strange. And I also have a noisy AC compressor. It’s like a whirling sound. If the fan is on and compressor is off, I don’t hear it. Then the compressor kicks on and it’s whirling again. I’ve got into two same trucks. 1 did the same, 1 was much quieter and hardly noticeable at all. I’ve messed with the vents, speeds, everything but it’s only when the compressor is on. Maybe GMC newer trucks make this sound and it’s a design issue ? I don’t know, it’s my first GmC truck. Nice truck but wtf over. I have an appointment in a couple weeks but still. Any ideas where they could start ? 
 

update: went for a drive around town. I can feel the vibration / hear is chattering slowing from 40 mph to around 35. Barely any pressure on the brake pedal. Will chatter in the sweet spot for a few seconds. If steady pressure is put coming from any speed or 40, no issue and no chatter.. I don’t freaking get it. 

 

Crow0722 New Member

Crow0722

Posted
Posted

My 2020 Sierra does the same thing and the dealer can’t figure it out ... and recently I saw the traction control light come on when it does it every once in a while

ChacAT4 New Member

ChacAT4

Posted
Posted

I’m pretty sure there is recall about that. I purchased a 2019 Silverado RST. It had so many problems and recalls I ended up trading it in for a 2020 Sierra AT4.  I did a lot of research about the GMs new T1 platform and the infotainment 3 system. Which included reading all the complaints, recalls, GM technical bulletins between engineers and the technicians. Some of the earlier 2020 model trucks still needs the recalls done. 

  • 4 months later...
Smokey Chevy New Member

Smokey Chevy

Posted
Posted

I too have this problem with the brake pedal on my 2020 Chevy Silverado Custom. I mentioned it to my dealership’s service department after noticing it occurring intermittently. They did a ride along with me, and of course it didn’t happen, but he did ask me some questions that made me start better observing conditions present when it happens. Today, I figured out that it happened only when I applied VERY LIGHT pressure to the brake pedal when traveling between 30 and 40 mph. It would be a condition much like someone barely riding their brakes. Feels similar to how ABS acts sometimes on a gravel road. I can duplicate the condition fairly easily now. Not every time, but most of the time. I can also hear it, so I’ll probably be able to get video of it while it’s happening. 

Thejet07 Enthusiast

Thejet07

Posted
Posted

If you ever figure this out please let me know. I’ve had this issue for 29k out of 30k miles and my dealership is useless. I have a 2019 rst with 5.3 for reference.


Sent from my iPhone using Tapatalk

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

  • Latest Articles

  • Posts

    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...