Hi.
I know that he at least sometimes reads along here.
I have a few suggestions on how to make VCDS even more productive.
- codingLog.txt with FIN
"When I'm coding multiple, similar vehicles, the coding log isn't helpful because how am I supposed to figure out which of the four Passat 3C models I modified. Having the VIN before the control unit part number would be very helpful, especially if they all have the same control unit."
Okay, bitte gib mir den deutschen Text, den du übersetzt haben möchtest. Ich werde ihn dann ins Englische übersetzen und gegebenenfalls Datum und Uhrzeit hinzufügen.
- reconnect
"When you want to create longer logs, but the ECU has been temporarily disconnected (for example, by turning off the engine and restarting it on an MSA12), the logging process stops, and a modal dialog box appears saying "ECU not responding." A log window appears with this message, and in my opinion, it would be more user-friendly to have a reconnect option, because I want to log until I click "STOP," not until something unexpected (like the engine being turned off) happens."
OK, my idea of a 13-hour long-haul flight all the way to the Atlantic was already quite ambitious

.
- complete group withdrawal
A dump of all blocks of an ECU at once. Yes, this only makes limited sense, because by the time you get to the next block, something has already changed. But it's supposed to be just a static snapshot. Other "testers" can do something like this.
to be continued...
Okay, here's the translation:
Thank you.
martin