Jump to content

Recommended Posts

Posted

Brand new 2019 AT4 with 6.2 and 10 speed, hooked up my 24' ATC aluminum trailer before I put my car in it and it bottoms out on the bump stops,

just put my 2945 lb race car in and the truck, now sagging in the back so bad I had to change receptor and ball out just to release the jack on the trailer 

Drove it around the block and it steers like crap due to the suspension being bottomed out

This truck supposedly has 9k plus towing capacity? 

 

My 2015 Suburban w. 5.3 is perfectly level when towing the exact same load

 

Anyone with same towing problems?

Posted

Sounds like something’s wrong. I put a 4500lb travel trailer on my z71 and it barely moved. What’s the tongue weight of your trailer?


Sent from my iPhone using Tapatalk

Posted

If you are using the same hitch you were on your old vehicle that could be the problem as the AT4 is much taller you need to have a larger drop. I have not been towing with mine yet because I need a new hitch to get it lower to the ground to make the load level.

Sent from my SM-G965U using Tapatalk

  • Like 2
Posted
20 hours ago, 21STCMC said:

Brand new 2019 AT4 with 6.2 and 10 speed, hooked up my 24' ATC aluminum trailer before I put my car in it and it bottoms out on the bump stops,

just put my 2945 lb race car in and the truck, now sagging in the back so bad I had to change receptor and ball out just to release the jack on the trailer 

Drove it around the block and it steers like crap due to the suspension being bottomed out

This truck supposedly has 9k plus towing capacity? 

 

My 2015 Suburban w. 5.3 is perfectly level when towing the exact same load

 

Anyone with same towing problems?

Your problem is related to the less than optimum factory Tenneco "Rancho" shocks. 

A shock improvement or airbag setup will help yield better towing results. :thumbs:

Posted

Thanks Dan for the reply, can you suggest a specific model/brand (direct fit) for this application

 

I really appreciate it 

 

Best Regards,

John P

Posted
1 hour ago, gothp28 said:

If you are using the same hitch you were on your old vehicle that could be the problem as the AT4 is much taller you need to have a larger drop. I have not been towing with mine yet because I need a new hitch to get it lower to the ground to make the load level.

Sent from my SM-G965U using Tapatalk
 

Believe it or not my 2015 stock Suburban hitch receptacle sits 2-3" taller than the "lifted" AT4

Posted
6 hours ago, Controller23 said:

Sounds like something’s wrong. I put a 4500lb travel trailer on my z71 and it barely moved. What’s the tongue weight of your trailer?


Sent from my iPhone using Tapatalk

You may have the "Max Tow" Package, after further study I see that the AT4 & Denali do not come with and it's not available on either model, forcing someone

that wants to tow into a Sierra with a Max Tow option, hard to believe that is needed for such little weight 

Posted
Believe it or not my 2015 stock Suburban hitch receptacle sits 2-3" taller than the "lifted" AT4
If its 3in lower That would mean the trailers nose would also be 3" lower meaning it has way too much tongue weight.

Sent from my SM-G965U using Tapatalk

  • Like 2
Posted (edited)

How bout a set of Timbrens as a cheap fix?  Take about 5 minutes to install.

Edited by CRApex
Posted
2 hours ago, gothp28 said:

If its 3in lower That would mean the trailers nose would also be 3" lower meaning it has way too much tongue weight.

Sent from my SM-G965U using Tapatalk
 

Went from a drop hitch to straight, trailer was same height

Posted

I don’t believe you can order Z71 with max tow.   I ordered my LTZ and it my was either Max Tow or Z71.   Ordering Max Tow canceled out the Z71 option.

Posted

John, 

 

Some on the K2 forum have reported good results with Bilstein 4600 or 5100 shocks when towing.

Sounds like you are pulling a beast. An air bag setup will probably work best with your situation.

Posted

Shocks can slow down bottoming out, they are supposed to reduce the bounciness/"shock" of the springs working.  If you are fully bottomed-out and not just bouncing off the bump stops occasionally then you need stronger or taller springs, not different shocks.  If you are just bouncing off the stops then stronger shocks might be enough to slow/stop that.  Shocks don't hold the truck up, springs do.

 

Airbags are spring alternatives not shock alternatives so that sounds like a good choice.

  • Like 2
Posted

I wouldn’t think an empty aluminum trailer would bottom out any truck much less a max tow pkg.. something has to be wrong with leaf springs....

Posted

I'm gonna put an airlift kit in my AT4 on mine just because of ride quality and my plans to lift/level but I def don't need it.  

 

It doesn't even squat a little when I put my 18ft flatbed on there and that's got to weigh close to the same as your atc.  I've hauled a 4 place loaded with sleds and gear and it simply leveled the truck out. 

 

Sounds like something else is wrong to me.. 

  • 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

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