colby

iTrader: (3)

EcuFlash 1.28 is out and supports reflashing the Evo 9 as well as ~03 Lancer Automatics (maybe some other years - not sure which). Jason has updated the Evo 9 maps definitions a bit too. I don't have any maps for the Lancers that are supported yet. If you have made up any new XML files yourself, you will need to change the <flashmethod> parameter in them. Any flashmethods that used to be "evo" should now be "mitsukernel"... If you have your rommetadata somewhere other than the install directory, you will need to update all of your files (or just use the new ones) or you won't be able to flash. Sorry for the inconvenience!

EcuFlash 1.28

EvoRicer

iTrader: (7)

NICE! Thanks Colby and Jason for all your hard work...now I just gotta wait ill I get off work at Midnight...damn...

Noogles

iTrader: (-1)

Damn,

I'm still working on the users guide for version 1.27

gsrboi80

iTrader: (38)

DL'ed thanks gentlemen

jasonc32amg

iTrader: (2)

sweet, time to order a cable

colby

iTrader: (3)

not much has changed that would require updating a manual... yet.

AlwaysinBoost

iTrader: (17)

noticed the first problem... you can't compare values from different maps at the same time. With the previous version you could open up two maps and have say the High Octain timing map opened up on both. Now when you click anywhere except for on the map, whatever your looking at gets sent to the background. know what I mean?

andenbre

iTrader: (4)

efn awsome

gsrboi80

iTrader: (38)

Oh that sucks I liked thats. Its how I looked at me and my girls roms side by side

AlwaysinBoost

iTrader: (17)

getting the following error message when I try to reflash my ECU:
[04:04:34.187] Version 1.28.716
[04:04:34.203] 8 memory models read.
[04:04:34.671] 72 ROM metadata models read.
[04:04:34.671] checksum module "subarudbw" loaded.
[04:04:34.671] flashing tool "wrx02" loaded.
[04:04:34.671] flashing tool "wrx04" loaded.
[04:04:34.671] flashing tool "sti04" loaded.
[04:04:34.671] flashing tool "sti05" loaded.
[04:04:34.671] flashing tool "mitsukernel" loaded.
[04:04:34.671] flashing tool "mitsukernelocp" loaded.
[04:04:34.671] flashing tool "mitsubootloader" loaded.
[04:04:43.343] 262144 byte image read.
[04:04:44.515] Flashing tools do not recognize flash method 'evo'
[04:04:49.625] Flashing tools do not recognize flash method 'evo'
[04:04:56.062] Flashing tools do not recognize flash method 'evo'
[04:05:02.812] Flashing tools do not recognize flash method 'evo'
[04:05:03.734] Flashing tools do not recognize flash method 'evo'
[04:05:07.468] Flashing tools do not recognize flash method 'evo'
[04:05:11.968] Flashing tools do not recognize flash method 'evo'
[04:05:49.359] Flashing tools do not recognize flash method 'evo'
[04:05:55.328] Flashing tools do not recognize flash method 'evo'
[04:06:02.984] Flashing tools do not recognize flash method 'evo'

andenbre

iTrader: (4)

it works for me you just have to minimize ecu flash and all the maps will be on the desktop

AlwaysinBoost

iTrader: (17)

I just reinstalled ver 1.27 due to the fact I can't reflash my ECU, so I'm good for a little bit until those bugs get worked out. It may actually be a problem on my end... I dunno.

Warrtalon

iTrader: (6)

AlwaysinBoost, it looks like that error would be related to what Colby said above about changing <flashmethod> from "evo" to "mitsukernel."

So, we can now flash IXs? Uber.

andenbre

iTrader: (4)

Colby, If I remember correctly you were planning on integrating datalogging into ecuflash, Is this being considered? I know evo4mad is on the verge of releasing data logging software and I was wondering if this is going to effect those plans.

gsrboi80

iTrader: (38)

Havent tried flashing to it still waiting on my map "AL" . But I DL'ed the 1.28. So how do I go about changing <flashmethod>?