Windows based logger, similar to ME7Logger, which won't work with ST10 ecus, and is easier to use.
Features include pausing logs with space bar, automatic increment of last filename on start and robust connection.

Developed for the VR6 R32 golf MK5 / audi A3 3.2 with the ME7.1.1/ST10 processor but might work with other ST10 ECUs.

You will need RAM locations for your ECU. These are found in A2L files. Or the hard way using IDA. I included the ones for the 022906032CE in the package. Version 1.2 has a RAM dump , useful for getting some codes from the EEPROM mirror and anything else hiding in the RAM.

If the logger crashes the ecu immediately, you just need to manually find another RAM scan range as described below. I only had a 022906032CE and 022906032KG to test and the default memory area works with those. Some audi A3s and probably R32s,  just need a different RAM scan area and will work very well.

Uses K-Line dumb cable.


Written in VB6, tested on XP through to Win10 32&64

What to do if it crashes on first log:
For some ECU versions, logger will connect just fine, but crashes the ecu when it tries setting up for the log.
This occurs because each version of the ecu is different and the logger used an area of ram which was not free, although it looked like may have been.
What you need to do is to do a ram dump of the whole ram area, 380000 to 38fe00. This takes a few minutes if you clicked on the fast timing parameters first. Use the developer section of the logger in the settings menu for the ram dump feature.
Then you look in the dump file for ram areas that look empty (all zeros in a row) and write down a few addresses to try.
Then, delete the cfg file created by the logger file so that the logger will need to search ram areas again. In the advanced menu, change the 383400 for the ram search to what you believe is a good area, and try logging.
If still no good, repeat the process with another ram area. Be sure to power down the ecu for 2 minutes each time to clear RAM, or the pointer will not be found.I can't remember if just the ignition off is enough, but if the logger no longer finds the pointer it was still getting some standby power.
Eventually the logger will be happy and the new settings saved for the future.

Edit :27 Aug 2021
-----------------
Latest version 1.2+ (source code available) and 'developer' functions, including RAM dump, which allows you to view and save memory locations of the ST10 (Similar to VAG Commander, which doesn't work on ST10). Also works in countries where decimal places use "'," instead of ".".
 

Download  and install the 1.0 version first! 1.2 is just the updated exe file. No need to download the source code if you just want to log.

Source Code
--------------------
If you have VB6 you can edit the code and add your own functions change mine etc etc.
Source code has not been beautified. It is exactly as it developed as I experimented with the ECU.
It might be useful for someone who wants to write a specific logger in  for other KLine ME7s that have a KWP2000 protocol with a slight twist.  For example, only 'slow init 'is executed to connect to the ecu, but you could add 'fast init'  code if you needed it.

Good job! Quick test shows it starting up after dll register (must be running CMD as admin,very important).

I tested this quickly on a R32 022906032CE ecu (same as op), my sw version is 6733.
No error messages on startup or anything, connects fine and starts logging, but logged values in file are all zeroes (engine running).

Created VIN.cfg file, contains [PointerAddress] 0F11CA and [VariablesNewMapAddress] 383400.

I will test compatibility mode.
My Windows is 10 Pro 21H1 build 19043.1110

Btw i have 64bit Win10.
I tested XP SP2 and SP3, still all zeroes. Tried running as admin, with and without compatibility mode, same result.
Tried connecting only ignition on and also engine running, same result.

I haven't touched the cfg file since it was first generated, ecu file is the one supplied with sw.

Edit: I tested file in your rar, same result. Tried also Win7 mode.

Very strange. The timestamp part has nothing to do with the ecu and is just a simple command:
Print #1, Format$(TimerEx - Start, "0.00")
TimerX and Start are just  real numbers. Regardless of the result, it should always have  2 decimal places when printed, yet on your computer is printed rounded up with no decimals!

Looks like all the printing of numbers isn't working, or the mathematical operations are integers instead of real numbers or both!

I will try out an up to date win 10 64 bit tomorrow on a bench ecu tomorrow and let you know.

It is indeed locale handling problem in software.
I changed system decimal separator from "," to "." and now values display normally in log file.
This still happens A LOT with US made software when used elsewhere in the world, propably vice versa also.

Edit: Latest version now works.