Jump to content

Seized AFM lifter round 3

Mathew Kirsch
 Share

Recommended Posts

Mathew Kirsch Enthusiast

Mathew Kirsch

Posted
Posted

Just paid to have all 16 lifters replaced in my 2015 Silverado 1500 5.3L with 141,000miles, because one seized in the #3 cylinder.

 

This happened the first time back at around 103,000 give or take.

 

Got it back, ran mint. For about 500 miles.

 

Last Saturday I was 150 miles from home, and had just gotten up to highway speed on the expressway when something caught my eye. The traction control light was on, then I saw the check engine light blinking. Sure enough when I got into it even a little, it would start shaking and squeaking. 

 

The mechanic who fixed it came over yesterday and scanned it. Says it's misfiring on #1. So maybe not another seized lifter? Sure feels like one though...

 

'Bout ready to send the truck to the crusher, and swear off GM products for life.

  • Sad 3
diyer2 Senior Enthusiast

diyer2

Posted
Posted

I understand but the install may have something to do with it. 

  • Like 2
16LT4 Enthusiast

16LT4

Posted
Posted (edited)

Plenty of reasons for misfires, I'm assuming the ignition system was ruled out? Intake valve CBU?

Edited by 16LT4
  • Like 1
Mathew Kirsch Enthusiast

Mathew Kirsch

Posted
  • Author
Posted
43 minutes ago, 16LT4 said:

Plenty of reasons for misfires, I'm assuming the ignition system was ruled out? Intake valve CBU?

 

It happened Saturday. I didn't get home until 7PM. Sunday was Sunday. Yesterday was a holiday. 

 

Hopefully he's able to take a look at it today.

 

 

Snowcamo Senior Enthusiast

Snowcamo

Posted
Posted

Lifter, cam pushrods need to be replaced at the same time. Not one or the other. Check the ignition coil to plug wire connections as they corrode over time.

  • Like 1
mjm-1957 Enthusiast

mjm-1957

Posted
Posted

The squeaking is never good, could be a roller let go on one of the lifters and is grinding down the cam lobe.

  • Like 1
customboss Senior Enthusiast

customboss

Posted
Posted
2 hours ago, 16LT4 said:

Plenty of reasons for misfires, I'm assuming the ignition system was ruled out? Intake valve CBU?

CBU = internet for carbon build up........gawd that had me wondering what the heck was......cluster bombs etc.....LOL  

  • Haha 1
pokismoki Senior Enthusiast

pokismoki

Posted
Posted (edited)

even the Dodge rocker arms have issues, no matter what truck you buy these days they are all ******! too many gizmos and features..   better off going back to old SB1 motor with carb and mechanical fuel pump and digital ignition. 

 

 

if you stripped off all the emmissions stuff the 5.3 would be awsome again

 

 

Edited by pokismoki
  • Thanks 1
16LT4 Enthusiast

16LT4

Posted
Posted
21 hours ago, customboss said:

CBU = internet for carbon build up........gawd that had me wondering what the heck was......cluster bombs etc.....LOL  

 

Seems to be a bit of a concern for some DI engines in these trucks, but is definitely a concern for Ford Ecoboosts, BMW N54/N55 and VW/Audi EA888 engines.  Just another potential cause of misfires, especially at the OP's 140k+ miles.

 

 

  • Like 1
customboss Senior Enthusiast

customboss

Posted
Posted
44 minutes ago, 16LT4 said:

 

Seems to be a bit of a concern for some DI engines in these trucks, but is definitely a concern for Ford Ecoboosts, BMW N54/N55 and VW/Audi EA888 engines.  Just another potential cause of misfires, especially at the OP's 140k+ miles.

 

 

Absolutely!  An issue that I worked earnestly on before retirement. Starting with Toyota 3.0 V6's in early 2000 and ended in HD DI diesel engines carbon cleanup in-situ. 

  • Like 1
Mathew Kirsch Enthusiast

Mathew Kirsch

Posted
  • Author
Posted

The mechanic had good news for me. Valve train is OK. Cam is OK.

 

#1 fuel injector is either stuck open or not firing at all. He thinks stuck open because the #1 plug was "washed clean."

 

This is the second time the #1 injector has failed. Happened very early on when the truck only had a couple thousand miles on it.

  • Like 1
diyer2 Senior Enthusiast

diyer2

Posted
Posted

 

Great news. 

A suggestion, shorter OCI's maybe change oil brand. 

 

  • Like 1
KARNUT Senior Enthusiast

KARNUT

Posted
Posted

I just noticed there was 2 threads on the same truck. Most people who want to be helpful are going to ask questions. Cost analysis, how many miles, original owner, shape of vehicle, only vehicle. And most important who's doing the work. At different stages in my life I would do things differently. Early on I would do the work myself. Rebuild the top end myself or salvage engine. Probably my only vehicle needing to fly. Staged two fix good enough to trade in. Staged three in my 40s screw it trade in running bad take the hit. In my 50s with the low mileage 6.0 truck available. Pull the 6.0 modify it and the transmission install in the 2015. The parts to do all that is available. In the rust belt my whole out look would be different. I’d have a Subaru for bad weather. My truck would be in the garage it would be cherry. The only that would be original would be the block.. People forget we’re all different, live in different parts of the country. 

  • Like 1
16LT4 Enthusiast

16LT4

Posted
Posted
3 hours ago, Mathew Kirsch said:

The mechanic had good news for me. Valve train is OK. Cam is OK.

 

#1 fuel injector is either stuck open or not firing at all. He thinks stuck open because the #1 plug was "washed clean."

 

This is the second time the #1 injector has failed. Happened very early on when the truck only had a couple thousand miles on it.

 

And the resulting fuel dilution of the oil is probably at least partially at fault for your repeated lifter/valvetrain issues.  Methinks the crux of the issue has been stumbled upon...

  • Thanks 1
diyer2 Senior Enthusiast

diyer2

Posted
Posted

How often did you change the oil and filter? 

What oil and filter?

  • Like 2

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