cool- will do it when I get home from work

 

Ok Lancer with 92290014 ecu id will work with the attached definition.

I have only done what you will really need- and have not done the knock sensor maps on purpose.
If you set your ecu flash to not show invalid maps (under options) you will only see the maps which are finished.

I found an extra high octane timing/fuel map. This is used for startup and there is no need to adjust-UNLESS your modified maps are quite different. Then just copy the modified high octane maps to the extra ones.

I suggest that you guys spend a bit of time in the ecuflash forum in the evo section. You wont need to read anything to do with boost etc- but the general tuning tips are the same- except for afr.

If you are running a turbo kit with this ecu- you will have problems. The map resolutions are not very dense and will need to rescaled to higher loads (anything over 100 is in boost). If you run over the load values the car will misfire as the ecu has no reference point. That is what happened when I increased boost but had got rid of the boost cut.

The only reason why it would have worked with piggy backs is, when modifying the input signals you are changing the load that the ecu sees.

If you use these loggers you will need to change the injector size in the definition of the logger. This is too hard to explain- but evoscan will have a revision soon that allows you to change injector size.

 

Good job, monsta! I have another ROM here for Wickdaddy - could you take a look at it? Thanks!

 

Does anyone have a tiptronic gearbox in their Lancer? Do you know if you have a separate TCU? or do you know that the ECU does it? Im pretty sure that the 04+ Lancers have them combined.

The reason that I ask is my Airtrek has a tiptronic gearbox and doesnt have a separate TCU. I know for a fact that we could change how/when the gearbox changes gear and the speed of the change, but I need more Tiptronic ECUs to compare to.

Anyone who could post their Auto rom, whould be providing heaps of help.

Obviously I will post the updated definitions once I work it out

I actually was hoping that someone had already done it for the Lancers, but the majority of work been done with Ecuflash, has been done on Evos.

 

Not sure about the tiptronic or TCU stuff. As for not much done with Lancers, you are correct. This is the first thread ever started for the base Lancers and ECUFlash, so we're all pioneering here.

 

i'll check it out and see if it works tonite! thanks... (i hope that you meant for me to look at it )

 

It's not finished: that was a work-in-progress... but no-one ever got back with me to verify that the def/map would load properly anyone else's comp.

 

monsta: thank you, it looks like it works, all the values are in the right places. But what do you mean problems? is it because our ecu does not know what boost is?

I have talked to John from Jestr tuning and he said he has tuned a couple of turboed lancers with ecuflash and no problems, and will probably have him tune it on a dyno.

 

ya definitely just tried to get the thing to work and ya, like you said, it is a no-go right now... is there something that I can do to help out? what knowledge would I need to make this thing work and possibly help out others in the future

 

Load is derived from airflow, temp, throttle etc. As you are increasing airflow dramatically, the load will off the scale. Yes the load can be rescaled but the resolution is not as fine as a turboed ecu.
You should still be able to get a good tune, but if you have problems or start pushing the HP higher, you will need more resolution.
Tuners like jester know what they are doing, Im more reffering to DIYers trying to tune their aftermarket turbo kits themselves.

Any ECUs that come through will be renamed with the ECU ID number. This is so when you upload your rom-but dont have a definition, you can see your ID and load up the def for your car.

Keep them coming- Ill do the latest one tomorrow after work. If you upload one of the defs and most of the info is fine, but some are scrambled- send your rom through so I can tidy the def up. Remember to delete any definition thats the same number in your rommetadata file->misti->lancer. Also make sure that ecu flash is not on while you are changing the files.

All the maps that you dont need day to day- ill do later. I like to help anyone with Mitsis, and as your roms dont have as many things to do to get tuning straight away, it doesnt take too long.

 

Here is the link to my first rom: https://www.evolutionm.net/forums/sh...&postcount=350

and here is the "edited" one that has been posted... https://www.evolutionm.net/forums/sh...&postcount=378

let me know if you can get it working... thanks because this is what is happening: Lancer not working screen capture

 

from what i've been reading on the evo ecuflash forums, the evo and lancer ecus are practically the same, just different programming. Also the maf is the same, which means our cars can read boost, just the ecu does not know what to do past that point ( that is why the RRM turbo kit comes with a frequecy clamp for that ) so if we were to rescale the maf frequecies to read boost, and then rescale the load it would work the same as a turbo cars ecu. Anyway that is what i got from this thread. need some more reading up before i start messing with this, anyone know any other places than here and openecu forum where there might be some good info on this ecuflash?

 

Unfortunately, I deleted copies of the definition file & ROM

BUT... (and some of you guys know why I do things this way...)

Here was the last work-in-progress I had -- complete with a partially-completed definition file (98720010.xml) for you:

 

sweet just tried that and a bunch of the stuff I got readings for... don't quite know what they mean, but it is looking like it is starting to work! Let me know when you guys get the whole thing completed! Thanks so much!

 

so, now that I read some stuff from the ecu and did not change anything, my check engine light is not on anymore... does just connecting and reading from the ecu clear the codes or did the light just burn out after being on so long?