I want to BTS to kick in just before ATR to hopefully prevent ATR from engaging. ATR kicks in at 950c physical. I went through great pains to ensure that my fueling and MAF scaling is as close to real value (not underscaled) and actually logged BTS vs ATR while torturing my engine. In my tune, there was only 10c difference when temps entered ATR reaction zone.

Otherwise I don't want the BTS interfering with anything.

Would you be happy if your timing map had same resolution as your LAMKR map?

So basically.. to sum things up.. (in my head, after reading countless of pages..)

i can use KFLAMKRL as "main" fueling path.. at column "0 degrees", and this map is lambda value, with actual engine load% as the other axis?(this axis wont go over 100%, right?)

..then i add more fuel at higher "degree" columns if knock activity raises and more timing is pulled..

i can then use LAMFA, which is rpm and requested torque based, to add preemptive fuel at spots where i know the engine is prone to detonation.. ie att the tq peak.. leaving the rest of the map at lambda 1 (for the KFLAMKRL to override as primary).

i then have BTS kick in at high calculated EGT(850-900ish) to cool things down if pushed too hard, i.e long pulls at the track.

ATR is actual EGT-sensors and regarding those maps?


have i understood things correctly? or are there more maps i need to fiddle with regarding the KR based fueling?

i have been following this interesting thred for quite some time now, thumbs up for all the time spent looking into this, keep up the good work guys  

rl_w will exceed 100.
mrfa_w in LAMFA will not exceed 100%.

Yes, just remember that this axis is not considering only knock regulation. It is also includes dzwwl which will offset wkrma a few degrees.


Personally, I have tabgbts set to 650 and plan to adjust it accordingly from logs.


KFLAMKR - multiplier for lambda in KFLMAKRL
KFLAMKRL - target lambda values
DLAMTANS (optional) - offset lambda for IAT
CWLAMFAW - clear bit 0 to disallow positve offset from DZWWL

ok, thank you for clarifying, and this is actual load?
why im asking is my axis in a me7.5 032HN box looks like this:

20.25
39.75
60.00
69.75
80.25
90.00

which is totally useless then for this KR-based fueling method..
and you would think this would go beyond 100 even in the stock tune.. yet it doesnt..
is there a reason why it looks like this? which other relevant MAPS share this axis? (if i am to modify it..)


DLAMTANS, can this one be tuned to i.e add extra fuel at IATs higher then +50c? (originally it seem to be configured for extreme cold conditions)

Column units

Either axis address is bad or an option called "Step" in the table definition is set to default -4 or whatever tunerpro likes to do. my TunerPro likes to reset these on some of my maps for no reason resulting in weird looking axes.

THank you!  Its fixed now.

Here's what I had to do for future reference:
 I had to change the label source to "internal pure".  This allowed to to edit the address step.  I then changed the address step to 1 in both rows and columns.  it was at -4.