That didnt work for me because everytime I plugged the cable in it said it found new hardware and I had to download new drivers.

 

Yeah, no email back from tactrix yet either. I tried all the above suggested fixes, except re-serializing the cable. I only use this computer for the car, so I'm going to go to it's last restore date and give that a try. I have nothing else to loose I guess..

 

Update..I deleted/uninstalled every single ftdi/ecuflash/tactrix or openport item I could find on my computer. I restarted and downloaded 1.42 again. It said it sucessfully installed the openport drivers..3 of them. Now when I plug my 1.3m cable into the comp. for the first time it can't even load the driver. I select the specific location for it to look for the driver and I get an error that says "Driver not intended for this platform". I'm running a pos toshiba satellite w/vista. Nothing special. Anyone else have this problem? Or a solution?

 

I switched from 1.34 to 1.42 about a month ago and I still can't get it to connect to my ECU. Evo Scan works just fine. I've got the 1.3 cable with the single wire coming off of it. I've deleted and installed almost every version out there and still can't seem to get it to work. Let me know what you guys figure out.

 

I think Ben and I ironed it out. I think somehow the cable "lost" it's serial number. I noticed when trying to connect, the serial number had like 30 zero's after the first couple letters. Ben tried it on his car, same problem. He used his cable on mine and connected fine, so we ruled out the laptop. I emailed tactrix a couple days ago, with no response. I came across a thread on here of a guy with the same problems and he somehow assigned a new serial number to his cable and it fixed the problem. I'll keep you posted on the for-sure fix.

 

hey-

i cant get my 1.3 cable to read from my ecuflash on my new evo 8 ecu. i can read/write the rom on my lancer oz fine just not the evo 8 ecu. anyone have a copy of 1.31 or earlier that they can send me?


josh

 

I have the same problem with my 1.3m cable except I cant read the rom off my lancer ecu or my evo ecu but I can write to my lancer ecu (havent tried writing to the evo ecu since I cant extract the rom to do so)

 

ok so i have the 1.3b cable and went back to v1.29a of ecu flash and i keep getting the error:


any ideas? and also does anyone have a GOOD version of 1.42 because i keep getting errors from downloading it from the openecu site.


josh

 

That's the same thing mine says now that I went from 1.34 to 1.42. Still waiting to see if Psquared or Alicea figure it out.

 

Try to uninstall using Windows Device Manager. Reinstall the drivers again after reboot. Worked for my friend.

 

One of the local guys may be onto something...uninstall everything, then go into the registry and delete all the openport stuff. It doesn't remove with the add hardware/remove hardware wizard. Gonna try it tomorrow on my laptop, i'll post results..

 

tried that. i got an uninstaller program that does that and still with no result.


josh

 

i have 1.3u i keep getting this error

08:59:28.828] Using interface OpenPort 1.3 Universal TX27XeHm39c1f4d53c43cca6c18bdebbdf14777d4bf1c331
[08:59:31.812] sending init sequence 1 (0003)
[08:59:32.843] got 0x05 response
[08:59:32.843] sending init sequence 2
[08:59:32.859] got 0x1B response
[08:59:32.859] sending init sequence 3
[08:59:33.234] entering bootloader
[08:59:33.250] sending kernel size (4420)
[08:59:33.281] sending kernel load address (0xFFFF7000)
[08:59:33.296] uploading kernel
[08:59:34.015] verifying kernel checksum response
[08:59:34.015] kernel valid
[08:59:34.234] kernel get version
[08:59:34.234] rkrv: preamble 1 error
[08:59:34.250] reading kernel comm buffer size
[08:59:34.468] reading kernel flash buffer size
[08:59:34.687] interface close

any suggestions on what version will work

 

Well to add to this thread. I installed a brand new hard drive in my laptop. Installed a fresh copy of XP Sp3 with all the updates. Then downloaded and installed ECUFLASH Version 1.42.2595. When I go to read my ECU I get the attached message.

 

Also having this problem. I cant seem to use the cable with 1.29 OR 1.42 now!