Notices
ECU Flash

Rom ID issues, '03 Evo 8

Thread Tools
 
Search this Thread
 
Old Nov 18, 2007 | 09:48 AM
  #1  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
Rom ID issues, '03 Evo 8

I've tried a few different versions of EcuFlash to see if it's the program, and so far every version gives me the same thing. My car's rom ID is currently 94170015 and the program's values looked very screwed up when opening the rom. Not only that, but I can't seem to use the 2 byte load or any patches to the rom. Now if I open 94170008 everything shows up perfectly in EcuFlash and I can do the 2 byte load and maf scaling or anything else for that matter. Is this a common issue for the 0015 rom? After doing some research it seems that it's the "p0300" update issued by the stealership, and I'm wondering if I downgrade my ecu to the 0008 rom if I'm going to have the code popping up all the time. Right now the car seems to run pretty well with the 0015 coding, and that may have a part in why my datalogging has been so picky and showed some strange values on my first few attempts. Which direction should I go? Sorry for the noobish question, this one's got me puzzled though.
Reply
Old Nov 18, 2007 | 11:46 AM
  #2  
cpoevo's Avatar
Evolved Member
iTrader: (1)
 
Joined: Apr 2006
Posts: 880
Likes: 1
From: SD
Since your car is an 03 you should have the 008 ECU. Its from when it was flashed they used the 015.
Reply
Old Nov 19, 2007 | 02:48 PM
  #3  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
Originally Posted by cpoevo
Since your car is an 03 you should have the 008 ECU. Its from when it was flashed they used the 015.
That I already know. Basically I want to know if the original 008 map will be reliable without tossing the dreaded knock code if I downgrade for better control of my tuning. Right now I can't do squat with the 015 map, every time I try to add the 2 byte load variable or change anything else is screws up all the values how they are read in EcuFlash. Not only that, but some of the tables show screwed up values (mostly the boost tables) without me even touching the map. It's like EcuFlash doesn't have the correct files to properly read the 015 map.
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Evo_Goodness
ECU Flash
18
Sep 2, 2016 05:05 PM
Ultraspeed EVO
ECU Flash
1
Feb 21, 2016 05:10 PM
br3akrboi
ECU Flash
2
Dec 6, 2015 11:40 AM
Pd1
ECU Flash
278
Oct 11, 2009 05:17 PM
fireroasted
ECU Flash
2
Mar 14, 2009 12:16 AM




All times are GMT -7. The time now is 04:22 PM.