Jump to content

Want Some Meat On My Stock Wheels?

phil69

By phil69
in Tires, Wheels & TPMS

Recommended Posts

phil69 New Member

phil69

Posted
Posted

Hey I am new on here and been seaching all evening. I would like to put some meat on the truck with stock wheels and no level kit if possible. I like the Good year Wangler duratrac. Will a 285/60/20 fit with no rub? How about if I level it how big can I go?

 

Thanks guys :D

Elboman Enthusiast

Elboman

Posted
Posted

2008 GMC C1500

Original tire size is 275/55/20

Just put 305/50/20 Yokohama Parada Spec-X's on. The spedo matches perfectly with my GPS. Tires are about an inch and a half wider. I like the look but not much bigger than stock. Same diameter just wider.

http://www.tirerack.com/tires/tires.jsp?ti...romCompare1=yes

 

After mounting them on the stock rims in my driveway, I drove them about 5 miles to Walmart to get them balanced. All seems good so far.

Hope this helps you in your decision making.

Good luck.

Elboman Enthusiast

Elboman

Posted
Posted

No leveling kit. All stock 2wheel drive tires fit fine and no rubbing full left to right turn. Have about 40 miles on them now and no complaints.

Elboman Enthusiast

Elboman

Posted
Posted

2008 gmc c-1500 305/50/20 parada spec x on factory 20" wheels

400 miles now and all is good. My factory splash gaurds come the closest to touching on the right side with a half a turn back off the steering wheel from full right. I have about 1/4 inch clearance at that point. All is well, quiet, smooth and look good. Just a bit less gas milage I believe. Time will tell.

Elboman Enthusiast

Elboman

Posted
Posted

Wow. Sure enough. Gas mileage suffering from the 305/50/20's. After almost two weeks of driving back and forth to work I am averaging about 21.3 mpg. I use to get 24 to 25 mpg. I drive through the Blackwater river state forest. Cruse set at 45 mph. It is hilly and a few stops. 35 miles each way. I think the big difference is my truck doesn't seem to run in the 4 cylinder mode on level ground at 45 mph anymore. The tires seem to add just enough drag to make that difference. Don't know what the difference would be at 55 or say 65 mph. Probably not as big a difference because even with the factory goodyears the truck wouldn't run in 4 cylinder mode on level ground at speeds above 55. It is a dissapointing side effect but still worth the better looks.

mc7719 Enthusiast

mc7719

Posted
Posted

I believe with the 2" level kit, you can go 285/55R20 or 275/65R20 with no rubbing at least from what I've read on here...

jsciaretta Enthusiast

jsciaretta

Posted
Posted

you cant fit a 275/65 with the levelling kit. It will rub. 285/55 and 275/55 are close in size. I have a rc spacer and 275/60 and i rub when locked or wheels turned and suspension flexs a good bit from a bum.

Elboman Enthusiast

Elboman

Posted
Posted

305/50/20 on stock rims.

Ahh just heard a rubbing sound from the front today.

Further inspection and testing found out on a down hill grade with wheel turned all the way to the right and the brake applied it would cause the front right wheel to be pulling on the tie rod as appose to normaly the tie rod pushing the wheel, I would rub the inside of the sidewall just a bit on the smooth part of the front sway bar on the right side. No harm other then the paint might rub off of the swaybar after a while. But some of you, depending on your front end alignment, might rub more or not at all.

It is just a darn close fit!

Archived

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

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