Jump to content

Recommended Posts

Posted (edited)

I use a 2" hitch along with the adapter sleeve in the 2.5" receiver.  What anti-rattle do I need?  One for 2" hitch or one for 2.5" hitch? Any recommendations?

IMG_4096.jpeg

Edited by AndrewF
Posted

Get a 2.5” hitch. Sell current one. 
 

or wrap it with some electric tape and jam it in there. I did that in the past and it worked for a long time. 

  • Like 3
Posted

Is it rattling when the trailer is hitched to the truck or not?

 

If its the latter, just remove it when you dont need it.

 

Personally Ive just gone w/ 2 1/2" drawbars over the years. 

  • Like 1
Posted
2 hours ago, revrnd said:

Is it rattling when the trailer is hitched to the truck or not?

 

If its the latter, just remove it when you dont need it.

 

Personally Ive just gone w/ 2 1/2" drawbars over the years. 

It’s just when it’s not hitched to a trailer on rougher roads so it’s not that big of a deal. Sadly I bought this hitch a few months before I bought the truck, I still have another truck I occasional swap the hitch to with a 2” receiver so probably won’t upgrade yet.
 

Maybe I will cut some sheet metal and try to shim it. Or if it fails go to electrical tape

  • Like 1
Posted

Once I bought this truck, I went with 2.5" on everything. I changed out the shank on my WDH to 2.5" as well...that thing is heavy!

  • Like 3
Posted
15 minutes ago, johnnyquick said:

Electric or Duct tape, save the $$ for the work the truck will need all to soon.😂

Boy aren't you a ray of sunshine...

  • Haha 1
Posted
4 minutes ago, revrnd said:

Boy aren't you a ray of sunshine...

LOL, I know it seems that way but they definitely are not like buying a 2014 or so brand new.

GM themselves finally see it with engine and transmission recalls taking months to resolve it is a sad sight.

Posted
5 hours ago, rdonarski said:

I always remove it when It’s not in use. My shins prefer it.

First thing i do when I get to my campsite is remove it. I welded on a 2 1/2" receiver on my trailer to store it.

  • Like 1
Posted

I guess what’s another $300 after spending $55k 😅

 

Sounds like consensus is that with the 2.5” hitch it doesn’t rattle around and I wouldn’t need an “anti rattle” device?

Posted

I do recall my statement from earlier with only rattling with no trailer. Picked up a small 5x9 trailer today and it bounced around making noise off the hitch on the smallest bump. Maybe it is time to upgrade. 

Posted (edited)
On 10/26/2025 at 10:43 AM, AndrewF said:

I do recall my statement from earlier with only rattling with no trailer. Picked up a small 5x9 trailer today and it bounced around making noise off the hitch on the smallest bump. Maybe it is time to upgrade. 

I've wondered that too as to owning an adjustable height 2 1/2 receiver insert as everything else I have accumulated over the years is all 2 inch and they get used in other trucks as well.  I haven't been towing anything yet with this truck other than moving a trailer around the yard so the adapter worked fine for that. One thing is for sure, you don't want to forget the hitch assembly in the receiver if your going to use a multi pro tailgate !. 

 

The fancy aluminum hitches, they are certainly lighter and as long as its made well enough and rated for the task but oh are they expensive although the steel ones are pricey enough. 

 

I've never had reason to try using tape as was suggested and that could be an interesting experiment, use electrical tape to fit your adapter so it just nicely goes in and then your 2" as well and then use it pulling the trailers and see if the tape can handle the weight stress, the price is right at least and won't damage anything. 

Edited by Chuck FB

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