Jump to content

Recommended Posts

Posted
10 hours ago, Chris Panke said:

Any follow-up yet?  Inquiring minds want to know

 

I had the GM factory suspension lift installed and the noise went away completely but now after a few thousand miles it seems to have come back. Its not as loud as previous, but definitely the same noise and goes away shifting from 2WD to Auto AWD.

 

I shared the new bulletin with my dealer and they said they can't do the repair because the bulletin is a CV axle swap which was already done with the GM factory suspension lift.  I explained that the bulletin fix should be the stubshaft in the differential but they are saying that the work instruction and part number are for the CV shaft or "F Shaft" replacement, not the stubshaft, which I believe the stubshaft is the highlighted parts below:

image.png.75f79e1919450f843617a61772141f71.png


I have an appointment set for Monday to get the work done. Parts just came in today from what my buddy told me. I should have some pictures then and will update as soon as I can.

  • Like 1
  • Thanks 2
Posted

New stub shaft pic, I'm waiting for the tear down to compare the different parts. Truck just got on the lift.

3EC47AFD-4E4B-4058-B8D7-60D486832734.jpeg

  • Like 1
  • Thanks 1
Posted (edited)

Alright, from what I can tell is the metal slinger that covers the bearing is now made of a polycarbonate or plastic material. It also looks like it was glued to the stub shaft as well. I think the logic here is that the metal one was resonating as the stub shaft shifted which caused the noise. You can see the "wear ring" on the inside of the metal slinger which is where I believe it was rubbing on the housing.
 

I will try to keep updating this as I continue to drive more.

 

Edit: I would like to also add that whole looking back old photos, the clip that fits on the stub shaft "looks" bigger on the new one than the old one did.
 

C69D2BEE-C4A2-4585-A784-BE5FE3AF45C9.jpeg

Edited by Otherguy
  • Like 1
  • Thanks 2
Posted

Trying to picture it. You can’t see that from the outside at all, right?

 

Just wondering what they did to mine. 

Posted (edited)
5 hours ago, AJMBLAZER said:

Trying to picture it. You can’t see that from the outside at all, right?

 

Just wondering what they did to mine. 

Edit, you can see the slinger just by looking. See attached photo.

1174718C-4A82-4484-AD66-D69ADCCDF8FE.jpeg

Edited by Otherguy
  • Thanks 1
Posted

I would like to know how a polycarbonate or plastic material will hold up better than plastic? What rubs on this thing? Wouldn't it wear down? 

Posted
Just now, Terry Schmitt said:

I would like to know how a polycarbonate or plastic material will hold up better than plastic? What rubs on this thing? Wouldn't it wear down? 

Mine is scheduled for replacement next week.

Posted
47 minutes ago, Terry Schmitt said:

I would like to know how a polycarbonate or plastic material will hold up better than plastic? What rubs on this thing? Wouldn't it wear down? 

Better than metal? Honestly I don't think there will be a difference as far as strength is concerned. It just won't resonate sound like metal would. What the slinger is running on, who knows.

Posted
On 4/11/2022 at 11:30 AM, Otherguy said:

Alright, from what I can tell is the metal slinger that covers the bearing is now made of a polycarbonate or plastic material. It also looks like it was glued to the stub shaft as well. I think the logic here is that the metal one was resonating as the stub shaft shifted which caused the noise. You can see the "wear ring" on the inside of the metal slinger which is where I believe it was rubbing on the housing.
 

I will try to keep updating this as I continue to drive more.

 

Edit: I would like to also add that whole looking back old photos, the clip that fits on the stub shaft "looks" bigger on the new one than the old one did.
 

C69D2BEE-C4A2-4585-A784-BE5FE3AF45C9.jpeg

Thank you for the pics!!

This makes sense from a materials perspective as the "jingle jingle" noise definitely sounds similar to a metal on metal contact.  Change to a dissimilar material like polycarbonate and it eliminates the resonance.  

 

I just wonder why it is only the DRV side as I would think the PGR side stub shaft would have similar material and design.  There must be a dimensional difference or an angle difference from side to side.

 

Either way, I have shared these pics with my dealership as we wait for part arrival.  Hopefully they can get me in soon so I can have a noise free summer.

Posted
On 4/11/2022 at 3:14 PM, Otherguy said:

Edit, you can see the slinger just by looking. See attached photo.

1174718C-4A82-4484-AD66-D69ADCCDF8FE.jpeg

Well, looked at mine and confirmed it is a metal dust cover. Not sure what they did correctly on mine but so far, so good. 

Posted

As I posted somewhere back in this thread, mine has quit making the noise. I even used electronic hearing protection to amplify the sound, just to make sure. And now, looking at the pic's just posted, I'm guessing with constant metal to metal wear, mine just wore down on its own. Warm weather should be here soon, and I'll listen for it again.

  • Like 1
Posted
On 4/11/2022 at 10:50 AM, Otherguy said:

New stub shaft pic, I'm waiting for the tear down to compare the different parts. Truck just got on the lift.

3EC47AFD-4E4B-4058-B8D7-60D486832734.jpeg

Do you happen to know the new part number? My dealers have an issue with saying they’ve never heard of the problem or tsb 🙄

Posted
17 hours ago, Stiffler said:

Do you happen to know the new part number? My dealers have an issue with saying they’ve never heard of the problem or tsb 🙄

 

TSB# PIP5653L.pdf

  • Thanks 1

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

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...