00 Software Version Management (SVM), Operating Instructions (GROUP 00, NO. 21-55)

Glossary of Terms & Acronyms used in this service bulletin

SVM Basics

SVM was developed to ensure that the hardware and software of each ECU is correct before the vehicle leaves the dealership repair facility.

A VAS 5051B, VAS 5052A, VAS 6150(A/B/C) or VAS 6160 diagnostic tool is required for reading the vehicle control module data and sending it to the SVM server (also called an "SVM communication"). The SVM communication data flow is illustrated below (Figure 1).

SVM Menu Options

The displayed items (Figure 2) may vary based on the vehicle connected:

1. Erasing DTC memory 
2. SVM - Activations 
3. SVM - Activations (FoD) 
4. SVM - Code input 
5. SVM - Erase Activations 
6. SVM - Function on Demand 
7. SVM - communication, checking 
8. SVM - Specified/actual comparison  (Only used on models up to 2017 A4 B9. Function has been moved to the "Check module configuration" under the guided function for each module).

   See the corresponding section below for an explanation of the functions.

SVM - Activations

Purpose: Used to recover existing activations or to activate new features/functions in an installed control module:

• When used to recover an existing activation, no activation code is required because the license authorization is already on the server.
• When used to activate a new function/feature, a new activation code (and possibly a PIN or customer code) may be required.

How it works: New SVM activation codes are used to add features or functions to a vehicle that were not previously there. Trailer hitch installations and navigation database updates are examples of when an activation code is used to add functions or features to a vehicle.

Instead of purchasing navigation map data, the customer must purchase an "activation packet" to unlock the map update installed in the MMI system. The activation packet consists of an activation code, activation number, and PIN. Once the activation packet information is used on a vehicle, it is permanently connected to that vehicle in the SVM database and cannot be used on any other vehicle. This is entered via SVM - Activations  .

Map update SD cards can be used on multiple vehicles however an activation document is needed for every car the software is installed on. See ETKA for the corresponding map update software to be used with the activation document. For more information regarding map updates, see TSB 2037809 91: How to update MMI MIB navigation map - potential customer concerns. 

Recovery activation is used in service if a module is replaced. When a control module is replaced that requires activation codes, these are pulled from the SVM server. This occurs during the ODIS replacement test plan which avoids the need to re-purchase the same activation documents in the future.

Additional Information: Starting with the Audi e-tron quattro and MY 2020 and newer vehicles, all activations are now stored within the Gateway. Previously, activations were split between the MMI (005F) and the Gateway (0019). This is important to understand when diagnosing concerns related to missing or inactive functions. Activated functions will change the available items displayed on the MMI screen.

SVM - Erase Activations

Purpose: To erase the activations inside the control module. This would be done in an attempt to repair activations that have become corrupt causing functionality issues in the vehicle. Some control modules have a maximum number of allowed activations that can be stored at one time. If there are incorrect or illegal activations stored they count towards the maximum number of allowed activations. In this scenario using the erase activations function can be helpful.

SVM - Function on Demand (FoD)

Purpose: Function on demand is a new feature starting with the 2019 Audi e-tron quattro. This function allows for new features to be activated or deactivated based on customer purchase or subscription.

SVM - Code input

Purpose: Code input is used to update the software in the vehicle. It is used for any updates that cannot be performed with SVM - Specified/actual comparison (or SVM - Check Module Configuration, depending on model).

How it works: When an SVM code is entered, a "Quick Test" is automatically performed. This test immediately verifies whether or not the SVM code is valid (before the update is attempted) by sending the VIN and SVM code for rough verification before other information is read out of the car and sent to SVM.

• If a hardware change is necessary, the software update will not be performed and the message "the SVM code is not valid for the vehicle" or "check hardware against ETKA" appears.
• If SVM determines that it will not be able to code and/or parameterize the control module after the update, it will indicate that the SVM code is valid for the vehicle, but the update cannot be completed. (In such cases, contact TAC for assistance).
• If no issue is found, SVM will perform the update.
• Some newer MMI and FPK software updates require the software to be downloaded from the SD creator ahead of time to complete the SVM update. For more information about the SD Creator process, see TSB 2047812: 00 SD Creator: how to set up and use the SD Creator for obtaining vehicle software updates via the MirrorServer. 
• After the update is complete, a specified/actual comparison is performed for the updated diagnostic addresses in order to calculate the new coding and parameter data¹ set for the control module and to set a new reference in the CARPORT database.

Additional Information:

• Before an SVM code input is attempted, it is important that the condition is correctly diagnosed and that only a valid code from an applicable TSB is used. Incorrect SVM codes can cause conflicts in the SVM database.
• SVM codes can be used to document manual software updates (which are performed with a CD, DVD, or SD card), such as MMI software package (ZUG) updates. An SVM code for an

  MMI update will document changes in the SVM database and provide coding and/or parameterization suggestions, but it does not perform software updates.

  SVM codes for MMI software package (ZUG) updates will only be successful if all control modules are already updated to the correct level (including those that were recently replaced).

• SVM exchange codes (XCHG) may be used to aid in the installation of new service parts when a specified/actual comparison cannot code or parameterize the replacement control module (such as with all Audi airbag control modules). XCHG codes can be found with the parts bulletin listed in ETKA, or in an applicable TSB. See Figure 3 for the location of SVM codes found in ETKA.
• It is critical that the XCHG code is run immediately  after a new control module is installed in the vehicle. If a specified/actual comparison is performed instead of the XCHG code, an invalid vehicle reference can be created in the SVM database which can prevent the XCHG code from functioning. (In such cases, contact TAC for assistance). Typically, GFF runs the XCHG code in the control module replacement routine automatically, or it will ask if an XCHG code was provided.

SVM - Specified/actual comparison

Purpose: (Note that this option is not available on model year 2015 and newer A3 vehicles and 2017 models forward - see SVM - Check module configuration,  below, for A3 information).

• By comparing the current vehicle data with the stored server data, a specified/actual comparison ensures that all control modules that are installed in the vehicle have the same part numbers, software versions, coding, and parameter data that were last recorded. If any discrepancies are found, SVM displays a notification.
• Specified/actual comparison does not suggest software updates; it only looks for the last recorded hardware/software part numbers and last recorded software versions.

How it works:

• When a specified/actual comparison is performed, the actual part numbers and actual software versions in the vehicle (the "actual" data) are sent to the servers. This "actual" data is compared to the "specified" data stored for the vehicle in the CARPORT database.
• The specified/actual comparison will document any changes that have been made to a control module's hardware part numbers and software versions if they are valid supersessions. It will also inform the user if the changes are accepted or rejected.
• When a new control module is installed, the specified/actual comparison calculates the coding and new parameter data set. If a "hardware change suggestion" is given, a conflict exists within the vehicle reference for the control module (SVM expects a different part number or software version).

Additional Information:

• SVM will not allow a new control module to be installed if it has an older version of the software, even if the control module has the same hardware/software part numbers. In this case, the new control module will need to be updated with the latest software if available on SD/SVM code card OR the correct module installed. If this is not possible contact TAC for assistance.
• If any hardware changes are suggested as a result of an SVM code being executed, a new vehicle reference will not  be set in the CARPORT database (in order to prevent any bad data from being documented). As a result, repeat coding and/or parameterization suggestions may be given with all subsequent SVM communications. It is recommended that all hardware change suggestions be resolved before  any SVM codes are entered. Once the hardware change issue is resolved, the SVM code must be run again in order to set the reference. This process is complete when a message appears explaining that no further actions are needed.

SVM - Check module configuration

Purpose: (Note that this option is only available on model year 2015 and newer A3 and 2017 B9 and newer models - see SVM - Specified/actual comparison,  above, for other vehicles). It is found when right-clicking on the module from the control module list display in GFF.

• This function ensures that a control module that is installed in the vehicle has the correct part numbers, software versions, coding, parameter data, and adaptation values by comparing the current vehicle data with the stored server data.
• Check module configuration does not suggest software updates; it only looks for the last recorded hardware/software part numbers, last recorded software versions, and performs all necessary adaptations.

How it works: The functionality is the same as that of a specified/actual comparison (see above), but there are separate communications from each control module, rather than one communication from the entire vehicle.

Additional Information:

• When a new control module is installed, this function calculates the coding, the new parameter data set, and any applicable adaptations required for the control module. (Not all control modules will support the setting of adaptations in SVM; ensure that the proper GFF replacement test plan is followed).
• If a control module is being replaced, it is necessary to perform the replacement test plan which can be found under the Control Modules tab in ODIS. This ensures all functions of the module are properly checked and activated.

Tip:  When SVM is used during the diagnosis of a customer concern it is helpful to look at the coding suggestions provided in the test plan. Based on the SVM action being performed, some modules are always recoded, adapted or parameterized even if no changes are actually made. This can be misinterpreted that a coding change was made which could lead to a misdiagnosis of a customer concern. For this reason, it is helpful to compare the actual coding changes to the suggested coding changes made at the end of the test plan. Here you will see if a change was actually made, or if it remained the same.

SVM - communication checking

Purpose: This function tests the communication of the VAS tester to the SVM server in Germany.

How it works: The VAS tester performs a quick check to see if the SVM server can be reached.

Additional Information: If an issue is found, check all connections to ensure that the tester has a sufficient internet connection. Check with IT to make sure that the tester can reach the internet. If the issue appears to be unrelated to the dealer IT infrastructure, call tester support.

¹ Parameterization (or parameter data) is data that is written into the control module by SVM that configures the software functionality for the specific vehicle or country of operation. To ensure proper function of the control module, it is critical that parameterization is executed when it is suggested by SVM. Not all control modules support parameterization by SVM. Parameter data may be referred to as "calibration data".

Service

Applies to vehicles with high-voltage components: 

To prevent charging of the high-voltage battery during the software update, the high-voltage cable is to be removed BEFORE entry of the SVM code on vehicles with high-voltage components.

Charging the high-voltage battery during a software update can damage the high-voltage components.

1. Before beginning the SVM code update, check the system for DTCs that are not related to the update. If there is a DTC in the system relating to "Checking Software Version Management" the control module is not properly configured and could be related to the concern. An example would be a module that was replaced without successfully coding and adapting the module. This could lead to customer complaints related to missing functions or incorrect vehicle behavior.

   If unrelated DTCs are found, these may need to be resolved first before proceeding. If that is not possible, write down the DTCs (to investigate later) because they may be erased during the update. It is possible that unrelated fault DTCs can prevent the execution of the SVM update.

   Tip:  Sporadic communication DTCs will be created during SVM coding or updates. These DTCs will be automatically erased when using the FLASH function in ODIS. For this reason, any needed diagnosis should be done before performing SVM actions. If using GFF, it is a best practice to ensure all DTCs created during SVM programming are cleared before exiting ODIS.

2. Check the vehicle for evidence of a tuned ECM or TCM (A tuned control module has been modified to perform outside of the normal parameters and specifications approved by Audi of America). See TSB 2028842: 01 Automatic detection of unauthorized chip tuning (TD1 warranty key)  . If evidence of tuning is found, do not proceed with any procedure that updates ECM or TCM programming until the following are completed:
   • The vehicle owner must be notified that the vehicle was found to have been tuned.
   • The vehicle owner must be notified that any damage caused by the tuning (including adverse emissions consequences) will not be covered by Audi of America warranties. If tuned control modules are updated, they may become unusable and require replacement.
   • The vehicle owner must provide written consent (see attached Control Module Tuning Form) for any requested repair (whether or not it is under warranty) that requires flashing that will automatically overwrite the tuned program.

     Tip:  Any programming update could overwrite any tuned ECM or TCM programming.

3. Confirm that the TSB being used for the update applies to the customer complaint, and perform only those operations explicitly stated in the TSB.
4. Ensure that the person operating the VAS tester has a valid GeKo user ID and password and that no more than one active tester session with this user ID is in progress.
5. Verify that all of the following requirements are met:
   • The tester is VAS 5051B, VAS 5052A, VAS 6150(A/B/C), or VAS 6160 with the latest ODIS base and brand updates installed.
   • The tester must be plugged into a 110V AC power supply at all times.
   • The tester must be plugged into the local network via a LAN Ethernet cable. (It is possible to connect via Wi-Fi with the VAS 6150 and 6160 testers, but a Wi-Fi connection is not recommended due to the possibility of signal drop-outs).
   • The VAS 5054A or 6154 transmitter must be connected  with a USB cable to the tester. The Bluetooth connection must be disabled  in the Windows system tray. If the Bluetooth connection is not disabled, Windows will default to using Bluetooth even though the cable is connected.
   • Ensure that the Windows power-saving settings are all disabled on the VAS tester (including Bluetooth power-saving). This requirement is especially important during an SVM software update in which the 110V AC power supply is interrupted. If power-saving settings are on, the VAS tester may shut down during the SVM software update. (Refer to service circular AVT-12-02 VAS Diagnostic Devices - Recommended Windows® Settings  for more information.)
     NOTE: If the Windows screensaver activates during a control module software update and the hard drive shuts down as a result of the power settings, a control module failure may result. (Refer to service circular AVT-12-02 VAS Diagnostic Devices - Recommended Windows® Settings  for more information.)