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 RTM Racing
Please Support STM Tuned

ECMlink connectivity problem RESOLVED

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.

gsxitement

20+ Year Contributor
1,887
1,665
Dec 9, 2002
DOBBS FERRY, New_York
I've been doing a wiring delete on my track only time trial car. Got the car fired up yesterday. Runs ok. My problem is link won't connect. At my DLC, I have 12v on pin 16, 5v on pin 1, pins 4 and 5 show good ground, and I've got good continuity through the pink data wire on pin 7 to the ECU. I get a "port refused to accept required bitrate" message. Also, my little pocket scanner won't connect either. I can't see the ECU being bad cause it just sat in my house while I did this work. I will add, that everything is custom. My own fusebox, my own relays. The MFI relay and fuel pump relay are controlled by switches on the dash panel. Any insight or recommendations would be appreciated. Thanks again.
You must be logged in to view this image or video.
 
For some reason its not receiving the handshake back from the ecu to prove that a connection has been made, what ecu are you using?
 
For some reason its not receiving the handshake back from the ecu to prove that a connection has been made, what ecu are you using?

The same ECU I've been using for 9 years. Worked fine at NJMP in August. Got the car home and started the wiring project in October. ECU just sat in the house until last month when we started routing wiring.
 
For some reason its not receiving a handshake back from the ecu to prove that a connection has been made between them, what about pin 15? thats the low data line, also pin 16 is battery positive, not switched ignition if thats what you have running to it.
 
For some reason its not receiving a handshake back from the ecu to prove that a connection has been made between them, what about pin 15? thats the low data line, also pin 16 is battery positive, not switched ignition if thats what you have running to it.


Ahhh....pin 15 isn't hooked up. That's gotta be it. That's crazy cause in all my research no one mentioned Pin 15 at all. Even when I look at the wiring diagrams. I'll have to look into that when I get home from work. Pin 16 is hooked up to my fuse box. Being that it's track only, when I turn the master switch on, it's sending power to that fuse box and anything that's not on a switch or relay gets powered up.
 
For some reason its not receiving a handshake back from the ecu to prove that a connection has been made between them, what about pin 15? thats the low data line, also pin 16 is battery positive, not switched ignition if thats what you have running to it.


Off the link website
You must be logged in to view this image or video.
 
My point is that you need data on two lines, high and low depending on which protocol your using will tell you which two pins on the obd connector to use, it looks like pin 56 on the ecu is the request line that your not using maybe? the picture below is just to reference that two lines are needed, not necessarily your own obd connector, if I seem to be babbling ignore me, I woke up early on just a few hours of sleep after having a root canal yesterday so I might be slightly out of my mind.

obd-png.575663
 
Last edited:
My point is that you need data on two lines, high and low depending on which protocol your using will tell you which two pins on the obd connector to use, it looks like pin 56 on the ecu is the request line that your not using maybe? the picture below is just to reference that two lines are needed, not necessarily your own obd connector, if I seem to be babbling ignore me, I woke up early on just a few hours of sleep after having a root canal yesterday so I might be slightly out of my mind.

obd-png.575663

Lol!! That's brutal. Root canal sucks. And I'll take any direction I can to save the ECU from being bad which I don't think it is. I'll definitely look more into that pin when I get home. I'm not gonna run the car again till I get this sorted. Really appreciate the info. Was kinda in the dark seeing as how the car runs, but won't communicate with anything. Hoping it's something dumb.
 
My point is that you need data on two lines, high and low depending on which protocol your using will tell you which two pins on the obd connector to use, it looks like pin 56 on the ecu is the request line that your not using maybe? the picture below is just to reference that two lines are needed, not necessarily your own obd connector, if I seem to be babbling ignore me, I woke up early on just a few hours of sleep after having a root canal yesterday so I might be slightly out of my mind.

obd-png.575663


You know what? I think the pinouts you mentioned don't apply to me since I'm on a 95 ECU.
 
Ive seen this message when the drivers need to be updated, but if your pocket scanner is doing the same thing then its unlikely. Only time Ive ever seen it though.
 
Thanks for following up with the solution. Now if anyone else has this issue, you guys are ones that figured it out. That is what is so great about this forum! :thumb:
 
Thanks for following up with the solution. Now if anyone else has this issue, you guys are ones that figured it out. That is what is so great about this forum! :thumb:


Absolutely. The combined experience of everyone on here is such a deep well of knowledge. Hope it helps someone in the future.
 
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