Official OpenFlash Tablet FA20 Tuning Tech Discussion Thread

[ST-A]

Originally Posted by steve99

Just a thought if you using an OFT and Romraider definition from Github or OFT site those definitions are in Imperial ie psi not metric bar.
@Kodename47 has done some metric definitions.

did you convert map sensor bar to psi ?

the OFT Vortech SC tune uses Omni 2.5 bar MAP sensor

the setting in that rom are

Multiplier (psi absolute/v) = 7.251
Offset = 1.450


Did increase MAF limit max (g/s) NA roms its 200 vortech SC rom 500

I know nothing about SC/Turbo tuning just some suggestions.

Also noticed on Techstream your Calculated engine load is 100% maybe your hitting a load limiter ??

i rescaled map sensor to the values given to me, it is the denso/honda map sensor i'm using, the same sensor they use with the ecutek kits.

my maf limit max is also 500
my maf scaling map just goes to 315 right now, i have not seen values over 300 yet.
engine load limit max is set at 4 g/rev
i did not convert the rom or xml to metric values, i'm still using the xml that comes with the oft 2.063 package (2.07 ZA1J700G)

how do i convert it to metric? adjust the whole XML file?

[steve99]

Originally Posted by ST-A

i rescaled map sensor to the values given to me, it is the denso/honda map sensor i'm using, the same sensor they use with the ecutek kits.

my maf limit max is also 500
my maf scaling map just goes to 315 right now, i have not seen values over 300 yet.
engine load limit max is set at 4 g/rev
i did not convert the rom or xml to metric values, i'm still using the xml that comes with the oft 2.063 package (2.07 ZA1J700G)

how do i convert it to metric? adjust the whole XML file?

@Kodename47 did some ZA1JA01G metric definitions here.

http://www.ft86club.com/forums/showp...&postcount=333

If your using an OFT ZA1J700G tune file its highly likely its actually a ZA1JA01G tune calid adjusted to look like a 700G.

You can check this with a hex editor
Open the tune file with a hex editor search for string ZA1J their will be three occurrances in the rom usually all are the same but in oft roms if its been calid adjusted the first two occurrances are the psuedo calid and the third instance is the real calid .

If the real calid is A01G then just change the xml files names and the calid in the xml file to 700G, and use kodename47 A01G metric defs with a lot of extra tables identified in them.

[Kodename47]

Originally Posted by ST-A

yes we have the 700G rom and i started from the OFT stage2 EL 2.063
I'm using romraider to tune
i just changed the map sensor scaling in 1 place , didn't find other places? can you guide me to where they are? i changed the "manifold pressure scaling" under the "manifold pressure sensor" tab.
i also rescaled the fuel and ignition maps to 2.25 in the load scale.
DI injection maximum is now 100% in the full map and GDI pressure target is 20Mpa above the 100 on the load axxis.

i use the Toyota techstream program for logging.

Do as @steve99 said and check the actual ROM you're using. It still worries me about your DI/PI settings, using 0 in the Pi ratio means that you're using 100% DI for fueling percentage and not using the PI at all. 100 would mean no DI at all. Either of those would mean you would hit 100% duty for the respective system causing your issue. You also would need to adjust the max DI volume tables. I know ECUtek recommend no higher than 1.3ml, that may still be high but may see further fuel be available.

[elBarto]

Originally Posted by ST-A

I did not convert the rom or xml to metric values, i'm still using the xml that comes with the oft 2.063 package (2.07 ZA1J700G)

how do i convert it to metric? adjust the whole XML file?

I converted my own A00G OFT XML to the metric system.
It is quite simple (thanks to Kodename47 XMLs and info)

Just open it with Notepad++ and find:

<scaling units="Vehicle Speed (MPH)" expression="x*.621" to_byte="x/.621"

And replace it with:

<scaling units="Vehicle Speed (Km/h)" expression="x" to_byte="x"

Then press the 'replace all' button and done, everthing is km/h

Then find the string:

scaling units="psi" expression="x*.01933677" to_byte="x/.01933677"

and replace them all with:

scaling units="bar" expression="x*.001333223" to_byte="x/.001333223"

Finally convert F to C
Find

<scaling units="Degrees F" expression="(x*1.8)+32" to_byte="(x-32)/1.8"

replace all with

<scaling units="Degrees C" expression="x" to_byte="x"

But I don't know if you can switch from an OFT XML with LC and FFS inside the Rom to a normal Rom XML without those tables. Maybe @Kodename47 or @steve99 kan answer this?
Because otherwise it's just editing Kodename47's XML to work with a 700G rom.

[steve99]

Originally Posted by elBarto

I converted my own A00G OFT XML to the metric system.
It is quite simple (thanks to Kodename47 XMLs and info)

Just open it with Notepad++ and find:

<scaling units="Vehicle Speed (MPH)" expression="x*.621" to_byte="x/.621"

And replace it with:

<scaling units="Vehicle Speed (Km/h)" expression="x" to_byte="x"

Then press the 'replace all' button and done, everthing is km/h

Then find the string:

scaling units="psi" expression="x*.01933677" to_byte="x/.01933677"

and replace them all with:

scaling units="bar" expression="x*.001333223" to_byte="x/.001333223"

Finally convert F to C
Find

<scaling units="Degrees F" expression="(x*1.8)+32" to_byte="(x-32)/1.8"

replace all with

<scaling units="Degrees C" expression="x" to_byte="x"

But I don't know if you can switch from an OFT XML with LC and FFS inside the Rom to a normal Rom XML without those tables. Maybe @Kodename47 or @steve99 kan answer this?
Because otherwise it's just editing Kodename47's XML to work with a 700G rom.

LC/FFS is a code patch in the OFT rom , to be able to access the tables for LC/FFS you would have to copy the relivant xml code that defines those tables from the oft rom to kodename47 roms.

[elBarto]

Originally Posted by steve99

LC/FFS is a code patch in the OFT rom , to be able to access the tables for LC/FFS you would have to copy the relivant xml code that defines those tables from the oft rom to kodename47 roms.

Ok thanks, found it.

These are the tables:

<table name="Launch Control Disable Speed" storageaddress="BAD50" />
<table name="Launch Control RPM Delta" storageaddress="BAD54" />
<table name="Flat-Foot Shift RPM Delta" storageaddress="BAD58" />

and

<table type="2D" name="Launch Control Disable Speed" category="Alpha - BRZ - FFS/LC" storagetype="float" endian="big" sizey="1" userlevel="4">
<scaling units="Vehicle Speed (Km/h)" expression="x" to_byte="x" format="#" fineincrement="1" coarseincrement="5" />
<table type="Static Y Axis" name="" sizey="1">
<data>Disable above</data>
</table>
<description>Launch Control will be disabled above this speed</description>
</table>
<table type="2D" name="Launch Control RPM Delta" category="Alpha - BRZ - FFS/LC" storagetype="float" endian="big" sizey="1" userlevel="4">
<scaling units="Engine Speed Delta" expression="x" to_byte="x" format="0" fineincrement="1" coarseincrement="100" />
<table type="Static Y Axis" name="RPM Delta" sizey="1">
<data></data>
</table>
<description>This table sets the required RPM delta for launch control to activate: redline (7600) - delta = launch control activated RPM</description>
</table>
<table type="2D" name="Flat-Foot Shift RPM Delta" category="Alpha - BRZ - FFS/LC" storagetype="float" endian="big" sizey="1" userlevel="4">
<scaling units="Engine Speed Delta" expression="x" to_byte="x" format="0" fineincrement="1" coarseincrement="100" />
<table type="Static Y Axis" name="RPM Delta" sizey="1">
<data></data>
</table>
<description>This table sets the required RPM delta for launch control to activate: redline (7600) - delta = FFS activated RPM</description>
</table>

Finaly I can ditch those old OFT XMLs and work with proper updated stuff.
Thanks alot

[elBarto]

So since I cannot sleep at this moment I merged Kodename47 definition with the LC/FFS shifting into one file.
Edited the XMLs also for all of the G-roms (except A02G).

Units are in Km/h, degrees Celsius and pressure in bar.

700G
A00G
A01G
Remember, these are for the CalId hacked OFT Roms G-series.

I hope Kodename47 doesn't mind I did this with his definitions?

[ST-A]

thank you very much!
There are way more tables in there like load limiters that weren't available in the OFT maps i was using! it looks like it is limited to 1.3 load.... that is probably one reason why its running so lean.

about the DI / PI ratio, say i want to max both of them out together i need to set them both to 50 instead of 100% in the "DI max" table?
Or do i adjust instead the 'total injection ratio warm + hot' tables?

my load in fuel and ignition maps i rescaled to 2.25

thanks allready for all of your help

[Kodename47]

@elBarto nice work. For reference the A02G is the same anyway, so you would only need to change the cal ID at the top of the definition.

@ST-A ensure MAF and load limits are raised. All 3 Injection ratio tables want to be the same as they are from the factory. To get the best out of the fueling you need to calculate the ideal ratio, you could put 50 in there to test but the DI can provide more fuel than the PI so a value of 30-40 would be a better starting point. Obviously you only need to adjust in the higher load region. Then you need to log injection duration for both systems. There's a thread further down this forum with lots of info.

I don't know of this DI Max table, the only one I know of sets ths max DI volume which needs to be increased.

[Bader]

Just wanted to ask a simple question. I was comparing OFT OTS 2.06 in romraider and found that there are 46 missing tables in the Middle East tune (manual and auto) compared to the US 93 Stg1 tune.

Mostly CEL codes. I was wondering if it's possible to run the US Stg1 93 oct tune on my 700K BRZ. Either way. I wanted to understand what the differences are between them. If this has been answered before then I would appreciate a link to the information.

[Kodename47]

Originally Posted by Bader

Just wanted to ask a simple question. I was comparing OFT OTS 2.06 in romraider and found that there are 46 missing tables in the Middle East tune (manual and auto) compared to the US 93 Stg1 tune.

Mostly CEL codes. I was wondering if it's possible to run the US Stg1 93 oct tune on my 700K BRZ. Either way. I wanted to understand what the differences are between them. If this has been answered before then I would appreciate a link to the information.

No you can't. I doubt there are any real differences in the tune, it just means less tables have been defined in Romraider.

[Kodename47]

Originally Posted by ST-A

thank you very much!
There are way more tables in there like load limiters that weren't available in the OFT maps i was using! it looks like it is limited to 1.3 load.... that is probably one reason why its running so lean.

about the DI / PI ratio, say i want to max both of them out together i need to set them both to 50 instead of 100% in the "DI max" table?
Or do i adjust instead the 'total injection ratio warm + hot' tables?

my load in fuel and ignition maps i rescaled to 2.25

thanks allready for all of your help

Just opened Romraider. Here are the main tables to look at:
Engine Load Limiters A & B
MAF Limit (Maximum)
Direct Injection Quantity Maximum (in ml not %) - Set to 1.2 or similar
Total Injection Ratio Cold/Warm/Hot - Remember this is the % of PI injection
Also worth checking the PI MRP Compensation and making the values above 0 Bar positive

[steve99]

Originally Posted by Bader

Just wanted to ask a simple question. I was comparing OFT OTS 2.06 in romraider and found that there are 46 missing tables in the Middle East tune (manual and auto) compared to the US 93 Stg1 tune.

Mostly CEL codes. I was wondering if it's possible to run the US Stg1 93 oct tune on my 700K BRZ. Either way. I wanted to understand what the differences are between them. If this has been answered before then I would appreciate a link to the information.

The only difference between 91 and 93 tunes is the ignition advance over 5000 rpm in tue 93 tunes its about 2 degrees more than the 91 tunes.

Outside the usa they only use the 91 version, if you have good fuel copy the BASE TIMING B table from a 93 tune to your rom.

Tunes tables in roms for same tunes in different countries are same ie a Petrol 91 EL header tune tables for a A01G is same as A01C but the roms are different.

The oft guys copy the tune tables from the usa roms into the roms for the different countries

[Bader]

Originally Posted by steve99

The only difference between 91 and 93 tunes is the ignition advance over 5000 rpm in tue 93 tunes its about 2 degrees more than the 91 tunes.

Outside the usa they only use the 91 version, if you have good fuel copy the BASE TIMING B table from a 93 tune to your rom.

Tunes tables in roms for same tunes in different countries are same ie a Petrol 91 EL header tune tables for a A01G is same as A01C but the roms are different.

The oft guys copy the tune tables from the usa roms into the roms for the different countries

Thank you for the help. I will try that once I get back home.

I keep arguing with others here that the 93 AKI US fuel is better than our 98 octane but they insist that ours is more knock resistant. I guess I'll find out soon.

P.S. Thank you and Kodename47 for all the helpful posts on this forum. I've been lurking since 2012 but I finally started to mess around and try to learn how my car works. It's been fun so far.