Jump to content

Recommended Posts

Posted

RT,

 

Very appreciative of the info you've put on here. I sent both those videos to them last week. Maybe the GM engineer will look at them as well. Sometimes I think "It has to be the tires" and other days I can't make heads or tails of anything. I wish I had a lift so I could at least measure this stuff myself. I have an accurate dial indicator.

Posted

Brakin7

 

Could you explain your symptoms in detail?

Congratulations on a smooth riding truck!! Notices like this give us hope

Posted

RT,

 

Very appreciative of the info you've put on here. I sent both those videos to them last week. Maybe the GM engineer will look at them as well. Sometimes I think "It has to be the tires" and other days I can't make heads or tails of anything. I wish I had a lift so I could at least measure this stuff myself. I have an accurate dial indicator.

Many Many Many people have installed new tires with no positive results. It will mask it for a while but I guarantee it's always shaking whether you think it is or not, You don't need a lift!!!. Hahaaa!!!!

 

RT

Posted

I had my driveshaft balanced by a professional shop and my truck still vibrates.

Posted (edited)

show them these videos and ask them if it's still the tires!

 

https://vimeo.com/194200154

 

 

 

 

RT

 

 

 

Where did these videos come from and are they available in a longer format? Not long enough to tell much about it..... but looks like it could be a vibration SHAKE source

Edited by MyFavTruck
Posted

1 was from performance trucks and the other was from this site. Long enough to see problems with both. I fixed my drive shaft and will be checking axles next but My vibration is gone after the driveshaft was trued. Look at the bottom plane on the drive shaft and then look at the outer edge of the axle flange.

 

RT

Posted

Then check the axles

 

RT

I will do that next. Thanks. If it was the axle flange, wouldn't I feel the shake all the time? Mine does it at 45mph exactly and between 72-85.

 

Thanks

Posted

Hey guys just a thought. Would it be possible to lift the truck up on a lift, all four wheels off the ground, bring the truck up to speed, get underneath the truck and try and see if anything sticks out as the source of vibration?

Posted

Makes me wonder if GM has or does any quality control checking of parts and sub components. How else can you explain all the different parts and components that people report got changed and helped some but not all. It appears it might be tires, driveshaft , axles , torque converter,motor mounts, cab mounts,shocks and the list goes on.

Posted

My vibrations are now gone to, but it took replacing the rear ring and pinion. I went from 3:08 to 4:10's.

That's a helluva jump in gearing! Hahaa I bet it runs like a bat out of Hell now! How tall are your tires and what RPM's is it showing at 80 mph?

 

RT

Posted

Has anyone tried running a lower than normal air pressure? I've noticed most of us on here like to run higher tire pressures for loads, mpg's, stuff like that. Maybe if we run factory pressure or little lower than factory that'll smoothen the ride....

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...