Jump to content

Driveline vibration

mike101010
 Share

Recommended Posts

mike101010 Enthusiast

mike101010

Posted
Posted

I have an 04 Sierra 2500hd and have been chasing this vibration. It vibrates at 70 mph and up. It's weird if your on the gas it vibrates like crazy if you let off the gas it stops then when it starts to deaccelerate it comes back. You can also notice the vibration at lower speeds but it's not bad if you weren't looking for it you won't notice it but at 70 it's real bad. I've had the drive shaft balanced new u joints new slip yoke and the transfer case rebuilt with no change everything feels tight it also does it in lock up or out of lock up I'm not thinking it's the tranny. The tranny has been serviced shifts fine. Any ideas

sdeeter19555 Senior Enthusiast

sdeeter19555

Posted
Posted

The only other thing I had do this was very obvious, but the vibration you describe can also be caused by bad pinion bearings...but it should be whining/growling to be that bad.

 

Sent from my SM-T350 using Tapatalk

Hantke Enthusiast

Hantke

Posted
Posted

i've got this same thing, at about 55 MPH it starts vibrating and humming, and it'll get louder if i go faster and quieter if I slow down, but if i just barely touch the gas pedal it goes away, I haven't pin-pointed it yet, but i noticed if i grab the front driveshaft and twist it back and forth quickly i get a small thud, but i don't think thats abnormal either.

  • 1 month later...
tthomas Enthusiast

tthomas

Posted
Posted

My 2015 2500HD is doing the exact same thing as yours Mike. Same speeds same symptoms. I'm gonna throw u joints at mine and see what happens. Let me know if u figure yours out.

BC2500HD Enthusiast

BC2500HD

Posted
Posted

Maybe u joints

 

The thump might come from the slip yoke binding on the output shaft of trans or TC?

 

I think there was a TSB on this? New yoke and special lube to use, from dealer.

 

Dealer did my yoke. Gave it back to me and I had the driveline vibration, as described. Took it back and they did front U joint. Fixed it.

  • 5 weeks later...
gmcblack Enthusiast

gmcblack

Posted
Posted

on my 2004 2500hd 8.1 replaced carrier bearing . an got vibration at start to 55 mph ,think I'm going to try front u joint to did everything else , no vibration before with the bad center bearing just bad rubber mount around the bearing ,,I should have left it alone// dam?


  • 6 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
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   4 Members, 0 Anonymous, 2,121 Guests (See full list)

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

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