Yortt wrote:When 12p was first released it did not have the ability to log knock retard it only had knock counts. I cannot understand why you would want to log knock counts and not log knock retard.
Is there some benefit in logging counts that I am obviously not aware of, as festy's post clearly indicates there can be knock but no knock counts.
Other way around, knock counts were added in 12P. Knock retard was always included, and was in the original $12 bin. Knock counts were added so you could setup the ignore counts table.
There cannot be knock retard with no counts, the knock retard value is calculated from the counts. What can happen is the counts get missed when logging, the counts happen quickly but the knock retard is slow to decay which is why it may appear to have retard without counts. Lets say you are logging at 10Hz, or 100ms between logging frames. Knock counts are a delta count over a 12.5ms period, so with 100ms gaps between logging frames there are 8 delta count calculations which you missed 7 of. If only one of those 8 had some delta counts (which would then produce some knock retard), logging only around 1/8th of the calculations there is a pretty high chance of that one delta count calc being missed.
So in 11P v104 the change was made to show the actual knock counter, rather than a delta of this counter. The knock counter item is continually incremented by the number of knock counts. Trouble is its a different way of reading the logs (your looking at a flatline of counts being no knock, and a step/change being knock), and its not possible to have a histogram thats of any use. I changed this in later (unreleased) versions of 11P back to the normal type of logging view with knock count spikes, except its a new ALDL item that sums between logging frames. Once sent over ALDL it resets to 0 and starts counting again. So its a delta counts between logging frames rather than delta counts per 12.5ms. The PCM knock code remains unchanged though.