Jump to content

Max Tow but still to much squat

BigDog88
 Share

Recommended Posts

corn18 Enthusiast

corn18

Posted
Posted
15 hours ago, madconcept said:

I have a levelled 2019 Sierra, Max trailering option. This truck sits higher than my last truck overall so I actually lowered the height position on my WD hitch to prevent our TT from going down the road with the front end pointed up.

Hooked the trailer up today and overall the trailer sits level now but my truck squats.

I’m sure the levelling kit doesn’t help.  I measured about 5 1/2” inches between fender and top of the tire up front and about 4” from tire to fender in the back.

I’m sure airbags would really help, especially for trucks with levelling kits.

I also have quite a bit of weight in that toolbox I have on my truck.  When on holidays I’ll empty that out, although probably have a load of firewood in the truck anyways.  Just make sure the firewood is pushed as far forward as possible.

Myself at 170 lbs, wife that is 105lbs then 3 kids in the back seat come in around 160lbs total will mean a fairly loaded truck but well below the limit I’m sure!

 

37520477-5424-48CB-86EC-5E8D022C2F81.jpeg

081CC146-536B-4D1A-9E9A-C04F0114D5C6.jpeg

8C46FDBF-C572-491E-8185-A0B5AA89A3A7.jpeg

Your trailer is level: goodness.  The WDH bars are level with the frame: goodness.  But your WDH head looks level in the last pic and that might indicate you are not transferring much weight to the front of the truck and the trailer axles.  I would tilt the WDH head down a bit more.  Those WDH bars will start bowing more and you should get a more level truck.  Although the CAT scales are the ultimate way to measure how well your WDH is setup, measurements work well, too.  Get the front of your truck within 1/2" of its empty height with the WDH hooked up.  

  • Replies 33
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

TRKLGND
TRKLGND

So how much does is squat?  You can also take it to a truck stop and put it on the scales.  It will tell you the total weight, weight of each vehicle and how much is on the tongue or pin. I

pewterliftedz
pewterliftedz

With you truck and trailer on level ground, how much taller is the ball than the top of the trailer ball mount?  These truck do have to squat some to engage the overload spring.

Likarok
Likarok

Personally I would do Air Bags.

Posted Images

madconcept Enthusiast

madconcept

Posted
Posted
18 hours ago, corn18 said:

Your trailer is level: goodness.  The WDH bars are level with the frame: goodness.  But your WDH head looks level in the last pic and that might indicate you are not transferring much weight to the front of the truck and the trailer axles.  I would tilt the WDH head down a bit more.  Those WDH bars will start bowing more and you should get a more level truck.  Although the CAT scales are the ultimate way to measure how well your WDH is setup, measurements work well, too.  Get the front of your truck within 1/2" of its empty height with the WDH hooked up.  

I ended up tilting the wdh head down a bit more yesterday.

Didn’t have time to hook up the truck to the trailer yet though.  Hopefully it works.

I’m taking the trailer in for service this week and I’m hoping they have a tongue weight scale.

Might be too front heavy the way I loaded the trailer with stuff?  Storing a bunch of heavier items in the front storage compartments of the trailer as those storage areas were convenient.

pewterliftedz Enthusiast

pewterliftedz

Posted
Posted (edited)
16 hours ago, madconcept said:

I ended up tilting the wdh head down a bit more yesterday.

Didn’t have time to hook up the truck to the trailer yet though.  Hopefully it works.

I’m taking the trailer in for service this week and I’m hoping they have a tongue weight scale.

Might be too front heavy the way I loaded the trailer with stuff?  Storing a bunch of heavier items in the front storage compartments of the trailer as those storage areas were convenient.

FYI, all the videos I've seen recommend at least 5 chain links between the bars and snatch bracket.

Edited by pewterliftedz

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

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