Jump to content

CRC GDI Valve Cleaner spray

FL335i

By FL335i
in Engines & Drivetrain

Recommended Posts

  • Replies 34
  • Created
  • Last Reply
Centex14 Enthusiast

Centex14

Posted
Posted

It’s amazing mine runs great at a 115k miles with no catch can or cleaning. Pulled the intake off and looked at the throttle body yesterday. No oil. Maybe I’m just lucky.


2014 z71 LTZ
Volant Intake
Borla Exhaust

  • 2 weeks later...
cwebb1227 New Member

cwebb1227

Posted
Posted
On 8/7/2018 at 1:17 PM, SkiDooNick700 said:

is there a risk of clogging up the cats by doing this?

That's what I was thinking, also, what happens to those shards of carbon that get sucked into the cylinder? Do they scratch the cylinder walls like sand? Because if the carbon is making it into the oil, it's gotta be slipping past the rings.  

Doublebase Enthusiast

Doublebase

Posted
Posted

I just used the 3M intake cleaning system (3 solutions, tank, throttle body cleaner and induction). 

 

Personally think it was a waste of time, luckily not resources as it was free. Can took about ten minutes to empty into the manifold while it was running. Didn't notice any smoke or any different performance after. Don't really think it did anything but it's a great great gimmick. Eveyone is scared of carbon deposits on DI engines, they know that, they sell something to "treat it". They have to be loving this. This kit I think is almost $50 and it has maybe $5 bucks of cleaning solution in it that doesn't do a damn thing to clean carbon off a valve.

  • 2 weeks later...
Pearl2017 Enthusiast

Pearl2017

Posted
Posted

I just did mine today using the vacuum connection above the TB. Took a rubber vacuum plug and put a small hole then pushed the tube thru it and hen slid in on over the fitting ...no vacuum leaks or CEL to deal with. Ran in about 3/4 can @ 2K then shut it off to sit awhile. Th CC is pulling out a lot of crud but i put it on ~10K.

 

5b8355e62199a_ValveClean1.thumb.jpg.2c620fc280ab0c88c2387737da367d63.jpg5b8355c3640ea_ValveClean3.thumb.jpg.fe75270fb4f5b97d9dbf6b03da9167cc.jpg

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