Jump to content

Recommended Posts

Posted

With our GDI engines, I thought this post from a senior member on the Corvette member was worth the read as it is a good explanation. My dealer said I should have my valves cleaned about every 25k miles - that's gonna be very expensive (and require a lot of crushed walnut shells).

 

So, has anyone had their valves cleaned?

 

"I've EXCLUSIVELY used Top-Tier gasoline for over a decade, and the research on the benefits is compelling in traditional fuel-injected engines. However, the research is also beginning to show that Top-Tier doesn't prevent the emerging problems of valve deposits on gasoline, direct-injected (GDI) engines, and all the LT engines now are GDI. In fact, the majority of modern engines now are GDI.

In traditional port-fuel injection engines, the injectors spray fuel on the valves, and the detergents in Top-Tier fuels do a good job of keeping them clean. In a GDI engine, the fuel is injected directly into the cylinders, by-passing the valves, and the same cleaning effect does not take place. The industry has recognized that new oil and fuel standards are required for GDI engines, and they are under development, but, as of yet, it's not clear what the answer is.

Thus, it's questionable that Top-Tier fuel alone can produce the same benefits in our GDI engines. It's a potentially, very large, "ticking time-bomb" w/ many GDI cars showing severe valve deposits relatively early in their lifetimes. Right now, the only solution is removal of the top-end, and mechanical valve cleaning."
Last edited by Foosh; 07-10-2016 at 10:43 AM.

 

Posted

I doubt anyone has as of yet. I would venture to guess that only the exhaust valves are going to show any real deposits. I would just have the GM top end cleaner or something similar ran thru every 10k miles to keep the deposits on the low side.

Posted

Throw a can of Seafoam, CRC or Gumout intake valve cleaner through every 25K. Lots of discussions on catch cans and if they help. I'm not taking my truck in every 25K for a valve job; instead I run Seafoam through and at 42K haven't experienced an engine failure. To my knowledge there is no stated requirement in our warranty books and schedule of maintenance that says a valve job is required...sounds like a major upswell by your dealer...much like them trying to sell you a highly encouraged paint sealant at time of purchase.

  • Like 1
Posted

25k is a bit excessive but you guys are over-imagining the procedure. They just pop off the intake manifold to clean the valves.

  • Like 2
Posted (edited)

engine needs complete tear down, cleaning, and then rebuild every 25k. Dealer is 100% correct

 

I just checked the 2016 Silverado User Manual maintenance section, and there is no mention of this "complete tear down". It is hard to believe that GM would build and people would buy a truck that needed a complete tear down every 25k.

 

I would love to hear from anyone who has actually had a "complete tear down" at 25k.

Edited by ColoRetiree
  • Like 1
Posted

I don't think he REALLY meant a 'complete' tear down - it's just the underside of the intake valves that need cleaning as with a DI engine there is no gasoline being sprayed to the under side of the valves. Thus the article was that even Top Tier gas does no good in keeping the valves clean when they don't get sprayed in the first place.

Posted (edited)

This issue has been discussed exhaustively in the catch can thread. It would take a while but you should read through that.

-

-A mechanical cleaning is one way to clean the valves. The other method is to run Seafoam or do a BG Induction Service which pumps cleaning chemicals into your engine at the throttle body to clean the valves. This should be done every 15,000 miles. Nothing that goes into the gas tank will every wash over the backside of the valves so Gumout, STP, and Techron fuel system cleaners or Top Tier Gasoline will do nothing to keep your valves clean. They will, however, help other parts of your fuel system so it's not a bad idea to use these products.

 

My personal opinion, your manual doesn't say anything about it because these engines likely won't have major mechanical issues from valve buildup until 100k+ miles. At that point, cleaning the valves would be a "repair job" not a maintenance item.

Edited by txab
  • Like 1
Posted

Running a higher octane fuel in these GDI will do nothing as far as cleaning the valves. 87 for me.

 

Correct. I run 89 based on the recommendation of Blackbear Performance with regards to engine knock. I run Shell for it's top tier status with regards to cleaning the engine. But yes either way it will do nothing for the valves themselves. Only a manual cleaning, upper induction cleaning service, or prevention with a catch can will help the valves. I prefer a combination of using the catch can to reduce the valve buildup and an upper induction cleaning service every 15,000 miles to clean off the stuff that does get by the catch can.

Posted (edited)

There is no reference in either warranty or maintenance guide of a valve cleaning. Like I mentioned earlier, I do a GDI valve intake cleaning at 25K and every oil change I throw a whole can of Seafoam into the crankcase when there is about 5% oil life left on the OLM which for me is about 350 miles. You can get any brand of intake valve cleaner from Wally World for $6-$8. I haven't taken the valve cover off or seen my intake valves, but I am confident and comfortable that my truck will suffer some other catastrophic failure such as a water pump or transmission, long before my engine takes a dump. Last I saw the newly redesigned 3.5 Ecoboost coming out next year will have a port injector to hose of the intake valve with gas. The new Tacoma 3.5 taken from Lexus already runs this setup.

Edited by txab
removed off topic material
Posted (edited)

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 mookdoc6
Posted (edited)

http://artofgears.com/2016/02/26/all-2nd-gen-3-5l-ecoboost-v6s-for-f-150-to-benefit-from-direct-port-injection/



Back on topic, I don't think you need a mechanical cleaning every 25k miles but how much are they charging for it? I do like mechanical versus chemical just so it's not blowing all that crap through your engine and exhaust system.


Sent from my iPhone using Tapatalk

Edited by txab
  • Like 1

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

    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...