At wits end with spark plugs and P0300
Nov 10, 2011, 07:22 AM
#19
Evolved Member
Thread Starter
iTrader: (89)
Join Date: Nov 2009
Location: Boston
Posts: 1,073
Likes: 0
Received 0 Likes
on
0 Posts
I apologize if I come across as stubborn.
Nov 10, 2011, 07:59 AM
#20
Evolving Member
iTrader: (8)
Join Date: Aug 2007
Location: florida
Posts: 215
Likes: 0
Received 0 Likes
on
0 Posts
it could be completely unrealated to the tune. some roms are just very picky.
I never had the code until i swapped my gsc cams in .. my code trips at idle because of how hard it cams out .
His hks are mild cams but the rom can just be sensitive to the "misfire" from cams.
I never had the code until i swapped my gsc cams in .. my code trips at idle because of how hard it cams out .
His hks are mild cams but the rom can just be sensitive to the "misfire" from cams.
Nov 10, 2011, 08:42 AM
#21
Not possible either
1 It was not properly disabled
2 Code was not cleared after disabling it
Nov 10, 2011, 09:25 AM
#23
People post up about this code constantly. It is nothing new. A quick search brings up a ton of info.
If you have an evo 8 of any year it is a pretty common problem. The patch was made up by some very smart individuals who had the problem as well. I could not tune out the problem so I simply disabled it years ago.
I used to get it every 30 seconds or less while cruising. I had no mechanical issues.
If you have a taxtric cable I could walk you through it. If you do not have one. I would buy one. It is extremely helpful to have in general when dealing with the ecu.
Good luck, don't make things too hard on yourself...
If you have an evo 8 of any year it is a pretty common problem. The patch was made up by some very smart individuals who had the problem as well. I could not tune out the problem so I simply disabled it years ago.
I used to get it every 30 seconds or less while cruising. I had no mechanical issues.
If you have a taxtric cable I could walk you through it. If you do not have one. I would buy one. It is extremely helpful to have in general when dealing with the ecu.
Good luck, don't make things too hard on yourself...
Nov 10, 2011, 09:32 AM
#24
Evolved Member
Thread Starter
iTrader: (89)
Join Date: Nov 2009
Location: Boston
Posts: 1,073
Likes: 0
Received 0 Likes
on
0 Posts
People post up about this code constantly. It is nothing new. A quick search brings up a ton of info.
If you have an evo 8 of any year it is a pretty common problem. The patch was made up by some very smart individuals who had the problem as well. I could not tune out the problem so I simply disabled it years ago.
I used to get it every 30 seconds or less while cruising. I had no mechanical issues.
If you have a taxtric cable I could walk you through it. If you do not have one. I would buy one. It is extremely helpful to have in general when dealing with the ecu.
Good luck, don't make things too hard on yourself...
If you have an evo 8 of any year it is a pretty common problem. The patch was made up by some very smart individuals who had the problem as well. I could not tune out the problem so I simply disabled it years ago.
I used to get it every 30 seconds or less while cruising. I had no mechanical issues.
If you have a taxtric cable I could walk you through it. If you do not have one. I would buy one. It is extremely helpful to have in general when dealing with the ecu.
Good luck, don't make things too hard on yourself...
Last edited by Ralliartize It; Nov 10, 2011 at 09:36 AM.
Nov 10, 2011, 09:47 AM
#25
0008 ROM is what they left the factory with. Don't spend money on any other ignition related components man. I would get it on a 0015 ROM and have your fuel and ignition tables tuned correctly, your ignition map prob looks like this:
88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 8888888888888888888888888888888888888888
From there if the issue still remains disable the code routine.
88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 88888888888888888888888888888888888888888888888888 8888888888888888888888888888888888888888
From there if the issue still remains disable the code routine.
Nov 10, 2011, 11:08 AM
#29
Second is most likely the wires themselves. They always run like crap when the P0300 gets thrown, there is some limp map that it will refer to (or low octane maps for that matter).
I would change the wires and have the P0300 disabled. Send me your ROM and I can get it taken care of if you have a cable.
Aaron
Nov 10, 2011, 11:18 AM
#30
Evolved Member
Thread Starter
iTrader: (89)
Join Date: Nov 2009
Location: Boston
Posts: 1,073
Likes: 0
Received 0 Likes
on
0 Posts
Aaron thank you for the offer. Sadly I the tactrix 1.3D cable which is just the datalogger only cable. At this moment in time I have no way of pulling my map. In the interim i will take your advice and order new plug wires.