I have downlaoded ECUflash 1.3 and I am unable to upload or download data fromt eh ECU.

It used to work on the older version.

Please advise what i need to do.

email me at roberttonge@cwdom.dm

 

Can you be more specific?

When the cable is plugged in, does the OS see it? If it does, what is the description of the device.

In ECUFlash, in the lower right corner, does it show a device name, or "No Vehicle Interface"

 

This is my guess you need to reinstall the drivers for the Flash Cable cause I had to

 

I am having the same problem. I installed ECUFlash 1.30 with no probs, and when I attached my laptop to the ECU, new openport drivers were installed. ECUFlash 1.30 recognizes that a cable is connected to a Mitsubishi, but when I attempted to upload a ROM to the ECU, ECUFlash gave a message in the console saying that it couldn't connect to the ECU. I tried rebooting the computer, but that didn't help. Running XP SP2.

I reinstalled 1.29, and it worked fine as before.

 

Weird.. Colby and I were discussing some of the issues that people have been turning up. The weird thing is not alot has changed between 1.29a and 1.30 Colby mentioned he added 64 bit drivers, and some improvements in how ECUFlash handles initialization timings so people can read newer subaru ECU's that might not have worked in 1.29a

Windows 2000 issues aside, since its a dead O/S and people should be migrating off it. There are a few people reporting installation issues, or problems launching the app. I haven't installed it on the laptop I do my tuning with, but I decided to try it on another laptop running XP and it installed and ran fine on that one.

Hopefully Colby will be able to offer some input if he see's this thread. But I would definitely post in OpenECU.org about your issues so he is aware of it.

 

I am having trouble on XP with 1.30 also. It does not open.

 

I'll try to give you a call tomorrow, I just got your voice mail a few minutes ago, trying to get a bit of family time after this long hectic week.

I actually don't know of a resolution, since you don't get any "Errors" or messages when it doesn't launch, the best I can think of is perhaps there is some tool like an anti-virus/spyware app preventing it from launching a particular DLL.

I would look in the computer's event log under application (and system) see if there are any interesting looking errors that are relevent.

 

Weird stuff. In order to get the program to open I need to delete EVO9base from the XML definitions just so ecuflash will open and when it does I get this message:

[01:01:13.765] Version 1.30.1095
[01:01:13.765] 8 memory models read.
[01:01:13.781] Unable to find parent metadata evo9base
[01:01:13.781] ROM metadata models 83540008.xml is invalid.
[01:01:13.781] Unable to find parent metadata evo9base
[01:01:13.781] Unable to find parent metadata 83540008
[01:01:13.781] ROM metadata models 89970010.xml is invalid.
[01:01:13.812] Unable to find parent metadata evo9base
[01:01:13.828] ROM metadata models 88570008.xml is invalid.
[01:01:13.828] Unable to find parent metadata evo9base
[01:01:13.828] ROM metadata models 88590013.xml is invalid.
[01:01:13.843] Unable to find parent metadata evo9base
[01:01:13.843] ROM metadata models 88590014.xml is invalid.
[01:01:13.843] Unable to find parent metadata evo9base
[01:01:13.843] ROM metadata models 88590015.xml is invalid.
[01:01:13.859] Unable to find parent metadata evo9base
[01:01:13.859] ROM metadata models 88840013.xml is invalid.
[01:01:13.859] Unable to find parent metadata evo9base
[01:01:13.859] ROM metadata models 88840016.xml is invalid.
[01:01:14.859] 137 ROM metadata models read.
[01:01:14.859] checksum module "subarudbw" loaded.
[01:01:14.859] flashing tool "wrx02" loaded.
[01:01:14.859] flashing tool "wrx04" loaded.
[01:01:14.859] flashing tool "sti04" loaded.
[01:01:14.859] flashing tool "sti05" loaded.
[01:01:14.859] flashing tool "mitsukernel" loaded.
[01:01:14.859] flashing tool "mitsukernelocp" loaded.
[01:01:14.859] flashing tool "mitsubootloader" loaded

This should be an easy fix with this information. Let me know what you figure out.

 

have you guys tried un-installing and then deleting the OpenECU directory all together, so that there are no old definition files?

then reinstall after that

 

there must be a problem with your 9 database
here is mine, change the extention to .rar before you open it
(evom wont take rar files and I dont have winzip)
it also has a couple extra definitions.

 

I got rid of 88570008 and it seems to have stabilized. We'll see how it goes.

 

Thanks for the feedback

 

I have ecuflash 1.3 on vista and it works fine just fyi.

 

what does the message log say?

colby

 

Mine seems to be working. I was able to read the image in my car. Dont know about flashing yet though