The Central Hub for DSM Community and Information

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.

ECUflash Ecuflash Error - Can't Read

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

TurboTesh

Proven Member
83
4
Jun 9, 2016
Mukwonago, Wisconsin
I'm losing my mind trying to get my Ecuflash to read my '99 GSX. I read and wrote to it about a year ago, and now it won't do either. Same computer!
Here is the log:
You must be logged in to view this image or video.


Reflash connector is plugged in, tactrix cable lights up, drivers are updated. I uninstalled, reinstalled, etc... I thought it may be voltage, so I hooked up 12.2 volt source to the reflash pin and still no luck. Any ideas? I can't move along with my build until I can flash!

OBD readers work. I believe last I checked, i had evoscan working too. Windows 10.

Failure occurs at 7%, "Initializing kernel" and then times out.
A note: The laptop makes the sounds like a device being diconnected. Leads me to think driver/software... but I wouldn't know what else to use...
 

Attachments

You must be registered for see attachments list
Last edited:
I basically know nothing about this platform, but does anything show up in device manager? If the tatrix cable does show up, what is its status? That could help rule out a driver issue.
 
It shows up as a com 5 in device manager and says functioning properly.
It says connected at the bottom right of ecuflash as well.
 
I hate to say it, but it's likely your OP 2.0 cable is in need of repair. If you try logging with evoscan and you can't get a connection or have intermittent issues, this confirms that most likely. Try multiple versions of evoscan as well
 
I dont believe OP2.0 can log evoscan can it? I use a VAGcom blue cable for that.
 
I tried OP 2.0 to log EvoScan to no avail... The program recognizes the cable and starts to read, but spits back "Unable to communicate with ECU"

Checked:
OBDII Voltage at each pin
Grounds
Reflash Connector Pin
Drivers (Shows device connected and functioning)
Etc... etc..

I just get "Init Sequence 2" and failure in EcuFlash and EvoScan won't log or actuate. My Vagcom FTDI cable WILL log. My code reader connects as well.

I'm tinking it's the OpenPort2.0 at this point. I've been in contact with Tactrix and got nowhere before they closed out the ticket prior to resolution; I will be in contact again to try and get a refurb/replacement process going I suppose.

Anyone have any other ideas, or does it sound like the cable is at fault? My last check would be to try on someone else vehicle/software, but I don't know of anyone around.
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top