Jump to content

Recommended Posts

Posted

What I’m reading is with a 2” level the widest you can go without rubbing would be a 285 but with a 60 aspect ratio.  This is for 20” wheels of course.

If you want to go to a 65 ratio you need to go slightly narrower with a 275 tire.

Jay Teez has  285/60’s

I have 275/65’s.  We both don’t have rubbing issues.

Bluerado has 285/65’s and has a slight rub in reverse at full lock.

We all have levels on our trucks.

Hope that helps.

Definently  helps me because once the tires I have now will need to be replaced I was considering going slightly wider to give myself a bit more rim protection but then I would have to go with a shorter tire.

I’ve kissed a few curbs and thankfully haven’t done any damage to my rims even with the 275’s!

The BFG’s do a good job deflecting the curb attacks!

  • Like 2
  • 4 weeks later...
Posted
741994584f0f80189e049a10a2e45923.jpg
285/65/20 with only 2 inch level from ready lift

About a 34.5 inch tall tire and 11.5 inches wide
Very light rub on plastic mud flap when reverse at full lock, not enough for me to trim.
How is the ride quality? Any issues?

Sent from my SM-G930V using Tapatalk

  • 5 weeks later...
Posted
What I’m reading is with a 2” level the widest you can go without rubbing would be a 285 but with a 60 aspect ratio.  This is for 20” wheels of course.
If you want to go to a 65 ratio you need to go slightly narrower with a 275 tire.
Jay ****** has  285/60’s
I have 275/65’s.  We both don’t have rubbing issues.
Bluerado has 285/65’s and has a slight rub in reverse at full lock.
We all have levels on our trucks.
Hope that helps.
Definently  helps me because once the tires I have now will need to be replaced I was considering going slightly wider to give myself a bit more rim protection but then I would have to go with a shorter tire.
I’ve kissed a few curbs and thankfully haven’t done any damage to my rims even with the 275’s!
The BFG’s do a good job deflecting the curb attacks!

The rub was almost nothing to be honest, I had to be full lock going in reverse and coming off a bad driveway angle. It was just touch but not even enough to cut whatever it touched


Sent from my iPhone using Tapatalk
Posted
On 4/6/2020 at 3:23 PM, Bluerado23 said:


The rub was almost nothing to be honest, I had to be full lock going in reverse and coming off a bad driveway angle. It was just touch but not even enough to cut whatever it touched


Sent from my iPhone using Tapatalk

Good to know.  I’ll probably consider 285/65 BFG KO2’s after I burn through my current set to get the wider/even more aggressive look.

Posted
On 2/7/2020 at 8:39 PM, madconcept said:

2019 Sierra Elevation, front level and 275/65R20 BFG KO2.  No rubbing.

 

A535A308-E52D-486C-A0EF-61F9C858FA6E.jpeg

3B4B6AF2-26EC-47A1-8CF6-92719FC05156.jpeg

Can you post a better picture of the front clearance? Want to see if A gator back mud flap will fit in there.

Thx

Posted
On 4/9/2020 at 6:29 AM, Vasa1 said:

Can you post a better picture of the front clearance? Want to see if A gator back mud flap will fit in there.

Thx

Clearance yo the factory front mud flap with the wheel straight.

I could take a pic with the wheel turned if you want.

26A8DFE0-FC45-4BC7-BC70-A0EDD343A961.jpeg

Posted

How big of tires can i go on my 22 inch rims on a RST stock,   thinking raw?appid=YMailNorrin&ymreqid=363a58d2-8about putting the TB lift on it and use the 22`s anyone have the black OEM  wheeels on?

Posted
2019 RST Z71 2 inch Southern Truck Level 
Stock 20 inch Wheels
285 60 20 Nitto Ridge Grapplers
No Rub!!! [emoji847]
4A58DBED-376F-488C-A42A-7086CA0EB21D.thumb.jpeg.d13c0df80324324afbf348792f7212eb.jpeg
That's a great looking truck! I love the RST and that color! Looks amazing!

Sent from my SM-N960U using Tapatalk

  • 3 months later...
  • 5 months later...
Posted

Have a 2020 Rst and looking to put fuel off road coupler 20 x 9 with +1mm offset on 275/60r/20 perelli at plus tires. Wondering if it needs to be leveled or if i can get away without it. Thanks

  • 2 months later...
Posted

Just an FYI . I just put 275x65x20 on my 2019 Silverado with a leveling kit in the front. I had to remove the mud flaps but that was ok as I'm putting on fender flares. 

Posted

I have the 2019 RST with a Rough Country leveling kit I'm running 275x65x20 on stock rims with the mud flaps removed with no problems.

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