Jump to content

Recommended Posts

Posted
3 hours ago, George Rojas said:

Im sorry no i bought the rims and tires from a friend he had them on 2018 silverado i just  install them as is I did not get them balanced or anything else I just installed them on the truck.  so I assume that's the problem. 

One of 2 problems. First off, 2018 GM truck sensors won't work on the 2019. 2nd is there may not be sensors in those wheels.

Posted
4 hours ago, George Rojas said:

Im sorry no i bought the rims and tires from a friend he had them on 2018 silverado i just  install them as is I did not get them balanced or anything else I just installed them on the truck.  so I assume that's the problem. 

Even if they came with sensors installed for the 2018 truck they will not work with your 2019.

 

If you want the sensors to work you need to buy new sensors and have them installed replacing the sensors in your new wheels, then you have to program the truck to listen to them.

Posted
33 minutes ago, Daverado said:

Even if they came with sensors installed for the 2018 truck they will not work with your 2019.

 

If you want the sensors to work you need to buy new sensors and have them installed replacing the sensors in your new wheels, then you have to program the truck to listen to them.

I see ok thank you for the info i will have to buy new sensors i really  appreciate the feedback.

Posted
On 1/15/2020 at 6:17 AM, BigBadSierra said:

20's would have never done this.  Destroyed two that cost 3K to replace on my 16 Sierra

I'm getting new summer rims for my 2018 Silverodo but staying with the stock rim size. The 20's ride better and I don't have to worry about the curbs.

Like other stated way more tire choices. You can buy top of the line tires for the 20's for less then anything that fits the 22 inch rims.

spacer.png

But is it really the rims or was it the driver ??✌️

  • Like 1
  • Confused 1
Posted

I replaced my rims from the 20 inch stock rims to the 22 inch Chevy rims. I put on about 5K miles on the 20s and about 7K miles on the 22s. I drive mostly on the highway so haven't noticed a difference besides the fact that I watch out for the curbs a little more. Also, it is slightly heavier than the 20s. I still have my 20s and plan to change them out during the winter time for when I take it up the mountains because I don't trust these tires in the snow. However, I haven't done it for this season and just kept the 22s on there.

 

 

3BDB3E70-5406-45A9-B601-A351668B3066.JPG.c0e8dfcb19a1b6929af03ed721401eeb.JPG

  • 6 months later...
Posted
On 1/29/2020 at 5:11 PM, Yondu said:

Don't get so defensive, it wasn't meant as a personal attack. It's my opinion big wheels look bad on a truck, sounds like it's yours that big tires look bad on a truck.  If you lowered your truck and put it on 22s and use it for work you're in the .1%. Most trucks with 22s are  bro'd out with a level kit and mud tire super swampers.  Not a scratch in the bed either as the owner doesn't use it. 

 

I bet you're in one of those warm states too, if you lived where the temp has 150 degree of fluctuation you're roads would be pretty bad and you may rethink those 22s. The roads I drive don't play well with that setup.  

 

 

Bro'd out???????????????????

Posted (edited)

Big wheels are only way to go for me. If there was a way to reprogram speedometer in these new trucks without spending thousands of dollars, I’d have 26s on them. I love huge rims. Makes the truck look very aggressive and more of a sport truck!  
smaller diameter rims and larger mud tires look like a kids “Powerwheels” to me. 

Edited by TNTSilverado
Posted (edited)

With all other things being equal, lower profile tires will rider firmer/harsher. How much, depends on the particular vehicle and suspension. For example, a good air suspension can compensate quite well. I'd suggest driving a few back-to-back on a dealer lot and it's easily noticeable. Given I'm staying on pavement, I'd normally go 20's for a full-size truck as a good balance between looks and practicality. 

 

But I went 22's because, you know, "Denali Ultimate." 

Edited by omegafiler
Posted
On 10/29/2020 at 10:00 AM, Wmoor004 said:

Bro'd out???????????????????

The truck the bro's drive.  The guys that have popped collars, call their buds bro.  They usually wear Oakley sunglasses, love Affliction.  There trucks are lifted, 22 or 24's with mud tires and really low offset. You might find them with multi color headlights and highly customized trucks that in their attempt to make them look tough made them quiet fragile.  Look under the truck for 10" lift blocks too.  More often than not the truck is white for some reason...clean I think?  They love black wheels with machined accent, or all chrome.

 

There will typically be a visor or a unworn ballcap of some sort hanging from the rear view too.  

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

  • Latest Articles

  • Posts

    • 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?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...