Jump to content

Recommended Posts

Posted

Hello, trying to get a little feedback from anyone who have installed the ReadyLift SST 2 inch kit on their 1500 AT4.

 

I have the SST kit installed on my 2021 Sierra 1500 AT4 and rides fine in 2wd. I understand ReadyLift doesn't recommend driving in Auto 4Hi, which is fine. ReadyLift says it is fine in 4Hi or 4Lo, however I'm getting vibrations in 4Hi. The shop who installed it, does a lot of work with lift kits, etc., and they have checked just about everything. 

 

Wondering if anyone else having this issue with 4Hi on the AT4. 

 

Thanks

Posted

its either angle of cv shafts (4" is lot for standard geometry) or its interferring with boot/cv axles is my guess.......shouldnt have a problem running any 4WD mode if done properly....I have heard of issues with Ready Lift TB kits and 4WD modes.....it would concern me if a company says our kit hinders normally functioning operation of the drive system.....something isnt right

 

I would check out those 2 things

  • Like 2
Posted
On 5/16/2021 at 5:46 PM, doggfatherone said:

I understand ReadyLift doesn't recommend driving in Auto 4Hi, which is fine. ReadyLift says it is fine in 4Hi or 4Lo,

You lost me with this quote?

 

I agree with Dunn, how did they get a GM approval if there are issues?

Posted (edited)

It sucks for sure.  I have researched a ton and it appears the only way to do this and not have issues it to drop the differential.  BDS makes a great 4" kit but you are going to spend about $3,000.  I looked at the readylift for my AT4 but just can't pull the trigger due to the stress on the CV's due to the angles, the diff has to drop.

Edited by Rackumrack
  • Like 1
Posted

Or just but a drop kit..I haven't found many though just by themselves....maybe BDS/Zone will sell them independently but good luck getting ahold of them

  • 2 weeks later...
Posted
On 5/18/2021 at 1:58 PM, Rackumrack said:

It sucks for sure.  I have researched a ton and it appears the only way to do this and not have issues it to drop the differential.  BDS makes a great 4" kit but you are going to spend about $3,000.  I looked at the readylift for my AT4 but just can't pull the trigger due to the stress on the CV's due to the angles, the diff has to drop.

@Rackumrack Yeah, I may take the @readylift SST kit off due to the cv angles and ride issues.

Posted
54 minutes ago, doggfatherone said:

May be a dumb question, but did you double check to make sure the shop installed the correct kit, The 69-3920 SST Lift Kit works with the factory 2" front lift. 

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

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