94170008 to 94170015 = no more cruise p0300 - EvolutionM - Mitsubishi Lancer and Lancer Evolution Community



94170008 to 94170015 = no more cruise p0300

Reply
 
 
 
Thread Tools Search this Thread
Old Jul 23, 2008, 08:43 PM   #1
Evolved Member
Thread Starter
iTrader: (5)
 
Smogrunner's Avatar
 
Join Date: Aug 2003
Location: Inland Empire, CA
Posts: 3,558
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 03 Evo VIII bought new, orignal owner

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.

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.
Offline
 
Reply With Quote
Old Jul 23, 2008, 11:52 PM   #2
EvoM Guru
iTrader: (6)
 
Join Date: Feb 2007
Location: Melbourne, Australia
Posts: 9,475
Thanked 37 Times in 29 Posts

Drives: WW EvoX GSR

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..
Offline
 
Reply With Quote
Old Jul 24, 2008, 05:29 AM   #3
Evolved Member
iTrader: (19)
 
chmodlf's Avatar
 
Join Date: Oct 2004
Location: CT
Posts: 885
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 03 EVO

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.
Offline
 
Reply With Quote
Old Jul 24, 2008, 05:33 AM   #4
Evolved Member
iTrader: (53)
 
Evoryder's Avatar
 
Join Date: Apr 2004
Location: ☼ Florida ☼
Posts: 7,336
Thanks: 0
Thanked 1 Time in 1 Post

Drives: EVO METH MACHINE

Glad you got it fixed. I had the issue w/ too lean at cruise
Offline
 
Reply With Quote
Old Jul 24, 2008, 08:59 AM   #5
Evolved Member
iTrader: (94)
 
EvoDan2004's Avatar
 
Join Date: Feb 2005
Location: New Jersey
Posts: 8,983
Thanks: 0
Thanked 2 Times in 2 Posts

Drives: 03 Evolution 8

tephra

any chance in a patch or fix in disabling the p0300 code all to geather so it cant come on at all??
Offline
 
Reply With Quote
Old Jul 24, 2008, 09:11 AM   #6
Evolved Member
iTrader: (37)
 
gsrboi80's Avatar
 
Join Date: Aug 2005
Location: Where the streets have no name
Posts: 7,719
Thanked 18 Times in 18 Posts

Drives: 03 TB VIII

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
Offline
 
Reply With Quote
Old Jul 24, 2008, 11:02 AM   #7
Evolving Member
 
Join Date: May 2007
Location: Europe
Posts: 207
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: Evo VIII

What is RPM adress for boost limit in 94170015(with Tephra mod)???
I opened boost limit table and RPM column is in incorrect
Offline
 
Reply With Quote
Old Jul 24, 2008, 11:10 AM   #8
Evolved Member
iTrader: (37)
 
gsrboi80's Avatar
 
Join Date: Aug 2005
Location: Where the streets have no name
Posts: 7,719
Thanked 18 Times in 18 Posts

Drives: 03 TB VIII

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

So 6dd2 is the right address

Last edited by gsrboi80; Jul 24, 2008 at 11:13 AM.
Offline
 
Reply With Quote
Old Jul 24, 2008, 12:28 PM   #9
Evolving Member
 
Join Date: May 2007
Location: Europe
Posts: 207
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: Evo VIII

Quote:
Originally Posted by gsrboi80 View Post
<table name="Boost Limit" address="3614">
<table name="RPM" address="6dd2" elements="9"/>

So 6dd2 is the right address
Thank's. Working great now
Offline
 
Reply With Quote
Old Jul 24, 2008, 12:28 PM   #10
Evolved Member
iTrader: (37)
 
gsrboi80's Avatar
 
Join Date: Aug 2005
Location: Where the streets have no name
Posts: 7,719
Thanked 18 Times in 18 Posts

Drives: 03 TB VIII

np bud
Offline
 
Reply With Quote
Old Jul 24, 2008, 01:25 PM   #11
Evolved Member
iTrader: (53)
 
Evoryder's Avatar
 
Join Date: Apr 2004
Location: ☼ Florida ☼
Posts: 7,336
Thanks: 0
Thanked 1 Time in 1 Post

Drives: EVO METH MACHINE

Quote:
Originally Posted by gsrboi80 View Post
np bud
way to rep my quote in your sig...i guess it was pretty funny?

back on topic.
Offline
 
Reply With Quote
Old Jul 24, 2008, 01:56 PM   #12
EvoM Guru
iTrader: (6)
 
Join Date: Aug 2004
Location: Birmingham, AL
Posts: 6,267
Thanks: 0
Thanked 11 Times in 10 Posts

Drives: Evo VIII/SVO Mustang/BMW E30 M3

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.
Offline
 
Reply With Quote
Old Jul 24, 2008, 01:57 PM   #13
EvoM Guru
iTrader: (8)
 
razorlab's Avatar
 
Join Date: Aug 2003
Location: Alameda, ca
Posts: 10,198
Thanked 129 Times in 113 Posts

Drives: a laptop connected to your ECU.

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

Consider yourself lucky.
Offline
 
Reply With Quote
Old Jul 24, 2008, 03:07 PM   #14
Evolved Member
iTrader: (9)
 
Slo_crx1's Avatar
 
Join Date: Sep 2007
Location: Simpson, PA
Posts: 821
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: '03 Evo 8, '92 Integra GS-R

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.
Offline
 
Reply With Quote
Old Jul 24, 2008, 03:20 PM   #15
EvoM Guru
iTrader: (8)
 
razorlab's Avatar
 
Join Date: Aug 2003
Location: Alameda, ca
Posts: 10,198
Thanked 129 Times in 113 Posts

Drives: a laptop connected to your ECU.

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

Related Topics
Thread Thread Starter Forum Replies Last Post
P0300 help !!!!!!!! DJErickG Evo General 4 Feb 11, 2015 05:57 PM
Problem with Tephras NLTS patch awdordie EcuFlash 4 Apr 20, 2012 10:20 PM
94170008 ROM 2 byte load mod for dummies (like me :) A418t81 EcuFlash 62 Nov 6, 2009 04:19 PM
Tephra, can you make a mod to fix the VIII's p0300 issue? Mr. Evo IX EcuFlash 68 Nov 1, 2008 11:17 PM
Changed ECU, OBDII testing steadly2004 EcuFlash 9 Sep 28, 2008 04:28 PM


Tags
2002, 2004, 94170008, civic, highway, honda, immobilizer, lancer, misfire, p0300, part, po300, problems, springs, throttle

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



All times are GMT -7. The time now is 01:46 AM.


 
  • Ask a Question
    Get answers from community experts
Question Title:
Description:
Your question will be posted in: