Jump to content

Recommended Posts

Posted (edited)

Sad thing for our Ford friends is they cannot use a chemical direct induced valve cleaner such as Seafoam, CRC or Gumout as the chemicals in these products may run the turbo system. Lots of discussions on f150forum.com about this.

 

hmmm.....Gm reconfigured the intake/outlet ports on their heads to minimize the problem recently......hmmm.....go check out the Ford Ecoboost boys forums all coked up at 50,000K.....hmmmm Ferd's new 3.5 EB has completely addressed this seemingly made up problem of GDI's coking the valves to Mt Rushmore granite hardness!All of which are facts and all of which can be found on the internet......interesting!

Edited by Silverado Steve
Posted

I'll let you all know down the road how mine does. No catch can,no valve cleaning going to change oil and drive it. Just like I have done with all my other trucks.

  • Like 1
Posted

Just under 2800 miles on my 2016 now in just over 5 weeks.................................I can count the miles on ONE HAND that my truck has been in V4 mode. I use M5 exclusively around suburbia empty and towing my work trailer, as my speeds rarely exceed 50mph. I use the "Range" AFM delete device for long highway travels in order to use the 6th gear!!!

 

The oil level on my dip stick hasn't changed at all since ownership. I added an Elite catch can though at less than 500 miles on the clock.

Posted

I'll let you all know down the road how mine does. No catch can,no valve cleaning going to change oil and drive it. Just like I have done with all my other trucks.

I'm running a similar experiment with a coworker. He and I have the exact same truck. He's maintaining his like you normally would...87 octane gas from wherever, regular oil changes, no valve cleaning, no catch can, etc. I'm running 89 shell gas exclusively, catch can, and BG induction services every 15k miles to maintain the valves. I have about 34k miles and he has about 50k. We're going to see how both trucks are doing around 100k to see if what I've been doing has been worth it or a total waste of money. I'll keep the forum updated as well.

 

 

Sent from my iPhone using Tapatalk

  • Like 7
Posted

Well I've had my truck for a couple months, and I've put about 6000 miles on it. So I should find out how the valves do in short order lol.

Posted

I'm running a similar experiment with a coworker. He and I have the exact same truck. He's maintaining his like you normally would...87 octane gas from wherever, regular oil changes, no valve cleaning, no catch can, etc. I'm running 89 shell gas exclusively, catch can, and BG induction services every 15k miles to maintain the valves. I have about 34k miles and he has about 50k. We're going to see how both trucks are doing around 100k to see if what I've been doing has been worth it or a total waste of money. I'll keep the forum updated as well.

 

 

Sent from my iPhone using Tapatalk

Would love to hear about this!

Posted

I will it may take some time seeing as I drive about 13,000 miles a year on average haha. But I will post a new thread about it regarding long term results.

Posted

It is weird with these engines. My wife has a 2011 Acadia with 60,000 miles on it no engine problems what so ever. My mom has a 2011 traverse with 40,000 miles on it. Had to have the valves cleaned, dealer said they were full of carbon on them. She also used gas where ever she could get it the cheapest. My wife has only ever used top tier fuel. So maybe it does work..who knows.

Posted

It is weird with these engines. My wife has a 2011 Acadia with 60,000 miles on it no engine problems what so ever. My mom has a 2011 traverse with 40,000 miles on it. Had to have the valves cleaned, dealer said they were full of carbon on them. She also used gas where ever she could get it the cheapest. My wife has only ever used top tier fuel. So maybe it does work..who knows.

neither of those have DI engines

  • Like 3
Posted

1fbe26e3f2990ac9dbde22e87c18e39e.jpg

 

That's about 24000 miles on my 6.2... The intake valves look just fine.

 

Sent from my PURE XL using Tapatalk

  • Like 1
Posted

neither of those have DI engines

I'm pretty sure on top of the plastic cover that's on top of engine says"VVT direct injection 3.6." Is this not the same type?
Posted (edited)

As an owner of one of the first DI's hitting the market in '07 (BMW 335i) I'll give you the readers digest version of all this hoopla. The gas you run never touches the valves so don't get to caught up on that front, worry about the octane and freshness for your use. Only walnut blasting is the remedy. How often.... that's a subjective item that depends on YOUR car and actual carbon build up. I went 65k on my 335i and never had issues. The BMW dealers have special blasting equipment and walnut media. (Google walnut blast 335i) For a 335i, it was approx a $900 job at the dealer, $500 at the indies. Intake manifold comes off, blast the valves and reassemble. The only OTC medicine is CRC's German mechanic in a can. $14 later, it seems to work, especially if you use it more frequently than trying to use it every 50k. I've used one can on my K2XX and am due for another now. The consensus on the E90 forum was IIRC 50k intervals for blasting cars with no symptoms. Again, camera your valves and make your own decision. The only preventative measures you can do is run a catch can. I opted for a ADD W1 can with some baffle material. the amount of oil it catches in one oil change is mind boggling. I've spent WAY too much of my life on this topic. I read stuff where Toyota was toying with putting in an injector behind the throttle body to combat this long-term issue in their engines (Guess Toyota wants to keep that brand reputation of long term longevity). This is an issue that will affect the people who keep their vehicles longer than the warranty. So at the end of the day, the fuel injection has come full circle. From a TBI, to SFI, to TPI, then the DI and now we're back to where we started in 1987. An injector in the throttle body. My '14 has almost 52k on it now (yes I drive a lot). No issues on this front. I'm also confidenced a lot of Hwy driving and a pair of heavy Red Wings help combat the issue. I recommenced the USA made Red Wings model 606, they really help prevent carbon build up... my truck is proof. In all seriousness, some people get way too worked up over this. I've seen this on two forums now since 2007. The sky still hasn't fallen, 335i's are still running around and so are DI cars from GM and other makers. Install a catch can, run the CRC stuff frequently and sport your 606 red wings on the skinny pedal. Move on in life.

 

This topic makes me always think of something an older guy I work with tells people. Sometimes technology is not always better. In the 1960's the US spent $12M to develop a pen that wrote in space. Guess what the Russians used? A F'n pencil.

Edited by FL335i
  • Like 4

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

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...