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.

2G EcuFlash Can't Read/Write or even detect ECU.

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

Heavyslowfwd

Probationary Member
1
0
Jul 25, 2015
Central, Alabama
So I've had my OP 2.0 cable for a while, and finally got all my exhaust leaks tracked down to start tuning. I plugged in both the mitsu reflash connector as well as the 2.0 into their respective slots and plugged the usb into my laptop and the drivers attempted to download but failed. I then installed the drivers from the usb drivers folder and my laptop said the cable was functioning correctly.

When I opened up ecuflash, it ran through a long code that seemed to repeat the same 5 lines over and over. It looks similar to the OP's log in this thread: http://www.dsmtuners.com/threads/cant-read-write-in-ecuflash-evo-8-ecu-swap.451588/ except it loads the API, the DLL, version, then my device serial number and says interface close. It does these same lines ~6 times until it just stops.

In the top left menu, I have no options pertaining to the ecu, just a Open Rom, Vehicle Select, and Others that I cant remember (Dont have my laptop with me right now, going on memory but it was 4 options total).

Anyway, I AM able to log in evoscan and the data transfers and appears fine, which makes me think the drivers are installed properly for the cable. So I think my problem is with the reflash connector not making a good connection or does it need a separate set of drivers?

Any insights?
 
Last edited:
Definitely redownload and reinstall the drivers before looking elsewhere for other issues. The 2.0 cable is an unfortunately very 'touchy' and 'fragile,' however sometimes something as dumb as wiggling it around and reconnecting the cable can solve connectivity issues. Outside of that be sure you have the proper settings to read the ecu etc. I can't tell from your original post if you are trying to read or write though, and if you are having issues with reading then you may need to be sure that you have the proper rom and hex file definitions in the proper folder (you HAVE to manually place them there being that this is opensource stuff). Good luck
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top