Jump to content

3500 DRW Hitch Height

John FX
 Share

Recommended Posts

John FX Enthusiast

John FX

Posted
Posted (edited)

Hi all,

 

I have a new 3500 DRW in transit, I expect it to arrive some time next month. One thing I'm trying to take care of ahead of time is ordering a new drop hitch for the 2.5" receiver so I can jump right into pulling a trailer. But I'm finding it impossible to find the hitch height documented anywhere. I checked with my dealer and they also weren't able to find any documentation on that dimension, and since nobody has any duallys in stock we couldn't just walk up to one and measure it.

 

If any of you happen to know the height, or if you already have a 20/21 3500 dually I'd really appreciate if you could share the height (measured from ground to the top of the receiver)! Thanks!

 

Quick rtfm check for where I've already searched:

Edited by John FX
John FX Enthusiast

John FX

Posted
  • Author
Posted
4 minutes ago, Metz54 said:

Just checked a 20 DRW, to the top of the receiver is 22.5".

Thanks! Is that with factory suspension, unloaded? I'm a little surprised since the other post measured a 2020 2500 to be 24". I expected a DRW to sit at least the same, or even higher.

Metz54 Enthusiast

Metz54

Posted
Posted
2 minutes ago, John FX said:

Thanks! Is that with factory suspension, unloaded? I'm a little surprised since the other post measured a 2020 2500 to be 24". I expected a DRW to sit at least the same, or even higher.

That is unloaded on a 20 High Country, I would think all the trims are the same height. I was surprised as well on one sheet I found from Chevy, the 3500 SRW has a total height 1" taller than the 2500.

John FX Enthusiast

John FX

Posted
  • Author
Posted
4 hours ago, Metz54 said:

Now that I think about it, you get smaller tires on the DRW. 

Good call. I just checked a tire website to get the tire sizes from the factory.

 

2020 Silverado HC 2500 = LT275/65R20 = 275mm * .65 = 178.75mm = 7.08" tire + 20" wheel = ~27" overall

2020 Silverado HC DRW = LT253/80R17 = 253mm * .8 = 202.4mm = 7.96" tire + 17" wheel = ~25" overall

So the DRW's axle is actually 1" lower to the ground. I imagine differences in suspension would raise the rest of the truck up to offset it, so they may be roughly the same overall ride height.

Keith_Schumaker Enthusiast

Keith_Schumaker

Posted
Posted

I figure all trucks are a little different so I'll post mine up too. I have a Chevrolet 3500 drw w/t with the Sulastic shackles which raised the rear at the wheel wells 1/4" when I measured. My hitch is 23" from the ground to the top.

Going back to every truck is different though, my last one was a 2018 f350 and one day at a new job site I parked next to another f350. I was about 2" lower in the front and 1" in the rear. He had aftermarket wheels and tires on his so I thought he just had a level kit and bigger tires. You should have heard how upset he got when I asked where he got his level kit, here he had a 6" lift kit on his just to get up to where mine sat from factory.

Sent from my ONEPLUS A6013 using Tapatalk

John FX Enthusiast

John FX

Posted
  • Author
Posted (edited)
On 3/21/2021 at 5:13 AM, Keith_Schumaker said:

I figure all trucks are a little different so I'll post mine up too. I have a Chevrolet 3500 drw w/t with the Sulastic shackles which raised the rear at the wheel wells 1/4" when I measured. My hitch is 23" from the ground to the top.

Going back to every truck is different though, my last one was a 2018 f350 and one day at a new job site I parked next to another f350. I was about 2" lower in the front and 1" in the rear. He had aftermarket wheels and tires on his so I thought he just had a level kit and bigger tires. You should have heard how upset he got when I asked where he got his level kit, here he had a 6" lift kit on his just to get up to where mine sat from factory.

Sent from my ONEPLUS A6013 using Tapatalk
 

Thanks for the info! I totally agree, every truck is different. Plus it also depends on what you load into it... if you've got a huge toolbox + a bunch of equipment always hanging around in the back its going to sag a bit.

 

FWIW in case anyone else discovers this thread and has the same question: It seems like I can expect the receiver height to sit somewhere in the mid-to-low 20"s. I ended up ordering the 10" drop hitch from weigh safe, I figured that will give me the most flexibility even if I don't need to use the full drop all the time.

Edited by John FX
Keith_Schumaker Enthusiast

Keith_Schumaker

Posted
Posted
42 minutes ago, John FX said:

Thanks for the info! I totally agree, every truck is different. Plus it also depends on what you load into it... if you've got a huge toolbox + a bunch of equipment always hanging around in the back its going to sag a bit.

 

FWIW in case anyone else discovers this thread and has the same question: It seems like I can expect the receiver height to sit somewhere in the mid-to-low 20"s. I ended up ordering the 10" drop hitch from weigh safe, I figured that will give me the most flexibility even if I don't need to use the full drop all the time.

Watch pulling out of parking lots with steep aprons,  I had a 8" drop on my f350 which was about 1" higher than my chevy and it would rub quite often leaving my local dunkin donuts.  It was a 2.5" shank that I bought to replace the shank on my w/d hitch so I just cut about 1" off the bottom and it wouldn't rub anymore.  Just remember the drop hitch isn't measured from top to bottom of hitch it is measured from top to bottom of ball.  My 6" weigh safe hitch with the 2.5 shank is 9" from top of hitch to the lowest point of the hitch, so a 10" would probably be 13" or so which would only leave about 10" ground clearance 4 feet behind your axle which isn't much.

  • Like 1
John FX Enthusiast

John FX

Posted
  • Author
Posted
1 hour ago, Keith_Schumaker said:

Watch pulling out of parking lots with steep aprons,  I had a 8" drop on my f350 which was about 1" higher than my chevy and it would rub quite often leaving my local dunkin donuts.  It was a 2.5" shank that I bought to replace the shank on my w/d hitch so I just cut about 1" off the bottom and it wouldn't rub anymore.  Just remember the drop hitch isn't measured from top to bottom of hitch it is measured from top to bottom of ball.  My 6" weigh safe hitch with the 2.5 shank is 9" from top of hitch to the lowest point of the hitch, so a 10" would probably be 13" or so which would only leave about 10" ground clearance 4 feet behind your axle which isn't much.

 

Oh good point, I didn't consider that. In that case I may change out which one I order...

  • 3 months later...
THE YETI Enthusiast

THE YETI

Posted
Posted

So what did you order and how much clearance from lowest point of drop hitch to the ground?

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

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