Jump to content

2007 1500 Classic - Slop in front end question

jsm10
 Share

Recommended Posts

jsm10 Enthusiast

jsm10

Posted
Posted (edited)

I recently bought a 2007 Silverado 1500 classic.  I noticed when putting some shocks on it that it has some slop in the front wheels.  The passenger side is minimal (maybe 1/8"), but the driver's side is worse (maybe 1/4").  It is only horizonal slack (move wheel side to side).  There is no vertical slack.  So, I think the bearings/hubs are OK.  The slack goes all the way back the rack and pinion (I can see the shafts back to the rack and pinion boots move).  There is no slack in the outer tie rod joint with the steering knuckle.  The truck also has a slight whine when turning the wheel that is worse at cold temperatures.  I guess I am going to need to replace the rack and pinion assembly (for the slack) and the power steering pump, right?  Or, am I off track here?  Thanks in advance for any advise anyone can provide.

Edited by jsm10
davester Senior Enthusiast

davester

Posted
Posted (edited)

Don't expect the PS pump to be completely silent, you will likely be disappointed with the replacement pump if you do...

 

I would suggest first flushing the PS fluid with fresh, good quality PS fluid.

 

I would also recommend changing all the other fluids (engine oil, transmission oil, transfer case and front diff (if 4wd), rear diff, brake, coolant).  And examine the brake lines for rust, particularly along the frame from the driver's side front wheel to the abs controller under the driver's seat, and (more difficult to see) along the frame rail above the fuel tank, the the lines are known for rusting...

Edited by davester
jsm10 Enthusiast

jsm10

Posted
  • Author
Posted

Thanks for the replies.  Does a 2WD have inner tie rod ends?  I searched some videos online and everything I saw is 4WD trucks.  Thanks in advance.

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

Yes. The 2WD trucks have a steering rack with inner and outer tie rods.

 

The 4WD trucks use an idler and pitman arm steering system.

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...