Disable P0300 on the Evo 10
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
ok, I'd have to dig deeper to separate out the P0300 from the P030X codes. Not sure when I'll be able to get to that.
So yea I hear ya on that, but still it could help spot something not in WOT that makes you check a bad sparkplug early or something.
I found these the day that MrFred posted... I guess should have posted then.
For 5557, 8 and 9:
<table name="DTC P0300 Disable/Enable (0/1)" category="Misc" address="503b5" type="1D" level="1" scaling="uint8"/>
For 5557, 8 and 9:
<table name="DTC P0300 Disable/Enable (0/1)" category="Misc" address="503b5" type="1D" level="1" scaling="uint8"/>
Aaron
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Just to be clear, it only disables P300, P0301, P0302, P0303, P0304. I'm still puzzled why you guys are worried about the P030X codes. A consistent misfire is easy to detect by seat of the pants. Heck, even a random misfire can typically be detected in a datalog. An example of something I wouldn't disable would be a crank sensor or cam sensor code.
Mine did. I wouldn't have know there was a problem either had it not been for the code. The car seemed to be running fine, threw the code so I pulled the spark plugs and found one of them to be damaged.
Honestly that is an oddity. They have thrown them for clutches, cams, valvesprings, dogs barking, etc. but I have never seen the P0300 for a misfire. In the 1G and 2G it will do it on a 6 bolt swap when you switch the cam sensors. Like Mychailo said, you can feel the hickup from a misfire, see it in a log or dynosheet (100whp drop sometimes), and never actually throw the code.







