OFT - Example alternate maps for AT, 98RON, E85, MAF Scales

[KoolBRZ]

I am trying to find which category and table Wayno referenced to get the attached 3D table. It isn't labeled for the third variable and I've looked everywhere in his ROM to find it. Does this table look familiar enough to recognize where it came from and what name to find it under?

[KoolBRZ]

I did it. It works! I copied and pasted almost every table, except the metric celsius tables, and left all the CEL codes turned on. I had to redo my MAF scale, since I use a Skunk2 Intake without the insert. My tune also had differences in the AVCS Intake and Exhaust "safe" tables, because of the work I've been doing to compensate for my PLM long-tube header. I was getting a gear-lash effect with my old tune while shifting manually without lifting off the throttle, (No Lift Shift = NLS). The new tune with @Wayno's additions smoothed it out and removed the gear-lash effect when I NLS'ed my shifts. @Wayno thank you, @Td-d, @steve99, @Kodename47 and anyone else who has helped.
P.S. @Wayno have you considered getting a Nameless Long tube header, or the PLM long-tube header? That, plus a low restriction Intake make for more low-end torque, a particular need for the automatics.

[Wayno]

Originally Posted by KoolBRZ

I am trying to find which category and table Wayno referenced to get the attached 3D table. It isn't labeled for the third variable and I've looked everywhere in his ROM to find it. Does this table look familiar enough to recognize where it came from and what name to find it under?

That's likely Base Timing B + KCA - 6.

[Td-d]

Nah, not really There are two sections - the table addresses, and the 32bitbase where the typology of the table is described. From my xmls:

    <table type="2D" name="Engine Load Limit B Maximum (RPM)" category="Mass Airflow / Engine Load" storagetype="uint16" endian="big" sizey="9" userlevel="4">
      <scaling units="Engine Load (g/rev)" expression="x*.00006103516" to_byte="x/.00006103516" format="0.00" fineincrement=".01" coarseincrement=".1" />
      <table type="Y Axis" name="Engine Speed" storagetype="float" endian="little" logparam="P8">
        <scaling units="RPM" expression="x" to_byte="x" format="#" fineincrement="50" coarseincrement="100" />
      </table>
      <description>This is the maximum allowable engine load. Engine load will be capped at this limit regardless of actual engine load. "Engine Load Limit A (Maximum)" must also be changed as it also impacts the max engine load.</description>
    </table>
    <table type="2D" name="Engine Load Limit C (Maximum) (RPM)" category="Mass Airflow / Engine Load" storagetype="uint16" endian="big" sizey="9" userlevel="4">
      <scaling units="Engine Load (g/rev)" expression="x*.00006103516" to_byte="x/.00006103516" format="0.00" fineincrement=".01" coarseincrement=".1" />
      <table type="Y Axis" name="Engine Speed" storagetype="float" endian="little" logparam="P8">
        <scaling units="RPM" expression="x" to_byte="x" format="#" fineincrement="50" coarseincrement="100" />
      </table>
      <description>This is the maximum allowable engine load. Engine load will be capped at this limit regardless of actual engine load. "Engine Load Limit A (Maximum)" must also be changed as it also impacts the max engine load.</description>
    </table>

In any case - I'm glad you came right - this code does take some time to get your head around!

Originally Posted by KoolBRZ

He's done a bit more than just rename them. Here's the lower, descriptive section from his A01I xml.
<QUOTE></table>
<table type="2D" name="Engine Load Limiter A" category="Test" storagetype="uint16" endian="big" sizey="9" userlevel="3">
<scaling units="Engine Speed (RPM)" expression="x*0.0000610351563" to_byte="x/0.0000610351563" format="0.00" fineincrement="0.1" coarseincrement="1" />
<table type="Y Axis" name="Engine Load" storagetype="float" endian="little" logparam="P2">

<scaling units="" expression="x" to_byte="x" format="#" fineincrement="100" coarseincrement="500" />
</table>
<description>Engine load limit against RPM.</description>
</table>
<table type="2D" name="Engine Load Limiter B" category="Test" storagetype="uint16" endian="big" sizey="9" userlevel="3">

<scaling units="Engine Speed (RPM)" expression="x*0.0000610351563" to_byte="x/0.0000610351563" format="0.00" fineincrement="0.1" coarseincrement="1" />

<table type="Y Axis" name="Engine Load" storagetype="float" endian="little" logparam="P2">

<scaling units="" expression="x" to_byte="x" format="#" fineincrement="100" coarseincrement="500" />

</table>
<description>Engine load limit against RPM.</description>
</table>
</QUOTE>
This looks totally different than your code. You can see why I would think it describes a totally different table. @Wayno's tables are in a new category, called Test, at the very bottom of the list in RR. I know now that I can just copy and paste from the B01D xml's to my OFT A00D xml's. Thank you for all your help.

[Wayno]

I just copied kodename's addresses because my priority was getting my car running right, not make defs pretty for other people.

I've made them all consistent now so there's less chance of people screwing up their tables, including reverting to Fahrenheit, even though the ecu values are stored in Celsius and the rest of the world uses Celsius.

[KoolBRZ]

Originally Posted by Wayno

I just copied kodename's addresses because my priority was getting my car running right, not make defs pretty for other people.

I've made them all consistent now so there's less chance of people screwing up their tables, including reverting to Fahrenheit, even though the ecu values are stored in Celsius and the rest of the world uses Celsius.

Does that mean you have ported all of your changes to the B01D files, and converted to Fahrenheit, or, did you convert all your files? I was just thinking of converting mine to Celsius, so it would be more compatible with mods to tunes from all around the world. It's just for reference anyway, since the ECU uses the metric scale inside. Doesn't that mean that somewhere in the code there is a standard to metric converter, in order to interface with the metric ECU?
I'll be testing tunes on the dyno tomorrow. I have 5 tunes loaded. OFT stage 2 EL and UEL 91 Octane, my latest tune with significant changes to AVCS Intake and Exhaust Safe tables, my latest tune with AVCS changes and @Wayno's additions, and @Wayno's 98 RON with my rescaled MAF scale. I'm hoping my tune with @Wayno's additions will come out on top, but I think it will be enlightening regardless. I'll post the results tomorrow.

[Kodename47]

Originally Posted by KoolBRZ

Does that mean you have ported all of your changes to the B01D files, and converted to Fahrenheit, or, did you convert all your files? I was just thinking of converting mine to Celsius, so it would be more compatible with mods to tunes from all around the world. It's just for reference anyway, since the ECU uses the metric scale inside. Doesn't that mean that somewhere in the code there is a standard to metric converter, in order to interface with the metric ECU?

What you have to understand is it's just how the definitions work, there is no difference in the data in the ROM. Look at the expression and to_byte information. On the temperature data it's just "x" for Celsius, for Fahrenheit it's "(x*1.8)+32". When you input into Romraider it uses the definition to change the data to the correct hexadecimal expression.

[KoolBRZ]

Originally Posted by Kodename47

What you have to understand is it's just how the definitions work, there is no difference in the data in the ROM. Look at the expression and to_byte information. On the temperature data it's just "x" for Celsius, for Fahrenheit it's "(x*1.8)+32". When you input into Romraider it uses the definition to change the data to the correct hexadecimal expression.

By my count, it needs to be changed 183 times. Wow. Can I use "replace all"? It looks like I need to replace all ("Degrees F" expression="(x*1.8)+32" to_byte="(x-32)/1.8") with ("Degrees C" expression="x" to_byte="x").

[Wayno]

You can replace all from imperial to metric, but not in reverse. All the defs attached to the OP are all imperial as i replied last night.

There's not that many tuning changes in my rom. Just leaner AFR under low load on E85, timing map smoothing and load limits to make AFR more predictable. All the rest are tweaks developed by forum members . None should make any more power except in the 2500-4000rpm range and possibly a couple hp around 7000rpm due to not hitting load limit around 6400 and being able to run leaner maf scale value in that cell.

[Kodename47]

Originally Posted by Wayno

You can replace all from imperial to metric, but not in reverse. All the defs attached to the OP are all imperial as i replied last night.

So long as you use:
Find:
<scaling units="Degrees F" expression="(x*1.8)+32" to_byte="(x-32)/1.8"

Replace With:
<scaling units="Degrees C" expression="x" to_byte="x"

Then you can use the opposite to revert back. You must include the scaling units part of the description. The same works for speed conversions and even ratio conversions like ECUtek tables.

[Wayno]

Originally Posted by Kodename47

So long as you use:
Find:
<scaling units="Degrees F" expression="(x*1.8)+32" to_byte="(x-32)/1.8"

Replace With:
<scaling units="Degrees C" expression="x" to_byte="x"

Then you can use the opposite to revert back. You must include the scaling units part of the description. The same works for speed conversions and even ratio conversions like ECUtek tables.

I know, but less risk to just use originals rather than go around in circles.

[Kodename47]

Originally Posted by Wayno

I know, but less risk to just use originals rather than go around in circles.

Yes, I agree.

[KoolBRZ]

My tune is now Metric. Now I can copy mods from the rest of the world. Going to the dyno today. VIP Performance in Portland. I'll be comparing OFT OTS stage 2 91 Octane EL and UEL, versus my best tune without @Wayno's additions, my best tune with @Wayno's additions, and @Wayno's stage 2 UEL 91 v66A tune, ported to A00D. I'll see whether my AVCS changes helped or hurt my power.

[Wayno]

Originally Posted by KoolBRZ

My tune is now Metric. Now I can copy mods from the rest of the world. Going to the dyno today. VIP Performance in Portland. I'll be comparing OFT OTS stage 2 91 Octane EL and UEL, versus my best tune without @Wayno's additions, my best tune with @Wayno's additions, and @Wayno's stage 2 UEL 91 v66A tune, ported to A00D. I'll see whether my AVCS changes helped or hurt my power.

The load limits won't directly effect power.

The only thing they do is make the AFR more predictable like it is on the MT, so you can tune MAF easier, but that's per car specific.

There's nothing else in there that will increase power at WOT except MAF scale.


I've modified the load limit scale in the OP attachments so that 4000 rpm doesn't spike lean so much, and modified 3.44V to be not as lean also, as seen here:

http://datazap.me/u/wayne/v66-4?log=...1909&mark=1844

Fix: