Jump to content

Recommended Posts

Posted

With your 4" I'd bet you might squeeze 35s. What wheels are those? Look kind alike fuel dunes but not.

 

They are Moto Metals. Forget the model number though.

I like the dunes but they only come in twenty inch.

I really like the look of these rims the only thing is the valve stem is located in the middle of the wheel meaning special air chucks and tire gauges .

  • Like 1
Posted

e8u5a8e6.jpggu9umyhe.jpg

 

RC 2.5" Lift with 285/60/20 on Stocks No rub no trim

 

 

Sent from my iPhone using Tapatalk

  • Like 4
Posted

OK here ya go-


Helo wheels


Nitto Grappler All Terrains- 305/55R20


Offset -12


4" lift


No trimming and no rubbing


post-128289-0-52705400-1400341727_thumb.jpg

post-128289-0-74442400-1400341758_thumb.jpg

post-128289-0-52705400-1400341727_thumb.jpg

post-128289-0-74442400-1400341758_thumb.jpg

post-128289-0-52705400-1400341727_thumb.jpg

post-128289-0-74442400-1400341758_thumb.jpg

post-128289-0-52705400-1400341727_thumb.jpg

post-128289-0-74442400-1400341758_thumb.jpg

  • Like 3
Posted (edited)

2.5 Rough Country kit with rear blocks. Stock AT wheels with Toyo Open Country M/T 275/65/20=34.5x11. Slight rub on front wall but no trimming required IMO.

ja6emu3a.jpg

u6u6uqug.jpg

Edited by TX_AT
  • Like 10
Posted (edited)

Rough County 2.5" with rear blocks

275/60R20 Cooper AT3's

20x9 Rockstar 2's, 18 offset, no rub at all, no trimming required.

post-124245-0-93188900-1400379406_thumb.jpgpost-124245-0-23006800-1400379520_thumb.jpgpost-124245-0-64766700-1400379611_thumb.jpg

post-124245-0-93188900-1400379406_thumb.jpg

post-124245-0-23006800-1400379520_thumb.jpg

post-124245-0-64766700-1400379611_thumb.jpg

post-124245-0-93188900-1400379406_thumb.jpg

post-124245-0-23006800-1400379520_thumb.jpg

post-124245-0-64766700-1400379611_thumb.jpg

post-124245-0-93188900-1400379406_thumb.jpg

post-124245-0-23006800-1400379520_thumb.jpg

post-124245-0-64766700-1400379611_thumb.jpg

Edited by Cmillerjr
  • Like 3
Posted (edited)

Awesome trucks Everyone! I was wondering if anybody has pics of how much their rims and tires come out past the wheel wells. Im trying to get an idea of what will look too fat or skinny.

Edited by eft123
Posted (edited)

22 Inch Wheel - 5-Split-Spoke Ultra Bright Machined High-Gloss Black (CK160) - SEW

285/45/22 Bridgestone Dueler H/L Alenza

 

post-38565-0-61260700-1400469559_thumb.jpg

post-38565-0-83121800-1400469706_thumb.jpg

post-38565-0-61260700-1400469559_thumb.jpg

post-38565-0-83121800-1400469706_thumb.jpg

post-38565-0-61260700-1400469559_thumb.jpg

post-38565-0-83121800-1400469706_thumb.jpg

post-38565-0-61260700-1400469559_thumb.jpg

post-38565-0-83121800-1400469706_thumb.jpg

Edited by cansled
  • Like 1
Posted

Awesome trucks Everyone! I was wondering if anybody has pics of how much their rims and tires come out past the wheel wells. Im trying to get an idea of what will look too fat or skinny.

Here's mine 275/60R20, 20x9 wheels with a +18 offset. Hope this helps, I was looking for the same type of info before I bought my setup.

 

post-124245-0-01428900-1400470903_thumb.jpgpost-124245-0-76581400-1400470969_thumb.jpgpost-124245-0-61140100-1400471151_thumb.jpgpost-124245-0-45967000-1400471237_thumb.jpg

post-124245-0-01428900-1400470903_thumb.jpg

post-124245-0-76581400-1400470969_thumb.jpg

post-124245-0-61140100-1400471151_thumb.jpg

post-124245-0-45967000-1400471237_thumb.jpg

post-124245-0-01428900-1400470903_thumb.jpg

post-124245-0-76581400-1400470969_thumb.jpg

post-124245-0-61140100-1400471151_thumb.jpg

post-124245-0-45967000-1400471237_thumb.jpg

post-124245-0-01428900-1400470903_thumb.jpg

post-124245-0-76581400-1400470969_thumb.jpg

post-124245-0-61140100-1400471151_thumb.jpg

post-124245-0-45967000-1400471237_thumb.jpg

Posted (edited)

Awesome trucks Everyone! I was wondering if anybody has pics of how much their rims and tires come out past the wheel wells. Im trying to get an idea of what will look too fat or skinny.

My -12s poke out. pics on First page

Edited by Full Lock
Posted

Looks very good. Tire brand? Clearance issues? Do you remember your wheel offset?

aja4u6a6.jpg6a9anuhu.jpg
24x10 gm ck375 reps with 295/40/24

  • Like 1
Posted

Have had a few stages of mine:

 

2.5" Level

22x9 ET 31 GM CK375

285/50R22 Nitto Terra Grapplers

No Rubbing / No Trimming

20140309_181408_RichtoneHDR_zpshpzrn76q.

20140309_163922_RichtoneHDR_zpssc3pelut.

 

2.5" Level + 1.5" Body Lift

22x9 ET 31 GM CK375

285/50R22 Nitto Terra Grapplers

1.5" Wheel Spacers

No Rubbing / No Trimming

20140410_171128_RichtoneHDR2_zps23f8ff92

20140321_172117_RichtoneHDR_zpskneqfo8m.

 

 

2.5" Level + 1.5" Body Lift

20x10 ET -25 Ultra Lightning

33x12.50R20 Federal Couragia M/Ts

No Rubbing / No Trimming

NewFrontEndHDR3_zps7b91246e.jpg

NewFrontEndHDR2_zpsb76bf71a.jpg

20140505_194936_RichtoneHDR_zpsf7uu5eer.

 

Coming Soon...

3.5" "Lift" + 1.5" Body Lift

20x12 ET -44 TBD

33x12.50R20 Federal Couragia M/Ts

HOPEFULLY No Rubbing / No Trimming

  • Like 10

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...