sheezy'sES

So if I pay the $25 for the evoscan download link and serial number, then I should have no problem writing my tune to my computer?? If so, I'll buy it right now. Seems like the tuner would have told me that to start with and not told me I could use that cable with EcuFlash.

03lances

iTrader: (14)

Damn that sucks but that sounds right since at the bottom of the page you linked to it clearly states cannot use with ecuflash

marcouxa1

I have the same issue with my 04 and i have the tactrix cable...i have the tephra mods definition files with the lancer big map for the 03 and it won't write..even if i load my stock rom on ecuflash and try to reflash it w/o mods it doesn't work!

ryancb

iTrader: (11)

i still bet money on drivers issue then. Id by evoscan either way though nice to see what the tuner did for your tune as you learn more about it.

RoadSpike

iTrader: (5)

Its not really a driver issue ryan its ecuflash and how its written.

Ecuflash uses a serial key embedded into the cable's chipset which it reads and validates as a cable ecuflash can use. The evoscan cable does not have a serial number which ecuflash deems as valid so it rejects the cable just that simple. The drivers are actually the same. His cable if its a tactrix cable may be an older model, tactrix switched to a longer serial key as of some ecuflash version and even I with an origional 1.3M cable needed to contact ecuflash present my reciept and get a serial key installed into my cable.

The evoscan cable is a carbon copy of the tactrix cable without the license embedded. I know older ecuflash versions would accept these cables but it will simply be easier to buy evoscan and use it as the method for flashing and reading the car.

ryancb

iTrader: (11)

But if its saying not attached it would imply its not seeing the cable. I haven't had this issue as i own both but It would seem to me since not picking up the cable at all and he hasn't confirmed all 3 drivers installed thats still likely a issue.

RoadSpike

iTrader: (5)

It would be nice if he posted the log in ecuflash when he tried to read or write a rom. It should end up in the middle of the screen like this.

marcouxa1

I have the 2.0 tactrix cable with evoscan installed and baught....i can read from ecu with ecuflash and see live data with evoscan...all i cant do is to write to my ecu with ecuflash! Although when i load my rom into ecuflash i cant see any maps but i guess that`s because i need my rom`s definition file which is a 04 AT rom?!

RoadSpike

iTrader: (5)

Yes that's probably the reason it wont flash. Download the list of definitions from senates thread.

marcouxa1

I can read my rom but i can't write to ecu...any advice?

RoadSpike

iTrader: (5)

Paste the log as i showed in my picture. Its just text copy and paste it over after you try flashing it should have the errors in the log.

marcouxa1

Yes it had a rkrv preamble 1 error i think if i remember right..

RoadSpike

iTrader: (5)

My understanding that error for the lancers implies that the kernel version its using is wrong, ie trying to load an evo 9 rom into an evo 8 or visa versa.

In the definitions for the car the flashing method is probably wrong. Your sig says 04? It should be mitsukernel with no ocp on the end. if not try it with ocp mode and see if it takes it.

marcouxa1

Do you have to change the rom info in the definition file itself for the ROM you're trying to write to or see the maps like so?:

<rom>
<romid>
<xmlid>88210000</xmlid> ---------------------(mine is 82300015)
<internalidaddress>f52</internalidaddress>
<internalidhex>88210000</internalidhex> -(mine is 82300015)
<make>Mitsubishi</make>
<market>USDM</market>
<model>Lancer</model>
<submodel>ES</submodel>--------------------(mine is a ES also)
<transmission>Auto</transmission>----------(mine is auto also)
<year>2003</year> -----------------------------(mine is a 2004)
<flashmethod>mitsukernel</flashmethod> -(mine is mitsukernel also)
<memmodel>SH7055</memmodel>-----------(mine is SH7055 also)
</romid>

<include>88200000</include>---------------------(mine is 82300015)

Any advice would be appreciated!

RoadSpike

iTrader: (5)

You'd change the xml for your romid only take the line

<flashmethod>mitsukernel</flashmethod> and change it to

<flashmethod>mitsukernelocp</flashmethod>

if it works then you have an oddity for the ecu using the newer flashing method even though its in the 04 year.