Burnhad91

So I'm brand new to this software and tried installing evoscan and ecuflash today. The programs seemed to load fine. I then proceeded to hook the cable up to my evoX and read ecu.

At this point I saw some failures come up and it said something about a memory dump which did not sound good to me.

I restarted the program and tried to read again. It had a slightly different failure text from the first time and now my car won't start.

I have done some searching on the forums and find most people saying the ecu is bricked but I am unsure how this happened. Was it my fault? Software malfunction? It kind of makes me weary to try and use the software again if I get it back to normal.

Here is the second failure(First one I didn't capture...) PLEASE HELP!

[21:50:18.483] EcuFlash Version 1.44.4347
[21:50:18.483] OS Version Windows 7
[21:50:18.483] Qt Version 5.2.0
[21:50:18.495] 67 memory models read.
[21:50:18.496] scanning for metadata models in C:/Users/DJ/Desktop
[21:50:18.737] 747 ROM metadata models scanned.
[21:50:18.738] checksum module "subarudbw" loaded.
[21:50:18.738] checksum module "subarudiesel" loaded.
[21:50:18.738] checksum module "mitsucan" loaded.
[21:50:18.738] checksum module "mitsuh8" loaded.
[21:50:18.738] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[21:50:18.738] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[21:50:18.747] using metadata XML ID read_mitsum32186f8can from file C:/Users/DJ/Desktop/Ecuflash v1.44/EcuFlash/rommetadata/read templates/read_mitsum32186f8can.xml
[21:50:18.756] flashing tool "wrx02" loaded.
[21:50:18.767] flashing tool "wrx04" loaded.
[21:50:18.773] flashing tool "sti04" loaded.
[21:50:18.778] flashing tool "sti05" loaded.
[21:50:18.778] flashing tool "mitsukernel" loaded.
[21:50:18.778] flashing tool "mitsukernelocp" loaded.
[21:50:18.778] flashing tool "mitsubootloader" loaded.
[21:50:18.778] flashing tool "shbootmode" loaded.
[21:50:18.778] flashing tool "shaudmode" loaded.
[21:50:18.784] flashing tool "subarucan" loaded.
[21:50:18.789] flashing tool "subarucand" loaded.
[21:50:18.794] flashing tool "subarubrz" loaded.
[21:50:18.800] flashing tool "subaruhitachi" loaded.
[21:50:18.805] flashing tool "mitsucan" loaded.
[21:50:18.813] J2534 error [unable to open device].
[21:50:18.814] J2534 error [unable to open device].
[21:50:18.816] J2534 error [unable to open device].
[21:50:18.817] J2534 error [unable to open device].
[21:50:18.819] J2534 error [unable to open device].
[21:50:18.820] J2534 error [unable to open device].
[21:51:08.406] using metadata XML ID read_mitsum32186f8can from file C:/Users/DJ/Desktop/Ecuflash v1.44/EcuFlash/rommetadata/read templates/read_mitsum32186f8can.xml
[21:51:08.408] J2534 error [unable to open device].
[21:51:08.408] unable to connect to vehicle interface.
[21:51:08.408] interface close

Burnhad91

So I'm wondering if uninstalling the drivers for the tactrix cable or the ecuflash software and reinstalling might help?
The reason I haven't tried this already is because I wasn't sure if there was a way to recover my original rom and didn't want to risk losing it if there was. But if it's gone for good then I will try anything. Any input appreciated!

MikeyPSF

If you're ever having a serious problem, in addition to checking here, also send us an email at support at tactrix dot com. I sometimes check that support queue on the weekends, but for sure I would have gotten back to you early this morning.

If you encountered an error during the read process and you then cycled the key, then you're most likely stuck in programming mode. These vehicles entering programming mode for a read or write and only exit that mode upon the successful completion of that operation. If the process was interrupted, then it was left in that state.

Connect your Openport and EcuFlash, select Mitsubishi CAN as the vehicle type, and then under the ECU menu, select the 'exit programming state' option.

-Mike
Tactrix

Burnhad91

You're awesome man! That was exactly the problem ahhhh I'm so happy!!

Thanks a million Mike!

MikeyPSF

Glad to hear the problem is solved! By the way, I noticed you're using an older version of our software. The version on our site was updated just a couple weeks ago. I'd recommend updating to that version.

-Mike
Tactrix

Burnhad91

Alright

Dumb question but do I have to uninstall my current version and then install the new one?
Or can I just install the new version and everything will transfer?

MikeyPSF

No need to uninstall the old version. The new installer will update everything as needed. EcuFlash will also backup your old definition files so that if you happen to have custom definitions in there, those won't be lost.

-Mike
Tactrix

Burnhad91

Fantastic thanks again!

Shinzon

iTrader: (4)

i am have similar issues. I have 2015 USDM MR. i was able to flash it before. all of a sudden i cant read or write anymore. it leaves me with a dtc that ecufash cant clear. using golden evo's definitions. using rom 5959006. i am able to drive and start just fine. please help


[20:05:58.351] EcuFlash Version 1.44.4503 [20:05:58.351] OS Version Windows 7
[20:05:58.351] Kernel Type winnt
[20:05:58.351] Kernel Version 6.1.7601
[20:05:58.351] CPU x86_64
[20:05:58.351] Product Name Windows 7
[20:05:58.351] Product Type windows
[20:05:58.351] Product Version 7
[20:05:58.351] Qt Version 5.4.0
[20:05:58.362] 67 memory models read.
[20:05:58.362] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[20:05:58.518] 751 ROM metadata models scanned.
[20:05:58.518] checksum module "subarudbw" loaded.
[20:05:58.518] checksum module "subarudiesel" loaded.
[20:05:58.518] checksum module "mitsucan" loaded.
[20:05:58.518] checksum module "mitsuh8" loaded.
[20:05:58.518] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[20:05:58.518] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[20:05:58.526] using metadata XML ID read_mitsum32186f8can from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_mitsum32186f8can.xml
[20:05:58.531] flashing tool "wrx02" loaded.
[20:05:58.534] flashing tool "wrx04" loaded.
[20:05:58.536] flashing tool "sti04" loaded.
[20:05:58.538] flashing tool "sti05" loaded.
[20:05:58.541] flashing tool "mitsucan" loaded.
[20:05:58.541] flashing tool "mitsukernel" loaded.
[20:05:58.541] flashing tool "mitsukernelocp" loaded.
[20:05:58.541] flashing tool "mitsubootloader" loaded.
[20:05:58.541] flashing tool "shbootmode" loaded.
[20:05:58.541] flashing tool "shaudmode" loaded.
[20:05:58.543] flashing tool "subarucan" loaded.
[20:05:58.546] flashing tool "subarucand" loaded.
[20:05:58.548] flashing tool "subarubrz" loaded.
[20:05:58.550] flashing tool "subaruhitachi" loaded.
[20:05:58.556] interface open
[20:05:58.568] J2534 API Version: 04.04
[20:05:58.568] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[20:05:58.568] Device Firmware Version: 1.15.4474
[20:05:58.568] Device Serial Number: TAcTvY0Y
[20:05:58.569] interface close
[20:05:58.570] interface open
[20:05:58.582] J2534 API Version: 04.04
[20:05:58.582] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[20:05:58.582] Device Firmware Version: 1.15.4474
[20:05:58.582] Device Serial Number: TAcTvY0Y
[20:05:58.583] interface close
[20:05:58.584] interface open
[20:05:58.596] J2534 API Version: 04.04
[20:05:58.596] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[20:05:58.596] Device Firmware Version: 1.15.4474
[20:05:58.596] Device Serial Number: TAcTvY0Y
[20:05:58.597] interface close
[20:05:58.598] interface open
[20:05:58.609] J2534 API Version: 04.04
[20:05:58.610] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[20:05:58.610] Device Firmware Version: 1.15.4474
[20:05:58.610] Device Serial Number: TAcTvY0Y
[20:05:58.610] interface close
[20:05:58.611] interface open
[20:05:58.623] J2534 API Version: 04.04
[20:05:58.623] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[20:05:58.623] Device Firmware Version: 1.15.4474
[20:05:58.623] Device Serial Number: TAcTvY0Y
[20:05:58.624] interface close
[20:05:58.624] interface open
[20:05:58.636] J2534 API Version: 04.04
[20:05:58.636] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[20:05:58.636] Device Firmware Version: 1.15.4474
[20:05:58.636] Device Serial Number: TAcTvY0Y
[20:05:58.637] interface close
[20:06:02.738] opening rom file C:/Users/Admin/Desktop/evo tuning/myevo/2015/my2015_mivec_sst rax.srf
[20:06:02.769] 59590004 (219 tables) inheriting RAX59590004 (12 tables)
[20:06:02.770] 59590006 (0 tables) inheriting 59590004 (231 tables)
[20:06:02.778] mitsucan checksum module determined checksum area to be {{0x00000000-0x000fffff}}
[20:06:02.793] using metadata XML ID 59590006 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/59590006.xml
which inherits XML ID 59590004 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/59590004.xml
which inherits XML ID RAX59590004 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/59590004 RAX2 Patch.xml
[20:06:02.841] mitsucan checksum module determined checksum area to be {{0x00000000-0x000fffff}}
[20:06:02.857] using metadata XML ID 59590006 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/59590006.xml
which inherits XML ID 59590004 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/59590004.xml
which inherits XML ID RAX59590004 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/59590004 RAX2 Patch.xml
[20:06:07.888] baud set to 500000
[20:06:07.888] interface open
[20:06:07.900] J2534 API Version: 04.04
[20:06:07.900] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[20:06:07.900] Device Firmware Version: 1.15.4474
[20:06:07.900] Device Serial Number: TAcTvY0Y
[20:06:07.901] characteristics set to 0,8,1
[20:06:07.902] flush
[20:06:09.913] -- loading kernel --
[20:06:09.913] -- connecting to kernel --
[20:06:09.913] kernel get version
[20:06:09.913] [W](5) 00 00 07 e0 01
[20:06:10.114] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:10.114] [10] 92
[20:06:10.114] [W](6) 00 00 07 df 10 92
[20:06:10.215] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:10.215] [10] 92
[20:06:10.215] [W](6) 00 00 07 df 10 92
[20:06:10.216] kwp2000 request readEcuIdentification - 1 bytes
[20:06:10.216] [1A] 87
[20:06:10.216] [W](6) 00 00 07 e0 1a 87
[20:06:10.717] unable to receive correct kwp2000 response
[20:06:10.717] kwp2000 request readEcuIdentification - 1 bytes
[20:06:10.717] [1A] 9C
[20:06:10.717] [W](6) 00 00 07 e0 1a 9c
[20:06:11.219] unable to receive correct kwp2000 response
[20:06:11.219] kwp2000 request readEcuIdentification - 1 bytes
[20:06:11.219] [1A] 90
[20:06:11.219] [W](6) 00 00 07 e0 1a 90
[20:06:11.721] unable to receive correct kwp2000 response
[20:06:11.721] kwp2000 request testerPresent - 1 bytes
[20:06:11.721] [3E] 02
[20:06:11.721] [W](6) 00 00 07 df 3e 02
[20:06:11.722] kwp2000 request controlDTCSetting - 4 bytes
[20:06:11.722] [85] 02 FF 00 02
[20:06:11.722] [W](9) 00 00 00 1c 85 02 ff 00 02
[20:06:11.723] kwp2000 request communicationControl - 1 bytes
[20:06:11.723] [28] 02
[20:06:11.723] [W](6) 00 00 00 1c 28 02
[20:06:11.724] -- unlocking ECU --
[20:06:11.724] starting session...
[20:06:11.724] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:11.724] [10] 85
[20:06:11.724] [W](6) 00 00 07 e0 10 85
[20:06:12.226] unable to receive correct kwp2000 response
[20:06:12.226] requesting seed...
[20:06:12.226] kwp2000 request securityAccess - 1 bytes
[20:06:12.226] [27] 05
[20:06:12.226] [W](6) 00 00 07 e0 27 05
[20:06:12.728] unable to receive correct kwp2000 response
[20:06:12.728] interface close
[20:06:12.729] interface close
[20:06:23.065] interface open
[20:06:23.077] J2534 API Version: 04.04
[20:06:23.077] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[20:06:23.077] Device Firmware Version: 1.15.4474
[20:06:23.077] Device Serial Number: TAcTvY0Y
[20:06:23.078] characteristics set to 0,8,1
[20:06:23.078] flush
[20:06:24.762] -- connecting to kernel --
[20:06:24.762] kernel get version
[20:06:24.762] [W](5) 00 00 07 e0 01
[20:06:24.963] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:24.963] [10] 92
[20:06:24.963] [W](6) 00 00 07 df 10 92
[20:06:25.065] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:25.065] [10] 92
[20:06:25.065] [W](6) 00 00 07 df 10 92
[20:06:25.065] kwp2000 request readEcuIdentification - 1 bytes
[20:06:25.066] [1A] 87
[20:06:25.066] [W](6) 00 00 07 e0 1a 87
[20:06:25.567] unable to receive correct kwp2000 response
[20:06:25.567] interface close
[20:06:25.568] interface close
[20:06:30.877] interface open
[20:06:30.889] J2534 API Version: 04.04
[20:06:30.889] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[20:06:30.889] Device Firmware Version: 1.15.4474
[20:06:30.889] Device Serial Number: TAcTvY0Y
[20:06:30.890] characteristics set to 0,8,1
[20:06:30.890] flush
[20:06:33.524] Clearing DTCs for module at 0x7E0
[20:06:33.525] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:33.525] [10] 92
[20:06:33.525] [W](6) 00 00 07 e0 10 92
[20:06:34.027] unable to receive correct kwp2000 response
[20:06:34.027] Clearing DTCs for module at 0x7E1
[20:06:34.028] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:34.028] [10] 92
[20:06:34.028] [W](6) 00 00 07 e1 10 92
[20:06:34.033] [R](6) 00 00 07 e9 50 92
[20:06:34.033] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:34.033] [50] 92
[20:06:34.033] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:34.033] [14] FF 00
[20:06:34.033] [W](7) 00 00 07 e1 14 ff 00
[20:06:34.044] [R](7) 00 00 07 e9 54 ff 00
[20:06:34.045] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:34.045] [54] FF 00
[20:06:34.045] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:34.045] [10] 81
[20:06:34.045] [W](6) 00 00 07 e1 10 81
[20:06:34.053] [R](6) 00 00 07 e9 50 81
[20:06:34.053] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:34.053] [50] 81
[20:06:34.053] DTCs cleared.
[20:06:34.053] Clearing DTCs for module at 0x620
[20:06:34.054] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:34.054] [10] 92
[20:06:34.054] [W](6) 00 00 06 20 10 92
[20:06:34.056] [R](6) 00 00 05 04 50 92
[20:06:34.056] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:34.056] [50] 92
[20:06:34.056] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:34.056] [14] FF 00
[20:06:34.056] [W](7) 00 00 06 20 14 ff 00
[20:06:34.076] [R](7) 00 00 05 04 7f 14 78
[20:06:34.076] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending
[20:06:34.295] [R](7) 00 00 05 04 54 ff 00
[20:06:34.295] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:34.295] [54] FF 00
[20:06:34.295] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:34.295] [10] 81
[20:06:34.295] [W](6) 00 00 06 20 10 81
[20:06:34.305] [R](6) 00 00 05 04 50 81
[20:06:34.306] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:34.306] [50] 81
[20:06:34.306] DTCs cleared.
[20:06:34.306] Clearing DTCs for module at 0x784
[20:06:34.307] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:34.307] [10] 92
[20:06:34.307] [W](6) 00 00 07 84 10 92
[20:06:34.325] [R](6) 00 00 07 85 50 92
[20:06:34.326] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:34.326] [50] 92
[20:06:34.326] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:34.326] [14] FF 00
[20:06:34.326] [W](7) 00 00 07 84 14 ff 00
[20:06:34.366] [R](7) 00 00 07 85 7f 14 78
[20:06:34.366] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending
[20:06:34.685] [R](7) 00 00 07 85 54 ff 00
[20:06:34.686] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:34.686] [54] FF 00
[20:06:34.686] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:34.686] [10] 81
[20:06:34.686] [W](6) 00 00 07 84 10 81
[20:06:34.706] [R](6) 00 00 07 85 50 81
[20:06:34.706] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:34.706] [50] 81
[20:06:34.706] DTCs cleared.
[20:06:34.706] Clearing DTCs for module at 0x6A0
[20:06:34.707] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:34.707] [10] 92
[20:06:34.707] [W](6) 00 00 06 a0 10 92
[20:06:34.718] [R](6) 00 00 05 14 50 92
[20:06:34.718] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:34.718] [50] 92
[20:06:34.718] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:34.718] [14] FF 00
[20:06:34.718] [W](7) 00 00 06 a0 14 ff 00
[20:06:34.727] [R](7) 00 00 05 14 54 ff 00
[20:06:34.727] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:34.727] [54] FF 00
[20:06:34.727] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:34.727] [10] 81
[20:06:34.727] [W](6) 00 00 06 a0 10 81
[20:06:34.737] [R](6) 00 00 05 14 50 81
[20:06:34.737] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:34.737] [50] 81
[20:06:34.737] DTCs cleared.
[20:06:34.737] Clearing DTCs for module at 0x77B
[20:06:34.738] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:34.738] [10] 92
[20:06:34.738] [W](6) 00 00 07 7b 10 92
[20:06:35.240] unable to receive correct kwp2000 response
[20:06:35.240] Clearing DTCs for module at 0x622
[20:06:35.241] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:35.241] [10] 92
[20:06:35.241] [W](6) 00 00 06 22 10 92
[20:06:35.246] [R](6) 00 00 04 84 50 92
[20:06:35.246] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:35.246] [50] 92
[20:06:35.246] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:35.246] [14] FF 00
[20:06:35.246] [W](7) 00 00 06 22 14 ff 00
[20:06:35.263] [R](7) 00 00 04 84 7f 14 78
[20:06:35.263] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending
[20:06:35.285] [R](7) 00 00 04 84 54 ff 00
[20:06:35.285] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:35.285] [54] FF 00
[20:06:35.285] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:35.285] [10] 81
[20:06:35.285] [W](6) 00 00 06 22 10 81
[20:06:35.293] [R](6) 00 00 04 84 50 81
[20:06:35.293] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:35.293] [50] 81
[20:06:35.294] DTCs cleared.
[20:06:35.294] Clearing DTCs for module at 0x7B6
[20:06:35.294] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:35.294] [10] 92
[20:06:35.294] [W](6) 00 00 07 b6 10 92
[20:06:35.796] unable to receive correct kwp2000 response
[20:06:35.798] Clearing DTCs for module at 0x688
[20:06:35.800] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:35.800] [10] 92
[20:06:35.800] [W](6) 00 00 06 88 10 92
[20:06:35.817] [R](6) 00 00 05 11 50 92
[20:06:35.817] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:35.817] [50] 92
[20:06:35.817] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:35.817] [14] FF 00
[20:06:35.817] [W](7) 00 00 06 88 14 ff 00
[20:06:35.847] [R](7) 00 00 05 11 54 ff 00
[20:06:35.847] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:35.847] [54] FF 00
[20:06:35.847] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:35.847] [10] 81
[20:06:35.847] [W](6) 00 00 06 88 10 81
[20:06:35.877] [R](6) 00 00 05 11 50 81
[20:06:35.877] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:35.877] [50] 81
[20:06:35.878] DTCs cleared.
[20:06:35.878] Clearing DTCs for module at 0x600
[20:06:35.878] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:35.878] [10] 92
[20:06:35.878] [W](6) 00 00 06 00 10 92
[20:06:35.892] [R](6) 00 00 05 00 50 92
[20:06:35.893] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:35.893] [50] 92
[20:06:35.893] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:35.893] [14] FF 00
[20:06:35.893] [W](7) 00 00 06 00 14 ff 00
[20:06:35.902] [R](7) 00 00 05 00 54 ff 00
[20:06:35.902] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:35.902] [54] FF 00
[20:06:35.902] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:35.902] [10] 81
[20:06:35.902] [W](6) 00 00 06 00 10 81
[20:06:35.915] [R](6) 00 00 05 00 50 81
[20:06:35.915] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:35.915] [50] 81
[20:06:35.916] DTCs cleared.
[20:06:35.916] Clearing DTCs for module at 0x6E0
[20:06:35.916] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:35.916] [10] 92
[20:06:35.916] [W](6) 00 00 06 e0 10 92
[20:06:35.922] [R](6) 00 00 05 1c 50 92
[20:06:35.922] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:35.922] [50] 92
[20:06:35.922] kwp2000 request clearDiagnosticInformation - 2 bytes

Shinzon

iTrader: (4)

[20:06:35.922] [14] FF 00
[20:06:35.922] [W](7) 00 00 06 e0 14 ff 00
[20:06:35.962] [R](7) 00 00 05 1c 7f 14 78
[20:06:35.962] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending
[20:06:35.992] [R](7) 00 00 05 1c 54 ff 00
[20:06:35.992] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:35.992] [54] FF 00
[20:06:35.992] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:35.992] [10] 81
[20:06:35.992] [W](6) 00 00 06 e0 10 81
[20:06:36.022] [R](6) 00 00 05 1c 50 81
[20:06:36.022] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:36.022] [50] 81
[20:06:36.022] DTCs cleared.
[20:06:36.022] Clearing DTCs for module at 0x6E8
[20:06:36.023] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:36.023] [10] 92
[20:06:36.023] [W](6) 00 00 06 e8 10 92
[20:06:36.033] [R](6) 00 00 05 1d 50 92
[20:06:36.033] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:36.033] [50] 92
[20:06:36.033] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:36.033] [14] FF 00
[20:06:36.033] [W](7) 00 00 06 e8 14 ff 00
[20:06:36.055] [R](7) 00 00 05 1d 7f 14 78
[20:06:36.055] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending
[20:06:36.474] [R](7) 00 00 05 1d 54 ff 00
[20:06:36.474] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:36.474] [54] FF 00
[20:06:36.474] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:36.474] [10] 81
[20:06:36.474] [W](6) 00 00 06 e8 10 81
[20:06:36.483] [R](6) 00 00 05 1d 50 81
[20:06:36.483] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:36.483] [50] 81
[20:06:36.483] DTCs cleared.
[20:06:36.483] Clearing DTCs for module at 0x7A8
[20:06:36.484] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:36.484] [10] 92
[20:06:36.484] [W](6) 00 00 07 a8 10 92
[20:06:36.986] unable to receive correct kwp2000 response
[20:06:36.986] Clearing DTCs for module at 0x6B0
[20:06:36.987] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:36.987] [10] 92
[20:06:36.987] [W](6) 00 00 06 b0 10 92
[20:06:37.489] unable to receive correct kwp2000 response
[20:06:37.489] Clearing DTCs for module at 0x7D8
[20:06:37.490] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:37.490] [10] 92
[20:06:37.490] [W](6) 00 00 07 d8 10 92
[20:06:37.992] unable to receive correct kwp2000 response
[20:06:37.992] Clearing DTCs for module at 0x7F8
[20:06:37.993] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:37.993] [10] 92
[20:06:37.993] [W](6) 00 00 07 f8 10 92
[20:06:38.494] unable to receive correct kwp2000 response
[20:06:38.494] Clearing DTCs for module at 0x790
[20:06:38.495] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:38.495] [10] 92
[20:06:38.495] [W](6) 00 00 07 90 10 92
[20:06:38.997] unable to receive correct kwp2000 response
[20:06:38.997] Clearing DTCs for module at 0x728
[20:06:38.998] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:38.998] [10] 92
[20:06:38.998] [W](6) 00 00 07 28 10 92
[20:06:39.500] unable to receive correct kwp2000 response
[20:06:39.500] Clearing DTCs for module at 0x648
[20:06:39.501] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:39.501] [10] 92
[20:06:39.501] [W](6) 00 00 06 48 10 92
[20:06:40.003] unable to receive correct kwp2000 response
[20:06:40.003] Clearing DTCs for module at 0x658
[20:06:40.004] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:40.004] [10] 92
[20:06:40.004] [W](6) 00 00 06 58 10 92
[20:06:40.505] unable to receive correct kwp2000 response
[20:06:40.505] Clearing DTCs for module at 0x7B5
[20:06:40.506] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:40.506] [10] 92
[20:06:40.506] [W](6) 00 00 07 b5 10 92
[20:06:40.511] [R](6) 00 00 07 b4 50 92
[20:06:40.511] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:40.511] [50] 92
[20:06:40.511] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:40.511] [14] FF 00
[20:06:40.511] [W](7) 00 00 07 b5 14 ff 00
[20:06:40.531] [R](7) 00 00 07 b4 54 ff 00
[20:06:40.531] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:40.531] [54] FF 00
[20:06:40.531] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:40.531] [10] 81
[20:06:40.531] [W](6) 00 00 07 b5 10 81
[20:06:40.541] [R](6) 00 00 07 b4 50 81
[20:06:40.541] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:40.541] [50] 81
[20:06:40.541] DTCs cleared.
[20:06:40.541] Clearing DTCs for module at 0x7B9
[20:06:40.542] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:40.542] [10] 92
[20:06:40.542] [W](6) 00 00 07 b9 10 92
[20:06:41.044] unable to receive correct kwp2000 response
[20:06:41.044] Clearing DTCs for module at 0x6B2
[20:06:41.045] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:41.045] [10] 92
[20:06:41.045] [W](6) 00 00 06 b2 10 92
[20:06:41.547] unable to receive correct kwp2000 response
[20:06:41.547] Clearing DTCs for module at 0x769
[20:06:41.548] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:41.548] [10] 92
[20:06:41.548] [W](6) 00 00 07 69 10 92
[20:06:42.049] unable to receive correct kwp2000 response
[20:06:42.049] Clearing DTCs for module at 0x794
[20:06:42.050] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:42.050] [10] 92
[20:06:42.050] [W](6) 00 00 07 94 10 92
[20:06:42.552] unable to receive correct kwp2000 response
[20:06:42.552] Clearing DTCs for module at 0x788
[20:06:42.553] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:42.553] [10] 92
[20:06:42.553] [W](6) 00 00 07 88 10 92
[20:06:42.569] [R](6) 00 00 07 89 50 92
[20:06:42.569] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:42.569] [50] 92
[20:06:42.569] kwp2000 request clearDiagnosticInformation - 2 bytes
[20:06:42.569] [14] FF 00
[20:06:42.569] [W](7) 00 00 07 88 14 ff 00
[20:06:42.609] [R](7) 00 00 07 89 54 ff 00
[20:06:42.609] kwp2000 response to clearDiagnosticInformation - 2 bytes
[20:06:42.609] [54] FF 00
[20:06:42.609] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:42.609] [10] 81
[20:06:42.609] [W](6) 00 00 07 88 10 81
[20:06:42.629] [R](6) 00 00 07 89 50 81
[20:06:42.629] kwp2000 response to startDiagnosticSession - 1 bytes
[20:06:42.629] [50] 81
[20:06:42.629] DTCs cleared.
[20:06:42.629] Clearing DTCs for module at 0x660
[20:06:42.630] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:42.630] [10] 92
[20:06:42.630] [W](6) 00 00 06 60 10 92
[20:06:43.132] unable to receive correct kwp2000 response
[20:06:43.132] Clearing DTCs for module at 0x6B4
[20:06:43.133] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:43.133] [10] 92
[20:06:43.133] [W](6) 00 00 06 b4 10 92
[20:06:43.634] unable to receive correct kwp2000 response
[20:06:43.634] Clearing DTCs for module at 0x7D0
[20:06:43.635] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:43.635] [10] 92
[20:06:43.635] [W](6) 00 00 07 d0 10 92
[20:06:44.137] unable to receive correct kwp2000 response
[20:06:44.137] Clearing DTCs for module at 0x798
[20:06:44.138] kwp2000 request startDiagnosticSession - 1 bytes
[20:06:44.138] [10] 92
[20:06:44.138] [W](6) 00 00 07 98 10 92
[20:06:44.639] unable to receive correct kwp2000 response
[20:06:44.639] interface close
[20:06:44.640] interface close




as you can see i tried to do a rax patch. i tried it without the patch with the same results. have removed and reinstalled ecuflash, still same. with one change. i can clear the dtc using evoscan now but under "can obdII EFI" ecu option only. the other ecu options (can mut III sst/ayc) do not clear the dtc. normaly associated with MR flash dtcs. please help

MikeyPSF

I wanted to add a note to explain what happened to the previous poster. He created a definition for 5959006 by inheriting directly from 5959004, which is mostly correct except the Mode 23 is at a different address. Looking at the mode 23 options in 5959006 it said 'no match' which indicates that the expected value to toggle was not there. When that 'no match' was forced to the expected value (at the wrong location) it caused an ECU communication problem that could only be corrected with a bench reflash. The moral of the story is that if it says 'no match' that means the table is invalid and shouldn't be used. We'll update that field to a bloblist type variable in a future release to make it impossible to force that sort of value where it doesn't fit.

-Mike
Tactrix

Shinzon

iTrader: (4)

That's not entirely correct. Mine didn't say "no match" cause I was using downloaded golden Evo definitions from his site. Not default Tactrix which I should have. On the golden Evo def in only allows me to change direct hex values. On Tactrix its a on off switch . later when mike told me it says "no match" I realised the difference between how the definitions are written . so the moral of the story is USE TACTRIX DEFINITIONS! If I did I would have realised it is wrong.

Shinzon

iTrader: (4)

On the brighter side I made a really good benching kit for the future .

richardjh

Technically, the moral of the story is not to create off-the-cuff ROM inheritance XMLs, eg.

Taking an XML for 5959004 (which does exist on goldenevo.com)...

...and using it to edit a ROM which is not code/data aligned, such as 59590006 (which does not exist on goldenevo.com at the time of writing).


It doesn't matter if a "base" XML comes from Tactrix, from goldenevo.com or anywhere else. You should never or copy it so as to edit a different ROM image...

...not unless you've disassembled both ROMs, and know all code/data items are aligned.


As a side note, if an XML allows raw hex editing, it's good form for the author to describe both the expected source and the destination data in the item name, eg.

Mode 23 - IFMode 0x05 -> 0x23 #1

If you go to edit that, and find the pre-edit value is NOT 0x05, don't touch it.

That's no ironclad guarantee that an INCORRECT address won't inadvertently point at the "wrong" 0x05 byte... but not even blobbit source/dest checks will save you from that!

Rich

Shinzon

iTrader: (4)

As a result