Attached is a stock 4D0907559E Euro S6 file.  Hope it helps.

---

ME7Check v1.12 (c) mki, 06/2004-05/2012
Checking file C:\WinOLS (559E S6 (Original) - 360170) (size=1048576)
Reading Version Strings...
-> Bootrom Version = 06.02
-> EPK = 42/1/ME7.1.1/5/8001.07//23h/Dst03o/040800//
-> Contents of ECUID data table:
   - '0261206846'         (SSECUHN)
   - '1037360170'         (SSECUSN)
   - '4D0907559E  '       (VAG part number)
   - '0002'               (VAG sw number)
   - '4.2L V8/5V      '   (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'

-> No errors found. File is OK.   *********************

Ok, so I figured out how to open it with WinOLS Demo, by creating a new project and importing the file as a binary file.
So I'll have to learn what I'm looking at here.  I think I could figure out what maps are where if I found an .xdf file for the 560AE ECU?

If I'm looking at this correct, this actually is the bin file, right?  I would just need to add the .bin extension to it when downloading with nefmoto?  And I would have to make sure I found an .xdf file for this ECU -(or use the .xdf uploaded from the one I have) -that should work, right?

- Not that i would say I want to do that right now anyway, i first want to try to understand a bit about what's going on with the maps, and determine that all my ducks are in a row before I would think of downloading.

Ah, wow, wow, wow... I'm starting to grin from ear to ear.. You guys are such a HUGE help!
I'll really have to seek you guys out if I'm ever around wherever you are and get you a beer!

-I really do appreciate all the help 

-Awesome, so it sounds like I have a complete set of files (.bin and .xdf) now, and could flash that if i wanted, and see how it runs.

But I'm going to first try to understand how the maps are generated and where/how they're located.
I think the map locations are specified in the .xdf file, which can be viewed with TunerPro, and I can use that to find those maps, by the specified address range in WinOLS.. right?  It looks like TunerPro has the ability to look at maps though, but it doesn't seem to have the power of WinOLS, plus WinOLS has what appears to have a nicer 2D and 3D viewer.  I guess you can't see the whole hex dump with TunerPro, though.  So I guess that's why WinOLS is so useful.  Is that the major reason to edit the bin's maps in WinOLS as opposed to TunerPro? -Just trying to understand the methodology of editing in which software, I guess.

Thanks again!!!

Just for a quick clarification as it seems you are confused.

Imagine the .bin file is my novel.  Say I ask you to go and look up the fueling table?  You have no idea where it is or what to look for.  In order to "understand" the file, you need to understand what is on each "page" of the novel.

For this, you need an XDF or .kp file.  XDF is for TunerPro and .kp is for WinOLS.  Without these, you have no idea what maps are stored within my novel or what they do.

Since you now have an XDF, you can open your new .bin with TUNERPRO; NOT WinOLS! With TunerPro, you can navigate through the defined "pages" in the .bin and understand/adjust.

If you can get a .kp from a friendly user here, you can open the file in OLS and adjust it because you can see the maps from your defined .kp.

Imagine that the XDF (for TunerPro) or .kp (for WinOLS) is the contents page for the .bin.

As you said in the first paragraph, these XDF's or .kp's are peculiar to the specific .bin you have.  You cannot mix and match.

Furthermore, the XML for the Flasher is stored in the install directory (C:\Program Files (x86)\Nefarious Motorsports Inc\NefMoto VW Audi ME7 ECU Flasher\Memory Layouts) or similar.  There is a thread in here with the layouts for specific ECU's.  

@adam-
Sorry I wasn't so clear on what I understand so far.. Right, the xdf is the "directory" to the maps in the bin.
I didn't know the WinOLS equivalent "directory" -the .kp file.
For now I think I feel comfortable using the TunerPro environment of .xdf and .bin files, I'll try to stick to those when I can.  

That's what I was thinking, that you can't mix and match .xdf's with .bins, but I'm still wondering if the .xdf matches the .bin, if they can be loaded into an ECM that doesn't exactly match, say, placing these 559E files in a 560AE ECM.  My gut feeling tells me this is off limits.  I have a feeling that I need to have a .xdf that matches its .bin, and both of those should match with the ECM they're going into.  Am I right on that one?  -At least for this application?

@ddillenger
Right.  It looks like Tunerpro is the editor for me, for now, being a greeney.  I can use a simple look at things for starters.
I was thinking that was the big plus with WinOLS, to find these patterns and look at all the data in one window.

Thanks for the 560AE binary. I'll start comparing maps, and looking in the tuning wiki to understand what I'm looking at.

You're right, I did forget to mention that about the intakes.. I have learned earlier that the intakes for the A6 and the S6 were different, but I thought it was more of a size difference, I did not know the S6 was only a 2 stage intake (only one flap).

I also got a little excited and didn't see that what was initially provided were 559E files, not 560AE files.  I just wasn't thinking there.  More comparison must be done.

So I think I've just overwhelmed myself with questions, and not sure what order to ask them, and which ones are appropriate.

If my thinking is right, I need to create a complete & configured 560AE.xdf and a 560AE.bin to download to my 560AE ECU.  I don't think I can just modify these 559E files and download them to the 560AE ECU.  -This is kind of repetitive of the question I posed above.

Then if that is the case, I need to use the majority of the maps that are in the 559E Euro S6 .bin, and place/overwrite those appropriate maps into the 560AE bin.
-I'll have to learn which maps are appropriate to copy over.

But I'll have to consider what you mentioned about the intake flaps: I think I'll need to leave the stock 560AE [air handling]? map in place, so the ECU knows how to appropriately use the intake configuration: 2 flaps instead of 1 and an air box flap.  -Or better yet, I might have to copy the ART A6 558S air handling map into the 560AE, as the 558S and the 560AE are just a little different in intake manifold -or throttle orifice size, if I remember correctly.

-Am I getting that part correct?  Can the intake flap situation be taken care of if I change mapping information?  -Or is it more complicated, and maybe this is in base code, and not as easy as changing map tables?  -That's my biggest confusion right now, I guess.

I suppose I need to turn now to the tuning wiki, to see what map controls the intake flaps.  I've found a bit difficult to find so far though, most things are talking about 1.8 and 2.7 boosted motors.

Another side question about the intake flap differences: do you think it is in my best interests to a: change the ECU calibration to expect two intake flaps, or b: change the physical configuration of my intake flap actuators, and use one to actuate an air box flap??

I'll start comparing, hopefully I'll start to see how maps can be copied over to another .bin, and that the flaps can be controlled properly.

Hmm, this morning I wanted to start comparing the 559E to the 560AE files, but I've realized I don't have all the information I need for that.
I have the 559E.xdf and the .bin, but for the 560AE, I only have the bin file.  Would you happen to have a 560AE.xdf definition file?
Then I could get to comparing the two.

I guess I could wait till I create my bench flash harness and pull the 560AE file (and I guess the .bin that's there too) from my 560AE ECU laying in the garage, but I guess I'm just a little ancy to start comparing.  -Just for confirmation that my thoughts are correct on this: I could take the .xdf from my 560AE ECU, and use that definition file for the 560AE bin you sent me, right?  I would think this is correct, if the .xdf is the specific definition file for that ECU, it shouldn't matter what 560AE ECU I pull it from, right?

So might you have a 560AE.xdf file already? Or should I just grab that from my own 560AE ECU?

Thanks,

Aah, I thought when you read from the ECU, it pulled the .bin and a .xdf.  My mistake.  Only the .bin then.  Got it.

So if the .xdf must be created/defined from the .bin, that must mean that one must be learned at identifying for themselves what address each map starts and ends at?
If one must create the definition file, he must first know how to look at the .bin and know what he is looking at?

If so, man, I feel quite out of my league, and must do some major learning!  -And hat's off to all you who can do this!  Hopefully I can get there myself.
I am very much in the stage of "I don't know what I don't know".  It's more humbling as i discover how deep this rabbit hole goes!

Is there a wiki or documentation on how to create a .xdf directory file, from looking at a .bin?  A described method on how to identify where maps start and end?
I guess I could ask ddillenger for his csv for the 560AE he offered up, and that would immediately help me see map locations, but I'm curious how I could find this myself, too.