Jump to content

How many trucks in your area have 20+" rims?


LikeaRock14

Recommended Posts

Posted

There's quite a a few around here actually. The local Chevy dealer across town actually has like 1/3rd of all their 2wd trucks lowered w/ like 20 or 22's put on before they're even up for sale, there's TONS of Burbs/ Ho's/ Yukons that have 22's on them. I was just driving around yesterday and realized "woah, there's a lot around here".

Usually I'm not a fan of them. but there's some decent looking ones out there. Me, I prefer 4" of lift w/ 35's :D

Posted

Probably half of the SUVs up here have larger aftermarket rims. There are always one or two on the local lots that have the rims on them. I like the 20-22" in size, when you can still have some tire sidewall....the larger "bling" rims are horrible IMO

Posted
Probably half of the SUVs up here have larger aftermarket rims. There are always one or two on the local lots that have the rims on them. I like the 20-22" in size, when you can still have some tire sidewall....the larger "bling" rims are horrible IMO

True. 20's and some 22's look very nice. It's the 24's and the others with spinners that crack me up. I saw a Ford Escape with spinners on it a few days ago.... :D

Posted

I'm thinking that my next set of wheels/tires are going to be 18"ers....But they will probably be 33" tall. :D

 

Gotta have a little sidewall for traction in the sand.

Posted

There are a lot of trucks around here that have 20's and a lot of them look really good. Although there are many that are focking ugly, and it seems that every Tahoe around here has 20's or 22's and has not been lower an inch. To me it would look better to lower it and cut down on that fender gap.

Posted

Zero

 

Us poor ol dirt farmers still haven't figured out how to make those things stand up when you get off the pavement or stand up to the loads that our trucks get while out there WORKING. :D

Posted
Zero

 

Us poor ol dirt farmers still haven't figured out how to make those things stand up when you get off the pavement or stand up to the loads that our trucks get while out there WORKING. :D

Yeah, I don't know how no sidewall would do in the dirt and rocks. :thumbs:

Posted

The last couple of months I have started seeing more and more around St. Louis.

 

I'm with the majority here, anything larger than 22's starts to look bad - not enough sidewall on the tire.

Posted
My friend at school dirves a Kia w/ Kragen spinner hubcaps :D

You should reconsider having him as a friend. :thumbs:

Archived

This topic is now archived and is closed to further replies.

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