Great news, thank you very much.

The only thing now is, with 0 KFDDLBTS, if i tune FBSTABGM like we're debating... Will it enrich if timing retardation happens?. Because of course actual egt increases, but don't know if that means tabgbts_w (which is the input for FBSTABGM) increases too.

I mean, I know it's modeled to increase if load increases or lambda decreases, but don't really know if it looks at timing retardation (because it's just the function of kfdlbts*kffldbts)... It's good to know because it's just what I pretend

I know isn't the right subforum but now that we are here...

Is there any method to know what maps share their axis? For example if I re-scale one of them I'll have to reinterpolate all those others with the same axis

I'm not very sure about doing it in TunerPro, but I think i guess how to do it in winols, I'll take a look nyet, thanks.

What's more, I use TunerPro to tune the maps I know doing the xdf by myself helped by the fully defined .kp... So it's not really a problem knowing how to do it only in Winols.


By the way, I ended up leaving the maximum of FBSTABGM as 1 and put 0.1-0.4 at high values of KFFDLBTS with stock KFDLBTS (Which is pretty linear)
I only want to enrich from 0.82 (kflbts) to maybe 0.8 or 0.79 if timing efficency drops. Which I consider conservative enough for a stage 1+ (maf 175g/s), having in mind the 3"DP that's installed will decrease actual (but not calculated) egt.

I looked at some logs and substracted actual timing from KFZWOP
entred it in ETADZW to obtain efficency
entred it in KFDLBTS, multiplied by KFFDLBTS, made the calculation in LAMBTS diagram and it does theorically enrich that 0.03 lambda I was looking for.
From the logs, areas with timing retardation (Little bit, 1-5-3º), a little bit more enrichment than the others with 0º

Now, question... As I keep learning more and more questions appear:
Looking at LAMBTS I atually don't see TABGBTS as an activator for BTS. Why? TABGBTS is set at 400ºC. But FBSTABGM has as first value @900ºC = 0, so that 0 multiplies and makes the output from LAMBTS stoichiometric, equal or leaner than LAMFA and therefore LAMFA will manage lambdas.
@920º TABGBTS=0.5 -> 50% BTS enrichment
and @940 and more, TABGBTS=1

So that 0 extrapolates as 0 below 900º and I'm not gonna enter in BTS till 920ºC. What's the function of TABGBTS then? am I understanding ir wrong?
Should I put 1 at the entire FBSTABGM? that'd extrapolate as always 1 and make the car run always in BTS, which I don't know if its a good approach. Or does being below TABGBTS certainly use only LAMFA?
Should I enrich LAMFA map a little bit? (which now is stock)?
Should I cange the axis to for example 700 800 900 1000º?



What do you sincerely think about this? Feel free to comment, I accept "Stupid pre-engineer (only 6 subjects left), you're an idiot and you're gonna melt yor engine or bend a rod"

I'm doing a project at university about remapping my me7.5, that's why I've re-taken this.


Ps: When Spec lambda goes below 0.8, inmediately actual lambda goes exactly 0.75... even if spec lambda is 0.79. I don't know why.
Is actual lambda near 0.79 but stock wideband goes out of range and shows 0.75?
Does the stock wideband read 0.79 but the diagnosis tool shows 0.75?
Am I going really 0.75? why? my car is not the first one that makes so.
Sorry for that huge amount of questions guys...

I believe the minimum the wideband can read/display is 0.75 (as per LALIUS).

However, there is LALIUSMN which is the minimum measurable lambda. You can reduce from 0.79 (at least that's what it was in my ecu and sounds like the same in yours) to 0.75 to log down to 0.75.

Great idea mate, I'm gonna take a look

LALIUS:

Lambdalinearisierung, LSU-Sonde vor Katalysator (22x1)

(LSU-Spannung vor Kat, korrigiert)/-

      V                                                               
      0.3027   0.8008   0.9912   1.1768   1.2988   1.3770   1.4160   1.4551   1.4941   1.4990   1.5234   1.5527   1.5771   1.6260   1.7139   1.8213   1.9287   2.2314   2.5098   2.7881   3.1641   3.4619
-   0   0.75000   0.84009   0.87988   0.91992   0.94995   0.96997   0.97998   0.98999   1.00000   1.00195   1.01001   1.02002   1.03003   1.05005   1.09009   1.13989   1.19995   1.39990   1.64990   2.00000   2.80005   4.00000

Shitty resolution at the low part

LALIUSMN: 0.80005

So that means you were absolutly right. That helped me a lot Spacey3. Thank you very much !!

I don't really understand VAG/Bosch in this... why to cap minimum measurable lambda?

Ahám, that makes sense... what doesn't is to put that limit at 0.8  Being lambda linearization map programmed to a minimum of 0.75

Anyway, I decreased LALIUSMN and now it works perfectly and as planned, reads 0.79 when needed.

Thank you all guys.

One more time: modeled egt!=actual egt and ATR!=BTS

Of course is different, but the engine doesn't know actual egt. It only knows calculated egt.

Whats more, from FR, LAMSEL:



There's no egt sensor in the AUM, so SY_ATR = 0, then dlamatr_w doesn't matter at all, additive will be 0.

Ps: One more time? Is there any previous one?


Thanks a lot



As i'm realizing, the actual map TABGBTS is very different from the word tabgbts_w. The map has something to do in the hysteresis delta RSP. I'll study it better in a while.