Jump to content

When In 4wd - Click,clunk,knock Sound?


Recommended Posts

Posted

Hey all,

Got a 6 inch lift put on my 2005 GMC Sierra and dont know if this has anything to do it with it, but When I put it in reverse and/or turn wheel sharp and drive it gives and awful sound like I am contacting something I am not suppose to be. Sounds like something grapping and giving a click, snap, pop noises when rolling..Please respond with any advice you can give,,Thanks

Stephen

Posted

Do you have it in 4Hi or 4Lo. I am pretty sure this is normal in 4Lo due to the TQ you are putting to the ground. It takes a lot to move those wheels and then you try to turn them, it puts more stress on the system, especially at slow speeds.

Posted
Do you have it in 4Hi or 4Lo. I am pretty sure this is normal in 4Lo due to the TQ you are putting to the ground. It takes a lot to move those wheels and then you try to turn them, it puts more stress on the system, especially at slow speeds.

 

 

your not driving around in 4wd on the dry pavement are you? Cuz that will do it, and those sounds "sound" bad for a reason.

 

edit: After re-reading the post, i see that your saying it happens on sharp turns and in reverse? Is it when your turning in revcerse?? and does this ONLY happen in 4wd? Generally rubbing in reverse and when ur turned fully locked is clearance issues wth tires and fenders. Wat size tires are you running? Is that whats rubbing?

Posted

Yep, It only happens in 4wd and I think it is hi b/c when I forst noticed it I must have accidentally hit the button before backing up with wheels turned..But I pulled a car out of ditch in snow we had here in the south and started spinning, then put in 4 hi and pulled him out, but when backing up with wheels turned, I heard it again (the sound)..I am just assuming it is the lift I have,,,I am running a 6 inch lift with 35's...No other issues are happening...

Posted

If it doesn't do it in 2wd, then it cant be the CV's. Since they are always spinning, it will do it in 2wd or 4wd if it were the CV's. The only bad thing about it is that these front ends have so many different parts to them. It could be a number of things. Front axle actuator, worn out tie rods-idler arm, ball joins might be starting to go (even if they arnt leaning yet, if they get weak they will lean while under a load from the front tires ) etc... Im running a 6 inch and 35's as well and my front end is smoked and when Im in 4wd, she makes all kinds of popping and pinging and snapping sounds. Its just front the worn out front end and steering parts moving around so much due to slack. Could be wrong, but mine does it and i know my 4wd is flawless and my CV's are brand new. something to check.

Posted
its becuz you dont have locking hubs you should be fine as long as it only does it in 4wd

 

 

Im sorry but thats not right. If a front end clunks and pops and clinks at all....ever, then there is somthing not right. Worn out joints, bushings, busted CV, stripped or worn teeth on the axle lock inside the diff, brocken teeth on ring and or pinion...etc. The only difference between an auto hub and a manual hub is the manual hub, you get out and lock them by hand. An auto hub is always locked in since your CV is splined right into your wheel bearing and hub which is held on by your outter CV nut. Like I said before, if it only does it in 4wd, then its not your CV shafts. If you dont want to check your front end yourself, then take it to a shop or have a buddy check it out for you for loose and worn out front end parts. If you dont feel like doing any of that, then just put her up on jack stands on all corners, put it in 4wd, put it in 1st and let them spin while in the air. Turn your tires back and forth. If it dont do it while on the stands, then I would bet money its your front end components making the racket. If it does do it, then I think its either your ring and pinion or your axle lock in the diff.

Archived

This topic is now archived and is closed to further replies.

  • 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   3 Members, 0 Anonymous, 2,173 Guests (See full list)

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