So fine knock learning isn't an actual knock event. Feedback knock is real time values that show timing being taken away when your engine knock sensor hears what it thinks is knock, and the ECU takes away timing to protect itself. Many times these events are noise or false knock.
Your datalog actually looks decent and the feedback knock value and dam look fine. I am by no means a guru when it comes to tuning or reading datalogs, but from what I can tell everything looks ok.
Fine knock learning at only a -1.05 value is well within normal boundaries. Although staying at 0 is ideal during WOT pulls, but at times not practical. Somewhere along the line your ecu detected a knock event within that rpm/load range where you are seeing fine knock learning corrections and now the ecu is automatically taking away that timing to prevent a future knock event to happen within those parameters.
In time, as long as your car doesn't detect knock in that rpm/load range, the fine knock learning will learn itself out and back to 0. With no actual feedback knock being detected you have nothing to worry about.
Your datalog actually looks decent and the feedback knock value and dam look fine. I am by no means a guru when it comes to tuning or reading datalogs, but from what I can tell everything looks ok.
Fine knock learning at only a -1.05 value is well within normal boundaries. Although staying at 0 is ideal during WOT pulls, but at times not practical. Somewhere along the line your ecu detected a knock event within that rpm/load range where you are seeing fine knock learning corrections and now the ecu is automatically taking away that timing to prevent a future knock event to happen within those parameters.
In time, as long as your car doesn't detect knock in that rpm/load range, the fine knock learning will learn itself out and back to 0. With no actual feedback knock being detected you have nothing to worry about.
