Knock Detected as histogram?

[The1]

for the tables this should be the calcs, fair few xdf's have wrong calcs

For Ignore and Addon Time Tables (MSec)
X*(.015259*8)

Recovery Tables (Deg/Sec)
X/(256/90*(E+1)/8)
E = Scalar ESC 12.5ms Loop Recovery Update Delay

Attack Rate Multiplier Table
X/128

Attack Rate Vs RPM (Deg/MSec)
X*.01526

[VX L67 Getrag]

Thanks for that The1, even if it's cleared on the next frame I would have thought if you choose in the history table for maximum or minimum it would show if it every got triggered, but I'm not as knowledgeable as most of you guys!

[antus]

No, it will not show if it ever got triggered. The ecu operates quicker than the serial link. What you see in the log, is snapshots of the state of the inputs and outputs at the moment the frame is sent. Events like 'knock detected' can be set, processed and cleared between frames and the ecu wont put it on the data link and tunerpro and you wont see it at all if thats the case. The ecu does not log that its happened but you havnt seen it yet, and does not make a note to include it in the next frame for you. As Tuner Pro never sees it, it is not included in the history tables (which it calcuates itself from the data received from the ecu. If it happens enough, then you will see some of them so the data you see is worth something, but you wont see all the events. Also you would have noticed but for anyone else reading this thread trying to understand more about logging- tunerpro needs to playback the log to collect the data, so you need to rewind to the start of the start of the log after pick a different type of histogram, hit play, and pick acquisition -> playback speed, and either pick 400% (ctrl+4) or pick custom if you want to go faster again and let it run through to do all the averages or min/max again (perhaps user custom: 10 or 20 for 10x or 20x). PC/Laptop speed will be your limit here.