cant read or write ecu using ecu flash (latest version from tactrix)

When attempting to read or write ECU Flash leaves a dtc. i used evoscan to read it
its "j2534 read error - 16" X

i tried using a brand new tactrix 2.0 as well and nothing is working. clean uninstall and reinstall has been attempted. tried installing the drivers as well separately from tactrix website.

 

this is my log from ecuflash

[09:36:23.820] EcuFlash Version 1.44.4503
[09:36:23.820] OS Version Windows 7

[09:36:23.820] Kernel Type winnt

[09:36:23.820] Kernel Version 6.1.7601

[09:36:23.820] CPU x86_64

[09:36:23.820] Product Name Windows 7

[09:36:23.820] Product Type windows

[09:36:23.820] Product Version 7

[09:36:23.820] Qt Version 5.4.0

[09:36:23.835] 67 memory models read.

[09:36:23.835] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata

[09:36:26.378] 748 ROM metadata models scanned.

[09:36:26.378] checksum module "subarudbw" loaded.

[09:36:26.378] checksum module "subarudiesel" loaded.

[09:36:26.378] checksum module "mitsucan" loaded.

[09:36:26.378] checksum module "mitsuh8" loaded.

[09:36:26.378] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.

[09:36:26.378] patch module "Mitsu CAN RAM Parameter Logging" loaded.

[09:36:26.394] using metadata XML ID read_mitsum32186f8can from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_mitsum32186f8can.xml

[09:36:26.394] flashing tool "wrx02" loaded.

[09:36:26.394] flashing tool "wrx04" loaded.

[09:36:26.394] flashing tool "sti04" loaded.

[09:36:26.394] flashing tool "sti05" loaded.

[09:36:26.394] flashing tool "mitsucan" loaded.

[09:36:26.394] flashing tool "mitsukernel" loaded.

[09:36:26.394] flashing tool "mitsukernelocp" loaded.

[09:36:26.394] flashing tool "mitsubootloader" loaded.

[09:36:26.394] flashing tool "shbootmode" loaded.

[09:36:26.394] flashing tool "shaudmode" loaded.

[09:36:26.394] flashing tool "subarucan" loaded.

[09:36:26.394] flashing tool "subarucand" loaded.

[09:36:26.409] flashing tool "subarubrz" loaded.

[09:36:26.409] flashing tool "subaruhitachi" loaded.

[09:38:18.607] using metadata XML ID read_mitsum32186f8can from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_mitsum32186f8can.xml

[09:38:18.607] baud set to 500000

[09:38:18.607] interface open

[09:38:18.638] J2534 API Version: 04.04

[09:38:18.638] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08

[09:38:18.638] Device Firmware Version: 1.15.4474

[09:38:18.638] Device Serial Number: TA43Gwi3

[09:38:18.638] characteristics set to 0,8,1

[09:38:18.638] flush

[09:38:20.588] -- loading kernel --

[09:38:20.588] -- connecting to kernel --

[09:38:20.588] kernel get version

[09:38:20.588] [W](5) 00 00 07 e0 01

[09:38:20.806] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:20.806] [10] 92

[09:38:20.806] [W](6) 00 00 07 df 10 92

[09:38:20.915] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:20.915] [10] 92

[09:38:20.915] [W](6) 00 00 07 df 10 92

[09:38:20.915] kwp2000 request readEcuIdentification - 1 bytes

[09:38:20.915] [1A] 87

[09:38:20.915] [W](6) 00 00 07 e0 1a 87

[09:38:21.430] unable to receive correct kwp2000 response

[09:38:21.430] kwp2000 request readEcuIdentification - 1 bytes

[09:38:21.430] [1A] 9C

[09:38:21.430] [W](6) 00 00 07 e0 1a 9c

[09:38:21.945] unable to receive correct kwp2000 response

[09:38:21.945] kwp2000 request readEcuIdentification - 1 bytes

[09:38:21.945] [1A] 90

[09:38:21.945] [W](6) 00 00 07 e0 1a 90

[09:38:22.460] unable to receive correct kwp2000 response

[09:38:22.460] kwp2000 request testerPresent - 1 bytes

[09:38:22.460] [3E] 02

[09:38:22.460] [W](6) 00 00 07 df 3e 02

[09:38:22.460] kwp2000 request controlDTCSetting - 4 bytes

[09:38:22.460] [85] 02 FF 00 02

[09:38:22.460] [W](9) 00 00 00 1c 85 02 ff 00 02

[09:38:22.460] kwp2000 request communicationControl - 1 bytes

[09:38:22.460] [28] 02

[09:38:22.460] [W](6) 00 00 00 1c 28 02

[09:38:22.460] -- unlocking ECU --

[09:38:22.460] starting session...

[09:38:22.460] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:22.460] [10] 85

[09:38:22.460] [W](6) 00 00 07 e0 10 85

[09:38:22.975] unable to receive correct kwp2000 response

[09:38:22.975] requesting seed...

[09:38:22.975] kwp2000 request securityAccess - 1 bytes

[09:38:22.975] [27] 05

[09:38:22.975] [W](6) 00 00 07 e0 27 05

[09:38:23.489] unable to receive correct kwp2000 response

[09:38:23.489] interface close

[09:38:23.489] interface close

[09:38:34.814] interface open

[09:38:34.830] J2534 API Version: 04.04

[09:38:34.830] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08

[09:38:34.830] Device Firmware Version: 1.15.4474

[09:38:34.830] Device Serial Number: TA43Gwi3

[09:38:34.830] characteristics set to 0,8,1

[09:38:34.830] flush

[09:38:37.404] -- connecting to kernel --

[09:38:37.404] kernel get version

[09:38:37.404] [W](5) 00 00 07 e0 01

[09:38:37.607] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:37.607] [10] 92

[09:38:37.607] [W](6) 00 00 07 df 10 92

[09:38:37.716] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:37.716] [10] 92

[09:38:37.716] [W](6) 00 00 07 df 10 92

[09:38:37.716] kwp2000 request readEcuIdentification - 1 bytes

[09:38:37.716] [1A] 87

[09:38:37.716] [W](6) 00 00 07 e0 1a 87

[09:38:38.231] unable to receive correct kwp2000 response

[09:38:38.231] interface close

[09:38:38.231] interface close

[09:38:50.901] interface open

[09:38:50.917] J2534 API Version: 04.04

[09:38:50.917] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08

[09:38:50.917] Device Firmware Version: 1.15.4474

[09:38:50.917] Device Serial Number: TA43Gwi3

[09:38:50.917] characteristics set to 0,8,1

[09:38:50.917] flush

[09:38:53.194] Clearing DTCs for module at 0x7E0

[09:38:53.194] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:53.194] [10] 92

[09:38:53.194] [W](6) 00 00 07 e0 10 92

[09:38:53.709] unable to receive correct kwp2000 response

[09:38:53.709] Clearing DTCs for module at 0x7E1

[09:38:53.709] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:53.709] [10] 92

[09:38:53.709] [W](6) 00 00 07 e1 10 92

[09:38:53.725] [R](6) 00 00 07 e9 50 92

[09:38:53.725] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:53.725] [50] 92

[09:38:53.725] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:38:53.725] [14] FF 00

[09:38:53.725] [W](7) 00 00 07 e1 14 ff 00

[09:38:53.725] [R](7) 00 00 07 e9 54 ff 00

[09:38:53.725] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:38:53.725] [54] FF 00

[09:38:53.725] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:53.725] [10] 81

[09:38:53.725] [W](6) 00 00 07 e1 10 81

[09:38:53.740] [R](6) 00 00 07 e9 50 81

[09:38:53.740] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:53.740] [50] 81

[09:38:53.740] DTCs cleared.

[09:38:53.740] Clearing DTCs for module at 0x620

[09:38:53.740] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:53.740] [10] 92

[09:38:53.740] [W](6) 00 00 06 20 10 92

[09:38:53.740] [R](6) 00 00 05 04 50 92

[09:38:53.740] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:53.740] [50] 92

[09:38:53.740] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:38:53.740] [14] FF 00

[09:38:53.740] [W](7) 00 00 06 20 14 ff 00

[09:38:53.771] [R](7) 00 00 05 04 7f 14 78

[09:38:53.771] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending

[09:38:53.990] [R](7) 00 00 05 04 54 ff 00

[09:38:53.990] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:38:53.990] [54] FF 00

[09:38:53.990] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:53.990] [10] 81

[09:38:53.990] [W](6) 00 00 06 20 10 81

[09:38:53.990] [R](6) 00 00 05 04 50 81

[09:38:53.990] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:53.990] [50] 81

[09:38:53.990] DTCs cleared.

[09:38:53.990] Clearing DTCs for module at 0x784

[09:38:53.990] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:53.990] [10] 92

[09:38:54.005] [W](6) 00 00 07 84 10 92

[09:38:54.021] [R](6) 00 00 07 85 50 92

[09:38:54.021] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:54.021] [50] 92

[09:38:54.021] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:38:54.021] [14] FF 00

[09:38:54.021] [W](7) 00 00 07 84 14 ff 00

[09:38:54.052] [R](7) 00 00 07 85 7f 14 78

[09:38:54.052] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending

[09:38:54.380] [R](7) 00 00 07 85 54 ff 00

[09:38:54.380] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:38:54.380] [54] FF 00

[09:38:54.380] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:54.380] [10] 81

[09:38:54.380] [W](6) 00 00 07 84 10 81

[09:38:54.395] [R](6) 00 00 07 85 50 81

[09:38:54.395] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:54.395] [50] 81

[09:38:54.395] DTCs cleared.

[09:38:54.395] Clearing DTCs for module at 0x6A0

[09:38:54.395] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:54.395] [10] 92

[09:38:54.395] [W](6) 00 00 06 a0 10 92

[09:38:54.411] [R](6) 00 00 05 14 50 92

[09:38:54.411] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:54.411] [50] 92

[09:38:54.411] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:38:54.411] [14] FF 00

[09:38:54.411] [W](7) 00 00 06 a0 14 ff 00

[09:38:54.411] [R](7) 00 00 05 14 54 ff 00

[09:38:54.411] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:38:54.411] [54] FF 00

[09:38:54.411] kwp2000 request startDiagnosticSession - 1 bytes

 

[09:38:54.411] [10] 81

[09:38:54.411] [W](6) 00 00 06 a0 10 81

[09:38:54.427] [R](6) 00 00 05 14 50 81

[09:38:54.427] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:54.427] [50] 81

[09:38:54.427] DTCs cleared.

[09:38:54.427] Clearing DTCs for module at 0x77B

[09:38:54.427] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:54.427] [10] 92

[09:38:54.427] [W](6) 00 00 07 7b 10 92

[09:38:54.941] unable to receive correct kwp2000 response

[09:38:54.941] Clearing DTCs for module at 0x622

[09:38:54.941] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:54.941] [10] 92

[09:38:54.941] [W](6) 00 00 06 22 10 92

[09:38:54.941] [R](6) 00 00 04 84 50 92

[09:38:54.941] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:54.941] [50] 92

[09:38:54.941] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:38:54.941] [14] FF 00

[09:38:54.941] [W](7) 00 00 06 22 14 ff 00

[09:38:54.957] [R](7) 00 00 04 84 7f 14 78

[09:38:54.957] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending

[09:38:54.988] [R](7) 00 00 04 84 54 ff 00

[09:38:54.988] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:38:54.988] [54] FF 00

[09:38:54.988] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:54.988] [10] 81

[09:38:54.988] [W](6) 00 00 06 22 10 81

[09:38:54.988] [R](6) 00 00 04 84 50 81

[09:38:54.988] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:54.988] [50] 81

[09:38:54.988] DTCs cleared.

[09:38:54.988] Clearing DTCs for module at 0x7B6

[09:38:54.988] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:54.988] [10] 92

[09:38:54.988] [W](6) 00 00 07 b6 10 92

[09:38:55.503] unable to receive correct kwp2000 response

[09:38:55.503] Clearing DTCs for module at 0x688

[09:38:55.503] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:55.503] [10] 92

[09:38:55.503] [W](6) 00 00 06 88 10 92

[09:38:55.519] [R](6) 00 00 05 11 50 92

[09:38:55.519] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:55.519] [50] 92

[09:38:55.519] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:38:55.519] [14] FF 00

[09:38:55.519] [W](7) 00 00 06 88 14 ff 00

[09:38:55.550] [R](7) 00 00 05 11 54 ff 00

[09:38:55.550] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:38:55.550] [54] FF 00

[09:38:55.550] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:55.550] [10] 81

[09:38:55.550] [W](6) 00 00 06 88 10 81

[09:38:55.581] [R](6) 00 00 05 11 50 81

[09:38:55.581] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:55.581] [50] 81

[09:38:55.581] DTCs cleared.

[09:38:55.581] Clearing DTCs for module at 0x600

[09:38:55.581] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:55.581] [10] 92

[09:38:55.581] [W](6) 00 00 06 00 10 92

[09:38:55.581] [R](6) 00 00 05 00 50 92

[09:38:55.581] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:55.581] [50] 92

[09:38:55.581] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:38:55.581] [14] FF 00

[09:38:55.581] [W](7) 00 00 06 00 14 ff 00

[09:38:55.597] [R](7) 00 00 05 00 54 ff 00

[09:38:55.597] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:38:55.597] [54] FF 00

[09:38:55.597] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:55.597] [10] 81

[09:38:55.597] [W](6) 00 00 06 00 10 81

[09:38:55.612] [R](6) 00 00 05 00 50 81

[09:38:55.612] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:55.612] [50] 81

[09:38:55.612] DTCs cleared.

[09:38:55.612] Clearing DTCs for module at 0x6E0

[09:38:55.612] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:55.612] [10] 92

[09:38:55.612] [W](6) 00 00 06 e0 10 92

[09:38:55.628] [R](6) 00 00 05 1c 50 92

[09:38:55.628] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:55.628] [50] 92

[09:38:55.628] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:38:55.628] [14] FF 00

[09:38:55.628] [W](7) 00 00 06 e0 14 ff 00

[09:38:55.659] [R](7) 00 00 05 1c 7f 14 78

[09:38:55.659] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending

[09:38:55.690] [R](7) 00 00 05 1c 54 ff 00

[09:38:55.690] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:38:55.690] [54] FF 00

[09:38:55.690] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:55.690] [10] 81

[09:38:55.690] [W](6) 00 00 06 e0 10 81

[09:38:55.721] [R](6) 00 00 05 1c 50 81

[09:38:55.721] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:55.721] [50] 81

[09:38:55.721] DTCs cleared.

[09:38:55.721] Clearing DTCs for module at 0x6E8

[09:38:55.721] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:55.721] [10] 92

[09:38:55.721] [W](6) 00 00 06 e8 10 92

[09:38:55.737] [R](6) 00 00 05 1d 50 92

[09:38:55.737] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:55.737] [50] 92

[09:38:55.737] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:38:55.737] [14] FF 00

[09:38:55.737] [W](7) 00 00 06 e8 14 ff 00

[09:38:55.753] [R](7) 00 00 05 1d 7f 14 78

[09:38:55.753] kwp2000 error clearDiagnosticInformation -> reqCorrectlyRcvd_RspPending

[09:38:56.174] [R](7) 00 00 05 1d 54 ff 00

[09:38:56.174] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:38:56.174] [54] FF 00

[09:38:56.174] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:56.174] [10] 81

[09:38:56.174] [W](6) 00 00 06 e8 10 81

[09:38:56.174] [R](6) 00 00 05 1d 50 81

[09:38:56.174] kwp2000 response to startDiagnosticSession - 1 bytes

[09:38:56.174] [50] 81

[09:38:56.174] DTCs cleared.

[09:38:56.174] Clearing DTCs for module at 0x7A8

[09:38:56.174] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:56.174] [10] 92

[09:38:56.174] [W](6) 00 00 07 a8 10 92

[09:38:56.689] unable to receive correct kwp2000 response

[09:38:56.689] Clearing DTCs for module at 0x6B0

[09:38:56.689] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:56.689] [10] 92

[09:38:56.689] [W](6) 00 00 06 b0 10 92

[09:38:57.203] unable to receive correct kwp2000 response

[09:38:57.203] Clearing DTCs for module at 0x7D8

[09:38:57.203] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:57.203] [10] 92

[09:38:57.203] [W](6) 00 00 07 d8 10 92

[09:38:57.718] unable to receive correct kwp2000 response

[09:38:57.718] Clearing DTCs for module at 0x7F8

[09:38:57.718] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:57.718] [10] 92

[09:38:57.718] [W](6) 00 00 07 f8 10 92

[09:38:58.233] unable to receive correct kwp2000 response

[09:38:58.233] Clearing DTCs for module at 0x790

[09:38:58.233] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:58.233] [10] 92

[09:38:58.233] [W](6) 00 00 07 90 10 92

[09:38:58.748] unable to receive correct kwp2000 response

[09:38:58.748] Clearing DTCs for module at 0x728

[09:38:58.748] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:58.748] [10] 92

[09:38:58.748] [W](6) 00 00 07 28 10 92

[09:38:59.263] unable to receive correct kwp2000 response

[09:38:59.263] Clearing DTCs for module at 0x648

[09:38:59.263] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:59.263] [10] 92

[09:38:59.263] [W](6) 00 00 06 48 10 92

[09:38:59.777] unable to receive correct kwp2000 response

[09:38:59.777] Clearing DTCs for module at 0x658

[09:38:59.777] kwp2000 request startDiagnosticSession - 1 bytes

[09:38:59.777] [10] 92

[09:38:59.777] [W](6) 00 00 06 58 10 92

[09:39:00.292] unable to receive correct kwp2000 response

[09:39:00.292] Clearing DTCs for module at 0x7B5

[09:39:00.292] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:00.292] [10] 92

[09:39:00.292] [W](6) 00 00 07 b5 10 92

[09:39:00.292] [R](6) 00 00 07 b4 50 92

[09:39:00.292] kwp2000 response to startDiagnosticSession - 1 bytes

[09:39:00.292] [50] 92

[09:39:00.292] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:39:00.292] [14] FF 00

[09:39:00.292] [W](7) 00 00 07 b5 14 ff 00

[09:39:00.323] [R](7) 00 00 07 b4 54 ff 00

[09:39:00.323] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:39:00.323] [54] FF 00

[09:39:00.323] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:00.323] [10] 81

[09:39:00.323] [W](6) 00 00 07 b5 10 81

[09:39:00.323] [R](6) 00 00 07 b4 50 81

[09:39:00.323] kwp2000 response to startDiagnosticSession - 1 bytes

[09:39:00.323] [50] 81

[09:39:00.323] DTCs cleared.

[09:39:00.323] Clearing DTCs for module at 0x7B9

[09:39:00.339] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:00.339] [10] 92

[09:39:00.339] [W](6) 00 00 07 b9 10 92

[09:39:00.854] unable to receive correct kwp2000 response

[09:39:00.854] Clearing DTCs for module at 0x6B2

[09:39:00.854] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:00.854] [10] 92

[09:39:00.854] [W](6) 00 00 06 b2 10 92

[09:39:01.369] unable to receive correct kwp2000 response

[09:39:01.369] Clearing DTCs for module at 0x769

[09:39:01.369] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:01.369] [10] 92

[09:39:01.369] [W](6) 00 00 07 69 10 92

[09:39:01.883] unable to receive correct kwp2000 response

[09:39:01.883] Clearing DTCs for module at 0x794

[09:39:01.883] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:01.883] [10] 92

[09:39:01.883] [W](6) 00 00 07 94 10 92

[09:39:02.398] unable to receive correct kwp2000 response

[09:39:02.398] Clearing DTCs for module at 0x788

[09:39:02.398] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:02.398] [10] 92

[09:39:02.398] [W](6) 00 00 07 88 10 92

[09:39:02.414] [R](6) 00 00 07 89 50 92

[09:39:02.414] kwp2000 response to startDiagnosticSession - 1 bytes

[09:39:02.414] [50] 92

[09:39:02.414] kwp2000 request clearDiagnosticInformation - 2 bytes

[09:39:02.414] [14] FF 00

[09:39:02.414] [W](7) 00 00 07 88 14 ff 00

[09:39:02.461] [R](7) 00 00 07 89 54 ff 00

[09:39:02.461] kwp2000 response to clearDiagnosticInformation - 2 bytes

[09:39:02.461] [54] FF 00

[09:39:02.461] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:02.461] [10] 81

[09:39:02.461] [W](6) 00 00 07 88 10 81

[09:39:02.476] [R](6) 00 00 07 89 50 81

[09:39:02.476] kwp2000 response to startDiagnosticSession - 1 bytes

[09:39:02.476] [50] 81

[09:39:02.476] DTCs cleared.

[09:39:02.476] Clearing DTCs for module at 0x660

[09:39:02.476] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:02.476] [10] 92

[09:39:02.476] [W](6) 00 00 06 60 10 92

[09:39:02.991] unable to receive correct kwp2000 response

[09:39:02.991] Clearing DTCs for module at 0x6B4

[09:39:02.991] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:02.991] [10] 92

[09:39:02.991] [W](6) 00 00 06 b4 10 92

[09:39:03.506] unable to receive correct kwp2000 response

[09:39:03.506] Clearing DTCs for module at 0x7D0

[09:39:03.506] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:03.506] [10] 92

[09:39:03.506] [W](6) 00 00 07 d0 10 92

[09:39:04.021] unable to receive correct kwp2000 response

[09:39:04.021] Clearing DTCs for module at 0x798

[09:39:04.021] kwp2000 request startDiagnosticSession - 1 bytes

[09:39:04.021] [10] 92

[09:39:04.021] [W](6) 00 00 07 98 10 92

[09:39:04.535] unable to receive correct kwp2000 response

[09:39:04.535] interface close

[09:39:04.535] interface close

 

i tried using a different laptop, different ecuflash version, still nothing. car runs and drives fine.

 

I'd look into the firmware for your Tactrix and make sure you read with to car ON not running. did you contact Tactrix support? check device manager on your PC when you plug in your tactrix for errors too.

 

There was a forced firmware update recently , I do not know how to rollback the firmware in the openport 2.0 and yes I am trying to read and write with ignition "on"

 

I seen that on the website. I wonder if you can't load and older firmware to test. I have an 2008 gsr and went to compare my log vs yours. But I messed up some thing. I'd say try a pervious version of EcuFlash then the previous firmware and see what happens.

I wasn't trying you intelligence by making sure the car was on. Just checking our basis.

 

Lol, no I didn't take any insult to it. Thanks BTW. I have tried a few different versions of ecuflash with same result. Tactrix got back to me last night . Mike is saying there is some response back from the ECU but not all. It's not bricked. He is thinking I might have wiped some memories/parameters with bad data by using incompatible patch or definitions . he is checking my rom which is 5959006. Inherited from 5959004. When I use definitions that came with ecuflash and turn on "show undefined or incompatible definitions ,but grey them out" there are alot of tables greyed out. When I switch to the most recent definition from golden evo's website , there are none. So I'm thinking that's the issue. I'm waiting for him to get back to me. BTW I have never been able to log via mode 23. That's one of the things I turned on in my last successful flash. And this started to happen. Can someone please give me the rax patch for 5959006 ? Mike from Tactrix suggested the 5959004 rax patch might not be comparable with 5959006. Another funny thing I noticed is when I do attempt to flash the transmission overheat, and few other warning lights starts to pope up like it does during a normal flash. But after no response log it goes back to normal without bricking. If this happened to another Evo I was working on before it would have bricked it and fans would have been runing. It comes out of programming mode automatically .

 

OK, mike from Tactrix said even though it's not bricked the definition i am using is mostly correct (inherited from 5959004) except mode 23 strings. The previous year models address in not the same as 2015 Usdm MR. I used golden evo's def which is manual change to hex "23". So when I changed that value it changed something in the communication bits. When I load mikes defs it is an " enable" or "disable" option nothing to set manually, and it says "unavailable". So I have to bench flash the ECU with the last know good rom. Which still leaves me out of 23 mode logging . does anyone have the definitions for this for 2015 USDM MR rom of 5959006?

 

2015 Defs are hit and miss for completeness, what you can do is bench flash the rom down to a 2014 or even a 2010 Tephra ROM and get a ton more support. That said it is strange that you can't at least read what is there and save it despite not having xml defs because if anything went wrong you would want to have some option of going back to stock.

 

Luckily I saved my stock rom. I benched it back to stock and someone on this forum game me a working def file. Mike from Tactrix suspects the address on 2014 I used for mode 23 was wrong and messed something up in the communications department . now it works fine. I didn't realise I can bench a 2010 rom in it. How would the address work if it is in different locations ?