EcuFlash and Vista
Thread Starter
Evolved Member
iTrader: (4)
Joined: Dec 2006
Posts: 520
Likes: 0
From: San Antonio, TX
[15:30:51.918] Using interface OpenPort 1.3 Universal TX26apCv972db7c99d10f094ed94cac81eb2c9401a7d7459
[15:31:00.822] sending init sequence 1 (0001)
[15:31:04.089] sending init sequence 1 (0003)
[15:31:07.345] sending init sequence 1 (FFFF)
[15:31:10.089] no response to any known code
[15:31:10.091] interface close
[15:31:10.107] interface close
You can get that error when the tactrix open port driver is not recognized on the correct port. Go to device manager and check the port then match it in the software.
I also installed mine in a different directory than normal and it seems to work better.
c:\ecuflash in stead of c:\program files\openecu\ecuflash.......
Vista has some write protection on files located inside of the prog. files directory.
Uninstall reboot then re-install could fix as well.
I also installed mine in a different directory than normal and it seems to work better.
c:\ecuflash in stead of c:\program files\openecu\ecuflash.......
Vista has some write protection on files located inside of the prog. files directory.
Uninstall reboot then re-install could fix as well.
Thread Starter
Evolved Member
iTrader: (4)
Joined: Dec 2006
Posts: 520
Likes: 0
From: San Antonio, TX
So I uninstalled EcuFlash and reinstalled it. I now have another problem. When I try to read from the ECU, EcuFlash pops up with the window to select your vehicle, like normal. I select mine, click read and the program does not respond and freezes up. So I have to close the program and try it again. Same thing happens. I tried uninstalling and reinstalling, numerous times, in a different location and the same thing happens. Even after uninstalling and reinstalling, the date modiefied is the same as when I first downloaded the software. I can't figure it out. Can anyone help?
Trending Topics
I get the same problem. After selecting the vehicle type it hangs.
It did not happen with V1.34, only started happening with V1.35. Removed it and re-installed V1.34 and it works fine again.
It did not happen with V1.34, only started happening with V1.35. Removed it and re-installed V1.34 and it works fine again.
Thread Starter
Evolved Member
iTrader: (4)
Joined: Dec 2006
Posts: 520
Likes: 0
From: San Antonio, TX


