Jump to content

Recommended Posts

Posted

Hello Everyone,

 

New to the forum. New to trucks as well at this point in time.

So, recently picked up a '19 GMC Sierra 1500 AT4. Love the car, plus it came with low mileage (hopefully not rolled back), and a few mods (rims, exhaust, lift kit).

 

I am used to SUVs and Sedan sports cars (Audi, BMW), so having a truck definitely feels different, so bear with me if I ask silly questions lol

 

So, I've test driven the 2021 5.3L V8 1500 GMC Evolution, was NOT impressed with it at all really, but thats because I'm used to a bit of a higher standard when it comes to interiors and options. Then noticed the dealership had a used 19 5.3L AT4, and I was sold right there. Took it for a drive, loved it due to the exhaust, lift, and wheels, a few less things for me to do with it. I did not feel it at first, but the car seems a bit jittery when driving, granted I get that its a heavy truck so acceleration isnt all that great, plus wheels are heavy so it may not be super smooth, but the car drives very jittery and not smooth. Service Dept at the dealership took it for a drive and said it drives fine, so not sure if its just me getting used to the truck, or what, but was hoping to get some insight from you truck folks on here. Another thing...DRONE at highway speeds is driving me up the wall. Love the sound of it when it turns on and when you step on it, the V8 growl is definitely pleasant, but at cruising speeds, that drone is just annoying...

 

My setup is as follows:

GMC Sierra 1500 AT4 - 5.3L V8

Rough Country 4" lift kit (no coilovers in front)

20" XD829 Hoss 2 wheels wrapped in Nitto Ridge Grappler 35x12.50R20

Exhaust looks like a chopped up exhaust (custom), do not recall the type of muffler in the center (not home now to check), but assuming that both flappers were cut out, but no clue if thats the case or not

 

Any help would be appreciated.

Posted

The 2019s were known to not ride the greatest in the first place, GM “retuned” the suspension (changed the springs) for 2020. And I doubt any of the aftermarket additions on your truck are helping matters.

 

Drone...if you have a hacked up pieced-together exhaust, not surprising. You really might want to consider getting a catback from GM Performance, Borla or Corsa. They are expensive sure, but they are also engineered to avoid drone.

Posted

If you're still running the Rancho shocks in the rear (And struts in the front) that has been a cause of a ride somewhat like you're describing. 

Posted

Thanks for the input guys. Recently moved from NJ to FL and this is my new gift but I want to LOVE the ride, but I just dont, at least not yet haha

So if I were to swap out the struts/shocks to coilovers in front and better shocks in back, would that solve the issue perhaps?

 

The below is what the truck has installed from what I narrowed down

https://www.roughcountry.com/gm-suspension-lift-kit-27530c.html?find=2019-gmc-sierra-1500-4wd-740023 

Cheapest config, so no coilovers or monotube shocks

Posted

I’m not lifted, but swapping my stock rear shocks for Bilstein 5100s definitely reduced the tail happy rear end behavior over bumps. 
 

Worth noting though, the stock Ranchos on the AT4 and Trail Boss are monotube. They supposedly much better than the ones that come with a normal height Z71 / X31 truck.

Posted (edited)

The Bilsteins are noted to be a big improvement, but I would start with finding out exactly what was changed when it was lifted.

 

As noted, I would also look at the exhaust to try and determine what was changed.  But it wouldn't surprise me if at least part of the drone is the tires.  Even with cars, tires can make a huge impact on ride and noise (I can tell a difference between my "summer" tires and my "winter" tires on the Camaro).

Edited by Jim E
Posted
I’m not lifted, but swapping my stock rear shocks for Bilstein 5100s definitely reduced the tail happy rear end behavior over bumps. 
 
Worth noting though, the stock Ranchos on the AT4 and Trail Boss are monotube. They supposedly much better than the ones that come with a normal height Z71 / X31 truck.
..... They're all monotube. [emoji38] I don't think that's it. Also, the TB/AT4 Ranchos are not any different from the other Z71s. It's only a 2 inch factory lift.

Sent from my SM-A516U using Tapatalk

Posted (edited)
33 minutes ago, HeySkippyDog said:

..... They're all monotube. emoji38.png I don't think that's it. Also, the TB/AT4 Ranchos are not any different from the other Z71s. It's only a 2 inch factory lift.

Sent from my SM-A516U using Tapatalk
 

No. Rancho shocks on a normal Z71 / X31 are twin tube, and they are junk. 

Edited by OnTheReel
  • Like 2
Posted

I'd go drive a stock factory lift truck (AT4) for comparison .

 

It might give you an idea which issues are due to the mods. 

 

 

  • Like 1
Posted
20 hours ago, HeySkippyDog said:

..... They're all monotube. emoji38.png I don't think that's it. Also, the TB/AT4 Ranchos are not any different from the other Z71s. It's only a 2 inch factory lift.

Sent from my SM-A516U using Tapatalk
 

 

19 hours ago, OnTheReel said:

No. Rancho shocks on a normal Z71 / X31 are twin tube, and they are junk. 

@OnTheReel is correct. The Z71 Ranchos are all twin-tube. And speaking as one who has a Z71 with these shocks... they are terrible. 

 

OP, you're right to realize that you're being a little unrealistic in hoping a lifted truck rides as smoothly as the SUVs and sedans you've driven. My 2019 RST rides LIGHT YEARS better than my 2007 Silverado did. The first week I drove the 2019, I was shocked at how much better the truck rides/handles. 

 

However, my wife's Honda Odyssey still rides better than my truck overall. 

 

But her van cannot pull 9500#, go off road, nor tower over the other cars on the road. 😎  

  • Like 1
Posted

those big spacers you have in front on that lift kit isnt helping.....and RC shocks well not so good

 

new shocks all way around with coilovers up front for that lift height (get a decent brand), make sure wheels are balanced and alignment is good, and that will be about as good as your gonna get.....maybe take a ride in someones who has quality setup already on and see if you like it....lifted trucks can ride horrible or pretty sweet but its still a lifted truck, and whats really nice to someone familar with trucks can be maybe not so much to someone who isnt.....

 

check to make sure someone did do something mickey mouse somewhere as well, you never know and people do it.......maybe take it to a reputable shop

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