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.

1G Problems connecting with ECMLink V2.5

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

DSM IN MN

Supporting VIP
705
23
May 17, 2009
Wadena, Minnesota
A buddy picked up a '94 TSi AWD yesterday and it needs some slight adjustment. I was going to give it a try but I am having an issue getting connected. I have the correct cable and adapter. I have the key turned to the on position as well.

These are what I have downloaded:

Windows (complete install)
Windows (installer app)


Still no dice. Messages I get:


"COM1: Trying to connect
COM1: SerOpenPort failed: Port not valid
LOG MSG: Action raised exception"

i realize this could be many things. It seems though that my laptop doesn't register anything other than a COM4 port. I tried that and got nowhere. The laptop I am using is running Windows 7; if that helps any.


I understand I may be pretty vague, if so & more information is required just say so. Thanks!
 
Do you have a USB to serial adapter? I had a similar issue and it was because I didn't have the proper software installed for the USB to serial adapter and it would never connect.
From what I understand or can tell yes. There is an adapter that the had a green light that flashes. When plugged in it says it is being installed and checked or vise-versa.

I'm seriously starting to consider the fact that wiring may be the issue. This is because most of the gauges do not work (cluster), I get zero response from the radio (I just put in [pulled from my '94 Colt in which it worked not more than 10 hours ago]), and random wires like the cigarette lighter outlet factory wires get no power. All of which have good fuses in the under dash fuse box.

It's also a wonder how the guy who had it before my friend got to street tune it. This is why I think it is mostly user error.
 
I say Hunt down all the electrical gremlins, and fix them all, get a fsm wiring diagram of the dash wires and see if you can can get those gauges working right again, then if it still wont work, email tom at ecmlink and write him a detailed email of what is wrong, and he will help you out.

by hooking it up on the car with wiring issues etc. you might
have corrupt the data on the ecmlink module chip, if that is the case you will need to have the ecu, cable and module sent out to ecmlink to have it inspected and fixed.

if you have access to another dsm with no electrical issues, you can try and see if it will connect.
 
There is a problem with the older cables.

You can test it by grabbing a pair of vice grips or what ever and clamping down on the black box while trying to connect with the software.
 
I once removed the car door lock fuse underneath the dash trying to track down my slow battery drain. turns out that 10a fuse prevented me from connecting to LINK. some time after that i was having a hard time connecting link. i went directly to that fuse and it was blown. repalced it with a good fuse and it reconnected right away. since you said there's possibly wiring issues that's what i'm leaning towards.
 
I got my laptop connected to the ECU. As it was loading...different settings or whatever when you first connect to the ECU, I got the message "This ECU does not support direct, byte-level access." I am unsure what this means. Should I be concerned?
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top