There is a simple process to go through to configure knock control, and this is outlined below. Note that experienced professionals will be able to determine knock levels correctly.


  1. Make sure your knock sensor is correctly installed and wired to the ECU.
  2. Use a knock frequency calculator to determine the knock frequency of your engine. You can multiply this by ‘2’ to use the 2nd harmonic frequency to lower background noise.
  3. Make sure the ignition map is set very conservatively when doing the base runs.
  4. Set the entire Knock Acc Val Table to a high number (>66,000)
  5. Configure the RPM ranges, window and step size according to your preference.
  6. Set ‘Enabled’ to ‘No’ in Knock Settings.
  7. Adjust the Time Constant and Gain (don't forget to cycle the power after each change) until Knock Reading is around 4,000 at idle (on GEN1) around 100 on GEN2
  8. Do a couple of runs in a higher gear with logging activated, or use a Histogram DRO view (pause it by pressing ‘P’ after a run) trying to cover the entire RPM range where you want to have knock control active.
  9. Reset the gain at this point so the engine noise is around 30% of the knock sensor range (on a GEN1 it is 0-65,535) on a GEN2 it is (90-1024).
  10. Fill in the Knock Acc Val Table with the corresponding readings from the log, corresponding to the RPM row which you're adjusting. Obviously, leave a margin (the value in the table should be higher than the one in the log) for changing conditions. 10% should be enough, but use your best judgement.
  11. Adjust the Fuel Knock Trim Table to add fuel when knock occurs. Make sure you edit the input axis as well as the output.
  12. Re-enable knock control, and if safe to do so, create a knock event by over advancing and checking the ECU reacts as expected. Do so at your own risk to you and the engine!


Be sure to test using an ancillary measurement system such as traditional 'det-cans' to ensure everything is in line before relying on knock control to protect your engine!


Note that if gain is not set correctly, high readings will "wrap" back around to the lower readings due to saturation.