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

[Bader]

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.

[steve99]

Originally Posted by Bader

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.

[Bader]

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.

[aagun]

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

[steve99]

Originally Posted by aagun

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

[troek]

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.

[steve99]

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.

[KoolBRZ]

Originally Posted by troek

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.

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.

[thambu19]

@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?

[steve99]

Originally Posted by thambu19

@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

[thambu19]

Originally Posted by steve99

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!

[steve99]

Originally Posted by thambu19

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

[thambu19]

Originally Posted by steve99

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

[Dallen]

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.