I have no way to pull the code either, looks like I'm taking a trip to autozone. I had just installed the ECU plus, went for a drive, got my buddies laptop, it threw a code on the way back home.

Started up pretty nasty too, made some noise when I just started it.

 

Probably will be the PO300 code.

Have you checked that the cam angle sensors are set to EVO? It is now a default but I don't know when you bought your system.

PM tom.

Boltz.- accidentally posting as Eve-slow

 

It was the p0300 code x2. I just bought my ecu+ this week.

I didn't get a chance to check out the settings because my laptop died.

 

That P0300 code is the bane of my existence! I've been working on it, so last night I deliberately completely hosed up the ECU+ firmware to the point that my car was bucking and surging and stalled out when you came to a light. Total codes: zero! There's something that Mitsubishi did seriously different in the 2005 ECUs that fixes the P0300 problem seen on the 2003-2004 cars.

I'm gonna get this figured out if it kills me. I couldn't get it to happen on my Eclipse, so I go out and buy an EVO, and I still can't make it happen.

All - if you have any particular driving pattern that seems to cause this code, I'd like to hear about it.

Tom

 

3 codes total so far today in about 40 total minutes of driving. All three codes at WOT all in 2nd gear.

Trust me when I say I want to get this figured out as well. If you could take a look at my log in the other thread I would appreciate it, I'm awake and I can make runs and adjustments as need be.

 

Mine only occur at very low RPM or at Idle. I don't think it is related to ECU+ as I was getting it WAY before ECU came to market too.

 

I was seeing 2.5 volts from around 5500-7500rpm in knock. I added fuel, the knock is now half that at the same RPM and I picked up 15hp.

 

Tom - You can have my car for a week as a beta tester to figure it out, I have an 03. Just make sure you leave an ECU + in it when I come pick it up BWHAHAHAHAHAHA


Actually I'll be going up toward your neck of the woods when I get home some if you need an 03 to play with a little let me know.

Dan

 

i can make my car give the p0300 code on demand.

second or third gear at 6500+ rpm not accelerating, just "cruising" and it will throw the code and run like crap for a few seconds.

I never threw the code unless i did that before i installed the cams, now after i installed cams it throws it when i idle.

Im just thinking about buying a CReader and being done with it.

 

Yeah, the P0300 is a given. I've thought about going to the dealer to get their P0300 fix. The car still runs the same, so no reason to worry. Tom will figure it out.

So Tom, what I'm hearing is it doesn't happen on the 05's? I wonder if it's something Al might be able to correct to match the 05 ecu?

 

Maybe, but I'd like to figure it out anyway. Seems like if a car doesn't throw the code without the ECU+, then it shouldn't with it, either. Maybe indicates an "opportunity for improvement" as they say in the management meetings at work!

Tom

 

I'll have to give that a try. I usually cruise at 2500 RPM - don't think I've ever tried revving that high for an extended period of time. How did you ever notice this?

Tom

 

Understandable Tom, I'm sure you'll find it.

 

LOL street racing from a 70 mph kick in 3rd gear.


believe me, i dont do it often.

 

From what I have read about the PO300 code in other threads is that it is related to an overly sensitive knock sensor, as the code occassionally is set following say a Harley or a large truck. I have even read about guys going over RR tracks and getting the code.

That being said, I never got the code prior to the ECU+ neither did my buddy, who has a '04. I know Mitsu reprogramed the portion of the knock sensoring system of the '05s to correct for this probem and apprarently it is working.

What I don't understand and I am sure Tom is scratching his head about to is why do the '03s and '04s that didn't have the PO300 problem prior to the ECU+ now have the problem? Tom has theorized that his algorithm to keep the OEM ECU happy in the timing section is that his algorithm is either moving to fast or too slow to what the OEM ECU wants to see. When that happens BOOM CEL PO300

Unfortuntely, no one has been able to set the CEL on demand until EvilDylan, so hopefully that will help Tom figure this out as he has been at this for nearly 2 years off and on

PO300

Just goes to show that he isn't goingto give up until it is solved