openecu.org

I am seeing all of these 05 Airtrek ROMs and they were pulled using EVO 9 read method, but all are EXACTLY like the 02-03 Airtreks that I have looked at (except for the HEX size). Even the ID Tags.

Did Mitsubishi keep the data the same for this particular model over the years? Should I apply the EVO 9 base or are the people that are pulling the ROMs not choosing the correct read method? I almost feel as though that the ECU did not change that much if the data is the same. On the other hand though, if they can only pull a ROM using the EVO 9 read method, I should logically use that flash method.

The major issue that is happening is that when I build an XML for the 05, it over-writes the XMLs of the 02-03 (depending on model ROM) because the ROMs have the same internal HEX address. It happens both ways, so as I would define one the other was overwritten, LIKE 5 TIMES. This is why I have not touched them to much.

I want to give the people that pulled the ROMs the benefit of the doubt that they are giving me the correct years, but the same HEX/XML addresses for the 03 as the 05?

Lend me your thoughts guys.

My 05 Rom has more high/low octane maps and the knock filters are different/more. They kept the most of the maps the same, but there is definantely more going on.

What I am having trouble finding are the Auto transmission maps. Found some but not all.

ROM image pulled and why.
http://forums.openecu.org/viewtopic.php?t=999

How and who.
http://forums.openecu.org/viewtopic.php ... ht=airtrek

Some others.
http://forums.openecu.org/viewtopic.php ... ht=airtrek

ROMs & XMLs.
http://forums.openecu.org/viewtopic.php?t=925
or
http://www.osecuroms.org/



Should the ID be the same for both ROMs of the 03 and 05? I was HOPING on an EVO 9 base Outlander Airtrek ROM and should re-direct my question to.

Is there an EVO 9 base Airtrek?

I figured that the ROM was pulled using whatever read method one could. The same image of 03 and 05 will then conflict until there is an EVO 7-8 read method. I scanned both in HEX and just saw 2 like ROMs based on addresses. I figured that an EVO 9 and any other ROM of the EVO 7-8 would have some obvious differences. Also could never get both ROMs to load in ECU Flash and view.

So did anyone get there “cables” on a 05 Airtrek and pull with the EVO 7-8 read method? It would be neat to have the ROM fit in a build hierarchy of some sort.

I would like to go over the entire lot of XMLs, straighten out the actual hierarchy of them to compact the files and intend on working on that soon. Is there any form of info on this to help me out? The other option is listing by hand and visual comparison of addresses (and post results I guess).

Overall I am just pleased they got the ROM with the EVO 9 read method!

My Car is a 2005 Airtrek. It was one of the last onesto be shipped to NZ.
I have tried uploading with using the 7-8 kernal, but it doesnt work.
It only works with Evo9 Kernel

I have personally done 5 different Airtrek roms people that I havent listed yet,and they all had different IDs and were from models from 2002 on.

Most of the maps were generally in the same places but things like rpm scales etc were in different places, so needed a different definition.



What are you trying to do? There should be no need to flash different roms onto other years. If you need a stock rom give me your rom id and I will see if I have that one.



Ive done the auto trans stuff- once tested properly I will rlease.

Based on previous thread, I checked the JDM 2002 map, and noticed that the value in the map starts from 13.3 to 14.7, etc .... I assume that's the A/F ratio.

However, I pulled the Tomei map, and it reads 5, 22, 40+ !!! (Inherited Airtrek map)

Is there some setting that I must configure ? Why are both maps totally way off each other ?

Are you talking about the 4 ignition maps that are the same?

I think Tomei found a cheap way to work around knock related, ignition retarding while tuning the ignition for a more aggressive mapping (maybe for the lack of wanting to go through the task of tuning the knock limits). I know nothing about what Tomei modified on the engine (pistons, rods) but this obviously worked for them. If Tomei keeps the factory warranty, I would consider it OK to a point.

If you are looking at a fuel map, you probably have the wrong XML.

Anyone else know why they keep all ignition maps the same on some tuned Mitsubishis? Is it for the reason above?

can the 03 Airtrek Turbo;s be flashed? what kind of power would they make? i am thinking about buying one, but would like some info before.

thanks!

mtcavity wrote:ROM image pulled and why.
http://forums.openecu.org/viewtopic.php?t=999

How and who.
http://forums.openecu.org/viewtopic.php ... ht=airtrek

Some others.
http://forums.openecu.org/viewtopic.php ... ht=airtrek

ROMs & XMLs.
http://forums.openecu.org/viewtopic.php?t=925
or
http://www.osecuroms.org/



Should the ID be the same for both ROMs of the 03 and 05? I was HOPING on an EVO 9 base Outlander Airtrek ROM and should re-direct my question to.

Is there an EVO 9 base Airtrek?

I figured that the ROM was pulled using whatever read method one could. The same image of 03 and 05 will then conflict until there is an EVO 7-8 read method. I scanned both in HEX and just saw 2 like ROMs based on addresses. I figured that an EVO 9 and any other ROM of the EVO 7-8 would have some obvious differences. Also could never get both ROMs to load in ECU Flash and view.

So did anyone get there “cables” on a 05 Airtrek and pull with the EVO 7-8 read method? It would be neat to have the ROM fit in a build hierarchy of some sort.

I would like to go over the entire lot of XMLs, straighten out the actual hierarchy of them to compact the files and intend on working on that soon. Is there any form of info on this to help me out? The other option is listing by hand and visual comparison of addresses (and post results I guess).

Overall I am just pleased they got the ROM with the EVO 9 read method!

Hi Mtcavity,

Finally i manage to get this Rom with EVO 9 read, hope can help.

I tried adjust it via ECUFlash, but just few of the items works, need your help on this.

Thanks.

Here you go sir, but there are stipulations that go with this!

Like I said in the post above, if you want to look at the 03 Airtrek ROM that has been pulled using the EVO 7-8 read method, you will have to remove the XML based off the EVO 9 read method. Just put it on the desktop until you are done viewing maps. If you intend on just using this XML, just leave it in the rommetadata folder. If you try to use both and load up the 03 Airtrek ROM, you will overwrite the XML you need.

I would keep an eye on monsta11’s work with these! He is doing some nice research on the Airtreks and is full of knowledge on this particular Mitsubishi model. There is also FQ-Airtrek whom is very familar with the Airtrek.

How did the 04 tuning go?

Have fun tuning and take care.

Hi mtcavity,

Sorry for my late reply, thank you very much for your help on this.

For the Tomai XML that you gave me is work, since my car already upgraded a A/R 70 turbo, Tomai 260 cam, front mount intercooler, custom made full set of exhaust…..etc, the stock ECU still can be tune via ECUFlash, and the result not bad, just facing some problem with the idle, it was too low, around 5++ to 6++ rpm, try adjust from ECUFlash idle section, feel a bit better.

Above result was 3 months ago, now I converted my gearbox to manual & the result is damn good, but the stock ECU seems like can’t support, so I drop in a Haltech. Any suggest on this? Thanks in advice.

For the 2005 Airtrek EVO 9 Readmethod XML, Just tried it yesterday on my member’s car, but facing an error to burn it back to ECU, will check & update here soon.

On last week, our Malaysia Airtrek Club organize an event, help all members remove their speed & boost cuts via ECUFlash, at the same time we do the data logging via EVOScan as well, this event quite successful, all members are learning something on it. Will continue it when we free

Attached here with the Airtrek ROMs from year 2003 – 2005 that I manage to get from above event & some Data Logging file for your reference, hope can get some advise from you & others Pro as well.

P.S. Will post up the Tomai Rom datalog file soon.

Sorry for my poor english, hope you guys understand what i means!!!


Thanks & Regards,

Yee

Congratulations on the tune and glad to hear on the sharing! But “tuning” is hard for me to do, even with data! I am hoping one of the other Airtrek owners can give you “proper” advice with map tuning (Monsta11 perhaps?).

I just installed the turbo on my 4G64 and am in search of tuning advice. Unfortunately, the best way is to take it to a professional tuner (dyno) = $$$. I am getting ever the more interested in the sporty-auto gearing, and may be using the ROM for management. I am sure there will need to be some pin re-arrangements, but luck out with a full ROM pull for my ECU. Finding an EVO GTA full ROM has been rather difficult, so will opt for the Airtrek ROM instead.

If everything goes as planed, I may need some advice from YOU for a tune.

I have the Evo GTA ROM if you need one.

Hahaha, thanks Sub 7.

Btw me, Sub 7 & AC once of the member here are a gang to playing this ECUFlash together, and AC already installed my stock TD04 turbo kit on his Airtrek NA 4G63 single cam, he tuned the car via ecuflash as well, the result not bad, maybe he can give some advise on your 4G64, i will force him post up here!!! hahahahaha!!!!

Nice to know you bro and many thanks for your reply, keep in touch!!!!