Jump to content

Recommended Posts

Posted (edited)

my truck was throwing a code and it was really sluggish. got new cats installed and it was back to the normal slow 4.8 feel

 

also if you get new cats, have a new fuel filter put on

Edited by KMGZ400
Posted

+1,!! A fresh fuel filter is always a good start..And regardless if it was the problem or not..Its new and one less thing to worry about!

But the cats are important..Ive seen cats after 230,000 miles and they looked new. Also seen cats with 50,000 miles and 3/4 clogged,

Many things can get them shitty, Bad fuel, exhaust leak for a long period of time,etc...

Posted

My truck's a 2wd, so it's not suck in 4 hi.

 

I changed the fuel filter a few months ago, but I'll throw a new one on this weekend for good measure.

 

My next steps are:

1. Change the fuel filter again.

2. Try to find a good mechanic with a data logger/live data tool to see what's going on. If I can't find that, then:

3. Get the cats pressure tested

4. If the cats look good, change out the O2 sensors

 

This may take a week or so, but I'll reply back as soon as I make progress. Thanks for everyone's help!

 

On that note, do any of you guys know a good mechanic in the Austin/Round Rock, TX area?

  • 5 months later...
Posted

Digging this one back up from the grave because it is FINALLY SOLVED!!! The problem was a bad catalytic converter. I never had a check engine light or any codes. I heard some rattling one day, so I tapped on the driver side cat with a hammer, and it sounded like the thing was full of BBs. Replaced the cats, and my Yukon is running like a champ now.

  • Like 2
  • 7 years later...
Posted

Old post but I’m having the same issue as you 

@Juice75 I changed fuel pump fuel filter plugs and new wires changed tps and it just feels like Im driving up a steep hill 

going up hill is ridiculous i uave to floor it to stay at speed limit 

and same thing if I let off the gas it slows me down as if I’m pressing the breaks any update? Did you ever find a fix?

Posted
On 1/6/2021 at 9:45 PM, Slow4.8 silverado said:

Old post but I’m having the same issue as you 

@Juice75 I changed fuel pump fuel filter plugs and new wires changed tps and it just feels like Im driving up a steep hill 

going up hill is ridiculous i uave to floor it to stay at speed limit 

and same thing if I let off the gas it slows me down as if I’m pressing the breaks any update? Did you ever find a fix?

his fix was a bad cat. He did extensive replacement and his issue was ungoing for a long time.  

  • 1 year later...
Posted

Same exact issue with my 05 XL.. but would that cause handling to be a little rough at times? I'm beginning to think my Yuki has bipolar. Lol. drives fine on one trip, then next trip, everything feels off. Then back to riding normal. Im driving my husband nuts with it. he'll test drive it and says he doesn't feel anything. 

  • Like 1
Posted
21 hours ago, YukiTheYukon said:

Same exact issue with my 05 XL.. but would that cause handling to be a little rough at times? I'm beginning to think my Yuki has bipolar. Lol. drives fine on one trip, then next trip, everything feels off. Then back to riding normal. Im driving my husband nuts with it. he'll test drive it and says he doesn't feel anything. 

 

When was the suspension rebuilt last and what brand of parts were used?  The truck is 17 now, almost old enough to vote!  Rebuilt mine at 13 and she drives like new.

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...