Jump to content

Recommended Posts

Posted (edited)

Haha thanks man! And oh hell no, my OCD drove me insane for the. 1 week I had to wait for my spacers to come in to match the track widths! Lol.

I have the RCX 6" knuckle lift

Same, I am a crew chief on F15s and we have to be anal and ocd in order to make sure the jets are ready to go and to be honest the front track width difference with this kit is not worth it for me to put the extra strain on the hub with a spacer. I ran alot of spacers on my cars while I was in Japan and they got on my nerves of how many times I had to retorque them from coming loose granted most spacers here are hub centric which is a plus but Japan put a bad taste in my mouth for spacers haha how do you like that kit so far? Edited by Pooj
Posted

I just got a price from a local shop for a 6" lift with 35" Mickey Thompson ATZ's and 20x9 Ultra Gauntlets

With a BDS kit it would be 4,800 with a Full Throttle kit it would be 5,200 installed. How do those prices sound?

Posted

Pretty good because from what I can find that's 1600-1800 in just tires. Wheels (not a fan/familiar with Ultra's) probably 800 +/- and the bds kit is 2400-3200 depending on configuration

Fts just add more $$$$ haha

Posted

Before and after of 6" BDS lift with Toyo RT 35x12.50r20 tires with stock 20x9 wheels. I used the block lift option in the rear with no leafs or spacers. There is no rubbing or trimming required. I also replaced the stock chrome side step with the AMP power steps. I'll post more pictures when I take it out for some light break in off road! There is a slight rake to the truck (rear is an inch lower than the front when measuring center of wheel to fender. I might do an add a leaf to make it level; especially since I tow.

 

 

 

 

post-136911-0-41889700-1462331302_thumb.jpg

post-136911-0-41889700-1462331302_thumb.jpg

post-136911-0-41889700-1462331302_thumb.jpg

post-136911-0-41889700-1462331302_thumb.jpg

  • Like 2
Posted

Love it!

Before and after of 6" BDS lift with Toyo RT 35x12.50r20 tires with stock 20x9 wheels. I used the block lift option in the rear with no leafs or spacers. There is no rubbing or trimming required. I also replaced the stock chrome side step with the AMP power steps. I'll post more pictures when I take it out for some light break in off road! There is a slight rake to the truck (rear is an inch lower than the front when measuring center of wheel to fender. I might do an add a leaf to make it level; especially since I tow.

 

 

 

 

  • Like 1
Posted

Finally had some time to take a few photos since I got her back. I'm pretty damn happy! 9" McGaughys suspension, 1.5" Zone body lift, 37x13.50r22 Toyo MTs, and 22x12-44 Fuel Maverick D260 wheels.

Hey dude sweet ride, think you could have cleared the 37's minus the body lift?

Posted (edited)

I have a Question I am really baffled by. I am looking at a set of Fuel Beast wheels to put on my 2015 Sierra . I already have a Rough Country 2.5" level kit on my truck. I want to get a set of BFG AT K02 tires as well. the wheels I am looking at are the 20x10 -18 offset . what's the biggest tire I can get on these without rubbing . I was thinking of 25/65r20's or 295/60r20's but i'm not sure if that's too much sidewall or not for just a 2.5" lift/level. Has anyone done this or have any input. I was hoping the -18 offset would allow me to run these .My end game plan is to run a 6" Fabtech or BDS lift but I just want something to hold me over a year or so till I can scrounge up the extra cash.

Any info on this would be greatly Appreciated.

Edited by 2015SLTSierra
Posted

Hey dude sweet ride, think you could have cleared the 37's minus the body lift?

You will have to cut the front bumper a bit on a gmc depending on wheel width and also the wheel well arches. But it will clear 37s with 9 inch wide wheels and possibly 10 wides with minor cutting

Posted

You will have to cut the front bumper a bit on a gmc depending on wheel width and also the wheel well arches. But it will clear 37s with 9 inch wide wheels and possibly 10 wides with minor cutting

Ya I may do it and go with 37s on factory 20s I think 35s and 6 is 1. Crazy coming from a Ford F-150 & then dodge dually 2. Over done. No one runs narrow'ish 37s anymore.

Posted

Ya I may do it and go with 37s on factory 20s I think 35s and 6 is 1. Crazy coming from a Ford F-150 & then dodge dually 2. Over done. No one runs narrow'ish 37s anymore.

Im pretty sure you have to get spacers for the stock wheels cause of the offset and backspacing on them brother.

Posted

Well according to the track width movement at 9" of lift it should be poked out over stock 3/4"-1" so if anything would be needed I could probably throw a 1/4" spacer up front and a 1.25" in back and be dead even track to track and clear everything suspension wise, UCA, Sway bar, and Tie Rod end but that's just an on paper discussion. How's it ride at 9" ? I don't want a body lift because ill be doing the Iron cross full replacement front bumper and a winch and extension brackets plus replacement bumpers don't mix especially when you start winching on them.

id like to keep factory wheels for one reason and one reason only. Save Money! plus the look of a Big Factory'ish truck looks sick to me sleeper status....+9".....

I also don't want the SS kit I want the silver components and less flash. Not a big fan of big and flashy definitely with the way I use my truck just like the Big part !! could you post some pics of driver and passenger side CV and balljoint angles and also the height to the top of the tailgate with it in the down(open) position?

Posted (edited)

Just picked up from the dealership 2016 Midnight Edition. I had the dealer put on a level kit and 33's with the deal. I have had it only 24hrs and I am ready to go higher....lol

post-157853-0-40808600-1462393006_thumb.jpg

post-157853-0-40808600-1462393006_thumb.jpg

post-157853-0-40808600-1462393006_thumb.jpg

post-157853-0-40808600-1462393006_thumb.jpg

Edited by missouri_sooner
  • Like 2
Posted

Ya I may do it and go with 37s on factory 20s I think 35s and 6 is 1. Crazy coming from a Ford F-150 & then dodge dually 2. Over done. No one runs narrow'ish 37s anymore.

 

 

Im pretty sure you have to get spacers for the stock wheels cause of the offset and backspacing on them brother.

 

Na, You can run factory 20's with the lift no problem. No spacer needed to clear anything. You'll want a spacer for the back to even the track out, but its not a necessity.

Posted

 

 

 

Na, You can run factory 20's with the lift no problem. No spacer needed to clear anything. You'll want a spacer for the back to even the track out, but its not a necessity.

McGaughys told me at 9 inches it will only clear a 0- -22 offset with a 9 to 10 inch wide wheel and stock wheels require spacers on 37s. Stock wheels are 9 inch wide with I believe +27 offset.

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