Jump to content

3.5 inch lift. Tire sizes??

Tyler Shelley
 Share

Recommended Posts

Tyler Shelley Enthusiast

Tyler Shelley

Posted
Posted

I have a 20 Sierra Elevation with a 3.5" Rough Country Lift. I swapped my factory wheels with a co-worker for some 20x10 with a -24 offset. He has some "what looks small" 285/55 R 20 tires on it know. What tire size do you recommend. My main question is what is the largest tire size I can run 

Screenshot_20200120-195328_Gallery.jpg

Dunn Senior Enthusiast

Dunn

Posted
Posted

look at thread below yours with 3' RC lift by chris walker

Flatblack83 Enthusiast

Flatblack83

Posted
Posted (edited)

Depends on do u want taller or wider..?  On chevys they go to 295/60/20 =34x11 or 305/55/20 =33.5-12.50 both these sizes are popular on here. Some fit 35s but trim.  So on yours they use a little smaller with the wheel well shape. I'd measure it and see is a 295 60 would fit. That gives u a little width plus the heigth.

 

 

Edited by Flatblack83
Tyler Shelley Enthusiast

Tyler Shelley

Posted
  • Author
Posted
14 hours ago, Flatblack83 said:

Depends on do u want taller or wider..? Go to 295/60/20 =34x11 or 305/55/20 =33.5-12.50 both these sizes are popular on here.

 

I have 295 60s with a 3 inch on stock 20s, no rub.

I was looking into 295/60R 20 but i dont have factory wheels. My wheels have a -24mm offset. I think I will buy a set of that size and try them. They are barely wider than what I have but taller than what I have now. The hight is what I'm  after. The width is what is worried about. 

Tyler Shelley Enthusiast

Tyler Shelley

Posted
  • Author
Posted
3 minutes ago, Flatblack83 said:

Take a look at the custom offsets gallery,  lots of wheel n tire combos on there.

I looked at them. They have a lot for the previous gen trucks but they dont have a lot for this gen. If they do, I can't find it. I traded my factory wheels for these with my co-worker. I can trade back with no problem, but I really like the way the wheels look, but the tires look to small

Flatblack83 Enthusiast

Flatblack83

Posted
Posted (edited)

There is a few GMC 1500s, not sure on your package tho.. Most with a 20x10 with a 3-3.5 lift have 33-12.50-20 or 305 55 20.  The 6 plus inche Lift most are 35-12.50.  

 

Turn the wheels and measure how much room you have, that will give you a basic measurement on how  tall/wide you wanna go. An inch taller looks like it would help you a ton. Remember an inch taller is a 1/2 inch bigger all the way around...really isn't much.

Edited by Flatblack83
  • 1 year later...
Matt1072 New Member

Matt1072

Posted
Posted

I've got the same truck just different color. It's getting the 3.5 rc lift today..  what size tire did you end up going with? I've got 33/12.5 r20's to put on it but thinking I have to buy different rims. Kind of sad cause I hate to get rid of my ballistics rims.. 

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