Jump to content

How-To: Refinish A Vehicles Wiper Arms (Video).

ProStreetDriver

Recommended Posts

ProStreetDriver Enthusiast

ProStreetDriver

Posted
Posted

Video tutorial on how to clean up those rusty pealing windshield wiper arms on your vehicle. This method applies to both front and rear windshield wiper arms of a vehicle.

Procedure:
-the wiper arms can either be painted on the vehicle or removed from the vehicle, extra taping off will have to be done if you decide to paint the arms on the vehicle to ensure there is no over spray
-in order to remove the wiper arms, most are held on my a nut to the shaft on the cowl which can be accessible from under the hood of a vehicle
-sometimes there is a plastic cap covering the nut which needs to be popped off
-once the nut is exposed, determine the correct size socket and loosen the nut
-sometimes the wiper arm will pop off, other times you will need a puller to remove it
-in this case, I used a battery puller to remove the arm
-leaving the nut flash with the threaded shaft, install the battery puller and tight until the arm comes free
-sometimes the puller might need a light tap with a hammer to jar the arm loose
-once the arm is removed from the vehicle, you can now remove the windshield wiper from the arm assembly
-scrape off an loose paint with a scraper
-continue to sand down the rusty or pealing paint areas with 200grit sandpaper
-once done, give the rest of the wiper arm a sand down with 400grit sandpaper
-another option besides sanding would be to sand blast the arm assembly if you have access to one
-wipe the arm down with a degreaser and now you're ready to apply a coat of filler primer or ordinary primer
-filler primer will help fill in any pitting from the rust on the arm itself if you decide to go with that route
-once the primer is dry, give the arm another sand down with 400grit paper careful not to expose any of the bare metal
-give the arm another wipe down with degreaser to ensure there is no contaminants on the piece
-pick your choice of color or finish of black (I picked the low gloss black Fleet Paint by Dupli-Color)
-now you can paint the piece, apply 2-3 coats to both the underside and top portion of the arm
-allow the paint to fully harden before you flip it over to paint the opposite side or reinstall it on the vehicle
-installation of wiper arm and windshield wipers in reverse order of removal/disassembly

Mike-1000 Enthusiast

Mike-1000

Posted
Posted

There it is. Neither my first generation Ipad or my Android phone could see the link. I guess the PC is still good for something.

 

Mike

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   5 Members, 0 Anonymous, 1,769 Guests (See full list)

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...