Notices
ECU Flash

EcuFlash V1.34 released

Thread Tools
 
Search this Thread
 
Old Nov 8, 2007, 07:25 PM
  #31  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
There should be 2 drivers...delete them, uninstall ecuflash.




install a new copy of ecuflash 1.34, the new tactrix drivers will be installed untill you connect the cable to the computer. When prompted, select the option that lets you tell windows where to look for the drivers. Use Browse button to go to the C:\Program Files>OpenEcu>EcuFlash>drivers>x86 directory click ok. It will ask you to do this 2 times to load the new drivers.
Attached Thumbnails EcuFlash V1.34 released-tactrix-drivers.jpg  
Old Nov 10, 2007, 09:56 AM
  #32  
Account Disabled
iTrader: (28)
 
Dapper Dan's Avatar
 
Join Date: Jul 2006
Location: ft. walton beach, FLORIDA
Posts: 1,115
Likes: 0
Received 0 Likes on 0 Posts
thanks! and yes i did have 4 drivers....ill test it out again tonight....
Old Nov 17, 2007, 02:15 PM
  #33  
EvoM Guru
iTrader: (50)
 
mrfred's Avatar
 
Join Date: Mar 2006
Location: Tri-Cities, WA // Portland, OR
Posts: 9,675
Received 129 Likes on 97 Posts
Originally Posted by Jorge T
did you uninstall the old tactrix drivers? the new ones are: (6/27/07 2.02.04)

Mine reads: Using interface OpenPort 1.3 Mitsubishi TX34.

I've noticed most that report OpenPort 1.3 Mitsubishi TX 14 have the ECU connection problem. Not sure if this has anything to do with it but
I also have .NET Framework 2.0 and 3.0 installed.
Haven't been able to get any versions after v1.29a to work. Just tried v1.34 today. Tried all the tricks, and couldn't get it to read/write to the ECU. I'm running the OpenPort 1.3 Mitsubishi TX14 cable. Guess its back to v1.29a yet again...
Old Nov 17, 2007, 04:53 PM
  #34  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
Interesting ... I'm starting to wonder if there are different cable firmware and/or hardware versions. Last weekend I could not read an ECU that was flashed with a cable newer than mine. And when I connected his cable on my computer it started recognizing as new hardware.
Old Nov 17, 2007, 09:46 PM
  #35  
EvoM Guru
iTrader: (5)
 
MalibuJack's Avatar
 
Join Date: Feb 2003
Location: Royse City, TX
Posts: 10,569
Likes: 0
Received 9 Likes on 9 Posts
Its possible that ECUFlash is checking versions of the cable to prevent knockoff cables from being used with it.

The Openport cable is the revenue generator for the development of ECUFlash..

I have an early 1.3m cable (from his first or second batch of cables), and a newer 1.3u cable and both worked fine with every version of ECUFlash I have installed. I do know drivers can be a PITA at times and generally uninstall them when I can before I update the software.
Old Nov 18, 2007, 07:44 AM
  #36  
EvoM Guru
iTrader: (50)
 
mrfred's Avatar
 
Join Date: Mar 2006
Location: Tri-Cities, WA // Portland, OR
Posts: 9,675
Received 129 Likes on 97 Posts
Originally Posted by MalibuJack
Its possible that ECUFlash is checking versions of the cable to prevent knockoff cables from being used with it.

...
I got my cable from Mynes, so that shouldn't be the cause in my case.
Old Nov 18, 2007, 08:25 AM
  #37  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
I haven't had and issue with any version of EcuFlash either, but it is also a second or third batch generation. Maybe it's a bug in the cable checking routine MJ mentions.
Old Nov 18, 2007, 01:41 PM
  #38  
Evolved Member
iTrader: (23)
 
nothere's Avatar
 
Join Date: Jan 2004
Location: Bellevue. WA
Posts: 2,680
Likes: 0
Received 1 Like on 1 Post
a little observation

ecuflash 1.34 downloaded and working fine on a never before ecuflash downloaded laptop.

the same program downloaded to a laptop that had 1.29 totally removed,(checked and checked again) using the same cable, gives an empty box from which I should choose car version.

rules out the cable, means there is something, someplace I'm not removing.
Old Nov 18, 2007, 02:03 PM
  #39  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
I have the same thing, somehow the set path is lost. I just go to options and change to the "read directory" but it's a hassle to have to go to options each time
I'm getting a laptop with a clean install of xp next week, I'll see what behaviour shows up.
Old Nov 18, 2007, 03:24 PM
  #40  
Evolved Member
iTrader: (9)
 
C6C6CH3vo's Avatar
 
Join Date: Feb 2005
Location: sc
Posts: 4,223
Likes: 0
Received 4 Likes on 4 Posts
Originally Posted by mrfred
I got my cable from Mynes, so that shouldn't be the cause in my case.
It's not a fact of where you got the cable, it's when you got it and which one. The newer cable version was recently released.

As far as ECUFLASH version, if you have the older cable then what reason is there to upgrade the version? Now if there were some new defined tables then that would be worth upgrading cable and ECUFLASH version. Just seems that the software has taken a hard left turn to Subaru if you ask me

Last edited by C6C6CH3vo; Nov 18, 2007 at 03:27 PM.
Old Nov 18, 2007, 03:55 PM
  #41  
Evolved Member
iTrader: (17)
 
Evo_Jay's Avatar
 
Join Date: Jun 2005
Location: Chico, CA (NOR-CAL)
Posts: 3,417
Received 13 Likes on 12 Posts
Originally Posted by mrfred
Haven't been able to get any versions after v1.29a to work. Just tried v1.34 today. Tried all the tricks, and couldn't get it to read/write to the ECU. I'm running the OpenPort 1.3 Mitsubishi TX14 cable. Guess its back to v1.29a yet again...
how bout 1.30?? 1.31 is when it became different.
Old Nov 18, 2007, 10:14 PM
  #42  
EvoM Guru
iTrader: (50)
 
mrfred's Avatar
 
Join Date: Mar 2006
Location: Tri-Cities, WA // Portland, OR
Posts: 9,675
Received 129 Likes on 97 Posts
Originally Posted by nothere

...

the same program downloaded to a laptop that had 1.29 totally removed,(checked and checked again) using the same cable, gives an empty box from which I should choose car version. ...
That issue I've tracked down. ECUFlash stores the path for the ROM template files in the registry. If you know how to handle the registry file, that one is easy to fix.

Last edited by mrfred; Nov 18, 2007 at 10:25 PM.
Old Nov 18, 2007, 10:23 PM
  #43  
EvoM Guru
iTrader: (50)
 
mrfred's Avatar
 
Join Date: Mar 2006
Location: Tri-Cities, WA // Portland, OR
Posts: 9,675
Received 129 Likes on 97 Posts
Originally Posted by C6C6CH3vo
It's not a fact of where you got the cable, it's when you got it and which one. The newer cable version was recently released.

As far as ECUFLASH version, if you have the older cable then what reason is there to upgrade the version? Now if there were some new defined tables then that would be worth upgrading cable and ECUFLASH version. Just seems that the software has taken a hard left turn to Subaru if you ask me
The older version of ECUFlash takes down my entire computer on occasion. Its only annoyance, but its a big one. I usually have about 15 folders open and often have IDA Pro running at the same time. I loose all the folders and if IDA Pro gets taken down, I loose my place in the disassembly.
Old Nov 18, 2007, 10:24 PM
  #44  
EvoM Guru
iTrader: (50)
 
mrfred's Avatar
 
Join Date: Mar 2006
Location: Tri-Cities, WA // Portland, OR
Posts: 9,675
Received 129 Likes on 97 Posts
Originally Posted by Evo_Kid
how bout 1.30?? 1.31 is when it became different.
Same issue with those versions.
Old Nov 18, 2007, 10:57 PM
  #45  
EvoM Guru
iTrader: (6)
 
tephra's Avatar
 
Join Date: Feb 2007
Location: Melbourne, Australia
Posts: 9,486
Received 66 Likes on 42 Posts
lol @ idapro... you know your in trouble when you have more than 8 windows of disasm open


Quick Reply: EcuFlash V1.34 released



All times are GMT -7. The time now is 10:00 AM.