Using RomRaider to edit tunes ( ROM) files OFT and non- OFT
 

Using Romraider to Edit Modify Tune files

Disclaimer: This information is provided in good faith, however their may be errors or omissions. Use this info at own risk

Tune (ROM) must be in standard binary/hex format ie .bin extension. Complete ROM for BRZ/86 is aprox 1280K bytes long

You Tune ROM (bin/hex) file will have a calibration identifier CALID like ZA1JA01G you will also need a matching definition file RR_ZA1JA01G.xml

The Tune or ROM (bin/hex) is the file to be loaded into your ECU it contains a mixture of program instructions and tune tables.

The Definition file or xml file is the index into the ROM which tells RomRaider (the editor) where to locate the tune tables withing a ROM. The ROM and XML must match else you will alter incorrect areas of the rom or actually alter program code instead of tune tables.

Obtain latest romraider software
general instructions and info at romraider site below

www.romraider.com


While Romraider will let you load multiple definitions at once its best if you only load ONE definition into romraider at time,
this reduces the risk of you editing a tune file with the wrong definition.


For OFT Tunes

Always use the Definition files from the OFT download site

DO NOT use Romraider definitions from the Github site for OFT tunes.

The OFT tune can have modifications to the Calibration ID of the tune file and you need to use the specific OFT definition's which have had the corresponding modifications made to the definitions to match the OFT tunes

Always use the OFT definition specific to your tune revision ie
Use OFT V1x definitions for OFT V1x tunes
Use OFT V2x definitions for OFT V2x tunes
and oft V3 defs with oft V3 tunes
and OFT V4 tunes and defs different again
Mever mix and match use def that come with each tune revision only with that revision
Use the definition that matches your rom type calibration ID ie ZA1JA01G
Definitions for OFT V2x tunes are in the download zip files with the tuned ROM's.

Some OFT Tunes have a Patch for Launch Control and Flat Foot Shifting LC/FFS. Make sure the ROM and definition are matched.
If you see BLACK boxes in romraider that are BLANK when trying to edit LC/FFS STOP , this means the ROM does not have the Patch if you edit a non patched rom you will brick your ecu if you flash it.
Patched ROMs will show green box's with values in them as per example image attached below at end of post.
Too avoid this problem always download the full tunes and definition tune pack and only use the defs that come with the pack to edit rom from same pack.
dont use old defs on new roms and dont use new roms with old defs unless you rearly understand what your doing


Obtain OFT tune definitions from here
www.openflashtablet.com
http://openflashtablet.com/Automotiv...ads/index.html

Many OFT roms have the calibration ID internally adjusted so the OFT will load the ROM.
This is done so that OFT users can load the latest ROM series compatable with their vehicle.
For example an OFT user has original stock ROM calid of 700C. The OFT will only let them load 700C roms for safety.
However the latest calid compatible with their car is B01C. The 700C tuned OFT rom is actually based on a B01C rom (OFT V2 tunes) then modified to "look" like a 700C so the OFT will load it
This allows the person with an old calibration ID to be running the latest factory revisions as well as the OFT rom tune modifications.
Unfortunately this also "tricks" romraider, so the OFT guys produce special modified Romraider definitions to match their tuned roms. That is why you must use the OFT definitions for OFT roms.


Many OFT roms have not had the checksums corrected so romraider will pop up a message saying checksum is incorrect. you can use romraider to correct checksum, but the OFT and openflash manager software
will correct the checksum for you when you load the rom into the OFT.


For STOCK ROM,s (tunes) or NON OFT ROMs

Use the definitions from the github site

Do NOT use these for OFT tuned ROM files , these definitions for Stock ROMS or NON-OFT roms only.

https://github.com/TD-D/SubaruDefs/t.../RomRaider/ecu






General checks

Always Check some known tables in the ROM like the "Primary OL Fuel Table" and the "BASE TIMING B" table make sure tables have sensible values in them and that the axis of the tables are correct. If the table contains rubbish or wildly incorrect values then something is wrong your ROM and definition are mismatched DO NOT Flash the ROM.

Example, their might be slight differences in your rom. see pictures at end of post below


If you see weird table corruptions or strange values in axis X or y stop do not edit or flash


If romraider brings up errors about "Possible corrupt rom " stop







http://i.imgur.com/6W3B1GH.png

http://i.imgur.com/qnMNFVd.png

Only ever have ONE definition file loaded into Romraider at a time. Unless your very familiar with romraider use and are transferring data from one rom type to another.

Don't ever have two definitions for same rom type open in romraider as it will not know which one to use, even if the filenames are different as romraider works off calid ie an OFT V1 and V2 def for same calid or OFT def and non OFT def for same calid.

Its good practice to save your modified rom to a new filename, then re-open it and check your work carefully.

See video here

https://youtu.be/IaxnBe-INRg


https://youtu.be/IaxnBe-INRg


Some Tune Tweaks you made consider
http://www.ft86club.com/forums/showthread.php?t=74754








Further Reading on Tuning in general

Very good post here with lots of links to tuning info


http://www.clubwrx.net/forums/tuning...r-tactrix.html


Also google
"Bad Noodle Tuning Guide"
http://forums.nasioc.com/forums/show....php?t=1626520







Video tutorial by @JB86'd

[ame="https://www.youtube.com/watch?feature=player_embedded&v=hvmVOxI3GPs"]OFT & RomRaider Tutorial - YouTube[/ame]




.

And for those who don't know what these should look like:

http://i.imgur.com/qnMNFVd.png http://i.imgur.com/6W3B1GH.png

Not all ROMs will have the exact same values, but they should have similarly smooth gradual changes.

I feel like this is a stupid question but how do I save changes made to a rom as a .bin

in romrader click save rom as, then name it romname.bin

Just that easy I guess I over think some stuff in fear of bricking my ecu

What if I want to compare two different roms? One is A00G and the other is A01G? So I shouldn't open both at the same time?

At the moment i'm viewing them with both .xml def files in the file manager. Is this wrong?

Romraider can open several roms ar a time and they can have different defs like you are doing ie opening an A01G and A00G. This is fine once you become familiar with romraider.

The danger is having say an 700G OFT def and a 700G standard rom raider def in romraider at same time or trying to open a 700G stock or non oft rom and an 700G oft rom as the oft 700G def and rom are actually A01G and calid hacked, that kind of mismatch can result in bricked ecu waiting to happen. It ok if your aware of the oft calid changes but a trap if your not. The oft roms also have a lc\ffs patch which you need their defs to alter, however using an oft def on a stock rom and trying to alter lc\ffs may also result in bricked ecu as instead od altering a table your altering program code.

very importenat to match defs and roms.

was just trying to be safe for novice people.

@steve99 @Fizz is not using OFT ROMs or definitions.

Fizz, you can load up all definition files so long as they are different. In fact you can have have more than one of the same, it uses the top one 1st if there are 2 of the same definition. Generally only have one per cal ID to make you life easier, I have pretty much every current FT86 Cal ID loaded into mine.

i think he had some old oft one loaded from his oft days as in another thread he had weird table values, once he deleted them all sweet or he was in compare mode as you worked out :D

@Fizz if you only use the defs I sent you then you'll be golden. These aren't suitable for any OFT ROM use without possible issue, so comparing to the OFT files isn't a good idea.

I'l update this statement, if you want to compare OFT ROMs using my definitions use these v2.0# OTS Tunes:
ZA1JB01C
ZA1JA01G

Those are NOT Cal ID edited and therefore will work with standard definitions.

Correct me if I'm wrong, but the OP states that this Free software can edit a stock tune. Does this mean that i can use my laptop and OBDII-USB cable to edit my stock BRZ tune to do any of the following:

* Flash newest ECU updates
* fix idle Dip
* Fix torque Dip
* tune Launch control/flat foot shift

all without costing me anything? Granted one would need to know how to edit these perimeters. . .

Well not that simple

Yep Romraider is free.
But you need a device that is capable of extracting and writing the rom from your ECU

Cheap Obd cables will not do this

the cheapest device to read and write roms is a Tactrix and you need the Ecuflash software see links below.

lc and ffs are not available in stock rom firmware its an addon patch done by the openflash guys.

if tactrix\ecuflash looks a bit daunting then buy yourself an openflashtablet.

One doesn't simply "fix the torque dip" by tinkering about with the stock rom on a stock car..

Is there a way to add DTC error code switch tables to the OFT OTS tune files? I've managed to add the idle and in gear MAF tables required for lowering the cold start with a cattless header.

Even though the OFT 2.7 xml definition has the error on/off switch table listed, it doesn't show in RR. I'm guessing that I need to figure out where it is located in memory on the ECU or something.

I'm working with the J and K roms which are based on the A01J and A01K roms.

See if the error dtc codes are in the romraider defs on github.

then you need to check with hex editor your oft rom and see if its been calid hacked, ie check all three instances of the calid in the rom are the same, if all 3 the same then you can use the romraider def from github.

if the dtc you want are not in giyhub you would have to ask the romraider guys to dig arround in the rom for the ones you want.

I've already checked using a hex editor and know which rom the oft 2.xx is based on (A01J and A01K for the middle east cars). The DTC switch table is mentioned in both xml definition files (OFT and Github/RR). The tables simply don't show up in romraider. My guess is that they're missing the information related to their location on the ECU memory.

Thanks for suggesting asking the romraider forum. I guess that will be my only option.

i compare between ja01j and b01c and there are 47 table that ja01j does not include it and 41 of it is DTC codes .

some definitions especially the more popular ones like C\D and G rom contain more defined tables than other definitions.

if you specificly need some DTC defined for your rom then post in the romraider forum

in the ecu and logger def thread
http://www.romraider.com/forum/viewf...0367225f9fd79c
@Td-d is a very helpfull guy

Those guys work for free so it nice to make a small donation for their efforts

anybody messed with cam angle timing? im running an HKS equal length catless header now, and just wondering if theres optimized cam angles floating around for that header. I cant remember what kind of header @Shiv@Openflash used to set the EL tunes.

Added warning and some checks you can do when editing launch Control and flat Foot Shift parameters to first post to determine if your rom has LC/FFS patch.

http://www.ft86club.com/forums/attac...1&d=1443676411

AVCS or cam/valve timing tables
 

Edit; I've updated the pics to show my best tables for economy and power. @troek, as far as I know, I'm the only one brave, fearless, or foolish enough to extensively modify the Intake and Exhaust AVCS Safe tables. If you are still interested you can try copying the values in these pics to your own AVCS Safe tables, or send me an IM, and I'll see what I can do.

:burnrubber:

@steve99 would you be able to do a similar write up of the steps to start with OFT/OTS rom files with their corresponding def files and flashing them using the TACTRIX/ecuflash instead of OFT? Looks like ecuflash needs def files while writing rom files. Should we use non-OFT def files or OFT def files with the OFT/OTS tunes?

While I have an OFT and a tactrix and it can be done, I have an ethical problem with spelling out exactly how to achieve flashing oft roms with tactrix as the roms are supplied for use with OFT and part of the OFT pricing included rom development.

Romraider and ECUFLASH definitions are very different, romraider defs have no "flashing" information in them they just have information for editing rom tables. The OFT contains info on how to flash rom to car , checksum correction ect

Ecuflash definitions have the information for editing the tables and in addition have information required to flash the rom such as vehicle type type of rom, flashing method check sum algorithm as a tactrix cable can flash many types of vehicles eg subaru mitsubishi ect.

Tactrix has very little safguards to prevent uses from writing incorrect roms to the car, OFT is a far easier product to use and has many safeguards built in. It also makes logging far easier and simpler.


Honestly if your not familiar with rom,defs.flashing ect its far easier and safer to buy an OFT and the logging functionality big gauge displays and tuning alerts where you can set alerts for oil/coolant temps knock IAM drop, fuel trims whatever are very useful

Ok so this is what I gather:

1. If the plan is to flash in roms OFT is the better/safer route

2. If one only wants to log data Tactrix will work initially but OFT can do logging as well.

OFT wins! :)

for tactrix logging you need to know the ecu ram addresses for the parameters and it changes for each rom calid, the romraider guys who work part time for donations are the only guys in general who did these addresses out

Shoot... Should have waited to order the Tactrix cable. Well its always good to have one I guess

I'm getting an error when trying to save a file in romarider after i have edited a few parameters, i can't get it to save.

If post up the eroor or a screen shot and maybe a copy of rom and definition it would help

Are you able to copy and paste between two tables?

I couldn't, and also saving didn't work as well. In my case I simply had to change Romraider's locale settings to (US-) English.

If your system locale is already English, check your Java version. On my Linux desktop, I'm using a 64 bit Oracle Java binaries. 32 bit exposes all forms of errors with my window manager. I simply ignore the error startup message.

I can't seem to download the XML Definitions off the OFT website.
http://openflashtablet.com/downloads/
I get 404: Page Not Found.
Tried different browser and clearing cache.

any chance someone could upload somewhere so I can download?

Cheers

thats a rearly old link

go the to www.openflashtablet.com web site and navigate to downloads or go here

http://openflashtablet.com/Automotiv...ads/index.html

you want 2.07 tunes and xml files are in with tune pack

Looks like they updated the site. New link: http://www.openflashtablet.com/downloads/

@steve99

Has anyone figured out how to force emissions readiness for our ecu and roms? I remember the older 16 bit ecus had this option in romraider


or is that what the section ALPHA AF 3(Rear O2 Sensor) attempts to do

AFAIK no one even Ecutek dont force readiness monitors.

When you for example inhibit P0420 cat efficiency its just disabling the code so it does not trigger CEL and any action the ECU might take as a result of that code triggering like limp mode or disabling cruise control.

however it seems the readyness monitoring is separate block of code and it still detects abnormal operation of even though cel codes disabled.

It would certianly be possible to defeat the readiness monitoring but would require some code patching i suspect. eg like romraider guys did on older ecu.

I suspect even ecutek dont do force readyness probably due legal ramifications of falsifying emissions tests

I believe that AF3 (rear 02 alpha stuff is for the afr adjustments done by rear 02 during highway cruising, mainly for people who have removed rear 02 completly. so you can disable adjustments

So I'm a rookie at using RomRaider but in the OFT stage1 91oct tune, I noticed in the 'base timing idle (in-gear)(above speed threshold)' table that that columns are a bit messed after 2000 rpm. I know the ECU won't read those values but messed up/redundant data drives me crazy (since I deal survey/gps data from field crews at work). What's the easiest way to remove those columns? I thought romraider worked similar to excel but I'm guessing the y-axis is hard-coded into the table?

1. Get the correct definition file/correct the definition file.
or
2. Ignore it

Do not edit those values

As @Kodename47 said either remove those table references from definition ( do not alter that table in romraider) or just ignore it and never change anything in that table. Theirs no real need to alter those values.


Its an error in the definition and its likely pointing to program code and not a table , so as above don't edit those values else it will likey have bad consequences ie ECU brick. As long as you don't alter that table it will be fine.


don't ever cut and paste from or into a table that looks corrupt like that.

Hey guys I just flashed to the e85 tune using jdl el headers I don't feel much of a difference from my 91 tune is there new maps for el or just for the uel ?

log your LTFT and AFR make sure its not running rearly rich.

also E85/tune tends to smooth out the torque dip a lot so the power is more linear and smooth ,