Customer Statement / Workshop Findings

Technical product information 2037026/30 https://erwin.audi.com/erwin/rp/elsaweb/ctr/TPLdisplayContent/src/42/1...
Copyright VW AG
Technical Service Handbook
VIN: WAUZZZ4F36N026651 Model year: 2006

Sales code: 4F20HL Model description: A6 Sal.q. TDI3.0 V6165 DPFA6
Engine code: BMK Gearbox code: HKG
Registration number: Final drive code:
Username: erwin Service advisor name:
Basic filtering of vehicle description
Brand Model year Sales model Engine code Gearbox code Final drive code
A 2006 % - --- % % %
Technical product information Transaction No.: 2037026/30
Working with the Software Version Management (SVM) Release date: 19-Dec-2018
Customer statement / workshop findings

Repair instructions for the software version management (SVM)
• The SVM code cannot be used.

• Performing the SVM code fails before, during and after the update.
• Feedback not possible.
• Functions have been lost.
Technical background
Because of the variance and complexity of the vehicle electronics it must be checked after completing the repair
whether the new hardware and software combination has been approved. This check must be carried out with
the software version management.
Production change
Continuous improvements
Measure
List of contents:
1. Current information
2. General information
3. Necessary information for contacting the SVM section.
4. Information about individual diagnosis addresses
Chapter 1 Current information:

New content
1 iš 17 28/11/2019 01:10
4. Information about individual diagnosis addresses
19 – diagnosis interface for data bus (from new A3/8V)
Activations of functions are lost after an update or control unit replacement
• Cruise control system

• Driver Alert System
• Drive Select/Charisma: CHA, ECO, ASY alternative drive system (PHEV)
Possible event entries about missing activations of functions:
• Diagnosis interface for data bus (DA19):

"U112400: data bus for multiple installations detected": active/static
• Engine electronics (DA01)
"P164700: Check coding/variants of control units in drive train": active/static
=> With the tester perform the function "restore existing functions" as described under 2.12 to reactivate the
affected function (e.g. after a control unit replacement).
Make sure to always activate control units after a replacement via the test plan "Replace control unit" to avoid
event entries.
• If possible, use the interface of the VAS 5055 or VAS 6154 for a data bus diagnostic interface update.
Chapter 2 General information:
! The attached documents will be updated if new information becomes available.
2.1 Connection variants between diagnosis interface and ODIS tester recommended for performance
reasons during an update:
Diagnosis interface WiFi USB Bluetooth
VAS 5054(A) X
VAS 5055 X
VAS 6154 X X
If available, we recommend the use of the VAS 6154 or VAS 5055 to update control units, as have very good
ESD shielding.
The WiFi connection of the VAS 6154 offers the best ESD shielding, as there is no electric connection at all
between vehicle and diagnostic tester.
2.2 Information about using the VAS 5054A via USB
2 iš 17 28/11/2019 01:10
But never connect the USB cable with a VAS 5054A already connected to the vehicle, as in this case the
connection to the tester may already have been built up via Bluetooth and still exists.
Always use a USB cable for the connection of the VAS 5054A via the USB cable in the following sequence:
1. Disconnect the VAS 5054A from the vehicle.

2. Connect the VAS 5054A with a USB cable to the ODIS tester.
3. Switch the ignition off and on.
4. Connect the diagnosis interface of the VAS 5054A with the USB cable to the vehicle.
Always check the correct connection via USB before the update as follows:
1.) Under Start => programs => Softing D‑PDU API for VCIs… click on => EDIC Configuration Manager:
2.) The message "USB – active connection“ should appear:
3 iš 17 28/11/2019 01:10
If "USB – active connection“ appears the USB connection is correctly fitted.
When the message "USB – active connection“ appears, a complete check has been carried out:
• USB connection on the VAS 5054A

• USB‑ cable
• USB connection on the ODIS tester
Without this check the connection could be built up again via Bluetooth if there is an interruption.
This saves deactivating the Bluetooth adapter.
2.3 How to avoid electrostatic discharge when updating control units
Note: The following information only applies to a cable connection between ODIS tester and diagnosis interface,
To reduce the probability of problems through electrostatic discharges (ESD) during the update the following
precautions are recommended:
Before entering an SVM code, i.e. before the start of the update:
• Wear anti-static safety shoes according to the ESD standard DIN ISO 20345 or alternatively ESD heel
straps, both are included in the workshop equipment catalogue.
• Avoid using the ODIS tester inside the vehicle.
• If necessary, connect the charger for the ODIS tester.
• Connect the charger for the vehicle battery.
Both chargers should be connected to the same circuit.
4 iš 17 28/11/2019 01:10
During the update:
• Ensure the power supply of the vehicle and the ODIS tester before starting the update and do not disconnect
the battery charger for the vehicle and the main connection for the ODIS tester during the update.
• Avoid unnecessarily touching the vehicle.
• Do not get into and out of the vehicle.
• If possible, do not open and close the doors or lids.
• Avoid switching electric drives in the direct vicinity of the workbay, such as electric doors or lifts.
2.4 Safe use of SVM code

Check in every case in the fitting instructions, the parts catalogue or respective TPIs whether the SVM code for
this vehicle and its equipment is valid.
There are no safety enquiries and no alternative solutions.
Irrespective of whether the SVM code is part of
• a service campaign,
• a modification,
• a service installation or
• an update.
After using the code the vehicle has a new specification for SVM.
• Example for misuse:

The supposed "standard SVM code" for retrofitting a tow bar is incorrectly used.
=> The wrong tow bar (PR No.) is fitted and the radiator performance is wrongly controlled – but the
necessary correction of the PR No. is not possible any more.
2.5 Important points to observe when performing the update
2.5.1 1 Update according to service campaign always before TPI update
Note: A wrong sequence can alter the data version of the vehicle in such a way that a service campaign cannot
be performed any more.
Example:
• The customer comes to the workshop with a complaint.

• An open service campaign for the vehicle is determined.
• In this case always work in the following sequence:
1. Narrow down the complaint to the affected diagnosis address.

2. Check whether the affected diagnosis address is included in the service campaign and whether the
complaint matches the described measure.
5 iš 17 28/11/2019 01:10
a. The complaint is described in the service campaign:
b. The complaint is not in the described service campaign: continue with 3.)
3. Deal with the complaint in the normal way. If the TPI asks you to update the control unit, e-g- according to a
TPI – do not (now) update according to the TPI as the service campaign has to be completed first.
4. Complete the service campaign including feedback.
=> give service campaign priority
5. Now perform the update according to the TPI found including feedback.
If the tester shows the following message after entering the SVM code:
"The entered SVM code is not valid for this vehicle or model" the TPI does not apply to the vehicle any more
because of a service campaign.
6. If the complaint persists, deal with the complaint in the normal way – check also whether another TPI applies
to this vehicle.
2.5.2 Correct sequence of performing service campaign

When performing several service campaigns always proceed in the sequence of their start date.
Perform:
• Firstly the oldest not yet implemented service campaign according to the start date
• Lastly the latest not yet implemented service campaign according to the start date
Note: A wrong sequence can alter the data version of the vehicle in such a way that a service campaign cannot
be performed any more.
Note for every service campaign that:
• it is successfully completed
• after its performance a bus silence must take place before starting the next service campaign.
If the sequence of the service measures is ignored
• an older service campaign may not start if a newer one was performed beforehand.
Reason: The vehicle is now in a condition for which an older service campaign does not apply any more.
In this case you would have to make an avoidable support enquiry.
An example for which it is assumed that no service campaigns have yet been completed.
• The service campaigns after the start date are in the sequence in the red circles.
• Please ignore the current number as the sorting is not correct.
6 iš 17 28/11/2019 01:10
Illustration
2.5.2 shows the correct sequence of the service campaigns according to the launch date
2.6 Always send support ticket.

• Please send a support ticket with all ODIS tester issues.
• More information can be found in the document SVM updating failures in chapter 5.3 Failure during update
by tester
2.7 Observe the attached document about SVM updating failures:

• Requirements for a correct update
• General information about the correct procedure for updates
• Procedures about possible failures before and during the update
2.8 Observe the attached document with the ETKA parts management:
• Parts search via chassis number – how to find the correct part for your vehicle
• Assembly group control – includes the current data version for the parts search
• Part Bulletins - important information for the repair and how to find it
• Activations and service installations depend on the PR numbers
=> examples for tow bar and navigation
2.9 Messages before start of update

ODIS tester message - "conditions not fulfilled" or "Unknown failure - programming aborted 4"
In this case at least one requirement for updating a control unit is not fulfilled. These requirements are already
checked and displayed in the current ODIS version.
The requirements differ depending on the control unit.
Even when the vehicle stops - check possible requirements are met, such as:
• Charge level (SOC) >80% / system voltage at least 12.5V

• Charger connected
• Ignition key slotted in / precisely positioned directly on the emergency reading coil
See information for DA17 in chapter 4
• Ignition on
7 iš 17 28/11/2019 01:10
• Engine off
• Selector lever in P
• Wheel revolution sensors connected
• Specific ambient conditions of engine control unit:
‒ Speed signal = 0 (may deviate e.g. if the tyres are changed during the update and the ABS control unit
recognises a rev signal)
‒ Engine speed = "0"
• …
Please complete event entries of all diagnosis addresses which may influence the fulfilment the requirements for
updating the affected diagnosis address.
e.g.:
- DA 03 ABS control unit sends speed signal = 255 km/h although vehicle is stationary.
2.10 Messages of the ODIS tester during the update

Check the attached document about SVM failures for the various messages and procedures.
Compact: If the update does not start or was unsuccessful although the TPI/campaigns applies to your
vehicle:
1. Charger connected? Battery charge level (SOC) >80%? Unnecessary consumers deactivated?
2. Does the vehicle identification number of the order really match the one of the vehicle?
3. Perform a bus silence - close all doors and covers and turn off the vehicle for at least 20 minutes.
Important: Bus silence A terminal 30 reset does NOT have the desired effect here.
4. Now turn on the ignition for at least 5 minutes to completely boot up all control units before accessing the
diagnosis again.
5. Completely restart the ODIS tester or use another ODIS tester.
6. In a such case use, if possible, diagnosis interface VAS 6154 with WiFi or VAS 5055 for best ESD shielding.
7. Start in every case a new diagnosis session so that all control units can be read again.
8. Check whether the affected control units can be reached via the diagnosis. If not, perform a terminal 30 reset
of the control unit(s) not reached for 20 minutes.
9. If after the check all affected control units can be reached, repeat the update.
10. If the repeated update attempt fails, send in every case an ODIS support ticket with chassis number, if
available the BAID and include the message "ODIS IGS Support Audi" as described in the attached
document in chapter 5.3.
2.11 Event entries after an update/control unit replacement in various control units
8 iš 17 28/11/2019 01:10
Try the following procedure:
1. Bus silence - close all doors and covers and turn off the vehicle for at least 20 minutes.
2. Check whether the event entries are now sporadic and can be deleted.
3. Delete the event entries.
4. If the event entries still cannot be deleted, try the following:
Access the Guided Functions in the ODIS program. Go to the appropriate diagnosis address e.g.: "03 brake
electronics" and continue with "Read and delete event memory". This increases your chance of success.
Observe also chapter 4 for further information about individual diagnosis addresses.
2.12 Vehicles functions have been lost (various diagnosis addresses)

After an update, control unit replacement or another repair functions are lost (e.g. cruise control, Charisma /
Drive Select, Driver Alert System or navigation does not work any more)
• Try to restore the functions with the ODIS tester: "special functions" => "SVM activations" => "restore
existing activations“
9 iš 17 28/11/2019 01:10
• Please note that service installations not performed by Audi AG but by a manual coding or service installation
and therefore not recorded in the Audi systems can get lost after
‒ an update via TPI

‒ an update via a service campaign,
‒ a required/actual comparison or a
‒ configuration check of an individual control unit
. We cannot provide support for questions about these manual service installations and coding as they
are neither recorded nor correctly activated. To restore the coding of the control units after a workshop
visit can only again be performed manually and independently.
‒ Observe also chapter 4 for further information about individual diagnosis addresses.
2.13 Activate control units always via the test "Replace control units"
• For the control unit replacement use the Guided Fault Finding and there always the test "Replace control
unit".
• Here the correct test plan is selected for this control unit in this vehicle.
• You are also asked whether you have an XCHG code.
‒ - Note the Parts Bulletin in the parts catalogue if an XCHG code is necessary.
‒ - If e.g. a 1:1 change is involved with the Audi/VW part number and the hardware part number being
identical with the faulty part according to the diagnosis protocol, a XCHG code is not needed in the test
plan for replacing the control unit.
‒ - If you are unsure, try the start-up by entering the XCHG code. If this does not work, perform the replace
control unit test plan again WITHOUT entering the XCHG code.
10 iš 17 28/11/2019 01:10
• Never activate a control unit via a target/actual comparison.
‒ Here the control unit may be included in the reference of the vehicle, but it would not be activated
(including no adaptation, coding and parametrisation).
‒ Once the control unit is in the reference, the XCHG code may not work any more.
‒ In a such case you have to submit an avoidable SVM enquiry.
Chapter 3 Necessary information for the first contact with the SVM Section:
The current diagnosis protocol has been sent online via the guided fault finding.
Describe in detail the checks you made and their results and whether you have followed this TPI. If the update
fails, before submitting an enquiry send an ODIS support ticket
(illustration in the attachment under: "SVM_Flashabbrüche" chapter 5.3).
Write the following data on the ODIS ticket:
• Chassis number
• The related BAID - if you report with the DISS system.
• "ODIS IGS Support AUDI"
This information is required for dealing with the enquiries.

• Campaign instructions cannot be opened?
=> Please contact verbraucherschutz@audi.de
• Can control unit be accessed via diagnosis?
• Have the fuses of the affected control unit been checked?
• In case of replacement: Is the correct control unit fitted according to diagnosis log and parts catalogue?
• Charger connected?
• Battery charge level (SOC) >80%?
• Unnecessary consumers deactivated?
• Is the diagnosis interface connected with the tester via a USB cable or WiFi?
=> observe the Current information 2.1.
• Bus silence performed for >20 minutes?
• Terminal 30 reset performed for >20 minutes?
• Have you checked the information about the individual diagnosis addresses in chapter 4?
If you have more information for us or have noticed any irregularities, add them.
• …
Chapter 4 Information about individual diagnosis addresses

All diagnosis addresses:
• Service campaign instructions cannot be opened.
11 iš 17 28/11/2019 01:10
=> Please contact verbraucherschutz@audi.de

• Make sure to always activate control units after a replacement via the test plan "Replace control unit" to avoid
event entries.
01 - engine control unit:

• If the event entry "check coding/variants of control units in drive train" is active, the cruise control function is
not (no longer) available in the diagnosis interface for data bus => With the tester perform the function
"restore existing functions" as described in chapter 2.12 to reactivate the affected function (e.g. after a control
unit replacement).
• Make sure to always activate control units after a replacement via the test plan "Replace control unit" to avoid
event entries.
• 8R/Q5 and older vehicles
Despite performing the test plan "Replace control unit" the engine control unit cannot be coded.
‒ Perform the test "Adapt immobiliser".

‒ Then perform a required/actual comparison and reassess the situation.
02 - gearbox control unit:

• Note that when performing an update the selector lever always has to be in position P – otherwise you get
the error message "programming aborted 4".
If you get the message "programming aborted 4" despite the correct procedure, another requirement for
updating the control unit is not fulfilled - see the programming conditions under 2.9 Messages before start of
update.
03 - brake electronics:
• If the control unit cannot be reached after a failed update or the update cannot be repeated, perform a
terminal 30 reset for 20 minutes. Repeat the update with another tester in a new diagnosis session.
Reassess the situation.
• After an update diagnosis address 03 includes one of the following event entries that cannot be deleted.
‒ "Vehicle identification number not saved on incompatible".

‒ Check coding/variants of control units in drive train.
‒ Adaptive Cruise Control (ACC) is lost.
To delete the above event entries and to restore the lost function with the ODIS tester, perform the test
plan "Replace control unit".
The control unit must not be replaced here.
• If other event entries after the update cannot be deleted, proceed as described under 2.11.
05 - convenience control unit:

• See diagnosis address 46.
09 - onboard supply control unit:

• Only for A4/8W/F5, Q5/FY and Q7/4M
Message "data string invalid"
Check whether TPI 2046098 applies
15 - airbag:
12 iš 17 28/11/2019 01:10
• If available
‒ always first use the SVM code (XCHG…) according to the Parts Bulletin) and
‒ only then activate the component protection.
17 - instrument cluster:
• When working with the SVM on the instrument cluster (update/replacement) the engine always has to be
switched off.
• Only for A4/8W, A5/8W, Q5/FY, A3/8V and TT/FV with Keyless Access locking and starting system:
The key must be held over the full surface of the emergency reading coil during the complete update. Attach
the key in the hollow (red) of the emergency reading coil e.g. with residue-free removable adhesive tape. In
case of abortions or messages before and during the update check whether the key is fully on the
emergency reader coil. With the TT/FV the steering wheel may have to be moved out.
Illustration 17.1 emergency reading coil A3/8V Illustration 17.2 emergency reading coil
TT/FV
Illustration 17.3 emergency reading coil A4/8W A5/8W Illustration 17.4 emergency reading coil
Q5/FY
=> Place the key as centrally/over full surface as possible on the symbol.
The steering wheel may have to be moved out
• Only for A4/8W, A5/8W, Q5/FY, A3/8V, TT/FV, A6/4G and A7/4G:
Fault code 142
13 iš 17 28/11/2019 01:10
If the fault code 142 is shown in the instrument cluster, the key could not be read by the emergency reading
coil. Check the correct fit of the key on the emergency reading coil and move out the steering wheel a little as
described so that the key rests fully on the coil. Manually select "Try again" and perform the download to the
end.
As the connection to the ODIS tester has been disrupted because of fault 142, the SVM code has to be selected
again, so that feedback can be provided and adaptations, parametrisation and coding carried out.
Message: "No updating software available"
If the message "no updating software available" is displayed when performing the update after entering the
SVM code in the ODIS tester, make sure that the correct SD card is properly inserted in the left SD card slot.
If this is the case, start the download manually via the red menu.
Important: After the successful MMI update the update must be started again via the SVM code for the
feedback, adaptation, parametrisation and coding of the control units.
Failed update: Control unit cannot be accessed or has restricted functions
‒ The control unit does not respond after an update failure, works incorrectly or the update cannot be
repeated:
After an update failure the instrument cluster rejects further enquiries for an update until it had a longer
bus silence. Please perform a bus silence of at least 20 minutes while the vehicle is locked. Please
restart the ODIS tester or use another ODIS tester. In every case start a new diagnosis session and if
possible use VAS 6154 with WiFi or VAS 5055 to avoid another update failure. Repeat the update and
reassess the situation.
‒ After the update there are event entries that cannot be deleted:
Reset terminal 30 for about 20 minutes. Reassess the situation.
18 - auxiliary heater:
14 iš 17 28/11/2019 01:10
• The following requirements must be fulfilled for performing an update:
‒ Speed signal = 0
‒ The auxiliary heater must be switched off
19 – diagnosis interface for data bus (from new A3/8V))

Activations of functions are lost after an update or control unit replacement
• Cruise control system

• Driver Alert System
• Drive Select/Charisma: CHA, ECO, ASY alternative drive system (PHEV)
Possible event entries about missing activations of functions:
• Diagnosis interface for data bus (DA19):

"U112400: data bus for multiple installations detected": active/static
• Engine electronics (DA01)
"P164700: Check coding/variants of control units in drive train": active/static
=> With the tester perform the function "restore existing functions" as described under 2.12 to reactivate the
affected function (e.g. after a control unit replacement).
Make sure to always activate control units after a replacement via the test plan "Replace control unit" to avoid
event entries.
• If possible, use the interface of the VAS 5055 or VAS 6154 for a data bus diagnostic interface update.
44 - power steering:
• Make sure that the steering rack wiring is connected.
• Before starting the power steering the control module (steering angle sensor) must be programmed and
calibrated.
• When updating or starting the diagnosis address 01 must deliver the following values in the specific ambient
conditions:
- engine speed: 0.0 rpm
- vehicle speed: 0 km/h or 0 mph
- The wheel revolution sensors must be slotted in.
• When updating/starting the control unit there must not be any event entries in diagnosis address 03.
Especially
- front left/right speed sensor
Further information under 2.9 Conditions not fulfilled
46 - convenience control unit:

• During the complete update the hazard warning lights always must always be on to keep the data buses
going.
Without hazard warning lamps the update may be aborted and not restarted.
• In many cases you can also wake up the vehicle after an update failure with the hazard warning lamps to
achieve another update attempt for control unit DA05/DA46.
15 iš 17 28/11/2019 01:10
If despite switched-on hazard warning lamps the update is not possible, proceed as follows:
a. Do a terminal 30 reset on the convenience control unit DA05/DA46 for over 20 minutes.
b. Then activate the vehicle by switching the hazard warning lamps on and off every 2 seconds or less.
While switching every 2 seconds try to access a new diagnosis session and perform the update again
with another ODIS tester or after restarting the current tester.
5F - information electronics 1:
• After the replacement perform "Replace control unit for information electronics"
• After replacing the infotainment control unit the following message appears on the diagnostic tester:
"Hardware to be checked has been recognised". Check whether TPI 2038973 "According to SVM new
infotainment control unit does not match vehicle" applies.
• MIB1+MIB2 only apply to: Q7/4M, A3/8V, A4/8W, A6/4G+A7/4G from 22/2014, TT/FV
After the replacement the control unit cannot be started.
a. Check whether there are other MOST participants such as DA 0E, 47, 57, etc. in the vehicle according to
the equipment, but are currently not reachable via the diagnosis.
If this is the case, the MOST ring on the new information electronics 1 has been deactivated by the pre-
set code (light off). But a start-up is only possible if all MOST participants can be reached.
b. In ODIS select the control unit self-diagnosis of address 5F, select coding and in byte 19 change the bit
for MOST to on.
c. Then establish a bus silence in the MMI and then restart it.
d. Perform the test "Replace control unit" again.
• After the replacement of the control unit the functions and activations cannot be restored.
• MIB1+MIB2 only apply to: Q7/4M, A3/8V, A4/8W, A6/4G+A7/4G from 22/2014, TT/FV You get the
message "activation_not_ok_wrong_creation_date" in the ODIS tester.
Proceed as follows:
‒ Adapt component protection

‒ Perform the test plan "Delete SVM activations for all proposed diagnosis addresses
(e.g. diagnosis addresses 13, 19, 5F)
‒ Perform the test plan "Restore SVW activations"
• The specified SVM code does not achieve anything for the vehicle.
If according to the ODIS tester the SVM code is not valid for this vehicle although you are sure that the code
should be valid, (e.g. open service campaign), check whether all control units of the MMI can be reached
with the Guided Fault Finding.
Possibly missing diagnosis addresses (depending on equipment): 5F, 0E, 47, 56, 57, 7F
The update can only be started if all control units can be reached.
• Only for A3/8V with PR No. 7UF or 7UG
The activated navigation function is lost after a map update.
Perform with the tester the test plans
a. "Delete SVM activations" for diagnosis address 5F and

b. "Restore existing activations" as described under 2.12 to reactivate the activation of the navigation.
16 iš 17 28/11/2019 01:10
• B200087 control unit software incompatible, active/static

After an update the following event entry is logged: B200087 control unit software incompatible, active/static
In this case not all modules of the infotainment control unit 1 were updated. If this is the case, start the
download manually via the red menu. Make sure that in the update summary all modules are confirmed with
OK or N/A.
A module must not be confirmed with not OK. If a module was confirmed with not OK, repeat the download
after a bus silence of at least 20 minutes or a terminal 30 reset of control unit for information electronics 1 of
20 minutes.
74 - running gear control unit:

• Only applies to A4/8W/F5, Q5/FY, Q7/4M
During the configuration of the running gear control unit (DA74) or of the whole vehicle a valid result
"ERP0460E" is shown.
As a result, the running gear control unit (address 74, J775) cannot be automatically parameterised. The
identifier F1B1 may be shown as incomplete or invalid in the Guided Fault Finding.
• Only applies to A4/8W/F5, Q5/FY, Q7/4M
The warning lamp for the controlled suspension comes on in the instrument cluster.
7F - information electronics 2:
• See diagnosis address 5F
8C - battery control unit:

• The control unit does not respond when starting the diagnosis or after the update failure.
‒ Perform a terminal 30 reset of >20 minutes and check whether the control unit responds again via
diagnosis.
=> repeat the update.
C6 - High voltage battery charger:

• The control unit does not respond when starting the diagnosis or after the update failure.
‒ Perform a terminal 30 reset of >20 minutes and check whether the control unit responds again via
diagnosis.
=> repeat the update.
• Only for Q7-e-tron Q7/4M
Service campaign 93C2 consists of two SVM codes:
Following SVM code 93C2B162 it is also necessary to perform SVM code 93C2C162 to parameterise the
control unit C6 - during the update you will be asked for a second code.
• Only for A3 e-tron A3/8V
Service campaign 24CE consists of two SVM codes:
Following SVM code 24CEB120 it is also necessary to perform SVM code 24CEC120 to parameterise the
control unit C6 - during the update you will be asked for a second code.
17 iš 17 28/11/2019 01:10

Customer Statement / Workshop Findings

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Customer Statement / Workshop Findings

Uploaded by

Copyright:

Available Formats

Technical product information 2037026/30 https://erwin.audi.com/erwin/rp/elsaweb/ctr/TPLdisplayContent/src/42/1...

Technical Service Handbook

VIN: WAUZZZ4F36N026651 Model year: 2006

Basic filtering of vehicle description

Technical product information Transaction No.: 2037026/30

Customer statement / workshop findings

• The SVM code cannot be used.

Chapter 1 Current information:

4. Information about individual diagnosis addresses

19 – diagnosis interface for data bus (from new A3/8V)

Activations of functions are lost after an update or control unit replacement

• Cruise control system

Possible event entries about missing activations of functions:

• Diagnosis interface for data bus (DA19):

Chapter 2 General information:

! The attached documents will be updated if new information becomes available.

Diagnosis interface WiFi USB Bluetooth

2.2 Information about using the VAS 5054A via USB

1. Disconnect the VAS 5054A from the vehicle.

2.) The message "USB – active connection“ should appear:

If "USB – active connection“ appears the USB connection is correctly fitted.

• USB connection on the VAS 5054A

This saves deactivating the Bluetooth adapter.

2.3 How to avoid electrostatic discharge when updating control units

Both chargers should be connected to the same circuit.

During the update:

2.4 Safe use of SVM code

There are no safety enquiries and no alternative solutions.

Irrespective of whether the SVM code is part of

• Example for misuse:

2.5 Important points to observe when performing the update

2.5.1 1 Update according to service campaign always before TPI update

• The customer comes to the workshop with a complaint.

1. Narrow down the complaint to the affected diagnosis address.

a. The complaint is described in the service campaign:

2.5.2 Correct sequence of performing service campaign

Note for every service campaign that:

If the sequence of the service measures is ignored

2.6 Always send support ticket.

2.7 Observe the attached document about SVM updating failures:

2.9 Messages before start of update

The requirements differ depending on the control unit.

• Charge level (SOC) >80% / system voltage at least 12.5V

2.10 Messages of the ODIS tester during the update

Try the following procedure:

2.12 Vehicles functions have been lost (various diagnosis addresses)

‒ an update via TPI

• Never activate a control unit via a target/actual comparison.

(illustration in the attachment under: "SVM_Flashabbrüche" chapter 5.3).

Write the following data on the ODIS ticket:

This information is required for dealing with the enquiries.

Chapter 4 Information about individual diagnosis addresses

• Service campaign instructions cannot be opened.

=> Please contact verbraucherschutz@audi.de

01 - engine control unit:

‒ Perform the test "Adapt immobiliser".

02 - gearbox control unit:

‒ "Vehicle identification number not saved on incompatible".

05 - convenience control unit:

09 - onboard supply control unit:

• The following requirements must be fulfilled for performing an update:

19 – diagnosis interface for data bus (from new A3/8V))

• Cruise control system