I have a new laptop running Windows 7, Ecuflash 1.42, and using my Tactrix Openport 1.3 cable - although the computer appears to recognize the cable I cannot connect to the ECU (read or write). Any ideas why ?

I can use the same cable just fine on an older laptop running XP, Ecuflash 1.30, and the same cable. Thanks in advance!

 

I have the same problem. I cant connect win7, ecuflash 1.42, 1.3 cable

but if i get the hex using evoscan 2.6, it downloads fine

 

If its looking at the cable and you see the serial key for the cable contains a bunch of 0's at the end like this. xxxxxxxx00000000000000000000

What it means is you have a cable that was bought before they changed the way they do serial keys. Tactrix has a way of updating the cable's serial key but you have to email them with proof of purchase like an email with your receipt and the serial key you have currently would be needed.

 

in for result...
Ive been thinking of going to windows7 from vista...
GL OP!

 

FYI i run windows 7 ultimate x64 bit edition with ecuflash no issues here with a 1.3 cable. Ordered a 2.0 cable and will test it next week if you guys want.

 

RoadSpike, any news on your test? I just got my openport 2.0 from tactrix.... having problem getting it to connect to the ECU

 

Where do you find the serial key for the 1.3 cable? I looked through the properties in device manager and such but couldn't come up with anything.

 

I have no issues connecting both of my Win7 laptops with either 1.3 or 2.0 cables. I did configure the Properties under Compatibility Mode and check the box for Run Program in compatibility mode for Windows XP (Service Pack3) in the drop down. Not sure if it's necessary but I did it. One of the two laptops does go blue screen if I'm driving around with it logging for awhile. This one I have not figured out.

 

Kind of off topic but
can you use open port 2.0 cable to log your evo9 with evoscan2.7?

 

^ Yes.