Jump to content

Recommended Posts

Posted

Dropped my truck off at a shop for an engine enhancement/tune. Got a super surprise message back I need validation on from the page. See below. Rear drivers side hub/bearing is gone, saying whole assembly should be replaced.
 

Sound right? Thx in advance.
 

 

“We’ve noticed the drivers sides rear axle was leaking fluid when we moved the truck yesterday.  We pulled off the wheel/axle thinking it was just a bad seal.  However, inside axle tube, the wheel bearing is completely torn apart.  There is no bearings left in the bearing case.  So essentially the axle was riding around inside the tube with no bearings.  No one here has ever seen that happen before.  The inside of the differential tube is destroyed. Basically the entire rear axle housing needs replacement because of that. “

4B5086C0-F40D-4FE9-BAB2-14869CB93FD3.jpeg

CC1C481D-85BC-446E-897C-0FA7306AC35B.jpeg

02A63C6C-92DB-4B9D-9C57-69900C3982EA.jpeg

Posted

Well, technically it's not "destroyed".

 

You could clean all that up and make it smooth there again, then pound in a new axle bearing because the rear axle rides on the bearings that are held in that bearing case.

 

AKC10.jpg

Posted

The tube is no longer round. Oblong.
 

Where did the bearings go?
 

the wheel did take an impact 2 years ago when someone ran a stop sign and hit my wheel. I never felt any shimmy or shake at all - that is what drives me crazy. Maybe 10k miles since hit that tho. Baffling! 

Posted

Pull the diff cover, see what you find in the bottom. Might be chunks of metal in there.

 

If it's oblonged, then yeah I guess you need a new rear axle.

Posted

The image doesn't really show "Out of Roundness", might be worth a try to have them clean it up and try a new bearing and seal, just monitor it, now if they do not want to try it, then short of having the truck towed back home for "DIY" then your stuck!

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

    • This video may not be the exact content for the joke thread but its a lot of laughs so here it is, I've only watched a portion of it so far but if anyone is looking for some light hearted good soap box driving action, its here. As a note in the upper left of the screen it shows the number out of 100 to refer back to any particular vehicle for comment !.    https://www.facebook.com/reel/1351928276956715
    • 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.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...