Jump to content

Recommended Posts

Posted

According to my dealership, GM is reporting there is no fix on the horizon anytime soon and to keep me in the loaner for the foreseeable future. My dealership has been great trying to accommodate me, but it’s beyond frustrating. I have teenagers that need the leg room of my crew cab. The loaner’s extended cab just isn’t passing muster. 
 

I filed the report with the NHTSA a couple weeks ago. My family is a loyal GM family, but we’re ready to start breaking rank if this isn’t rectified soon!

Posted

I also filed a NHTSA complain but, in addition, sent a detailed email to several automotive reporters with links to the various threads here discussing the brake and forward camera updates and how they - ironically - bring about the very issues the updates were meant to avoid. Will see if that generates any media coverage/scrutiny of GM. 

Posted
1 hour ago, DenaliDonkey said:

According to my dealership, GM is reporting there is no fix on the horizon anytime soon and to keep me in the loaner for the foreseeable future. My dealership has been great trying to accommodate me, but it’s beyond frustrating. I have teenagers that need the leg room of my crew cab. The loaner’s extended cab just isn’t passing muster. 
 

I filed the report with the NHTSA a couple weeks ago. My family is a loyal GM family, but we’re ready to start breaking rank if this isn’t rectified soon!

Extended Cab Silverado - try a Chevy Trax on for size... that was my last loaner.

Posted

Oh I had the Trex and the Equinox over the past few weeks as well. I’m 6’3” so the Trex was the equivalent of being back in the womb. I’d prefer to take out the front seat and drive from the back.

Posted
3 minutes ago, Joshua Gregg said:

Am I the only one who wasnt given a loaner and told to keep driving it ?

I was given back my truck and told not to use the app. 

Posted (edited)

Glad I found this series of conversations.  Own a 2019 Sierra Denali brought my truck in for a simple oil change they said hey have some recalls to preform we will do those at the same time.  It has been a nightmare ever since. The truck has about 20,000 miles on it and owned for a year absolutely no issues with it until they performed the recalls.  I picked it up after oil change and recalls completed drove about an hour.  I was driving about 70 mph on a busy road and dashboard lit up like a Christmas tree - all the same indications that everyone else is noting, I had no brakes, completely press all the way down to the floor, no way of stopping:

 

Brake System Failure 62 MPH top speed

Service ESC

Service Steering Assist

Service Assist is Reduced Drive with Care


Luckily I coasted onto an off ramp able to reduce speed without hitting anyone.  Shut the truck off and restarted and it worked.  Drove straight back to dealership left it there.  They called the next day indicated something with the front camera was reading that I had been in a collision and it was malfunctioning.  Waited three weeks for the “part” to replace the front camera, they tested and drove the vehicle, called us for pick up.  Picked up the vehicle this week, dealership indicated all in working condition.  Drove the truck again for approximately one hour and same thing happened, no brakes, flashing dash and also this time the truck shut off numerous times.  Needless to say not happy called the dealership once again.  Truck back to the dealership, they replaced the main wire harness, called said it was good to go, they drove it and tested it all ready!  Picked up the truck yesterday drove for about another hour.  On my way home with my children in the car the same error codes lit up the dash and I had no brakes once again, I am beyond appalled at this point.  The dealership has no clue how to fix it,  I am concerned for the safety of myself and my family when driving this overpriced vehicle and further more I never had one issue until they messed with it.  The truck is sitting back at the dealership with no end in sight as I am reading all the threads available.  My advice DO NOT perform the recall update if you want your truck in working condition unless you already have experienced issues.

Edited by Denali2019junk
Posted

Stopped by the dealer this morning. They have a bulletin that came out yesterday saying to not use the app as apparently that can trigger these issues. Leaving It with them for the week while I’m away on vacation...If these issues persist I’ll be looking for my 3rd new truck in as many years, and it will not be a GM. Truck only has 18000 KM on it...I’ve had it in for some warranty work on a monthly basis it seems. This is getting old.

Posted

I'm with you Mhugg226. I was also told about the app., not to use it. I've had my Silverado 1500 for about a month, since then they've replaced the temperature control knobs. I bought the truck, the next day hopped in, started it, and the temp control knobs didn't work, you'd turn the dial, but the temp didn't change. well that sucked.. The dealer told me I can use the info screen to adjust temp. Also, the back gate wouldn't click shut. also, my gear shift lever hangs like a loose noodle, measured play is over an inch. so sloppy. I can go on. and on. actually I still love the truck and I could have lived with all these issues. but I cannot live with or continue to own this vehicle when the brakes keep failing and the truck careens out onto the street in front of my house.

Posted

I need to answer denail2019junk. It is important for all reading this post to know that as with Mr. denail2019junk, my brake failures did not start occurring until they "addressed the recall". after that, look out. I'd suggest to al other gm truck owners to forego the recall, or at least ask gm before getting it "addressed".

Posted (edited)
 

I was given back my truck and told not to use the app. 

Has it happened again since? Both times my 2019 LTZ did it, was when i used my phone to start the truck. Never had an issue with my app starting the truck until the dealing performed the brake recall. Been driving a loaner truck for 3 weeks!

Edited by RadCopperND
Adding more info
Posted
39 minutes ago, RadCopperND said:

Has it happened again since? Both times my 2019 LTZ did it, was when i used my phone to start the truck. Never had an issue with my app starting the truck until the dealing performed the brake recall. Been driving a loaner truck for 3 weeks!

I think I would be okay not using the app if they could pinpoint that as the problem, but only for a certain amount of time, and I would of course expect credit back for not being able to use the functionality I pay for.

 

Bottom line - Chevy needs to get this fixed in a hurry.  Saying don't use a feature of the $67K truck you bought because it could cause you to lose all braking control is 100% inexcusable.

 

I'm starting to get curious.  Are we in a minority here, or are there thousands others out there that just don't know about this forum and are having this issue?

Posted
5 hours ago, DenaliDonkey said:

Oh I had the Trex and the Equinox over the past few weeks as well. I’m 6’3” so the Trex was the equivalent of being back in the womb. I’d prefer to take out the front seat and drive from the back.

Have you tried the new Blazer?

Posted

To answer JAshworth03 , my dealership said there was one other owner with the brake issue. I'm sorry, I don't believe him. I am not trusting of anything I am told at an auto dealership, be it while buying a new car or whilst it's in service. Just a lot of bad experiences, they lie.

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

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...