NefMoto

Thought I'd share this, since I was not able to find an exact xdf for my 8N0 906 018 BP Audi S3. However, I found a pretty close one thanks to this thread: http://nefariousmotorsports.com/forum/index.php?topic=2511.0 for 8N0 906 018 BH, which I then modified to match the addresses for the 8N0 906 018 BP  + I added a few new scalars I had the addresses for.

If someone has a better file I failed to find or addresses for maps that are missing from this one, I'd really appreciate it if you share. Thanks!

Here's version 2 of the file, I was able to track down a few tables that have to do with cold starts and warmup, they have been added now.

Added some idle control maps, thought to update the file...

Here's what I consider the last version of this file. I pretty much have everything I need to tweak the areas I needed. Please note that I've configured this file to work with MTX's plugin for checksum correction. If you're not using this just go to XDF->View/Edit XDF Header Info->Checksums(tab) and remove the selected checksum.

Still, if someone adds more tables to this, it would be nice to share {:

I found a nasty 1 byte error in the definition for the FKSTT_0_A and FKSTT_1_A (Cold start enrichment factor) tables, which were messing up the numbers big time. Decided to update the file. This is the only difference to the previous file.

nicely done man

Been playing with the car a lot more lately, so I've added more tables, hopefully someone will benefit.

Hey
Can You share ori bin file for this xdf ?
Regards
Kris

Sure

Also the latest version of the file.

is there a chance to upload this map to an A3 1.8 180hp and improve the hp ?

I have added: CW_SAWE and KFTVSA for popping/gargle .

Thanks for the upload! How does this work exactly?

I am afraid your file had a small error with the address of this map. I have corrected it and attaching a new version. Please double check if you want.

Hi,

I downloaded the latest tunerpro to load your v9 XDF and your Original BAM Bin works absolutely perfectly in it, but my bin from my 2003 BAM TT doesn't, all the figures are wrong.  Although the same XDF and BIN files worked perfectly well in my AMK S3 - if I was to start using your XDF and edit your bin with my settings instead of my existing ones - will they also work in my 2003 TT BAM ECU - also these settings worked in an immo off ECU I bought.  it is as if the file locations are different in your original file and associated XDF?

If this xdf does not work with your bin right now, don't change anything to your bin with this xdf. You can either look for an xdf that works, or use file compare between my original bin and your bin, and then adjust my xdf slightly (I think the addresses need to get shifted by about 2 bytes) to make it match your bin. This is how initially started building this xdf, because there was only AMK xdf available.

Check your ecu number, if it is different than 8N0 906 018 BP (note BP letters), then it is possible that this bin does not work for you even though your engine is also BAM... what is your ecu number?

Just because two ECUs are both "BAM" it doesn't mean anything. Almost every ECU with different P/N's have different map layouts (there are exceptions but they are rare).

okay - thanks just to be clear, just because my 2001 S3 AMK and 2003 TT BAM both had the same map arrangement from bin to XDF - this was just coincidence as they must have used the same part number, but you cannot put a differently organised bin file structure - I wasn't sure whether when the car "booted up" the ECU would start reading the file and know what goes where from some sort of file allocation table.

I do remember on AudiSportNet, when some people were testing putting their AMK and BAM maps onto different cheaper 1.8T ECU's from Passat's or similar to document which ECU's can or cannot be used - as long as immo defeated and original MAP available to flash over second hand ECU.  it's weird as some extra settings I have looked up and used the memory addresses found on-line and they were correct.

no matter - it was just a question.  thanks for the replies :)

Physical ECUs are often cross flashable; you can put any number of different bins on them.

The issue is the bin's P/N, not the ECU itself.

Thanks guys,
I will use your file to compare with my bin.
Good work.

More definitions added, but please note that there are launch control and NLS definitions on here that might not match your bin, so I would not use them out of the box.

MLHFM content was all over place, changed it back to working one.

Thank you for sharing! definitely a well organized definition file!