Hello all,

Yesterday I tried to read the ROM file from my ECU to edit and enable mode23 for logging purposes, When I clicked on read, a number of errors come up on the dashboard such as "transmission overheat" and shortly after EcuFlash presented me with "An error occurred, see log for more details" After this I was left with a Transmission Cell Light on, although the car starts and drives fine and the light has now gone off on its own? I am not sure what happened here, can anybody help please? It's almost like the software had tried to read the TCU instead of the ECU.

My Car is a 2014 FQ-440 MR

Any help is much appreciated.

Below is the error log for reference: -

[15:29:30.380] EcuFlash Version 1.44.4799
[15:29:30.380] OS Version Windows 10
[15:29:30.380] Kernel Type winnt
[15:29:30.380] Kernel Version 10.0.17134
[15:29:30.380] CPU x86_64
[15:29:30.380] Product Name Windows 10
[15:29:30.380] Product Type windows
[15:29:30.380] Product Version 10
[15:29:30.380] Qt Version 5.6.0
[15:29:30.380] Qwt Version 6.1.2
[15:29:30.380] QwtPlot3D Version 0.2.6
[15:29:30.380] Boost Version 1.60
[15:29:30.380] FTDI Library Version 3.02.11
[15:29:30.380] Openport J2534 Library Version 1.02.4798
[15:29:30.390] 67 memory models read.
[15:29:30.390] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[15:29:30.546] 745 ROM metadata models scanned.
[15:29:30.546] checksum module "subarudbw" loaded.
[15:29:30.546] checksum module "subarudiesel" loaded.
[15:29:30.546] checksum module "subaruhitachi" loaded.
[15:29:30.547] checksum module "mitsucan" loaded.
[15:29:30.547] checksum module "mitsuh8" loaded.
[15:29:30.547] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[15:29:30.547] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[15:29:30.549] using metadata XML ID read_mitsum32186f8 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_mitsum32186f8.xml
[15:29:30.553] flashing tool "wrx02" loaded.
[15:29:30.553] flashing tool "wrx04" loaded.
[15:29:30.557] flashing tool "sti04" loaded.
[15:29:30.557] flashing tool "sti05" loaded.
[15:29:30.557] flashing tool "mitsucan" loaded.
[15:29:30.557] flashing tool "mitsukernel" loaded.
[15:29:30.557] flashing tool "mitsukernelocp" loaded.
[15:29:30.557] flashing tool "mitsubootloader" loaded.
[15:29:30.557] flashing tool "shbootmode" loaded.
[15:29:30.557] flashing tool "shaudmode" loaded.
[15:29:30.561] flashing tool "subarucan" loaded.
[15:29:30.561] flashing tool "subarucand" loaded.
[15:29:30.565] flashing tool "subarubrz" loaded.
[15:29:30.565] flashing tool "subaruhitachi" loaded.
[15:29:30.604] J2534 API Version: 04.04
[15:29:30.604] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[15:29:30.604] Device Firmware Version: 1.17.4877
[15:29:30.604] Device Serial Number: TAv66JIX
[15:29:30.605] interface close
[15:29:30.626] J2534 API Version: 04.04
[15:29:30.626] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[15:29:30.626] Device Firmware Version: 1.17.4877
[15:29:30.626] Device Serial Number: TAv66JIX
[15:29:30.627] interface close
[15:29:30.654] J2534 API Version: 04.04
[15:29:30.654] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[15:29:30.654] Device Firmware Version: 1.17.4877
[15:29:30.654] Device Serial Number: TAv66JIX
[15:29:30.655] interface close
[15:29:30.676] J2534 API Version: 04.04
[15:29:30.676] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[15:29:30.676] Device Firmware Version: 1.17.4877
[15:29:30.676] Device Serial Number: TAv66JIX
[15:29:30.677] interface close
[15:29:30.705] J2534 API Version: 04.04
[15:29:30.705] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[15:29:30.705] Device Firmware Version: 1.17.4877
[15:29:30.705] Device Serial Number: TAv66JIX
[15:29:30.707] interface close
[15:29:30.729] J2534 API Version: 04.04
[15:29:30.729] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[15:29:30.729] Device Firmware Version: 1.17.4877
[15:29:30.729] Device Serial Number: TAv66JIX
[15:29:30.730] interface close
[15:29:36.759] using metadata XML ID read_mitsum32186f8 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_mitsum32186f8.xml
[15:29:36.777] J2534 API Version: 04.04
[15:29:36.777] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[15:29:36.777] Device Firmware Version: 1.17.4877
[15:29:36.777] Device Serial Number: TAv66JIX
[15:29:45.846] -- loading kernel --
[15:29:45.846] -- connecting to kernel --
[15:29:45.846] kernel get version
[15:29:46.174] ECU HW part number : 1860C335
[15:29:46.194] ECU SW part number : 1860C33500
[15:29:46.207] VIN :
[15:29:47.856] -- unlocking ECU --
[15:29:47.856] starting session...
[15:29:47.866] requesting seed...
[15:29:47.877] interface close
[15:29:47.878] interface close

 

Its normal to have all this errors during reading and writing.
After read or write you need to do a DTC clear

 

Yea, all SST equipped mitsu's will do that on read/write because the SST loses communication with ECU and throws an error. Totally normal, just clear the DTC after

 

Any chance the op could post that rom? The fq440 has an sst and 400 ft lbs of torque... just curious how the sst tables compare to my 08 MR

I know this is well over a year old, but worth a shot.