When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
after a valve grind, heads magna fluxed, and decked..... the cylinder walls...still had the cross hatches, this baby ran perfect for three weeks then it would miss for a minute then be fine.....misses all the time now.....dealer says this is how coil overs act on the way out... spordiac like that.....the problem is this is apperently not bad enough to throw out a code....so short of taken out to the big scope.....200$$$ is there a way to figure out what ## ??? Mike in Omaha
If someone you know has a good scanner it will tell you miss fires per cylinder, that is what you need to know, either switch out the COP or change them to another location to see if they missfire in that location to make sure it is the COP.
If someone you know has a good scanner it will tell you miss fires per cylinder, that is what you need to know, either switch out the COP or change them to another location to see if they missfire in that location to make sure it is the COP.
Missfires due to the COP are very commonly not reported. If he doesn't have a CEL, he's got nothing to go on in the missfire department. The thread I provided a link for goes over all the troubleshooting for this.
Missfires due to the COP are very commonly not reported. If he doesn't have a CEL, he's got nothing to go on in the missfire department. The thread I provided a link for goes over all the troubleshooting for this.
I have autoenginuity scanner software for my laptop, I had the same problem, no CEL, my software will tell you percent missfire per cylinder, that's how I fixed my missfire issue. All depends on the scanner being used, an autozone scanner will not tell you this, a snap on scanner or many others I'm sure as mine does, will tell you missfires per cylinder.
I have autoenginuity scanner software for my laptop, I had the same problem, no CEL, my software will tell you percent missfire per cylinder, that's how I fixed my missfire issue. All depends on the scanner being used, an autozone scanner will not tell you this, a snap on scanner or many others I'm sure as mine does, will tell you missfires per cylinder.
That sounds great, but I wonder what it references to know that it has a misfire? I have a decent scanner, it does all vehicles, abs codes, data loggin, etc, but it still can't detect a missfire unless the engines computer detects it...and if the engine's computer detects it, usually it will throw a CEL. Not always, but usually. Hmmm. How pricey was that software you have?
That sounds great, but I wonder what it references to know that it has a misfire? I have a decent scanner, it does all vehicles, abs codes, data loggin, etc, but it still can't detect a missfire unless the engines computer detects it...and if the engine's computer detects it, usually it will throw a CEL. Not always, but usually. Hmmm. How pricey was that software you have?
No, actually you have to have an almost dead cylinder before you light a CEL on these engines. A misfire will throw a pending code, but before a CEL is lit you need X misfire codes over a Y time period. You can have a real rough running engine with no CEL. This is why it is important to use a scanner that reads the pending codes.
I have read on this blog and in Ford service manuals that the CEL will not illuminate in many situations that you would otherwise expect. The reason is the V-10 is listed as a 'heavy duty engine' according to the emission folks.
The hand-held scanners that most of you (and me) have will not detect this. A high-end scanner (like the dealer has) with an oscilliscope will do the trick.
Mine was diagnosed in the service drive. Upon inspection the locking tab had broken out of the plug causing an intermittent connection.
No, actually you have to have an almost dead cylinder before you light a CEL on these engines. A misfire will throw a pending code, but before a CEL is lit you need X misfire codes over a Y time period. You can have a real rough running engine with no CEL. This is why it is important to use a scanner that reads the pending codes.
Gotcha, that makes perfect sense now. But still...my scanner reads pending codes...wonder why I never was able to see any misfires before.
That sounds great, but I wonder what it references to know that it has a misfire? I have a decent scanner, it does all vehicles, abs codes, data loggin, etc, but it still can't detect a missfire unless the engines computer detects it...and if the engine's computer detects it, usually it will throw a CEL. Not always, but usually. Hmmm. How pricey was that software you have?