Stock Roms and XML link...

[mtcavity]

The definitions are there to be looked over for verification, and in the interest of map/model comparison. I will probably not use all but my own definition for my Galant, and will not "completely" trust the XMLs until they are directly released here (in newer ECU Flash releases).

Please contact me if you see any corrections or have any questions.

00_GALANT_ES_USDM_AT_85850014
01_ECLIPSE_GS_USDM_MT_96510009
01_ECLIPSE_GS_USDM_AT_85850013
01_ECLIPSE_GT_USDM_AT_86720008
01_ECLIPSE_GT_USDM_MT_96720008
01_ECLIPSE_GT_USDM_MT_96720009
01_ECLIPSE_GT_USDM_AT_86720009
01_GALANT_ES_USDM_AT_85850013
01_LANCER_EVO7_JDM_MT_93390000
01_LANCER_EVO7_JDM_MT_99860002
01_LANCER_EVO7-RalliArt_EDM_90550001
01_LANCER_EVO7-RalliArt_JDM_92460000
01_MIRAGE_ ES_USDM_87260006
01_MIRAGE_LS_USDM_97250005
01_STRATUS_RT_AT_85120031
02_ECLIPSE_GS_AT_88930010
02_ECLIPSE_GS_MT_98950010
02_ECLIPSE_GT_AT_88840009
02_ECLIPSE_GT_MT_98850010
02_ECLIPSE_GT_MT_98850010
02_LANCER_EVO7_GSR_EDM_88840013
02_LANCER_EVO7_JDM_98640014
02_LANCER_EVO7_JDM_AT_80700010
02_LANCER_EVO7_JDM_MT_98640014
02_LANCER_EVO7_JDM_AT_80700010
02_LANCER_OZ_MT_98720010
04_AIRTREK_JDM_AT_TOMEI_89970017
02_AIRTREK_JDM_AT_89970010
03_AIRTREK_JDM_AT_83540008
03_ECLIPSE_GS_MT_90920006
03_ECLIPSE_GT_MT_97560014
03_ECLIPSE_RS_MT_90920009
03_GALANT_ES_AT_80890008
03_GALANT_ES_USDM_80890007
03_LANCER_OZ_USDM_81900006
03_LANCER_ES_USDM_81900015
03_GALANT_GTZ_AT_80930005
03_STRATUS_RT_AT_81000005
04_LANCER_EVO8_EDM_RalliArt_99270000
04_LANCER_EVO8-MR_USDM_MT_94170008
04_ECLIPSE_GS_MT_94830008
04_LANCER_ EVO8_USDM_94170008
04_LANCER_ EVO8 GSR Ralliart_JDM_MT_97250001
04_LANCER_EVO8_FQ300_JDM_93660005
04_LANCER_EVO8_JDM_96260007
04_LANCER_EVO8_JDM_96260009
04_LANCER_EVO8_USDM_94170008
04_LANCER_EVO8_USDM_94170015
05_ECLIPSE_GT_MT_94450007
05_LANCER_EVO8_AUS-SA_96530006
05_LANCER_EVO8_JDM_MT_97470001
05_LANCER_EVO8_USDM_96940011
05_LANCER_EVO9_AUS_88580013
05_LANCER_EVO9_EDM_88580014
05_LANCER_EVO9_GSR_JDM_88570008
06_LANCER_EVO9_AUS_88590013
06_LANCER_EVO9_EDM_88840016
06_LANCER_EVO9_JDM_88900006
06_LANCER_EVO9_JDM_89280002
06_LANCER_EVO9_USDM_88590014
06_LANCER_EVO9_USDM_88590015

[mtcavity]

Here is a backup of my Mitsubishi and Dodge XML folders.

I am posting XML definitions for checking purposes only! I feel very certain about them, BUT! I have not tried them on any of the vehicles. This is only for verification of addresses, XML definition/model archiving, and general model comparison.

Please notify me of ANY errors, missed tables or features.

[nvr2fast]

Good stuff should be sticky!

[mtcavity]

The XML file associated with the EVO 8 FQ300 needs to be re-downloaded and replaced or adjusted to flash this vehicle.

The problem was with the flash method listed in the XML definition. The error was the flash method listed as "EVO" while it should be "mitsukernel".

I apologize to all whom have been affected by this error.

[mrfred]

When I try to use the 89290002.xml and 88900006.xml definitions in ECUFlash, the program will not launch. Its giving an error about not being able to complete the launch process. I looked through the first few lines of the .xml files and didn't see anything odd. I'm running ECUFlash 1.29 and WinXP.

[vajid]

I could not find a stock ROM for 03' Lancer EVO8 USDM? Any pointers appreciated.

[mtcavity]

I noticed that myself, seems no one has posted any 03 EVO ROMs (and no 02 USDM EVOs).

Any 2002-03 EVO owners out there?

Ask around you might get away with 02, but I personally like to ONLY flash the ROM that was pulled from the vehicle.

Another option is if you own an 03 EVO USDM, purchase a cable, pull a ROM and post it.

[vajid]

My problem is I need to remove the Speed Cut of 180Km/h .. I cant seem to find the right definition files for my car.. I can read the ROM, make changes but dont wana write it back .. im not sure if it's the right definition (evo7base) is the only closest one.. and might end up screwing my car.

[mtcavity]

If you post the ROM, we can look it over to double check definition addresses and make suggestions/changes if applicable.

It took me 4 months to build up enough confidence to flash my car, but with enough reading the wealth of information on this and other sites I feel VERY safe about my flashes.

Take your time, ask questions (no matter how noob), and READ!

Unless you post the ROM, you will have to trust your own opinion on the definition addresses.

Good luck and have fun.

[mtcavity]

All XMLs posted have been updated! Knock maps were the focus along with a few questionable maps viewable only using the developmental user level.

Absolutely DO NOT USE THE ANTI LAG MAPS. These maps are open to further research and discussion, so keep an eye out for updates and info.

The knock maps in my opinion should not be changed unless you changed the bore/stroke, crank (specifically crank angle), or displacement, most of which is done achieve power and lower knock (or make it more tolerant to knock).

For example, if you are working the engine that was not a swap, and “modified” it to the point were knock is an issue. Changing the knock values is the wrong answer. It could leave you at risk on causing damage to the engine because of the lack of knock protection. The “knock” needs to be remedied by physical changes to the engine like doming the head (removing metal from the valve side of the head), replacing with modified/aftermarket pistons, changing the crank angle, different rods (decreasing stroke) or more (quantity), higher octane fuel. Point being the factory knock “is the limit” (although there will be some that disagree), with your aim to get engine output right to edge of the knock limit.

I am sure there are countless examples of where knock sensors would be changed, but most are for racing, where engine management is probably going to be aftermarket (like 9000-12000 RPM revs).

If you choose to change the knock maps, be careful. Be sure to have some sort of knock light or other knock measuring devise to save the engine from damage.

[os2]

If you are still looking here is mine - unmolested 2003 USDM EVO8 image and I'm the only owner (bought in 8/03 but image says 2004 for some reason).
Even if I'm a total noob at this that was the first thing I did in ecuFlash - backed up my image . XML definition 94170008 that comes with ecuFlash worked quite well opening up the maps.

[Newfoundlancer]

BUMP! This NEEDS to be a sticky! Thx for the help MtCavity.

[sub7]

Can I get a pointer which ECU internal id inside the file Evo 7-8-9-- XMLs - 4-9-2007.rar is associate with my evo7 JDM? Is it evo7base.xml only or there are others? What do 98640014.xml is used for then?

Thx!

[mtcavity]

ID tag (98640014) is model specific, more having to do with the way Mitsubishi handles its shops turn-around time in manufacturing/servicing and the protocol they decide to build their engine/transmission setups on. I know someone posted this in one of the first posts. At any rate, 98640014 is your car.

The “evo7base” is the file that contains “scalings”, or the mathematics that directly relates the data on your ECU to you (and then back to the ECU). The reason it is the same for the EVO 8 is that there were probably running the same basic engine management set-up, just manipulating the data in the later years for “pollution control” reasons and data upgrades. The 98640014.xml is used to define the ECU data, along with the help of the evo7base scalings, to adjust the stock map.

I am sure there are other ROMs, based on modifications, which may work for gaining performance, although there should be a nice pile of research behind this. For instance, I would research on the engine/transmission of the ROM being used right down to the pin-outs to the ECU.

Modifications of this nature are posted on sites like:
http://forums.evolutionm.net/forumdisplay.php?f=179
http://www.osecuroms.org/

Both outstanding sites. Good luck!

[sub7]

Thanks a mil MTCavity! The downsite after reading evom, it sink my learning curve due to big gap difference between my evo7 and IX. After you said, evo8 and evo7 ROM/scaling are alike, I hope the curve keep up-scaling.