So I take it your error went away after cable installation?

 

Yes.

I didn't have to reinstall the software. All I had to do is plug the cable in.

Therefor - I'm assuming the cable provides some type of feedback that lets the application know that it's there.

 

i love this thread, saved the night tonight!

 

Ive done everything in this thread and I still get the FTD error. I have a Tactrix 2.0 cable, tried all the solutions in the posts, still get the error and EvoScan doesnt work or Show CEL codes, and gives me the same error as ECUflash. Any thoughts?

 

I ended up figuring mine out, for future reference if anyone else has the same problem, I had to manually download the FTD....DLL file from a search on the internet. Just make sure you save the file to the desktop, and scan it a few times with whatever virus blocker/malware program you have to make sure its clean. Moved the DLL file from the desktop to SYS32 folder in the C drive, and I no longer have the error code on ECUflash.

On the other hand though, I just found out that the previous owner of my Evo got the OP2.0 cable instead of the OP1.3U cable I need to check my EFI/ABS codes....Sweet.

 

Experienced the exact problem and followed the steps you mentioned, worked like a charm. Thanks mate !

 

hello my bro...link die plse