Jump to content

Recommended Posts

Posted (edited)

The tires on my 19 are cracked to pieces. I'll be replacing them soon, but has anybody else seen theirs cracking like this? They'll be getting replaced soon anyway, but just wondering what everyone's thoughts were. Should I be worried about a blowout? 

 

Which brings me to my next question... which tire? I drive my truck for work quite a bit and get paid mileage, so MPG is a top priority. It's on pavement 95% of its life. What's y'all favorite smooth, quiet highway tire? 

20240306_094310.jpg

20240306_094318.jpg

Edited by juscuzram
Posted

Replace ASAP. 

 

Put on some Michelin Defender LTX M/S tires. Good street and highway tire. With proper rotations you should be able to get 80,000 miles out of a set. 

Posted
49 minutes ago, fondupot said:

Replace ASAP. 

 

Put on some Michelin Defender LTX M/S tires. Good street and highway tire. With proper rotations you should be able to get 80,000 miles out of a set. 

Yeah, I'll be swapping them in the next week or two. My dad swears by Michelin Defenders. They're a little more $, but I guess you get what you pay for. 

Posted

I would run them, especially if I wasn't towing or hauling anything heavy. I have driven on far worse. 

 

That being said, falken tires are popular here. My wife has the wildpeak at3/ws on her truck and she loves them.  My 23 has open range at's on it and they seem to be great. 

Posted

Yeah, the Michelin Defenders for highway pounding trucks. The new LTX M/S 2's are a nice tire.

Posted
2 hours ago, juscuzram said:

The tires on my 19 are cracked to pieces. I'll be replacing them soon, but has anybody else seen theirs cracking like this? They'll be getting replaced soon anyway, but just wondering what everyone's thoughts were. Should I be worried about a blowout? 

 

Which brings me to my next question... which tire? I drive my truck for work quite a bit and get paid mileage, so MPG is a top priority. It's on pavement 95% of its life. What's y'all favorite smooth, quiet highway tire? 

20240306_094310.jpg

 

 

I can see the wear bar is very-VERY close to cashing in this tire. I'd say you got your money's worth from this set and don't understand the complaint. You seemed to like this set well enough to use them up so buy a second set and be happy, don't worry. 

Posted

Looks like you never used any UV protection on the tires. If you don't like shiny, use 303 on them. 

  • Like 1
Posted

If you want quiet, Michelin Primacy.

Posted (edited)

These are the factory set, bought the truck last year with 26k on the clock. Closing in on 49k now. Just never saw a set crack this bad. Wondering if it's from the non-use that the truck got from the first part of its life. Not terribly worried about them, like I said I'm changing them anyway. They have a little life left in them tread depth wise, just want to swap before they get any worse, and while all the spring tire rebates are going on. 

Edited by juscuzram

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...