So i recently got a limitless 1.3 universal cable so i can tune both my subaru and evo with the same hardware. However, when i connect the cable to my evo the anti-lock light in the cluster flashes at me at idle

also when i go to log (evoscan 2.5 on vista), it will connect and log for about 30 seconds then it will drop the connection and the error "FTDI error-4" pops up. this same logging issue pops up when i log my subaru.


flashing with the cable is not a problem on either car (ecuflash 1.38)

any ideas?

fyi I logged a support ticket on the limitless website and have not gotten a reply, its been almost two weeks.

my tactrix 1.3 mitsu-only cable works flawlessly

 

tried reinstalling the drivers, same thing happened.


has anyone else had this problem?

is anyone else even using the 1.3U cable?

 

i have that exact same cable and never had an issue.

weird!

 

When I log with my tactrix on my 3000GT with EvoScan, I know there is something about the flashing ABS light meaning that the ECU is in diagnostic mode and ready to receive connections.

Once you flash or start logging with it connected, does it stop flashing?

 

it flashes normal, but if i try to log it will start logging, then drop the connection after about 20-30 seconds

 

Does the one you sold me do the same thing? or is mine the mitsu only???!?!

 

lol, no you're good. i never had this problem wit the cable you have now.

 

bump. any else have any ideas?

 

In EvoScan, there's a menu (Alarms, Logging, or maybe Gauges & Dashboards) that has an option that says "Disable Dashboard Indicators" or something like that.

 

1. try another laptop, could be a cpu timing thing
2. try a friends cable
3. try uninstalling and reinstall latest evoscan with defaults
4. only log TPS, to be sure it stays connected.
5. try a replacement cable www.evoscan.org/helpdesk send yours back.

 

As far as I know, in Mitsubishi's the anti-lock light will always flash when a scanning/logging cable is connected. Mine does it as well and I've had no issues logging, flashing, or scanning (1.3M).

Unhook the cable and it goes away

It will flash whenever you aren't moving.

 

well i upgraded to v2.6 beta 11 and the issue got better, but not fixed. it now will log for approx 5 minutes on the first try, if i try to start a new log session i get the same issue.

if i unplug the cable and then plug it back in i can log again.

im also getting a new error in addition to the one posted above. "write command error FT_status=4"

ill try another laptop when i can get my hands on one

 

weird, my 1.3m cable never did this

 

You can also try going to the device manager and removing all of the drivers for the FTDI/tactrix cable (there are a few of them, look very thouroughly). There is an option to show hidden/unplugged drivers that you will need to check if your cable is not plugged in, but it may be good to use it to make sure there isn't more than one driver installed.

After you have removed all of the drivers and BEFORE plugging in the cable again reboot. Then reinstall the drivers. There is a sub folder for evoscan and ecuflash that has them or (recommended) you can download a fresh copy of ecuflash and install it.

 

I'm having the exact same problem and have tried just about everything. I have lodged 2 support tickets but still no reply.

Did this problem ever get solved. I'm thinking about buying another cable but it's to much for something that will just screw up again.

Any help?