Jump to content

Recommended Posts

Posted

Put the belltech 2-3" shackle in the back a couple days ago and left the block in. Truck sits with a 1/2" squat with it installed at the 3" hole. The front probably pivitided upward slightly to make it lower in the back now. Thinking of going to the 2" hole and hope it'll make it a 1/2" rake cause I'd much rather that. this thread has been super helpful just reading it. Here is what she looks like with a slight squat Wanted to call it darth vador but someone beat me to it on here lolpost-160818-0-04873000-1469651933_thumb.jpeg

post-160818-0-04873000-1469651933_thumb.jpeg

post-160818-0-04873000-1469651933_thumb.jpeg

post-160818-0-04873000-1469651933_thumb.jpeg

  • Like 1
Posted

Put the belltech 2-3" shackle in the back a couple days ago and left the block in. Truck sits with a 1/2" squat with it installed at the 3" hole. The front probably pivitided upward slightly to make it lower in the back now. Thinking of going to the 2" hole and hope it'll make it a 1/2" rake cause I'd much rather that. this thread has been super helpful just reading it. Here is what she looks like with a slight squat Wanted to call it darth vador but someone beat me to it on here lolattachicon.gifimage.jpeg

You could always change the chrome that's left to red and call it Darth Maul.

 

Sent from my SM-G935V using Tapatalk

Posted

You could always change the chrome that's left to red and call it Darth Maul.

Sent from my SM-G935V using Tapatalk

That's true haha. I've got a few different colours of vehicle wrap so I can change my emblem any time, red being one of them lol

  • Like 1
Posted

Put the belltech 2-3" shackle in the back a couple days ago and left the block in. Truck sits with a 1/2" squat with it installed at the 3" hole. The front probably pivitided upward slightly to make it lower in the back now. Thinking of going to the 2" hole and hope it'll make it a 1/2" rake cause I'd much rather that. this thread has been super helpful just reading it. Here is what she looks like with a slight squat Wanted to call it darth vador but someone beat me to it on here lolattachicon.gifimage.jpeg

Looks great!

Posted

Looking good,you happy with the drop is that like a 2/3 drop?

 

 

Sent from my iPhone using Tapatalk

I like it. I really wanna somehow drop the rear 1 more inch though. Not sure about a 3" drop shackle as it doesn't look like it will fit.

Posted

I like it. I really wanna somehow drop the rear 1 more inch though. Not sure about a 3" drop shackle as it doesn't look like it will fit.

Did you need alignment how's the ride?

 

 

Sent from my iPhone using Tapatalk

Posted (edited)

I like it. I really wanna somehow drop the rear 1 more inch though. Not sure about a 3" drop shackle as it doesn't look like it will fit.

I have the 3" shackle in my truck with the block still in and there isn't much clearance between the bump stop. With the block out i would have to cut the bump stop or get aftermarket one.

Edited by Cdoan3
Posted

I didn't know there was a 3" drop shackle. I thought there was only a 2" and to get 3" you remove the block. Most have to flatten the bed seam to fit the 2", so how tight is the 3"?

Posted (edited)

I didn't know there was a 3" drop shackle. I thought there was only a 2" and to get 3" you remove the block. Most have to flatten the bed seam to fit the 2", so how tight is the 3"?

Belltech has a 2-3" adjustable shackle available. My dealership orders the shackles in and when I got it back that's what was in there. When I looked underneath it looks like the guy that installed it lifted the box cause the seam isn't folded. I looked up the part number to find this out it was the 2-3" adjustable shackle. I'm thinking of putting the adjustable strut belltech has so I can get a 2-4 drop without flipping the axel. Oh and I have no vibration or anything with it at the 3" hole. Edited by Cdoan3
Posted (edited)

I thought it was a 2" shackle and removing the block for 3" on 07 and up. Then they have another shackle for 3" drop but that is for the HD models

 

What are the rear ground to fender measurements? Wonder what they did? A 3" shackle on these truck would in the bed, what was the part number on your shackle?

Edited by wuznme
Posted

That's what I understood too. The shackle in Belltech 6400 and 6401 were both a 2" drop, but the 6401 kit came with spacers to put between the nuts and plate on the axle because the threads weren't long enough when you removed the lift block. I just bought the 6400 and 2WD u-bolts so I didn't have to use spacers.

Posted

Did you need alignment how's the ride?

 

 

Sent from my iPhone using TapatalkI

 

I did require an alignment. The front rides great. The rear is a little stiff but that should change after I get the new belltech shocks on.

 

Also with the 2" shackle I did have to fold the bed seam.

Posted (edited)

just got a 2016 CCSB sierra slt 2wd. first mod i did was replace the factory 20's with some black OE replica 24" rims on 305/35/24. thinking about just lowering the rear to level the truck out with the front. a little apprehensive though after reading about the issues with driveline vibration. need some advice. would the dealer do the installation? how much does the rear have to come down to level it out?

Edited by ozone

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...