Jump to content

Recommended Posts

Posted

2020 Rocky Ridge K2 Silverado 5.3L

14K miles

First time posting.

 

Have been expereincing intermittent brake lights staying on after engine shut down for several weeks. Took it to the dealership, who ran a diagnostic on the truck and came back with "all things look normal, no codes". By the time I got home, the brake lights were in a state of constant "on" and I was able to restart the truck without applying the brake, even with the key fob outside the vehicle. Received several Onstar warnings to "Service Parking Brake". The parking brake had engaged and would not release. I disconnected the battery for 20 minutes, reconnected the battery which cleared the code. Called the dealership and was told I would have to leave it with them for awhile (several days to a week) to find out what the issue is. Would be ok except they do not provide a loaner car and rentals are thru the roof in our area ($100/day) so I have been living with this inconvenience until I can find an alternative way to work (80 miles rt).

 

Then this happened over the past weekend:

 

While driving back from the lake with my boat in tow, the truck went into a critical brake failure mode. Here is the series of events.
  1. Moored boat at dock and went to retrieve truck to remove boat from water.
  2. Could not unlock door on truck with FOB. Truck was "dead". No voltage activity.
  3. Used 12v portable jump pack to start vehicle.
  4. Let run for @20 min before proceeding to drive home with boat attached. Check engine light was on for 30 seconds then went out, but no warning dialog boxes.
  5. After we were on the road for @15 min, in rapid succession, I received the following warning dialog boxes:
    1. Service Trailer Brake System
    2. Service ESC
    3. Service Parking Brake
    4. Brake System Failure - 62 MPH Top Speed
    5. Check engine warning light
    6. Traction Control Off warning light
    7. ABS Off warning light
As soon as I saw this, I tried to apply the brakes and they went to the floor. As you might imagine, it was chaotic in the vehicle when it became apparent that the vehicle along with the 6000lbs of Boat/trailer in tow was not going to stop in any timely fashion. Along with the trailer brake failure and vehicle brake reduction, the backup surge brakes on the trailer would not engage due to the lack of quick inertia braking force. I had the pedal to the ground and eventually we came to a stop. The rest of the ride home (2 miles) was a 5mph white knuckle event.
 
The insult to the injury is there has been no warnings, email, text or posted on account from Onstar about this series of events but... I did get one on the same day that my Oil change is due. I am posting the screen shots I took after we came to a stop.
IMG_6595.thumb.jpg.0fa8958999d57f903e4926a3e806c192.jpg
IMG_7297.thumb.jpg.710f5d91bb38ed099da9375c5803af5a.jpgIMG_7301.thumb.jpg.40cac10017fa91cbaab1d4739fcc4962.jpgIMG_7298.thumb.jpg.ad3c52c5d0d3a5b4cd58b4923687eba7.jpg
IMG_7306.thumb.jpg.e5a27d862e72a7c77e83a16f51f5dfc9.jpg
 
It is being towed to the dealership tomorrow. I will let you know what happens.
 
I absolutely love my truck. It is the 5th Chevy that Ive owned, and sadly the worst one of the bunch.
 
M

 

 

IMG_7296.jpg

Posted

If I was throwing parts at it, I'd start with the brake switch and a reflash.  

Posted

Update 07/06/2021

Delivered vehicle to dealership @7:30 am. Reviewed issues with intake service personnel and validated that they had received documentation of events and supporting pictures.

Service Advisor called me @ 1:30pm and informed me that they had identified the issue. They retrieved a p25a2 code and proceeded to re-program the BSM per 20-na-073 warranty code 28yn75386417. Had to look this one up. It is a GM Service Bulletin that outlines the Loss of Brake Assist.

https://static.nhtsa.gov/odi/tsbs/2020/MC-10175760-9999.pdf

 

I picked up the truck 10 min before they closed (big mistake) and was told that everything had been cleared, the vehicle road tested and was good to go. After gathering my wife, who was eye balling a GMC Sierra, we left the dealership and proceeded home. After @ 5 min, my wife called me (she was following me home) and let me know that my brake lights have been on the entire time since we left and wanted to know if I was riding the brake. I immediately turned around and took it back before I experienced another brake failure. This is now the third time it will be back to the dealership for the same issues. Im exhausted and disgusted with this whole process.

Any suggestions on the next move? Should I start the process for turning this turd into a lemon? How long should I be reasonable about this?

 

Thx

M

Posted

Updated 7/7/2021

Received call from Service Advisor and he stated that they found the issue. The Brake Module needed to be refreshed to relearn the brake pedal position sensor. I went to pick up the truck and when they pulled it up for me, the brake lights stayed on with no one in the truck with the engine still running. WTF!! They drove it back into the shop to rescan it and found no codes. Restarted the truck and the brake lights went off. I decided to drive it home and roll the dice. Stopped at Petsmart for some dog food and brake lights stay off when I turned the truck off. By the second stop (restaurant) the brake lights wouldn't turn off and now it sits in my driveway with the brake lights on till it drains the battery.

 

I am starting the process to lemon this one out. It will go back to the shop for the forth time in less than a month.

 

Has anyone ever been thru the process? I bought the truck new @ 7 months ago.

Thanks

M

Posted

Updated 7/7/2021

Called GM's Warranty, Repair and Lemon Law helpline and was given a case number. They will be assigning a Senior Advisor within the next 48 hours that will work with my dealership until this is brought to an acceptable resolution. I will  post updates as this progresses.

M

Posted

I lemon lawed a 2015 Tahoe in Florida, do a Google search for the requirements in Georgia. Have good documentation and all service work orders. Also Google search Lemon Law attorneys, most will get paid when GM settles the case. I did not get much help from GM and I doubt things have changed in the last few years. Good luck and keep us informed.

Posted (edited)

Did some research and Georgia has 24mo/24K with an extra year to file for arbitration. Also, if it involves critical components or a safety related issue that could possibly endanger the occupants of the vehicle or others, it only has to happen once to qualify for Lemon status and I can bypass the usual 3 attempts to repair. I guess either way, since it has been to the dealership 4 times for this and next week will be number 5, I could file for the status now.

GM has already contacted the Service Advisor and will be discussing with me next week what the process towards resolution will be. I will give GM some time to work it out. Don't really want to give it back and not sure there is a suitable replacement availble in our area.

Will post updates when I get them.

M

Edited by mdot
Posted

Updated 07/16/2021

Truck spent two days at dealership and received the following repairs:

Installed 13597422 SL-N-Sensor

Installed 84683650 SL-N-Connector Kit

Brake lights are now staying off when parked and ignition is off. Hope this will take care of the issue.

M

 

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...