16 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPing!
Leading reported evidence
Replace twice, the most recent also at 20k miles ago
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
Has had new plugs 20k miles ago (currently about to cross 80k), has had Mahle fuel filters replaced twice, the most recent also at 20k miles ago.
Leading evidence: 'Replace twice, the most recent also at 20k miles ago' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'small exhaust leak' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace mass air flow sensor' (1 discussions). For that action, 0 discussions report a resolution and 1 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report an unsuccessful attempt
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Unsuccessful attempt · Original poster
Even swapped my old MAF which is still good back in with no change.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
16 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
3 acknowledgements have no verified action link; they do not establish a repair result.
I�ve been getting pinging at part throttle at freeway speeds when under load. From 3,500 rpm to roughly 5,000 rpm in 3rd gear and higher. Doesn�t happen at wide open throttle, only when applying light throttle on freeway inclines. Been wracking my brain trying to figure out what it could be. Tried Lucas injector cleaner then Lucas Octane booster. No change. From what I read, knock sensors rarely fail. I have the service records since the care was new and it has been meticulously maintained. Has had new plugs 20k miles ago (currently about to cross 80k), has had Mahle fuel filters replaced twice, the most recent also at 20k miles ago. Going through my folder of receipts, the only thing that hasn�t been done is the fuel pump. I found this thread and even though this is an 09 DFI motor, the symptoms are identical.
http://www.6speedonline.com/forums/9...gine-ping.html
It�s going to my Indy this week. The car pulls like a freight train, no other issues being exhibited. What do you guys think??
No codes. New MAF. Even swapped my old MAF which is still good back in with no change. I’ve noticed an increase in the level of the pinging over the last few weeks which is leading me to think the fuel pump may be on its way out.
Is there a high pressure fuel pump on your car? If not, I�d suspect that the fuel pump is fine if it pulls strong at WOT without pinging? Or does it ping at any throttle position?
Causes of pinging
1 ignition timing too high (computer controlled)
2 fuel octane too low
3 compression ratio too high (carbon build-up?)
4 engine temp too high
5 A/F ratio too lean
Any one of these or a combination of these can cause pinging. hope this helps.
Thanks. That�s what is leading me to think it�s the fuel pump. Knock sensors should pull back the timing if needed and these rarely fail. Tried Lucas Octane booster. No change. Tried Lucas fuel system cleaner to remove any buildup. No change. Engine temp is normal. So that leaves A/F ratio too lean. If the pump is not supplying enough fuel it�s gonna run lean and I�d imagine it�s too much for even the knock sensors/ecu to dial out. Then reading that other poster on 6 Speed having the exact same symptoms and it ended up being the fuel pump.
Correct, but seems the pump wasn�t delivering enough fuel at part throttle in the 6 Speed Online I linked above, even though it was supplying enough at WOT. His symptoms mirror mine exactly. Also, if it was due to increased compression due to carbon buildup wouldn�t it ping at WOT, not just part?
But his fuel pump issue was the 2nd pump - the high pressure fuel pump - whereas your car, and I�m not 100% sure about this - only has a lower pressure fuel pump and a completely different fuel delivery setup via DFI.
Regardless, though, I could see a problem manifest itself whereby the fuel pump delivers different levels of pressure that depend on fuel flow. Like having more than one speed. So at WOT, the pump would be on high, but at part throttle, medium or low. That�s what I would find out next.
Talked to my Indy. He doesn't think it's pinging. Much more likely a small exhaust leak. Albeit, this is just in talking to him. He hasn't taken the car out to test it yet. I'll be dropping it off next week. He did school me on not EVER using octane boosters again though. Apparently they can form a "crust" on top of pistons, causing hot spots like a glow plug and can ruin a motor pretty quickly. Lesson learned!
