dude.

you can use ME7Sum to validate checksums as well.  If you don't pass in a second file path parameter to the command line it just checks.  I have tunerpro setup like this:

ctrl + alt + v = "validate" with me7sum
ctrl + alt + c = "correct" with me7sum
ctrl + alt + x = "check" with me7check

After I've saved my bin, I'll do a validate and check just for the hell of it just to make sure there are checksum errors.  Then I will correct, followed by a validate and check to verify all is well with the file.

------------

As for which variables to log, use the attached ME7Logger config file to start.  We can add more variables if needed. I really want to see those logs!!!

Driver's Requested Relative torque (mrfa_w) closely resembles accelerator pedal position.  You can "go read the FR", sorry had to, to understand the relationship.  I'm pretty sure that mrfa is the lamfa % axis.

You should post a screenshot of your LAMFA table now that you've mentioned you started at 50%.  If you are enriching the mixture at 50% and your lowest axis value is 50%, that means that from 0% to 50% it will interpolate 1 to .85 or whatever your value is at 50%. 

Example - 25% mrfa would (could) give you .925 lambda.  You don't want to be doing that.

For LAMFA, I will typically modify the axis as 50, 60, 70, 80, 90, 100

I will put what I want my request to be at WOT in the 90 and 100 columns.  I will then take those values and paste them into the 80, 70 and 60 columns and multiply the values by 1.05, 1.10, 1.20 respectively.  This gives a smooth transition to my desired WOT fueling request, should the driver request less than 90%.  It won't start enriching until after 50% because my 50% row is all ones, and my 60% is not much less than one.

Tunerpro's visual graph is really nice too.  I'll use it once I get my main points figured out to make smooth transitions between those points.

Attached is an XDF for software number 37369307 which includes most of the definitions in ddillenger's 2.7T Stage 1 XDF with the exception of the emissions related definitions (still trying to figure these out..). I will keep track of updates to this file as to not derail the purpose of the thread.

Update:
The attached XDF is only compatible with a bin that has a 37369307 software version, the stock bin is posted here.  The software version can be verified in ME7Check, it is in the output and labeled SSECUSN.

I believe you are using the bin file that is in the original post.  That file has a different software version changing the locations of many if not all maps.  With the matching software number file the maps are correct, see attachment. 

I updated my previous post to clarify which 518AK bin that XDF is compatible with.

If possible, I'd like to include all of the applicable files/xdfs in the OP to avoid confusion and clutter. That way the most updated xdfs and correct bin files are all in one place, paired for convenience. What do you think? Moderators?

I'll go back and change the names of the original files I posted, with the proper extensions.

This is what I see from the logs.

Boost starts at 15psi @ 2500rpm and tapers to around 9psi @ 6,000rpm

Air Fuel Ratio Desired is following Drivers Requested Target AFR, but is not following what we have in our LAMFA table.  @2.5k lambda request is .92 and tapers to .86 @5,360, at which point it looks like BTS fueling kicks in. We are not logging the BTS fueling lambda request, so this is an assumption.

Timing looks good for now.  No timing pull.  Keep it safe until everything else is sorted out.

We need to figure out why our lamfa_w request is lean and not following LAMFA.  Once the we get the correct mixture, it will hopefully keep us out of BTS fueling up high (at which point we are seeing fuel injector duty cycles > 100% currently)

You know... We should also get some logs of the stock file for comparison.