ECUflash Evoscan issue

[dannyd97gst]

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 endI know there is something stupid that I am missing like drivers or a compatability problem.

 

[knochgoon24]

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

 

[dannyd97gst]

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]

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]

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]

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]

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]

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]

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]

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]

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]

Is the dsmlink cable an openport cable?

 

[casperfast]

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?

 

[ziggo0]

so what was the other program you had to download?

x2 I'd like to know...more like I need to know. EvoScan 2.6 is not working with my 95, where is 2.5 barely stays connected for 1 ~ 5 seconds.

 

[the_mork]

Download ecuflash from openecu.org in order to be absolutely certain that you have drivers which are properly configured.

 

[ziggo0]

Before your suggestion I decided to give those a try this morning, still no change. If I reboot the laptop (fresh XP install/.net/etc) it seems to stay datalogging a bit longer but it just gets caught in the loop of logging 7 to 9 samples, disconnect...reconnect...7 to 9 more....disconnect, reconnect...sometimes it just loops in the disconnect/reconnect without even getting any samples. This is in 2.5v mind you. In 2.6v it connects and says no responce from ecu then disconnects, doesn't even get one sample. Sometimes it will go 'green' and throw a long line of random characters and disconnect. I'm not trying to log many things either, just wanting to get my fuel trims going.

 

[jeffo]

For the 1995/96 ECU's: have you tried lowering the baud rate to 10400?

 

[ziggo0]

For the 1995/96 ECU's: have you tried lowering the baud rate to 10400?

Hmm, I've tried making it higher from default for shits and giggles and that didn't change anything but I'll give that number a try.

Gonna add this in here for anyone to see in the morning, is there any way to get a higher sample rate than 5 samples a second? I'd killin meh.

 

[95Eclipse]

I'm having the same problem as ziggo0. I’m using the evoscan 2.6v on a 95 AWD Talon (w/Eprom) w/eBay 409.1 cable.
Cable is recognized, but when I start to log it gets caught up on the retry loop, check pic(1)…notice(Mitsubishi MUTIII selected).
At the end it loops again and again, I tried different baud rates 15625, 10400, 1953 and even 100 Doesn’t Work.
I than select “DSM/3000GT/Ecl. MUTovrOBDII” and get exactly what ziggo0 is getting even the going green thing except for one thing, no logging samples at all... It just connects and disconnects with the "No response from Vehicle Ecu" message before it loops... take a look at pic(2) I tried diff. baud rates too.
Is there something I'm doing wrong or is evoscan still not working properly for all 95’s?

Hey ziggo0, Did you get yours to work properly? if so, let us know how please.

Here’s what didn’t fit in the event log window on “pic2”:
All the stuff after “No response from Vehicle Ecu” doesn’t always show up, only when I stop the log exactly after it connects, otherwise it just loops over and over until it’s stopped.

Info: Initialize Vehicle ECU...
Info: DSM Initialize...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: DSM Connected.
Info: Connection successful...
Error: No Response from Vehicle ECU
at #=qxhKYH1mFtMAh8z93zD7prqWQvv2_OfgSnHCmz2Zy3v0=.#=q4wG$BmytYsscBYbM0CQyd6dVRjbyQzgv1$pYSJHpgoA=(Int32 #=qSmYp_2_Xyy$V9QRSo0fSww==, Int32 #=qWvQwf1OY$GAyrAUDgi9A_6Fryk2D5cpro3$tGG7lzAw=)
at #=qxhKYH1mFtMAh8z93zD7prqWQvv2_OfgSnHCmz2Zy3v0=.#=qgPjsDP_xx5oij7gGqW7v3w==(Int32 #=q6DqTuA5PV1$pWADoW8iuYw==, Int32 #=q06iGv8jbiegxletYYJ2Zfprz4wFBu8dHyQ_LAuSG$kU=)
at #=qcYTi9Xx62Q46MlRsGjuPN1obrQTs8A5PdOAFjpb$dxs=.#=qcdl0rnAUma_98f$ksRzQrA==(Boolean #=qIIIQIoNWCY0W3ObcSCY5A8g48TQbJ2x4KFtJCu_3jH8=, String #=qdlx8tN28mG6zvxtZKbZXmw==, Boolean #=qHDhEvCFQv_V0O1oZAa5jUVrwieg057naUpvwjsJ9dz0=, Int32 #=qFWAUDcQAn9jFGwkqDMJZJA==)
at #=qcYTi9Xx62Q46MlRsGjuPN1obrQTs8A5PdOAFjpb$dxs=.#=qI2Bxs8jh5r0BxamKtYJJTA==()
Info: Datalogger Ended.

 

[jeffo]

The MUT-over-OBDII is broken in v2.6. You need to run v2.5 for now, unless he has fixed it in v2.7.

 

[95Eclipse]

The MUT-over-OBDII is broken in v2.6. You need to run v2.5 for now, unless he has fixed it in v2.7.

ziggo0 (from some posts back) was running V2.5 and was having trouble, with it too, maybe I'll have better luck, Where Do I get v2.5 from limitless website? On v2.5 which do I select Mitsubishi MUTIII or DSM/3000GT?
I can't wait to get this thing logging.

 

[kiddsm95]

Does anyone know what fuel trim (cruise & idle) request ID's to use in V2.6 or V2.7? I know there are a few of us on the board that can not log LTFT & STFT, or the reading just stays at ".1008" and never changes. This makes scaling injectors extremely difficult!

Is it possible we are using the wrong Req ID's in EvoScan, or is there another issue going on here?

 

[95Eclipse]

I just contacted limitless asking for v2.5 release, but he didn't even mention v2.5, instead he gave this to try,
"Evoscan 2.7 (FULL Final BETA)" so I'm going to be trying that one and I'll post back to let you Know if it works on my '95 Eagle talon.

 

[kiddsm95]

I've been running V2.6 for a few months now, and switched over to V2.7 about 2-3 weeks ago. Still can't log fuel trims.

Does anyone know if the EvoScan request ID's for 95-96 & 97-99 are different? I have noticed that those of us running H8 ECU's in our 95's are having this issue.

Any help would be appreciated.

 

[diambo4life]

I just contacted limitless asking for v2.5 release, but he didn't even mention v2.5, instead he gave this to try,
"Evoscan 2.7 (FULL Final BETA)" so I'm going to be trying that one and I'll post back to let you Know if it works on my '95 Eagle talon.

I had tons of issues when I tried to use V2.7 on the EVO VIII I was tuning. D'led 2.6 and it worked perfectly.