Q: How does RomRaider allow me to tune?
You must first retrieve a copy of your ECU's image from your vehicle by using an additional program called EcuFlash (discussed below). A special cable, manufactured by Tactrix, is used to connect your laptop to the OBD-II port in your car (which is located below your steering wheel). Once a copy of your image (also known as a ROM) is downloaded from the vehicle's ECU to your computer, you can then use RomRaider to make tuning changes to this ROM. Once you’ve finished with your changes, you can then save a copy and transfer this edited image back to your vehicle's ECU in a process known as flashing. As long as you keep a back-up copy of your original image, you can revert back to it at any time. In addition to tuning, RomRaider also allows you to data log your Subaru to monitor the results and safety of your tune.


Q: I want to log and/or tune my Subaru with RomRaider. What do I need to do?
1. Purchase a Tactrix OpenPort cable HERE (http://www.tactrix.com).
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).
5. Download and install the latest RomRaider logger definitions (http://www.romraider.com/forum/topic1642.html). Choose standard or metric units.
6. Download and install the latest version of 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://www.romraider.com/forum/topic3808.html). Choose standard or metric. Note: these updated definitions are only compatible with EcuFlash versions 1.31 and later. Note: If you are attempting to flash a CANbus ECU, you must use EcuFlash version 1.40 or later (do NOT use older versions).
Note: Some of the download links above require you to register to the respective forum in order to download.


Q: Can I potentially tune any Subaru with the OpenPort cable and EcuFlash/RomRaider?
NO, older models are not supported by the hardware and software. You CANNOT tune the following:
* ANY 2001 and prior USDM Subarus, USDM 2002-2003 Impreza RS/Legacy/Forester, USDM 2004 Impreza RS
* ANY 2000 and prior ADM/EDM/JDM Subaru, 2001-2002 (and some 2003) ADM/EDM/JDM non-WRX/STi models


Q: Which version of the Tactrix OpenPort cable do I need?
http://www.romraider.com/Documentation/RomRaiderFAQ#toc8


Q: How exactly do I install the ECU and logger definitions?
For RomRaider versions 0.5.1b and later:

To install the ECU definitions:

1. Download the latest ECU definitions file available HERE (http://www.romraider.com/forum/viewtopic.php?t=360). Download the file of the units you prefer (either metric or standard).
2. Unzip the ecu_defs.xml file into your main RomRaider directory (or in another directory of your choice where it is unlikely to be moved or deleted).
3. Run Romraider and select "ECU Definitions" -> "ECU Definition Manager" from the menu bar.
4. If any definitions files are listed, select each file and click "Remove".
5. Click "Add" and select the location of the unzipped ecu_defs.xml file.
6. Click "Save".

To install the logger definitions:

1. Download the latest logger definitions file available HERE (http://www.romraider.com/forum/topic1642.html). Download the file of the units you prefer (either metric or standard).
2. Unzip the logger.xml file into your main RomRaider directory (or in another directory of your choice where it is unlikely to be moved or deleted).
3. Run Romraider's logger ("Logger" -> "Launch ECU Logger") and select "Settings" -> "Logger Definition Location" from the menu bar.
4. Select the location of the unzipped logger.xml file.

For EcuFlash:
1. Download the latest EcuFlash definitions file available HERE (http://www.romraider.com/forum/topic3808.html). Choose the file with 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: Why do I need to install the ECU and logger definitions? Doesn't the latest RomRaider download include the newest definitions?
The RomRaider software (starting with version 0.5.1b) does not ship with any ECU or logger definitions. These will have to be downloaded and installed by the user in order for the software to be functional. This is to ensure that you have the latest version of the ECU and logger definitions at the time when you first install RomRaider. You also want to periodically check to see if there are new versions of the ECU and logger definitions in the future as these updates may include bug fixes, additional tables/parameters and additional ECU support.


Q: I have everything installed and ready to go. How do I start tuning?
Read HERE (http://www.romraider.com/Documentation/RomRaiderFAQ#toc14) (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#toc16


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


Q: Why do I get the error message “ECU Definition Not Found” when I attempt to open my ROM in RomRaider?
Assuming you've installed the ECU definitions and they are the latest version, 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. Or you can post your ROM in the ECU and logger definitions sub-forum at the RomRaider site (Note: we do not allow commercial ROMs to be posted).


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 OpenPort 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.1b supports the following wbO2s:
Innovate LC-1
Innovate LM-1
AEM UEGO - functionality for the AEM UEGO is currently spotty


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.

Can I use the CANBUS APv2 OBDII connector/USB cable to datalog on RomRaider? Or do I need Tactrix, I ONLY need to datalog. If I need drivers where to find them? Thx.

The old APv1 allowed for data logging on the older models. I would assume that you could do the same with the APv2 cable, but I may be wrong.

can someone point me in the direction of finding a map that i could download?

www.osecuroms.org

thanks alot bro...really appreciate it....trying to find a good map to use....my buddy keeps on telling me not to use an aggressive map...what do you think... i have a stock 06 wrx

no, you can't use the ap ver 2 cable for logging with romraider or reading/flashing with Ecuflash.

can i use romraider with linux (ubuntu)?

may have been coverd but there are 5 pages and i just need a quick answer, with romraider on the 2.0 cable there are no definitions or a logger with it so where do i store them? sorry new to this

may have been coverd but there are 5 pages and i just need a quick answer, with romraider on the 2.0 cable there are no definitions or a logger with it so where do i store them? sorry new to this
DL them and use the Ecu Definition Manager and the logger definition manager with RomRaider 0.5.1b RC4 to add them.

cool thanks got it

is there even away to flash a 2004 rs.. any way or can i replace the ecu with a newer better moddel oem or aftermarket

is there even away to flash a 2004 rs.. any way or can i replace the ecu with a newer better moddel oem or aftermarket
No, there's no way to flash 2004 and prior NA models. You cannot swap in a newer ECU (i.e. 2005+ N/A) as those cars have drive-by-wire throttle (and even if it didn't still wouldn't likely be compatible). Swapping in a standalone ECU would be possible but outside the scope of an open source reflash discussion and not worth the cost unless you've added a turbo, etc.

I am trying to datalog for the first time with the Openport 2.0 cable. I am choosing the right com port 4 (Openport 2.0) but cannot connect to the ecu. Have the latest defs and all.

Do I need to add the Ecuflash defs to the ECU Manager in order to log? I only have the Romraider ECU def loaded in in ECU Manager but none of the 20 or so Ecuflash defs. Just trying to figure out what's going on.

I am trying to datalog for the first time with the Openport 2.0 cable. I am choosing the right com port 4 (Openport 2.0) but cannot connect to the ecu. Have the latest defs and all.

Do I need to add the Ecuflash defs to the ECU Manager in order to log? I only have the Romraider ECU def loaded in in ECU Manager but none of the 20 or so Ecuflash defs. Just trying to figure out what's going on.
No, Ecuflash defs do not go in the ECU definition manager for RomRaider. Are you using RomRaider test release 0.5.1b RC5 found in the development forum at the RomRaider site? If so, make sure you are not using an old shortcut - should read "0.5.1b RC5" in the title bar when you are running RomRaider. You also need to install Ecuflash 1.40 and do the firmware update if necessary. The firmware update for the OP 2.0 occurs in Ecuflash when you attempt to read from the ECU - so do that first.

EDIT: Also, if you are running Vista, make sure you install RomRaider as an admin by right-clicking the RR installer and selecting "run as admin". You may also need to do the same thing when you run RomRaider (romraider.exe).

EDIT: Also, if you are running Vista, make sure you install RomRaider as an admin by right-clicking the RR installer and selecting "run as admin". You may also need to do the same thing when you run RomRaider (romraider.exe).

I had to do just that in Vista. You have to run RR as admin for the OP 2.0 for some reason to get the logger to connect...

Running:

- XP
- Romraider 0.5.0 Beta Build # 83 =>> I will uninstall and load 0.5.1b RC5.
- EcuFlash 1.40.2178

".....The firmware update for the OP 2.0 occurs in Ecuflash when you attempt to read from the ECU - so do that first...."

I interpret the above comment as :

1. Run EcuFlash and hit the "Read from ECU" icon. Doing so creates the vehicle interface between ECU and OP 2.0 cable.

2. Run Romraider and start logging.

Part of my confusion aside from running the Beta version of Romraider was I just wanted to log and did not think it was necessary to read my ECU first on EcuFlash.

I will try the above two steps and report back.

It finally worked (Tea Cups thank you). I am able to log now on my CAN BUS 07 FXT with OP 2.0

I was not able to read the ROM but the fact of starting EcuFlash first (before opening RomRaider) and trying to read the ECU must have loaded the OP2.0 missing driver and allowed me to finally be able to datalog.

This is the error message, just for giggles as I am not interested in copying or flashing my ROM at this time, I just want to datalog.

14:51:28.731] Version 1.40.2178
[14:51:28.751] 19 memory models read.
[14:51:28.751] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[14:51:29.031] 308 ROM metadata models scanned.
[14:51:29.031] checksum module "subarudbw" loaded.
[14:51:29.031] flashing tool "wrx02" loaded.
[14:51:29.031] flashing tool "wrx04" loaded.
[14:51:29.031] flashing tool "sti04" loaded.
[14:51:29.031] flashing tool "sti05" loaded.
[14:51:29.031] flashing tool "mitsukernel" loaded.
[14:51:29.031] flashing tool "mitsukernelocp" loaded.
[14:51:29.031] flashing tool "shbootmode" loaded.
[14:51:29.031] flashing tool "shaudmode" loaded.
[14:51:29.031] flashing tool "subarucan" loaded.
[14:53:23.406] J2534 API Version: 04.04
[14:53:23.406] J2534 DLL Version: 0.50.2176 Oct 20 2008 17:50:12
[14:53:23.406] Device Firmware Version: 1.01.2145
[14:53:42.433] kernel get version
[14:53:42.703] SSM2 init
[14:53:42.753] SSM2 ECU ID is 4E 12 58 41 07
[14:53:42.804] Requesting Seed...
[14:53:42.854] Sending Key...
[14:53:42.894] interface close

So were you able to log with the AP v2 cable?

It finally worked (Tea Cups thank you). I am able to log now on my CAN BUS 07 FXT with OP 2.0

I was not able to read the ROM but the fact of starting EcuFlash first (before opening RomRaider) and trying to read the ECU must have loaded the OP2.0 missing driver and allowed me to finally be able to datalog.
It writes the new firmware to the cable by doing this. The firmware has to be compatible with the OP 2.0 DLL that is installed by Ecuflash, otherwise it won't work, which is what your problem was. As far as the Ecuflash read failure, you need to make sure you are in test mode first. Also, could be your timing between turning the ignition on and starting the read. Read the Ecuflash troubleshooting section of the RomRaider FAQ.

Tea Cups,
Thanks for all your time and effort with all the questions.
Happy Thanksgiving!
dm

Tea Cups,
Thanks for all your time and effort with all the questions.
Happy Thanksgiving!
dm
no problem.
Happy Thanksgiving!

So were you able to log with the AP v2 cable?
No, I ended up buying the Tactrix OP2.0.

Ah ok, seems like it would just take a driver for the dongle or something in order to be able to use the AP2 cable...

Noob to this , having problem with Romraider

I successfully downloaded the rom from the car, and saved it. When I try t open it in Romraider, the progress bar says promising things, such as creating tables, populating tables, finalizing, then done, bu the screen stays black, nothing else.

Latest Java installed, all the latest ecu def's installed, ect.

Any ideas?

you have to click on what table you want to look at on the left side. then something will appear in the black.

what happened to the turboxs wideband support?

its not in the new version of romraider and i NEEDZ it

Where are you guys getting your Stage 1 roms from?
for 04 WRX?

what happened to the turboxs wideband support?

its not in the new version of romraider and i NEEDZ it

It was alpha quality in that it used features from another program I wrote a long time ago. Kascade tore it out when pulling out dead-ish code.

When flashing a map onto the ECU I...

-Opened EcuFlash
-Connected my cable
-Connected the Green Connectors
-Connected the Init connector
-Opened the map I was going to flash
-Clicked Write to ECU
-Turned Key to "ON"
-Clicked Okay
-Done...
-Disconnected the Green Connectors
-Disconnected the Init connector

Did I miss something or do something wrong here...?

Just a HUGE heads up as I see this WAY too often: YOU NEED AN OFFSITE BACKUP OF YOUR STOCK MAP.

So email it to yourself if you have a webmail account... :D

Thanks for the guide, I was wondering though what exactly is a test write and how do you do one?

A test write in Ecuflash is one of the selections includiing the usual read and write. It basically does everything in the flashing process except the actual flash, allowing you to discover problems beforehand.

My biggest fear is that it will erase or mess up and I will lose my protune when I get my ECU information. Has this ever happened? I only want to log.

My biggest fear is that it will erase or mess up and I will lose my protune when I get my ECU information. Has this ever happened? I only want to log.
Logging has no risk whatsoever and will not change your tune.

Thanks for the quick reply. I am hoping to find my cable and contribute to the road dyno thread.

Car: saab 92x linear
Engine: EJ253

I recently bought a tactrix cable and I started logging for using Romraider, driving around. I then desided to try and pull the ROM from the ECU, I put the car in test mode. (green connector). Then I opened ECUFlash, and yes I have the ECU defs installed. Then I hit read rom, and go this error message no madder which DBW setting I used.

[11:26:07.746] Using interface OpenPort 1.3 Universal TX45rBqS9d1ab7c956c5f7aae78bab98f7276a5dc3826586
[11:26:08.557] kernel get version
[11:26:08.938] SSM2 init
[11:26:09.088] SSM2 ECU ID is 3E 12 08 41 06
[11:26:09.188] Requesting Seed...
[11:26:09.238] Sending Key...
[11:26:09.879] interface close
[11:26:09.879] interface close

any ideas?

just one question, can i use the cable that came with my cobb AP and connect it to my computer to run romraider?

just one question, can i use the cable that came with my cobb AP and connect it to my computer to run romraider?
If it is Accessport ver 1 cable, then you can log with RomRaider if you get a serial to USB converter (Belkin is a good one). However, that is it. You will not be able to flash your ECU (i.e. tune). AP ver 2 cable, you will not be able to log at all with RomRaider.

does anyone know how i can tell what tactrix cable i have? i searched but no results. i had originally bought one for a 2004 STi but after a year i have just located it in my garage. there is no stickers on it indicating what version it is so it could be 1.2 to a 2.0? thanks

If it is a year old, it won't be the 2.0. It will show your cable's version in Ecuflash.

so you mean the 2.0 just came out in the last year?

Yes, not to mention it looks different than the previous cables. It has a detachable cable and a translucent cover with led lights.

I am a newbie, and Ive read as much as I can find out including this entire thread. I get this error:

[20:11:47.515] J2534 error [device not responding].
[20:11:47.515] unable to connect to vehicle interface.
[20:11:47.515] interface close
[20:13:56.812] J2534 error [device not responding].
[20:13:56.812] unable to connect to vehicle interface.
[20:13:56.812] interface close
[20:14:10.187] J2534 error [device not responding].
[20:14:10.187] unable to connect to vehicle interface.
[20:14:10.187] interface close


How do I know what com port to use?

woot got it. Just had to restart my laptop.

Where can I get the Ecuflash? The link not working!!!!

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.

I'm having the same exact problem. I don't see the parameters "feedback knock correction", etc... How can this be fixed? and what do you mean by saying "you have to have a copy of the ROM to define them"? is this different for every rom?

And I have a 2007 wrx tr if that matters.

Also was wondering, tea cups, are you the person writing the definitions for RomRaider?

I'm having the same exact problem. I don't see the parameters "feedback knock correction", etc... How can this be fixed? and what do you mean by saying "you have to have a copy of the ROM to define them"? is this different for every rom?

And I have a 2007 wrx tr if that matters.

Also was wondering, tea cups, are you the person writing the definitions for RomRaider?
You have to be connected to your car's ECU in order for the extended parameters to appear as they are ECU specific. That is, you have to have the tactrix cable hooked up, romraider running, and your car's ignition on in order to view any extended parameters. If they still don't appear (make sure you can actually log), then that could mean either you have old definitions or your ECU is not supported. If your ECU is not supported, that means that no one has uploaded your specific ROM revision before for support to be added (there can be multiple revisions for a particular car, so it doesn't matter if there's already support for a USDM 07 WRX MT, there can be multiple "versions" for that car).

Yes, I do the defs for RomRaider (my screen name at romraider is merchgod).

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.

You have to be connected to your car's ECU in order for the extended parameters to appear as they are ECU specific. That is, you have to have the tactrix cable hooked up, romraider running, and your car's ignition on in order to view any extended parameters. If they still don't appear (make sure you can actually log), then that could mean either you have old definitions or your ECU is not supported. If your ECU is not supported, that means that no one has uploaded your specific ROM revision before for support to be added (there can be multiple revisions for a particular car, so it doesn't matter if there's already support for a USDM 07 WRX MT, there can be multiple "versions" for that car).

Yes, I do the defs for RomRaider (my screen name at romraider is merchgod).

OK this makes sense. But still doesn't fix my problem. And the problem is that it is not supported because I did everything you mentioned (having everything connected and ignition on etc, AND it does actually log.)
I got a reflash at the dealership recently for "misfire" fix, so maybe thats why?

Anyway,

I have 2 questions:

1. Can I give you my ROM so you can update the def's for it?
2. If I "read from ecu" using ECUFlash, would it leave any marks on the ECU that it has been touched? I mean its not write to it its supposed to just "read" but still wanna make sure. Because I don't want the warranty to be denied with the car and ECU and everything

Thanks

Yes, you can either PM me the ROM at the romraider site (merchgod) or post it there. Make sure you do it fairly soon as the next update will be in about a month.

Reading doesn't change anything as far as the ROM is concerned. The fact that you pulled the ROM should not be detectable by the dealership as far as we know.

Just sent you my ROM at romraider. my username overthere is _AraSh_.

So when are the new definitions coming up?

So when are the new definitions coming up?
hopefully about a month. Can't say for sure, though.

I just bought a 2004 STI and I downloaded rom raider but I am having trouble finding any one who has a tactrix open port 2.0 that is not out of stock. Are these hard to comeby? I would like to buy one but I don't want to pay the prices that they have on ebay. Am I just gonna have to eat it and buy one?

-Thaks

New Definitions needed highly :(

Hey guys, I just came from the VW world where this type of thing is totally taboo for some reason.
Once I got my 03 WRX about a month ago, I knew I had to have this! Well, I got my cable and everything yesterday, reformatted my laptop, and got it all setup last night and went for a little drive. It is all working perfectly! :D

I don't think I am going to get into tuning my own car for a while, but I will be datalogging and possibly playing with it a little.

My question is this, with the VW, there was programming available for totally stock cars that would net huge gains in performance. I haven't seen anything like this for the Subaru, however, I have heard that the stock programming is not perfect. Is there any benefit of getting an upgraded map for a car with just a 3" cat back?
I would like to optimize the car for now until I can get all the parts required for a stage 2 upgrade in a couple of months.
I would also like to add launch control to the car asap, so if there is a better stock map available, it would be a good time to add both of these to my car right now.
Before I would do anything, I'd like to do some logs and post them up to make sure everything looks ok with my car. Which parameters would I need to log in order to do this?

Thanks RomRaider and all the experts here that freely release all their hard earned info for free. I will be donating to the cause shortly!

Colin

subscribed