Problem with ecuflash openport2

[Diego 10]

Hi I'm a new member of this forum my name is Diego and I'm an italian boy my car is an mitsubishi lancer evo IX with 30k km!!!!
The problem with my car is this...I can't read ecu...this is the log file
[18:59:36.281] EcuFlash Version 1.42.2595
[18:59:36.281] OS Version Windows XP
[18:59:36.281] Qt Version 4.5.0
[18:59:36.296] 56 memory models read.
[18:59:36.296] scanning for metadata models in C:/Programmi/OpenECU/EcuFlash/rommetadata
[18:59:36.515] 343 ROM metadata models scanned.
[18:59:36.515] checksum module "subarudbw" loaded.
[18:59:36.515] checksum module "mitsucan" loaded.
[18:59:36.515] flashing tool "wrx02" loaded.
[18:59:36.515] flashing tool "wrx04" loaded.
[18:59:36.515] flashing tool "sti04" loaded.
[18:59:36.515] flashing tool "sti05" loaded.
[18:59:36.515] flashing tool "mitsukernel" loaded.
[18:59:36.515] flashing tool "mitsukernelocp" loaded.
[18:59:36.515] flashing tool "mitsubootloader" loaded.
[18:59:36.515] flashing tool "shbootmode" loaded.
[18:59:36.531] flashing tool "shaudmode" loaded.
[18:59:36.531] flashing tool "subarucan" loaded.
[18:59:36.531] flashing tool "mitsucan" loaded.
[18:59:43.984] J2534 API Version: 04.04
[18:59:43.984] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[18:59:43.984] Device Firmware Version: 1.10.2658
[18:59:45.984] sending init sequence 1 (0001)
[18:59:49.234] sending init sequence 1 (0003)
[18:59:52.484] sending init sequence 1 (FFFF)
[18:59:55.187] no response to any known code
[18:59:55.187] interface close
[19:00:06.453] J2534 API Version: 04.04
[19:00:06.453] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:00:06.453] Device Firmware Version: 1.10.2658
[19:00:08.140] sending init sequence 1 (0001)
[19:00:11.390] sending init sequence 1 (0003)
[19:00:14.640] sending init sequence 1 (FFFF)
[19:00:17.343] no response to any known code
[19:00:17.343] interface close
[19:00:42.468] J2534 API Version: 04.04
[19:00:42.468] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:00:42.468] Device Firmware Version: 1.10.2658
[19:00:44.171] sending init sequence 1 (0001)
[19:00:47.421] sending init sequence 1 (0003)
[19:00:50.671] sending init sequence 1 (FFFF)
[19:00:53.375] no response to any known code
[19:00:53.375] interface close
[19:01:13.046] J2534 API Version: 04.04
[19:01:13.046] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:01:13.046] Device Firmware Version: 1.10.2658
[19:01:19.578] sending init sequence 1 (0001)
[19:01:22.828] sending init sequence 1 (0003)
[19:01:26.078] sending init sequence 1 (FFFF)
[19:01:28.781] no response to any known code
[19:01:28.781] interface close
[19:02:02.125] J2534 API Version: 04.04
[19:02:02.125] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:02:02.125] Device Firmware Version: 1.10.2658
[19:02:04.281] sending init sequence 1 (0001)
[19:02:07.531] sending init sequence 1 (0003)
[19:02:10.781] sending init sequence 1 (FFFF)
[19:02:13.484] no response to any known code
[19:02:13.484] interface close
[19:02:22.234] J2534 API Version: 04.04
[19:02:22.234] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:02:22.234] Device Firmware Version: 1.10.2658
[19:02:24.015] sending init sequence 1 (0001)
[19:02:27.265] sending init sequence 1 (0003)
[19:02:30.515] sending init sequence 1 (FFFF)
[19:02:33.218] no response to any known code
[19:02:33.218] interface close
[19:02:47.125] J2534 API Version: 04.04
[19:02:47.125] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:02:47.125] Device Firmware Version: 1.10.2658
[19:02:48.859] sending init sequence 1 (0001)
[19:02:52.109] sending init sequence 1 (0003)
[19:02:55.359] sending init sequence 1 (FFFF)
[19:02:58.062] no response to any known code
[19:02:58.062] interface close
[19:03:29.734] J2534 API Version: 04.04
[19:03:29.734] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:03:29.734] Device Firmware Version: 1.10.2658
[19:03:33.609] sending init sequence 1 (0001)
[19:03:36.859] sending init sequence 1 (0003)
[19:03:40.109] sending init sequence 1 (FFFF)
[19:03:42.812] no response to any known code
[19:03:42.812] interface close
[19:04:00.328] J2534 API Version: 04.04
[19:04:00.328] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:04:00.328] Device Firmware Version: 1.10.2658
[19:04:02.062] sending init sequence 1 (0001)
[19:04:05.312] sending init sequence 1 (0003)
[19:04:08.562] sending init sequence 1 (FFFF)
[19:04:11.265] no response to any known code
[19:04:11.265] interface close
[19:04:28.921] J2534 API Version: 04.04
[19:04:28.921] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:04:28.921] Device Firmware Version: 1.10.2658
[19:04:30.656] sending init sequence 1 (0001)
[19:04:33.906] sending init sequence 1 (0003)
[19:04:37.156] sending init sequence 1 (FFFF)
[19:04:39.859] no response to any known code
[19:04:39.859] interface close


I tried to connect with evo9/eclipse protocol and also whit CAN vehicles protocol but nothing to do, if anyone has had this problem and can help me, I would be very grateful
Diego

[radsdau]

Check the init connector is in properly. If that doesn' work, try ECU unlocker.

[Diego 10]

Thanks, I have ECUFlash ECU Unlocker_v1.1(is the latest release?) is better use ecuflash 1.28 or it still works with ultimate release?
Many thanks
Diego

[radsdau]

I think it still works with the current release, otherwise just use an earlier one for the read.

[Diego 10]

Thank so much I'm waiting for the week-end to try
Diego

[Diego 10]

Many thanks to radsdau!!!!Unlockers works great!!!I try with ecuflash 1.3 the cable is an Open port 1.3 now i can read/write ecu!!!
Diego

[radsdau]

Many thanks to radsdau!!!!Unlockers works great!!!I try with ecuflash 1.3 the cable is an Open port 1.3 now i can read/write ecu!!!
Diego

You're welcome; glad to help.