Attached is a document of all of the variables in RAM that I have documented. These have all come from my ECU disassembly in IDA of the 8D0907551M 002 binary. I documented all of these originally for use in my data logger. They have all been tested via my data logger, but there may still be errors. I have attached the reference ECU binary as well.

Update, here are a few more variables:
wkrdy 0xF9B4 byte unsigned degrees 0.75
etazws 0x380D96 Percent byte unsigned 0.5
dzws 0x380D95 Degrees byte signed 0.75
zwopt 0x380CB6 Degrees byte signed 0.75
zwsol 0x380D97 Degrees byte signed 0.75

Wow. Just goes to show how little APR cares (cared?) about PID tuning. I always wondered why ECUx never included any of those (CRITICAL!) values.

Also, of note:

Max spec MAP is 0xff*10 = 2550 mBar
Max measured MAP is 0xffff/25.6 = 2559.9609375 mBar *BEFORE DSLOFS*

AFTER DSLOFS, max measure MAP is 2559.9609375 - 16.4065 = 2543.55... bad news

First off: byte != bit

The accuracy isn't really relevant. I was pointing out that the maximum measured value is lower than the maximum possible set-point if you use the stock DSLOFS.

Not good.

Great collection. Lots of these variables have not been prepared for logging even by Bosch.
Just two minor things I saw:
(Address=0x380984, DataType=UINT8, Scale=(1.0 / 1.25), Offset=(0.0), Name="Vehicle Speed", Units="km/h")

I think it must be Scale=(1.25) instead.

(Address=0x380F88, DataType=INT16, Scale=(1.0 / 256.0), Offset=(0.0), Name="Bank 1 Intake Camshaft Adjustment", Units="Degrees")
(Address=0x380F8A, DataType=INT16, Scale=(1.0 / 256.0), Offset=(0.0), Name="Bank 2 Intake Camshaft Adjustment", Units="Degrees")

Here Bank 1 and Bank 2 must be exchanged.

Here is what I have for Bosch translations:

http://s4wiki.com/wiki/Motronic_abbreviations

0x380bbe is tanslin.
For Boost values: pvdkds_w is at 0x382216 and pvdks_w at 0x38221A.

I was working since some time on a tool that extracts information about variables out of ME7 images.
The list of RAM cells that Spen gave me once inspired me to dig further ...
Basically the list of variables in section TKMWL of the Funktionsrahmen is processed, as far as possible.
I hope to get this finished in the near future.

Well, I'm still continuing work on the tool to discover variables and other things in ME7 images
as far as time allows. At this point I wanted to give a first impression of the results for review.

I prepared output for the M-Box as example, as this is most widely used here.
At first there is an overview which variables get logged in the measurement groups
when using KWP1285 (e.g. with VCDS):
  -> see attached file 8D0907551M.grp
Might be usefull if you are wondering which internal variables you see in VCDS logs.
This list is not fully correct when a result consists of multiple variables or bitmasks,
but for single values it is fine.

Then there is the list of variables that are detected from the image:
  -> see attached file 8D0907551M.ecu
In this file, the alias names are just at the starting point and definitely it's needed to add more of them.
The comments in the file are derived from damos/asap2 files, so they are in German ...  .
I checked the data for correctness as far as possible using all images with matching damos
files I have on my hands.

The .ecu file in the current format is used as logger input. In the meantime I had successful runs   
with my ECU and my serial interface cable, but I could not gather experience besides this setup.
Next step on this will be to check with other ECUs/cables, but I won't distribute tools to public
before having some basic functionality working also with other setups.
Would one or two be willing to act as beta tester?

Happy Easter! 

setzi, if the offer is still up, I would caan test out your tool with various ECU's