Jump to content

Recommended Posts

Posted
16 minutes ago, newdude said:

 

 

They shouldn't be doing that until its listed as open.  If its incomplete, they can't do the recall and shouldn't be calling.  They can see right in GM's system if its open or not.  My guess is they are just using their dealer manifest list and not actually checking to see if the recall is open.  

 

 

 

PM sent.  Should be two letters.  One informing you of it being "incomplete" and may or may not describe the fix, and then a second letter that's along the lines of you can schedule the inspection to be done or if you fall under the other recall version where its just replace the engine.  

I'm not sure how they determine your place in line. I have only received the 1st letter at this point, and my (2021) vin is at the start of the recall. You would think I would have been contacted. Oh well I have a couple of 2Kmile+ trips coming up I I'll see what happens!

Posted
1 hour ago, WeGone said:

I'm not sure how they determine your place in line. I have only received the 1st letter at this point, and my (2021) vin is at the start of the recall. You would think I would have been contacted. Oh well I have a couple of 2Kmile+ trips coming up I I'll see what happens!

I wouldn’t worry unless I was pulling a camper. If that’s the case maybe a backup plan is in order. 

Posted
On 7/26/2025 at 10:10 PM, MrLeadFoot said:

So sorry to hear this, but it figures. It's so disappointing what's happened to GM. They're just lousy at making these trucks comfortable to drive. It almost seems like they think gadgets and amenities make up for lack of ergonomics, comfort and noise. I know it's a different chassis, but my 2000 Suburban was SO much more comfortable than my 22 Sierra Denali. And, that Suburban gave me no major problems, although it did drink oil. But, even so, I sold it with 235k miles on it, and the buyer was thrilled at the condition of it. All my friends had older trucks that, even though they weren't as luxurious as the new ones we all have now, felt more robust or something. I can't put a finger on it, but I find myself worrying more about something going wrong with my Sierra more than I ever did with my Suburban, my 93 Vette, and the 2001 vette i still have. I seriously wonder if Mary Barra changed the culture to one that thinks more bells and whistles means more comfort, when in reality wind noise, vibrations, and seemingly little things like visibility (aka blind spots); omission of windshield eyebrow tint (resulting in way more heat in the cabin on hot days even with the a/c on full blast); omission of rear door handle unlock buttons; cheap, noisy, pop-up fabric sunroof wind deflectors, and the like all detract from what once was the best in the business. Spending a little more time on ensuring wind noise is suppressed and addressing the vibrations alone would make for a much more comfortable ride and attract more of the luxury buyers, since these trucks are already in the luxury price range, but are nowhere near as comfortable as true luxury.

 

Ironically, my truck has been serviced at multiple dealerships, and when I voiced concern about something that isn't quite the way it's supposed to be, more than once the response has been "... it's not a Lexus." Makes me wonder if that's what they are taught to say! Darned right it's not a Lexus, because if it was, it would have been cheaper, price-wise, and designed and  assembled with better attention to detail.

 

We always boast about how things made in America are of better quality, yet you just bought a new 2025 truck from the company whose CEO said just the other day in an interview that these trucks are their strongest earners, but you have excessive wind noise? Unbelievable! 

 

(Getting off my soap box now) 

Where do I start? My maily has had pick ups since 75 (GM of course since my father and I worked in the Oshawa Truck Plant from 1965 to 2008). Somewhere along the line they went from work vehicles to glorified Impalas. The emphasis like you say has been on gizmos. I will say the Intellibeam system on my 2024 does work. That's more than what can be said about the 'auto dimming' rear view mirrors...

 

I wonder what percentage of trucks don't see a stick of lumber or bag of gardening material in the back?  

Posted
2 hours ago, revrnd said:

Where do I start? My maily has had pick ups since 75 (GM of course since my father and I worked in the Oshawa Truck Plant from 1965 to 2008). Somewhere along the line they went from work vehicles to glorified Impalas. The emphasis like you say has been on gizmos. I will say the Intellibeam system on my 2024 does work. That's more than what can be said about the 'auto dimming' rear view mirrors...

 

I wonder what percentage of trucks don't see a stick of lumber or bag of gardening material in the back?  

Probably 50-75 percent. "Gizmos" and technology aren't the problem. I'm kinda tired of that complaint by people who don't build things.

 

Planned obsolescence and excessive EPA standards are. Couple that with a complete lack of management, and this is the result. Toyota is no saint, but at least they recalled all of their vehicles under the covered range for engine replacements. It's what gm *should do*, but they would rather pay lawyers to fight it instead of acknowledging a short coming and do what's right for the long term success of the company. I can say, their handling of my situation has permanently turned me off of the brand. 

  • Sad 1
Posted (edited)

it’s apropos  to L87 issues. 
key takeaway :  

FRICTION ≠ WEAR 

use great oil analysis from @Black02Silverado

 


Lake Speeds SPEEDDIAGNOSTIX is not giving enough FTIR data for the cost. 

Edited by customboss
  • Like 1
Posted

This may be a “no ****** captain obvious” post but for what it’s worth I figured id share my experience. Took my 2024 Trailboss 6.2 in to a GMC dealer this weekend to see about trading in for a 2025 AT4 3.0. Dealer gave me a great price on the AT4 but had very little interest in my truck as a trade in. Offered me 10K below KBB. 

 

Anyone else had a similar experience? 

Posted
On 8/4/2025 at 8:48 PM, KevinTM said:

This may be a “no ****** captain obvious” post but for what it’s worth I figured id share my experience. Took my 2024 Trailboss 6.2 in to a GMC dealer this weekend to see about trading in for a 2025 AT4 3.0. Dealer gave me a great price on the AT4 but had very little interest in my truck as a trade in. Offered me 10K below KBB. 

 

Anyone else had a similar experience? 

I received a competitive trade value for my 2023 when I got my 2025 a few months ago. 

Posted (edited)
On 8/4/2025 at 8:48 PM, KevinTM said:

This may be a “no ****** captain obvious” post but for what it’s worth I figured id share my experience. Took my 2024 Trailboss 6.2 in to a GMC dealer this weekend to see about trading in for a 2025 AT4 3.0. Dealer gave me a great price on the AT4 but had very little interest in my truck as a trade in. Offered me 10K below KBB. 

 

Anyone else had a similar experience? 

 Was offed $32k for my 21 Z71 LTZ 6.2 10 speed with all options still like new 16k miles.......

Edited by WeGone
  • 2 weeks later...
Posted

Just updating from the field.  This is the one I wrote about on July 27th, our "first victim" of the recall.  Engine is coming out, all the parts are in and ready to go for assembly time. 

 

On another sad note, we just had another victim get towed in.  2023 Denali with 71k miles.  It runs, albeit poorly and does have the P0016 code set.  So that is getting an engine now as well.  

 

IMG_3156.thumb.JPG.38297ee4af40fa3922280347557decf8.JPG

 

 

 

  • Like 1
  • Thanks 1
Posted

I thought I read that the engine swap was a cab off procedure.

Posted (edited)
On 8/14/2025 at 2:20 PM, newdude said:

Just updating from the field.  This is the one I wrote about on July 27th, our "first victim" of the recall.  Engine is coming out, all the parts are in and ready to go for assembly time. 

 

On another sad note, we just had another victim get towed in.  2023 Denali with 71k miles.  It runs, albeit poorly and does have the P0016 code set.  So that is getting an engine now as well.  

 

IMG_3156.thumb.JPG.38297ee4af40fa3922280347557decf8.JPG

 

 

 

Thanks for updating us.

 

Have you heard of ANY engine replacements at ANY dealership based on a failed test, that was not an engine that had already broken down or developed obvious problems?

Edited by MrLeadFoot
Posted

I had the pico test done yesterday on my 22 refreshed 6.2 Denali. it passed and it got the oil change and cap. 30000 miles on truck. I've had no problems with the truck to date.

Posted
19 hours ago, MrLeadFoot said:

Thanks for updating us.

 

Have you heard of ANY engine replacements at ANY dealership based on a failed test, that was not an engine that had already broken down or developed obvious problems?

 

 

We've yet to run into one that ran but failed the test.  Its so far been passed the test or towed in broken.  

Posted

My gut says if it runs it's going to pass.

They aren't going to put a new engine in if it still runs.

Go ahead and put the 0w40 in it now. I did a couple of months ago and im still waiting for the test.

Posted (edited)
1 hour ago, dieselfan1 said:

My gut says if it runs it's going to pass.

They aren't going to put a new engine in if it still runs.

Yeah, I'm kind of suspecting that the test might very well be just their way of placating the NHTSA. I hate to be morbid, but it's possible that someone will have to die from this problem before they get serious.

Edited by MrLeadFoot

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