Jump to content

Service ESC after 6000 miles?

Adam Kane
 Share

Recommended Posts

Adam Kane New Member

Adam Kane

Posted
Posted

Service ESC after 6000miles??

Hey all I bought a 2020 Chevy Silverado RST brand new from the dealer in December. I put about 6,000 miles on it already (traveling) and now I got a rattle every time I accelerate, check engine light flashing, service brake light, service ESC light. Like wtf? Did I just buy a lemon? Anyone experience anything like this? 

I plan on taking it to the dealer but are saying they don’t have loaner trucks for me even though I have a travel trailer I need to tow

calgator73 Senior Enthusiast

calgator73

Posted
Posted

rattle and flashing check engine light sounds like a misfire condition.  If you're using consistent top tier gas I wouldn't think that was the problem...  Hopefully your build date doesn't put you in the valve spring TSB.  Good luck.

ericarenee Enthusiast

ericarenee

Posted
Posted

Call GM Customer care and tell them you need to get it repaired but must have a  compatible  vehicle . be nice but  firm and  they will ok the dealer to rent you something from enterprise . its how it works for us .   

  • Like 1
  • 2 weeks later...
jljii Enthusiast

jljii

Posted
Posted

I had similar warning lights and had to replace ignition coil.

 

redwngr Senior Enthusiast

redwngr

Posted
Posted
On 3/27/2021 at 1:46 PM, Adam Kane said:

Service ESC after 6000miles??

Hey all I bought a 2020 Chevy Silverado RST brand new from the dealer in December. I put about 6,000 miles on it already (traveling) and now I got a rattle every time I accelerate, check engine light flashing, service brake light, service ESC light. Like wtf? Did I just buy a lemon? Anyone experience anything like this? 

I plan on taking it to the dealer but are saying they don’t have loaner trucks for me even though I have a travel trailer I need to tow

The lights might all be related to a sensor or connection serving the ESC. 

Might not take long to check/swap.  

 

 

Minnvmax Enthusiast

Minnvmax

Posted
Posted (edited)

I've seen the service esc light come on a couple times in two years so it can also be a fluke and nothing to worry about. But not when coupled with an actual problem. My 2019 is my personal reigning champion of weird non-issues. 

"No, I did not leave the radio on the last time I used the truck!" lol

Edited by Minnvmax
redwngr Senior Enthusiast

redwngr

Posted
Posted

On older trucks I've had the ESC (stabilitrac) fault occur when there was a bad wheel bearing causing change in sensor gap, or a wiring issue near a wheel.

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...