ME7Info -g ../bins/mbox.bin | grep 112
measgroup 112: 0098(tats_w              ), 00C4(dlamatr_w           ), 0099(tats2_w             ), 00C5(dlamatr2_w          )

-> Should be dlamatr_w and dlamatr2_w which you are searching for.

I'm having a trouble to import the data to the MS Excel or Open office. There are space before the values, or many after it after the import. Also some columns have "' ' " marks berfore the value.

The charts are not shown because of those spaces or marks. It is very difficult to clean those manually. Am I doing something wrong, or could I open the data differently?

Excel is 2010, Open office calc is 3.3.0. Excel opens the csv-files ok, but didn't remove the whitespaces. It seemed that the values were text, not numbers.

I changed the system settings so that the decimal value is ".", and not "," as it was. Now the excel works right, and removes the whitespaces and understands the numbers. But still the Open office doesn't work.

I would like to use Open office, but now I cant.

I'm not sure that if this problem is also with ECUxPLOT, because it doesn't show any graphs. It can open the cvs, and can select the variables, but is doesn't plot any lines.

Ok, I found the "fault" with ECUxPLOT. I had the "filter data" option on, and with it most of the logs didn't show nothing. So now I have only the Open office problem

The data you see from ME7Logger are the most accurate values you will get in this case  .
Variables fra_w, frao_w, frau_w are stored as unsigned word (16bit) in the ecu.
Damos specifies the conversion from internal to physical value for these:
PHYS = INT / 32768, this returns values in range 0.0 to 1.99997 (a factor without unit).
The conversion factor which ME7L uses is therefore 1/32768, which is just 3.05176e-005.

Now, when you log with VCDS, the ECU processes each variable and performs an internal
conversion, then delivers for each variable three bytes (a, b, c) to VCDS.
Byte c is a conversion formula number
(see here: http://nefariousmotorsports.com/forum/index.php/topic,22.msg22.html#msg22),
bytes a and b are data values used in the conversion formula.
VCDS takes a and b, then converts again using the formula and presents you the result.

In case of fra_w, frao_w, frau_w, the ecu always sets c = 20, so the formula for VCDS is:
a*(b-128)/128  [in %].
The ecu sets a=50 and b to result from a conversion of the original 16bit value.
You can see, that VCDS can compute the final percentage result with a resolution
of 50/128 = 0.390625% in a range of -50% .. +50% (b can be 0 ..255).

Be aware, when you log via KWP1285 (as VCDS does), the ecu alway processes variables
internally before delivering data and you probably loose accuracy.

I've only just started to look into using this tool. I see that

"The stock binary is sufficient (as long as you don't change variable addresses in the code, which is normally NOT done)".

I have my stock binary file, but my car has a Revo Stage II remap. What is the likelihood of me being able to implement ME7logger successfully given what is generally known about Revo code (i.e. read over OBDII disabled, extra maps, information moved around? Etc.)

Advice would be gratefully received. I thought this might have been a way of, ahem, understanding the remap better, but I'm reluctant to embark if isn't likely to work.

TTQS

Super. I've created a template and had a browse through the available variables.

Thanks.

TTQS

Looks fine up to now. I created a definition file with 127 of the choicest variables ready to try some logging but I'm falling at the first hurdle when trying to connect over USB with a genuine Ross-Tech interface set to boot in dumb mode. It fires through all the variables o.k. on the command line window but then returns the failed to connect error. Which port should I be selecting for this or do I require a VCP driver? It's a dumbass noob question I know, but any ideas...?

TTQS