I'm thinking it probably will cap out at 20msec like the evo gta does. The solenoid in the transmission really just can't shift it any faster than that.

 

Will a ECU mapped pressure increase help with the issue that keeps the transmission from shifting while under boost at high RPM? I haven't been able to look at the tables, but this is my biggest complains with the turbo autos that I've tuned.

Also, what about a RPM based shift point map? From what I remember, I couldn't get them to rev past 6200 ... and Daniel will need a couple more hundred than that ... lol.

 

Thats going to take me awhile to decode touring.

My biggest problem is mapping the RAM variables that the ecu is using. I need logs of these variables so i can see litterally what is being used for what and get a sense of what maps do what. If I can get some logging in with a custom MUT it would help greatly.

First though I need more free time lol. I wont be able to decode anything tonight got plans. I will search out the commonly used variables this weekend and get and idea for a custom MUT to log. Personally I'd love to find transmission temp, if rpm is being used or shaft speed, and perhaps learn about the variable that seems to be throttle position in this segment of code.

 

none of us have time man. I know exactly how it is. You've done more than enough already ... take a break!

 

I'm fine really

My main problem is I don't own an automatic lancer to try loggin variables with so getting data to figureout that this ram means this doesn't exist for me. I just need a tester to do it for me and I'll slowly be able to work out the related tables from there.

 

and im that tester since clixt is leaving

 

0k.. so i need the EVO ROM to flash to my 05 AT ECU...where do i get it? so0o0o lost..

 

Ok couple things you need to know before trying this.

One since your an automatic you need to use the Evo 7 GT-A rom otherwise the transmission will be in fully clutch locked mode and stall the car.

Second you need a copy of your origional rom in case this doesn't work use the lancer read template a few pages back from here to get the full 512kb rom out of your car and save it.

Here's a link to the rom I'm using please use at your own risk this is still highly experiemental for the auto transmissions.

http://evoecu.logic.net/images/2/2e/...M-JDM_512k.hex

Below is a link to the maps I have atm they aren't probably labeled just estimates for now.

 

@link: yah i know.. 8 more hours to go lol. but imma leave like at 6pm. friday is always traffic and i dont want to be late.
im still gonna be a tester since imma bring my laptop with me.
@RS: dude if only you live close to my house, you could drive my auto with pleasure lol

 

That would be cool I do feel silly driving other peoples cars because i'm super protective of my own

I'm sure with the people on here we can have this worked out just will take time to understand all the maps needed to handle auto transmission points. I'm just hopeful some breakthrus will happen with locating the shift points via the variable maps

 

i demand more auto guys to participate. for the good of the lancer community lol

 

thanks for that. i did read and save my stock ROM http://www.box.net/shared/j1j7yzk1ch. I had flashed ROM 94170715 and it didnt work... tried flashing the original ROM to the ECU but it fails.. car wont turn over/start now.. i just flashed the 80700010 ROM also and its not working either. using 501 MAF if that makes a difference thanks for the help

error trying to flash OEM ROM back to ECU:
[17:00:38.194] Using interface OpenPort 1.3 Universal TX2BXnAx27aba5c569d2fb2b0f387f4a74218b70e2143b82
[17:01:05.825] sending init sequence 1 (0001)
[17:01:09.077] sending init sequence 1 (0003)
[17:01:10.110] got 0x05 response
[17:01:10.110] sending init sequence 2
[17:01:10.120] got 0x1B response
[17:01:10.121] sending init sequence 3
[17:01:10.497] entering bootloader
[17:01:10.514] sending kernel size (4420)
[17:01:10.525] sending kernel load address (0xFFFF7000)
[17:01:10.537] uploading kernel
[17:01:11.255] verifying kernel checksum response
[17:01:11.255] kernel valid
[17:01:11.469] kernel get version
[17:01:11.480] rkrv: preamble 1 error
[17:01:11.495] reading kernel comm buffer size
[17:01:11.707] reading kernel flash buffer size
[17:01:11.919] interface close

 

try to pull the rom from your car. see if that works.
anyhow, later guys.

 

Communications error probably the definition file stopping this.

Means that the kernel is trying to load a memorymodel which is wrong for the ecu into the car and stops. Basically its looking at a 512kb file and the rom definition states its supposed to be 256kb so it faults.

Were you able to correctly load your stock rom into ecuflash and open it for edit?

Same question with the evo 7 gta rom.

EDIT:
Oh i forgot if you loaded an evo 8 rom onto the ecu and tried to flash an evo 9 ecu it wont work. You have to flash it back with your partial 265kb file

 

Oh another thing crossed my mind.

If you didn't save a copy of your old 256kb partially download rom I may know of a way to trick the ecuflash program to upload the evo7 rom anyways