Hey Guys/Girls,

I've searched and searched but still can't find any solutions to my problem.

i have tried both mistulogger and evoscan and both seem to have the same problem occurring. I am able to connect to the scanner when my engine is off and it will stay connected fine. As soon as i turn the engine on it will either work for about 3 seconds then disconnect or just disconnect straight away. I have also tried connecting to evoscan with the engine already running but this doesn't help either.

When evoscan has disconnected once it looses the ability to find the tactrix 1.3u cable. The solution has been to swap to a different com port but this hasn't helped the disconnecting issue. below is the error that is given when it disconnects.

Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: Waiting for INIT Response...
Info: ECU ID: E4B5
Info: Connection successful...
Error: ML Write command error. (FT_Status: 4)
at #=qcYTi9Xx62Q46MlRsGjuPN1obrQTs8A5PdOAFjpb$dxs=.#= qWI1iCxyK3S3lwUZt78q$wA==(String #=qfYtdU1te8HdvgUixlJO_HQ==)
at #=qcYTi9Xx62Q46MlRsGjuPN1obrQTs8A5PdOAFjpb$dxs=.#= qI2Bxs8jh5r0BxamKtYJJTA==()
Info: Datalogger Ended.


There was another error too which was FDTI error 4.
How do i fix this problem. I'm really keen on logging but i'm getting turned off by the unreliability of evoscan.

 

I had this same
problem but the reason was cause a newer version came out and that old one didn't work. Do u have version 2.6. If not u might have to download the newest one or uninstall and then install again. That's all I got man

 

First off, I have been using EvoScan for MULTI yeah (since it came out) and I have never had any connection/logging problems.

Next, can you use ECUflash? If so, try uninstall Evoscan (make sure delete the Evoscan folder and to restart your computer after uninstall), then reinstall Evoscan.

If you cant use ECUflash, uninstall everything (evoscan, ecuflash and the tactrix drivers), make sure to delete all the pertaining folders and instances of those programs/drivers. Restart, then reinstall ECUflash. then plug in cable and install the drivers. then check to see if ECUflsah and the cable drivers are working. If so, then proceed to install evoscan.

 

I have tried all of this but nothing changes. Whats interesting is that i am able to read the ECU on one laptop but unable to see the parameters oh the other when using ecuflash. Even when i add the same XML file to each rommett data file. WTF

I'm getting ready to burn this cable. Is the 2.0 any better?

 

Have you went to the evoscan website and submitted a support ticket?? Hamish is really helpful and responds in a timely manner.

and NO the 2.0 isnt better, if you have an Evo 7-9

and you have .xml problem with ecuflash, probably from you messing with stuff.

Uninstall and delete everything, clean registry, restart and reinstall everything.

 

I've sent him 2 support tickets and even an email to his hotmail account but havent heard anything for a week. maybe he's away on holidays or something. I guess i'll be patient... what else can i do

 

This is what I would do. It works for me as well.

 

Any update to this? I'm getting the same error.

 

what version of evoscan are you using? have you tried v2.5?
v2.5 seems to be the best version for me.


are you using some sort of wideband o2 sensor?
for a few days i had problems trying to log if i was connected to my wideband


have you tried revo uninstaller?
google that and try it out. i was having all sorts of problems with just about every version of evoscan acting up when connected to my AEM UEGO. finally i downloaded revo and used it to completely wipe evoscan from my computer. I reinstalled evoscan v2.5 and everything works flawlessly to include the AEM UEGO.

 

Woah - sweet dude, thanks for all the info. Yes, I am trying to use my UEGO too, but I'm not sure if I have always had it connected. Right now I'm trying Mitsulogger to see if I can isolate the issue to evoscan. I'll probably go back to 2.5 (using 2.6 currently if it IS an evoscan problem). I'll let you know what happens - Thanks again for your input!

 

v2.6 definitely will not work with UEGO. i think there are a few rare cases of it working.

a lot of people have had success with v2.7 beta 5 upgrade, however i did not.

but yes, try to log without the UEGO hooked up and see if it'll atleast log without it.