Quote:
Originally Posted by Kodename47
How does the lower one work?
|
No real idea, but the value that gets passed to the 2D table is the FLKC cell offset - this reads 0-4 in the first RPM range as load increases, then 5-9 in the next RPM range... 35 values in all for 5 load ranges and 7 RPM ranges.
I played around with reformatting the table to the following, which makes me suspect that this is a table defining knock threshold or sensitivity per FLKC cell. The logic is very complex and I am nowhere close to unravelling it:
Code:
<table type="3D" name="Knock Threshold" category="Ignition Timing - Knock Control" storagetype="float" endian="little" sizex="5" sizey="7" userlevel="4">
<scaling units="ECU value" expression="x" to_byte="x" format="0.000" fineincrement=".2" coarseincrement="1" />
<table type="Static X Axis" name="" sizex="5">
<data>FLKC Load Range 1</data>
<data>FLKC Load Range 2</data>
<data>FLKC Load Range 3</data>
<data>FLKC Load Range 4</data>
<data>FLKC Load Range 5</data>
</table>
<table type="Static Y Axis" name="" sizey="7">
<data>FLKC RPM Range 1</data>
<data>FLKC RPM Range 2</data>
<data>FLKC RPM Range 3</data>
<data>FLKC RPM Range 4</data>
<data>FLKC RPM Range 5</data>
<data>FLKC RPM Range 6</data>
<data>FLKC RPM Range 7</data>
</table>
</table>