View Single Post
Old 12-13-2014, 05:47 PM   #1
steve99
Banned
 
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,987 Times in 2,981 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
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











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







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]




.
Attached Images
 

Last edited by steve99; 03-28-2018 at 07:38 AM.
steve99 is offline   Reply With Quote
The Following 14 Users Say Thank You to steve99 For This Useful Post:
connorlug (12-14-2014), elBarto (12-15-2014), fstlane (01-01-2015), JB86'd (10-01-2015), Joe-G (10-01-2015), j_Zer0 (01-20-2015), keen as (05-18-2015), P@ul (12-14-2014), phrosty (12-13-2014), Shiv@Openflash (12-13-2014), Sportsguy83 (05-21-2015), thambu19 (11-08-2015), Viper8 (08-19-2018), vynervt (03-13-2015)