Lancer_Evo_8

iTrader: (1)

I dont know why, but i have not anymore a connetion between the Tactrix Openport 2.0 and my ECU of my EVO 8

Step by Step:

1. I connect the Tactrix and the reflash-plug to my EVO. (The Tactrix send the normal lights) --> so thats okey
2. I connect the USB of the Tactrix to my Laptop. The Laptop recognize the Taxtrix in the USB Port --> so thats also okey
3. I open the Ecuflash Software, BUT THEN I CAN NOT SELECT READ, WRITE OR MAKE E TEST WRITE. EVERYTING IS GREY.

I made a screenshot, so maybe somebody can hep me PLEASE

Raptord

iTrader: (10)

It says "no vehicle interface" in the bottom right, so something isn't right either with your cable or it's connection to your laptop

Boosted Tuning

iTrader: (12)

^ yeah, looks like you have a driver problem. When ECUflash recolonizes the cable, it will show the cable int eh lower right hand corner.

Lancer_Evo_8

iTrader: (1)

Yes but its weird. I tried with my laptop abd with my notebook. With booth i have no connections. And the tactrix send also the normal connections light. Hmmm i really dont know. 2 weeks ago it was working perfectly!

Lancer_Evo_8

iTrader: (1)

And how i can look if there is a driver problem?

Samuelwoo

iTrader: (5)

I would first uninstall and then reinstall ecuflash. Then insert the cable into another USB port other than the first usb port. I've seen bad USB ports on laptop cause very abnormal problems with USB connected device.

worksie

Did you turn your ignition on?

Lancer_Evo_8

iTrader: (1)

@ worksie

Je i tried with ACC and also with ignition on.

Lancer_Evo_8

iTrader: (1)

Now i re-installed the EcuFlash from the Tactrix Homepage. Then it downloaded automaticly 3 driver. Then i tried to connect with the car (ignition on). And it doesnt work

PS: Batterie Voltage when i put the Ignition on is around 12.3V-12.8V

I really dont know what to do.

Lancer_Evo_8

iTrader: (1)

So, ECUFlash work again. I delete just the driver from my Laptop, and installed the driver new. Restart the laptop and it works again......

But thanks for helping me

Abacus

iTrader: (9)

To the OP, glad you were able to get it working.
I had a few problems and will share my story. My car would not flash or read but I could scan the car thru evoscan. It turned out I needed to have my car on the charger in order to flash it. The car cranks fine but the voltage may have been to low for ecuflash.

Lancer_Evo_8

iTrader: (1)

I have the problem that i can not write my new map file to the car. I made now a printscreen. Maybe somebody can help me

Biggy VIII

reinstall openport driver manually from ecuflash/driver folder, with cable connected. than run ecuflash.

mines5

I am having problem reading and writing with ECU flash 1.44.3719, i have a 1.3u cable.

The read option appears some times and the ECU reads the image and prompts to turn the ignition off. The map shows but when i turn the ignition on [ not crank ] and load the map in ECU flash to write. There is no WRITE option on the main window and ECU option is blank.

I re-opened the ECU flash and tried to read it gave some an error

[15:33:09.965] kernel read area: addr: 0001E600 len: 0200
[15:33:10.058] kernel read area: addr: 0001E800 len: 0200
[15:33:10.152] kernel read area: addr: 0001EA00 len: 0200
[15:33:10.230] kernel read area: addr: 0001EC00 len: 0200
[15:33:10.323] kernel read area: addr: 0001EE00 len: 0200
[15:33:10.433] kernel read area: addr: 0001F000 len: 0200
[15:33:10.526] kernel read area: addr: 0001F200 len: 0200
[15:33:10.620] kernel read area: addr: 0001F400 len: 0200
[15:33:10.713] kernel read area: addr: 0001F600 len: 0200
[15:33:10.807] kernel read area: addr: 0001F800 len: 0200
[15:33:10.901] kernel read area: addr: 0001FA00 len: 0200
[15:33:10.994] kernel read area: addr: 0001FC00 len: 0200
[15:33:11.072] kernel read area: addr: 0001FE00 len: 0200
[15:33:11.197] kernel read area: addr: 00020000 len: 0200
[15:33:11.291] kernel read area: addr: 00020200 len: 0200
[15:33:11.384] kernel read area: addr: 00020400 len: 0200
[15:33:11.462] kernel read area: addr: 00020600 len: 0200
[15:33:11.556] kernel read area: addr: 00020800 len: 0200
[15:33:11.649] kernel read area: addr: 00020A00 len: 0200
[15:33:11.743] rkrv: bad checksum
[15:33:11.743] invalid / no kernel response to read
[15:33:11.743] kernel read area: addr: 00020A00 len: 0200
[15:33:11.759] readback mismatch
[15:33:11.759] rkrv: preamble 1 error
[15:33:11.759] invalid / no kernel response to read
[15:33:11.759] kernel read area: addr: 00020A00 len: 0200
[15:33:11.759] readback mismatch
[15:33:11.759] rkrv: preamble 1 error
[15:33:11.759] invalid / no kernel response to read
[15:33:11.759] ECU memory read failure.
[15:33:11.759] can't read image.
[15:33:11.759] interface close


WHAT IS CAUSING all this ? OR AM I MISSING SOME MAJOR POINTS on how to write thru ECU FLASH ?

Can any one write step by step how you write your new map on to the ROM using ECU flash ?

PLEASE HELP !

mines5

OK , now i see all the read , test write , write and compare options but when i try to test write i get the following error.


93660005 (71 tables) inheriting evo7base (176 tables)

[18:02:06.033] using metadata XML ID 93660005 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/93660005 2004 JDM Lancer Evo 8 FQ300 MT.xml

which inherits XML ID evo7base from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/evo7base.xml

[18:02:06.033] ---notes---

2012/11/16 [Tactrix] updating to standard file naming.

2012/11/21 [Tactrix] correcting naming for Boost Desired Engine Load 2. Removed - from "Idle Stepper Look-up".

2012/11/19 [Tactrix] Visually examined tables for obvious errors, but no in-car verification has been done.

[18:02:06.064] using metadata XML ID 93660005 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/93660005 2004 JDM Lancer Evo 8 FQ300 MT.xml

which inherits XML ID evo7base from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/evo7base.xml

[18:02:06.064] ---notes---

2012/11/16 [Tactrix] updating to standard file naming.

2012/11/21 [Tactrix] correcting naming for Boost Desired Engine Load 2. Removed - from "Idle Stepper Look-up".

2012/11/19 [Tactrix] Visually examined tables for obvious errors, but no in-car verification has been done.

[18:04:47.915] Flashing tools do not recognize flash method 'evo'