Jump to content

2020 Silverado front suspension versus previous years


Recommended Posts

Posted

I recently purchased a 2020 Silverado 1500 LT and a lifetime of driving cars. I found the ride too uncomfortable and after some reading here, replaced the rear shocks with Bilstein 4600 series. Made a substantial difference in the ride quality on rough roads. Thinking about replacing the front struts and looking at videos pf 2013 to 2018, it is fairly simple. Remove top 3 strut bolts and bottom two and the assembly comes right out.

 

I can not find a video on 2019-2020 but videos of front leveling kits being installed show the control arms being disassembled and the ball joints removed. So it seems that there is a change for 19-20 models but need to confirm.

Posted

I've been curious about this same thing. I have a '19 LTZ 4x4 without the Z71 package. I've noticed the rear gets unsettled on rough roads and gets a little loose. Granted, it's got the max trailering package and I realize it's a bit stiff, but it sounds like changing the components helped out. Do you have the exact part number of the Bilsteins you used?

Also, I've noticed the front end has quite a bit of bounce to it in uneven parts of the roads here in DFW. Is that what you've experienced as well to make you want to upgrade the front?

Sent from my SM-G965U1 using Tapatalk

Posted

The link below is the ones I put on my truck but keep in mind that mine is a 1500 LT 2WD.

 

https://smile.amazon.com/gp/product/B00Y9CQ1OE/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

 

 

I never owned a truck so it is hard for me to describe the ride. When I hit one bump, it felt like I was hitting a few bumps. I am assuming that the rear wheels were bouncing after hitting a bump. The main road near my home is an old country road that has been patched and patched and patched. It was a miserable ride with the original shocks. I am feeling the same thing from the front.

Posted

The 19-20 is redesigned but is the same basic concept. Pop the tie rod loose, then upper and lower strut bolts and remove strut.

Sent from my SM-G973U using Tapatalk

Posted
On 6/17/2020 at 4:09 PM, Dwayne C said:

I recently purchased a 2020 Silverado 1500 LT and a lifetime of driving cars. I found the ride too uncomfortable and after some reading here, replaced the rear shocks with Bilstein 4600 series. Made a substantial difference in the ride quality on rough roads. Thinking about replacing the front struts and looking at videos pf 2013 to 2018, it is fairly simple. Remove top 3 strut bolts and bottom two and the assembly comes right out.

 

I can not find a video on 2019-2020 but videos of front leveling kits being installed show the control arms being disassembled and the ball joints removed. So it seems that there is a change for 19-20 models but need to confirm.

Presumably you are running the truck unloaded.

 

Have you reduced the tire pressures from the numbers recommended for when the truck is at max load?

Makes a huge difference in the ride harshness. 

 

As does staying away from the 20's and 22's that the factory offers.

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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...