Jump to content

Lifter issue: TSB PIP5776E - published June 18

1500guy
 Share

Recommended Posts

1500guy Enthusiast

1500guy

Posted
Posted (edited)

Another victim here, 3000 miles on my sierra I am almost positive the lifters are shot. 
 

i’m 400 miles from my dealership. OnStar says they’ll tow it to the closest one, and can’t help me with my family and all my other junk that I have with me on vacation. 
 

heard there is a brand new tsb: PIP5776E which will cover all lifters on failure @ < 8000 miles.  Does anyone have access to this tsb?  I can’t find it online yet. Apparently published June 18

Edited by 1500guy
  • Replies 91
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

CamGTP
CamGTP

In all reality it's not a major repair. Things just have to come apart to reach the lifters.   In total they replace a few gaskets and bolts. Them being 2 head gaskets, head bolt kit, possib

Firehawk99
Firehawk99

The first 7 digits on mine were T221077. Which means T-Tonawanda, 2-2nd shift, 21-2021, 077- the 77th day of the calander year. Which was 3-18-21.

Firehawk99
Firehawk99

Any trucks built after 3-4-21 should be fine. That is the break point.

Posted Images

sohccammer427 New Member

sohccammer427

Posted
Posted (edited)

1st post guys.   Just trying to see if this lifter issue is just hit and miss or something more.   Have a 2021 Trail Boss 5.3l that I've finalized a deal on working on-line.  Was just about to go for it but I read tsb PIP5776E and it mentioned VIN build date range 9/1/2020 thru 3/31/21.  The build date of this truck is 02/2021.

 

Not sure I can being myself to drop 60k on a fully equipped TB with a potential issue that GM is acknowledging. Maybe I'm being to cautious, but I think I'm going to wait until year end and see if the quality issue has been resolved. 

Edited by sohccammer427
spell
Transient Senior Enthusiast

Transient

Posted
Posted
On 7/7/2021 at 11:42 AM, sohccammer427 said:

1st post guys.   Just trying to see if this lifter issue is just hit and miss or something more.   Have a 2021 Trail Boss 5.3l that I've finalized a deal on working on-line.  Was just about to go for it but I read tsb PIP5776E and it mentioned VIN build date range 9/1/2020 thru 3/31/21.  The build date of this truck is 02/2021.

 

Not sure I can being myself to drop 60k on a fully equipped TB with a potential issue that GM is acknowledging. Maybe I'm being to cautious, but I think I'm going to wait until year end and see if the quality issue has been resolved. 

Any truck you buy, regardless of make, will have problems.  It's just the way it is.  It's rather have a manufacturer acknowledge the problem instead of try to hide or avoid it.  They question really is, how willing are you to take on a specific makes problems?

  • 4 weeks later...
Firehawk99 Enthusiast

Firehawk99

Posted
Posted (edited)
1 minute ago, jayoco said:

How do you know this?

I work for GM at the Tonawanda engine plant. We build the 4.3, 5.3, 6.2 and the 6.6.

Edited by Firehawk99
  • Like 1
jayoco Enthusiast

jayoco

Posted
Posted
3 minutes ago, Firehawk99 said:

I work for GM at the Tonawanda engine plant. We build the 4.3, 5.3, 6.2 and the 6.6.

Well that's great to know.  I've got two '21's.  A Silverado and my wife's Denali with the 6.2.  I assume the Denali (build date 6/21) will be fine.  Fingers crossed on the Silverado.

tanner benjamin New Member

tanner benjamin

Posted
Posted

First post, my 2021 high country is at the dealership with the bad lifters. I have 8360 miles so they will only repair the bad side.  How upset should I be? Pretty sure with the way they are treating me this will be my last GM.  If they acknowledged bad lifters, why would they not just replace all of them?  I am waiting for a manager a customer service to call me back,  sucks when you can't trust your brand new ride.

jayoco Enthusiast

jayoco

Posted
Posted
2 minutes ago, tanner benjamin said:

First post, my 2021 high country is at the dealership with the bad lifters. I have 8360 miles so they will only repair the bad side.  How upset should I be? Pretty sure with the way they are treating me this will be my last GM.  If they acknowledged bad lifters, why would they not just replace all of them?  I am waiting for a manager a customer service to call me back,  sucks when you can't trust your brand new ride.

What is your build date?

jayoco Enthusiast

jayoco

Posted
Posted
2 hours ago, Firehawk99 said:

Any trucks built after 3-4-21 should be fine. That is the break point.

One more question if I may...

 

Is that engine build date or vehicle build date?  is there much of a delay between the time you guys build them and the time they are installed at the plant in Arlington?  I appreciate the response. 

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

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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