Jump to content

Recommended Posts

Posted (edited)

I would demand a full market retail price. Or a new loaner till  its fixed!

Edited by ram1067
Posted

My understanding was that anything over 8500 not both sides. Mine failed @ 6500 and my dealer did both sides! Possibly because of my 30yr history which them…… I don’t understand why a dealer would bring in a vehicle spend the time taking one side apart and then possibly six months down the road have to bring it back in and do the other side! Didn’t make sense to me or my dealer.  Just demand it work with the dealer. Ask to speak with area rep. 

Posted

Your dealer is asleep. About two months ago GM started replacing both banks up to 16000 miles. Mine were all replaced at 9900 miles. There is a serv8ce bulletin verifying this.

  • 1 month later...
Posted

My 2019 GMC Sierra with 5.3 had the issue with less than 10k miles. Dealer got me a loaner car for almost three weeks.

Besides replacing two lifters they replaced the wire harness to the solenoids for AFM. Truck has been running good since with 65k miles.

  • Thanks 1
Posted
On 8/24/2022 at 9:24 AM, RobZ said:

My 2019 GMC Sierra with 5.3 had the issue with less than 10k miles. Dealer got me a loaner car for almost three weeks.

Besides replacing two lifters they replaced the wire harness to the solenoids for AFM. Truck has been running good since with 65k miles.


Nice to hear from someone that had this happen and has a few miles on the engine without problems. This happened to me late last December and all of my lifters were replaced. My truck has been running great since then but I’m low mileage. How long has it been since this happened to you?

  • 2 weeks later...
Posted

i'll have to add my two cents, after 20,110 miles on my 2021 crewcab 4x4 it began "misfiring" and diagnose finally was #3 cylinder error and lifter............hopefully the fix will be forever as it is embarrassing as a chevy owner FOREVER AND EVER with 4 different 5.3 engines that this is all of a sudden happening, especially to a new one!!!

Posted
On 9/7/2022 at 6:39 PM, wb5rag said:

i'll have to add my two cents, after 20,110 miles on my 2021 crewcab 4x4 it began "misfiring" and diagnose finally was #3 cylinder error and lifter............hopefully the fix will be forever as it is embarrassing as a chevy owner FOREVER AND EVER with 4 different 5.3 engines that this is all of a sudden happening, especially to a new one!!!

 

What was your build date?

  • 1 month later...
Posted

Well I jinxed my self, 67000 miles and its back at at the dealer for #3 cylinder, lifter, piston and ring replacement.

Posted
1 hour ago, RobZ said:

Well I jinxed my self, 67000 miles and its back at at the dealer for #3 cylinder, lifter, piston and ring replacement.

Its not you its GM engineering at its finest. 

  • 3 weeks later...

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

    • 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.
    • Just don't turn the steering wheel as much?
    • Rockauto bud. I pass local stores for parts.   Findya something online. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...