00 Software Version Management (SVM), operating instructions
00 19 25 2011732/11 September 17, 2019. Supersedes Technical Service Bulletin Group 00 number 14-65 dated
July 15, 2014 for reasons listed below.
Model(s)

Year

VIN Range

Vehicle-Specific Equipment

All

2002 – 2025

All

Not Applicable

Condition
REVISION HISTORY
Revision

Date

Purpose

11

-

Revised header (Added model years)
Revised bulletin to include the latest information

10

07/15/2014

Revised entire bulletin to include ODIS information

9

02/07/2012

Revised header (Added model years)
Revised Technical Background
Revised Service (Added image)

This Technical Service Bulletin (TSB) details the general process for carrying out a Software Version
Management (SVM) software update for any TSB or Update.
Troubleshooting information is included at the end of the Service section.

Technical Background
Glossary of Terms & Acronyms used in this service bulletin
SVM:

Software Version Management.

ODIS:

Offboard Diagnostic Information System.

ECU:

Electronic Control Unit (i.e. ECM,
TCM, BCM, gateway, cluster, etc.)

ECM:

Engine Control Module.

TCM:

Transmission Control Module.

CARPORT:

The database that stores the last known
good configuration for each VIN.

XCHG:

Abbreviation for “exchange” or
replacement (i.e. SVM Code
XCHG15A005).

ASAM-MCD:

ASAM - Measurement, Calibration, and
Diagnostics.

Page 1 of 16
© 2019 Audi of America, Inc.
All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of Audi of
America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval system, or transmitted
in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior expressed written permission of the
publisher.

ETKA:

ET = Ersatzteil (Spare Parts) & KA =
Katalog (Catalog).

MMI:

Multi-Media Interface.

ASAM:

Association for Standardization of
Automation and Measuring Systems.

MIB:

Modular Infotainment System (ENG).

MOST:

Media-Oriented System Transport.

Service42:

Server hosting the SVM application.

VAS:

Volkswagen Automotive Service
Equipment.

Version42:

Engineering database hosting the ECU
data and configuration files.

ZUG:

Refers to the software package, or
train, of an ECU. “Zug” is a German
word for the train.

FoD:

Function on Demand (after-sales features
or functions that are activated over the air
or SVM).

FPK:

Free-Programmable Cluster (AKA
Virtual Cockpit).

Modularer Infotainment Baukasten (GER).

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).
Note:
 ODIS should be updated to the latest software level before beginning diagnosis or coding.
 Diagnostic head 6154 is required on all 2019 and newer vehicles.
 Starting with 2019 and newer vehicles the hood is required to be open when programming, this is due to
security architecture in the vehicle.
 Windows 10 does not support the 5054x diagnostic head.

Page 2 of 16
© 2019 Audi of America, Inc.
All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of Audi of
America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval system, or transmitted
in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior expressed written permission of the
publisher.

Figure 1. SVM communication data flow.

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

Figure 2. SVM main menu options.

Page 3 of 16
© 2019 Audi of America, Inc.
All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of Audi of
America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval system, or transmitted
in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior expressed written permission of the
publisher.

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.

Page 4 of 16
© 2019 Audi of America, Inc.
All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of Audi of
America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval system, or transmitted
in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior expressed written permission of the
publisher.

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 data1 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.

Page 5 of 16
© 2019 Audi of America, Inc.
All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of Audi of
America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval system, or transmitted
in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior expressed written permission of the
publisher.

 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.

Figure 3. Location of SVM code 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).

Page 6 of 16
© 2019 Audi of America, Inc.
All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of Audi of
America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval system, or transmitted
in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior expressed written permission of the
publisher.

 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.

Page 7 of 16
© 2019 Audi of America, Inc.
All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of Audi of
America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval system, or transmitted
in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior expressed written permission of the
publisher.

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