First wanted to start off apologizing if this was posted in the wrong place. I see there is a sticky, and read through most of it. However I didn't see my specific issue. The thread also hasn't been updated since Nov of last year. If need be, this can be merged into it. But figured I'd get more views as a stand-alone thread.

I'm getting a tune on Wednesday remotely, and it's been a mission trying to get a tune date worked out. So I feel as if I am short on time.

The issue:

Anytime I try pulling the ROM or anything on ECU-Flash, I get the following:

What I've tried:

• Uninstalling / Reinstalling software and drivers.
• Tried three different computers, Two Windows 10 machines, and one of them being Windows XP out of desperation
• Ensured cable is snug into the OBD II port as well as the Mitsu Reflash Cable

What is weird is Evo-Scan works perfectly fine with no issues.

Any ideas?


--------------------

Issue ending up being the Reflash Connector

 

From the log it looks like it is not receiving a response from the ECU. Make sure your battery is strong and charged, low voltage can cause connection problems. Also make sure everything is good with your flash connector.

 

Thanks for the response. Flash connector is brand new. I just put a CTEK charger on the battery, but I'm thinking it's not a voltage issue.

I should also note when attempting to connect, the PC (all PC's actually) make a USB-Disconnect sound, and re-connect sound. As if I was unplugging / re-plugging the USB.

 

Hi, check all your obd2 connector pins that there's not problems, test conductivity with a electrical tester, the logs says that the interface was closed because a time out this happens to me in a Subaru and the problem was with the pins

 

Thanks for the tip. Question though. If the OBD II connector pin was the issue, wouldn't this cause Evo-Scan to not work?

 

That sounds sketchy, the PC shouldn't be reloading the drivers like that. Might be defective hardware.

 

You welcome, depends on which pin fails can cause both Evoscan and Ecuflash to malfunction

 

Everything checks out fine. This has me completely stumped.

Any chance that a locked ECU that needs to be unlocked can be causing this?

 

Yes a locked ECU can be a issue too, if your obd2 connector its all fine the ECU for sure its locked, try with this unlocker:

https://www.aktivematrix.com/blog/ak...ix-useful-info

 

Thanks for the reply!

I went ahead and downloaded ECU-Flash unlocker. But I only get prompt with a splash page and no other options show up. How do I exactly unlock the ECU with it?

 

I also noticed when in the Device Manager, there is a "?" on the Tactrix Interface. Is this normal? Or could this in fact be a drivers issue? ( Which.. I've tried at least 3 different PC's. )

 

did you turn your key to pos. 2? lol

 

Going to pretend that wasn't asked lol

(yes, key was set to ON/just before start)

 

You said this is a new Tactrix Openport 2.0 device. I also see you have an Evo IX which is a non-CAN interface device.
Did you download the appropriate adapter?

The Tactrix site states a re-flash adapter is needed for Evo 9's

For Mitsubishi, you'll need the adapter for most pre CAN vehicles which include the 5-9 Evo.
Choose the adapter you need from the 'Reflash Adapters' drop down list on the right side of this page.

 

Find the instructions in the below link:

https://www.evolutionm.net/forums/ec...ml#post3695484