Hello everyone,

I'm been browsing around on this website/forum for a while now but never dared to tamper with my car... Until now.

So I'm the current owner of an Audi S3 1.8T AMK EG.

More info ECU wise:
8N0906018J
0004
360314

So, my initial strategy was as follow: keep my stock ECU as is, buy another one and start messing around with that one on the bench without immobilizing the car.
I have plenty of question on that subject but let's put that aside for the moment as I found something else on the car that worries me.

So, one of the previous owner did a poor job of tuning the car and blew the engine. It had to be redone. Previous owner assured me the car was reverted to stock during that rebuild.

Except when I compare the content of my ECU to a basefile I found on the forum. It doesn't add up.

Differences (Map name - my understanding of the map - start addres in hex):

KFKHFM (Correction map for Mass Air Flow) - 0x10C23
KFMIRL (Engine load request - rlsol) - 0x150CA
KFLF (Injection time scaling) - 0x18B20
KFLDIMX (unclear to me) - 0x1E200
KFLDRL (Map for linearization of boost pressure) - 0x1E352
KFLDHBN (Maximum pressure ratio - usefull for atmospheric pressure adaptation) - 0x1E8F2
LDRXN (Maximum load - boost pressure control) - 0x1EAD4
LDRXNZK (Maximum load if knock) - 0x1EB16
?? (No info in xdf/a2l) - from 0x1BC90 to 0x1BD59
?? (No info in xdf/a2l) - from 0x1E760 to 0x1E8DF
?? (No info in xdf/a2l) - from 0x1E932 to 0x1EAB1
?? (No info in xdf/a2l) - from 0x1EB94 to 0x1EBD2
?? (No info in xdf/a2l) - from 0x1FC46 to 0x1FC7C
?? (No info in xdf/a2l) - from 0x1FE36 to 0x1FE3C

?? (No info in xdf/a2l) - from 0x8D93A to 0x8D949
?? (No info in xdf/a2l) - from 0xFFFE0 to 0xFFFE5
Those last two might not be mapping related. I don't know enough yet to be certain.

I'll link all the files I used so you can check by yourself if you want to. This above is just a short summary.



So my questions are:
1) Is my map short definition somewhat near the truth?
2) What is all this? This thing has modification on fueling & boost but no ignition. I'm kind of lost here. Does it look legit to you?
3) Any info on the map I didn't have a definition for? Didn't find a .a2l with that info.
4) Could the differences be linked to hardware modification (sensors?). I don't think by looking at the map modified (except maybe KFKHFM) but I'm clearly not an expert.
5) Should I revert to standard mapping I found here?
6) If you took the time to read all this, THANK YOU!

Edit: No sure if this is the right section for this kind of question. But I'm a noob after all and this is not exactly a rate my tune. If I'm mistaken just let me know

There is a full hex/a2l for your binary freely available.
Look around for it, if you haven't yet.

And yes deffo go to stock first. Never modify a tuned file that was not done by yourself.

Attached.
Not a2l, but dam is good enough to locate everything for tuning.

Wow, thanks for this prj!

Thanks. I've no way of reading .a2l/.dam at the moment. Is there any free (and legal, obv) tuner soft that can read those definition files?
If not I guess I'm stuck with TunerPro for now and I'll notepad the sh*t out of that .dam file into .xdf. This might even be helpful for other people I guess.


Honestly, you lost me there but I guess I'll figure it out as I go forward

Thanks!

So, little update:

As I mentionned earlier. I'm trying to understanding the structure of the .dam file you shared with me. So far I found table definition looking like this.



So what I deduced so far:
/SPZ gives main information about Table: Name, Description, TBD, Start address

/SPW gives information about Cells of the table: TBD, Cell Data Size, Min Value, Max Value

/SPX gives information about X-axis: TBD, Cell Data Size, Min Value, Max Value, TBD

/SPY gives information about Y-axis: TBD, Cell Data Size, Min Value, Max Value, TBD

/FKX : TBD (I tought it was about X-axis size but does not seem to be the case after investigating several table)
/FKY: TBD (same as FKX but for Y-axis?)
/ABL: TBD

Is there any truth to what I just wrote?
If so and if I find all those info, I'm pretty sure I can create a script to translate .dam into .xdf for the ones among us that can't afford WinOls.

Ok thanks. It will make logging easier.

Is it possible to do this in 512kb ecu?

I've searched in S3 1024 file and found "3D 06", if I search the same in my 512kb ecu the value is different