Ford Mustang Forum banner
1 - 20 of 21 Posts

Jasmat

· Registered
2012 mustang premium, 3.7, manual, 3.73 , pypebomb cat back, ksport coilovers, 235/50/18
Joined
·
20 Posts
Reaction score
3
Discussion starter · #1 ·
I unfortunately have a code p0302 stored on my computer, cylinder 2 misfire. The check engine light flashes for about 10 - 15 seconds , can faintly hear a misfire , and than it goes away . Typically happens within first 10 minutes of driving while holding 3200 rpms or so .

Only had car for just over a month and this started about two weeks ago , maybe once every other day or so the CEL flashes for a few seconds.

I swapped coils 2 with 4 but p0302 code returned, today I swapped plugs 2 and 4 though they both looked clean .

Next step may be to test the resistance at cylinder 2 fuel injector.

Any advice or tips appreciated.
 
Your troubleshooting and process of elimination is good so far. Next, I would also suspect the injector to be the problem. You also might want to have a look over the wiring/connectors/harness for the coil, plug, and injector to look for damage or see if a rodent didn't start to have at anything in there. With no other accompanying code a single cylinder misfire is usually pretty basic in its nature: coil, plug, or injector.
More rarely a basic internal engine issue or a bad PCM are the cause but these would be much less likely.
 
Discussion starter · #3 ·
I checked injector and coil connectors, thought problem was gone but returned 3 days later briefly. I scanned the obd2 with bluedriver, here is a link if anyone wishes to check it out. Says 27 misfires on cylinder 2 but a few other cylinders have 5 or so misfires.

Meet Google Drive – One place for all your files
 
I checked injector and coil connectors, thought problem was gone but returned 3 days later briefly. I scanned the obd2 with bluedriver, here is a link if anyone wishes to check it out. Says 27 misfires on cylinder 2 but a few other cylinders have 5 or so misfires.

Meet Google Drive – One place for all your files
It's best if you just post the actual codes or a screenshot. There are people that don't like opening files/links like that. You also need a google account and to sign in to view them so unless you post what the codes are you won't get help from some people on here me included.
 
A few cylinders have 1-8 misfires per cylinder either the average over the last 10 driving cycles or the last cycle while others have none. #2 has 7 average misfires for the last 10 driving cycles with 27 misfires for the last driving cycle which apparently triggered the P0302 code. Are there still no other codes being registered?
 
Discussion starter · #8 ·
No other codes registered . I'm considering replacing the purge valve solenoid but not sure that will help.

Might be the crank sensor going bad also.
Did you ever replace yours? If so did you do the relearn?
 
No other codes registered . I'm considering replacing the purge valve solenoid but not sure that will help.
I noticed that it said EVAP test wasn't completed but it seems odd to me that no other codes were registered. You are using a Bluedriver dongle though. Another member was reporting inconsistencies with their Bluedriver on here recently. Maybe drive the car to an auto parts store and see if they can pull codes with an actual scan tool.
 
Discussion starter · #10 ·
I noticed that it said EVAP test wasn't completed but it seems odd to me that no other codes were registered. You are using a Bluedriver dongle though. Another member was reporting inconsistencies with their Bluedriver on here recently. Maybe drive the car to an auto parts store and see if they can pull codes with an actual scan tool.
The bluedriver never actually read the code, I pulled the p0302 using my hypertech programmer.
 
Check and see if the cat on that side is clogged or damaged. Climb under and hit the side of the cat with your fist and listen for a rattle. My 12 coyote would throw 302/304 code. Ford checked the misfires and said that the number 4 cylinder wall was scratched and scored. Engine was replaced and new motor had same exact codes. Passenger side cat was clogged. They wanted 1k to replace cat. I replaced both sides for 450$ and it runs great. Doesn’t hurt to check. Hope this helps.
 
  • Like
Reactions: Jasmat
Discussion starter · #12 ·
Check and see if the cat on that side is clogged or damaged. Climb under and hit the side of the cat with your fist and listen for a rattle. My 12 coyote would throw 302/304 code. Ford checked the misfires and said that the number 4 cylinder wall was scratched and scored. Engine was replaced and new motor had same exact codes. Passenger side cat was clogged. They wanted 1k to replace cat. I replaced both sides for 450$ and it runs great. Doesn’t hurt to check. Hope this helps.
Thanks for the tip , I was wondering about them sensors themselves seeing I have a pipe bomb exhaust wasn't sure if I have extensions people were having problems with.
 
A clogged cat is a possibility but it should give a code. The downstream O2 sensors should report the functionality of the cats to the PCM. Being that some cylinders on both banks of the engine are giving a misfire every now and then I wonder if the mystery cause just isn't bad enough yet to register a code. This is one of those frustrating problems to figure out.
 
I never got a code for my cat, only the misfire. Took two trips to ford to find out it was clogged. They never got a code either, they heard the rattle.

My passenger side cat.


New cats and H pipe
 
  • Like
Reactions: Jasmat
Yes.no problems with sensors. Mechanic said he has only seen this a few times in his 20+ years as a mechanic for Ford. Sorry for the delay in response, I was having new wheels put on the wife’s ranger and I had to cut the grass before the rain comes.
 
3 hours is actually pretty fast to respond on these forums.
My theory in your case is that the cat was still partially functioning and just on the edge of throwing a code but functioning poor enough with the restriction to cause the misfires.
Also, with other issues I have read of codes not being registered like with low fuel pressure so that might just have been one of those odd instances of the PCM just not registering when it should have. That makes things so much harder to figure out. At that point monitoring live data and knowing what to look for out of/on the edge of normal ranges is helpful.
 
1 - 20 of 21 Posts