RomRaider

Yes, but you don't need to reflash, you can also just reset. But anyway, that's exactly what I mean by logging. Logging and tweaking is what tuning is all about, IMO. Learning View is a quick way to get some info about whether or not your tune needs work, but by itself, it's not enough for tuning.

You need to log multiple pulls to cover the whole FLKC table. With an MBC that's not hard. Without an MBC, you can probably still cover enough of the table by doing pulls at part throttle.



It would be easier, and more reliable, to log FLKC, FBKC, and IAM. More useful, too - logging will give you a more precise indication of the RPM and load where the knock event actually occurred. And note that LV does not show you anything about FBKC anyway. FBKC is the least interesting of the three, but it shouldn't be ignored.

sixstar1979, I moved your post to its own thread in Tuning Discussion.

viewtopic.php?f=15&t=7023

Great thread NSFW! Has helped me understand quite a bit!

What does it mean when Learning View shows positive FLKC when IAM is at 1? Everything I've read on here says this shouldn't happen, that FLKC gets reset when IAM changes and FLKC will only be used to reduce timing if IAM is at 1.

I've attached several examples (please ignore the high MAF DTC, that is a separate issue for maxing the MAF during wot in the rain).

Go into your ROM right now

Your FLKC retard value has been set at a positive value(looks to be +1.01), not a negative value so it is ADDING timing when it knocks

Holy cr@p! Thank you so much. I looked back through my change log and that was set by my tuner 2 years ago when he did my initial stage 2 tune. I guess this validates my decision to go to move to a new guy.

I've got this fixed now. Thank you, thank you, thank you. I guess this is a lesson learned to always check your tuner's work. I'll be sure to do that going forward.

I've made that mistake myself...

So, if it is all 0's, does that mean there is no knock - or is it possible to knock and not have it show in LV?

is possible to have mechanical knock and not have the ECU 'hear it' as it would ignore noise in ome cases. That said, have seen LV show values when knock ears could not sense it.

It means there's no learned knock regions. That doesn't mean no knock as feedback knock will still retard timing and that will only show up in logs you make.

Awesome write up!!! thanks for doing this!

Thanks for this awesome info.

I have tweaked the Fine Correction rows (rpm) but I'm wary of changing the Fine Correction columns (load). I was planning on having values of 1.30, 1.64, 2.00, 3.00 because the max load I saw during WOT pulls is about 3.30. These numbers are also the same as the factory values with the exception of the last one which is at 5.00.

However I noticed in the Fine Correction (Range) table that fine correction is disabled above a load of 3.00. So probably no point in me changing the highest value in the Fine Correction columns (load) table from 5.00 to 3.00 then. I'm assuming it's disabled above 3.00 because of the chance of false knock created by noise from a screaming engine.

Am I understanding this correctly? Should I perhaps change the columns to 1.50, 2.00, 2.50, 3.00? Any harm in doing this permanently?

Thanks.