[ztan]

Following @Td-d's work on the ROMraider forums here:
http://www.romraider.com/forum/viewt...hp?f=40&t=8615

I had a look at the A01G ROM with ScoobyROM.

Knock sensor calibration table was easy to find using Td-d's ScoobyROM method, unpicking the knock control logic is quite difficult. There is also a table that looks like it uses FLKC table offset as an input - possibly a threshold. All highly experimental.

Welcome any input into deciphering the knock logic.

    <table name="Knock Sensor Calibration" storageaddress="11DF48">
      <table type="Y Axis" storageaddress="11DDEC" />
    </table>
    <table name="Knock Threshold" storageaddress="11612C">
      <table type="Y Axis" storageaddress="1160A0" />
    </table>


    <table type="2D" name="Knock Sensor Calibration" category="Ignition Timing - Knock Control" storagetype="uint16" endian="big" sizey="87" userlevel="4">
      <scaling units="ECU value" expression="x-32" to_byte="x+32" format="0" fineincrement=".5" coarseincrement="10" />
      <table type="Y Axis" name="Knock Sensor" storagetype="float" endian="little">
        <scaling units="volts" expression="x" to_byte="x" format="0.0000" fineincrement=".01" coarseincrement=".1" />
      </table>
      <description>Knock sensor calibration</description>
    </table>
    
    <table type="2D" name="Knock Threshold" category="Ignition Timing - Knock Control" storagetype="float" endian="little" sizey="35" userlevel="5">
      <scaling units="ECU value" expression="x" to_byte="x" format="0.0000" fineincrement=".5" coarseincrement="10" />
      <table type="Y Axis" name="FLKC Offset" storagetype="float" endian="little">
        <scaling units="Offset" expression="x" to_byte="x" format="0" fineincrement="1" coarseincrement="1" />
      </table>
      <description>?? Knock threshold by FLKC offset </description>
    </table>