DSMTalk Forums: Mitsubishi Eclipse, Plymouth Laser, and Eagle Talon Forum banner
1 - 20 of 21 Posts

paec311

· Banned
Joined
·
31 Posts
Discussion starter · #1 ·
I know there are a couple threads on the dsmlink forum already started with this issue, but I couldn't any specific recommendations to solve it.

Basically, it is trying to connect (the light goes from yellow to red, back and forth) and then I get an error message "IO failed: Command timed out". I had no problem connecting for the past week, since I've had the software running, and then all of the sudden I get this issue.

I tried adding the following to my dsmlink pref:

interByteDelayMillis=40
interCommandDelayMillis=40
cmdReplyTimeoutMillis=1000

but the same problem occurred. I'm using a Keyspan usb/db9 adaptor, and again had no problems when I first had the eprom/socket done. What route can I take to further resolve this issue? Thanks in advance.
 
Discussion starter · #3 ·
Thanks for the advice budget90

Through DSMlink it was set on COM10. I checked in my Keyspan settings and it has port COM4. There is no COM4 through DSMlink; in which I tried COM3 (the lowest port available) and each usb port on my laptop and still nothing...

I was going through the DSMlink forum, and read that it could be a bad connection w/the cable that came w/the program?? I'm not sure what else to diagnose for as there were not too many other topics on this issue.
 
scottsee said:
open dsmlink.prefs file located in c:\program files\dsmlink

Edit with notepad and add:
portIDForce = COM4

Sorry for bumping an old thread.

I am having trouble connecting my DSM Link. I have had it connected before. The only comm port I have in the drop down menu is COM1. I tried to add the COM4 as described but it did not work. Do I add it at the bottom of the prefs, under the COM1, or just replace COM1 with COM4?
 
Depends on which com port your Serial or USB is.

Go to your hardware devices and find out which port it is you want to use and then force that specific one.
 
I'm not sure if thats your problem. You shouldn't have to force anything. Check if your hardware (connector) is properly installed, if its being recognized by your OS, if its connected well to the diagnostic port and if your ign. key is in the on position.
 
Then you need to figure out what is using your com 1 port. Is it serial or USB? I would assume serial since you only have one port.
 
What cable are you using? The provided DB9 cable or the cable with a DB9 to USB converter?

Did you install the drivers for the converter and under what COM port?
 
I just went out and tried connecting again and got nothing. I am not using a usb adapter. Just plugging straight in to the computer (serial port). Once I connect the cable I try F11 and on line under the ECU toolbar. It says timed out for both.
 
What type of adapter are you using? Do you have the proper drivers for it installed? If so - you should see under device manager the name of the adapter and to what port its supposed to be on.

If DSMLINK doesn't show that port in the drop-down menu, try restarting the computer, and see what happens.
 
LatDSM said:
What type of adapter are you using? Do you have the proper drivers for it installed? If so - you should see under device manager the name of the adapter and to what port its supposed to be on.

If DSMLINK doesn't show that port in the drop-down menu, try restarting the computer, and see what happens.
Yeah, everything is installed properly. I just used it about 2.5-3 weeks ago. COM1 is the only thing on the drop-down menu and it is under device manager on my laptop as stated in a previous post.
 
LatDSM said:
What type of adapter are you using? Do you have the proper drivers for it installed? If so - you should see under device manager the name of the adapter and to what port its supposed to be on.

If DSMLINK doesn't show that port in the drop-down menu, try restarting the computer, and see what happens.
It doesnt sound like he is using an adapter.. he is just connecting the db9 to the serial port on the computer. Therefore, he should be connecting via COM1, right?
 
If you have not solved this problem, while I dont have a dsmlink, I am a cerified network tech.

You issue is that serial interfaces are legacy technology (OLD and less FLEXIBLE). If it were truly a USB interface through and through, the USB API would handle that for you. That may have been gibberish to some, but OH WELL.

Anyhow, it doesnt matter which COM the dsmlink is on or the USB port is set to, so long as they are both the SAME. If setting the above value in the .dll file did not work, it is:
A) because that is not the port DSMLINK wants to communicate on, or
B) Yo shit is FUCKED UP!

To fix this, simply do this in vista (very similer in XP, but Im not a fucking GeekSquad employee, so use Google)

Hit the windows key or orb (start menu or windows key in XP)
go to "control panel"
go to device manager (called system bleh bleh bleh in XP, and has a tab labled "hardware" which contains a button labeled "device manager")
Eyeball the PORTS section of the tree display
the port you want will be listed, and without having to click on any particular one, should say (COM##) next to it

edit the dsmlink.prefs file as state before using the com## you saw in the device manager

You should be good to go, but if not, restart; legacy hardware often times requires a restart for changes to take effect. (windows 95/98 anyone?)
 
1 - 20 of 21 Posts