Jump to content

Stock ride height - 4" rake?

SS2Sierra

By SS2Sierra
in Modifications & Accessories

 Share

Recommended Posts

SS2Sierra Enthusiast

SS2Sierra

Posted
Posted

Hey guys

 

I'm looking to level my 2017 Sierra Denali 4wd 6.2L. 

 

I noticed my rear sits 4" higher than the front (36" front/40" rear). I measured from ground through center of wheel to fenderwell AND from center of wheel up to fenderwell to hopefully get rid of any difference caused by tire pressure. Still 4" difference. That seems pretty high to me. Could it be from the larger engine up front, or am I missing something? I was hoping to just install the SuspensionMaxx 2" level and get pretty close to level but it looks like I'll still have 2" of rake.

 

I guess as a side note I was hoping to install 275/60/20 Duratracs after the level. That should fit no problem, right? 

 

Thanks !

GMC_SD_Ult_16 Enthusiast

GMC_SD_Ult_16

Posted
Posted

SS2Sierra,

I did the exact lowering of the rear you are looking at with a small amount of rake remaining.. I have a 2016 Sierra Denali Ult 6.2L 4WD and like the look and ride very much... I also purchased a longer magneride sensor arm so it would be closer to stock position. I used the shock extenders as well and lastly had a trim level relearn performed at dealership ...For me it rides better than it did stock and seems to get better mpg by a small amount. Looks better too and I can haul my travel trailer perfectly level.

Sent from my SM-N976V using Tapatalk

dieselfan1 Senior Enthusiast

dieselfan1

Posted
Posted
2 hours ago, SS2Sierra said:

Hey guys

 

I'm looking to level my 2017 Sierra Denali 4wd 6.2L. 

 

I noticed my rear sits 4" higher than the front (36" front/40" rear). I measured from ground through center of wheel to fenderwell AND from center of wheel up to fenderwell to hopefully get rid of any difference caused by tire pressure. Still 4" difference. That seems pretty high to me. Could it be from the larger engine up front, or am I missing something? I was hoping to just install the SuspensionMaxx 2" level and get pretty close to level but it looks like I'll still have 2" of rake.

 

I guess as a side note I was hoping to install 275/60/20 Duratracs after the level. That should fit no problem, right? 

 

Thanks !

Is it a standard (6' 6") bed?

Mine is and has 3 1/2" difference.

36 5/8"front,  40 1/8" rear.

The tires will fit with the 2" level no problem.

SS2Sierra Enthusiast

SS2Sierra

Posted
  • Author
Posted (edited)
16 minutes ago, dieselfan1 said:

Is it a standard (6' 6") bed?

Mine is and has 3 1/2" difference.

36 5/8"front,  40 1/8" rear.

The tires will fit with the 2" level no problem.

It's a crew cab short bed. 5' 8" - maybe the combination of short bed and 6.2L 4WD explains the 4" difference. 

 

I was hoping to limit my level to 2" in the front just to avoid needing any other suspension upgrades or potential issues. Do you think a 2" difference front to rear will even look any better than what I have now? Kind of frustrating, would be nice to go with a 1.5 or 2" level and be within an inch or less front to rear

Edited by SS2Sierra
added crew cab
dieselfan1 Senior Enthusiast

dieselfan1

Posted
Posted
27 minutes ago, SS2Sierra said:

It's a crew cab short bed. 5' 8" - maybe the combination of short bed and 6.2L 4WD explains the 4" difference. 

 

I was hoping to limit my level to 2" in the front just to avoid needing any other suspension upgrades or potential issues. Do you think a 2" difference front to rear will even look any better than what I have now? Kind of frustrating, would be nice to go with a 1.5 or 2" level and be within an inch or less front to rear

Go with a 2.25" then. 

Lots of reading material here...

 

GMC_SD_Ult_16 Enthusiast

GMC_SD_Ult_16

Posted
Posted

Here is my before and after pics... Subtle but very noticeable especially when standing at the bed... It makes getting items in and out of the bed much easier surprisingly. f03b6cbe185038943f0e1f9a3660aa66.jpg819b6b3c7b7a2f2a42cd7fd747c1168d.jpg

Sent from my SM-N976V using Tapatalk

  • Like 1
JimCost2014 Senior Enthusiast

JimCost2014

Posted
Posted
1 hour ago, rah7777777 said:

91A73997-EE42-4FE2-ADDE-0D545EA26A4A.thumb.jpeg.4fa57f7fc7da034a2d295b967f3a5ec5.jpeg

 

 

 

Not the best pic at all, but I lowered my rear about 2" to help level it out. Still a little higher in the rear, but much better than stock. 

 

Looks good, what did you use to bring down the rear?

rah7777777 Enthusiast

rah7777777

Posted
Posted

It was a lowering shackle.
2” I think, or right around that. Easy install except dropping the hitch receiver and bending the pinch weld on the bed up to get the bolt to clear. 

  • 2 years later...
Hystiker Enthusiast

Hystiker

Posted
Posted

Did you ever identify an issue with your front ride height?  Or did you put on a leveling kit and call it good?

 

I've got a 6" differential F/R and trying to sort the cause of the low front end.  

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

    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...