Notices
ECU Flash

Ecuflash 1.3

Thread Tools
 
Search this Thread
 
Old Mar 24, 2007 | 07:50 PM
  #16  
dudical26's Avatar
Evolved Member
iTrader: (17)
 
Joined: Nov 2005
Posts: 2,544
Likes: 0
From: NNJ
is there anywhere we can still download 1.28 and 1.29 I deleted my old install files and I would like to be able to run 1.28 or .29
Reply
Old Mar 24, 2007 | 08:53 PM
  #17  
TTP Engineering's Avatar
Account Disabled
iTrader: (465)
 
Joined: May 2005
Posts: 8,824
Likes: 2
From: Central FL
He probably doesn't want it posted here, but:
http://www.norcalmotorsports.org/use...lash_versions/
Reply
Old Mar 24, 2007 | 09:05 PM
  #18  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Originally Posted by colby
what does the message log say?

colby
I used the v1.29 uninstaller to remove 1.29, and then I installed 1.30 again. When I plug in the openport cable after doing a 1.30 install, a window comes up to install two drivers (openport and openport serial). I install the drivers and try to use 1.30. In the log below, I tried writing a ROM twice. I also tried rebooting the computer after the driver install, but it didn't help.

[00:06:07.562] Version 1.30.1095
[00:06:07.578] 8 memory models read.
[00:06:07.718] 22 ROM metadata models read.
[00:06:07.718] checksum module "subarudbw" loaded.
[00:06:07.734] flashing tool "wrx02" loaded.
[00:06:07.734] flashing tool "wrx04" loaded.
[00:06:07.734] flashing tool "sti04" loaded.
[00:06:07.734] flashing tool "sti05" loaded.
[00:06:07.734] flashing tool "mitsukernel" loaded.
[00:06:07.734] flashing tool "mitsukernelocp" loaded.
[00:06:07.734] flashing tool "mitsubootloader" loaded.
[00:06:27.656] 524288 byte image read.
[00:06:31.203] unable to connect to vehicle interface.
[00:06:46.109] unable to connect to vehicle interface.
Reply
Old Mar 24, 2007 | 09:12 PM
  #19  
MalibuJack's Avatar
EvoM Guru
20 Year Member
iTrader: (5)
 
Joined: Feb 2003
Posts: 10,572
Likes: 14
From: Royse City, TX
Out of curiosity does it recognize the cable in the lower right corner of ECUFlash?

It is a tactrix cable right? Not an E-bay one or anything like that?
Reply
Old Mar 24, 2007 | 09:40 PM
  #20  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Originally Posted by MalibuJack
Out of curiosity does it recognize the cable in the lower right corner of ECUFlash?

It is a tactrix cable right? Not an E-bay one or anything like that?
Yep, ECUFlash definitely recognizes the Tactrix cable being inserted/removed. The text changes on the bottom right of the ECUFlash window. The text reads the same as when I am running 1.29. Got the cable from Mynes.
Reply
Old Mar 25, 2007 | 09:47 PM
  #21  
Crufty Dusty's Avatar
Evolving Member
 
Joined: Jan 2002
Posts: 363
Likes: 0
From: Singapore
Originally Posted by MalibuJack
Out of curiosity does it recognize the cable in the lower right corner of ECUFlash?

It is a tactrix cable right? Not an E-bay one or anything like that?
MJ, what I've noticed is that the ability to select the COM port has been disabled. i.e. selecting "Options" from the menu just gives the preferences screen. Thus if the wrong port was recognized there is no way to select it.
Reply
Old Mar 26, 2007 | 02:13 AM
  #22  
ONRAILS's Avatar
Evolved Member
iTrader: (7)
 
Joined: Jul 2006
Posts: 841
Likes: 0
From: Kentucky
Same thing mine was doing. Coby please post a link to 129a on your site again i had to go though hell to get it back..

if anyone needs it. I have the installer just hit me up on AIM sn. Violentfun
Reply
Old Mar 26, 2007 | 05:57 AM
  #23  
MalibuJack's Avatar
EvoM Guru
20 Year Member
iTrader: (5)
 
Joined: Feb 2003
Posts: 10,572
Likes: 14
From: Royse City, TX
The way the software works is it doesn't use "Com" ports any longer. It selects it from the driver, so its unlikely to select the wrong cable unless you have two openport cables plugged in at the same time.

If it works like Mitsulogger, it'll select the first device it sees that is an openport cable, and doesn't require any configuration.
Reply
Old Mar 26, 2007 | 07:55 AM
  #24  
Oracle1's Avatar
Evolving Member
iTrader: (1)
 
Joined: Nov 2005
Posts: 425
Likes: 0
After new install run setup drivers for cable 1.3. Or connect cable to ecu and reboot computer, this will pick it up as default and install correct driver
Reply
Old Apr 1, 2007 | 05:34 PM
  #25  
96_LXR's Avatar
Evolving Member
iTrader: (3)
 
Joined: Jun 2004
Posts: 203
Likes: 0
From: Pacific Northwest
I'm having the same issue. Just tried it for the first time today. I believe the screen message says something about "unable to load something Evo"?

The strange thing is that I was able to download what was currently in the car but it took waaay longer than it used to.

I would guess it took about a minute to dl.

I'm gonna uninstall / reinstall and see what happens.

Uninstalled the software, deleted the folder, reinstalled and now it is working again. It did prompt me for drivers, selected the defaulst and now it's working.

Last edited by 96_LXR; Apr 1, 2007 at 08:34 PM. Reason: It's fixed
Reply
Old Apr 5, 2007 | 08:16 PM
  #26  
kmcconn9's Avatar
Evolved Member
iTrader: (33)
 
Joined: Jun 2005
Posts: 3,044
Likes: 3
From: Hagerstown
weird, I dowloaded 1.30 today and came across this error..

Code:
[20:04:51.500] Version 1.30.1095
[20:04:51.515] 8 memory models read.
[20:04:52.406] 145 ROM metadata models read.
[20:04:52.406] checksum module "subarudbw" loaded.
[20:04:52.406] flashing tool "wrx02" loaded.
[20:04:52.406] flashing tool "wrx04" loaded.
[20:04:52.406] flashing tool "sti04" loaded.
[20:04:52.406] flashing tool "sti05" loaded.
[20:04:52.406] flashing tool "mitsukernel" loaded.
[20:04:52.406] flashing tool "mitsukernelocp" loaded.
[20:04:52.406] flashing tool "mitsubootloader" loaded.
[20:04:52.453] error loading FTChipID.DLL
[20:05:02.375] 262144 byte image read.
[20:05:16.718] 262144 byte image read.
Reply
Old Apr 5, 2007 | 08:19 PM
  #27  
nj1266's Avatar
Evolved Member
iTrader: (6)
 
Joined: Nov 2004
Posts: 3,254
Likes: 13
From: USA
I had a problem with 1.3 as well. I got an error message. So I reverted back to 1.29a and it worked. I have no idea why 1.30 is not working on my lap top.
Reply
Old Apr 6, 2007 | 05:56 AM
  #28  
kmcconn9's Avatar
Evolved Member
iTrader: (33)
 
Joined: Jun 2005
Posts: 3,044
Likes: 3
From: Hagerstown
well I will find out today if the 1.3 works today as I need to make some changes to my idle. It loads a saved rom fine, so we will see.
Reply
Old Apr 7, 2007 | 11:50 PM
  #29  
tirbolag9's Avatar
Evolving Member
 
Joined: Sep 2005
Posts: 145
Likes: 0
From: cali
Originally Posted by nj1266
I had a problem with 1.3 as well. I got an error message. So I reverted back to 1.29a and it worked. I have no idea why 1.30 is not working on my lap top.
I am experiencing the same deal. Reverted back to 1.29 and everything works fine. I've also uninstalled/installed a couple of times already and still does not work.
Reply
Old Apr 8, 2007 | 12:01 AM
  #30  
nj1266's Avatar
Evolved Member
iTrader: (6)
 
Joined: Nov 2004
Posts: 3,254
Likes: 13
From: USA
Originally Posted by mrfred
I used the v1.29 uninstaller to remove 1.29, and then I installed 1.30 again. When I plug in the openport cable after doing a 1.30 install, a window comes up to install two drivers (openport and openport serial). I install the drivers and try to use 1.30. In the log below, I tried writing a ROM twice. I also tried rebooting the computer after the driver install, but it didn't help.

[00:06:07.562] Version 1.30.1095
[00:06:07.578] 8 memory models read.
[00:06:07.718] 22 ROM metadata models read.
[00:06:07.718] checksum module "subarudbw" loaded.
[00:06:07.734] flashing tool "wrx02" loaded.
[00:06:07.734] flashing tool "wrx04" loaded.
[00:06:07.734] flashing tool "sti04" loaded.
[00:06:07.734] flashing tool "sti05" loaded.
[00:06:07.734] flashing tool "mitsukernel" loaded.
[00:06:07.734] flashing tool "mitsukernelocp" loaded.
[00:06:07.734] flashing tool "mitsubootloader" loaded.
[00:06:27.656] 524288 byte image read.
[00:06:31.203] unable to connect to vehicle interface.
[00:06:46.109] unable to connect to vehicle interface.
I think I am getting the same error message that you are mrfred. Glad I kept the 1.29a on my lap top so I can revert back to it.
Reply



All times are GMT -7. The time now is 09:54 AM.