EVOscan EVOScan settings with Tactrix 2.0?

[ditchmagnet]

I have a 99 flashable ECU installed, and I a 2.0 cable. I just bought EVOScan, and I am trying to figure out what settings I need to log correctly.


I choose to use openport 2.0, and Mitsubishi/MUTIII but I keep just getting disconnects, and then it reconnects.

If I try choosing DSM it just hangs and never connects.

I thought I read about changing some settings for this situation, but I can't find the answers.

Please help!

Thanks.

I just tried setting the Engine setting to 2byte, and the RPM to 2byte, but that didn't fix it.

It is frustrating cause I can't get any logs. Evo scan will report 21hp, and then 510hp, so I know it is loosing connection even when I do not look at it.

Even if I just sit idle and watch it, it will just disconnect and reconnect.

I'm going to try a different USB cable now.

Please give me suggestions.

 

[jukematt]

I was searching for something else and came across this thread. Did you figure things out yet?

If not:

What version of EvoScan are you using?

What cable are you using to log?

 

[ZombieSix]

2.7 muttIII works for me.
choosing dsm never connects

 

[ed1380]

This is how mine has always been. From v2.5 to 2.8


I had a problem with it not connecting in the 97, and the problem was a bad connection. Jiggling it fixed it.

 

[ditchmagnet]

Mine will still disconnect. I try on v 2.8 and 2.9. I am using the 2.0 cable right now. I switched USB cables and it doesn't disconnect as often. I bought an $8 vagcom on ebay, but I haven't tried it yet. I will post back after a do some logging with it.

I am using the same settings as pictured above. I have flashed a ton of times already and no issues there.

 

[ed1380]

Have you tried a different usb port?

 

[ditchmagnet]

Yes, I did, and I tried a different laptop, but it does the same thing. I know a lot of people don't like to log with the 2.0, but I didn't know if this was why.

Also, the sample rate will slowly drop till it disconnects and reconnects. I think it starts at a little over 100 samples a second, then it drops to the 70s, and I think lower if I remember right, then it disconnects.

I will be trying out the vagcom cable later today.

 

[ditchmagnet]

I am trying to get the vagcom cable to work with evoscan, but it wont detect it.

I am trying to use the tactrix drivers when I install the cable, but there are different choices.

Can someone tell me exactly what driver to use for the vagcom?

 

[97ebaygst]

im pretty sure when u download ecuflash it downloads the proper driversfor the cable

 

[ditchmagnet]

Yes, in the ecuflash folder there is a drivers folder, but it has a few different ones. I have tried a few, but I can't get it to work.

There is FTDIbus, and FTDIport, and Tactrix 2.0.

Then within those, I have to pick if it if openport 1.3 Mitsubishi, subaru, universal, or just USB serial.

I have tried on two different computers, and evoscan 2.8 and 2.9. Maybe I just have a bad cable, I don't know. I can make it use any driver, it is just that evoscan is unable to communicate with the cable.

 

[ed1380]

Try an older version like 2.5. I just switched to 2.8. I dont have too much faith in it. If not then I would start suspecting hardware problems

 

[ditchmagnet]

I just recently bought the software, and my key only works on 2.7+

 

[MY1GDSM]

I'm not sure why everone had these issues, I don't...
Maybe once or twice the op2.0 has disconnected. But, the cable gettign bumped was more then likely the reason.

Though I mainly use it for flashing not logging... .

Anyone using a cable other then a OP Click here you can find the right drivers for your system. Then just pick OP 1.3 in newer versions of Evoscan

I just recently bought the software, and my key only works on 2.7+

Click Here they will email you a number that will work for older versions

 

[ditchmagnet]

Well, I tried 2.5, and I tried the drivers you linked, but I just still can't get EvoScan to see it.

Oh well. Guess the cable I bought just isn't compatible for some reason.

I will try a different USB cable with the 2.0 for now and see if it helps.

EDIT:
Actually, is there still a place to get MHIscan? I am just curious if this 409.1 cable will work with it.

And this is the vag-com cable I had bought:

http://www.ebay.com/itm/ws/eBayISAP...sspagename=STRK:MEWNX:IT&orig_cvip=true&rt=nc

 

[GSXDNA]

Sell your 2.0 cable and get a 1.3 or 1.3U. I've had my 1.3 for like 7 years, never had a problem connecting to any OBD-II EVO or DSM. They were only $25 on ebay back then

 

[ed1380]

try this program. I've also used it with the 2.0 cable.

Mut Monitor V1.9 Release 31/1/2009 - evolutionm.net

 

[ditchmagnet]

Sell your 2.0 cable and get a 1.3 or 1.3U. I've had my 1.3 for like 7 years, never had a problem connecting to any OBD-II Evo or DSM.

I need the 2.0 for flashing my H8

try this program. I've also used it with the 2.0 cable.

Mut Monitor V1.9 Release 31/1/2009 - evolutionm.net

Can't find any working mutmonitor download links.

EDIT:

I found a link for Mutmonitor 1.3. It will detect my 2.0 cable, but not the 409.1 cable. I really think the cable is just no good.

 

[ed1380]

pm me your email and I'll send it to you

 

[GSXDNA]

I need the 2.0 for flashing my H8.

Bummer.