So this is fantastic. Apparently I haven't been logging knock retard this whole time. I set up a histogram for it and I always check it, looking back I should have known that no data at all isn't the same as all 0's. lol So ok I started logging it and during the first drive I get a small area with some 3's and 4's while normal part throttle cruising. So rather than watching the laptop instead of the road I just take it easy so I can check the whole log later and see if anything pops out at me. It never did it again.
So I'm looking it over later and the wb wasn't logging. That's happened before so I try to quickly check that everything is logging before I go, but I guess this time I didn't notice that it wasn't logging. I just wanted to see if the kr was during a lean spike or something. The stft's did add about 5% right when it happened but when I looked at other logs to see how the stft corresponded with the wb, it didn't seem like 5% was a huge response to anything so who knows.
What causes it to not log certain channels sometimes? Am I logging too many channels? I have no idea why I'm logging 3 or 4 different throttle position channels, so I did away with those. I've read of people saying to keep channels to a minimum, even not logging MAF when it's turned off as an example. Anyway on the ride back I made sure the wb was logging and it didn't register any kr that time at all so Idk why it did it that first drive. I'm still running stock spark tables, the only thing I've done with it at this point is move the IAT tables over a couple columns. Possibly false knock? Well at least I can keep an eye on it now.