Jump to content

Recommended Posts

Posted
35 minutes ago, Jus Cruisin said:

25 pages.... This recall sure got the site revved up and busy. 😉

It might beat my thread at 29 pages.🤫

Posted
6 hours ago, customboss said:

casting issues = debris in the block that deposits in bearing journals etc. earlier BOOM

boring= un even pressures on bearings and rotating stock.  slighly later BOOM 

 

My take. 

 

6 hours ago, customboss said:

casting issues = debris in the block that deposits in bearing journals etc. earlier BOOM

boring= un even pressures on bearings and rotating stock.  slighly later BOOM 

 

My take. 

No argument from me here, although bad spec could also cause casting issues. Either way, as you said, fall down go boom, and case can't be re-used (or, at least, shouldn't be re-used).

 

On the other hand, according to the video above it's a not a case-related issue, it's a crank issue. But, even though the case can be used for a rebuild, it still requires a complete teardown and reassembly, which dealerships are simply not equipped to do reliably en masse. Now, the fact that GM is doing new replacements, as @newdude shared, I suspect they are not exactly positive, at least not sure, enough to gamble and put us in reman'd motors using the same case. 

 

My take. 

Posted
4 hours ago, Jus Cruisin said:

25 pages.... This recall sure got the site revved up and busy. 😉

You mean, the "world".... 

 

And, looks like you now don't have a care in the world. 😉

Posted
3 hours ago, PunchT37 said:

It might beat my thread at 29 pages.🤫

And, rightly so. This topic should stay at the top of all news until GM resolves the issue for existing owners, which I suspect may never come to fruition for a lot of us. 

Posted

I spoke with a service manager acquaintance at my local dealer and he said, GM has never replaced an engine under warranty with a re-manufactured engine. Its always been a new engine. Its typically short block if the heads and intakes system are usuable.  Its different with transmissions in that the only thing they reuse is the case, all internal parts are new. So says he, 25 yrs in GMC/Chevy/Cadillac Service.

Posted (edited)
10 hours ago, Z45 said:

I spoke with a service manager acquaintance at my local dealer and he said, GM has never replaced an engine under warranty with a re-manufactured engine. Its always been a new engine. Its typically short block if the heads and intakes system are usuable.  Its different with transmissions in that the only thing they reuse is the case, all internal parts are new. So says he, 25 yrs in GMC/Chevy/Cadillac Service.

 

 

Engines can be reman or new.  Depends on the year of the vehicle mostly.  Service guy was blowing some smoke there.  

 

GM does not sell short blocks anymore for production vehicles.  Long block only.  

 

2016-2019 model year window for example.  You have a 6.2 and it quits after 90k miles.  GM offers two L86 6.2s at the moment.  One p/n is remanufactured, the other is a brand new engine.  The 5.3 for that year range?  Only option is reman.  

 

The 6.2 L87 for 2019-2021 model year, that p/n is a reman.  

 

Many of the engines for 2020+up vehicles so like 1.2 turbo, 1.3 turbo, 2.7 turbo, 3.0 Duramax, etc., those are new.  

 

4.3 V6 for 2019-2021 is available as a reman or new.  

 

If it is new or reman'd, the GM EPC is quite clear in labeling such.  

 

The recall 6.2?  Those that get replacement engines they will be a 100% new engine, not a reman.  

Edited by newdude
  • Thanks 3
Posted
16 hours ago, Z45 said:

I spoke with a service manager acquaintance at my local dealer and he said, GM has never replaced an engine under warranty with a re-manufactured engine. Its always been a new engine. Its typically short block if the heads and intakes system are usuable.  Its different with transmissions in that the only thing they reuse is the case, all internal parts are new. So says he, 25 yrs in GMC/Chevy/Cadillac Service.

In my specific case my 2021 6.2 (Built in February, not part of the recall VIN Sequence in the recall) engine was replaced with a reman. when the engine failed at 26000 miles. So, I can report that they do not always replace with a new engine.

Posted

Yeah that ultra thin oil doesn't cut it at low RPM and load....exactly what i'm doing pulling  a heavy trailer with my 5.3. Si, i'm puttin in the molasses too!😆

  • Like 2
Posted (edited)

Hmmm, looks like thin oil strikes again?

 

 

The dude slams GM. But, don`t most all recalls start out life as TSB`s?

Edited by PunchT37
Posted
18 minutes ago, PunchT37 said:

But, don`t most all recalls start out life as TSB`s?

Nope

Posted
1 hour ago, PunchT37 said:

Hmmm, looks like thin oil strikes again?

 

 

The dude slams GM. But, don`t most all recalls start out life as TSB`s?

No. Pictures show damage on cams that look like 3rd party abrasive damage or metallurgy issues. 

Posted

One of our guys did 3 in stock used 6.2 vehicles for the recall using the Picoscope.  So far we are 3 for 3 that passed and are getting 0w40.  2022 Tahoe, 2023 Yukon and a 2024 Silverado 1500.  

Posted (edited)
39 minutes ago, newdude said:

One of our guys did 3 in stock used 6.2 vehicles for the recall using the Picoscope.  So far we are 3 for 3 that passed and are getting 0w40.  2022 Tahoe, 2023 Yukon and a 2024 Silverado 1500.  

I understand that these are on the lot for sale, but did an extended warranty get assigned to their VINs? I suspect not, even if GM does end up providing warranties to existing owners (which I am still doubtful about), because GM might want to help enable dealers to sell warranties when/if these types of vehicles get sold.

 

Additionally, I'd like to know if the pico test ever does report a test failure, or if this is all smoke and mirrors, so I appreciate you providing these reports.

Edited by MrLeadFoot
  • Like 1
Posted

So my truck engine not in the recall, bwoodsmn's engine not in the recall, both blew up, and I know one guy with a 5.3 that the bottom end went out at 100,000 miles, GM has a big problem on their hands with their engines going out way above this current recall which is only for the 6.2s.  Maybe the percentage of vehicles giving trouble is low, but....

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   3 Members, 0 Anonymous, 2,122 Guests (See full list)


  • Latest Articles

  • Posts

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

  • Popular Contributors

×
×
  • Create New...