Jump to content

Recommended Posts

Posted (edited)

I'm towing this toy hauler.  6500lb empty.  Gross 10000lb.

 

Im only loading it to about 8500lb with bikes in the back.  Tows well, I have a blue ox swaypro with it.  1000lb bars but I might switch to the 1500lb bars. 

 

When I take it across the cat scales I'll right at the rear axel limit and about 100 lb under gvwr all loaded with the family.  Hoping the bigger bars will move a little more weight off the rear and back on the trailer.

 

20210702_140040.jpg

Edited by bowtie76
Add picture
  • Like 1
Posted
On 7/2/2021 at 11:14 AM, bowtie76 said:

I'm towing this toy hauler.  6500lb empty.  Gross 10000lb.

 

Im only loading it to about 8500lb with bikes in the back.  Tows well, I have a blue ox swaypro with it.  1000lb bars but I might switch to the 1500lb bars. 

 

When I take it across the cat scales I'll right at the rear axel limit and about 100 lb under gvwr all loaded with the family.  Hoping the bigger bars will move a little more weight off the rear and back on the trailer.

 

20210702_140040.jpg

 

What engine does your truck have?

 

Posted
On 7/4/2021 at 5:42 PM, Anacortes Army Guy said:

 

What engine does your truck have?

 

5.3L with the 10 speed.

 

pulled everything with no issues, been over the mtns to West Virginia and back with no issues.

Posted
On 6/22/2021 at 8:23 PM, Bcoyle21 said:

Thanks for the response. I am most definitely looking to add a WDH to the setup to support. My family weighs around 240lbs** and our luggage would be very little (200lbs as we pack light). From what I can find online the truck can safely tow around 9500lbs. This would be significantly less than the added payload and loaded trailer. We don’t plan to travel more than 1 hour 30 minutes away. I have several friends with half ton truck towing 6000lbs+ with no issues. The trailer is a total length of 32’ 11” tongue to tire. 

IMHO, I think you should pay close to what Army Guy is saying.  He's dead on.  Can your truck tow it?  Yes.  Can it tow it safely?  Likely not.  I knew based on what you were posting you either have a toy hauler or a 30'+ trailer.  It's too much trailer for such a light truck.  You're too close to some of your limits, and will likely go over on payload.  Imo, I recommend looking at a slightly shorter trailer.  A 26' trailer will be about 28'-29' total length, and drop a bunch of weight.  Also, Army Guy brought up the point of the trailer acting like a giant sail.  He's correct.  The size of the trailer, with it being fairly empty, will catch a bit of wind blowing from the side and push your back end out.  There are 2 things to consider to help with this.  One is your load rating on your tires.  Perhaps upgrading to a 10 ply tire would help?  Another factor is how close together the axles on the trailer are to each other.  When I was looking for a travel trailer one thing I learned about was how the further apart the axles are on the trailer the more stable the trailer will be when pushed on the side by wind.  This was a deciding factor with my purchase.  IMHO, the trailer you're looking at is best suited for a 2500.

Posted

It will tow it. Want to tow it and relax while doing it in some situations, 2500. 6 K pounds max for a 1500 IMO. 

  • Like 1

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
  • Latest Articles

  • Posts

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...