Jump to content

ABS kicks in on when it shouldn't

ghorty

By ghorty
in Troubleshooting & Recalls

 Share

Recommended Posts

ghorty Enthusiast

ghorty

Posted
Posted

I just started having an issue where my ABS breaks kick in when it shouldn't. I have noticed it happen mostly when backing up or down grade, and then doesn't turn off until I take it out of Drive. I have also had this happen when parking in a dry parking lot, so no reason it should kick in. There are no error codes being generated by the ABS. When it does kick in, I noticed the brake peddle clicks when I press it.

 

Anyone else have this or any ideas what's causing this?

 

2016 Silverado Z71

Andy Seibel Enthusiast

Andy Seibel

Posted
Posted

This sounds very strange. When the ABS activates, it actually releases pressure on the brakes to allow the wheels to turn. if this were to happen while you are rolling on dry pavement, you should have problems stopping. Can you feel the pulsing? the ABS pulses and you can feel it in the brake pedal.

 

When you hit the brakes is the truck stopping faster or slower than you want it to?

 

Your issue isn't with grade braking is it?

2strokesmoke Enthusiast

2strokesmoke

Posted
Posted

Under a set speed say around 20 mph abs engagement should not activate, locked out by either speed sensor, or abs wheel sensor. If you hear it cycling or notice your breaking is reduced at low speed stops, have it checked as this can be very dangerous and is not operating normally!

 

Best of luck

ghorty Enthusiast

ghorty

Posted
  • Author
Posted

This is all under 20 MPH. I am bringing it back in. I just wanted to check if anyone has heard of the issue before so I could give them better detail than it happens from time to time that ABS kicks in and doesn't throw an error code.

Andy Seibel Enthusiast

Andy Seibel

Posted
Posted

I'm not certain that 20 mph is the correct limit. I have my ABS activate all the time when I'm plowing snow, trying to stop on ice. And most of that occurs under 20. so the actual limit may be much lower.

 

But the key is when you apply brakes and the wheels suddenly & immediately stop spinning, the system thinks you are still moving forward so it releases the brakes to help you gain traction.

 

If the system is engaging when your wheels are still rolling, there is something wrong, and I agree you should take it in.

  • Like 1
2strokesmoke Enthusiast

2strokesmoke

Posted
Posted

I'm not certain that 20 mph is the correct limit. I have my ABS activate all the time when I'm plowing snow, trying to stop on ice. And most of that occurs under 20. so the actual limit may be much lower.

 

But the key is when you apply brakes and the wheels suddenly & immediately stop spinning, the system thinks you are still moving forward so it releases the brakes to help you gain traction.

 

If the system is engaging when your wheels are still rolling, there is something wrong, and I agree you should take it in.

It may vary well be a lower speed engagement, but the principle is the same should not cycle at low speed!

Have it checked!

ghorty Enthusiast

ghorty

Posted
  • Author
Posted

It's in the shop right now, the ABS even kicked in as I parked it in the service garage there. Have not heard any follow up yet. Will keep it updated for anyone else who runs into it.

ghorty Enthusiast

ghorty

Posted
  • Author
Posted

Just got off the phone, the dealer was able to replicate it today while in the shop and they are talking with GM on the issue. They are giving me a rental until as they dig deeper into the issue. Progress!

paumat Enthusiast

paumat

Posted
Posted

This was a common issue on the 99-02's and there was a recall for it. I can't remember the exact cause but I believe it was corrosion on the wheel speed sensors.

SILVER SLED Senior Enthusiast

SILVER SLED

Posted
Posted

The cause from the recalled older trucks is because the flat mount portion of the wheel speed sensor that mounts to the hub would be raise up by rust on the hub pushing up on the sensor causing an out of spec reading from that sensor causing the abs to activate at slower speeds...hope that makes sense. This never set a code either, but if the vehicle is drive with a scanner set to observe the sensors, you can see a sensor(s) drop out/display 0mph wheel speed. A bad sensor can cause this also. It shouldn't be that complicated. Hopefully for you the problem is that simple and an easy fix.

ghorty Enthusiast

ghorty

Posted
  • Author
Posted

When I picked up the rental they were talking to GM on it, and might not get an update until Monday, we will see. I hope it didn't rust in less than a year that I owned the vehicle.

 

And yes, I was ecstatic when they said they replicated the issue. That was the issue with the 2014 Silverado I turned in with the steering vibration. They would not admit they could replicate the issue. I traded the 14 in on this one before the manufacture warranty went out on it.

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

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...