Jump to content

Recommended Posts

Posted

We have a 2016 Yukon 6.2L which developed a rattle at approximately 60k miles. Initially I believed the source of the rattle was a heat shield, but everything seems to be tight. It has been to the dealer twice and no progress has been made to resolve the issue. The first time they dismissed the problem and called it "normal" and the second time they believe it's a broken baffle weld in the muffler. What do you think? Thanks in advance

 

Video with several angles from under the vehicle demonstrating the issue. The problem only surfaces when the vehicle inters v4 mode. Also, the rattle is so loud it is picked up by the Knock Sensors and it pulling timing. Scan performed with HP Tuners VCM Scanner.

 

Posted

Have you tried some wire or zip ties to hold the exhaust flapper open to see if the sound changes??

 

As for the knock, I always see knock on these trucks even without a rattle. It's worse if someone doesn't run 91+ octane like they are suppose to in a 6.2. Even the 5.3's on 87 octane knock worse than when on 89+.

Posted

Thanks for the response.

 

Have I tested the flapper, yes. I used a piece of wire and tested both open and closed. Same results.

 

The knock is only recorded when in 4v mode. I am monitoring PID - Displacement on Demand Request and as soon as it flips to YES, the knocking starts. It's pulling about 4 degrees. While running in v8 mode there is no knock.

 

image.thumb.png.9f9729f462c1caaf3bc913c86ba5f481.png

Posted

Beats me. Anyway I look at it tells me that the engine needs to be opened up and that's expensive.

 

Turning off the DoD is cheap and would stop all these problems.

  • Like 1
  • 4 weeks later...
Posted

From the first two viewing angles it almost sounds like your driveshaft was installed upside down. Common mistake, but you may have already checked that out. 
The last viewpoint makes me wonder if you have something going on in, above, around the frame area near the body. Are you running with a spare tire hanging in the rear? Have you checked up in that area to see if you can hear anything. Tried using a compressor with an air wand to see if you can duplicate the sound while parked. Could you have part of your “honeycomb” rattling around inside the exhaust (a piece broken off from inside the cat)? I’m just pulling at straws here to throw ideas out there of similar things I’ve found. 
Originally I would have thought the same thing you did...a loose heat shield. Let us know if you ever found the problem. 

  • 2 months later...
  • 1 year later...
Posted

Did you ever figure out the issue? Having the same trouble with my 2015 Denali. Was told it was the spring valve on the exhaust, got that taken off and still have the same noise. It’s driving me crazy at this point.   

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

    • 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.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...