P0300 Is this the fix for it?
#1
Staging Lane
Thread Starter
Join Date: Dec 2001
Location: Texas
Posts: 88
Likes: 0
Received 0 Likes
on
0 Posts
P0300 Is this the fix for it?
Ok just got my car back today. Had it completly rebuilt. Forged 347 runs great. BUT i still get the damn P0300 random misfire code. Now i used the search and found that some just reccomend editing out the code. Is this what i should do or is there a "real" way to get rid of it? The engine is very sound and runs like a raped ape. That lil orange light just pisses me off.
Thanks guys.
(H/C all the bolt ons) ive got edit
Thanks guys.
(H/C all the bolt ons) ive got edit
#4
TECH Enthusiast
iTrader: (12)
Join Date: Mar 2002
Location: w.s.n.c.
Posts: 539
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by stangkillin99ss
Ok just got my car back today. Had it completly rebuilt. Forged 347 runs great. BUT i still get the damn P0300 random misfire code. Now i used the search and found that some just reccomend editing out the code. Is this what i should do or is there a "real" way to get rid of it? The engine is very sound and runs like a raped ape. That lil orange light just pisses me off.
Thanks guys.
(H/C all the bolt ons) ive got edit
Thanks guys.
(H/C all the bolt ons) ive got edit
You should set all the tables marked low, in misfire detection, to 32000. that way at higher rpms real misfire will still be detected.
#5
TECH Apprentice
iTrader: (1)
Join Date: Feb 2002
Location: Harrah, OK
Posts: 347
Likes: 0
Received 0 Likes
on
0 Posts
some people edit it out by raising the temp at which the test is run so high, that it basically never runs. Some people edit it out of only the low rpms, by changing all the values for the low RPM tables to 32000. There are actually 2 low RPM tables, and a "idle by cylinder" table I think. Changing the tables to the 32000 would be the better way to go....Although I can't because it hasnt been implemented fgor 98's yet...? Anyone know another way?