Jump to content

Recommended Posts

  • 1 month later...
Posted

Did anyone ever find a fix for this? Mine still does it occasionally. I just try to ignore it. But I would like to get it fixed at some point.

  • Like 1
  • 1 year later...
Posted (edited)

Looking for a potential remedy for this as well. I have two downhill left turns on my daily drive and it happens every time on both turns. 

Edited by clubba
A word
Posted
1 hour ago, clubba said:

Looking for a potential remedy for this as well. I have two downhill left turns on my daily drive and it happens every time on both turns. 

See if water is getting inside the ABS control module.  A guy on another forum discovered this, his acted up only on left turns when the water sloshed to that side of the board and shut down his brakes and worked fine while driving straight or turning the other way.

Posted
On 4/19/2021 at 6:58 PM, swathdiver said:

See if water is getting inside the ABS control module.  A guy on another forum discovered this, his acted up only on left turns when the water sloshed to that side of the board and shut down his brakes and worked fine while driving straight or turning the other way.

Worth a shot. Any idea where the ABS module is located on these rigs? 

Posted
2 hours ago, clubba said:

Worth a shot. Any idea where the ABS module is located on these rigs? 

Not specifically on yours.  It's likely attached to the driver's side frame rail and probably not far from the ABS pump.

  • 2 years later...
Posted

Hello,

It has been 2 years since anyone has responded to this topic.  Has there been a fix?

My 2019 5500 has started the traction control light coming on going into turns and curves above 25 mph.  When light comes on, power is restricted until you let off accelerator, then there will be a delay then a noticable shift and then you can accelerate again.

Dealer tech thought a hub adjustment would take care of it.  No fix now they are reaching out to GM for help.

 

I told the Service Rep who wanted me to pay $600 to make these adjustments, that it wasn't going to be as simple as making some adjustments.  I was correct!  Thanks to this forum, I was educated.

 

If there is a solution to the problem, please help us.  Thank you!

Posted

Also, for those who might be experiencing this currently...

I did find that turning the traction control off using the switch on the dash.  The light no longer comes on nore do you get reduced power.  I read in a different thread that holding the button for 3 seconds will disable it.

This is not a permanent fix, but it will allow you to have acceleration power to climb hills when pulling a load.

  • 4 months 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
  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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...