Need BTS, ATR, etc too, it will be one thing after another I think.

Throttle will need redone as well iirc.

3rd gear pull.

Check the S4 Wiki, Nyet did a very comprensive write-up about the ME7 torque structure.

Also, I would highly suggest getting yourself a registered version of MegaLogViewer from EFIanalytics. It's only about $70, but I live and die by that program when it comes to tuning my cars.

It allows you to take the CSV and lay out trace graphs, scatter plots and histograms.

FYI: you're running into problems whenever your misopl_W value exceeds your mifa value.

If you look at the logs, you're running into timing interventions even at part throttle. But at WOT, the timing pull begins at 3200 as soon as you go WOT

so..MRFA_W is going to 105% but my MIFA_W is staying gradual. It's not hitting MIMAX exactly, its a few percent below it but is that still indicative of intervention? Should MIMAX be raised to what MRFA_W (from KFPED) can go to?

Well, here's the basic stuff for logging. Set up me7l cfg file with factors from "similar" known vars.

mizsol_w 0xCC96
mibas_w 0xCCAA
misolv_w 0xCC90
mizsolv_w 0xCC94
dmzms_w 0xCC82?
dmaufr_w 0xD298
etazwb 0x3809E0
dmllr_w 0xCAFE (tee-hee)
dmar_w 0xCBB8
zwbas 0xF535
dzwb 0x3809D9
miopt_w 0xCCAE
mimax_w 0x3853DE

B_zwvz 0xFDA8.4? or .3?
B_zwvs 0xFDA8.2

I also strongly suggest FFing TMAR at 0x10FD8, to take ARMD out of the equation.

Also I think that it's a good idea to log rlmax_w at 0x385272

Most of the addresses should be correct. I definitely need some sleep now, will update the post tomorrow with more vars.

wow that was quick. thank youuuuuuuu. wish i had check this before i left to go logging tonight!

Well I do not propose always running it like that. For testing purposes only.
Orrrr, well, just watch the dmar_w - if it's zero, you're fine ARMD-wise. 

I strongly suspect that the problem originates with rlmax_w since the car is originally NA.

When in doubt - use "RAW" conversion factor of 1, compare with other vars and correct the value afterwards.

I didn't like what I saw in your log happening with the variable I named "rlmax_w", which is why I went and picked another (NA) ECU to cross-reference stuff to.
Turns out, the NA var is actually called rlmxs_w, and funnily enough you have already looked that way.

So, after rlmxs_w is formed, it goes through KFMIOP to form mimxl1_w, which is then multiplied by FMIVL to finally output mimax_w.
Anyways, looking again at your log, your WOT run doesn't seem to trigger any tq intervention?

I'll look at the part throttle one in a few.

Well, part throttle is not that happy, but nothing too severe. Some ARMD action here and there, etc.
Let's start with the basics: what are we trying to solve? What is the initial problem? WOT run seems fine torque-structure-wise. That "sawtooth" pattern you see on the zwbas/zwout plot is normal since you have different CFs in different cylinders - and the logger just samples them one by one. So it can pick 0 degree cylinder, then pick the one with -4.5 CF, then another one with zero. Boom, you have a dip on the graph.

If you're concerned about the lack of ignition advance up top - well, tune the KFZW tables then? Adjust the axis if it's not enough. but be careful with other maps that run off the same axis. Let me know, I can list those for you.

EDIT2: Nothing to be scared of. SRL11OPUW works only for KFZW/2 and KFMDS in this bin.

EDIT3 (I just love editing my posts, yeah): Might want to play some with ZWOP to make etazwb a bit higher, but that's optional, I guess.