Here's what shows up in the log box when Evoscan disconnects from the USB cable abruptly. I'm using the universal 1.3u cable BTW.

Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: Waiting for INIT Response...
Info: ECU ID: E4C1
Info: Connection successful...
Error: Write command error. FT_Status = 4
Info: Datalogger Ended.


I have submitted a ticket to limitless, but Hamish never responded. Anyone dealt with this before? Have any ideas or solutions? Thanks.

Usually taking it out and plugging it back in will provide a temp. fix, but sure enough it'll happen again.

 

FT_STATUS = public enum(
OK = 0,
INVALID_HANDLE,
DEVICE_NOT_FOUND,
DEVICE_NOT_OPENED,
IO_ERROR,<--------------------------------------------------- 4
INSUFFICIENT_RESOURCES,
INVALID_PARAMETER,
INVALID_BAUD_RATE,
DEVICE_NOT_OPENED_FOR_ERASE,
DEVICE_NOT_OPENED_FOR_WRITE,
FAILED_TO_WRITE_DEVICE,
EEPROM_READ_FAILED,
EEPROM_WRITE_FAILED,
EEPROM_ERASE_FAILED,
EEPROM_NOT_PRESENT,
EEPROM_NOT_PROGRAMMED,
INVALID_ARGS,
OTHER_ERROR);

I would say it is bad soldering/cut wire somewhere.

 

mine started to do the same thing. i havent flashed or logged in a while and when i tried to log, it was connecting to the ecu and says "link engaged" then instantly says "link disengaged" and disconnects. i can still flash the ecu but cannot log.

 

yea mine just chooses when it want to work lol but usualy it says usb not connected or something like that even tho it is and its a new comp

 

me too. although one day it worked like nothing had ever happened, but now its doing the quick two step again.


it may be linked to my upgrading to ecuflash 1.4xxx?

 

I realize this is an old thread but I'm having the exact same problem. It's 98% of the time when I go WOT for more than 2 seconds or so. Same fix - unplug USB, close EvoScan, plug in USB, restart EvoScan & log again. Was there ever a solution to this?

 

Sorry for reviving this thread but I have been having this problem for over a year and thought it was a ****ty laptop. I just got a brand new one and it still happens. Could it be cable related? Anyone have any ideas?

 

I know with newer evoscan updates you will need a better processor laptop

 

Can't be my laptop. It's a Samsung Series 5 with an I3 processor and 4GB of RAM.