SB-10045462-5619

Technical Service Bulletin
94 Adaptive light: Headlight range control warning displayed in instrument cluster - DTC 00003 Control
Unit Faulty
94 12 83 2024877/4 July 9, 2012. Supersedes Technical Service Bulletin Group 94 number 12 – 82 dated June
26, 2012 for reasons listed below.
Model(s)

Year

A8

2008 – 2010

A6

2008 – 2011

Audi Q7

2008 – 2013

VIN Range

Vehicle-Specific Equipment

Not Applicable

Adaptive light

Condition
REVISION HISTORY
Revision

Date

Purpose

4

-

Revised header data (Modified title)

3

6/26/2012

Revised header data (Added 2013 Audi Q7)

2

4/27/2012

Revised header data
Revised Service (SVM code updates)

1

12/2/2010

Original publication

• Warning light for dynamic headlight range control is
displayed in the instrument cluster.

Figure 1. The dynamic headlight range control warning
light.
• DTC 00003 / 14 (Control unit faulty) is registered in the dynamic headlight range control unit, address word 55.
• Both headlights function normally.
• Vehicles equipped with adaptive (cornering) lighting.

Technical Background
Software issues in the dynamic headlight range control module.
© 2012 Audi of America, Inc.

Page 1 of 3 plus attachment

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.

Technical Service Bulletin
Production Solution
New software version 0010 in the dynamic headlight range control module addresses this condition. If the
headlight range control module has a software version lower than 0010 installed then use the SVM code listed
below to update the module.
Some control units will already have software version 0010 installed but still exhibits the conditions mentioned
above. When this occurs the software will need to be updated again using a separate SVM code. This allows the
corrupt software to be overwritten with the corrected software, even though the software version does not change
after the update.
Please note there are two different SVM codes listed below. Only one will need to be executed. There is no need
to execute both.

Service
1. Follow all instructions in the attached TSB 2011732 00 Software Version Management (SVM), operating
instructions.
2. Update the dynamic headlight range control unit (address word 55) using the SVM action code as listed in the
table below if necessary.

Model

Old Software Part
Number

Old
Software
Version

New Software
Part Number

New Software
Version
(or higher)

A8, A6, Audi Q7

4L0 907 357 B

10

4L0 907 357 B

0010

A8, Audi Q7

4L0 907 357 A

*

4L0 907 357 B

0010

4L0 907 357

*

4L0 907 357 B

0010

A8, A6, Audi Q7

© 2012 Audi of America, Inc.

SVM Action Code

55A007
55A001

Page 2 of 3 plus attachment

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.

Technical Service Bulletin
Warranty
Claim Type:

Use applicable claim type. If vehicle is outside any warranty, this Technical Service Bulletin
is informational only.

Service Number:

9498

Damage Code:

0039

Labor Operations:

Charge battery

2706 8950

10 TU

Diagnostic Time:

GFF

0150 0000

Time stated on
diagnostic
protocol (Max
60 TU)

Road test prior to service procedure

No allowance

0 TU

Road test after service procedure

No allowance

0 TU

Technical diagnosis at dealer’s discretion
(Refer to Section 2.2.1.2 and Audi Warranty Online for DADP allowance details)
Canadian Dealers: Please follow CAWP-09-02 for diagnosis process.
Claim Comment:

As per TSB # 2024877/4

All warranty claims submitted for payment must be in accordance with the Audi Warranty Policies and Procedures
Manual. Claims are subject to review or audit by Audi Warranty.

Additional Information
The following Technical Service Bulletin will be necessary to complete this procedure:
• TSB 2011732 00 Software Version Management (SVM), operating instructions.
All part and service references provided in this TSB are subject to change and/or removal. Always check with your
Parts Dept. and service manuals for the latest information.

© 2012 Audi of America, Inc.

Page 3 of 3 plus attachment

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.

Technical Service Bulletin
00 Software Version Management (SVM), operating instructions
00 12 32 2011732/9 February 7, 2012. Supersedes Technical Service Bulletin Group 00 number 10 – 02 dated
March 24, 2010 for reasons listed below.
Model(s)

Year

VIN Range

Vehicle-Specific Equipment

All Audi

2002 on

Not Applicable

Not Applicable

Condition
REVISION HISTORY
Revision

Date

Purpose

9

-

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

8

3/24/2010

Revised Technical Background
Revised Service (Added Response Codes section)

7

5/13/2009

Revised Service (Step 6)

6

12/15/2008

Revised Service (Step 3 – added information concerning use of wireless
VAS 5054A transmitter head)

5

11/17/2008

Revised Title to include Repair Group

4

10/21/2008

Revised Service (Step 3 – added information concerning Windows power
savings settings)

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 in the Additional Information section.
Please refer to the upcoming TSBs covering detailed aspects of SVM. They will be listed under group “99”.

Technical Background
SVM was developed with the main goal of ensuring each Audi vehicle has the correct electronic control units with
the correct software versions installed when it leaves the dealership repair facility.

© 2012 Audi of America, Inc.

Page 1 of 10

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.

Technical Service Bulletin
SVM is a feature of GFF that has a subset of
functions or components as seen in Figure 1. These
functions are explained below. A VAS 5051B, VAS
5052A, or VAS 6150(A/B/C) diagnostic tool is
required to read out the vehicle control unit data and
send it to the SVM server (also called an “SVM
communication”).

Figure 1. Subset of SVM functions

1. SVM – Specified/actual comparison
Goal: This function is designed to ensure all electronic control units installed in the vehicle have the correct
part numbers, software versions, coding and parameterization. It will not suggest a control unit software
update. During this SVM communication, the part numbers and software versions of the actual control units
installed in the vehicle will be sent to the SVM servers. This “actual” data is then compared to the “specified”
data in the SVM database for a particular vehicle. The specified data stored on the SVM servers is also
referred to as the vehicle “reference”.
What an SVM Spec/Actual can do:
• Document any changes to an electronic control unit’s hardware/software part numbers, hardware/software
versions, and provide feedback to the user if these changes are accepted or rejected.
1

• When new parts are installed, it will also calculate coding changes or parameterization changes. If a
“hardware replacement suggestion” is given, then a conflict exists with the vehicle reference for that
control unit (i.e. SVM expects a different part number or software version for the control unit in question).
• As a rule, SVM will not allow a control unit with the same part number as the original part to be installed if
the new part contains an older software revision. In this situation, SVM will return a hardware change
2
suggestion . In these special cases a new vehicle reference must be manually set by an Audi Product
Support Engineer. Please contact the Technical Assistance Center Helpline if you suspect this is the
case.
2. SVM - Direct Input: SVM code for problem related update
Goal: This function performs any additional functions which cannot be performed with an SVM Spec/Actual.
Those functions include the following.
What an SVM code can do:
3

• Update the software in a flash-capable control unit if the SVM code is valid for the vehicle.
• After the software update is completed, an additional SVM Specified/Actual comparison will be performed
to calculate a new coding and/or parameterization and to document all control unit changes as a new
reference in the SVM database.
• SVM Codes should not be used to update a control unit without knowing the solution(s) the software
update provides. To update control unit software, the technician must first diagnose the condition in the
vehicle and find an applicable TSB that provides a valid SVM Code. Randomly trying out multiple SVM
Codes wastes time and can sometimes cause conflicts in the SVM database.
• SVM codes can also be used to document manual software updates to the vehicle’s systems, as in the
case with MMI Software Package (ZUG) updates. These types of updates are performed manually with a
CD/DVD/SDcard. An SVM code for an MMI update documents the changes in the SVM database and
provides coding and/or parameterization suggestions. It does not perform any software updates.
© 2012 Audi of America, Inc.

Page 2 of 10

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.

Technical Service Bulletin
SVM codes for MMI Software Package (ZUG) updates will only complete successfully if every control unit is
updated to the correct software level. This is especially important when a control unit fails/dies during the
manual software update process and is then later replaced, but not updated after it is installed. Since the new
replacement control unit was not updated the SVM code will fail. The replaced control unit must be updated
prior to running the SVM code.
• SVM Exchange (XCHG) Codes can also be used to aid in the installation of new service parts when an
SVM spec/actual cannot code or parameterize the replacement control unit, as with all Audi airbag control
units.
It is critical to note SVM XCHG codes must be run immediately after a new control unit is installed in the