I would like to also mention that I see quite a few EVOs, nearly all the 2003-2004 models come into my shop with the splines on the input shaft worn down so severe that the gear rattles around because of the sloppy splines on the shaft.

If those with an 2003-2004 EVO could make proper comparisons between 4th gear and 5th gear in regards to the knock sensor output it should be possible to see....I don't know...something different between the two gears that correlates with the splines being worn down.

I'm guessing the knock sensor is picking up the backlash.

Jon@TRE

 

I have about 1400 miles on my fresh tranny and it is still throwing the code.

Now when I 1st got it, I drove about 60 miles @ 75 - 80mph. I was letting it cool down while waiting for some friends and that was when it 1st tripped. Never got it before the cams either.

 

Hey man,

So what do you think about the possibility of an improperly tensioned timing belt? I know a few people have started throwing p0300's right after a timing belt replacement only to find that it was not tensioned properly during the install. Since most of us get the code after installing cams, which involves messing with the tensioner mechanism........

 

If done properly and all your parts are in working order, tension should remain the same. The pully you use to tighten down the tbelt does not get messed with at all. Once you remoce the tensioning tool, the tensioner goes right back to where it was before.

I am sure it is possible to trip the light if it is off a tooth, but I would think the ecu would have enough room for the timing belt to stretch out or something over time to not toss that code.

 

Well,
As I suspected, the dealer P0300 fix did not work at all. FLashed the fix rom in last night, cleared the codes, drove into work this am, pulled pending codes when I got to the office, sure enough P0300 waiting on me like a faithful little pet.....

My ECU+ should be back from it's hardware upgrade this week, So I will see if it can keep the P0300 at bay long enough to get my inspection, then I will look at replacing my timing belt, tensioner, and crank angle sensor. It;s about time for my timing belt anyway....

 

crap... that's bad news for me.

 

the SES light doesn't bother me nearly as much as you guys I guess...it's just part of it.

 

Do you have OBDII inspections where you live? I cannot get my tag If I don't pass OBDII inspection. Can't pass OBDII with a code set so....

 

I don't but it clears if you disconnect the battery for awhile, can you do that before you get inspected?

 

Not in my state. In order to pass OBDII all the readiness checks need to pass. Disconnecting the battery makes them not ready.

Automatic F-

 

good info Dennis, I didn't know that. Has anyone swapped cams back to stock just to pass? it would be no different than changing back to the stock cat if that were an issue.

 

so i've had my HKS 280's in for a few weeks and finally I got the code the other day.. I reset the ecu and it went away for a day or so and it came back. I've leaned to ignore the code. Today I noticed it was gone.. I didn't change a thing *shrug* I'm sure it'll be back.

 

One trick I have seen work on a friends car with 280's in it - tension the throttle cable to idle the car around 1600 RPM's or so. Should keep the idle misfire from occuring and might get you by the readiness tests.

 

I think this is one of those codes that will reset itself after a few key turns/starts and there is no further detection of misfire.

My rear o2 flags everytime it rains out after the first start and goes away in a couple days. Strange yes, I wouldn't believe someone if they told me this, but it happens to me without fail.

 

Well, I'm getting short on options so I may try that but man I would feel silly driving around in a car that idles at 1500rpm..... anyone know what the idle limit is? I don't guess it matters for the obdII tests as much as it used to for the sniffer tests.