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.
I had my intake mani resealed/new gaskets a couple years a ago and am getting an intermittent miss and rough idle. I want to rule out a COP so my question is, will it throw a fault code and is it intermittent in it's bad behaviour. Thanks
Yes any misfire should throw a code, something in the P0350 range.
If the miss is intermittent though you can try pushing inward on the COP connector from the chassis wiring, checking if its making good contact. Sometimes the locking tabs on the harness connectors fail giving you a similar problem. They're easily replaceable with an NAPA part EC259 or something similar.
I had my intake mani resealed/new gaskets a couple years a ago and am getting an intermittent miss and rough idle. I want to rule out a COP so my question is, will it throw a fault code and is it intermittent in it's bad behaviour. Thanks
All misfires "should' throw a code, but I also believe that you can have a weak spark that will sound like a misfire without throwing a code. By throwing a code it will not illuminate the SES (Service Engine Soon) light. You HAVE to check for codes and not assume that because the SES light is not lit that you don't have a code.
Depends on the year of the truck - the 2-valve V10s with OBD-I will not light the check engine light, but MIGHT log a code that can be read with a reader.
Depends on the year of the truck - the 2-valve V10s with OBD-I will not light the check engine light, but MIGHT log a code that can be read with a reader.
True. I guess I should have clarified. I was referring more to the OP's 2000. As always, thanks Art.
Depends on the year of the truck - the 2-valve V10s with OBD-I will not light the check engine light, but MIGHT log a code that can be read with a reader.
Of course this is correct---I was assuming OBD-II as the OP didn't list his truck year, that I can see anyway!
Thanks everyone. It is a 2000 2V. It has also had an intermittent SES in the past and is now showing SES light. I can use our mechanics code reader in the morning and see what it reads.
OK, I came up with a cyl. 8 misfire on the scanner. It seems like the codes were not capturing earlier when the SES light was intermittent because I scanned it then and came up clear.
Anyway since I wasn't sure which side was #8 I checked both sides and it seemed like the driverside, 4th plug back connector slid on just a little. So far it's smoothed out. I'll spend a little more time with it this weekend. Thanks everyone.