Do you, or anyone, know how to fix that?

 

Well.... I have vista on two different laptops and mine worked fine right out of the box. I would try to download a different version or revision of the code.

 

Make sure you don't have anything else plugged into the lappy besides the ecu cable.

Also DL and open the ecu unlocker and run that first, then open ecu flash.

 

If you can't tell, I am new to this. What do you mean by revision of the code?

The tactrix cable was the only thing pugged in. Where can I get this ecu unlocker?

 

A different version of ECUFlash. Sometimes some people get one version to work for them and switching up/down doesn't work so that might be the problem.


Search around on aktivematrix.com

 

I had a similar problem... But found that it was .xml errors, or where I edited from... If u dont edit the .xml from where the program is located, ex. Comp>Program Files>Ecuflash, etc. it will mess everything up! I ended up un-installing/re-installing like 5-6 w/ ECUFLASH. And in the process of installing 5-6 times, it DL the driver in all of the 4different COM ports. U can fix this in ur device manger... Also you can make sure you have all versions uninstalled and all shortcuts/links deleted! When u install... Make sure the car is in ign. on/ engine off, Hook up the Tactrix cable to the comp, before installing, and it should find and use the COM port used on the last install.

From what I have read V. 1.29 is the most used. I use it w/ Vista. There is a thread on "ecuflash versions" I would DL 1.29 and try that!

Mattjin, Colby already released the new version? or is this an old 1 that I missed. I just read the thread in EVOM about the new .xml files for the upcoming version...

 

I seem to have had the same problem, but I dont think it was anything to do with the cable. And I am not new to the tuning game either (20 years experience).

It works perfectly on V1.34, and previously I have had driver issues where Windows will recognise the cable but both EvoScan and EcuFlash would not see it. On V1.35 the software detects the cable (bottom right of the page) but the software itself crashes. It freezes and windows reports the software not responding. Strange that installing V1.34 again fixes it, so it has to be an issue in V1.35.

MarkyMark, I would keep trying with V1.34. Seeing as we have the same problem with V1.35, and mine works on V1.34 means there is a solution possible for you.

Nonschlont, my EcuFlash opened up a pop-up that told me of the new release and the changes made. Only did this while running the software while I am online. I have wireless in the home and workshop. Try it and it should do it. Also popped it up again after I re-installed V1.34.

2007-05-15: Version 1.35 released
this is a minor update to support some recent cable changes - a major release is coming soon!
FTDI drivers updated to CDM 2.02.06
Qt updated to 4.4.0
Qwt updated to 5.1.0
bitfields now supported in bloblists
Subaru definitions update to merchgod's 0.8 release

 

Get it from http://www.openecu.org/index.php?title=EcuFlash

 

Thanks guys. I will try all of this as soon as I can. I am pretty busy with work right now. I will most likely get to it this weekend.

 

I have had problems with using vista too. I had to unistall it and download it from my friends computer. trying saving it to a disk then download it to your computer.

 

Thanks guys, I got it to work. I downloaded v1.34 again and also downloaded ECU Unlocker. One of the two things fixed it.

 

This might be a dumb question, but what version of Vista? Home Basic, Standard, Home Premium, Ultimate, Business, and is it 32bit or 64bit??

I noticed recently that some versions of the drivers are not 64bit, and some that are, are unsigned. This can make getting a good install of drivers under vista a bit challenging.

I just picked up a new Dev PC running a quad core 64 bit processor, running XP Ultimate 64bit. Until I realized I had some driver signing issues, I could not get it working. There *ARE* workarounds but need more specific information about the machine in question.

This doesn't appear to be an unlocker issue, however it can't hurt to try it. So go through all of the suggested steps from previous posts about versions and whatnot, but please post specifics on your OS.. This never occurred to me as being a problem until I started getting messages from people, and started realizing there are some inexpensive Dual Core laptops out there running Vista 64bit Home Premium (You should try to get Business or Ultimate installed on them in their place, as there are major enough differences that make getting this stuff to work more difficult)

 

Okay disregard.. It seemed like you had already tried a few things.. Generally if you cannot download a rom, you try unlocker first as its the easiest and least intrusive thing to try..

(This post is for people who searched for solutions to this issue)

I would still like to know who has tested/successes with 64 bit (multicore CPU) reflashing with ECUFlash, as I have built mitsulogger as a 64bit app recently.

 

I was having the V1.35 problem on Vista Business 32-bit.

 

I am running Vista Home Premium. I think it is 32-bit on a Intel Dual Core.