Jump to content

Recommended Posts

Posted

Has anyone tried to adjust the rear glass yet with ant success

I adjusted the lift gate stops and applied pressure to the glass while the vehicle was being driven at the sweet spot speeds. Not an issue, at least for me.

 

One thing I have noticed that others have early on in this thread is that it seems to have gotten worse with the colder temperatures. We're hovering around the freezing mark these days and it feels like the booming is worse.

 

IMHO, the booming is caused by vibrations in the rear drivetrain. It's the same boom sound that one can hear when driving slowly over expansion joints, curbs or gravel roads - only repeated and only at two speed ranges.

Posted (edited)

Has anyone tried to adjust the rear glass yet with ant success

 

my rear glass is super tight....and to confirm this, there's no wind noise around glass when moving. And yes I'm dealing with the horrible buffeting/pressure issue.

Edited by ajs800
Posted

I adjusted the lift gate stops and applied pressure to the glass while the vehicle was being driven at the sweet spot speeds. Not an issue, at least for me.

 

One thing I have noticed that others have early on in this thread is that it seems to have gotten worse with the colder temperatures. We're hovering around the freezing mark these days and it feels like the booming is worse.

 

IMHO, the booming is caused by vibrations in the rear drivetrain. It's the same boom sound that one can hear when driving slowly over expansion joints, curbs or gravel roads - only repeated and only at two speed ranges.

 

If the road or, for example unbalanced tires, are inducing the booming, the colder and thus thicker shock fluid will effectively stiffen the suspension's response to sharp inputs and thus excite things like the roof more.

 

Frank

Posted

This is my first post but I have monitored this forum for the last few months. My 2016 Yukon XL Denali will be going back to the dealer tomorrow through the GM buyback process. We tried to make it work but our Yukon had vibrations and the buffeting to the point where it could not be driven except for short trips. (1800 miles in 4 months) The dealer did successfully road force the tires after going through 6 tires with numbers <5. Still had the vibrations and started the buyback process. Service and salesman were unaware of the issue till I brought it up and showed them this forum. They all felt the vibrations and buffeting. I drove roughly 8-10 other vehicles trying to find a good one only finding one that was acceptable but did not want to take a chance of future problems down the road.(wrong color interior and exterior also) These are great vehicles. It is very unfortunate that they have these issues. Dealer sales and service did go out of the way to help me. I did not have the dealer service department do anymore than the tires. I will drive my new 2016 Sierra 6.2 replacement vehicle until GM decides to reengineer the Yukon.

Posted

I adjusted the lift gate stops and applied pressure to the glass while the vehicle was being driven at the sweet spot speeds. Not an issue, at least for me.

One thing I have noticed that others have early on in this thread is that it seems to have gotten worse with the colder temperatures. We're hovering around the freezing mark these days and it feels like the booming is worse.

IMHO, the booming is caused by vibrations in the rear drivetrain. It's the same boom sound that one can hear when driving slowly over expansion joints, curbs or gravel roads - only repeated and only at two speed ranges.

I adjusted the lift gate stops and applied pressure to the glass while the vehicle was being driven at the sweet spot speeds. Not an issue, at least for me.

One thing I have noticed that others have early on in this thread is that it seems to have gotten worse with the colder temperatures. We're hovering around the freezing mark these days and it feels like the booming is worse.

IMHO, the booming is caused by vibrations in the rear drivetrain. It's the same boom sound that one can hear when driving slowly over expansion joints, curbs or gravel roads - only repeated and only at two speed ranges.

Did you do the roof test? To see if the bows came loose
Posted

Did you do the roof test? To see if the bows came loose

 

No. The dealership has road-forced balanced all 4 tires, replaced 2 and we're now waiting for a complete axle replacement. They're after the vibration which can be felt and likely measured with their scope since they approved a new axle.

Posted (edited)

Well, just got an update from the dealer. After a week of working on it to ensure that the required PI from GM was followed to the letter, the tech drove it this afternoon and the buffetting was still there at 40-45. They did say that the issue at 65-70 was gone, but that was never as bad to begin with.

 

I am so disgusted right now it is not even funny.

Edited by Zig10
Posted

Well, just got an update from the dealer. After a week of working on it to ensure that the required PI from GM was followed to the letter, the tech drove it this afternoon and the buffetting was still there at 40-45. They did say that the issue at 65-70 was gone, but that was never as bad to begin with.

I am so disgusted right now it is not even funny.

Did that include the roof ?
Posted

Yup.

 

That drone at 45MPH is likely due to the engine's control strategy that upshifts to the tallest gear, switches to V4 mode, and lugs the engine at 1000-1050RPM. Fuel economy is outstanding but the lugging engine makes the vehicle drone. I do not think this is an exhaust issue. I think GM will need to design a more insulative engine mount or change the strategy to shift up a gear and the engine spinning a little faster.

 

Frank

Posted

The drone was a separate sound, and one I am familiar and ok with. One of my business partners bought a new Tahoe about 2 days before I got my Yukon. I drove his against mine back-to-back to see if the buffetting was there. His was fine. There was some drone in 4 cylinder mode, but no pressure sensation at all.

Posted

The drone was a separate sound, and one I am familiar and ok with. One of my business partners bought a new Tahoe about 2 days before I got my Yukon. I drove his against mine back-to-back to see if the buffetting was there. His was fine. There was some drone in 4 cylinder mode, but no pressure sensation at all.

When test driving how long would it take before you notice this problem, is it right away?

Posted

When test driving how long would it take before you notice this problem, is it right away?

I'd notice it right away too, at the sweet spot speeds and driving over expansion joints. Ditto on the exhaust drone - that's a distinctly different tone which isn't annoying as hell.

 

 

If the booming isn't across all vehicles, it's less likely a design flaw and instead defective part(s) or improperly installed parts. Somebody must be able to solve this!

 

I'd love to be able to visually inspect the underside of the truck while it runs at ~65mph.

Posted

When test driving how long would it take before you notice this problem, is it right away?

Within about 10 seconds of hitting 40-45. Normally it's jsu an annoyance, but if you have a cold with any kind of sinus pressure it becomes pain-inducing in your ears...or at least in mine. My family has been passing around a head cold for the past 20 days or so, and I haven't been able to drive that car for more than a 5 minute trip to the store and back.

 

The loaner they gave me is a base-model V6 Sierra SLE pickup. It drives pretty poorly and doesn't have enough power to get out of it's own way, but no pressure issues of vibrations of any kind.

 

Sad that I am making payments on a $70k vehicle, stuck driving a $45k vehicle, and somehow this is a better driving experience. How in the hell does GM think that this is acceptable in any way?

Posted

I'd notice it right away too, at the sweet spot speeds and driving over expansion joints. Ditto on the exhaust drone - that's a distinctly different tone which isn't annoying as hell.

 

 

If the booming isn't across all vehicles, it's less likely a design flaw and instead defective part(s) or improperly installed parts. Somebody must be able to solve this!

 

I'd love to be able to visually inspect the underside of the truck while it runs at ~65mph.

Anybody got a GoPro and a good magnet?

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,691 Guests (See full list)


  • Latest Articles

  • Posts

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