ECU flash and tactrics 1.3 -- not compatible with windows 7?

[Rogue]

I just upgraded to windows 7.. and can no longer, log or flash the ecu.

Any fixes.. or am I missing something?

I tried running both programs in windows xp compatibility mode with no success.

[project_skyline]

They probably haven't made the program compatible with windows 7, when you installed it did all the drivers get installed as well? Does it recognize when you plug in the tactrix cable?

[lqdchkn]

I can run it on Windows 7 x64 just fine. Course I have the evoscan v.s. ecuflash cable issue but lots of people have that.

[Rogue]

i run 64 bit also.

it beeps when it plugs in.. but does nothing after that. evoscan does not work either.

it appears it does not realize the cable/cars there...

[project_skyline]

Try reinstalling the driver again, go into device manager and verify that it reads it as the tactrix cable.

[jack_of_trades]

Hmm, I recently upgraded my tuning laptop to Windows 7 32-bit Home Edition but I haven't tried using my Tactrix cable with it yet. Anyone successfully running theirs with my combination?

[Rogue]

Hmm, I recently upgraded my tuning laptop to Windows 7 32-bit Home Edition but I haven't tried using my Tactrix cable with it yet. Anyone successfully running theirs with my combination?

Its new technology.. Not better.. lol


Windows 7 kicks ass compared to vista tho..

[lqdchkn]

i run 64 bit also.

it beeps when it plugs in.. but does nothing after that. evoscan does not work either.

it appears it does not realize the cable/cars there...

Not trying to be a smart a$$ but your sure your using a tatrix cable and not an evoscan cable, they are different and the newer versions of ecuflash and windows know the difference

[Rogue]

It worked just fine 15 mins before the upgrade.


How do you tell the difference in the cables? Mine has the OBD II plug and the small other plug..?


Mine looks like this

http://tunertools.com/proddetail.asp...C-OpenPort1.3U

[lqdchkn]

they look almost identical but usually the tatrix/ecuflash cables have 3 pins tapped in the flashing port(white plug) where as the evoscan cable only have one pin tapped in the flashing port.

[Rogue]

mine has 3

[lqdchkn]

Hmmmm I haven't really heard about too many issues with those. not sure if I missed it but What version of ecuflash?

[Evo_Kid]

they look almost identical but usually the tatrix/ecuflash cables have 3 pins tapped in the flashing port(white plug) where as the evoscan cable only have one pin tapped in the flashing port.

Even though the tactrix has three wires to the white plug, it doesnt matter, as the flash port itself only has one male pin. Tactrix only added the other two wires for strength.

And it doesnt matter if its a cable bought from tactrix/ecuflash or Evoscan/limitless, because BOTH cables are the exact same. As long as you have a 1.3U cable it will work with ECUflash & Evoscan. (Evoscan/limitless does sells a 1.3R cable. That cable WILL NOT work with ECUflash)

FYI I own both cables.

[lqdchkn]

Even though the tactrix has three wires to the white plug, it doesnt matter, as the flash port itself only has one male pin. Tactrix only added the other two wires for strength.

And it doesnt matter if its a cable bought from tactrix/ecuflash or Evoscan/limitless, because BOTH cables are the exact same. As long as you have a 1.3U cable it will work with ECUflash & Evoscan. (Evoscan/limitless does sells a 1.3R cable. That cable WILL NOT work with ECUflash)

FYI I own both cables.

Both cables are not the exact same try using an evoscan branded cable on ecuflash > 1.30. Even evoscan has posted that some of their cables need some kind of serial number update to the firmware to work. I don't believe they are still doing this which is why I'm trying to help him figure out which type of cable he has.

Sorry if you don't agree but there is a difference. I have one and it will not read or write to any ecu with any version of ecuflash > than 1.30. Your welcome to come to my house and attempt to make it work for me but believe me it won't and it won't even work if the newer driver are installed on the system.


Rogue-

So there you have it... why I was asking about your cable and the version of ecuflash your using. I know that in my scenario that I need to have a clean machine (PC) with only 1.30 installed for it to work properly. If any greater version is installed even just to use for editing it will muck up my drivers and Windows will not allow you to revert tothe older version. So you will have to have Windows uninstall the drivers, "forget" the device, completly uninstall all versions and drivers (they uninstall separately) and reinstall from scratch, if your in the same boat i'm in.

[Rogue]

Like you said tho -- I think it may just be a drivers issue cuz this all worked just fine on vista and XP and nothing has been updated.

My cable and car are both at buschurs so... ill check when I get it back.

[Evo_Kid]

Both cables are not the exact same try using an evoscan branded cable on ecuflash > 1.30. Even evoscan has posted that some of their cables need some kind of serial number update to the firmware to work. I don't believe they are still doing this which is why I'm trying to help him figure out which type of cable he has.

Sorry if you don't agree but there is a difference. I have one and it will not read or write to any ecu with any version of ecuflash > than 1.30. Your welcome to come to my house and attempt to make it work for me but believe me it won't and it won't even work if the newer driver are installed on the system.

Ok I know what your problem is. On some of the first 1.3U cables evoscan/limitless sold, they did NOT have an ECUflash serial number. Now though, all the 1.3U cables that Evoscan/limitless sales HAVE an ecuflash serial number and WORK with the newest version of ECUflash.

Or you didnt/dont have an 1.3U cable, and accidentally got/bought the 1.3R cable, which does NOT have a ECUFlash license.

[Evo_Kid]

So there is no more incorrect info

I just went out to my car and tested TWO EvoScan/limitless 1.3U cables.

BOTH HAVE an ECUFlash license

BOTH WORKED perfectly fine with ECUFlash ver. 1.42

I tested this on my laptop with Vista and setup (drivers installed) for a tactrix cable. All I did was plug then Evoscan cable in, it installed its drivers, then worked perfectly with both ECUFlash and Evoscan.

[lqdchkn]

So there is no more incorrect info

I just went out to my car and tested TWO EvoScan/limitless 1.3U cables.

BOTH HAVE an ECUFlash license

BOTH WORKED perfectly fine with ECUFlash ver. 1.42

I tested this on my laptop with Vista and setup (drivers installed) for a tactrix cable. All I did was plug then Evoscan cable in, it installed its drivers, then worked perfectly with both ECUFlash and Evoscan.

Ok I know what your problem is. On some of the first 1.3U cables evoscan/limitless sold, they did NOT have an ECUflash serial number. Now though, all the 1.3U cables that Evoscan/limitless sales HAVE an ecuflash serial number and WORK with the newest version of ECUflash.

Or you didnt/dont have an 1.3U cable, and accidentally got/bought the 1.3R cable, which does NOT have a ECUFlash license.

its a 1.3u but you wouldn't happen to know how to get the serial in mine would you?

[jack_of_trades]

Hmm, I recently upgraded my tuning laptop to Windows 7 32-bit Home Edition but I haven't tried using my Tactrix cable with it yet. Anyone successfully running theirs with my combination?

Its new technology.. Not better.. lol


Windows 7 kicks ass compared to vista tho..

I'm not really sure where your reply had any relevance to my post???? All I wanted to know is if anyone was running Windows 7 32-bit Home Edition with ECUFlash/Evoscan sucessfully before I got a chance to check myself on an Evo.

[Evo_Kid]

its a 1.3u but you wouldn't happen to know how to get the serial in mine would you?

Someone made a lil hack to get around not having the serial number. It should be on EvoM in the ECUFlash section.