I have collected some information from FL cars and will be sitting down in order to work out "whats what" next week but the main problem is I need a car I can spend some time with for testing. My new "project car" arrives late December so not too long to wait
I have provisionally noticed a problem though... I had a little time with which to plug in to a FL car and noticed that some of the modules / firmware versions may have inherited, in part, the new way of being programmed from the new A4, A5, Q5 and Q7 cars. If this is indeed the case then VCDS is not going to be able to code most of todays changes without a modest re-write of the application.
In the meantime if anyone has the time, and wants to be added to my Christmas card list, i welcome any FL information which people would be willing to send over. Ideally whats needed is the following:
- A full Auto-scan
- Adaptation maps of control modules
- Long Coding Helper screenshots
An auto scan is self explanatory. Long Coding Helper screenshots would be screens caps of all a control modules bytes and bits, example:
*note that some s/shots include expanded drop downs
For adaptation maps:
- From the VCDS main screen select the "Applications" button
- In the Applications section select the "Controller Channel Map" button
- Configure the maps screen as follows:
- Controller Address = the alphanumeric address of the control module
- Login or Security Access Code = Leave Empty / Blank
- Function = Adaptations
- Output = CSV File
Example: Central Electronics Module
Once configured as per the above select the "Go" button. A .csv file will now be created within your Ross-Tech>VCDS>Logs folder:
Example: (reverse camera 6C)
Repeat the process referencing your auto-scan for installed modules in order to create additional maps.
Would be amazing if these could be emailed over to
alex@vagcarcoding.com I would then submit these to Ross-Tech in order to help in the development of the application.