Jump to content

Bilstein leveling kit - 08 1500 4wd V8

thezentree
 Share

Recommended Posts

thezentree Enthusiast

thezentree

Posted
Posted

Hey all, new here and have a 08 Sierra 1500 V8 4wd that needs new shocks. It's currently got a RC 2" strut spacer leveling kit and 285s on it, but the shocks are factory and it's got 210k miles on it. They are done, to say the least. I think I have an idea of what I want, just wanted to run it past y'all in case I'm about to order the wrong parts. Before anyone jumps my sh*t, I did search and couldn't find a thread that cleared this up, but that's not to say I didn't miss something.

 

Front:

Bilstein shocks P/N 24-186940, with the spring seat clip set in the top groove, factory springs, and no RC spacer. I want to keep it as low as I can while still clearing the 285s with no cutting, so if I can get away with a lower groove, let me know.

 

Rear:

Bilstein rear shocks P/N 24-293082. Maaaybe and ORD zero rate in the rear to add an inch to the rear so it's not squatted when loaded? I am assuming that the rear shocks I listed above will work with 1" lift in the rear?

 

Thanks in advance.

Lurchenstein Enthusiast

Lurchenstein

Posted
Posted

I am interested in this as well.

I am looking in to,

front

Bilstein 6112

rear

bilstein 5160

wheels 18x9.5  -18 offset

tires 

goodyear wrangler duratrac 295/65/18

 

Gtschwifty Enthusiast

Gtschwifty

Posted
Posted (edited)

2012 Silverado 1500 V8(LC9) 6l80 4WD extended cab 6'6" bed WT.

 

Just ordered the B8 6112 with 5100's for the rear. 765 shipped 

 

Stock wheels and 265/70r17 tires for the time being 

 

Edited by Gtschwifty
Gtschwifty Enthusiast

Gtschwifty

Posted
Posted (edited)

Thezentree we need more detail. 285 is only the width. Need aspect ratio, rim size, offset to have any idea of what you're working with. I think you're on the right path with top notch in the front and adding an inch in the rear. Should net 1.25" MORE rake than you currently have. If that's too much I'd look into a different block in the rear or having one milled to achieve however much rake you're after. If it were me I'd order just the struts and shocks with those part numbers you posted(seems to be about $357 on shocksurplus with SHOCKD 5% promo code) set it at the top notch, drive it a while, load it, measure it, then decide what(if any) lift you would like in the rear. I can't see it being more than an inch so your rear shocks would be ready. Also with 210,000 miles on factory struts you may stand to benefit with a kyb top hat with bearing and spring seat ($40 per strut on rockauto) since you're swapping those over to the 5100s anyways it would be the time to do it.

Edited by Gtschwifty
  • Like 1
thezentree Enthusiast

thezentree

Posted
  • Author
Posted
2 hours ago, Gtschwifty said:

Thezentree we need more detail. 285 is only the width. Need aspect ratio, rim size, offset to have any idea of what you're working with. I think you're on the right path with top notch in the front and adding an inch in the rear. Should net 1.25" MORE rake than you currently have. If that's too much I'd look into a different block in the rear or having one milled to achieve however much rake you're after. If it were me I'd order just the struts and shocks with those part numbers you posted(seems to be about $357 on shocksurplus with SHOCKD 5% promo code) set it at the top notch, drive it a while, load it, measure it, then decide what(if any) lift you would like in the rear. I can't see it being more than an inch so your rear shocks would be ready. Also with 210,000 miles on factory struts you may stand to benefit with a kyb top hat with bearing and spring seat ($40 per strut on rockauto) since you're swapping those over to the 5100s anyways it would be the time to do it.

Hah sorry, I come from the land of 4Runners where “285s” means either 285/75R16 or the 17” equivalent. I’ve got 285/70R17s on factory wheels. My next set of tires will likely be 255/80R17s but if the 285s fit, the 255s should too. 
 

I think you’re right about holding off on doing anything to the rear (other than shocks). 
 

And good call on new hardware. I’m sure the existing stuff is a little crusty. 

Gtschwifty Enthusiast

Gtschwifty

Posted
Posted

Bilsteins, 255/80r17s, you do come from the land of Toyota. I am curious about that size as well, which tire? Haven't found anyone really running them on this platform 

thezentree Enthusiast

thezentree

Posted
  • Author
Posted
1 hour ago, Gtschwifty said:

Bilsteins, 255/80r17s, you do come from the land of Toyota. I am curious about that size as well, which tire? Haven't found anyone really running them on this platform 

#overlandAF haha

 

My Sierra has been relegated to a second vehicle since I got the 4Runner, but eventually I plan to cut up a 1st gen Tacoma as a dedicated trail rig so I don’t ruin the 4Runner or the Sierra. The Sierra is going to be the tow pig for that and won’t see much dirt other than trips to the beach or forest roads, so a skinnier tire is appealing to me from a MPG perspective. Right now I’ve got my eye on a set of Falken AT3Ws in 255/80 since I loved the set I had on the 4Runner. 
 

Gotta get new shocks first so I can get it aligned after it’s (re)leveled. 

Gtschwifty Enthusiast

Gtschwifty

Posted
Posted

Sounds like a plan. Full disclosure I ordered my shocks and struts before I've even taken possession of the truck, picking it up this Friday though. By financial necessity it will be my one and only daily driver. So for now I am thinking I'll try the second circlip ring on the 6112's (back has a mid-height topper and I need rake) along with just "4 ply" 265/70r17 falken at3w because at 600 for a set I am hard pressed to find a better tire. I loved my set on my old F150 and they are excellent for rain and winter, especially being non-LT with the grippy silica compound. Eventually I do want either the p285/70r17 or the LT255/80r17. 

thezentree Enthusiast

thezentree

Posted
  • Author
Posted

Welp, got the springs swapped to the new front shocks, but it's looking like I'm going to have to separate the upper ball joint so the lower control arm can drop far enough to get the bar pin on top of it. That means pulling the CV out of the hub so I can get a puller on the bottom of the ball joint.

 

Anyone run into this before?

thezentree Enthusiast

thezentree

Posted
  • Author
Posted
1 hour ago, Gtschwifty said:

How did it go?

It's still on jackstands, but mostly due to me being indecisive.

 

I thought about it more and decided to keep the RC leveling block and drop the spring seat down to the lowest groove. This way I keep the same amount of lift and don't have to add a bunch of preload to the springs and stiffen the ride a bunch.

 

Unfortunately the cheap spring compressor kit I had turned out to be basically disposable, so I'm waiting on an OTC clamshell strut spring compressor to get here to take it all apart again. Also I neglected to order jounce bumpers with the KYB top hats (you'd think they'd be included), and it would bug me forever to not have those installed, so those are on the way too. Thankfully I'm working from home and have the 4Runner to get around in, so I'm not too jammed up.

 

I'll follow up when I get all the parts and have time to take another stab at it.

Gtschwifty Enthusiast

Gtschwifty

Posted
Posted

I still cannot wrap my head around what people mean by preloading the spring. In my mind all you're doing is extending the distance from spring perch to lower control arm exactly the same as a lower spacer. Preloading shock travel and droop if anything. I am not saying I am right, I am looking to be set straight if I am missing something obvious here. The stiffer ride would be due to the arm being farther out of neutral resulting in less force acting perpendicular to the control arm meaning less torque rotating the arm into the dampener and more force sent through the arms into the frame. I cannot get past it being a result of geometry no matter how it's achieved. 

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
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,691 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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