EvolutionM - Mitsubishi Lancer and Lancer Evolution Community

EvolutionM - Mitsubishi Lancer and Lancer Evolution Community (https://www.evolutionm.net/forums/)
-   EcuFlash (https://www.evolutionm.net/forums/ecuflash-179/)
-   -   94170008 to 94170015 = no more cruise p0300 (https://www.evolutionm.net/forums/ecuflash/359465-94170008-94170015-no-more-cruise-p0300.html)

Smogrunner Jul 23, 2008 08:43 PM

94170008 to 94170015 = no more cruise p0300
I know that this is not a news flash for some, but I believe that many didn't know that help REALLY exists out there for this issue.

For nearly four years, I have been pestered by a p0300 code which is accompanied by simulataneous shudder/studder and a high knock count. It happens only when I am cruisin' on the freeway between 65 and 80mph in fifth gear. I'd let off the throttle momentarily and the car would be back to normal. But there would be a trouble code.

Back in the day (~2004), I rarely complained but I got 5th gear studder from time to time. I assigned blame variously from that crappy Greddy diverter valve, my Xede from Vishnu, my cams, etc. but nothing fixed it. It didn't happen all that often so I just altered my driving style to be less steady state and ignored it.

Then, I built my motor and got a turbo kit and switched to EcuFlash. The p0300 got even worse. On the freeway, I could almost replicate it at will. I had my little CReader which deleted the code, but it didn't stop the studder. Once again, I altered my driving style and tried to drive around it.

Then, two weeks ago, I discovered a error on my rom 94170008's knock table #1. It had values that were obviously wrong. I reserched here and found that MANY old Evo 8s had this knock table issue and there was fix to the code which I implemented. I was so excited to go out and test drive. Unfortunately, I still got the code! :( Back to the drawing board. :crap:

Then last week, I decided to switch to an entirely new rom. To my knowledge, the 94170008 has two newer roms that are very similar but offer slight upgrades. I started with the 94170014, but abandoned that effort and went with the newest and supposedly better 94170015. I was very careful to do the switch properly and for the last 3 days days I have been testing it.

Results?? It has completely eliminated the knock, the p0300, and the studder. I cannot replicate it regardless of how hard I try. I recommend any and all folks experiencing this problem to either do this upgrade yourself or have a trusted tuner do it for you.

tephra Jul 23, 2008 11:52 PM

cool - nice work. Good to have some good news about P0300.

I can do the stumble on freeway as well, basically boost a little bit (2-3psi maybe) then back off to 0tps then slightly back on the gas... the car will stumble like its running outa fuel for .5 sec and then run normal again.

I think its todo with fuel cuts + something with the load not being measured properly..

chmodlf Jul 24, 2008 05:29 AM

This is why I was trying to push the use of the 0015 vs the 0014 that some were favoring. Even though there are only a dozen or so different values between the two roms, you would think the Mitsu engineers had a reason for their changes.

Evoryder Jul 24, 2008 05:33 AM

Glad you got it fixed. I had the issue w/ too lean at cruise

EvoDan2004 Jul 24, 2008 08:59 AM


any chance in a patch or fix in disabling the p0300 code all to geather so it cant come on at all??

gsrboi80 Jul 24, 2008 09:11 AM

The P0300 fix is not what you see as jibberish in the 0008 ROM that is simply due to the Knock Table 1 filters being the wrong address in the XML file. A simple address change it would look normal again. Much like the Boost Limit Table I helped you fix

However the switching to the 0015 will fix the cruise P0300 alot of the times. Its not something you will see in the ECUFlash tables though

dolphin888 Jul 24, 2008 11:02 AM

What is RPM adress for boost limit in 94170015(with Tephra mod)???
I opened boost limit table and RPM column is in incorrect:(

gsrboi80 Jul 24, 2008 11:10 AM

<table name="Boost Limit" address="3614">
<table name="RPM" address="6dd2" elements="9"/>

So 6dd2 is the right address

dolphin888 Jul 24, 2008 12:28 PM

Originally Posted by gsrboi80 (Post 5927180)
<table name="Boost Limit" address="3614">
<table name="RPM" address="6dd2" elements="9"/>

So 6dd2 is the right address

Thank's. Working great now;)

gsrboi80 Jul 24, 2008 12:28 PM

np bud

Evoryder Jul 24, 2008 01:25 PM

Originally Posted by gsrboi80 (Post 5927562)
np bud

way to rep my quote in your sig...i guess it was pretty funny?

back on topic.

Ted B Jul 24, 2008 01:56 PM

Everyone with an VIII should make upgrading to the 015 ROM their first order of business. I suggest that earlier VIII ROMs no longer be supported in further developments, to reduce the workload on the developers.

razorlab Jul 24, 2008 01:57 PM

I've upgraded quite a few 03's to 015 and they still get P0300.

Consider yourself lucky. :)

Slo_crx1 Jul 24, 2008 03:07 PM

The upgrade to the 0015 map is a must, but for those of us that run cams know all too well that the p0300 code will come back eventually...but perhaps not with some things I've found.
I've run the 0015 map since the dealer reflashed the car, and never really had an issue since then. Then after installing a set of HKS 272's I started to get the p0300 code daily. After messing around with different tables this is what I've found:
I found that if I modified this table it seemed to get rid of any p0300 codes, including pending codes. I've been running this modification for almost a month now and haven't had a single code yet. Obviously when you open your map it won't look exactly like this one (this example was when I was playing with different values, my values now are pretty much just half of the original numbers), but pretty much I found that if I cut the numbers in half it would relieve the p0300 issue. I'm not sure what the timing advance pertains to, but after logging the lower load areas usually seen during cruise where the code tended to be set, that the timing numbers logged were much higher than what my map indicates. After seeing those logs and freeze frame data from when the codes were set, and adjusting this table accordingly, it seems to have cleared up completely.

razorlab Jul 24, 2008 03:20 PM

That is the EGR advance table. It basically adds to the timing advance table at those RPM areas

All times are GMT -7. The time now is 08:27 PM.