Q: What happened to Enginuity and their site?
RomRaider is the new name for Enginuity. The new site can be found HERE (http://www.romraider.com/). The Wiki, posts, user names, and passwords have been transferred to the new RomRaider site, so you can log in as you did before and access the same information and downloads. The story behind what happened can be found HERE (http://www.romraider.com/forum/viewtopic.php?f=1&t=2722).


Q: I want to log and/or tune my Subaru with RomRaider. What do I need to do?
1. Purchase a Tactrix (http://www.tactrix.com)(Openport) cable.
2. Download and install the latest version of Java (http://www.java.com/en/index.jsp).
3. Download and install the latest RomRaider software (http://www.romraider.com/RomRaider/Download).
4. Download and install the latest RomRaider ECU definitions (http://www.romraider.com/forum/topic360.html). There are two versions. Choose standard units if you wish to tune in imperial units (ex. psi, degrees F, mph, etc.) or metric units for metric units (ex. bar, degrees C, kmh, etc). Note: RomRaider version 0.5.0b already includes the latest standard units ECU definitions so this step is unnecessary for this version unless you need metric units.
5. Download and install the latest RomRaider logger definitions (http://www.romraider.com/forum/topic1642.html). Choose standard or metric units. Note: RomRaider version 0.5.0b already includes the latest standard units logger definitions so this step is unnecessary for this version unless you need metric units.
6. Download and install Ecuflash (http://www.openecu.org/index.php?title=EcuFlash). Note: Ecuflash Windows versions 1.30 and later are only compatible with WinXP and Vista.
7. Download and install the latest Ecuflash ECU definitions (http://forums.openecu.org/viewtopic.php?t=3031). Choose standard or metric. Note: these updated definitions are only compatible with Ecuflash versions 1.31 and later. Note: Ecuflash version 1.35 already includes the latest metric units ECU definitions so this step is unnecessary for this version unless you need standard units.

Note: Some of the download links above require you to register to the respective forum in order to download.


Q: How exactly do I install the ECU and logger definitions?
For RomRaider:
ECU definitions -> To, install, download the file of the units you wish to use. Unzip the ecu_defs.xml file into your main RomRaider directory replacing the existing file.

Logger definitions -> To, install, download the file of the units you wish to use. Unzip the logger.xml file into your main RomRaider directory replacing the existing file.

For Ecuflash:
1. Download the file of the units you wish to use (metric or standard).
2. Delete the Subaru folder (backing up if necessary) in the Metadata directory specified in File->Options menu of Ecuflash (ex. C:\Program Files\OpenECU\EcuFlash\rommetadata\).
3. Unzip the new Subaru definition folder into the same directory.


Q. I'm having problems installing RomRaider with Windows Vista. What am I doing wrong?
Unzip and then right click the RomRaider installer and select "install as administrator".


Q. There are several different tactrix cables available. Which one do I need?
There are two different ECUs in modern Subarus that can be potentially flashed via Ecuflash:
16-bit ECU (USDM 02-05 WRX, non-USDM 01-05 WRX/STi, non-USDM 01-03 Forester Turbo)

32-bit ECU (All other drive-by-wire USDM 04+ models, drive-by-wire non-USDM 03+ models, and select drive-by-cable non-USDM 03/04 FXT/FSTi models) Note: 07 FXT/LGTs and all 08+ models cannot be currently flashed by Ecuflash.

OpenPort for Subaru WRX and Drive-by-wire vehicles (http://www.tactrix.com/product_info.php?products_id=35) -> Purchase this tactrix cable if you wish to read/flash both the 16-bit ECU and the 32-bit ECU. This includes the flash jumpers that are necessary to read/flash the 16-bit ECU (32-bit ECU does NOT require a flash jumper).

OpenPort for Subaru Drive-by-wire vehicles (http://www.tactrix.com/product_info.php?products_id=31) -> Purchase this cable if you wish to read/flash only the 32-bit ECU (you would still be able to log the 16-bit ECU, however). You can also purchase the flash jumpers separately for the 16-bit ECU later if you wish.


Q: Why do I need to install the ECU and logger definitions? Doesn't the latest RomRaider download include the newest definitions?
As of this writing, RomRaider 0.5.0b does have the latest ECU (0.8.0b) and logger (0.3.2b) definitions, however, the definitions may be updated independently of a RomRaider release in the future. The definition updates include bug fixes, additional tables/parameters and ECU support.


Q: I have everything installed and ready to go. How do I start tuning?
Read HERE (http://www.romraider.com/Documentation/RomRaiderFAQ#toc11) (describes how to read/flash your Subaru ECU with Ecuflash).

The basic procedure to tune is as follows:
1. Read the ROM from the car's ECU with Ecuflash, if necessary (if this is the first time you are tuning the car, it is always a good idea to read the ROM, keep this original in a safe place, and tune from a copy of it).
2. Open the ROM file in RomRaider (File->Open Image) or Ecuflash (File->Open ROM) to tune. Note: After reading a ROM, Ecuflash will attempt to open the ROM for tuning if it is supported by the ECU definitions. Both RomRaider and Ecuflash are ROM editors, so which one you use for tuning is a matter of preference. However, only Ecuflash can read/flash the ECU and only RomRaider can data log, between the two.
3. Make your tuning changes and save (RomRaider: File->Save, Ecuflash: File->Save ROM or Save ROM as)
4. Flash the new ROM file (or modified ROM file) to the car's ECU with Ecuflash to apply your changes. Your changes are now permanent until the next flash even if power is removed from the ECU or the ECU is removed from the car.


Q: I'm having problems reading/flashing my ECU. What can I do?
Follow the troubleshooting steps here:
http://www.romraider.com/Documentation/RomRaiderFAQ#toc12


Q: How safe is tuning and flashing my ECU? What is the worst that could happen?
http://www.romraider.com/Documentation/RomRaiderFAQ#toc8


Q: Why do I get the error message “ECU Definition Not Found” when I attempt to open my ROM in RomRaider?
Assuming you've updated to the latest ECU definitions, it's possible that your ROM revision is not currently supported. You can PM your ROM to me (merchgod) at http://www.romraider.com/forum/ and I can look at adding support for it in a future definition release.


Q: Is there a list of ROM revisions supported by the latest ECU definitions?
Yes. Check HERE (http://www.romraider.com/Documentation/SupportedECUs).


Q: Can you give me a step-by-step on how to log with RomRaider?
1. Turn on your laptop.
2. Connect the USB end of your tactrix cable to the laptop and the other end of the cable to the OBD-II port on your car (underneath the steering wheel).
3. Start RomRaider. Select Logger -> Launch Logger from the top menu.
4. In the logger's Settings menu, make sure "Control File Logging with Defogger Switch" is selected.
5. Turn the ignition key to on or start the vehicle.
6. Choose the correct COM port for your tactrix cable from the drop down box in the upper left hand corner of the logger.
7. Select the parameters you wish to log in the left pane (the greater the number of parameters selected, the greater the sampling interval will be).
8. When you wish to log to a file, turn on the defogger. When you wish to end writing to that file, turn off the defogger. Each on/off sequence of the defogger will generate a separate file.


Q: Where are my log files saved?
In the logger, go to Settings->Log File Output Location to view or change the directory where the log files are saved.


Q. How do I open my log files?
Use any spreadsheet software that supports .csv files.


Q: Do I need to install Ecuflash if I am just logging with RomRaider?
Yes, installing Ecuflash also installs the drivers for the tactrix cable which are also necessary for logging.


Q: Do I need to connect the green test mode connectors to log?
No. These should only be connected when reading/flashing the ECU, NOT logging.


Q: Does RomRaider support aftermarket wideband O2 sensor logging?
RomRaider version 0.5.0b supports the following wbO2s:
Innovate LC-1
Innovate LM-1
AEM UEGO - functionality for the AEM UEGO is currently spotty

Q: What exactly is the difference in the logger between standard parameters and extended parameters?
Subaru dealers use a diagnostic tool known as the Subaru Select Monitor (SSM) which takes advantage of a standarized protocol built-in these ECUs. This allows them to log a number of parameters (some which are not available via OBD-II) and at a faster rate. RomRaider's logger also takes advantage of the SSM protocol and allows you to log the same 'standard' SSM parameters specific to each Subaru ECU.

Extended parameters, however, are not available to the dealer. These are added separately to RomRaider's logger to allow users access to additional ECU parameters that may be useful when tuning (ex. feedback knock correction, IAM, engine load, boost error, etc). Since these must be defined manually for each ECU by analyzing a copy of the ROM, only those ROM revisions supported by the ECU definitions are also supported with extended parameters in the logger. Extended parameters are marked with an asterisk (*) at the end of the parameter's name to differentiate them from standard SSM parameters.


Q: How can I find out more about what these logging parameters mean?
A description for each extended logging parameter can be found HERE (http://forums.openecu.org/viewtopic.php?t=3030) (near the end).


Q: What is ecuExplorer and do I need it?
EcuExplorer was the first open source logger for Subarus. It has not developed for a few years now and for most users, RomRaider's logger would be a better choice. However, there are a few features in ecuExplorer that are not available in RomRaider's:

1. CEL code reader -> ecuExplorer has the ability to read CEL codes from some Subarus. However, this feature was never fully developed and it is not an OBD-II scanner. As such, it may display codes that are not set, codes that don't apply to the vehicle, or the incorrect code(s) with some ECUs.
2. Learned idle speed and ignition timing adjustments -> allows user to adjust target idle speed and overall ignition timing for applicable Subarus. These changes are volatile, meaning they will be lost when the battery is disconnected.
3. ECU reset -> allows user to reset the ECU (this capability is also available in RomRaider test release v774 and up).
4. ecuQuery -> allows user to read portions of the ECU's RAM to a file (useful for advanced users/developers only).
5. EcuFlash -> has an older command-line version of EcuFlash which allows you to read/flash the 16-bit ECU only. This might be useful for those running older versions of Windows such as Win2k or Win98/me that are not compatible with newer versions of Ecuflash.

ecuExplorer can be downloaded HERE (http://www.tari.co.za/downloads/software/release/).


Q: I have further questions that are not answered in this FAQ. Are there other resources?
Try the primary RomRaider and reflashing FAQ which goes more in-depth on a number of topics:
http://www.romraider.com/Documentation/RomRaiderFAQ

That is great Bill, do you mind posting it on my site as well?

That is great Bill, do you mind posting it on my site as well?
Done.

I <3 Tea cups

You might also note in the response to the first question that the author of EcuFlash designed it to run under Windows XP or Vista and that trying to run EcuFlash under any other operating system is a crapshoot (see http://forums.openecu.org/viewtopic.php?p=13994#13994).

;20453946']You might also note in the response to the first question that the author of EcuFlash designed it to run under Windows XP or Vista and that trying to run EcuFlash under any other operating system is a crapshoot (see http://forums.openecu.org/viewtopic.php?p=13994#13994).
I was hoping someone could do a Mac and Linux writeup about what works/doesn't work or steps to install as I don't know enough about it. I don't think there's too many users running win2k, win98/me anymore.

I don't think there's too many users running win2k, win98/me anymore.That's very true among current EcuFlash users, given that the current EcuFlash version doesn't run under any of those versions of Windows, which was the point I was trying to make. There is a substantial population out there wishing to minimize the entry price to open source ECU flashing. They want to know whether their hand-me-down laptop or some e-Bay laptop will be sufficient for open source use.

;20454465']That's very true among current EcuFlash users, given that the current EcuFlash version doesn't run under any of those versions of Windows, which was the point I was trying to make. There is a substantial population out there wishing to minimize the entry price to open source ECU flashing. They want to know whether their hand-me-down laptop or some e-Bay laptop will be sufficient for open source use.
Allright, I added notes about XP/Vista only compatibility with Ecuflash ver 1.30 and up, Ecuflash def compatibility for version 1.31 and up only, and the Enginuity download being the windows installer version.

Also added a question about ecuExplorer, alternative sites to discuss Enginuity due to the site being down and a basic overall description of how the tuning process works (i.e. read/open/tune/save/flash).

Sticky???

Good job and nice work.

this was long overdue

good work!

very good read, thanks for the info and work. Sticky please?

Great read for beginners, thank you! I agree it might not be a bad idea to make it a sticky.

very nice...many thanks to you guys for this

Great write-up! My problem, is that I have a laptop that is running Win2k Pro and ECUFlash says it needs XP or Vista. Do I need to upgrade my OS? Install ECUFlash anyway? Or is there another alternative? All I am looking for is the ability to log, not tune.

EDIT: All I need is the driver for Enginuity to recognize my 07 STi...

Props for the excelent write up on this one. Sticky?

Great write-up! My problem, is that I have a laptop that is running Win2k Pro and ECUFlash says it needs XP or Vista. Do I need to upgrade my OS? Install ECUFlash anyway? Or is there another alternative? All I am looking for is the ability to log, not tune.

EDIT: All I need is the driver for Enginuity to recognize my 07 STi...
You can try the drivers here:
http://www.ftdichip.com/FTDrivers.htm

Older versions of Ecuflash may work with win2k (and also install the drivers), probably versions 1.29a and earlier.

You can try the drivers here:
http://www.ftdichip.com/FTDrivers.htm

Older versions of Ecuflash may work with win2k (and also install the drivers), probably versions 1.29a and earlier.

1. I cannot even find v1.29a
2. I assume I need the VCP drivers?

I am going to try running it with the newest EcuFlash and see what happens. All I need is to log, so I may be okay.

I am going to try running it with the newest EcuFlash and see what happens. All I need is to log, so I may be okay.
Yes, installing Ecuflash will also install the drivers, although I'm not sure if the drivers changed from older version of Ecuflash.

Yes, installing Ecuflash will also install the drivers, although I'm not sure if the drivers changed from older version of Ecuflash.

So am I correct in that I only need EcuFlash for the driver's since I will only be logging?

Aargh! I want to go try this, but I am at work until 0600 tomorrow!

So am I correct in that I only need EcuFlash for the driver's since I will only be logging?

Aargh! I want to go try this, but I am at work until 0600 tomorrow!
Yes, you still need the drivers for the tactrix cable for logging which are installed when you install Ecuflash. If Ecuflash won't install in win2k, then you can try downloading and installing the drivers from here:
http://www.ftdichip.com/Drivers/VCP.htm

Or you can find an earlier version of Ecuflash (1.29a or earlier -> do a search on the openecu forums, I think someone posted up earlier versions a while back). If the latest version of Ecuflash installs but doesn't run, that's OK, there's a drivers directory it installs (x:\program files\openecu\ecuflash\drivers\x86)

If the latest version of Ecuflash installs but doesn't run, that's OK, there's a drivers directory it installs (x:\program files\openecu\ecuflash\drivers\x86)

Perfect, that is exactly what I was hoping for! Thanks a bunch, I'll let you know how it works!

Q: Approximately how long should it take to rewrite the existing programs for newer years? Yes, this is about the 08 STI with dual AVCS and SI-drive.

thank you IT people! Your knowledge and hard work are very appreciated!

Q: Approximately how long should it take to rewrite the existing programs for newer years? Yes, this is about the 08 STI with dual AVCS and SI-drive.
Well, someone would need to figure out how to read/flash the CANbus ECUs and develop a new cable as well. This will almost certainly be Colby (of EcuFlash/tactrix) and last I heard he was working on it. Then, the ROM(s) would have to be reverse-engineered and the definitions updated. How long both of these steps would take is impossible to guess at this point.

Teacups, thanks for the great write up!
I'm having trouble with the Enginuity logger for some reason. Instead of starting a new thread ,I thought I'd ask here.
Basically, I'm not getting all the parameters I want to log, mainly fine and rough knock correction,feedback knock, knock learning and a couple of others. According to everything I've read, solving this is as easy as downloading the latest logger defs. and loading them into enginuity. Well, I did that and still the same logger parameters as before.
Am I loading them wrong? I think I have the latest version of Enginuity, but should I re-download Enginuity and start over?
Logging and reflashing and connecting to the ECU work fine, its just that I can't seem to find these few parameters available for my use.
Any help would be greatly apprectiated!

--Brock

Basically, I'm not getting all the parameters I want to log, mainly fine and rough knock correction,feedback knock, knock learning and a couple of others. According to everything I've read, solving this is as easy as downloading the latest logger defs. and loading them into enginuity. Well, I did that and still the same logger parameters as before.
Post the ecu id shown in the lower right hand corner when you are connected with the logger and I can check and see if your ROM revision is supported or not. For extended parameter support (such as feedback knock correction, etc.), I have to have a copy of the ROM (extracted with EcuFlash) in order to define them. Likely no one has uploaded yours before, especially since it is an AT. If it is not supported, then you'll have to pull it with Ecuflash and a tactrix cable and send it to me and I can add logger as well as tuning support.

Hopefully I can get working with Colby on making ECUFlash work in Linux as it does in OSX already (easy port). I had an enginuity thread where I used an old laptop with enginuity for logging/editting running Gentoo Linux. If I had it for a reference I could make a writeup.

The FTDI drivers have been in the 2.6 kernel for almost a year now.

This would open a door for running Enginuity and ECUFlash on a small handheld mountable programmer that could be dash mounted, or a good car PC.

Hopefully I can get working with Colby on making ECUFlash work in Linux as it does in OSX already (easy port).

I wouldn't be so quick to claim that EcuFlash works on OS X. As best I can tell, it does, but if and only if you haven't installed any other software it doesn't like. It needs to to be the ONLY thing to have ever installed drivers or kexts that remotely touch any serial to USB conversion or any of the specific chips in the openport cable. Because I have a non-virgin computer (meaning I've installed hardware that installs drivers or kexts), EcuFlash will launch and allow editing of a ROM, but it will not recognize the openport cable. This makes it pretty useless. I was getting help from someone over on openecu.org, but the guy stopped participating in the thread so I have no idea what else to try.

If anyone knows much about the inner workings of EcuFlash, I will be happy to work with them and put as much time as is needed to try to figure out specifically what the problem is so that I can write up a "FOSS Tuning on the Mac FAQ" or the like.

Not to mention that Enginuity 0.4.1.b will only open only one ROM at a time, making it hard to compare two ROMs to each other (say current vs. stock).

FOSS tuning software support for OS X leaves a lot to be desired, thank god there's VMWare Fusion.

I can only get ecuflash to read/write ROMs (Vista) to the ecu. i cannot open/edit any maps.. weird..

I have the ECUFlash source. That sounds like a MAC specific problem with the openport drivers posssibly or just ECUFlash (they are FBSD drivers, similar code as the Linux FTDI drivers). I haven't seen much interest in a Linux version, but I want something that will run enginuity's logger, program some code for rough autotune of boost, timing and fuel (like the autronics has) and slap it in some small form factor and sell it. Using Linux cuts costs dramatically as I can use really cheap hardware to make this thing.

I can only get ecuflash to read/write ROMs (Vista) to the ecu. i cannot open/edit any maps.. weird..

You just have a missing def for your ROM, but ECUFlash is using the correct flash procedure.

Ive tried D/L the 080b EcuFlash Standard Defs from Kens mirror, but it comes back "unexpected end of file" in the zip..

Ive tried D/L the 080b EcuFlash Standard Defs from Kens mirror, but it comes back "unexpected end of file" in the zip..
Just DL and tested it -> don't have a problem here (XP).

Hmm.. Im on Vista.. Lemme try it again, saving to a different folder...

I can't get my ECUFlash to read the stock ROM from the ECU.

I have v 1.34 and I've connected the the 2 green tabs. I'm trying this on a 06 WRX Wagon. I get to FFFF3C80 len 68 and it gives me a readback mistmatch error.

Any help would be good. Thanks

Read the Enginuity FAQ, it has a link to a troubleshooting page.

Read the Enginuity FAQ, it has a link to a troubleshooting page.

Read it, doesn't answer my questions.

Well, I just got my tactrix cable and I cannot wait to get started on my 05 baja terbo!

thanks for the insight tea cups...

SUBSCRIBE!

openecu.org im signed up for, but im not approved by the admin yet, so its kinda useless... im hoping to read more here....

B e a utiful. Subscribing...

I can't get my ECUFlash to read the stock ROM from the ECU.

I have v 1.34 and I've connected the the 2 green tabs. I'm trying this on a 06 WRX Wagon. I get to FFFF3C80 len 68 and it gives me a readback mistmatch error.

Any help would be good. Thanks

Can you explain your problem a little more? Are you able to pull logs? At what point in the reading process does it error? After connecting the green test connectors and turning the ignition to "power on" can you hear a number of fan's cycling in the engine bay?

Can you explain your problem a little more? Are you able to pull logs? At what point in the reading process does it error? After connecting the green test connectors and turning the ignition to "power on" can you hear a number of fan's cycling in the engine bay?

I can hear the fans going on periodically, as the guide says. I can't read logs.

When I try to read from the ECU on ecuflash I select 05-07 DBW and then I turn the ignition on and immediately press ok and it gets to FFFF3C80 and then it stops and says readback mismatch.

From pressing ok to the error takes around 10 seconds.

What errors are you seeing when you try to log?

What errors are you seeing when you try to log?

I haven't tried logging yet. I'll get back to you on Tuesday.

bump to make this a sticky

I actually PMed the mod for the forum to make it happen. I guess they didn't think I was right...

I can hear the fans going on periodically, as the guide says. I can't read logs.

When I try to read from the ECU on ecuflash I select 05-07 DBW and then I turn the ignition on and immediately press ok and it gets to FFFF3C80 and then it stops and says readback mismatch.

From pressing ok to the error takes around 10 seconds.

if the fans kick on, you took too long from turning the key to clicking read.

if the fans kick on, you took too long from turning the key to clicking read.

I was responding to an earlier post to confirm that I was entering into diagnostic mode.

Anyways, I didn't drive the car for 9 days so the battery went flat and reset my ECU. I'll it again in a day or two and post with results (as I'm still expecting problems).

Can anyone post a picture of the pins on their tactrix cable? Thanks.

if the fans kick on, you took too long from turning the key to clicking read.
It also can mean that you are choosing the wrong read method.

Great info m8!

Just hope when enginuity comes back online, they all support for the ADM B4 TT ;)

It also can mean that you are choosing the wrong read method.

Let me clarify, I only heard the fans come on when I didn't try to read with ECUFlash.

Anyone have a picture of the tactrix cable pins?

This is my error if it helps:

block addr: FFFF3B80 len: 0080
[23:22:15.037] SSM2 write kernel ram block addr: FFFF3C00 len: 0080
[23:22:15.377] SSM2 write kernel ram block addr: FFFF3C80 len: 0068
[23:22:15.948] kernel get version
[23:22:15.978] readback mismatch
[23:22:15.978] reading kernel comm buffer size
[23:22:15.998] readback mismatch
[23:22:16.008] reading kernel flash buffer size
[23:22:16.038] readback mismatch
[23:22:16.038] interface close
[23:22:16.048] interface close

This is my error if it helps:

block addr: FFFF3B80 len: 0080
[23:22:15.037] SSM2 write kernel ram block addr: FFFF3C00 len: 0080
[23:22:15.377] SSM2 write kernel ram block addr: FFFF3C80 len: 0068
[23:22:15.948] kernel get version
[23:22:15.978] readback mismatch
[23:22:15.978] reading kernel comm buffer size
[23:22:15.998] readback mismatch
[23:22:16.008] reading kernel flash buffer size
[23:22:16.038] readback mismatch
[23:22:16.038] interface close
[23:22:16.048] interface close
Are you using a tactrix cable? What operating system? If it is XP/Vista (only versions of windows supported by Ecuflash 1.34 BTW), then plug your tactrix cable in and go to the device manager and look under ports. Right click the tactrix (openport) cable and update driver. Select the location for the driver and choose the Ecuflash driver location (x:\openecu\ecuflash\drivers).

XP with SP2, it should be a tactrix cable. The guy I bought it from said it was. Can you post a picture of yours?

XP with SP2, it should be a tactrix cable. The guy I bought it from said it was. Can you post a picture of yours?
http://www.tactrix.com/images/OpenPort1.3Ssm.jpg

did you try what I suggested?

Tea Cups, was wondering if you could assist.

I am getting an error when i try to read from the ecu.

This is what the log displays:

18:01:48.468] kernel get version
[18:01:49.343] interface close
[18:01:49.343] interface close
[18:02:04.062] Using interface OpenPort 1.3 Subaru TX46EF9xb42cb4d57c848f6101ada6c1370c8d3c0ea5a48c
[18:02:05.312] SSM2 init
[18:02:05.468] SSM2 ECU ID is 43 12 04 71 06
[18:02:05.578] Requesting Seed...
[18:02:05.656] Sending Key...
[18:02:06.328] interface close
[18:02:06.343] interface close

probably one of the following:
1. your are not in test mode (diagnostic connectors not connected). To verify if you are in test mode turn the ignition to on (without attempting to read with Ecuflash) and after a few seconds the radiator fans should cycle.
2. You need to wait until prompted to turn the ignition on and then immediately hit ok.
3. You are choosing the wrong read method (should be 2005-2007 dbw wrx/sti for an 06 2.5i).

All of this is in the main ecuflash troubleshooting faq linked in this faq.

probably one of the following:
1. your are not in test mode (diagnostic connectors not connected). To verify if you are in test mode turn the ignition to on (without attempting to read with Ecuflash) and after a few seconds the radiator fans should cycle.


I didn't realize that the 2.5i needed the connectors to be connected.

Your other suggestions I was doing properly.

http://www.tactrix.com/images/OpenPort1.3Ssm.jpg

did you try what I suggested?

Yep I updated the drivers same result though. I was looking for a picture of the pins.

Tea cups, it was the cable. Thanks for the help though.

where to get latest revision of enginuity ? and the defination files

where to get latest revision of enginuity ? and the defination files

Read the damned thread you just posted in. The very first post contains links for the software and the definitions.

What if i use the latest def and flash with ecuflash 1.29 ?

What if i use the latest def and flash with ecuflash 1.29 ?

Why are you still using 1.29?

The latest definitions will only work with Ecuflash versions 1.30 or greater.

Why are you still using 1.29?

because i have used it for a long time and it does its job.
i dont mind changing if its as reliable as the 1.29

all i use it for is upload the hex file to the ecu

where do i get ecuflash 1.31 ?

Use Ecuflash 1.34, the latest version.

where do i get ecuflash 1.31 ?

Please tell me you're only asking that to get a rise out of me... :eek::unamused:

It's at the top of this thread, just like all the other software. The definitions are up there as well

Is the link to the lastest version of the enginuity software not working? I keep getting invalid achive error message? Did the file get corrupted?

I'm looking for the latest version of the enginuity software, can someone help?

Is the link to the lastest version of the enginuity software not working? I keep getting invalid achive error message? Did the file get corrupted?

I'm looking for the latest version of the enginuity software, can someone help?
works fine for me

Strange. It worked for me after 20+ attempts. Not sure what I did differently. Some things I'll never understand.

I too have had the corrupt file message when trying to download from Ken's site it seems hit and miss for me.

I finally found the site that Kascade put the files up on, and transferred the other files I needed from another computer.

Great writeup, thanks so much!

Are there any repositories or collections of ecu files for our cars?

Great writeup, thanks so much!

Are there any repositories or collections of ecu files for our cars?
Some links to factory ROMs:
http://www.scoobypedia.co.uk/index.php/Knowledge/ECUVersionCompatibilityList

You can also find some at:
http://forums.openecu.org/

For tuned ROMs submitted by users and some you can buy (XPT), go here:
www.xpttuning.com (http://www.xpttuning.com)

When I try to install Enginuity there is an error

"java.io.FileNotFoundException: C;\Program Files\lib\j3dcore-ogl.dll (access is denied)"

Anyone else get this error. It seems like it's trying to read a file that dosen't exist?

Why isn't this sticky??

Yup got that on Vista. It doens't work on vista even when you do run as xp SP2. I just put it on an old crap computer and it worked just fine.

When I try to install Enginuity there is an error

"java.io.FileNotFoundException: C;\Program Files\lib\j3dcore-ogl.dll (access is denied)"

Anyone else get this error. It seems like it's trying to read a file that dosen't exist?

Yup got that on Vista. It doens't work on vista even when you do run as xp SP2. I just put it on an old crap computer and it worked just fine.
The answer to this exact question is in the FAQ in this thread.

Yay for the sticky!

ok i got an open source tune and we turned off the appropriate things to prevent CEL's
but i had one anyway, went to autozone and they checked it, it read NO Codes.
'pass' i think is what it actually read. the girl then clicked clear all codes and the CEL went away for a couple of days, now it's back on and autozone says nothing is showing up.
>???!???!?
i am cat-less DP but i have my rear O2 sensor pulled.
can anybody help!!!

When I try to install Enginuity there is an error

"java.io.FileNotFoundException: C;\Program Files\lib\j3dcore-ogl.dll (access is denied)"

Anyone else get this error. It seems like it's trying to read a file that dosen't exist?

I'm getting this error as well on Vista. Any suggestions?

Edit: Nevermind, I can read. :P

http://www.romraider.com/RomRaider/Download

clicked on download for Windows and says page not found :(

i need to log my car :(

http://www.romraider.com/RomRaider/Download

clicked on download for Windows and says page not found :(It works for me.

worked for me too..

weird it works now my comp failed me yesterday

OpenPort for Subaru Drive-by-wire vehicles (http://www.tactrix.com/product_info.php?products_id=31) -> Purchase this cable if you wish to read/flash only the 32-bit ECU (you would still be able to log the 16-bit ECU, however). You can also purchase the flash jumpers separately for the 16-bit ECU later if you wish.




Just to double check...if I am reading this statement correctly. If I purchase the above cable I will be able to log both my 06 WRX & my friend's 05 OutbackXT? We are not interested in flashing (nor will we ever be), just an occasional log for diagnostic purposes. (just to see if anything funny is happening)

Plus we are both electronic junkies and want to see what's going on when driving :)

Just to double check...if I am reading this statement correctly. If I purchase the above cable I will be able to log both my 06 WRX & my friend's 05 OutbackXT? We are not interested in flashing (nor will we ever be), just an occasional log for diagnostic purposes. (just to see if anything funny is happening)

Plus we are both electronic junkies and want to see what's going on when driving :)
The cable for Subarus is the same cable in both packages - it is just that the 16-bit ECU requires the separate jumper for flashing and that is included in that "package". Both vehicles you mention use the 32-bit ECU, so you only need the cable itself which is listed as the DBW package (and you'll be able to flash if you later decide to do so).

I bought a v2 AP a while ago off ebay and the guy included a ACCESSECU cable hooked up to a usb, he said he got it for datalogging - has anyone used one of these?, just wondering if it will work for data-logging with romraider (I have the AP to reflash) or if there is going to be a trick to using this vs the tactrix cable.

Also, do I still need ECUflash if I only want to datalog? I'm assuming I don't need to know what the current map is, though I wasn't sure if it was needed for some reason in order to get the live values.

I dont know if this has been discussed, but are you able to use a cable from a v1 cobb accessport for the use of open ecu tuning instead of a tactrix cable?

I dont know if this has been discussed, but are you able to use a cable from a v1 cobb accessport for the use of open ecu tuning instead of a tactrix cable?
nope.

nope.

Thank you.

sorry noob here....... so i want to load an xpt stg 2 map, i bought the tactrix cable and im downloading the map, what exactly do i have to do now? im confused? lol, and should i buy a gm bcs?

sorry noob here....... so i want to load an xpt stg 2 map, i bought the tactrix cable and im downloading the map, what exactly do i have to do now? im confused? lol, and should i buy a gm bcs?
As a customer, you can get support for your XPT map here:
www.xpttuning.com

sorry noob here....... so i want to load an xpt stg 2 map, i bought the tactrix cable and im downloading the map, what exactly do i have to do now? im confused? lol, and should i buy a gm bcs?

You will be much happier with the GMBCS and the XPT stage 2 map for it. I tried them both.

With the GMBCS map boost comes on quicker, stronger and smoother than with the non-gmbcs XPT stage 2 map.

nope.

Thanks. I dont want to give incorrect advice. I sold my acceport to somebody in AL and they wanted to use the cable for open programming. :diaf::diaf::diaf: I havent ever tried it as I have had the tactrix for quite a while...

alright thanks guys, i was just wondering about the whole logging thing

"OpenPort for Subaru Drive-by-wire vehicles (http://www.tactrix.com/product_info.php?products_id=31) -> Purchase this cable if you wish to read/flash only the 32-bit ECU (you would still be able to log the 16-bit ECU, however). You can also purchase the flash jumpers separately for the 16-bit ECU later if you wish."


I may be a little thick here, but perhaps someone can help. I want to log, and had tried to use the APv2 cable and all the associated software from cobb and tari, but have had no luck even connecting to the ecu.

I really want to log, and when i looked at this sticky, and tried to find which tactrix cable to buy, i just get "product not found" from the link above on the tactrix site.

Can someone point me to a tactrix cable for my 06 wrx?

"OpenPort for Subaru Drive-by-wire vehicles (http://www.tactrix.com/product_info.php?products_id=31) -> Purchase this cable if you wish to read/flash only the 32-bit ECU (you would still be able to log the 16-bit ECU, however). You can also purchase the flash jumpers separately for the 16-bit ECU later if you wish."


I may be a little thick here, but perhaps someone can help. I want to log, and had tried to use the APv2 cable and all the associated software from cobb and tari, but have had no luck even connecting to the ecu.

I really want to log, and when i looked at this sticky, and tried to find which tactrix cable to buy, i just get "product not found" from the link above on the tactrix site.

Can someone point me to a tactrix cable for my 06 wrx?
Looks like the old version of the cable is gone now. The new one is here:
http://www.tactrix.com/product_info.php?cPath=23_25_32&products_id=40

Looks like the old version of the cable is gone now. The new one is here:
http://www.tactrix.com/product_info.php?cPath=23_25_32&products_id=40

Crap. I was under the impression it was $75. This changes things. that $200 was earmarked for a sway bar.

Guess I am going to try harder to log with the APv2 for now, unless i can find a used one.

couple of questions I didn't see covered:

1> can this be used with the generic "ELM 327" units you see on ebay all the time (I have one I used for my other cars before I got my 06 STi this week).

2> can it be used in *READ ONLY* mode (I have ZERO desire to tune yet. I want nothing to do with messing with the ECU right now. I only want the data!)

Thanks!

couple of questions I didn't see covered:

1> can this be used with the generic "ELM 327" units you see on ebay all the time (I have one I used for my other cars before I got my 06 STi this week).
No, but some of the generic obdii cables on ebay may work for logging only. As far as which ones, hard to say, you may want to do a search and see what people have had success with. With the cheap cables, you can sometimes run into driver issues.

2> can it be used in *READ ONLY* mode (I have ZERO desire to tune yet. I want nothing to do with messing with the ECU right now. I only want the data!)
Then you just need to log.