Jump to content

2014+ Lowering / Drop Kits

mjw930

By mjw930
in Modifications & Accessories

 Share

Recommended Posts

Darth_Vader Enthusiast

Darth_Vader

Posted
Posted (edited)

McG spindles have been that way forever, the 17+ spindles will always need the ball joint trimmed. Lol... 17" wheel is a 17" wheel whether spare or not. You could always swap the wheels on the side of the flat and put the spare on the rear.

 

You mean too long going from 6-7, spec out shorter bilsteins. This part #33-062518 can use the same bushing/sleeves from current ones and 2in shorter.

 

Out of the box they're same size, not labeled L or R. When installing the rear shock passenger side appears to be longer if the truck is in the air; if the truck is on the ground they're same length eye-to-eye.

I can promise they are not the same length on the ground, when I measured them last I pulled my truck up on my 4-post, ran it up and measured them without ever jacking a part of the truck up. The passenger side is around 1" longer. Edited by Darth_Vader
  • Replies 3.4k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Heavy_Static
Heavy_Static

A few pics from last week:    

bakerrr
bakerrr

First post here Picked her about 2 weeks ago couldn't wait to start modifying it. Just installed Belltechs 4/7 drop this weekend It's low enough for the time being ??  

Nasty
Nasty

Posted Images

Nasty Senior Enthusiast

Nasty

Posted
Posted

Thanks for the part number. But I think I need even shorter because I'm going 8 in the rear as soon as my notch gets here

wuznme Enthusiast

wuznme

Posted
Posted

Check out Ridetech shocks, they are made by Fox...They will have shorter ones and they're good shocks, ran them on my bagged truck

07Softail Senior Enthusiast

07Softail

Posted
Posted

I can promise they are not the same length on the ground, when I measured them last I pulled my truck up on my 4-post, ran it up and measured them without ever jacking a part of the truck up. The passenger side is around 1" longer.

 

It's because of the pinion angle that one shock is shorter, The axle is tilted to get the angle right.

 

RT

wuznme Enthusiast

wuznme

Posted
Posted

I know at one time (probably when eff'n around with the crappy DJM flip kit) that they where the same length, depending which way your pinion is pointed will determine the amount for one side being longer/shorter than the other.

 

Nose down will always make the passenger side longer

Nose up will make the driver side even/longer depending how much it is pointed up.

 

The shock isn't shorter, what is stated above will determine the shock mount being shorter/longer.

Silver ice 6.2 Senior Enthusiast

Silver ice 6.2

Posted
Posted

Damn that...The Belltechs suck dirty ass!!

 

RT

I'm extremely picky on lowering kits and shocks... the belltech nitro's suck.. but these street performer's are awesome..
Silver ice 6.2 Senior Enthusiast

Silver ice 6.2

Posted
Posted

It's not the ride. It's the length

.. I'm a 7 inch drop out back.. shocks fit... I thought you were a 7 inch drop out back aslo?
Nasty Senior Enthusiast

Nasty

Posted
Posted

I am but they're a bit short I think and I'm going to 8-8.5 now

Darth_Vader Enthusiast

Darth_Vader

Posted
Posted

 

It's because of the pinion angle that one shock is shorter, The axle is tilted to get the angle right.

 

RT

I was wondering about that, but seemed like a big difference for only a couple degrees off center. I've always wondered if it caused the shocks to behave differently, suspension man I am not.

Nasty Senior Enthusiast

Nasty

Posted
Posted

I am extremely happy with the bilstien ride. Just need a shorter length. I would recommend them to anyone

DirtyMarcus Enthusiast

DirtyMarcus

Posted
Posted

Mine said there could be an issue with 17's but nothing about you'd be in a situation with your spare, lol.

This is true. I didnt know our spare was 17" lol.

wuznme Enthusiast

wuznme

Posted
Posted

I am extremely happy with the bilstien ride. Just need a shorter length. I would recommend them to anyone

 

 

 

I think you'll be good with the 2inch shorter Bils, the Belltechs are spec'd up to 7in drop and they are 20.5 which is what the Bils you have now are.

 

Or Ridetech's but they $135 or $185 a pop...

  • Like 1
Nasty Senior Enthusiast

Nasty

Posted
Posted

Which ride techs? If they are adjustable I don't mind spending the money

 

And would I have to swap out the bushings and sleeves?

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

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...