Jump to content

Level or lift 2015 2500HD

corn18

By corn18
in Modifications & Accessories

 Share

Recommended Posts

corn18 Enthusiast

corn18

Posted
Posted

Wanted to see what the front end geometry does if I decide to level the truck.  Stock has a pretty good rake and it takes 2.25" of front lift to level the truck.  I also looked at an intermediate level of 1 3/8".  Here's the pics:

Stock, 1 3/8" lift, 2.25" lift

140841-albums3520-picture20527.jpg
140841-albums3520-picture20528.jpg
140841-albums3520-picture20529.jpg

To my eye, level looks best.  But I would have to bag it for towing.  I'm ok with that.  

Now let's look at the front end to see if I can just crank the torsion keys to level it, or if I need more. (stock, 1 3/8", 2.25")

140841-albums3520-picture20533.jpg
140841-albums3520-picture20534.jpg
140841-albums3520-picture20535.jpg

Dang, anyone who just levels it with a new torsion key is really doggin' the UCA and the drive shaft.  If I went full level, I would do a diff drop and get new UCAs.

But I think that intermediate position @ 1 3/8" is OK.  It improves the look a bit, I shouldn't need bags for towing and the suspension bits look OK.  I have the torsion keys on the way so I think I will do just over an inch with them and check things out.  If I want to go full level, I will add the diff drop, new UCAs and bag the rear end (adding $800 to the bill).

Would appreciate any thoughts from the collective FR experience.  

Corn

gearheadesw Senior Enthusiast

gearheadesw

Posted
Posted

You, sir, are correct. Your'e on the right track. Running skinny 35's with keys, diff drop, 5160's with shock spacer, BDS steering stabilizer, UCA's, rear bags, and a bumper that lets nothing touch. I added the ready Lift UCA's at the end, and they made all the difference in the world for ride. They freed up the front suspension movement, got the alighnment back on track. I get in and out of my truck like 50 times a day it seems, so I don't want a lift, just a little level, and I'm good. Hope you figure out what you want, these are great trucks.

IMG_0186.JPG

  • Like 1
corn18 Enthusiast

corn18

Posted
  • Author
Posted

Well, I think I am going to lower the rear and throw bags on.   A lot simpler and cheaper.  If I don’t like it I can always raise the front. 

corn18 Enthusiast

corn18

Posted
  • Author
Posted (edited)

Rear shackles are in. That was easy.  Love it.  Now to put the air bags on and adjust the headlights.  It’s sitting perfectly level with the ground now. 
 

 

7FCF02C4-2636-4C6D-AA04-BBB7279E60A3.jpeg

Edited by Tom Hole
  • Like 1
Icutmetl Enthusiast

Icutmetl

Posted
Posted

I liked your 1-3/8” look the best, personally. I’m going to do 1” at both ends with mine. How are you liking the Grabber ATX’s?

corn18 Enthusiast

corn18

Posted
  • Author
Posted
51 minutes ago, Icutmetl said:

I liked your 1-3/8” look the best, personally. I’m going to do 1” at both ends with mine. How are you liking the Grabber ATX’s?

 

The Grabber ATX's seem fine.  Like all things, the AT aspect is a trade off.  It feels like a truck.  It doesn't drive like it's on rails like our BMWs.  They aren't too noisy.  They'll work.  I think when these wear out I may look at 20" rims.

corn18 Enthusiast

corn18

Posted
  • Author
Posted

After driving it around for a while with the drop shackle level, I like the look of the front end lift much better.   But the rear end lower is more practical for me right now.  We are looking at 5th wheels and lowering the rear and adding bags provides better clearance.  And it sure is easier to get in the bed with it lowered.  

corn18 Enthusiast

corn18

Posted
  • Author
Posted (edited)

Sorry to keep replying to myself but wanted to add more data.  

 

1.  Stock = 2.5" rake

2.  Rear drop shackles = level

3.  Add air bags = 3/4" rake

 

I was doing some other stuff to the truck and thought I would see if there was anything available on the stock torsion keys to get back to level.  Sure enough, I got 3/4" lift with about 2 turns on the stock key bolt.  I took it for a test drive expecting it to be rougher than before but it was actually better.  I guess after 5 years, the torsion bars might have needed some tightening.

 

So I am happy with this setup.  3/4" front lift with a few turns on the stock torsion keys.  Drop shackle in the rear with airbags.  

 

Now I need to find something else to futz with.

Edited by Tom Hole
  • Like 1
MNorby Enthusiast

MNorby

Posted
Posted

I originally considered lowering the rear of mine but ultimately lifted the front roughly 1.5" (7 turns of T-bar bolt) because I was concerned how airbag might react being compressed more from the get go. I also did the diff drop as well.

  • 1 month later...
corn18 Enthusiast

corn18

Posted
  • Author
Posted

UPDATE:  Decided to drop the front back down to stock.  It was bone jarring at the higher tension setting on the torsion bars.  Much better now. I can't imagine the death ride you would get if you cranked the torsion bars all the way up to get 2"+ of lift.  

  • 2 weeks later...
Icutmetl Enthusiast

Icutmetl

Posted
Posted
On 6/4/2020 at 12:30 PM, Tom Hole said:

UPDATE:  Decided to drop the front back down to stock.  It was bone jarring at the higher tension setting on the torsion bars.  Much better now. I can't imagine the death ride you would get if you cranked the torsion bars all the way up to get 2"+ of lift.  

Are you saying your ride went to crap with only the 3/4” of height you’d added to your front end, or am I misunderstanding?

corn18 Enthusiast

corn18

Posted
  • Author
Posted
3 minutes ago, Icutmetl said:

Are you saying your ride went to crap with only the 3/4” of height you’d added to your front end, or am I misunderstanding?

I'm saying it was worse with 3/4" of height added to the front with the tension thingies.  

corn18 Enthusiast

corn18

Posted
  • Author
Posted
Just now, Jacob Kuehl said:

wow.  I was going to crank up my keys 1"  but maybe I wont...

 

I would give it a go.  Real easy to do and undo, so if you don't like it, you can easily go back to stock.

  • 4 weeks later...
Zasker1 Enthusiast

Zasker1

Posted
Posted

What size tires are you running on your setup.

 

I just bought a 2016 LBZ, it has 265/60r20's on it at present, but I would like to put a 275/65 r20 on it.

 

The 265's look a bit too narrow

 

I'm hoping the increase in aspect of a 65 will give me a little bit better ride quality.

 

The truck has 85k on it so I was going to go ahead and replace the junk rancho shocks with fox shocks, turn the keys up 1.25 in and call it a day.

 

Unfortunately the aftermarket rims I believe have a zero offset so they're already sticking out a little bit in fact as you can see from the pictures the 265 just about rubs..

d40ccc9a59aecbe03dad8d32d4572b27.jpg

dd16068ddf9549bde3e629e9c7b43f91.jpg

 

Sent from my SM-G975U using Tapatalk

 

 

 

 

 

 

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

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