Jump to content

Recommended Posts

Posted

Hi everyone, I’m new to this forum and I just want to get a good idea of how many miles everyone’s getting out of there 14-18 5.3’s / 6L80 combos and what type of maintenance y’all are doing to get there. I have 90,****** now on my 2016. I follow my service schedule to a T. Trans fluid and filter every 22,500 and engine oil every 4000. What’s everyone else do to get there trucks up to high mileage 

Posted (edited)

Changing fluids is a pet peeve of mine. You're doing it right IMO. Better to change fluids more than not. 👏

Edited by diyer2
  • Thanks 1
Posted

I'd say stick with what you're doing, since you're comfortable with it. No need to decrease intervals

  • Thanks 1
Posted

I am just learning myself as I bought my son's 2016 with only 33k on it.  I would definitely go with an AFM delete either with a tuner or the Range plug in unit. I just stopped at a transmission shop as well because I have questions about the trans cooler. They will bypass the thermal bypass for the trans cooler (factory set up is for the trans fluid to bypass the cooler until it is 194 degrees) and change the tune on the trans to improve shift points and move the lockup between 4th and 5th gear instead of 2nd gear. They will also do the AFM delete for me.  they want $500 for all this and it is probably worth it because the Range plug in is $200 anyways.  I am big on preventative and it shows because I am just changing vehicles from the "91 GMC that I bought in 1992 :)

Posted

That’s awesome about the 91 GM jack, I have a range and have had it from 50,****** miles I like it and it does the job, I also would consider a catch can.I have one from OCS and it catches a ton of oil. Also look at exactly what there doing with the lock up in the tuning as I have heard the getting rid of it all together in 2, 3, and 4 is pretty much just as bad as it engaging all the time like it does stock

Posted
1 hour ago, Jack Buys said:

AFM delete either with a tuner or the Range plug in unit

This is not a delete. Both methods just turn off the function of AFM. You still have the same parts in the engine.

 

A true delete is tearing open the engine and replacing parts with non AFM versions. 

  • Like 1
Posted
11 hours ago, JimCost2014 said:

This is not a delete. Both methods just turn off the function of AFM. You still have the same parts in the engine.

 

A true delete is tearing open the engine and replacing parts with non AFM versions. 

Very true but a good first step is to eliminate it electronically because that needs to be done anyways. When I am retired in a year or two, I will pull the heads and replace the cam, lifters, etc. It's always been my theory that pistons and rods just aren't along for the ride, they need to all work equally for an engine to survive.

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

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