Jump to content

Recommended Posts

Posted (edited)

Hello all.

 

As some of you know by reading my other threads, I have been having seat vibration issues with my truck.

 

I am on my 4th set of tires and I think I finally found one that is a good combo of street comfort and still has a little bite for off road.

 

Went with E-rated: https://www.bridgestonetire.com/tire/dueler-at-revo-3

 

I had the Falken Wildpeaks AT3W and they required a lot of weight to balance. They are 61 pounds per tire, and these bridgestones are 48 pounds per tire and they're both E rated.

 

The bridgestones required very little weight.

 

Although my seat vibration issues have drastically been reduced with these new tires, I am still getting some seat vibration/feedback at anything over 65-70 mph even on the smoothest of roads.

 

Is this normal, especially for these bridgestone which are not very aggressive, even for an A/T tire.

 

I would appreciate the feedback.

 

Thanks all.

 

Edited by Sin City Trail Boss
Posted

Why E rated?  E's will ride like a brick, unless you're weighing them down with a load.  

Posted
15 minutes ago, bshort said:

Why E rated?  E's will ride like a brick, unless you're weighing them down with a load.  

Unfortunately for this tire size they either have only P rated or E. I was a little worried about going P rated because I do off road on occasion, and was worried about getting tire punctures. 

 

I have 90 days to try these out. Wonder if I should go back and get P rated ones.

 

I will say these ride a lot smoother than the Falkens. I still have seat vibration, but it's a lot less than before.

Posted

I had non E range wildpeaks on my 2015 and could not get rid of the vibration. Half the reason I switched to the 2019 (other have was the wonky 6spd shifting)

 

Running the factory tires on the factory 22"s and have a little seat vibration still. Just had the dealer road force balance and it is better but still there sometimes. Seems worse when I let the truck sit for a couple days. 

Posted
7 hours ago, Sin City Trail Boss said:

Unfortunately for this tire size they either have only P rated or E. I was a little worried about going P rated because I do off road on occasion, and was worried about getting tire punctures. 

 

I have 90 days to try these out. Wonder if I should go back and get P rated ones.

 

I will say these ride a lot smoother than the Falkens. I still have seat vibration, but it's a lot less than before.

My truck has the same shake with stock everything.  Since the shake is at the bottom of my list compared to the other issues I haven't had the dealer look at it yet. 

 

Seems like 99% of larger tires size then stock only come in E load. Big reason why I haven't upgraded. 

Posted (edited)
43 minutes ago, ct_corey said:

My truck has the same shake with stock everything.  Since the shake is at the bottom of my list compared to the other issues I haven't had the dealer look at it yet. 

 

Seems like 99% of larger tires size then stock only come in E load. Big reason why I haven't upgraded. 

The only time I had almost zero vibration was when I switched tires with my buddy. 

 

It was his stock 18" wheels and tires. Same size as what I have now, only P rated and they were street tires.

 

I wonder if this is just a normal thing for this truck? I figured since the tire I purchased is not very aggressive at all, that I would have zero vibrations, but I have seat vibrations even in the smoothest of roads once I hit 65.

Edited by Sin City Trail Boss
  • 3 years later...

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

    • Paid $2.72 for E85 today.
    • 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.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...