Jump to content

Rust Prevent - Fluid film or Eastwood internal frame coating

Flyin-Ryan

Recommended Posts

Flyin-Ryan New Member

Flyin-Ryan

Posted
Posted

My very first post. This forum is awesome. 

 

I just purchased a 2011 Crew cab 1500. I want to keep this forever. Everything on this truck is solid and I want to keep it that way. My question is, should I pull out all the plugs and spray in fluid film or Eastwoods internal frame coating? I know once I use Fluid film I'll never have success with the internal frame coating or paint or anything since nothing will stick. Im new to learning about fluid film. What are your thoughts? Ive got a great truck here and want to keep it that way. 

 

Thanks all! And thanks for having me on the message board. Ive been lurking awhile and learning what to shop for. Now I have one and look forward to learning even more and helping others as I learn.

 

Ryan

riverbanks Senior Enthusiast

riverbanks

Posted
Posted

Fluid film is fine,short lived thou,like every year in high spray(roadspray)areas it will need to be reapplied,but we'll worth the minimal cost

riverbanks Senior Enthusiast

riverbanks

Posted
Posted

Fluid film is fine,short lived thou,like every year in high spray(roadspray)areas it will need to be reapplied,but we'll worth the minimal cost

aseibel Senior Enthusiast

aseibel

Posted
Posted

I use fluid film every spring to coat my plow. Keeps it looking great the rest of the year with no rust.

but I don't have any desire to spray that on the truck frame. I'm sure you could use it in the cavities and it would be better than nothing. But I think there are other products that are more designed to "mist" into cavities like that. Fluid film is pretty thick. 

 

If you search around, you can see plenty of arguments about when and where to use fluid film.

C/K Man Enthusiast

C/K Man

Posted
Posted

These frames are dipped, so there isn't too much concern of them rusting on the inside.  The wax coating can be damaged on the outside, but it can be easily touched up.  The factory coating is available in aerosol cans.  newdude raises a good point, some 'anti-rust' coatings can damage the factory coating.  I use the factory coating, and touch it up from time to time.  This TSB has information on the frame coating:

 

https://gm.oemdtc.com/7624/service-update-14002-underbody-appearance-2014-chevrolet-silverado-gmc-sierra

HoosierZ Enthusiast

HoosierZ

Posted
Posted

I used Noxudol 700 cavity wax to hopefully protect my 2016. I sprayed it inside my doors, rockers, fenders, bedsides, tailgate, and cab floor braces. Basically, anywhere there’s pinch welds, spot welds, or cavities where water and salt can eat away panels from the inside. Time will tell if it works, but for less than $100 for six cans, it’s worth trying. Doing nothing didn’t work out too well for my 2008 Silverado that had a rocker panel rusted through at 8 yrs/ 90k miles. I bought the Noxudol on Amazon. 

Flyin-Ryan New Member

Flyin-Ryan

Posted
  • Author
Posted

Thanks all for the information. Any recommendations for treating the inside of the doors or rockers/cab corner? Or should I just do nothing and instead just keep the under carriage clean?

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...