The Top DSM Community on the Web

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. Log in to remove most ads.

Please Support ExtremePSI
Please Support ExtremePSI

ECUflash ECUflash problem with 2G Blackbox ECU

This site may earn a commission from merchant
affiliate links, including eBay, Amazon, and others.

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

mac 108

15+ Year Contributor
216
3
Feb 15, 2005
Memphis, Tennessee
My car is a 90 AWD with a 2G blackbox flashable ECU.

Right now I cannot get ECUflash to communicate with the ECU. I have tried two different laptops, one using Win 7 and one using Win XP with no luck.

I have vehicle set to 96-01 Mistu All 2nd Gen. I am using a Tactrix Openport 2.0 cable.

Win XP Laptop

[23:58:59.171] EcuFlash Version 1.44.4503
[23:58:59.171] OS Version Windows XP
[23:58:59.171] Kernel Type winnt
[23:58:59.171] Kernel Version 5.1.2600
[23:58:59.171] CPU i386
[23:58:59.171] Product Name Windows XP
[23:58:59.171] Product Type windows
[23:58:59.171] Product Version xp
[23:58:59.171] Qt Version 5.4.0
[23:58:59.187] 67 memory models read.
[23:58:59.187] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[23:58:59.359] 747 ROM metadata models scanned.
[23:58:59.359] checksum module "subarudbw" loaded.
[23:58:59.359] checksum module "subarudiesel" loaded.
[23:58:59.359] checksum module "mitsucan" loaded.
[23:58:59.359] checksum module "mitsuh8" loaded.
[23:58:59.359] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[23:58:59.359] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[23:58:59.375] using metadata XML ID read_evo5 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[23:58:59.375] flashing tool "wrx02" loaded.
[23:58:59.375] flashing tool "wrx04" loaded.
[23:58:59.375] flashing tool "sti04" loaded.
[23:58:59.390] flashing tool "sti05" loaded.
[23:58:59.390] flashing tool "mitsucan" loaded.
[23:58:59.390] flashing tool "mitsukernel" loaded.
[23:58:59.390] flashing tool "mitsukernelocp" loaded.
[23:58:59.390] flashing tool "mitsubootloader" loaded.
[23:58:59.390] flashing tool "shbootmode" loaded.
[23:58:59.390] flashing tool "shaudmode" loaded.
[23:58:59.390] flashing tool "subarucan" loaded.
[23:58:59.390] flashing tool "subarucand" loaded.
[23:58:59.390] flashing tool "subarubrz" loaded.
[23:58:59.390] flashing tool "subaruhitachi" loaded.
[00:00:42.093] using metadata XML ID read_evo5 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[00:00:42.125] J2534 API Version: 04.04
[00:00:42.125] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[00:00:42.125] Device Firmware Version: 1.15.4474
[00:00:42.125] Device Serial Number: TAQocN*a
[00:00:49.359] sending init sequence 2
[00:00:51.375] interface close






Win 7 Laptop

[13:58:42.804] EcuFlash Version 1.44.4503
[13:58:42.804] OS Version Windows 7
[13:58:42.804] Kernel Type winnt
[13:58:42.804] Kernel Version 6.1.7601
[13:58:42.804] CPU i386
[13:58:42.804] Product Name Windows 7
[13:58:42.804] Product Type windows
[13:58:42.804] Product Version 7
[13:58:42.804] Qt Version 5.4.0
[13:58:42.819] 67 memory models read.
[13:58:42.819] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[13:58:48.669] 747 ROM metadata models scanned.
[13:58:48.669] checksum module "subarudbw" loaded.
[13:58:48.669] checksum module "subarudiesel" loaded.
[13:58:48.669] checksum module "mitsucan" loaded.
[13:58:48.669] checksum module "mitsuh8" loaded.
[13:58:48.669] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[13:58:48.669] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[13:58:48.685] using metadata XML ID read_evo5 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[13:58:48.685] flashing tool "wrx02" loaded.
[13:58:48.685] flashing tool "wrx04" loaded.
[13:58:48.700] flashing tool "sti04" loaded.
[13:58:48.700] flashing tool "sti05" loaded.
[13:58:48.700] flashing tool "mitsucan" loaded.
[13:58:48.700] flashing tool "mitsukernel" loaded.
[13:58:48.700] flashing tool "mitsukernelocp" loaded.
[13:58:48.700] flashing tool "mitsubootloader" loaded.
[13:58:48.700] flashing tool "shbootmode" loaded.
[13:58:48.700] flashing tool "shaudmode" loaded.
[13:58:48.700] flashing tool "subarucan" loaded.
[13:58:48.700] flashing tool "subarucand" loaded.
[13:58:48.700] flashing tool "subarubrz" loaded.
[13:58:48.716] flashing tool "subaruhitachi" loaded.
[13:59:05.678] using metadata XML ID read_evo5 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[13:59:05.693] J2534 API Version: 04.04
[13:59:05.693] J2534 DLL Version: 1.01.4500 Jun 26 2015 15:08:08
[13:59:05.693] Device Firmware Version: 1.15.4474
[13:59:05.693] Device Serial Number: TAQocN*a
[13:59:13.103] sending init sequence 2
[13:59:15.116] interface close



I can get my handheld OBDII code reader to read and erase codes properly.

I can also get EvoScan to connect and datalog with the OBDII 96-05 or Mitsu MUTIII boxes checked.

If I check DSM/3000GT/Eclipse MUTovrOBDII, I get a J2534 error.


What am I doing wrong?
 
No I have not. I thought that was not necessary for 98/99 2G blackbox ECUs.
 
Well looks I was completely wrong. Lost in the shuffle of my jumper harness for the 1G harness to 2G ECU conversion, I missed that important detail.

Could I wire a 2.5mm mono jack directly to Pin 79 on the jumper harness, plug it into the Tactrix dongle, and be good to go?
 
Yes that should be fine just make sure it is connected to the wire that runs to the tip of the plug. If you check out the first flashed ECU thread Ceddy posted about how he had to add the 2.5mm plug when he was doing it. Looks like Pin 79 & your good to go. Below is just a copy and paste of what he posted:

Adding a Flash Connector to a 95-97:
You must be logged in to view this image or video.

You must be logged in to view this image or video.

On 95-97s you must add a pin at position 79 of your ECU Harness.
This must be connected to the 2.5mm phono plug on your OpenPort 2.0 cable.
It must be connected to the tip of your phono plug.
 
That's what confused me. I have a 98 ECU, MD346675, but apparently it's still necessary for a plug.
 
Ya when he says 95-97 he means the year of the car itself. As the 98-99 cars that came from the factory with the black box ECU have pin 79 wired to a flash connector under the dash right next to the OBD connector. On these cars you don't have to wire anything up to flash the computer you can just use the (2.5mm phono plug - Mitsubishi Flash Plug) adapter that comes with the Tactrix 2.0 Cable
 
Now it all makes sense. Obviously, I missed that part. Thanks for the help.
 
Ok. I ordered a solder ready 2.5mm plug. I soldered it to one of the extra ECU wires and put it into port 79 on the ECU.

I still the same error when I try to read the rom using ECU Flash. I follow the step by step instructions, but the result is the same.

I'm at a loss on what to do next.
 
hook a battery charger too your car while doing this. (the black box ECU and the dongle are VERY voltage sensitive. ALWAYS have a battery charger on the car when trying to read or write the rom) i would bet a case it will work fine when you hook up the battery charger.
 
The battery is low from the car sitting so long. I hooked up the battery charger on maintenance free. I'll let it charge until this afternoon and give it a try.
 
leave the battery charger connected while doing the reading/writing. if the voltage sags even a tiny bit in the write process you hose the ECU. just always hook up a battery charger when doing stuff that involves an H8 ecu.
 
Battery is good. Charger is connected. Still get this log entry with the error message.

[00:00:42.125] Device Serial Number: TAQocN*a
[00:00:49.359] sending init sequence 2
[00:00:51.375] interface close
 
The H8 ECU is not as sensitive to the battery voltage problem as the later ecu's in the evo's. I have flashed with the battery voltage as low as 10 volts. What it will not tolerate is if you are not getting the 5 volt signal to the OBD connector. A good way to check this is to unplug the Tactrix cable from your laptop. The green light in the Tactrix cable should stay lit with just the cable plugged into the OBDII port. If it doesn't you arnt getting a good 5 volts to the cable.
 
Nevermind I see you said you can log with evoscan. If evoscan is working then you are getting the 5 volt signal to the OBD connector. That software will error as well if you arnt.
 
I checked the Tactrix dongle plugged into the OBD port without being connected and with the key turned to ON. The lights on the Tactrix work.

Whether I am have it connected to the laptop or not, the dongle always glows different colors. Is it supposed to be one solid color? Do multiple colors indicate a problem?
 
Last edited:
it will change color, that's good actually.

maybe the driver did not load. maybe delete the device out of device manager and reload the driver. i have had the driver fail to load a couple times but its not real common.
 
I tried it with two different laptops yesterday. I will reinstall and give it another shot.
 
Still haven't had any luck. Is it possible to test the flash plug with a multimeter or some other way to see if the signal is being sent to the Tactrix dongle?

Pics of my setup are below in case something is obviously out of place. In the pic with the 2.5mm mono plug, the pen is pointing to the part where the wire from ECU pin 79 is soldered.

I found my old DSMlink v1 ECU. I'm tempted to swap the 6 and 14 pins on the factory harness and use that.

Back of the OBD port
http://img.photobucket.com/albums/v16/jericho941/ECU Pics/20160406_104712_zps4brsrqcc.jpg

Tactrix Openport 2.0 Dongle attached to OBD
http://img.photobucket.com/albums/v16/jericho941/ECU Pics/20160406_104656_zpsx1rvig2s.jpg

Tactrix dongle
http://img.photobucket.com/albums/v16/jericho941/ECU Pics/20160406_104449_zpsoieesnjd.jpg

OBD port wiring
http://img.photobucket.com/albums/v16/jericho941/ECU Pics/20160406_104436_zpsgfzu7cye.jpg

ECU
http://img.photobucket.com/albums/v16/jericho941/ECU Pics/20160406_104424_zpslgbeoy70.jpg

2.5mm Plug
http://img.photobucket.com/albums/v16/jericho941/ECU Pics/20160406_104351_zpsk6cfpphm.jpg

Full view of harness and ECU
http://img.photobucket.com/albums/v16/jericho941/ECU Pics/20160406_104330_zpsjhsidpfn.jpg

2.5mm plug before soldering
http://img.photobucket.com/albums/v16/jericho941/ECU Pics/20160406_105428_zpsyq1mr0ab.jpg

I mainly used these threads for the wiring guides:
http://www.dsmtuners.com/threads/2g-ecu-in-1g-wiring.418334/
http://www.dsmtuners.com/threads/first-flashed-dsm-ecu-98-99-flashing-faq.338754/


As mentioned earlier, my OBD scanner works. I can view realtime RPM, read, and delete trouble codes. I also can get EvoScan to log.

When I use ECUflash, I follow the instructions as they are. Plug in dongle with connected USB cable, plug in 2.5mm plug, then turn key to ON.
 
Last edited:
I had the flash connector installed in the wrong pin. Swapped it to the correct spot and I was good to go.
 
Support Vendors who Support the DSM Community
Boosted Fabrication ECM Tuning ExtremePSI Fuel Injector Clinic Innovation Products Jacks Transmissions JNZ Tuning Kiggly Racing Morrison Fabrications MyMitsubishiStore.com RixRacing RockAuto RTM Racing STM Tuned

Latest posts

Build Thread Updates

Vendor Updates

Latest Classifieds

Back
Top