Yes you need the flash connector from the OP2 to the flash plug on an IX.
If you did not get it with your OP2 you can order one on the Tactrix website.

Yep I connector works and I successfully read the ROM. However I cannot save the ROM file as bin or hex form. Only in srf format. Why is that? Thx a lot~{thumbup}

okay, so i have an openport 2.0 cable (with a rigged up jumper), ecuflash 1.42, evo 9, full 12 volts on the battery. running windows 7 on a toshiba laptop. i get the:
"[23:20:26.521] no response to any known code
[23:20:26.521] interface close"
i tried running the ecu unlocker program. not sure it's working since it's just a small window that opens... i've tried everything i can think of... what else is there?

Question, Understand that placing the right definitions in the right folder would unlock many of the flash/cal features, but is there ONE definition that would uncover all of the features, or do we have place them all? I am having a tough time understanding the mechanics of the process more than the calibrations.
Thanks in advance!

nevermind, problem was with my cable.

I am wondering if a 1.3M cable works with the newest evoscan? It's a cable Ive had for a long time, and was out of tuning my car for a long time, and my computer says it is not connecting. Do I need a 1.3u or 2.0 cable to even datalog with the new evoscan?

Hello, everybody!I have a EVO9.I read the ROM failure.ECUFLASH prompt error, and view the LOG.I used openprot2.0 ask you this question how to solve? ?

[22:03:05.421] EcuFlash Version 1.44.3721
[22:03:05.421] OS Version Windows XP
[22:03:05.421] Qt Version 4.8.0
[22:03:05.437] 63 memory models read.
[22:03:05.437] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[22:03:05.875] Error parsing xml of file C:/Program Files/OpenECU/EcuFlash/rommetadata/12345.xml:

Parse error at line 1, column 1:
error occurred while parsing element
[22:03:05.875] ROM metadata models 12345.xml is invalid.
[22:03:05.875] 646 ROM metadata models scanned.
[22:03:05.875] checksum module "subarudbw" loaded.
[22:03:05.875] checksum module "mitsucan" loaded.
[22:03:05.875] checksum module "mitsuh8" loaded.
[22:03:05.875] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[22:03:05.875] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[22:03:05.890] flashing tool "wrx02" loaded.
[22:03:05.890] flashing tool "wrx04" loaded.
[22:03:05.890] flashing tool "sti04" loaded.
[22:03:05.890] flashing tool "sti05" loaded.
[22:03:05.890] flashing tool "mitsukernel" loaded.
[22:03:05.890] flashing tool "mitsukernelocp" loaded.
[22:03:05.890] flashing tool "mitsubootloader" loaded.
[22:03:05.890] flashing tool "shbootmode" loaded.
[22:03:05.890] flashing tool "shaudmode" loaded.
[22:03:05.890] flashing tool "subarucan" loaded.
[22:03:05.906] flashing tool "subarucand" loaded.
[22:03:05.906] flashing tool "mitsucan" loaded.
[22:03:05.906] error loading FTD2XX.DLL
[22:07:47.828] using metadata XML ID read_mitsum32186f8can from file C:/Program

Files/OpenECU/EcuFlash/rommetadata/read templates/read_mitsum32186f8can.xml
[22:07:47.859] J2534 API Version: 04.04
[22:07:47.859] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59
[22:07:47.859] Device Firmware Version: 1.12.3688
[22:07:47.859] Device Serial Number: TApFbnC$
[22:07:49.750] -- loading kernel --
[22:07:49.750] -- connecting to kernel --
[22:07:49.750] kernel get version
[22:07:49.796] J2534 error [ERR_TIMEOUT].
[22:07:49.859] J2534 error [ERR_TIMEOUT].
[22:07:50.015] J2534 error [ERR_TIMEOUT].
[22:07:50.062] J2534 error [ERR_TIMEOUT].
[22:07:50.062] interface close
[22:07:50.093] interface close
[22:08:11.718] using metadata XML ID read_evo9 from file C:/Program

Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml
[22:08:11.750] J2534 API Version: 04.04
[22:08:11.750] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59
[22:08:11.750] Device Firmware Version: 1.12.3688
[22:08:11.750] Device Serial Number: TApFbnC$
[22:08:13.687] sending init sequence 1 (0001)
[22:08:16.890] sending init sequence 1 (0003)
[22:08:20.093] sending init sequence 1 (FFFF)
[22:08:22.796] no response to any known code
[22:08:22.796] interface close
[22:08:33.781] using metadata XML ID read_mitsum32186f8can from file C:/Program

Files/OpenECU/EcuFlash/rommetadata/read templates/read_mitsum32186f8can.xml
[22:08:33.812] J2534 API Version: 04.04
[22:08:33.812] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59
[22:08:33.812] Device Firmware Version: 1.12.3688
[22:08:33.812] Device Serial Number: TApFbnC$
[22:08:35.218] -- loading kernel --
[22:08:35.218] -- connecting to kernel --
[22:08:35.218] kernel get version
[22:08:35.281] J2534 error [ERR_TIMEOUT].
[22:08:35.328] J2534 error [ERR_TIMEOUT].
[22:08:35.484] J2534 error [ERR_TIMEOUT].
[22:08:35.531] J2534 error [ERR_TIMEOUT].
[22:08:35.531] interface close
[22:08:35.562] interface close
[22:10:08.921] using metadata XML ID read_mitsum32186f8can from file C:/Program

Files/OpenECU/EcuFlash/rommetadata/read templates/read_mitsum32186f8can.xml
[22:10:08.953] J2534 API Version: 04.04
[22:10:08.953] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59
[22:10:08.953] Device Firmware Version: 1.12.3688
[22:10:08.953] Device Serial Number: TApFbnC$
[22:10:10.437] -- loading kernel --
[22:10:10.437] -- connecting to kernel --
[22:10:10.437] kernel get version
[22:10:10.515] J2534 error [ERR_TIMEOUT].
[22:10:10.562] J2534 error [ERR_TIMEOUT].
[22:10:10.734] J2534 error [ERR_TIMEOUT].
[22:10:10.796] J2534 error [ERR_TIMEOUT].
[22:10:10.796] interface close
[22:10:10.843] interface close

HI,

I change recently my computer and try to connect to my EVO IX but It doesn't recognize the vehicule interface. I try to install the driver that come with ecuFlash (latest version) and I found my problem, It says that the language of the system of the DPInst.exe is not recognize by the ''driver installer'' (translate from french) and contact your administrator...

The computer his on Window 8. it should work on that?

How do I resolve that?
Thanks in advance!

I try to reinstall the DPInst on the old computer for the driver and I have the same error message... Than I connect the old PC in my EVO and it read the ecu like suppose too, soo this is not the problem. I went to see and the program of the new PC in I can see all the tactrix driver package, they seem to be there and ok.

I try to uninstall ecuflash and driver and reinstall it but still didn't work...

Here's what EcuFlash say:
[14:02:58.032] EcuFlash Version 1.44.3721
[14:02:58.032] OS Version Windows 7
[14:02:58.032] Qt Version 4.8.0
[14:02:58.048] 63 memory models read.
[14:02:58.048] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[14:02:58.235] 612 ROM metadata models scanned.
[14:02:58.235] checksum module "subarudbw" loaded.
[14:02:58.235] checksum module "mitsucan" loaded.
[14:02:58.235] checksum module "mitsuh8" loaded.
[14:02:58.235] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[14:02:58.235] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[14:02:58.235] flashing tool "wrx02" loaded.
[14:02:58.235] flashing tool "wrx04" loaded.
[14:02:58.235] flashing tool "sti04" loaded.
[14:02:58.235] flashing tool "sti05" loaded.
[14:02:58.235] flashing tool "mitsukernel" loaded.
[14:02:58.235] flashing tool "mitsukernelocp" loaded.
[14:02:58.235] flashing tool "mitsubootloader" loaded.
[14:02:58.235] flashing tool "shbootmode" loaded.
[14:02:58.235] flashing tool "shaudmode" loaded.
[14:02:58.235] flashing tool "subarucan" loaded.
[14:02:58.235] flashing tool "subarucand" loaded.
[14:02:58.251] flashing tool "mitsucan" loaded.
[14:02:58.251] J2534 error [unable to open device].
[14:02:58.251] J2534 error [unable to open device].
[14:02:58.251] J2534 error [unable to open device].
[14:03:11.433] using metadata XML ID read_evo9 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml
[14:03:11.448] J2534 error [unable to open device].
[14:03:11.448] unable to connect to vehicle interface.
[14:03:32.789] using metadata XML ID read_evo9 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml
[14:03:32.805] J2534 error [unable to open device].
[14:03:32.805] unable to connect to vehicle interface.

I have seen a remark on the site of tactrix talking about new driver for the last version of ecuflash, does I have the older one and my car and I can't read it with the new ecuflash?

Any idea why unable to open device with this new computer???

The only difference I see is that the old PC is using a 1.42 version of Ecuflash and the new one is using a 1.44 version. Should I try to install an older version?

help! does anyone knows the code for ralliart ecu? this ecu has been installed by previous owner

my stops at 40% and the log says

An error occurred while reflashing. See the log for details.

You were in the process of reflashing your ECU and
some memory areas have already been erased / written -
Start the reflashing process again, and the software
should be able to resume where it left off. If you are
still having trouble, save the log file, and send it to
http://openecu.org or support@tactrix.com and see if
someone can help you.



[17:07:21.817] J2534 API Version: 04.04
[17:07:21.817] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59
[17:07:21.817] Device Firmware Version: 1.12.3688
[17:07:21.817] Device Serial Number: TAer8isj
[17:07:24.169] sending init sequence 2
[17:07:24.169] got 0x11 response
[17:07:24.169] sending init sequence 3
[17:07:24.543] entering bootloader
[17:07:24.543] sending kernel size (2029)
[17:07:24.543] sending kernel load address (0x0000F000)
[17:07:24.559] uploading kernel
[17:07:24.886] verifying kernel checksum response
[17:07:24.886] kernel valid
[17:07:25.089] kernel get version
[17:07:25.089] kernel version is : OpenEcu Mitsubishi H8/539F Kernel V1.07
[17:07:25.089] reading kernel comm buffer size
[17:07:25.105] comm buffer size set to 256
[17:07:25.105] reading kernel flash buffer size
[17:07:25.105] flash buffer size set to 1024
[17:07:25.136] -- flashing image to ECU memory --
[17:07:25.541] -- comparing ECU flash memory pages to image file --
[17:07:25.541] seg start len ecu CRC32 img CRC32 same?
[17:07:25.682] LB7 00010000 00003000 7FDB4B60 DF1A34C8 NO
[17:07:25.697] SB0 00013000 00000200 A6BFEA7C D90A49D9 NO
[17:07:25.713] SB1 00013200 00000200 614E4403 614E4403 YES
[17:07:25.729] SB2 00013400 00000200 9C5C2520 9C5C2520 YES
[17:07:25.744] SB3 00013600 00000200 9D0A5827 9D0A5827 YES
[17:07:25.760] SB4 00013800 00000200 529496AA 529496AA YES
[17:07:25.775] SB5 00013A00 00000200 5541435B AB1E2EDA NO
[17:07:25.791] SB6 00013C00 00000200 BD7BC39F 01D43F34 NO
[17:07:25.807] SB7 00013E00 00000200 BD7BC39F BD7BC39F YES
[17:07:25.994] LB6 00014000 00004000 B733E61C 570329C0 NO
[17:07:26.197] LB5 00018000 00004000 68AF0E25 5363B41F NO
[17:07:26.399] LB4 0001C000 00004000 370EBAAD D4CD69CA NO
[17:07:26.587] LB3 00020000 00004000 5E12815E 5E12815E YES
[17:07:26.789] LB2 00024000 00004000 968D0FC7 968D0FC7 YES
[17:07:26.992] LB1 00028000 00004000 BFC27FD9 BFC27FD9 YES
[17:07:27.179] LB0 0002C000 00004000 03FA6008 0D8DC0EE NO
[17:07:27.179] kernel flash enable
[17:07:27.211] kernel blank flash page: addr: 0002C000
[17:07:42.234] WARNING: failed to erase page at 0002C000!
[17:07:42.234] kernel flash disable
[17:07:44.247] interface close

I am wondering if a 1.3M cable works with the newest evoscan? It's a cable Ive had for a long time, and was out of tuning my car for a long time, and my computer says it is not connecting. Do I need a 1.3u or 2.0 cable to even datalog with the new evoscan?


i posted q months ago and was wondering if anyone has insight about it? I never could get ahold of evoscan for a reply. I'd love to start playing with somethings on my evo again, now that good weather is here. anybody know?!?

My problem is it says won't respond to any known code, but it connect yesterday to mine and 2 others, now that I'm trying to flash the new maps it won't write or read, nothing has changed, same version, batters are charged even warmed them up, makes no sense.

i just got mine to work, i use evoscan to read and flash, then open and edit with ecuflash, but what worked for me was making sure the it plugged in good, let the car run for a bit and then pull the key out, hit the read button its say the "make sure the key is in the on position, then put the key in and put it in the on position and quickly hit the ok button. sounds crazy but it worked for me lol