Notices
Evo General Discuss any generalized technical Evo related topics that may not fit into the other forums. Please do not post tech and rumor threads here.
Sponsored by: RavSpec - JDM Wheels Central

Help a fellow member out

Thread Tools
 
Search this Thread
 
Old Jan 8, 2013 | 07:41 PM
  #16  
03GTEvo's Avatar
Thread Starter
Newbie
 
Joined: Nov 2012
Posts: 21
Likes: 0
From: Augusta, GA
RussellDaniel- That would be really helpful, but that's a little far of a drive. Do you think we could possibly meet around halfway? I could buy you lunch and give a little gas money.
Reply
Old Jan 8, 2013 | 08:20 PM
  #17  
hiboost2.0's Avatar
Evolved Member
iTrader: (15)
 
Joined: Oct 2010
Posts: 641
Likes: 4
From: NJ
Aw man, I was actually going to make a trip to Savannah GA to visit some buddies at their school this week. If I went I would have definitely helped you out. Good luck man.
Reply
Old Jan 9, 2013 | 05:31 PM
  #18  
RussellDaniel's Avatar
Evolved Member
iTrader: (9)
 
Joined: Oct 2012
Posts: 554
Likes: 2
From: hinesville
Its not too bad of a drive its like 2 hours right. I know we get guys that come down on buses from Augusta all the time I'll let you know for sure. I have to drive about 3 hours at the end of the week to go install by double pumper a spoolin up kit and get a little tweak to my tune.
Reply
Old Jan 9, 2013 | 05:39 PM
  #19  
MikeyPSF's Avatar
Newbie
 
Joined: Oct 2012
Posts: 60
Likes: 2
From: San Francisco
Originally Posted by evo8426
Do yourself a favor and uninstall 1.44.3719, I have not been able to use that version to flash or read my car.

Download 1.42.2595 and try with this version. I have been using it for many years without any issues like most users are seeing with 1.44.3719.
What problems were you seeing with your car? Can you post a complete copy of your log window output?

We've had a lot of users install and successfully use 1.44 so I don't think it's fair to say "most users are seeing". We are aware of a problem where the mem model isn't displaying under the ROM info section, and can patching isn't showing up but we'll have a fix out for those two issues shortly.

If you're having problems other than those it could be that our new definitions are missing something custom you had in your rommetadata folder. When you install a new version of EcuFlash it will back up old rommetadata folders in a folder called backup001 (or another number if you've installed multiple versions). If you accepted the default location values during install you should have a folder like:

C:\Program Files (x86)\OpenECU\EcuFlash\backup001

If you select "options" and then navigate to "directories->metadata directory" you can set that to value point to your old definitions instead of the default directory with the latest definitions we have. That will likely clear up most problems people are having.

If anyone is seeing other problems, please post them here or contact us at support at tactrix.com.

Mike
Tactrix
Reply
Old Jan 9, 2013 | 06:29 PM
  #20  
03GTEvo's Avatar
Thread Starter
Newbie
 
Joined: Nov 2012
Posts: 21
Likes: 0
From: Augusta, GA
RussellDaniel- Ok man. Just let me know if it can be worked out. I would sincerely appreciate it.

MickeyPSF- I'm seeing this:
[20:00:25.358] EcuFlash Version 1.43.3252
[20:00:25.358] OS Version Windows 7
[20:00:25.358] Qt Version 4.6.2
[20:00:25.368] 62 memory models read.
[20:00:25.369] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[20:00:25.609] 356 ROM metadata models scanned.
[20:00:25.609] checksum module "subarudbw" loaded.
[20:00:25.609] checksum module "mitsucan" loaded.
[20:00:25.609] checksum module "mitsuh8" loaded.
[20:00:25.609] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[20:00:25.610] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[20:00:25.610] flashing tool "wrx02" loaded.
[20:00:25.610] flashing tool "wrx04" loaded.
[20:00:25.610] flashing tool "sti04" loaded.
[20:00:25.611] flashing tool "sti05" loaded.
[20:00:25.611] flashing tool "mitsukernel" loaded.
[20:00:25.611] flashing tool "mitsukernelocp" loaded.
[20:00:25.611] flashing tool "mitsubootloader" loaded.
[20:00:25.611] flashing tool "shbootmode" loaded.
[20:00:25.612] flashing tool "shaudmode" loaded.
[20:00:25.612] flashing tool "subarucan" loaded.
[20:00:25.612] flashing tool "subarucand" loaded.
[20:00:25.613] flashing tool "mitsucan" loaded.
[20:00:37.390] Using interface OpenPort 1.3 Universal TX2GAQQS138a7fcdb4e5483d05653ab097d209e154b93dc9
[20:00:37.391] interface close
[20:00:37.402] unable to connect to vehicle interface.

I looked up that file and it is present on my computer. And when I go to Metadata Directory, it says it looks in a file named rommetadata. I don't understand what you said after that though. I'm usually good with computers, but EcuFlash really confuses me. If you can help point me in the right direction that would be greatly appreciated.
Reply
Old Jan 10, 2013 | 09:26 AM
  #21  
evo8426's Avatar
Evolved Member
iTrader: (27)
 
Joined: Jan 2006
Posts: 4,248
Likes: 9
From: Charlotte, North Carolina
Originally Posted by MikeyPSF
What problems were you seeing with your car? Can you post a complete copy of your log window output?

We've had a lot of users install and successfully use 1.44 so I don't think it's fair to say "most users are seeing". We are aware of a problem where the mem model isn't displaying under the ROM info section, and can patching isn't showing up but we'll have a fix out for those two issues shortly.

If you're having problems other than those it could be that our new definitions are missing something custom you had in your rommetadata folder. When you install a new version of EcuFlash it will back up old rommetadata folders in a folder called backup001 (or another number if you've installed multiple versions). If you accepted the default location values during install you should have a folder like:

C:\Program Files (x86)\OpenECU\EcuFlash\backup001

If you select "options" and then navigate to "directories->metadata directory" you can set that to value point to your old definitions instead of the default directory with the latest definitions we have. That will likely clear up most problems people are having.

If anyone is seeing other problems, please post them here or contact us at support at tactrix.com.

Mike
Tactrix
I'm not having a problem with xml files as I already knew to completely replace them with my previous rommetadata file. When I connected to my car it never gave me the option to flash/read/compare my rom.

I like to use graphs as much as I can but the new version does not work very well so reverting back to 1.42 is my solution.
Reply
Old Jan 10, 2013 | 05:19 PM
  #22  
03GTEvo's Avatar
Thread Starter
Newbie
 
Joined: Nov 2012
Posts: 21
Likes: 0
From: Augusta, GA
Come on guys I need some help here. I'm not asking too much, just hook up my cable to make sure it's not the problem. If I happen to mess up something on your car in the process, I promise to pay for the repair.
Reply
Old Jan 10, 2013 | 06:07 PM
  #23  
MikeyPSF's Avatar
Newbie
 
Joined: Oct 2012
Posts: 60
Likes: 2
From: San Francisco
Originally Posted by 03GTEvo
I looked up that file and it is present on my computer. And when I go to Metadata Directory, it says it looks in a file named rommetadata. I don't understand what you said after that though. I'm usually good with computers, but EcuFlash really confuses me. If you can help point me in the right direction that would be greatly appreciated.
rommetadata is the parent directory that contains all of the definition files. Based on what you said above, you're pointing to the right place.

Are you using a 1.3u cable purchased from evoscan? Do they offer any support to help you confirm the unit is working properly?

You mentioned that the previous owner messed with a bunch of wiring. What sort of wiring was tampered with? Under the hood or under the dash?
Reply
Old Jan 10, 2013 | 08:07 PM
  #24  
03GTEvo's Avatar
Thread Starter
Newbie
 
Joined: Nov 2012
Posts: 21
Likes: 0
From: Augusta, GA
MikeyPSF- I am using the 1.3u cable from evoscan. I haven't gone to them yet to see if it is defective or not. There were some tampered wires underneath the dash and some wires added, both of witch I'm not 100% sure what he wired them for. I looked underneath once and barely touched the power wire for the AEM UEGO he added and it fell out of the butt splice he did. I had to fix that plus another wire for the EUGO. So I have a hunch that there might be other wiring altercations he did poorly or incorrectly. I just haven't had much spare time during daylight to fully investigate it. I work from 7:30-5 Monday through Saturday, so I don't have too much spare time.
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
voltexct9a
ECU Flash
12
Jan 22, 2016 05:23 PM
ehall20
Evo General
1
Apr 3, 2014 03:38 PM
Mitsu.kid.02
Lancer Engine Management / Tuning Forums
2
Jan 23, 2014 11:10 AM
thebluesky
Southeast Region
8
Feb 18, 2013 05:55 PM
nuk1ear
ECU Flash
9
Jan 17, 2013 02:37 PM




All times are GMT -7. The time now is 06:07 AM.