Are you referring to the exercise we did comparing I-Max to WGDC? Continue to refine that?
No. He's referring to the adaptation channels which modify the i-lmit.
ldimxa_0 , {BoostCorrectFactorPID-IRange1} , 0x383D56, 2, 0x0000, {%} , 1, 0, 0.005, 0, {Adaptive Korrektur der LDR I-Regler Maximalwertbegrenzung}
ldimxa_1 , {BoostCorrectFactorPID-IRange2} , 0x383D58, 2, 0x0000, {%} , 1, 0, 0.005, 0, {Adaptive Korrektur der LDR I-Regler Maximalwertbegrenzung}
ldimxa_2 , {BoostCorrectFactorPID-IRange3} , 0x383D5A, 2, 0x0000, {%} , 1, 0, 0.005, 0, {Adaptive Korrektur der LDR I-Regler Maximalwertbegrenzung}
ldimxa_3 , {BoostCorrectFactorPID-IRange4} , 0x383D5C, 2, 0x0000, {%} , 1, 0, 0.005, 0, {Adaptive Korrektur der LDR I-Regler Maximalwertbegrenzung}
ldimxa_4 , {BoostCorrectFactorPID-IRange5} , 0x383D5E, 2, 0x0000, {%} , 1, 0, 0.005, 0, {Adaptive Korrektur der LDR I-Regler Maximalwertbegrenzung}
ldimxak_w , {BoostCorrectFactorPID-I} , 0x382742, 2, 0x0000, {%} , 1, 0, 0.005, 0, {Aktueller korrigierter Begrenzungswert I-Anteil LDR}
They're like fuel trims.
1. Lean it via LAMFA - Try to get closer to 11.5 on the wideband?
No. But might want to numb BTS first to see where KR goes. Logging req AFR is hopefully accurate enough for that activity, and making sure IDC doesn't exceed 95.
2. Increase timing via KFZW/KFZW2 - Do this until I see some timing retard and hold there or pull back slightly?
Yep. This. But only after we have fuel where we want it.
3. TABGBTS (EGT Threshold for component protection) is not something we have touched thus far. Current value is 499.99C, what's the reason for raising it? If EGT's are going to come down with the changes to fuel & timing why would we need to raise the EGT threshold?
Well, unfortunately, EGT and timing are interrelated, so we kinda need to numb one (possibly temporarily) so we can tune the other, then see where we end up after.
