Jump to content

Recommended Posts

Posted (edited)
On 5/14/2018 at 12:41 AM, z71truck82 said:

Just confirming the black HD has 35x12.5x18 tires with no lift at all? That’s crazy. 

Correct, I'm running Bfgoodrich 35x12.5x18 on stock wheels w/ no lift or modification of any kind to the suspension.

 

I was originally concerned about clearance, but any shop I spoke with or post I read did not actually mount one and check clearance prior to lifting.

 

Will always consider a lift / spacers or new wheels but for now the rubbing is not an issue.

 

driver-side-.thumb.png.0b6e48a8ef99eb3e39855bbe5695e1c5.png

 

side-shot.thumb.jpg.cc7b5e815e754c7fece9cf649454b059.jpg

 

Driver side rubbing chassis at full lock

 

full-lock-rub-driver-side.thumb.jpg.6cc9355e7cf3a1eb2cd1b8e397eadba8.jpg

 

passenger side rubbing at full lock

 

full-lock-rub-pass-side.thumb.jpg.dcd9e2a8fee689c54be26244213d0fc2.jpg

 

Sway bar has no contact 

Edited by OpsWest
  • Like 2
Posted (edited)

Okay cool thanks. I ended up ordering 17x9 +18 offset wheels, and 295/70R17 tires (33.3”x11.77”). Hope it will all fit. Might give the torsion bar bolts like 2 full turns to get front end up about .5”. I tow a 7500k TT so want to keep the rake.

Edited by z71truck82
Posted
On 5/14/2018 at 2:24 AM, z71truck82 said:

Going to get after market 17s with at least an 18mm offset. Can you attach a link to your pictures please.

I"m guessing that was directed towards me. I don't have any pictures in my gallery, but here's a link to the build thread where I posted pictures of my truck along the way: 

 

Posted
On 5/19/2018 at 2:10 PM, z71truck82 said:

Last question...when you turned the keys did you jack up one side at a time or both? I think I will turn 4 times and see if the tires fit. Thanks

I did one side at a time, but there's no reason you couldn't do both, as long as you can find a good placement for the jack. 

  • 4 weeks later...
Posted

Just sharing my experience with my 2018 Silverado HD. With 20x9 wheels +18 offset and Nitto Exo Grappler 275/60/20 (measure 33.25x11), they fit with no rubbing on completely stock height. The tires come VERY close to rubbing on the thick gatorback mudflaps. Without the mudflaps (or maybe with a set of kickbacks), you may fit one size bigger tire with this offset wheel.

Posted
On ‎6‎/‎12‎/‎2018 at 10:03 PM, z71truck82 said:

Thanks GForce! Would you mind posting a picture, including the ones where we can see how much the tires stick out of the wheel well. Thanks!!

here's a couple pics. I'd say the tires stick out roughly 3/4" - 1" passed the fender well.

comp.JPG

truck8.jpg

truck9.jpg

truck10.jpg

Posted

Anybody know if I can fit Nitto Terra Grappler G2 295 60 R20's on a stock 2015 2500 High Country without doing anything to the torsion bars? 

 

And if it just needs a little adjusting with the torsion bars will it make it that much rougher of a ride?

 

Thanks!

Posted
On 6/20/2018 at 12:51 PM, czamarron5 said:

Anybody know if I can fit Nitto Terra Grappler G2 295 60 R20's on a stock 2015 2500 High Country without doing anything to the torsion bars? 

 

And if it just needs a little adjusting with the torsion bars will it make it that much rougher of a ride?

 

Thanks!

If you're keeping the stock rims, they'll probably fit without any lift. However, if they don't, then it won't take much torsion bar cranking to make them clear. And, as long as you keep the front lift at 2" or less (and add shock extensions) the ride will be just fine. 

Posted
Anybody know if I can fit Nitto Terra Grappler G2 295 60 R20's on a stock 2015 2500 High Country without doing anything to the torsion bars? 
 
And if it just needs a little adjusting with the torsion bars will it make it that much rougher of a ride?
 
Thanks!


If they don’t rub your going to be very close. I just put on the G2’s in 275/65/20 with aftermarket wheels at +15mm offset. I was very close to the front fender and would just rub the liner at the back with full turn. Your a little wider but with the stock wheels. Like the other post said if they do rub you probably won’t need much more to clear.


Sent from my iPhone using Tapatalk
Posted
On 5/15/2018 at 8:53 AM, OpsWest said:

Correct, I'm running Bfgoodrich 35x12.5x18 on stock wheels w/ no lift or modification of any kind to the suspension.

 

I was originally concerned about clearance, but any shop I spoke with or post I read did not actually mount one and check clearance prior to lifting.

 

Will always consider a lift / spacers or new wheels but for now the rubbing is not an issue.

 

driver-side-.thumb.png.0b6e48a8ef99eb3e39855bbe5695e1c5.png

 

side-shot.thumb.jpg.cc7b5e815e754c7fece9cf649454b059.jpg

 

Driver side rubbing chassis at full lock

 

full-lock-rub-driver-side.thumb.jpg.6cc9355e7cf3a1eb2cd1b8e397eadba8.jpg

 

passenger side rubbing at full lock

 

full-lock-rub-pass-side.thumb.jpg.dcd9e2a8fee689c54be26244213d0fc2.jpg

 

Sway bar has no contact 

good to see this. now im very much considering running a 35x11.5/20 with my stock 20s. (from research, they appear to be the same width and offest as your 18s. )

  • 4 months later...
Posted

I have a 2015 GMC 2500HD All Terrain with stock 18 inch wheels and 265/70r18 tires. What is that largest tires I can fit on these factory wheels without rubbing. I was thinking of the BFGoodrich All Terrain KO2 285/65r18. Thanks for you input

Posted

285 75r18 on 18x9 with a +12 offset, the offset had me switching the stock keys for aftermarket torsion bar keys, so I could get the tire off the front mud flap at full lock.

IMG_1725.JPG

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

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...