stunt2

iTrader: (8)

as title says, is it possible ? if yes, how can it be done ?

if I klick the table and enter any value with "=", it doesn't allow me and puts '0' in there

jedibow

iTrader: (1)

Absolutely, you need to correct the xml definitions for the scaling as the scaling is upside down in the calculations... Let me see if I can find the correct scaling from my xml...

George

jedibow

iTrader: (1)

Look for these tables...

<table name="MAF Scaling" category="Global Fuel Settings" type="2D" level="3" scaling="AirFlow8">
<table name="AirFlowHZ" type="Y Axis" elements="21" scaling="MAFHz"/>
</table>
<table name="MAF Compensation" category="Global Fuel Settings" type="2D" level="3" scaling="Percent (128)">
<table name="MAF Hz" type="Y Axis" elements="21" scaling="MAFHz"/>
</table>

and the correct scaling is...

<scaling name="MAFHz" units="Hz" toexpr="6.29*x/64" frexpr="x*64/6.29" format="%.0f" min="0" max="5000" inc="1" storagetype="int16" endian="big"/>

stunt2

iTrader: (8)

couldn't quite understand, I have to replace this whole section

with this

in my rom's xml ?

is that formula same for every rom ? I use 96530706 V7

3SgteGuru

iTrader: (3)

Interesting I was about to ask the exact same question. My basically stock evo peaks out at 1900hz. And im trying to tune it with a bit of an un orthodox techinique ill probably get flammed for Im gonna try and enter this scaling into the my xml and tell you guys if my car blows up ok.

3SgteGuru

iTrader: (3)

Worked. Order of op error

Just click edit on the map and edit the map def, select scaling for the mafhz and edit the mafhz scaling change
"display to ROM f(x)" from "64/(6.29*x)" to "x*64/6.29"

jedibow

iTrader: (1)

Sorry no the only thing you need to fix is the scaling

jedibow

iTrader: (1)

Exactly!!! Now you can move the scaling out further, remember this will also change your Maf table be sure and correct it...

stunt2

iTrader: (8)

worked

max value it allows to enter is 3220 Hz
will log 2 byte airflow and see where my car peaks at. hope 2.3+holset won't max it out

thanks guys

merlin.oz

the correct eval is:

6.25*x/64

not 6.29*x/64

If the stock max Hz axis value is 1610Hz, you have the the incorrect 6.29*x/64 in your definition.

stunt2

iTrader: (8)

yes, I have 1610 Hz as the last value right now

so it was incorrect all the time I use this rom ?
its standart tephra v7 xml, downloaded from this forum's v7 thread

merlin.oz

yes, the correct eval will set it back to 1600Hz.

Once you have done that, then make your changes to the Hz axis.

stunt2

iTrader: (8)

changed both in ROM to Display and Display to ROM fields

is it correct now ?

merlin.oz

That looks right,
but
It is not a good idea to edit you xml using EcuFlash to do the editing, as it will delete any comments and notes embedded in the xml, and space/tabs.
Essentially, it will trash your xml down to only what EcuFlash needs to work.

So, if you were using one of my xmls for example, which have lots of tuning notes embedded in the definition, those comments and notes will be deleted.

That is why I always advocate using Notepad or Notepad++ to edit a definition file.

3SgteGuru

iTrader: (3)

Mine always resets back to the incorrect values when i close ECU Flash