Jump to content

Recommended Posts

Posted

Welcome to this forum!  You will find some very helpful information on this site.  The question you have asked is a popular topic and using the search feature will save you some time.  BTW I am not a fan of this forum's search feature and use Google's instead.  

Posted

Haha, I’ve asked this question also. It does seem like the collective knowledge base here could provide a quicker answer. Probably would take less time to type 275/60/20(not the answer). [emoji23][emoji23]

 

I’ve researched, and haven’t necessarily found a 100% solid (to me) answer. Depends on rims too, and the height of mine after leveling isn’t as high as some I’ve seen, measured from ground to fender. So, I’ll probably be conservative and go rims and stock sized, more aggressive tires. I don’t want to trim anything.

 

 

Sent from my iPhone using Tapatalk

Posted

I still cannot figure out two things. One is the search on this site is not very precise. How do you use google search instead?

Posted

Also, I have the same tire fitment questions everyone has. What to know what is the largest tire I can fit on 18 in rims with my 2020 AT4? Can I do 285 or 295 /70's or 75's. I know the speedo will be off a bit, but I am looking for a slightly different ride. Like the one on my old 2006 HUMMER H2. 

 

I know makes no sense, but its what I like....

 

TomD

Posted
56 minutes ago, Tom D said:

I still cannot figure out two things. One is the search on this site is not very precise. How do you use google search instead?

For example, in the Google search box type 2020 silverado max tire size gm forum  You will get plenty of hits including this thread.

Posted

I put 275/65/20 Goodyear Ultraterrain on my 19 Silverado LTZ with a ready lift level kit and have no rubbing at all. Basically a 34"x11.5"x20"

  • 2 weeks later...
Posted

well i went with 2" rough country with 33x12.50 on factory wheels and i think it turned out perfect!!! thanks for the suggestions

2146964618_banda.thumb.jpg.ccaaeb854a9134418f423db0e8656b9d.jpg

Posted

Looking good, a more aggressive tire on a nice aluminum rim that isn't a 20 looks excellent (more tire less rim is best). It looks nose high, I take it you didn't add a rear block to keep some rake? Also did you adjust your headlights down? That is going to piss off on coming traffic quite a bit...

 

Tyler

Posted

Your truck turned out great, I really like that look. Very clean. I would also encourage you to adjust your headlights slightly. Simple phillips head screwdriver and 30 seconds of your time.

 

I know there's a lot of these threads but I never get the answer I'm looking for. That's probably because nobody's done it-LOL. I want to add LT275/65R20 tires which sounds like the overwhelming popular size to go with when leveled. But I don't want the 2" level, I am only looking to increase 1.5".  For those of you that can look, say wheel fully turned and in reverse... how much room do you have until your kissing the liner/mud flap? Eye-balling it if your front was lowered by 0.5" (ie 1.5" level instead of 2.0") do you think it would rub? Tire size fit with minor trimming? Or have to do major trimming/or not fit at all.

 

Thanks. I'm towing more so want 1.5" up front and a 2.0" block in the rear to start with. This hopefully would get me just clear enough for better larger LT/E-rated tires and leveled when hooked to the trailer.

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

    • 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?
    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
    • Rockauto bud. I pass local stores for parts.   Findya something online. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...