Murry, that DFT link......WAY, WAY beyond me. I'm not gonna get a headache trying to make sense of that. Help me a little to understand more without making me read that.
From what I gather/guess, the software in the PCM has been programmed to read the knock signal, clean it up (ignore back round noise), and then advance this cleaned info further along in the code for the PCM to process and then take action if necessary = pull timing. No way we can do this without big time $$$$ tools/equipment.
What about a simple device that taps into the knock sensor signal and logs knock events as well as timing? Even though it's not perfect it should serve as enough info to help a little, no?
http://www.viatrack.ca/
"There is also a separate pseudo analog channel that allows capturing the knock event with a data logger"
After reading a little about this and thinking, this could mimic what the code in the PCM does in cleaning up the knock signal...and pretty inexpensively.
When analyzing, the knock event logs from this they would need to be overlayed onto timing logs, find timing being pulled, then look at what shows for the knock event. This setup would not be 100% but enough to get a basic idea of what conditions and when knock starts ocurring.
After a fair amount of logging and analyzing you might be able to tweak the knocksense unit so that you can have it send a signal (to a LED for example) just before you would expect the PCM to pull timing....set the knocksense to be a little more sensitive then factory.
" The internal threshold pot can be set so that it triggers on the desired level of the knock signal".
Using the led from the knocksense, a decient wideband, EGT readings, and boost you might be able to road tune a little better, no?
Anyway, if you have some time, explain a little more about DFT withou me having to read what you linked
