This is why abandonware is cancer.

The logger is still going well. I've just been ironing out a few things. I will probably limit it to 40 variables but 50 gave it no problem on the bench. The logger scans for a  large chunk of free RAM (00)  far away from data and writes the new RAM variables there. It scans for the original pointer and redirects it to the new address. I'm using the RAM in the lower regions  as the 380000 RAM takes about 2 minutes to lose its memory after powering down, making testing tedious.
Unfortunately, I still haven't managed to increase the baud rate.
The command 108663, which is apparently for 56000, is accepted by the ECU but then all communication stops. I tried sending $00,$01,$F1 $55 $70  but I just get echos back and eventually get disconnected. Its as if its waiting for some special character or something from the computer. There is nothing in the me7 FR and the there are no specifics in the MED9 FR I could find about the special baud command.The 1086 is well documented everywhere but 1086XX is an enigma.
Also tried getting into the weaker security access level  3/4  to see what it offers but after having tried adding all sorts of numbers to the seed  to make the key, and getting rejected, I gave up. A few I tried  were $40,$00011170,KLOGIN, SLOGIN. Is there a simple way of finding it in the bin file?   Or would a scan through the RAM reveal the key?

Next is the boring task of converting the numbers into values and saving them. I'm now remembering why the last program I wrote was back  in 96, with VB3....

Yeah, I change the setting straight after receiving the 5086. Mind you, the VCDS Turbo button also freezes up on these ecus. Im not sure if vcds uses the same method. BTW  Do you know if security level 3/4 opens doors to anything more than level 1/2 does?
 

I don't use any security for the logger! - so long as I dont try to change the baud rate that is, cause the108663 command for 56000 needs sec level 1/2 which the forum helped me crack.
 Without sec level  1/2 first, I get error 33. It might be an st10 issue that c166 dont have. I dont have a ME7.1.1 c166 to try so wouldnt have a clue if  all 7.1.1s need sec access or not to change baud.  Perhaps its ME7 that dont need security to change baud?

Sec level 3/4 i dont know much about, that's why I asked!
Why have 2 levels of security? What does it allow that 1/2 doesnt? It might be handy to know...

 So, atm, if I leave it at 10400, I have no need for any seed/key for the logger.
10400 might be quick enough - got to see final samples per sec after the conversion and saving of 40 variables to a file. A quick test indicates that it will be the ECU that will be the bottle neck, as I can process 35 variables and save them at about 500Hz.
 What is a regarded as a reasonable sample rate for tuning? Is 10Hz enough?

I gave up on baud rate, I just can't get it to work.
On the bright side, I changed the ecu in the Mk5 R32  car and took the first log.
I posted a snipped done at WOT. I don't know how to tune as yet, but at a glance all the numbers seem to have been converted properly?
There are too many significant figures for realistic accuracy, but will drop it to 2 decimal places next time. Hopefully it is compatible with Ecuxplot, I cant test that as I only have Win7 32 bit laptop ATM.
Can anyone see something that doesn't look right?

ecuxplot looks for certain headers to decide what format the log is.

That log doesn't have any of the things ecuxplot looks for to detect ME7Logger files, if thats what you intend to be compatible with.

It looks for ME7-Logger

It works, however the filter doesnt work possibly because you didnt log pedal pos% ?Good job.