Jump to content

Recommended Posts

Posted

He's wanting to run 35's, that kit says 33's are the max.

 

 

Sent from my kayak

 

Realistically, that's a conservative recommendation. There are many people on here with 35s and a 4" lift. Most of the 4" lifts recommend only a 33 though. It's doable, just not as guaranteed as the 33s, since there may be trimming involved unless there is proper offset.

  • Like 1
Posted

I was replying to my question, not CMSearle2.

 

I think I may opt for bilsteins and a 0.5" front spacer and small rear block.

 

10-4, misfire on my part.

 

Realistically, that's a conservative recommendation. There are many people on here with 35s and a 4" lift. Most of the 4" lifts recommend only a 33 though. It's doable, just not as guaranteed as the 33s, since there may be trimming involved unless there is proper offset.

 

I'm glad you cleared that up! I'm no lift expert, have been following this thread to educate myself on what route I want to follow, and it kind of confused me as to why it said 33s when you can fit those with a small level.

Posted

I know zero about body lifts. I reallllllllly want to run the C rated Raptor 315/70R17 KO2's, as they are cheap, light and I don't need an E tire as I don't tow/haul anything with great frequency that would require them.

 

I'm planning on coilovers to lift/level and greatly improve ride quality. From what I've read, coilovers, proper backspacing and even hefty trimming will not be enough to run these undersized 35's. I don't want to go with a full 4-6" suspension lift so I'm considering coilovers and new UCAs plus a 1.5" body lift.

 

Will a body lift defeat the purpose of going for coilovers to improve ride? I care more about ride/performance than I do looks.

 

Just wondering what, if any, the negatives are of a 1.5" body lift.

I'm running a body lift and leveling kit with no issues. It is also way less expensive and invasive on a truck than most suspension lifts if you're only looking to get 3.5" - 4" of lift. That being said, you're going to have issues with the width of the tires you're looking at with anything less than 5" of lift. You may be able to trim your way out of it, but there's no way to tell for sure until you put them on. If you decide to put a suspension lift then I would recommend the Zone 4.5" or Rough Country 5" knuckle lift. The BDS, Fabtech, and McGaughy kits are all great kits if you're planning to do extreme offroading, if not; then you're wasting money.

post-168372-0-45300700-1487023054_thumb.jpg

post-168372-0-45300700-1487023054_thumb.jpg

post-168372-0-45300700-1487023054_thumb.jpg

post-168372-0-45300700-1487023054_thumb.jpg

Posted

I'm wanting to get the fabtech 4" lift for my 2015 Silverado 1500. Anyone have this set up already that could tell me if it's a good set up?

  • Like 1
Posted

I'm wanting to get the fabtech 4" lift for my 2015 Silverado 1500. Anyone have this set up already that could tell me if it's a good set up?

its more of a glorified leveling kit......

 

 

Sent from my iPhone using Tapatalk

Posted

So I'm going to get a suspension kit this spring for the truck. Looking at 4 inch as it is the state legal max. But I'm curious do people have issues parking in parking garages or in other enclosed venues? Or do you avoid it?

 

Sent from my Pixel XL using Tapatalk

Posted

So I'm going to get a suspension kit this spring for the truck. Looking at 4 inch as it is the state legal max. But I'm curious do people have issues parking in parking garages or in other enclosed venues? Or do you avoid it?

 

Sent from my Pixel XL using Tapatalk

i avoid parking garages

 

 

Sent from my iPhone using Tapatalk

  • Like 1
Posted

Crappy pic, but this was right after it pulled out of the garage last night. 4.5 zone with fox in the rear, 35x12.50r20 nitto ridge grapplers on stock elevation rims. Ride seems better then stock, if that's even possible. I went back and forth on 4.5 and 6.5 and because I hunt out of the truck quite often , I went with 4.5. For me, it's the perfect height. I'll take some better pics when I get time.

 

803159D1-880B-4391-B10F-CB4C4D5AE74C_zps

  • Like 11
Posted

Crappy pic, but this was right after it pulled out of the garage last night. 4.5 zone with fox in the rear, 35x12.50r20 nitto ridge grapplers on stock elevation rims. Ride seems better then stock, if that's even possible. I went back and forth on 4.5 and 6.5 and because I hunt out of the truck quite often , I went with 4.5. For me, it's the perfect height. I'll take some better pics when I get time.

 

803159D1-880B-4391-B10F-CB4C4D5AE74C_zps

Looks great. How bad of a hit did the mileage take?

 

Sent from my SAMSUNG-SM-N910A using Tapatalk

Posted

So I'm going to get a suspension kit this spring for the truck. Looking at 4 inch as it is the state legal max. But I'm curious do people have issues parking in parking garages or in other enclosed venues? Or do you avoid it?

 

Sent from my Pixel XL using Tapatalk

I have a 4 inch BDS and haven't had any issues in parking garages. That being said, I generally avoid them if I have another option, but that has more to do with the width of the parking spaces as opposed to the height of the garage. Keep in mind, you're not necessarily lifting your entire truck by four inches. e.g., you might lift the front 4 inches, and the back 2.75 inches. And, the height you gain with tires should be about 1/2 the increase ..... For example, if you go from a 33 inch tire to a 35 inch tire, your truck is not sitting 2 inches higher. Plus, a lot of tires aren't really the height indicated. My 33x12.5 are not 33 inches tall - they're shorter. Likewise, I looked at a 34x12.5 from BFG, and it was actually 33.5 inches. There are folks on here with a ton more knowledge on this stuff than me, but those are my observations FWIW.

  • Like 2
Posted

I have a 4 inch BDS and haven't had any issues in parking garages. That being said, I generally avoid them if I have another option, but that has more to do with the width of the parking spaces as opposed to the height of the garage. Keep in mind, you're not necessarily lifting your entire truck by four inches. e.g., you might lift the front 4 inches, and the back 2.75 inches. And, the height you gain with tires should be about 1/2 the increase ..... For example, if you go from a 33 inch tire to a 35 inch tire, your truck is not sitting 2 inches higher. Plus, a lot of tires aren't really the height indicated. My 33x12.5 are not 33 inches tall - they're shorter. Likewise, I looked at a 34x12.5 from BFG, and it was actually 33.5 inches. There are folks on here with a ton more knowledge on this stuff than me, but those are my observations FWIW.

 

What's the height of your roof now? Basically what I mean is, what clearance is required for you to be able to get into a parking garage.

 

I'm only asking because this is the lift I am considering..

 

Thanks

Posted

 

What's the height of your roof now? Basically what I mean is, what clearance is required for you to be able to get into a parking garage.

 

I'm only asking because this is the lift I am considering..

 

Thanks

I just went outside and tried to eyeball it with a tape measure, but no level - looks like about 76 inches. I'll try to get a more definite measurement when I get home tonight.

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

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