FAQ

Questions

1.Q: Do you provide telephone-based support?
2.Q: How does this compare to other knock detection solutions?
3.Q: Why have you opted to not include headphone input like most other knock detection systems?
4.Q: Will you ever support flat-response type knock sensors?
5.Q: What about HKS AFK? Is that not the best solution?

Answers

1.Q: Do you provide telephone-based support?

1.A: No. However, one-on-one email support is provided.

2.Q: How does this compare to other knock detection solutions?

2.A: Every solution have their own set of features and application. Some solutions do _not_ provide analog-voltage-based knock level output, some do not provide real-time software-based knock level output, or some just do not work with the resonant-type knock sensors, which some people prefer to retain. You can read up on other solutions and make the comparison yourself:

• HKS AFK
• MoTeC Knock Module
• Knock Ears Basic
• Link KnockBlock
• Phormula Knock Analyser KS-4
• Gizzmo Kmon
• MSD Engine Knock Alert

3.Q: Why have you opted to not include headphone input like most other knock detection systems?

3.A: I did not consider this as a necessary requirement for calibration or providing an edge for tuning purposes, especially for road-based tuning.

4.Q: Will you ever support flat-response type knock sensors?

4.A: Yes, this is now completed and ready since 14 May 2012.

5.Q: What about HKS AFK? Is that not the best solution?

5.A: There's a couple of issues that I have with the HKS AFK. They are:
• It is expensive as it also integrates wideband controller (two for version 2)
• I could not get AFK v1 to function without erroring out.
• LCD display unit and button interface is cumbersome.
• Lack of technical support.
• Has annoying buzzer sound.
• Will not work with other aftermarket ECUs with knock-window-signal support.