Feature request

Hello

I'm sorry if this is not the place for this kind of post but could not find a better place.


I would like to request a feature for future versions.

I would be a big help if there was a way to log everything you do in VCDS.
So all buttons pressed and codes altered. So it is easier to go back and find potential user errors and easily remember what was altered.

Best regards
Alexander

Take a look in the \Ross-Tech\VCDS\Debug folder on the PC on which you run VCDS...

That is Perfect!

Thank you so much.

I've found the Debug folder saves any chances you make in long coding to a CodingLog.txt.

e.g.

2010 Golf seat belt warning disabled

Address 17:5K6 920 970 E recoded (Long Coding) from 470B00 to 470900 (01357/011/00200) Monday,25,April,2011,15:25:41:21184
Address 17:5K6 920 970 E recoded (ADP-Staging) from not active to active Sunday,14,August,2011,16:11:26:21184

2008 Golf GTI Edition 30 Cruise Control disabled and enabled

Address 01:1K0 907 115 T recoded (Long Coding) from 0403000318070160 to 0403000318070060 (04096/557/00059) Sunday,24,August,2014,12:40:36:21184
Address 01:1K0 907 115 T recoded (Long Coding) from 0403000318070060 to 0403000318070160 (04096/557/00059) Sunday,24,August,2014,12:41:01:21184
Address 03:3C0 614 109 P recoded (Short coding) from 0001298 to 0001298 (12345/123/00001) Wednesday,23,September,2015,14:32:06:21184

Keithuk said:

I've found the Debug folder saves any chances you make in long coding to a CodingLog.txt

Click to expand...

In the Debug folder on my PC there are .txt and .csv versions of the CodingLog and AdpLog files.

It looks like the .txt files are from older versions of VCDS, and the .csv files are from later versions - or is there a different explanation?