Jump to content

Recommended Posts

Posted
32 minutes ago, GoDj1978 said:

Are you using the factory wheels and if so what size wheels and tires are you running, also did you have to use the wheel spacers if so?

 

Aftermarket wheels: 17x8.5 (0 offset) with 35x12.50R. No spacers. Only rub at nearly full lock in reverse. 

  • 11 months later...
Posted
On 3/23/2020 at 7:46 AM, Kevin Galloway said:

LA, what were the issues that you had with it? I've had mine on now for about a month. Waiting on my BORA .375" spacers to mount my 35x11.5 Ridge Grapplers.  I ordered .25" spacers but the tires still contacted the UCAs at droop.  I feel like my driver side CV axle is binding at a certain point.  Passenger side wheel spins freely, but driver side I have to force to spin for about 30 degrees each rotation. Thanks

"4 kits are a bad idea.   No way around it.    I've been doing lifts for 25 years.   The major issues is the axle angles ...   You need to drop the T case to get the angles back to flat/near flat.   2" you can get away with.   

  • Like 1
Posted
On 3/25/2020 at 8:50 PM, Ericruiz911 said:

I'll chime in since I probably have the most miles on it. I put the kit on in April/2019 with about 300 miles on the truck and I have almost 10k miles on it now. Haven't had a single issue with the kit. No rusting or failing bushings/ball joint. The kit is a really soft ride because you're utilizing factory shocks and it also causes a loss of traction over really bumpy stuff, but that is on the factory shocks. Overall, I would highly recommend the kit.

 

The only other thing is that I am dying to change the stock shocks. The rear shocks are definitely on their way out because you can feel it, but the front left has now started making a noise too and the truck has begun to give off that floating feeling (so to speak). The truck hasn't seen any abuse as I moved to another state and have been focused on work so it's just another Silverado with hit or miss shocks. Been waiting on Bilstein since I put the kit on but nothing, and there really isn't too many options. Just going to get the stock ones replaced under warranty next time I need an oil change.

 

Hope this helps

With 4" your are outside the limits of the stock shocks.  Upgrade to ANYTHING that is right sized and you'll like the ride much better.   Go with a nice set of Bilsteins or Fox and you will love the ride.

Posted

exactly.....at some point you are gonna have problems...........longer cv axles dont correct the angle in which they sit at.....2" is the bubble and GM plays the odds on how many will come in for warranty vs how many wont.....its a win win for them regardless so what they say is pointless...no truck can go from standard to 4" with no modifications....its just physics 

 

live and learn i guess......i wish there was forums and message boards when i started doing this in the 80s, would have saved me a few trucks, lol

 

cant even count how many start with these kits only to end up with better one dtl after they wasted money they thought they were saving.....

  • Like 1
  • 3 months later...

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