Jump to content

Recommended Posts

Posted (edited)

My 2001 2500HD (2WD) is getting a complete overhaul on the front suspension.  I'm replacing the pitman arm, the idler arm, the upper control arm, tie rod ends,  the stabilizer link, shocks and lower ball joint.  So far all of that is complete.  I also bought the lower control arm bushings.  Given that the steering knuckle is out, I can get the lower control arms out in about 10 minutes (2 bolts and loosen the torsion bar and I'm done).  However, I've not seen any youtube videos or anything on replacing these bushings.  They seem to be in good shape, but I'm a bit nervous about tearing into them and potentially damaging the control arm or otherwise opening up a can of worms on something that doesn't seem broken (yet).  On the other hand, I've got the thing apart, I have the replacement parts, and I'd like to only align this thing once.

What do you guys think?  Is getting these rubber f-ers out a doable job.  (note:  I don't have a hydraulic press..  I was able to get the lower ball joints out with a big hammer and a lot of MAP gas.  I still have the ball joint install tool if that'll help with the bushings)

 

EDIT:  the truck has 190k miles on it. (if that matters).  All Arizona miles, so not much rust, but DAMN it was hard getting that knuckle off, the ball joint off, and the pitman arm off)

Edited by rszimm
Posted (edited)

Getting the rubber bushings out shouldn't be a huge deal, as you can burn or drill them out.  You might be get the new ones in with a vise or even pound them in with a hammer. You aren't going to damage the LCA unless you actually try to.

 

But, I haven't actually done it myself...

Edited by davester
  • 8 months later...
Posted (edited)

The lower control arm bushings easily press out using a ball joint press. You can get loaners/rentals from the a couple of the big brand auto parts stores. Much faster and cleaner than burning them out.

Edited by jcpwrd
typo
  • 2 weeks later...
Posted
The lower control arm bushings easily press out using a ball joint press. You can get loaners/rentals from the a couple of the big brand auto parts stores. Mush faster and cleaner than burning them out.


Have you actually done this for these HD trucks? I’m not sure if I need to spend the $15 in new bushings or $300 for two new entire LCA assemblies.
Posted (edited)

They do sell just the bushings, so they are designed to be replaced.  A ball joint press should work ok, as it can generate a good amount of force, might be awkward to hold steady if you don't have a vise or something to hold the LCA while you are cranking on the press, and maybe need to use a socket or a short section of pipe if the smallest included tube is too large for the bushing.

 

You probably can even use a hammer on them to get them out.

Edited by davester
Posted (edited)

I have not pressed out the bushings on an 2500HD LCA , however IMO a ball joint press (BJP) should still work as from what I can tell the 2500 LCA is nearly the same.

On 2500 LCAs it took less than 5 minutes per bushing to press them out using a BJP. (I had taken the LCAs to a shop for them to do it with their hydraulic press and they could not do it as they could not get the LCA set up within the opening - so I brought them back to my garage and pressed them out with the rental tool I already had for doing the ball joints).

Lower Control Arm Bushing removal using ball-joint press.jpg

Edited by jcpwrd
added photo of how to remove control arm bushing with ball joint press.
  • 3 years later...
Posted

Hey👋 

 

Any updates ?

 

Were you able to press them out and install the bushing in with just thr ball joint tool??

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