NefMoto

Hi guys,

why my car runs on 14.1~14.7 afr!?

i have a big turbo with greddy profec it boosts 1bar.
i wanna start tuning but my afr doesnt change with these maps. what will i do?

On lots of ECUs, (MED17.5.25/21) for example, LAMFA is disabled and no matter what you change it to it wont affect AFR, it Will run 14.7 until BTS lambda map is active, i just maintain LAMBDA BTS active all of the time by changing mínimum temp for component protection and setting it to 0 so its always active and the you can control lambda perfectly with BTS maps and with better resolution

hmm.. good idea.


so, does it make sense to change the kflf?

No.

Also ditch the greddy.

If the LAMFA module is in the binary then it is no problem to enable it.
Just because you don't know what to do doesn't mean "no matter what you change".
Read the FR and log with a ram logger, and the "impossible" becomes possible.

So this here is 100% misinformation.

As for the OP - is the map even defined properly?
You did not mention what ECU you have or anything of that nature.
Also, this is not how you tune the LAMFA map. You destroyed your fuel efficiency after 3800 rpm basically for no reason.

I've 2004 Audi A4 1.8TQ, 190ps bex engine.
I have ME7.5 ecu.
i read the afr on innovative wideband.

Whatever I did did not happen. where am i doing wrong?

I've a big turbo (16G) and i want to run 11.8afr.
it runs 13.7 afr at the moment  ???

Post logs WOT 3rd gear 1500-7000 rpm from me7logger.

i'll do it today.


how can i tune torque limits/settings?
which maps should I review(learn) to find out?

understanding the relationship between IOP/IRL is all you need.

There is an exhaustive explanation in the s4wiki

Logging all of the applicable vars is tricky since ME7Info doesn't find them all.

disassembly or possibly the various tools from prj/trev may help

No don't edit random things. Why would you do that w/o any evidence whatsoever that that is your issue? I also doubt whatever you changed made any sense since you didn't say what problem you were trying to fix.

You didn't post logs.

You certainly didn't post how you found the rest of the torque RAM locations. All of this is necessary if you expect to be able to tune IRL/IOP past the very basics.

i was unable to get log due to corona virus.
i just wonder how to fix mixture and modify afr. so i will start tuning little by little.

i have a big xdf file for 8e0909518ak. my file is 8e0909518an.
i use ak file to find maps for me. i have a lot of maps i need.
...attaching xdf (not correctly categorized)

RAM locations are not map locations. They're for logging.

we can't help you without logs. But you can help yourself by readig this topic.
http://nefariousmotorsports.com/forum/index.php?topic=6955.0title=
Here you will find that LAMFA on this engines are smoothet by other maps. But you will find all in that topic

Read again, i said: "no matter what you change 'it' to" referring to LAMFA map, if its not activated, then no matter what you change the map (LAMFA) to, you wont see any change in open loop fueling. I know it can be activated, i've read the FR, i usually dont but thats personal choosin. I was just telling him why his changes in LAMFA wont affect his fueling.

you are wrong, on this Flash ECU follow LAMFA( as it is any other ME 7.5) only flash is made so it can be smooth

He didnt specifiy what car or ECU he was referring, which is why i told him about some med17s not using LAMFA and just BTS maps when EGT protection hits. Just realized his log says aud a4 b6, but not atm of writing the reply to OP

i wrote later message.
I've 2004 Audi A4 1.8TQ, 190ps bex engine.
I have ME7.5 ecu.
i read the afr on innovate wideband.

i cant get log due to corona. after monday, i can go out for test & log.
i think i cant activate the lamfa. hope, it will after log with your suggestions.
thank you all.

which values should i log?
its attached one

Why are you using VCDS?

i coldnt connect with visual logger. i have vcds cable.
please help with this cause modifications i made on maps dont effect :S

here are my files.

Don't care about your files.

Get ME7Logger working.

So which values should i log?

Typical config comes with me7l

In vcds log you posted spec lambda goes to 0.8 so whats the question?
Actual doesnt follow it and you doesnt log o2 regulation, trims etc
And btw there is no boost :)

Nye what happens last year with the people?

Hello! I have a similar problem on the Audi A4 B6 1.8tq 8E0909518F 360910. lamsbg_w follows lamfaw_w or lamfawkr_w with a big lag. I can not find (kf) tlafa in my firmware. I found cwlamfaw 0x1915F and zklamfaw 0x1D900, I will be grateful for the correctness.
My IDA project:
https://drive.google.com/file/d/1ioAEfJT2MAWnDnyvJAVBQSe8CzNVa3fy/view?usp=sharing
Log:
https://drive.google.com/file/d/1Y7vLxqWDL_7YTGyryqdlozPzxFCt-sfJ/view?usp=sharing

Logs are in .csv format, you posted a .png.

Log uploaded to googledrive. The same log

Set ZKLAMFAV = FFFF, the situation has improved, but lamfa_w does not follow the smallest lambda value

Looks like it is following lambts just fine

Thanks for the answer! Apparently in my firmware, lambda follows lambts best. After small experiments with the lamfa axes, got a more or less working result. There are no more retards. I think I still need to edit zklamfaw

I do not think you should alter zklamfaw at all.

You're right. I tried the value 0xCCCC and I did not like the result. 91oct gas  :-[

Just add enough fuel with lamfa/bts to pre-emptively prevent knock.

ZKLAMFA is there for protection. like BTS.

That is exactly what I am seeking :). http://nefariousmotorsports.com/forum/index.php?topic=17681.msg135831#msg135831 I seem to have succeeded here, but I seem to get rich too soon and quickly. Or am I wrong?

Several months ago using IDA I found ZKLAMFAW maps at 8E0909518F.
They differ from other firmwares and have a table size of 1x6. For 8E0909518F 0261206878_1037360910 they are located at 0x1D870 and 0x1D87C.
With them I finally got control of Lamfa

I believe those maps are actually KLZKLAMFAW
 
I have a full damos for 8E0909518F 363670 if you need