Jump to content

Recommended Posts

Posted

I been running 35 psi on my 305-55-20 falken wildpeak. Is that a good number to stay in? I seen people running 50+. What's the difference if I put 50+?

 

2014 Silverado 2WT CC Summit White 4.3L V6

DROPKICK Edition

IG: jorge_dropkick_rangel

 

Are they P305/55R20's or LT305/55R20's? Typically LT tires would have 40-50 psi, sometimes more when towing or hauling a lot weight. P tires are normally less than 40 psi.

 

Looks like Falken might only make an LT version in 305/55R20.I'd start at 40 and adjust it from there.

Posted

 

Are they P305/55R20's or LT305/55R20's? Typically LT tires would have 40-50 psi, sometimes more when towing or hauling a lot weight. P tires are normally less than 40 psi.

 

Looks like Falken might only make an LT version in 305/55R20.I'd start at 40 and adjust it from there.

Yes they are LT. Might try putting them at 40 and see what it does.

 

2014 Silverado 2WT CC Summit White 4.3L V6

DROPKICK Edition

IG: jorge_dropkick_rangel

Posted

Anybody know where you can buy GM rims? I really like the chrome Denali rims and some of the other AT rims.

Besides that, what are some other good sites for other brands?

Posted

I been running 35 psi on my 305-55-20 falken wildpeak. Is that a good number to stay in? I seen people running 50+. What's the difference if I put 50+?

 

2014 Silverado 2WT CC Summit White 4.3L V6

DROPKICK Edition

IG: jorge_dropkick_rangel

I've got the exact same tires in that size on my truck. I usually have the PSI around 35-40 and anything more than that makes the ride super harsh in my opinion. Around town I like them at 35 and when I take a long road trip I'll pump them up to 40.

  • Like 2
Posted

I been running 35 psi on my 305-55-20 falken wildpeak. Is that a good number to stay in? I seen people running 50+. What's the difference if I put 50+?

 

2014 Silverado 2WT CC Summit White 4.3L V6

DROPKICK Edition

IG: jorge_dropkick_rangel

You should not run 50 psi on any size tire. 50 is Max psi (Blow up territory). If you are running at 35 psi cold, it will go up 2-3 psi, depending on how long you drive. With added weight you will go up another 2-3 psi. So the max you can put in your tires is 40psi. rule of thumbs for me is 10psi below max recommended.

Posted

You should not run 50 psi on any size tire. 50 is Max psi (Blow up territory). If you are running at 35 psi cold, it will go up 2-3 psi, depending on how long you drive. With added weight you will go up another 2-3 psi. So the max you can put in your tires is 40psi. rule of thumbs for me is 10psi below max recommended.

 

Depends on whether the tires are P-metric or LT's. His are LT load range E's with a max inflation of 65 psi. You'd be correct if he had P305/55R20's.

  • Like 1
Posted

 

Depends on whether the tires are P-metric or LT's. His are LT load range E's with a max inflation of 65 psi. You'd be correct if he had P305/55R20's.

You Sir are correct, my bad.

Posted (edited)

The new skins are on! BF Goodrich All Terrain KO2's. LT275/70/R18 with 2" level kit. Much better.... :)

 

20150811_194803_zpsvugm4xhw.jpg

20150812_172614_zpskxtpgp0w.jpg

Edited by fpdsniper
  • Like 2
Posted

The new skins are on! BF Goodrich All Terrain KO2's. LT275/70/R18 with 2" level kit. Much better.... :)

 

 

 

 

What is the actual size of that tire when mounted on the truck (true height, tread width, and section width)? Would like to see some low angle front and rear pics to see the full width of the tire if you could post them.

Posted

I have a 2015 Silverado and looking to put the Nitto G2s 305/55/20 on it. My question has to do with the tire pressure sensors and the vehicle diagnostics with OnStar. If I run around 10 lbs or pressure higher will it make any sort of tire light come in or show an error with OnStar diagnostics?

Posted

No you won't have an issue. I am running 42psi in my 35" tires and everything reports as normal.

 

I have a 2015 Silverado and looking to put the Nitto G2s 305/55/20 on it. My question has to do with the tire pressure sensors and the vehicle diagnostics with OnStar. If I run around 10 lbs or pressure higher will it make any sort of tire light come in or show an error with OnStar diagnostics?

Posted

 

What is the actual size of that tire when mounted on the truck (true height, tread width, and section width)? Would like to see some low angle front and rear pics to see the full width of the tire if you could post them.

 

Not the OP, but here you go:

 

275-70-18_zps0kd3qhhr.jpg

 

275-70-18-2_zpsib22bs24.jpg

Posted

 

What is the actual size of that tire when mounted on the truck (true height, tread width, and section width)? Would like to see some low angle front and rear pics to see the full width of the tire if you could post them.

Well, here's the low angle front, anyway:

 

20150811_193647_zps2suymzpx.jpg

Posted

Is a BFG KO A/T 285/65r20 to much for stock all terrain rims? Looks to be about 34"x11" so guessing I will have rubbing if stock height? Found a good deal on a set and hoping they will work

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

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