Jump to content

Hitch clunk - not your typical towing / hitch / receiver question

holty

By holty
in Towing, Hauling & Hitches

Recommended Posts

holty Enthusiast

holty

Posted
Posted

Hey guys,

 

I traded in my 2014 5.3 Crew cab Sierra (leased) for a new 2016 Denali. Basically the same truck but with upgraded Denali package and 8spd trans.

 

When towing my boat (fully loaded its about 7k lbs) both trucks pulled it great. However, after braking, stopping, or slowing, upon acceleration you can hear and feel a significant "clunk" from the hitch receiver. I believe the its the receiver causing the issue. There is about a 1/2 inch of slop in the receiver. Is that normal?

 

Here is my tow setup:

 

https://www.amazon.com/gp/product/B00OKYSWWU/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

 

 

 

 

post-35122-0-48808800-1467392399_thumb.jpg

post-35122-0-48808800-1467392399_thumb.jpg

post-35122-0-48808800-1467392399_thumb.jpg

post-35122-0-48808800-1467392399_thumb.jpg

ember1205 Senior Enthusiast

ember1205

Posted
Posted

There are a few places that you could have some "slop".

 

One is between the ball and the coupler on the trailer.

 

A second is in the holes for the clevis pin in both the hitch and the receiver as well as the clevis pin being worn. Check all of these to see how much play there is.

 

A third is a difference between the outside measurements of the hitch and the inside measurements of the receiver. There are shims available to take up slop in these measurements.

 

A slight amount of slop in ALL of the areas can greatly magnify the sound and 'feel' of any of them that you would notice individually.

kstruckcountry Senior Enthusiast

kstruckcountry

Posted
Posted

Most reciever hitches I've been around have a little slop. They don't want someone with a thick powder coat on their ball mount to not be able to fit it. And since a lot of people leave their hitches in, it saves dealers from having to unsieze them.

 

Sent from my SM-G920V using Tapatalk

crankman Enthusiast

crankman

Posted
Posted

Check the brake fluid reservoir on your trailer. I had that noise recently on my tandem trailer knew it wasnt the hitch and just by accident i checked the brake fluid level it was almost bone dry. refilled it bleed the lines and its all quiet now. That GEN Y hitch looks interesting havent ever seen that one.

holty Enthusiast

holty

Posted
  • Author
Posted

Thanks for the responses guys I really appreciate it.

 

It is definitely coming from the hitch and the receiver. Where can I find those shims?

ember1205 Senior Enthusiast

ember1205

Posted
Posted

https://www.etrailer.com/Hitch-Accessories/Boone-Outdoor/93347.html

 

That's one example. Lots of folks go a much more simplistic way and drill a hole through either the bottom or side of the receiver, weld a nut to the receiver, and then thread a bolt into the nut and through the hole after installing the hitch. Tighten it down so it doesn't slop around and you're good to go.

 

Some folks swap out the clevis pin for a 5/8" Grade 8 bolt and tighten it down after installing the hitch. This also supposedly removes some of the slop.

SouthernSilveradoGuy85 Senior Enthusiast

SouthernSilveradoGuy85

Posted
Posted

Don't want to state the obvious, but make sure you're using the right size ball. Had a buddy that wasn't too familiar with towing and mentioned that there was a ton of play. I looked at it and saw they towed with the ball that's 1 size too small. Should have been the 2" and they were using the 1 7/8".

 

I saw a video on Youtube where a guy welded around the where the receiver fits into the hitch and slowly ground off until there wasn't any play lift. So he basically just added metal and then removed little by little until it was just loose enough to insert and remove but was still very tight when in the hitch. He welded the top and the sides. Just grind off the paint or powdercoat, fix the welds and then paint over.

  • 3 weeks later...
Joe592 Enthusiast

Joe592

Posted
Posted

I had the same issue and concern with my 2007 sierra pulling 32' travel trailer. I thought it was also defeating half of the weight distributing hitch. I purchased the curt HD hitch. I had at one time video of my oem setup and i could lift the ball up 1-1/2" by hand because of the slop. with the new curt hd hitch that was reduced to 1/2" or less. still hear a bit of clank back there but well worth the money. got it from etrailer good price and quick.

BigBadSierra Senior Enthusiast

BigBadSierra

Posted
Posted

I just went from a 2014 GMC Sierra AT to a 2016 Sierra AT the hitch on the new one has more play then the old truck had so there is more play.

 

I suspect it's the same issue with you.

WhineyTTwins Enthusiast

WhineyTTwins

Posted
Posted

Been there, had that. Caused by play in the receiver. You will never have a receiver that is tight enough to seal the gap because they expand and contract with temps aswell as deform (to an extremely small extent) due to load and the amount of dropor raise the hitch has. Another reason is because not every receiver is made equal so making a hitch to certain spec and expecting every single manufacturer to match it won't happen. Coatings can cause them to be thicker. You also wouldn't want a real tight hitch because rust can seize it up. Use this http://www.etrailer.com/Hitch-Accessories/Roadmaster/RM-061.html

  • 6 months later...
johnandchrisinmo Enthusiast

johnandchrisinmo

Posted
Posted

Was your old truck a 2 inch receiver and the new truck a 2 1/2 inch receiver? that would account for the half inch of slop in the receiver. They make an adapter to use your 2 inch hitch in your 2 1/2 inch receiver, it slides into your receiver then you hitch slides into it then both are pinned in as usual Not sure i that i saw one at wally world in fact.

Cowpie Senior Enthusiast

Cowpie

Posted
Posted

Get a lock down hitch clamp. It's the best thing ever.

 

https://www.amazon.com/LOCK-DOWN-Tightener-No-Wobble-Stabilizer-Carrier/dp/B015TLZXB0

 

 

Beat me to it! Yep, one of those will usually do the trick.

 

And I have to agree with John's comment... the OP mentioned 1/2" of slop. My first thought was a 2.5" receiver instead of the regular 2" receiver, but I didn't think they put the 2.5" on 1500. if they did, might have been an assembly line error or they are doing something new.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • 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   3 Members, 0 Anonymous, 1,615 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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