Jump to content

Recommended Posts

Posted (edited)

4” BDS lift on 2” 2020 AT4

Custom shop installed. 
 

I recently started having a whirring/whine sound when starting off slowly and maintaining a slow crawl. Almost sounds like riding the clutch with a worn throw out bearing. 

 

Now since winter I’ve been getting groaning and creaking during the same process but pronounced over uneven surfaces. 

I suspected the suspension bolts needed tightening. Going underneath to peek, I found that the front CV axle boots appear to be leaking & spraying grease. Maybe they are making the sounds as they start and as they flex. No tears, seems to be leaking at the seam. Same on both sides. 
 

What is going on here? Is this the culprit?

thanks!
732339FF-3299-4587-865C-19F9A26AB5EE.thumb.jpeg.c4054b92d8c2d9edc199df65b80ae07d.jpeg

Edited by aragrev7
Posted

I don't think the CV is the issue.  They normally clunk when the grease is out.  The noises are worse while turning, especially while backing up and turning.  Are you driving in Auto 4WD mode all the time?

Posted

I had initially driven in 4 auto for the first few thousand km. But had gone to 2WD since (currently at 22000km) because of the issues that have been noted in general and specifically with lift kits. 

Would the leaks be an issue from the lift kit install? I had chosen the BDS kit because I wanted a neutral angle on the axles vs other cheaper spacer only designs. 

Posted (edited)

I'm not familiar with the BDS kit to know what it comes with.  However, that's definitely CV axle grease coming out.  Iirc, the GM lift kit for the Trail Boss/AT4 include new cv axles.  If the BDS kit didn't come with axles I would start to wonder if the axles are long enough. 

Edited by Transient
Posted

bds usually provides a drop kit with their kits.....so longer cv arent needed, idk if his did but usually they do......if it didnt than yeah 4'' is too high without correcting those shafts

 

Posted (edited)

That’s right, the BDS was a full kit with drop. The CV angles were very good. 
This kit:

https://bds-suspension.com/product?kid=1805H

 

I suppose my next question, is what is the fix for the leaking axle, and how would it have happened? Install issue? Bc then the shop should redo it properly. 
If this is a failure issue, then maybe* dealer will look at under warranty. BDS was adamant that their mod doesn’t break warranty issues for parts not replaced. (Dealer also uses this shop for all their mod work too - they go out of house for mods). 

Edited by aragrev7
Posted

I had the same issue with both of my CV boots slinging grease after installing the 6112 kit, dealer replaced both shafts under warranty no questions. Pretty sure 4wd auto is what caused all my issues.

  • 1 month later...
  • 1 month later...
Posted
On 2/1/2022 at 4:13 PM, HeavyChevy1500 said:

@aragrev7any update on your CV issues? I am having the same problem after putting a 4" Rough Country kit on my Trailboss.

Sorry for the delay. Didn't get a notification. They replaced the CV axles under warranty. The service guy tried to tell me, but noticing the lift kit, that my axles were "way out of spec". I told him to try again and take a look, with the BDS lift & diff drop, my axles are closer to factory spec than with the added AT4 2" factory lift. They offered a one time replacement, but the installers said they would stand by it and challenge the dealer should they give me grief about it again.

Does the rough country include a drop to re-align the axles?

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