RomRaider XML definitions.

[wparsons]

Just a question about which definitions to use with OFT OTS tune files... do you use the definition that matches whichever OEM ROM you have, or the one that matches the OEM ROM the new tune is based off?

ie 700C to match my factory ROM, or A10C to match the base ROM used for the OTS 1.5x tunes?

[AdrianG]

There are XML's on the OFT site for download, if you are editing an OTS tune you can do so with TD-D's A01C XML but you won't see launch control or FFS as that is only included in the definitions provided on the OFT site.

- AdrianG

[shif7i7down]

Originally Posted by wparsons

Just a question about which definitions to use with OFT OTS tune files... do you use the definition that matches whichever OEM ROM you have, or the one that matches the OEM ROM the new tune is based off?

ie 700C to match my factory ROM, or A10C to match the base ROM used for the OTS 1.5x tunes?

I'm assuming you mean A01C which should match your particular car,
in which case you would use the xml file that reads RR_ZA1JA01C.xml

[wparsons]

Sorry, yeah.. meant A01C.

So just to confirm, even though I'm using the 700C bin file (which is based on the A01C ROM) from Shiv, I should use the A01C XML definitions?

[shif7i7down]

Originally Posted by wparsons

Sorry, yeah.. meant A01C.

So just to confirm, even though I'm using the 700C bin file (which is based on the A01C ROM) from Shiv, I should use the A01C XML definitions?

You'll know if you used the right xml or not, if it doesn't load the ots map then you've used the wrong xml. that's what happened to me...btw if you don't mind me asking, what are you planning to change? I don't know much but Maybe i could point you in the right direction

[wparsons]

I used the 700C XML file and I can see all the tables (plus the FFS and LC extra stuff), looks like I'm good to go with it.

I'm not changing anything just yet, but will be redoing the MAF scaling once I get a couple more logs, then after that is cleaned up I'm going to look into patching up the ignition tables so I'm not dropping IAM in stop and go traffic.

[Ralph Spoilsport]

Originally Posted by wparsons

I used the 700C XML file and I can see all the tables (plus the FFS and LC extra stuff), looks like I'm good to go with it.

I'm not changing anything just yet, but will be redoing the MAF scaling once I get a couple more logs, then after that is cleaned up I'm going to look into patching up the ignition tables so I'm not dropping IAM in stop and go traffic.

Got a link to the procedure you are using to scale the MAF? Are you going to scale DI and PI separately ("he who must not be named" evidently had a procedure for doing this...)?

My LTFTs suck (> 5%) and I would like to do something about this.

[shif7i7down]

I see. Post back when you figure out the IAM issue, I'm assuming you're having engine knock and I'm interested in what you plan to do correct it besides better fuel.

[wparsons]

Originally Posted by Ralph Spoilsport

Got a link to the procedure you are using to scale the MAF? Are you going to scale DI and PI separately ("he who must not be named" evidently had a procedure for doing this...)?

My LTFTs suck (> 5%) and I would like to do something about this.

MAF scaling is 100% separate from injector scaling.

MAF scaling is basically a correction table that just gives engine load values for a given MAF voltage. It's a one dimensional table, and doesn't touch injectors or anything else at all.

I don't have a how to yet, gotta work that out with someone that used to be a member. Once I get more details I'll share them for sure.

[Vmax911]

My car was originally 700C. I'm changing the ignition advance table to correct the "traffic knock" and am using the files downloaded from the OFT website. Working well so far...