- Joined
- Apr 23, 2014
- Messages
- 111
- Reaction score
- 118
- Location
- Toronto, Canada
- VCDS Serial number
- C?ID=11844
VCDS is a great piece of software. One of the nicest features is that a user who has very minimal computer skills can create their own auto-scan controller list by simply copying the provided line for the vehicle type and pasting it at the very top of the Auto-Scan text file.
I have done this (created a custom auto-scan file) for my 2004 NAR version Phaeton. I took the existing auto-scan line for the 3D vehicle, and deleted all the controllers that were never offered in North America - about half a dozen controllers. It works great, and saves a lot of time when carrying out scans.
Except...
Every time a new release of VCDS is offered, my carefully and lovingly crafted 'personalized auto-scan line of text' gets banished, and replaced with the latest version of the Ross-Tech 'worldwide' auto-scan list. This means I have to go digging in the guts of the computer, find the 'AutoScan-old' file, copy my personalized line, open the new AutoScan file, and paste it in there. I ought to be good at this by now, because I must have done this 20 times in the past 10 years.
So, I have a suggestion: Perhaps you could create a new text file called 'Autoscans Customized'. Put a paragraph of text in that file explaining that the users should put their custom autoscan lists in that file, instead of in the Ross-Tech provided AutoScan file. Then, when the application is launched, have the application look at both the Ross-Tech provided autoscan text file, and the user modified 'Autoscans Customized' text file, and load lines from both files (naturally, any user-created lines would go at the top of the list within the AutoScan page of the application, and there would be a horizontal bar separating user created lines from the default Ross-Tech lines.
Doing that would save the users the aggravation of having to go and copy their personalized autoscans into the new file every time there is a software update for VCDS released.
Thank you for your consideration of this request.
Michael
I have done this (created a custom auto-scan file) for my 2004 NAR version Phaeton. I took the existing auto-scan line for the 3D vehicle, and deleted all the controllers that were never offered in North America - about half a dozen controllers. It works great, and saves a lot of time when carrying out scans.
Except...
Every time a new release of VCDS is offered, my carefully and lovingly crafted 'personalized auto-scan line of text' gets banished, and replaced with the latest version of the Ross-Tech 'worldwide' auto-scan list. This means I have to go digging in the guts of the computer, find the 'AutoScan-old' file, copy my personalized line, open the new AutoScan file, and paste it in there. I ought to be good at this by now, because I must have done this 20 times in the past 10 years.
So, I have a suggestion: Perhaps you could create a new text file called 'Autoscans Customized'. Put a paragraph of text in that file explaining that the users should put their custom autoscan lists in that file, instead of in the Ross-Tech provided AutoScan file. Then, when the application is launched, have the application look at both the Ross-Tech provided autoscan text file, and the user modified 'Autoscans Customized' text file, and load lines from both files (naturally, any user-created lines would go at the top of the list within the AutoScan page of the application, and there would be a horizontal bar separating user created lines from the default Ross-Tech lines.
Doing that would save the users the aggravation of having to go and copy their personalized autoscans into the new file every time there is a software update for VCDS released.
Thank you for your consideration of this request.
Michael