Jump to content

2019+up Wheels on K2 2014-2019?

newdude

By newdude
in Modifications & Accessories

 Share

Recommended Posts

newdude Senior Enthusiast

newdude

Posted
Posted

Has anyone done this yet?  I know in the T1 section there's a couple threads on mounting K2 wheels on the T1 trucks, and the calipers being wider and the need for a minor spacer in the fronts.

 

With that, going backwards, there should be plenty of clearance.

 

Any pics?  I can find K2 wheels on GMT900 and older trucks for days.  I was looking at either an 18" RST set, or the 18" accessory wheel that looks like the Colorado ZR2's wheel.  At this point, I'd even look at a picture of 20"s as well.   

 

Image result for gm 84040796

  • 2 weeks later...
uncledaddy Enthusiast

uncledaddy

Posted
Posted

I'm considering the same, wanting to put that new accessory wheel on a 2016 white Sierra All-Terrain. I'm a fan of the 17" Colorado ZR2 wheels, so those 18" ZR2 look-a-like accessory wheels have my attention.

image.thumb.png.0ab347d27d68b12413fb928f3084da1c.png

 

uncledaddy Enthusiast

uncledaddy

Posted
Posted

I haven't seen anyone mount them on a K2 yet, and can only find a few pictures of them on the new trucks. Just a few promotional images that GM released during the last SEMA show.image.thumb.png.4c9c49896627b0e7a4811105cb1d690e.png

2019-chevrolet-silverado-rst-off-road-concept-exterior-009.thumb.jpg.e950d17af4f1afe1cbedc173d548c53d.jpg

2018-SEMA-Chevrolet-Silverado-RST-OffRoad-Concept-005.thumb.jpg.d747d6a3895de19072703376f481e351.jpg

quickstang1 Enthusiast

quickstang1

Posted
Posted (edited)

I have 2019 wheels on my 17. There is a pic in this thread. Page 324. Sorry I don’t have the pic on my phone.

.

 

 

Edited by quickstang1
  • 2 weeks later...
newdude Senior Enthusiast

newdude

Posted
  • Author
Posted (edited)

Found it:

 

IMG_0499.jpg

 

Those look really good on there. 

 

Pretty sure I'm going to have to get some sort of T1 wheel for summers.  Either the one I posted above and is in the GM press shots above, or the set of 18" RST wheels we just took on trade. 

 

Edited by newdude
uncledaddy Enthusiast

uncledaddy

Posted
Posted

I'd like to have the ones in the press shots, but I'd hate to pay full price from GM. I'm already seeing like new T1 take-off wheels for sale at reasonable prices, but I doubt I'll find a set of those. I have yet to see them on any of the new trucks on the lots.

  • 3 weeks later...
  • 1 month later...
_level_ New Member

_level_

Posted
Posted

Hello newdude,

Any update your thoughts of the Grabber APT?  I'm looking at running the P275/70r18.

 

Thanks.

  • 3 months later...
stone150 Enthusiast

stone150

Posted
Posted

Added AT4 wheels wrapped in 275/65R18 Michelin LTX A/T2 tires to my 18'. Had to add 5MM spacers to keep the wheels from rubbing the UCAs
 

 

IMG_9771.jpg

  • Like 1
  • 2 years later...
Racindave Enthusiast

Racindave

Posted
Posted (edited)

I picked these up this week after my snowflakes started leaking. Honestly think I like the snowflakes better… I had never seen them before though. 

626B6E87-108E-4C07-B7B7-CEFC906D8010.jpeg

Edited by Racindave
  • 1 year later...
jrob56 Enthusiast

jrob56

Posted
Posted

Referenced this thread quite a bit when looking at T1 wheels to add to my K2, so I wanted to add mine here for anyone else looking. Tried the 18inch AT4 and looked pretty good, but didnt love it. Shortly after putting those on I ran across some 2023 Zr2 takeoffs and fell in love with them on Blue Granite. Taller than stock so some rubbing on fender liner at full lock, but Im only on a 1.85 level Bilstein 5100s.

zr2.jpg

zr22.jpg

newdude Senior Enthusiast

newdude

Posted
  • Author
Posted
37 minutes ago, jrob56 said:

Referenced this thread quite a bit when looking at T1 wheels to add to my K2, so I wanted to add mine here for anyone else looking. Tried the 18inch AT4 and looked pretty good, but didnt love it. Shortly after putting those on I ran across some 2023 Zr2 takeoffs and fell in love with them on Blue Granite. Taller than stock so some rubbing on fender liner at full lock, but Im only on a 1.85 level Bilstein 5100s.

zr2.jpg

zr22.jpg

 

 

 

Nice.  Those ZR2s look sweet. 

  • Like 1

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

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...