TSB_2079652_2 Service Bulletin/Repair Instructions

ZN Connection offline
Technical Service Bulletin Transaction No.: 2079652/2

91 Emergency call LED in roof module not lit up in green Release date: Dec 11, 2025

Condition

Model{s) Year(s) VIN Range Vehicle Specific Equipment

All Audi vehicles | 2016 — 2026 All e-call
REVISION HISTORY
Revision | Date Purpose
2 - Revised Condition (Added model table)

Revised Warranty (Updated warranty table)
Revised Service (Updated verbiage)
1 10/14/2025 | Initial publication
Customer states:
The emergency call LED in the roof module is not lit up in green.
Technical Background

Not applicable.
Production Solution

Not applicable.
Service
Move the vehicle into the open air and ensure that it has adequate GPS and mobile phone reception. Switch on the

ignition and wait at least 30 seconds.
Then evaluate the emergency call LED in the roof module as follows:
eCall (emergency call) status
Fall LED Feedback Status

1 eCall ongoin

eCall disabled
2
3 Predelivery state

4 Error
5 eCall not available
6 ecall available

Timing }0,55/0,55)0,55/0,55)0,55)0,55/0,55/0,55/0,55/0,55/0,55/0,5570,55/0,55/0,55)/0,5s5

Scenario 1 (eCall ongoing): eCall active and an emergency call is currently being made.
Scenario 2 (eCall disabled): eCall is deactivated. Perform the general test steps. If the LED is still flashing in red,

contact Product Support via reporting obligation 2063936 (see below).
Scenario 3 (Predelivery state): Vehicle is in transport mode. The pre-delivery inspection has not yet been

performed. If the LED is still flashing in red after the “Establish readiness for sending and receiving information”

routine has been performed successfully, carry out the general test steps. If the LED is still flashing red, contact

TAC.
Scenario 4 (Error): eCall is not available. Control unit communication interrupted, or LED is not activated. There is

a relevant event memory entry in the data bus diagnostic interface J533 or in the emergency call module J949.

Please work through this entry with Guided Fault Finding.
Scenario 5 (eCall not available): eCall is not available. Control unit communication interrupted, or LED is not

activated. There is a relevant event memory entry in the data bus diagnostic interface J533 or in the emergency call

module J949. Please work through this entry with Guided Fault Finding.
Scenario 6 (eCall available): eCall is available. Target status.
If the eCall LED still does not light up in green, proceed as follows:
Please check whether there is an IT error (disturbance) under the “Breaking News” tab in the service portlet.
General test steps
* If there is an IT error (disturbance), please check the Customer Information Portal (CIP) to determine if there is

an outage. If multiple vehicles are affected and there is no IT error (disturbance), contact Audi Digital Business

Support (DBS) and state how many vehicles are affected.
* — If there is no IT error (disturbance), check whether there are other relevant TSBs (product information,

software updates, etc.) for this vehicle regarding online services, the data bus diagnostic interface or the

emergency call module. If so, work through them first. If a TSB offers a software update for data bus

diagnostic interface J533, emergency call module control unit J949 or control unit for information electronics

J794, these should always be performed.
* Check whether the privacy settings in the vehicle are active. If this is the case, deactivate them and then put

the vehicle in bus sleep mode. Assess the status of the LED after switching on the ignition again.
* — Ifthe LED is still not green, perform a restart of the emergency call module via the “Control module restart”

routine. You will find instructions under “Emergency call module restart”.
* Please also refer to service info TSB 2061028, 97 Audi connect GEN3/GEN4: No Services in MMI and SOS

LED does not turn green after PDI.
Emergency call module restart:
©
Please observe the following instructions for restarting the emergency call module. Failure to observe

these instructions may result in irreparable damage to the emergency call system!
First restart the control unit via ODIS. To do so, select the following in the test plan: Select own tests > Diagnostic

capable system > 0075 — Emergency call module — J949 > 0075 — Emergency call module, functions > 0075 —

Control module restart. Then reassess the complaint.
If the complaint persists, please reset terminal 30 by disconnecting the 12V vehicle battery. You will find information

on this in the Workshop Manual.
If the terminal 30 reset did not resolve the issue, you can initiate a new vehicle registration in the backend. Proceed

as follows in the service portlet:
Service portlet
To initiate a new vehicle registration in the backend, you have the option of resetting the vehicle in the backend in

the service portlet.
To use this method, press the “Reset control unit in backend” button under the “Vehicle communication” tab in the

service portlet.
Switch the ignition on and check the LED in the vehicle.
If the control unit has already been replaced, please press the “Vehicle data synchronization for backend”

button under the “Vehicle data” tab in the service portlet.
In addition to this, the unresolved and resolved IT issues of the last 30 days can be viewed under the “Breaking

News” tab in the service portlet.
If you are unable to rectify the problem despite the above information, read out all measured values from the

emergency call module (diagnostic address 0075) and contact TAC to receive further support for the repair.
Warranty
If you are billing AUDI AG/the importer according to the warranty guidelines, please note the following accounting

instructions:
Please note that the scenarios specified below are not related to the scenarios described in the Measure chapter.
Selecting service number
When invoicing based on this TSB, the correct service number must be selected according to the situation. The

following applies when doing so:
1. Scenario 1: Service number 9107 may not be used to invoice replacement of parts. This service number is

reserved for technical causes outside the vehicle. This can affect the mobile network and backend, for

example.
2. Scenario 2: Work performed on the vehicle due to an issue that is not caused by the vehicle (e.g. a terminal 30

reset based on instructions given in response to a technical repair query or reporting obligation) must be

invoiced using service number 9107 and not using the service number for the component on which the repair

was performed.
3. Scenario 3: The service number for a component (9145, 9170 or 9035) should be used for invoicing if the

component in question was determined to be the cause of the complaint described. You can confirm this

based on the following:
a. Arelevant event memory entry is logged in the data bus diagnostic interface J533 or in the emergency

call module J949.
b. The emergency call module J949 or the data bus diagnostic interface J533 had to be replaced.

Use the following table to determine the service numbers for the components.
Service number
Component
9170
Diagnostic address 0075

OCU3 or OCU4

Models: A3, Q3, Q4 (including S and RS versions)
System designation in diagnostic log:
(1) Systembezeichnung- OCU3
9145
Diagnostic address 0075
Connectivity box Low or connectivity box High
Models: A4, A5, Q5, AG, A7, Q7, A8, Q8, e-tron, e-tron GT

(including S and RS versions)
System designation in diagnostic log:
(2) Systembezeichnung- ConBox
(2) Systembezeichnung- CB_H
9035
Diagnostic address 0019
Data bus diagnostic interface
System designation: Gateway
Damage code
For certain service numbers, a new damage code has been created specifically for this complaint.
A039 = emergency call LED not green
(does not apply to service number 9035)
As a result, the following combinations may be used for invoicing:
Service number /

damage code
Explanation
9113 / 0040 When an event memory entry for the GPS aerial was logged in emergency call module

J949 or data bus diagnostic interface J533

9138 / 0040 When an event memory entry for the aerial was logged in emergency call module J949
or data bus diagnostic interface J533 or aerial module 8107
9156 / 0040 When an event memory entry for the loudspeaker for telephone was logged in

emergency call module J949
9157 / 0040 When an event memory entry for the microphone is logged in emergency call module

J949 or information electronics J794
9178 / 0040 When an event memory entry for the emergency battery for telematics is logged in

emergency call module J949
9107 / A039 For work performed on vehicle due to issue not caused by vehicle technology
9145 / A039 When an event memory entry was logged in emergency call module J949 or emergency

call module has been replaced, and system designation is “ConBox’ or “CB_H_”
9170 / A039 When an event memory entry was logged in emergency call module J949 or emergency

call module has been replaced, and system designation includes “OCU”
9035 / 0039 When an event memory entry was logged in data bus diagnostic interface J533 or data

bus diagnostic interface J533 was replaced
Repair operations
Claim Type:
* — If the vehicle is outside of any warranty, this Technical Service Bulletin is

informational only.
Service Number: See above

Damage Code: See above

Labor Operations: Check online services 9170 0199 Please bill according

Scenario 2 to the time required

Check vehicle (bus sleep mode) | 0689 0199 10 TU

Check online services 9170 0199 Please bill according

. to the time required

Scenario 3
Check vehicle (bus sleep mode) | 0689 0199 10 TU
Check online services 9170 0199 Please bill according

to the time required

Scenario 3a | GFF / Guided Functions 0150 0060 Labor according to

the diagnostic log

or

Scenario 3b | Remove and install/replace 9170 19xx/ See SRT with

telematics control unit 9170 55xx associated

operations
Check vehicle (bus sleep mode) | 0689 0199 10 TU
Claim Comment: As per TSB 2079652/1
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.
Please note the information on predecessors and items that are included and excluded in the repair

operations, as well as any associated tasks.
Additional Information
All part and service references provided in this TSB (2079652) are subject to change and/or removal. Always check

with your Parts Department and/or ETKA for the latest information and parts bulletins. Please check the Repair

Manual for fasteners, bolts, nuts, and screws that require replacement during the repair.
©2025 Audi of America, Inc. All rignts reserved. The 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.

Bestseller No. 1

ANCEL AD310 Classic Enhanced Universal OBD II Scanner Car Engine Fault Code Reader CAN Diagnostic Scan Tool, Read and Clear Error Codes for 1996 or Newer OBD2 Protocol Vehicle (Black)

CEL Doctor: The ANCEL AD310 is one of the best-selling OBD II scanners on the market and is recommended by Scotty Kilmer, a YouTuber and auto mechanic. It can easily determine the cause of the check engine light coming on. After repairing the vehicle's problems, it can quickly read and clear diagnostic trouble codes of emission system, read live data & hard memory data, view freeze frame, I/M monitor readiness and collect vehicle information.
Sturdy and Compact: Equipped with a 2.5 foot cable made of very thick, flexible insulation. It is important to have a sturdy scanner as it can easily fall to the ground when working in a car. The AD310 OBD2 scanner is a well-constructed mechanic tool with a sleek design. It weighs 12 ounces and measures 8.9 x 6.9 x 1.4 inches. Thanks to its compact design and light weight, transporting the device is not a problem. The buttons are clearly labelled and the screen is large and displays results clearly.
Accurate Fast and Easy to Use: The AD310 scanner can help you or your mechanic understand if your car is in good condition, provides exceptionally accurate and fast results, reads and clears engine trouble emission codes in seconds after you fixed the problem. This device will let you know immediately and fix the problem right away without any car knowledge. No need for batteries or a charger, get power directly from the OBDII Data Link Connector in your vehicle.
OBDII Protocols and Car Compatibility: Many cheap scan tools do not really support all OBD2 protocols. AD310 scanner as it can support all OBDII protocols such as KWP2000, J1850 VPW, ISO9141, J1850 PWM and CAN. This device also has extensive vehicle compatibility with 1996 US-based, 2000 EU-based and Asian cars, light trucks, SUVs, as well as newer OBD2 and CAN vehicles both domestic and foreign. Pls confirm with our customer service whether it is compatible with your vehicle before purchasing.
Home Necessity and Worthy to Own: This is an excellent code reader to travel or home with as it weighs less and it is compact in design. You can easily slide it in your backpack as you head to the garage, or put it on the dashboard, this will be a great fit for you. The AD310 is not only portable, but also accurate and fast in performance. Moreover, it covers various car brands and is suitable for people who just need a code reader to check their car.

Bestseller No. 2

MOTOPOWER MP69033 Car OBD2 Scanner Code Reader Engine Fault Scanner CAN Diagnostic Scan Tool for All OBD II Protocol Cars Since 1996, Yellow

Multi-Functions - Practical Multi-Functions OBD2 code reader features built-in OBD2 DTC lookup library, which help you to determine the cause of the engine light, read code, erase code, view freeze frame, I/M ready, vehicle information, data flow, real-time curve, get vehicle speed information, calculate load value, engine coolant temperature, get engine speed.
Wide Capability - Supports 9 protocols compatible with most 1996 US-Based, 2000 EU-Based and Asian cars, and newer OBD II & CAN domestic or import vehicles. Supports 6 languages - English,German, Dutch, Spanish, French, Italian.
2.8" LCD Display - Designed with a clear display 2.8" Large LCD screen - white backlight and contrast adjustment. No need any battery or charger, OBD reader gets the power directly from your vehicle through the OBDII Data Link Connector.
Compact Design - Car diagnostic scanner is equipped with a 2.5 feet long cable and made of a very thick flexible insulator.There are 6 buttons on OBD2 Scanner:scroll up/down,enter/exit and buttons that quick query VIN vehicle number& the DTC fault code.
ABS / Airbag codes NOT Supported - It is able to read and clear check engine information which is part of OBDII system, but it cannot work with non-OBDII systems, including ABS / Airbag / Oil Service Light, etc.

Bestseller No. 3

FOXWELL NT301 OBD2 Scanner Live Data Professional Mechanic OBDII Diagnostic Code Reader Tool for Check Engine Light

【Your Personal CEL Doctor – Read & Clear Engine Codes】The NT301 OBD2 scanner lets you read diagnostic trouble codes (DTCs), check em-issions readiness, turn off your Check Engine Light (CEL) or MIL, reset monitors, and view live data streams. It retrieves your vehicle's VIN instantly. Like all standard OBD2 scanners, it clears codes only after repairs are completed—if the issue persists, the code will return. Designed for DIYers who want to understand what’s really going on under the hood.
【Easy Code Reading – Just Plug & Play】Simply plug into the OBD2 port, turn the ignition to “ON” (engine off), and select the correct menu: Select OBDII-> Wait for seconds-> Select Read codes. For accurate results, ensure your vehicle is compatible and the OBD2 port is free from damage or wiring issues. No batteries needed— powered directly by your car.
【Live Data Graphing & Accuracy for Most OBD2 Vehicles】View and log live sensor data in graph form—monitor oxygen sensors, fuel trims, coolant temp, RPM, and more. Spot trends and suspicious values in real time. Compatible with most 1996+ gasoline cars, light trucks, and SUVs sold in the U.S., as well as many 2000+ European and Asian models. Also works on 12V diesel vehicles equipped with OBD2.
【S-mog Check Helper – Know Your Readiness Status at a Glance】With dedicated I/M readiness hotkeys and a simple Red-Yellow-Green LED indicator, you’ll instantly know if your vehicle is ready for em-issions testing. Built-in speaker provides audio feedback. No guesswork—just confidence before you head to the test center.
【A Must-Have Tool for Every Home Mechanic】Compact, rugged, and ready to use right out of the box. The 2.8” color screen is easy to read, even in daylight. No charging or setup required—just plug into the 16-pin DLC and start diagnosing. Recommended by professional mechanics on YouTube and trusted by DIYers worldwide.

Last update on 2026-03-28 / Affiliate links / Images from Amazon Product Advertising API

This product presentation was made with AAWP plugin.

Buffer Copy Email Facebook Flipboard Hacker News LinkedIn Messenger Mix Pinterest Print Reddit SMS Telegram Tumblr X VK WhatsApp Line Xing Threads