Jump to content

Recommended Posts

Posted
On 9/4/2020 at 4:43 AM, BetaX said:

I'm on that size tire but have the 2" SST. Very minor rubbing when turned going over a bump. Normal conditions, nothing.

 

 

What wheel offset?

Posted (edited)

No good ones but here you go.

 

285/75/18 Nitto Ridge Grapplers

Stock 18s

No wheel spacers

Zero Trimming.

Zero way to go any wider of a tire without hitting the Ready lift UCAs unless wheel spacers are added, which will probably cause more rubbing issues.

Only rubbing as mentioned above (Slight rub going over a bump at full lock)

 

Truck has a 1 to 1.25" rake with the 2" SST.

 

IMG_3562.thumb.JPG.13d17273d56a18f4269e56784a4b57b9.JPG

Edited by BetaX
Posted

Here is my 2019 with same Ready Lift SST kit.  Also some photos of clearance of stock 275/75/18's on  on Method NV's which are a 12mm offset versus 26mm for stock.  So 285's would be very tight with RL UCA - but there is more room with stock UCA's 

 

IMG_8828.thumb.JPG.4eea0193c4acb8c3ede59614fa68c684.JPG820113448_UCAGAP3.thumb.JPG.e8d86b6b8438931edd4234f266b76d86.JPG

Posted

For reference, here is my tire clearance with the RL UCA (Tire specs in above post). 

Note that the outter lugs on the tire are not offset in the image so clearance is less than shown.

I've articulated the suspension pretty well to check for rubbing and haven't caught any marks yet but it is certainly close. 

IMG_3572.thumb.JPG.2477add1b8edcdfa1d48dc44904684eb.JPG

 

I'm convinced on this size tire, it will 100% come down to actual tire selection and not all 285/75/18's will fit without wheel spacers. 

  • 2 weeks later...
Posted
On 9/4/2020 at 6:23 AM, Trailboss91 said:

Anyone successfully put 285/75r18 tires on a stock AT4? I am looking at this size in the Falken Wildpeak AT3/W, they measure out to 34.8” tall and 11.2” wide. 

They'll fit fine as long as you only drive in a straight line.  You WILL HAVE rub with the inboard front fender liner and "probably" in the rear of the fronts at the mud flap and/or liner.  I just installed 285/75/18 on OEM wheels on my AT4 with the Rough Country 1318 - 2" leveling kit and they just clear at full lock and no articulation.  I imagine if the suspension is heavily loaded while off-roading and near full lock I will rub the fender liner on the inboard side in the front.  It's really close without any articulation.  Tires I installed are the Toyo Open Country AT3 in 285/75/18 which are 34.8" x 11.3".  If I do rub it will be minimal and I can get a little more room if I zip tie the liner back as many have done.  Anything wider than 11.3" would cause me problems.

 

 

Image 1.jpg

Posted

Has anyone run 295/60-20 tires on a 20x9 wheel with near zero offset and a leveling kit?  Ive seen other AT4s running this tire on a stock wheel with 26 offset, but not sure if the ~1" shift in wheel position would cause rubbing.  I'm also concerned with the difference between no rubbing on the pavement and no rubbing while light off-roading.  I could go with the 285/60-20 and be fairly comfortable, but I wanted the 295.  If i go 295/55-20, im not gaining much in diameter and it sort of seems like im not using my money wisely.  Why cant there be a 295/57.5-20?

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

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...