KPRO V4 enable target lambda not work

[EGK2082]

kpro v4 enable target lambda not work
Hi, I have my eg with k20a2 ecu prb with kpro v4
wideband aem 30-4110 connected in analog input 0
I have my fuel tables tuned to open lop between a / f 12.5 and 13.
Enable "open / closed loop target lambda" (kprov4) and modify my target lambda (high cam) tables in WOT column 9 and 10 to an A / F 12.8
I do a datalog and my A / F in wot gets rich around A / F 11.
Then also enable "fuel compensation from target lambda tables" thinking it would be the solution, I do my datalog and my A / F in WOT gets rich again around A / F 11

Because it does not work? because my A / F in wot is not what I load in my "target lambda high cam" tables
Because the A / F in my datalog doesn't match the 12.8 value I have loaded in my "lambda high cam target tables"?

[Spunkster]

Post your calibration as well as a datalog showing the issue.

[EGK2082]

datalogWOT.kdl

(31.99 KiB) Downloaded 110 times

if I disable target lambda my a / f stays as tuned between 12.5 and 13, and if I enable target lambda tables my a / f en it is enriched to 11

calibration.kal

(160.61 KiB) Downloaded 134 times

[Hondata]

Raise your maximum MAP for closed loop.

[EGK2082]

ok i will try that

[EGK2082]

I did a little test on WOT and it works fine.
I cannot understand why in the s.trim datalog it is taking out an average of -10% of fuel to reach the 12.8 target lambda.
My tables disabling target lambda are tuned between 12.5 and 13 average in wot, I do not understand why enabling target lambda my dtalog removes so much fuel to reach 12.8.

datalog2wot.kdl

(43.53 KiB) Downloaded 117 times

calibration2.kal

(160.65 KiB) Downloaded 114 times

[EGK2082]

Some answer?

Why does my target lambda in wot s.trim remove so much fuel to reach the target a / f 12.8 since my fuel tables are tuned well between 12.5 and 13?

[Hondata]

You would need to show us a test with the closed loop disabled and then another one with the same calibration and conditions and closed loop enabled.

It does work though. Thousands of people are using this for many years.

[EGK2082]

My a/f enabled target lambda is not stable, ej. look at 4918rpm a/f 13.56 and afcmd 12.8 and s.trim -16 ??? and so many rpm points with a lot of difference, when everything should go 12.8, and also the differences do not coincide with respect to the fuel removed by s.trim

disabled target lambda my fuel is much more stable.

I also use kpro for years, my problem is with enabled target lambda

calibration3enabled.kal

(160.62 KiB) Downloaded 105 times

dat3enabled.kdl

(32.63 KiB) Downloaded 98 times

calibration4disabled.kal

(160.62 KiB) Downloaded 104 times

dat4disabled.kdl

(44.81 KiB) Downloaded 121 times

[Hondata]

On the disabled calibration the WOT compensation is disabled. On the enabled calibration the WOT compensation is from the target lambda tables, so the ECU adds fuel and then immediately has to pull the fuel out again to meet the target. That's why it has the negative short term trim.

[EGK2082]

yes perfect that is understandable, but why my fuel not stable at 12.8 with enabled target lambda, if my target lambda tables are loaded in wot at A/F 12.8, it is not a small difference, I have many points from 11.2 to a/f 14.3. Thus it is not safe to use enable target lambda in wot.

I thought that kpro v4 had that possibility with enable target lambda to keep fuel stable with the a / f that you load in target lambda
My tuned fuel disabled compensation is more stable.

[EGK2082]

and s.trim with negative value never manages to reach the target that is loaded in my target lambda of A/F 12.8

[Hondata]

I suggest reading the help again and looking at your calibration because I still do not think you understand the difference between compensation and target lambda.

You always want the fuel trims to be as close as possible to 0% so you need to tune open loop with the same compensation as closed loop and the same target lambda for both.

Finally there is some problem with your laptop datalogging as the sample rate is poor so I would consider using on board datalogging to get better resolution. Also placement of the o2 sensor is important for response time and accuracy.

[EGK2082]

Target lambda tables are used in closed loop for the lambda target and both in open and closed loop at fuel compensation (similar to WOT compensation). Changing the target lambda table will also change the fueling. This way the lambda can be changed without needing to change the main fuel tables

that's the only explanation in the help file, anyway I always tune in wot without compensation, but I want to understand how it works by "enable target lambda", since I see several posts and in other forums confused with this, and the The only explanation in the help file is that.
Let's ask the simplest question, explain to me how I can make "enable target lambda" and that my a/f in my datalog is constant at 12.8, because it is not enough to just load my tables in wot with my desired goal 12.8

[EGK2082]

I appreciate a logical response please, the help file is very simple, there is no explanation whatsoever.