Well, it's good info none the less. The ROMs are updated for a reason and you should always use the latest one. For instance, the '03 Evo VIII ROM was updated to fix the P300 codes that were being thrown incorrectly. I'm sure the Lancer updates were for something similar.

And you are just as cool as Evo drivers. We're all enthusiasts and I believe that reflashes should be just as available to the Lancer driver as the Evo driver. I really do appreciate the effort you've put in to build these definitions.

I have the definition for an '02 ES Auto at the house that I will post if I remember to. I had to make some changes before since the high/low maps were backwards initially (based on '03 OZ XML), but it's better now that I based it on your '02 XML.

 

'02 ES Auto (88560010) definition. You might want to look it over Pete, but it's based on one of your definitions.

This is the ROM image

 

Everything looks good with the exception of of the x and y axis in the ignition tables. Should make a fine addition to the collection. Thanks!

 

How would I go about fixing the values? Are there just too many cols/rows or is the scaling/address off? I'm really a newb when it comes to disassembly.

 

I'm really confused about the 2006 ES M/T definition...along with a bunch of the others. It seems that the RPM and Load are completely wrong in the definitions. I've gone and looked at my rom through a hex editor and I can see all the values, and where the definition file is pointing, and the values are just off =x. What can I do to find the real values and correct this error?

EDIT: This is what I get when I open the majority of the maps: http://img.photobucket.com/albums/v4...hundefined.jpg

 

Sorry for my English. my question is, i can write to ecu a rom of any evo in my lancer ES 2003 AT, i have a turbo custom and i need modify the timing and fuel curves

thank you

 

No. The Evo ROM cannot be flashed to a Lancer ECU.

 

ok thank you, do you have a definition for a lancer ES 2003 AT, I search in all thread of ecuflash and no worked, I mail you my rom, maybe you can help me

 

Have you downloaded the definition files that are posted in this thread? And the updated list I posted at the top? You can send me a copy of your ROM and I'll see if I have a working definition file. Send it to senate6268 at comcast.net

 

Pete, have you noticed that some Lancer definitions seem to have the high/low maps swapped? It's odd ... the maps look to be labeled correctly ... more aggressive being the high octane maps. But, when tuning, I've found that the ECU looks to the low octane maps even with an Octane value of 100.

So, it looks like the maps are labeled correctly, but the ECU isn't referencing them right ... or Mitsu goofed it somewhere.

 

I did notice that the ECU does not reference the high octane map much, if not at all. I've always tuned my car for the low octane map. I don't know what conditions need to occur for the ECU to use the high octane map.

 

Yeah, It doesn't make sense really ...

My understanding is that the ECU should reference only the high octane maps as long as the octane value stays at 100. f knock is encountered the octane value begins to drop and the ECU begins to interpolate values from the low octane maps in a percentage relating to the octane value (likely not a 1:1 with octane %).

With the last Lancer I tuned I changed the titles of the high and low maps so it would make more sense. But, as you've seen as well, the high octane maps are really never referenced. If the maps were simply titled backward the ECU would lean the mix and add timing when knock is encountered (interpolating the more aggressive high octane map) ... I haven't seen that happen.

Should we assume that the Lancer only uses the low octane maps? I still set the "high octane" maps more conservative just in case ...

 

Thank you. I work perfect but with ecuflash 1.29

another question. I can increase the I number of columns to increase the load, because I have custom turbo in my Lancer ES 2003

in ignition and fuel maps

 

You cannot add colums, but you can rescale them ...

For instance, if your columns are ...

| 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 |

you can re-scale the values to ...

| 10 | 20 | 40 | 60 | 70 | 80 | 90 | 100 | 110 | 120 |

Just edit the axis value just like you would any other values in ECUFlash.

 

Thank you!!!! it is exactly what needed