Evoscan issue

dannyd97gst · 10-23-2009, 10:42 AM

At the risk of coming across as a complete idiot here goes.
Bought evoscan and a vagcom cable (cheap I know) but when connected to my car I get " Openport 1.3 cable not responding, perhaps try 2.0 if you have that". Now this occurs whether the car is connected or not. When I try the openport 2.0 connection I get " Openport 2.0 cable not responding, unplug the cable and try again"
I suspected my vag com cable was no good (Cheap E-bay crap) so I ordered the cable that evoscan recommended ($57) and I still get the same failures.
I've somewhat been in contact with the folks at Evoscan but they want me to download some kind of instant messenger for live tech support. Problem with that is my laptop has no internet connection.
Surely I'm not the only one who has this problem, any ideas?
I am at my wits end

I know there is something stupid that I am missing like drivers or a compatability problem.

knochgoon24 · 10-23-2009, 02:01 PM

Have you tried downloading the FTDI drivers? You need those.

dannyd97gst · 10-23-2009, 02:23 PM

Quote:

Originally Posted by knochgoon24

Have you tried downloading the FTDI drivers? You need those.

I'm not sure.
I am using windows xp. I've google'ed ftdi drivers and clicked on the first website. Virtual COM Port Drivers
I am far from a computer wizard but it looks as though I would want the 2.04.16 driver version. I hope that is all that is wrong.

dannyd97gst · 10-26-2009, 05:44 AM

Ok the ftdi drivers I downloaded worked great, must have had the wrong driver's the first time. Evoscan now keeps "trying" to get a response from the ECU so now we have round 2 of the problems. Just wanted to keep anyone up to date, I will continue trying to figure this problem out in the event someone else runs into this issue.

jeff24680 · 10-26-2009, 06:01 AM

Well, I'm sure you've have tried this already but I might as a well ask.

1 - Have you tried to connect with the car in accessory mode as well as running?
2 - What type of protocol are you using from with evoscan i.e. MUTII, OBDII, etc
3 - Baud Rate?
4 - ECU Type
The top left corner of main page is where you find all these settings,

These are the settings that I use with no problems:

BaudRate = 15625
Timeout = 1000
I have OpenPort 1.3x Selected
Protocol = Mitsubishi MUTIII
ECU = EFI

nytescion · 10-26-2009, 06:08 AM

I had this same issue with version do you have. They had me download 2.6 I believe and then they had me DL another program to "configure" the wire. Thats what they called it. I can let you know what the program was when i get home (or you can email them and they'll tell you). but after that all was good.

dannyd97gst · 10-26-2009, 12:14 PM

Quote:

Originally Posted by jeff24680

Well, I'm sure you've have tried this already but I might as a well ask.

1 - Have you tried to connect with the car in accessory mode as well as running?
2 - What type of protocol are you using from with evoscan i.e. MUTII, OBDII, etc
3 - Baud Rate?
4 - ECU Type
The top left corner of main page is where you find all these settings,

These are the settings that I use with no problems:

BaudRate = 15625
Timeout = 1000
I have OpenPort 1.3x Selected
Protocol = Mitsubishi MUTIII
ECU = EFI

Thanks.
1. Yes, tried checking dtc's and a few actuator tests. "Waiting for ECU"
2. DSM
3. Not sure but 15625 looks familiar
4. EFI
I am using OpenPort 1.3.
I was too excited to finaly get the cable to connect to even care about anything else. So I will have to play with the options again tonight when I get off of work.

jeff24680 · 10-26-2009, 12:27 PM

I am not 100% sure because you are 97 and not sure what year your car was actually produced in but you should be using "Mitsubishi MUTIII" as your protocol type, I tried the "DSM/3000GT/Ecl. MUTovrOBDII" and it did not work for me.

This is the cable I am using currently

http://www.dsmchips.com/viewproduct.php?id=22

Ceddy · 10-26-2009, 04:44 PM

If you have a 97 ecu use MutIII for the protocol.
And have 1.3 Cable selected.

You shouldn't need to change anything else.

LimitLess should give you some tech support since you bought their software and cable. They usually take a day to reply to a support ticket.

the_mork · 10-26-2009, 05:07 PM

For anyone else who has trouble with evoscan in the future and has driver issues the easiest way to take care of drivers is to download ecuflash. Whether or not you plan on flashing your car or have that ability ecuflash comes bundled with the drivers that you will need in order to run the cable, if you feel a bit more tech savvy then you can just get the drivers on your own.

dannyd97gst · 10-29-2009, 05:25 AM

Ok it's been raining here the last 2-3 days but last night there was no rain. Went out to the old car with the lap top set on MUTIII and bada bing bada boom we had connectivity.
So far as I can tell EvoScan is the bomb and now soft mods can commence.
Special thanks to knoch, jeff, and ceddy. A pre thanks for anyone else downloading EvoScan to mork.

saechao04 · 11-04-2009, 02:47 AM

Is the dsmlink cable an openport cable?

casperfast · 11-04-2009, 11:14 AM

Quote:

Originally Posted by nytescion

I had this same issue with version do you have. They had me download 2.6 I believe and then they had me DL another program to "configure" the wire. Thats what they called it. I can let you know what the program was when i get home (or you can email them and they'll tell you). but after that all was good.

so what was the other program you had to download?