2026 Mercedes-Benz CLA 250+ (ev) TSBs

Cause Accidental or unnoticed activation of the button to open the tailgate on the vehicle key. EXAMPLE: when stored in trouser pocket, handbag etc. Remedy As of the 6th generation, the vehicle key can be recoded so that the tailgate no longer opens as a result of a long press on the button, but by doubleclicking on the button instead. This reduces the likelihood of the button being activated accidentally or unintentionally. The recoding can be carried out as follows: 1. Add SA Code O19 into VeDoc (O for Oscar, not "zero") an XSS ticket may be necessary to add the SA code 2. Perform SCN coding of EIS N73 control unit 3. Deactivate the vehicle key (a successful deactivation is indicated by the LED lighting up 2x briefly and then 1x for a long period). 4. Place the vehicle key in the storage compartment on the key symbol and turn on the ignition. IMPORTANT: all other vehicle keys must be outside the recognition range of the vehicle when doing this! Perform steps 3 and 4 successively for all vehicle keys. Notes: 6th, 7th and 8th generation keys can be deactivated as follows: Up to modification year 22/1 by double clicking the "Lock button" As of modification year 22/1, by press and holding the Lock button", then doubleclick the Unlock button" at the same time. On model series 167, the storage compartment with the key symbol is located in the armrest. The SCN coding from the EZS is only transferred correctly to the vehicle key under the following conditions: Only one vehicle key is located in the vehicle, this key has been deactivated and it is positioned on the marking in the storage compartment for the data transfer. The costs for this adaptation are to be borne by the customer. For the newer BR 174, 178, 244, 248, 520, and 540, a software update must be initiated, as there is no way to perform SCN coding.

Cause Variable switching frequencies in the high-voltage on-board electrical system can cause vibrations that lead to noise complaints on the HV-PTC N33/16 (air heater). Remedy Perform the following steps: 1. Compare the noise with the attached example. If the noise matches the example, proceed to step 2; otherwise, create a TIPS case. 2. Check whether SNR A1748354600 is installed. (Quick test N33/16 Hardware): If SNR A1748354600 is installed, proceed to step 3; otherwise, create a TIPS case. 3. Hardware replacement of the HV-PTC N33/16 air heater install a new part with the current item number as per XPPI.

Cause In very rare cases ARTEMIS is sending a battery warning event to the Mercedes Intelligent Cloud (MIC) even though the signal is not present on the vehicle. Remedy Update the vehicle to the latest available car package release MB.OS 1.3.10 or newer. New ARTEMIS software E216.6 or higher will be installed that contains a fix.

Note: Fault code U160E97. Additionally, P161400 and/or C11009A may also be stored. Affected control units can be any of the radar sensors (B29/21, 22, 23, or 24). Cause Hardware malfunction. Remedy If the DTC is present in any of the radar sensors prior to a vehicle production date of May 12, 2026, follow the guided test. If the DTC is present in any of the radar sensors after a vehicle production date of May 12, 2026, please create a TIPS case to the Body/Chassis/Entertainment Inbox. Note: Multiple radar sensors in a vehicle may also be affected.

- Creaking - Squeaking - Chattering - Humming - Grinding Cause At present, there are no known noise problems with the steering column. Remedy Check surrounding area of the steering column for possible noises. Instrument panel support Steering column switch module NOTE: Occasionally to verify complaint, the steering column/vehicle needs to be in direct sunlight or hot conditions for a few hours. If noise only occurs when adjusting the steering column via electric actuation, please perform: 1. Disassemble bellows of steering column tube module. 2. Move steering column entirely out and entirely down. 3. Grease steering column on all pivot points including, but not limited to, green-marked positions with a suitable brush (find pictures in attachment). 4. Move column up 1/4 of the way and grease again. 5. Continue until upper limit stop is reached. 6. Then move steering column adjustment in all directions from limit stop to limit stop several times to work in the grease. 7. If noise does not resolve, wipe excess grease off and perform greasing and movement to limit stops in all directions again. For all other noises or if the above does not resolve, create a TIPS case Body, Chassis, and Entertainment inbox. Attach a detailed description of the noise complaint, images, and a recording of the noise. Include detailed items of the following: Position of height and longitudinal adjustment when the noise occurs If possible, locate affected component part on steering column State any change in the noise when steering column component parts are touched (e.g. spring, etc.)

due to system limitations and environmental effects. This can occur during startup of the vehicle but also during driving. No case is necessary for these. Please refer to the Owner's Manual for driver assistance system limitations and environmental effects. For "driver assistance systems unavailable" that are persistent or show on every key cycle AND Vehicle was produced prior to February 27, 2026. Cause Cause 1: In rare cases, one or more of the fault codes U05B555, U05B655, U05B755 or U05B855 (implausible data was received from the front/rear outer right/left radar sensor. The component part is not configured.) is "Active" in the N62/5 control unit. This cause mainly occurs in vehicles produced prior to September 5, 2025. Cause 2: The initial calibration of the acceleration sensor (IMU) in the N62/5 control unit was not performed/completed. There is no relevant fault code active in the N62/5 control unit. This cause mainly occurs in vehicles produced prior to February 27, 2026. Remedy Remedy 1: Navigate to N62/5 control unit via XENTRY and carry out: "Adaptations > Teach-in processes > Calibration of the N62/5 control unit (driver assistance system control unit)." If it is not possible to perform this process or the system is recognizing that all sensors are already calibrated and nothing further needs to be completed, we alternatively recommend carrying out "Calibration drive after exchange of the component part front bumper or rear bumper" under Teach-in processes. Once the calibration is started, the calibration screen will appear on the head unit. Xentry will instruct the user to disconnect the device from the vehicle and perform the driving calibration. XENTRY MUST be disconnected and cannot be left connected. Remedy 2: Navigate to N62/5 control unit via XENTRY and carry out: "Adaptations > Teach-in processes > Calibration of the N62/5 control unit (driver assistance system control unit)." If there are no identified calibrations, perform calibration drive for the N62/5 control unit. No XENTRY diagnostic device is required for this, as the calibration does not need to be initiated via XENTRY! Perform a calibration drive of at least 5 minutes and at least 20 turns (left/right evenly distributed) without interrupting the drive (stop and go is permissible, but no ignition cycling). The driving speed should be approximately 20 km/h, and the steering wheel angle about 180 degrees (ideal are 90 turns that must be driven through at more than 10 km/h). No message is displayed to indicate that the calibration has been successfully completed. After the calibration drive, the vehicle must be parked and locked for at least seven minutes to allow the vehicle bus to enter sleep mode. Once the bus sleep mode has completed, the fault messages should no longer be displayed in the driver display. Driver support systems may still not be fully available at this time. This is indicated by the ADAS system icons (see picture ADAS icons). These are available after a further driving time of approx. 10 minutes. Connect the vehicle to Mercedes me Connect. MB.Drive, Navigation, and On-Demand features REQUIRE that the vehicle is linked to a profile. Please also note the additional information regarding the connection between Mandatory Pairing (Head Unit Profile) and Pre-Delivery Inspection (PDI).

Remedy Check surrounding area of the steering column for possible noises. Instrument panel support Steering column switch module If noise only occurs when adjusting the steering column via electric actuation please perform: 1. Disassemble bellows of steering column tube module. 2. Move steering column entirely out and entirely down. 3. Grease steering column on green-marked positions with a suitable brush (find pictures in attachment). 4. Move column up 1/4 of the way and grease again. 5. Continue until upper limit stop is reached. 6. Then move steering column adjustment in all directions from limit stop to limit stop several times to work in the grease. 7. If noise does not resolve, perform above procedure again and anywhere there are movement or friction points that the noise seems to be emanating from. 8. Then move steering column adjustment in all directions from limit stop to limit stop several times to work in the grease. 9. If noise still does not resolve, please open a TIPS case. For all other noises or if the above does not resolve, create a TIPS case Body, Chassis, and Entertainment inbox. Attach a detailed description of the noise complaint, images, and a recording of the noise. A detailed description includes: Position of height and longitudinal adjustment when the noise occurs If possible, locate affected component part on steering column State any change in the noise when steering column component parts are touched (e.g. spring, etc.)

CLA (174 platform) vehicles, the software of the communication module (ARTEMIS) might not be configured according to current production specifications. As a result, remote status updates, or remote commands may not be available through the Mercedes-Benz App. Remedy MBUSA will conduct a service campaign. An authorized Mercedes-Benz dealer will update the software in the ARTEMIS control unit on the affected vehicles. With the update of the ARTEMIS, the latest Mercedes-Benz Operating System (MB.OS) version will also be installed on the vehicles.

Cause Accidental or unnoticed activation of the button to open the tailgate on the vehicle key. EXAMPLE: when stored in trouser pocket, handbag etc. Remedy As of the 6th generation, the vehicle key can be recoded so that the tailgate no longer opens as a result of a long press on the button, but by double-clicking on the button instead. This reduces the likelihood of the button being activated accidentally or unintentionally. The recoding can be carried out as follows: 1. Add SA Code O19 into VeDoc (O for Oscar, not "zero") an XSS ticket may be necessary to add the SA code 2. Perform SCN coding of EIS N73 control unit 3. Deactivate the vehicle key (a successful deactivation is indicated by the LED lighting up 2x briefly and then 1x for a long period). 4. Place the vehicle key in the storage compartment on the key symbol and turn on the ignition. IMPORTANT: all other vehicle keys must be outside the recognition range of the vehicle when doing this! Perform steps 3 and 4 successively for all vehicle keys. Notes: 6th, 7th and 8th generation keys can be deactivated as follows: Up to modification year 22/1 by double clicking the "Lock button" As of modification year 22/1, by press and holding the Lock button", then doubleclick the Unlock button" at the same time. On model series 167, the storage compartment with the key symbol is located in the armrest. The SCN coding from the EZS is only transferred correctly to the vehicle key under the following conditions: Only one vehicle key is located in the vehicle, this key has been deactivated and it is positioned on the marking in the storage compartment for the data transfer. The costs for this adaptation are to be borne by the customer.

due to system limitations and environmental effects. This can occur during startup of the vehicle but also during driving. No case is necessary for these. Please refer to the Owner's Manual for driver assistance system limitations and environmental effects. If the vehicle is on MB.OS 1.3.0 or later and the "driver assistance systems unavailable" message displays in the instrument cluster and either: DOES NOT clear within a few seconds OR Appears on every key cycle and DOES NOT clear NOTE: To find the MB.OS version number: 1. Navigate to VeDoc. 2. Go to "Control Units" tab. 3. Find the header bar labeled "Vehicle Information for Control Units". 4. Locate "MB.OS car package release customer version". Cause Cause 1: In rare cases, one or more of the fault codes U05B555, U05B655, U05B755 or U05B855 (implausible data was received from the front/rear outer right/left radar sensor. The component part is not configured.) is "Active" in the N62/5 control unit. This cause mainly occurs in vehicles produced prior to September 5, 2025. Cause 2: The initial calibration of the acceleration sensor (IMU) in the N62/5 control unit was not performed/completed. There is no relevant fault code active in the N62/5 control unit. This cause mainly occurs in vehicles produced prior to February 27, 2026. Cause 3: Above "Cause 2" did not fix. IDC hardware and software reset and full sensor suite calibration needed. Cause 4: Occasionally the vehicle will exhibit all ADAS systems offline on key cycle or during driving. Once the key is cycled the systems will function and messages gone. Subsequent key and drive cycles will not exhibit. Due to environmental influence or other reason. Remedy Remedy 1: Navigate to N62/5 control unit via XENTRY and carry out: "Adaptations > Teach-in processes > Calibration of the N62/5 control unit (driver assistance system control unit)." If it is not possible to perform this process or the system is recognizing that all sensors are already calibrated and nothing further needs to be completed, we alternatively recommend carrying out "Calibration drive after exchange of the component part front bumper or rear bumper" under Teach-in processes. Once the calibration is started, the calibration screen will appear on the head unit. Xentry will instruct the user to disconnect the device from the vehicle and perform the driving calibration. XENTRY MUST be disconnected and cannot be left connected. Remedy 2: Navigate to N62/5 control unit via XENTRY and carry out: "Adaptations > Teach-in processes > Calibration of the N62/5 control unit (driver assistance system control unit)." If there are no identified calibrations, perform calibration drive for the N62/5 control unit. No XENTRY diagnostic device is required for this, as the calibration does not need to be initiated via XENTRY! Perform a calibration drive of at least 5 minutes and at least 20 turns (left/right evenly distributed) without interrupting the drive (stop and go is permissible, but no ignition cycling). The driving speed should be approximately 20 km/h, and the steering wheel angle about 180 degrees (ideal are 90 turns that must be driven through at more than 10 km/h). No message is displayed to indicate that the calibration has been successfully completed. After the calibration drive, the vehicle must be parked and locked for at least seven minutes to allow the vehicle bus to enter sleep mode. Once the bus sleep mode has completed, the fault messages should no longer be displayed in the driver display. Driver support systems may still not be fully available at this time. This is indicated by the ADAS system icons (see picture ADAS icons). These are available after a further driving time of approx. 10 minutes. Please see attachment.

between the MMC App and the vehicle. The following complaints are possible: Vehicle remote control is not functional (unlocking/locking the vehicle via the Mercedes-Benz app). The vehicle status data within the Mercedes-Benz app is outdated and does not update. Digital Extra services cannot be activated/deactivated. A yellow message "Vehicle connection restricted" permanently appears in the Mercedes-Benz App. Cause A bug in the software update process can cause the ARTEMIS module to be unable to register with the backend after updating to software E216.4. Remedy Always use the latest XENTRY Diagnosis software version with all available AddOns. Required AddOns: AddOn 33166 for XD 12/25 or AddOn 33165 for XD 03/26 must be installed. Do not use XENTRY DVD 09/25 Then, perform a Seamless Update. XENTRY -> Overview -> Control Units List -> Software Update This will recode the ARTEMIS control unit A2/93 and resolve the error. If the complaint persists, please open a TIPS case to the Body/Chassis/Entertainment inbox with a current ARTEMIS control unit log file.

- Creaking - Squeaking - Chattering - Humming - Grinding Cause At present, there are no known noise problems with the steering column. Remedy Check surrounding area of the steering column for possible noises. Instrument panel support Steering column switch module If noise only occurs when adjusting the steering column via electric actuation please perform: 1. Disassemble bellows of steering column tube module. 2. Move steering column entirely out and entirely down. 3. Grease steering column on green-marked positions with a suitable brush (find pictures in attachment). 4. Move column up 1/4 of the way and grease again. 5. Continue until upper limit stop is reached. 6. Then move steering column adjustment in all directions from limit stop to limit stop several times to work in the grease. 7. If noise does not resolve, perform above procedure again. 8. Then move steering column adjustment in all directions from limit stop to limit stop several times to work in the grease. 9. If noise still does not resolve, please open a TIPS case. For all other noises or if the above does not resolve, create a TIPS case Body, Chassis, and Entertainment inbox. Attach a detailed description of the noise complaint, images, and a recording of the noise. A detailed description includes: Position of height and longitudinal adjustment when the noise occurs If possible, locate affected component part on steering column State any change in the noise when steering column component parts are touched (e.g. spring, etc.)

There is an implausible signal." In the quick test, there are also no other DTC's in other control units that point to or reference N80 Steering Column Control Module ("SCCM"). There is no effect on any other components or vehicle functions and it does not cause an instrument cluster light. Cause The DTC only ever occurs during initialization (initialization occurs after bus sleep). The SCCM then resets itself. Remedy 1. If the error is stored and no other control unit points to the N80 SCCM ignore and erase. Software expected in Q4 2026. 2.If the DTC is in the N80 SCCM AND the following DTC's are in N30/3 (Electronic Stability Program) and N68 (Electric Power Steering): N30/3 ESP: U071286, Steering column tube module control unit has a malfunction. There is an incorrect signal. N68 EPS: U042986, Implausible data were received from the steering column module. There is an incorrect signal. Please open a TIPS case to the Body/Chassis/Entertainment inbox.

MUST be in conjunction with a fault code in control unit N62/5 IDC (driver assistance systems): B1D9198 (Stored) - The "Driver assistance system" control unit is malfunctioning. Overtemperature in the component or system. Under certain circumstances, additional fault codes may be present in N125 CDCC_EV (central controller for charging and driving). Cause Air in the low-temperature circuit Remedy 1. Do not replace any parts 2. Perform a leak test on the low-temperature circuit 3. Perform a visual check of the coolant connection on the N62/5 control unit 4. Perform the bleeding routine via XENTRY and WIS. 5. Check the coolant level and top up if necessary (see WIS references) If this does not remedy the problem, please open a TIPS case to Body/Chassis/Entertainment.

due to system limitations and environmental effects. No case is necessary for these. Please refer to the Owner's Manual for driver assistance system limitations and environmental effects. If the vehicle is on MB.OS 1.3.0 or later and the "driver assistance systems unavailable" message displays in the instrument cluster and either: DOES NOT clear within a few seconds OR Appears on every key cycle and DOES NOT clear NOTE: To find the MB.OS version number: 1. Navigate to VeDoc. 2. Go to "Control Units" tab. 3. Find the header bar labeled "Vehicle Information for Control Units". 4. Locate "MB.OS car package release customer version". Cause Under Determination. Remedy Open a TIPS case to the Body/Chassis/Entertainment inbox based on the symptom below: If vehicle is still actively showing the white driver assist message: Do not shut off the vehicle and gather the following: Quicktest N62/5 Driver Assistance Control Unit Log with all sensors included. Other control unit logs that are referenced in N62/5 DTC's. If the vehicle is not actively showing the white driver assist message: Quicktest N62/5 Driver Assistance Control Unit Log with all sensors included.

Cause Accidental or unnoticed activation of the button to open the tailgate on the vehicle key. E.g. when stored in trouser pocket, handbag etc. Remedy As of the 6th generation, the vehicle key can be recoded so that the tailgate no longer opens as a result of a long press on the button, but by double-clicking on the button instead. This reduces the likelihood of the button being activated accidentally or unintentionally. The recoding can be carried out as follows: 1. Add SA Code O19 into VeDoc (O for Oscar, not "zero") an XSS ticket may be necessary to add the SA code 2. Perform SCN coding of EIS N73 control unit 3. Deactivate the vehicle key (a successful deactivation is indicated by the LED lighting up 2x briefly and then 1x for a long period). 4. Place the vehicle key in the storage compartment on the key symbol and turn on the ignition. All other vehicle keys must be outside of the vehicle when doing this! Perform steps 3 and 4 successively for all vehicle keys. Notes: 6th, 7th and 8th generation keys can be deactivated as follows: Up to modification year 22/1 double-click on the locking button As of modification year 22/1, by pressing and holding the locking button + double-clicking on the release tab On model series 167, the storage compartment with the key symbol is located in the armrest. The SCN coding from the EZS is only transferred correctly to the vehicle key under the following conditions: Only one vehicle key is located in the vehicle, this key has been deactivated and it is positioned on the marking in the storage compartment for the data transfer. The costs for this adaptation are to be borne by the customer.

Cause Variable switching frequencies in the high-voltage on-board electrical system can cause vibrations that lead to noise complaints on the HV-PTC N33/16 (air heater). Remedy Perform the following steps: 1. Compare the noise with the attached example. If the noise matches the example, proceed to step 2; otherwise, create a TIPS case. 2. Check whether SNR A1748354600 is installed. (Quick test N33/16 Hardware): If SNR A1748354600 is installed, proceed to step 3; otherwise, create a TIPS case. 3. Hardware replacement of the HV-PTC N33/16 air heater install a new part with the current item number as per XPPI.

P0CFE00 is stored in control unit "N83 - AC charger for high-voltage battery (SG-LG)". The instrument cluster message and the FC memory entry can also appear at the beginning of the charging pause during delayed charging. Both only occur in combination with active pre-entry climate control. Cause Software in control unit "N83 - AC charger for high-voltage battery (SG-LG)". Remedy For model series 206 and 223 with code 802: Perform a software update and SCN coding for the control unit "N83/11 - AC charger for high-voltage battery (SGLG)" in order to remedy the problem. For model series 243: The correction is already available. Perform a software update and SCN coding for the control units "N116/5 - Direct current charging connection unit (DCCU)" and "N83/11 - AC charger for high-voltage battery (SG-LG)" in order to remedy the problem.

One or More PARK Sensor Activations 3. Red Ring Around Vehicle 4. "Active Parking and Parking Assist Inoperative" on Instrument Cluster 5. Cameras 6. Other Park Topics Cause Various root causes Remedy See attached diagnostic guide.

- Creaking - Squeaking - Chattering - Humming - Grinding Cause At present, there are no known noise problems with the steering column. Remedy Check surrounding area of the steering column for possible noises. Instrument panel support Steering column switch module If noise only occurs when adjusting the steering column via electric actuation please perform: 1. Disassemble bellows of steering column tube module. 2. Move steering column entirely out and entirely down. 3. Grease steering column on green-marked positions with a suitable brush (find pictures in attachment). 4. Move column up 1/4 of the way and grease again. 5. Continue until upper limit stop is reached. 6. Then move steering column adjustment in all directions from limit stop to limit stop several times to work in the grease. 7. If noise does not resolve, perform above procedure again. 8. Then move steering column adjustment in all directions from limit stop to limit stop several times to work in the grease. 9. If noise still does not resolve, please open a TIPS case. For all other noises or if the above does not resolve, create a TIPS case Body, Chassis, and Entertainment inbox. Attach a detailed description of the noise complaint, images, and a recording of the noise. A detailed description includes: Position of height and longitudinal adjustment when the noise occurs If possible, locate affected component part on steering column State any change in the noise when steering column component parts are touched (e.g. spring, etc.)

No damage is present on the lock. The problem may occur in the following scenario: 1. Ignition on/vehicle ready to drive 2. Frunk is unlocked 3. Ignition is switched off 4. Frunk is closed. Cause After the ignition is switched off, the head unit CIVIC174 does not register that the frunk is closed. -> Software A26/17 Head Unit (CIVIC174) Remedy SW solution is being worked on. In the event of a problem, please open and close the frunk with the ignition switched on.

Cause Variable switching frequencies in the high-voltage on-board electrical system can cause vibrations that lead to noise complaints on the HV-PTC N33/16 (air heater). Remedy Note: Replacing the hardware does not solve the problem at present! Modified hardware for the HV-PTC (air heater) will be available from the beginning of 2026.

Cause The XENTRY battery tester uses the stored on-board electrical system data in the SAM module to access the health of the 12 volt battery. The XENTRY battery test may not take into account a single discharge event because the SAM or EZS cannot record the data if the battery is discharged. Note: A discharged battery does not necessarily need to be replaced. A discharged battery may be recovered with no permanent damage. Remedy 1) If the battery is discharged, charge the battery. Review WS54.00-P-0037B for minimum charger specifications. Note the amperage difference between trickle (maintainer) chargers of at least 16A and quick chargers of at least 30A. Review AP54.10-P-5449U. Note when battery is sufficiently charged the charger current is less 5A. 2) While charging the battery, analyze the vehicle data to determine root cause of discharge using the following data points: NOTE: For guidance on use of the on-board electrical data please review the AKUBIS video titled "New onboard electrical system diagnosis shown on BR 166". The video can be accessed through WIS by following the path WSM--> content by model series --> passenger cars --> ML-Class --> Model 166 --> group 54 --> New onboard electrical system diagnosis. Refer to the March 2023 PCTT for the video walkthrough of analysis as well as the attachment of the slides to this Li. Review GF54.10-P-1012A regarding what can cause deep discharge protection to not end a battery draw. Review SI54.10-P-0024A for proper maintenance of the vehicle. For Star 2 vehicles: -Review FSAM on-board electrical data conspicuous records NOTE: This data can be found via FSAM N10/6 -> Actual Values -> On-board electrical system -> On-board electrical system data For Star 3 vehicles: -Review N73/3 EZS on-board electrical data conspicuous records NOTE: This data can be found via EZS N73/3 -> Actual Values -> On-board electrical system -> On-board electrical system data 3) Determine if root cause is due to: vehicle technical issue? customer behavior? NOTE: Recommend using battery analysis sheet found in XiW -> Local Contents -> Diagnostic info -> Battery Discharge Worksheet 4) If battery still does not accept charge AND the vehicle does not fall within the parameters of improper maintenance, then create a TIPS case. *IMPORTANT* - If the improper maintenance/use is found during diagnosis, DO NOT open a TIPS case. If a TIPS case is opened, it will be marked 1 star and directed to your assigned FSE for review. TIPS Case must include with the case: Amperage setting of charger and time battery was on charger XENTRY Battery Tester results Voltage of battery taken with multimeter: Do not connect charger while taking measurements N10/6 FSAM, (N73 or N73/3) and (N73*1 or N73/3*1) Workshop analysis of conspicuous data Root cause analysis for battery discharge based on the above documents (technical, customer, etc.) NOTE: For expedited results when creating a case write customer complaint as "XENTRY Battery Tester implausible".

Cause Under analysis. Remedy To narrow down the cause, first of all remove the door trim. If the noise continues to occur even with the door trim removed, then continue the diagnosis working towards the speaker and if necessary, create a TIPS case with an informative video as an attachment. Note: Please refer to this document in the warranty claim and, once diagnosis is completed, select the damage code depending on the component part that is causing the issue. If the noise stops when the door trim is removed, please proceed in accordance with LI72.10P067691. Information: In this case, do not use a damage code for the speakers in the warranty claim!

When vehicle is shut off, instrument cluster message appears for "Driver Assistance Systems Available". Cause Under Determination. Remedy Perform initial startup of the head unit (A26/17) and the intelligent drive controller (N62/5).

When vehicle is shut off, instrument cluster message appears for "Driver Assistance Systems Available". Cause Under Determination. Remedy Perform initial startup of the head unit (A26/17) and the intelligent drive controller (N62/5).

Cause Under analysis. Remedy To narrow down the cause, first of all remove the door trim. If the noise continues to occur even with the door trim removed, then continue the diagnosis working towards the speaker and if necessary, create a TIPS case with an informative video as an attachment. Information: Please refer to this document in the warranty claim and, after completing diagnosis, select the damage code corresponding to the component part that caused the problem. If the noise stops when the door trim is removed, please proceed in accordance with LI72.10-P-067691. Information: In this case, do not use a damage code for the speakers in the warranty claim!

menu, e.g., 505 or 550A, which includes a service A. Cause The root cause is currently being investigated. Remedy To determine the cause, the instrument cluster control unit (N133/1) and powertrain control unit (N127) logs are required before confirming the service or correction using XENTRY Diagnosis. Please open a TIPS case to BCE inbox with the requested information in the attachments.

Assistance System Functions Limited Please Drive with Caution See Operator's Manual". Note: Verify this is the exact message, there are other variants of white ADAS cluster messages. To verify MB.OS number, it can be found in: 1. A26/17 in Xentry under version or 2. VeDoc > Vehicle Information for Control Units (below reference, vehicle is on 1.3.0) The driver assistance control unit N62/5 Processor will also have an active and stored DTC U142791 - "Implausible data were received from the control unit 'Head unit'. The parameter is outside the permissible range." Cause Under Determination. Remedy Update vehicle software to MB.OS 1.3.10, it is available. If message has cleared and concern is resolved, release the vehicle. If not, open a TIPS case to Body, Chassis, and Entertainment inbox.

Assistance System Functions Limited Please Drive with Caution See Operator's Manual". Note: Verify this is the exact message, there are other variants of white ADAS cluster messages. To verify MB.OS number, it can be found in: 1. A26/17 in Xentry under version or 2. VeDoc > Vehicle Information for Control Units (below reference, vehicle is on 1.3.0) The driver assistance control unit N62/5 Processor will also have an active and stored DTC U142791 - "Implausible data were received from the control unit 'Head unit'. The parameter is outside the permissible range." Cause Under Determination. Remedy New MB.OS update by June 09, 2026 at the latest for 1.3.10. If date is prior to June 09, 2026, vehicle can be released. The message just needs to be cleared on startup in the instrument cluster and all ADAS systems function. Once software is available, update and bus sleep (30 minutes). Re-check vehicle after bus sleep for presence of cluster message. If message has cleared and concern is resolved, release the vehicle. If not, open a TIPS case to Body, Chassis, and Entertainment inbox.

Assistance System Functions Limited Please Drive with Caution See Operator's Manual". Note: Verify this is the exact message, there are other variants of white ADAS cluster messages. To verify MB.OS number, it can be found in: 1. A26/17 in Xentry under version or 2. VeDoc > Vehicle Information for Control Units (below reference, vehicle is on 1.3.0) The driver assistance control unit N62/5 Processor will also have an active and stored DTC U142791 - "Implausible data were received from the control unit 'Head unit'. The parameter is outside the permissible range." Cause Under Determination. Remedy New MB.OS update by June 06, 2026 at the latest for 1.3.10. If date is prior to June 6, 2026, vehicle can be released. The message just needs to be cleared on startup in the instrument cluster and all ADAS systems function. Once software is available, update and bus sleep (30 minutes). Re-check vehicle after bus sleep for presence of cluster message. If message has cleared and concern is resolved, release the vehicle. If not, open a TIPS case to Body, Chassis, and Entertainment inbox.

Assistance System Functions Limited Please Drive with Caution See Operator's Manual". Note: Verify this is the exact message, there are other variants of white ADAS cluster messages. The driver assistance control unit N62/5 Processor will also have an active and stored DTC U142791 - "Implausible data were received from the control unit 'Head unit'. The parameter is outside the permissible range." Cause Under Determination. Remedy Check for new MB.OS update on May 29, 2026 from 1.3.7 to 1.3.10. If available, update and bus sleep (30 minutes). Re-check vehicle after bus sleep for presence of cluster message. If message has cleared and concern is resolved, release the vehicle. If not, open a TIPS case to Body, Chassis, and Entertainment inbox.

The UI continues to show the old stations artwork instead of updating to the new one. Cause Root cause currently being investigated. Remedy Please do not replace any parts. Please create a TIPS case to Body/Chassis/Entertainment inbox.

Cause Back end documentation error. Remedy Perform special procedure in Xentry Diagnosis. Before starting, check Xentry Diagnosis for the latest add-ons. Ensure that one of the following add-ons is installed on Xentry Diagnosis: 33115 for Release 12/2025 33115 for Release 09/2025 Next, please connect the Xentry Diagnosis to the vehicle. Select A26/17 MBUX multimedia system control unit + instrument cluster (head unit). The special procedure can be accessed using the following path: Actual Values -> Head Unit -> Anti-theft Protection and Subsequent Activatable Services. A note about the front passenger display will be shown here. Please observe the instructions in Xentry. Note: The special process (see attachments) is displayed only when the problem is occurring in the vehicle currently.

the vehicle is displayed as being in the middle of the ocean. Note: No relevant DTC is displayed during the quick test. Cause The GNSS antenna is not correctly inserted at the GNSS connection (see picture in the attachment) in the head unit (A26/17). Remedy Insert the plug into the GNSS connection and ensure that the plug has engaged correctly.

Cause Under analysis. Remedy To narrow down the cause, first of all remove the door trim. If the noise continues to occur even with the door trim removed, then continue the diagnosis working towards the speaker and if necessary, create a TIPS case with an informative video as an attachment. Note: Please refer to this document in the warranty claim and, once diagnosis is completed, select the damage code depending on the component part that is causing the issue. If the noise stops when the door trim is removed, please proceed in accordance with LI72.10-P-067691. Note: In this case, do not use the damage codes for the speakers in the warranty claim.

Condition may occur on one or more doors Fault code B25A3F0 may be stored in the affected door control unit Window normalization may be lost Cause System error in the power window motor Remedy 1.) Update SCN coding of the affected door control unit (N69/x) using Xentry. Repair coding is available with Car Package Release (CPR) 1.3.0 or higher. 2.) If the complaint persists after SCN coding or for repeat complaints replace the power window motor on the affected door following applicable WIS instructions.

Cause Fogging of the headlamps is a natural phenomenon, which can occur under certain climatic conditions. It does not lead to any technical impairment of the headlamp. If a pressure compensation diaphragm is fitted in the housing cover, then the lamp unit is a "closed system". Remedy Headlamp: Remedy 1 Clearing fogged/condensed LED headlamps: 1. Drive vehicle into workshop (temperature higher than +18 C/+64.4 F) and connect the exhaust extraction. Note: Do not perform an engine wash before the defogging test. 2. Switch off the engine and connect battery support via a charger. 3. Open the hood. 4. Switch on the lights. 5. Leave the vehicle in this state for 60 minutes. 6. Check for formation of condensation, a significant reduction in the formation of condensation must be clearly recognizable (thawing progress). Clearing of fogged/condensed LED headlamps and LED rear lamps on electric vehicles: 1. Drive the vehicle into the workshop (temperature higher than +18 C/+64.4F). 2. Connect battery backup via a charger. 3. Open the front-end flap and ensure sufficient ventilation. 4. Switch on the lights. 5. Leave the vehicle in this state for 60 minutes. 6. Check for formation of condensation, a significant reduction in the formation of condensation must be clearly recognizable (thawing progress). Clearing fogged/condensed halogen/xenon headlamps: 1. Drive the vehicle into the workshop (temperature higher than +18 C/+64.4F). Note: Do not perform an engine wash before the defogging test. 2. Switch off the engine. 3. Open the hood. 4. Switch off the lights. 5. Leave the vehicle in this state for 60 minutes. 6. Check for formation of condensation, a significant reduction in the formation of condensation must be clearly recognizable (thawing progress). Note: If there is no visible reduction in condensation, check the headlamp for malfunctions. (see Remedy 2) It is not physically possible to defog the headlamps completely. Fogging does not impair the operation or the service life of the headlamp. Note: Only implement Remedy 1 for model series 463 (from model year 2018) and model series 465. Remedy 2 A defective headlamp can be identified as follows: 1. Check the headlamp for external damage and that the cover caps and the diaphragm are correctly seated. 2. Check the electrical connectors of the plugs and pins. 3. Check for leak tightness according to LI82.10-P-078307. The test can only be conducted on headlamps. 4. If the headlamp or the rear lamp has any external damage, replace the component part in accordance with the WIS instructions. Note: External damage to the headlamp/rear lamp or faulty seating of the cover caps does not present a warranty or goodwill case. Note: With headlamps, it is possible to install desiccant packs if the problem occurs repeatedly. Open ventilation system LI82.10-P-078302 Closed ventilation system LI82.10-P-078304

occur under certain climatic conditions. It does not lead to any technical impairment of the headlamp. If a pressure compensation diaphragm is fitted in the housing cover, then the lamp unit is a "closed system". Remedy Headlamp: Remedy 1 Clearing fogged/condensed LED headlamps: 1. Drive vehicle into workshop (temperature higher than +18 C/+64.4 F) and connect the exhaust extraction. Note: Do not perform an engine wash before the defogging test. 2. Switch off the engine and connect battery support via a charger. 3. Open the hood. 4. Switch on the lights. 5. Leave the vehicle in this state for 60 minutes. 6. Check for formation of condensation, a significant reduction in the formation of condensation must be clearly recognizable (thawing progress). Clearing of fogged/condensed LED headlamps and LED rear lamps on electric vehicles: 1. Drive the vehicle into the workshop (temperature higher than +18 C/+64.4F). 2. Connect battery backup via a charger. 3. Open the front-end flap and ensure sufficient ventilation. 4. Switch on the lights. 5. Leave the vehicle in this state for 60 minutes. 6. Check for formation of condensation, a significant reduction in the formation of condensation must be clearly recognizable (thawing progress). Clearing fogged/condensed halogen/xenon headlamps: 1. Drive the vehicle into the workshop (temperature higher than +18 C/+64.4F). Note: Do not perform an engine wash before the defogging test. 2. Switch off the engine. 3. Open the hood. 4. Switch off the lights. 5. Leave the vehicle in this state for 60 minutes. 6. Check for formation of condensation, a significant reduction in the formation of condensation must be clearly recognizable (thawing progress). Note: If there is no visible reduction in condensation, check the headlamp for malfunctions. (see Remedy 2) It is not physically possible to defog the headlamps completely. Fogging does not impair the operation or the service life of the headlamp. Note: Only implement Remedy 1 for model series 463 (from model year 2018) and model series 465. Remedy 2 A defective headlamp can be identified as follows: 1. Check the headlamp for external damage and that the cover caps and the diaphragm are correctly seated. 2. Check the electrical connectors of the plugs and pins. 3. Check for leak tightness according to LI82.10-P-078307. The test can only be conducted on headlamps. 4. If the headlamp or the rear lamp has any external damage, replace the component part in accordance with the WIS instructions. Note: External damage to the headlamp/rear lamp or faulty seating of the cover caps does not present a warranty or goodwill case. Note: With headlamps, it is possible to install desiccant packs if the problem occurs repeatedly. Open ventilation system LI82.10-P-078302 Closed ventilation system LI82.10-P-078304

occur under certain climatic conditions. It does not lead to any technical impairment of the headlamp. If a pressure compensation diaphragm is fitted in the housing cover, then the lamp unit is a "closed system". Remedy Headlamp: Remedy 1 Clearing fogged/condensed LED headlamps: 1. Drive vehicle into workshop (temperature higher than +18 C/+64.4 F) and connect the exhaust extraction. Note: Do not perform an engine wash before the defogging test. 2. Switch off the engine and connect battery support via a charger. 3. Open the hood. 4. Switch on the lights. 5. Leave the vehicle in this state for 60 minutes. 6. Check for formation of condensation, a significant reduction in the formation of condensation must be clearly recognizable (thawing progress). Clearing of fogged/condensed LED headlamps and LED rear lamps on electric vehicles: 1. Drive the vehicle into the workshop (temperature higher than +18 C/+64.4F). 2. Connect battery backup via a charger. 3. Open the front-end flap and ensure sufficient ventilation. 4. Switch on the lights. 5. Leave the vehicle in this state for 60 minutes. 6. Check for formation of condensation, a significant reduction in the formation of condensation must be clearly recognizable (thawing progress). Clearing fogged/condensed halogen/xenon headlamps: 1. Drive the vehicle into the workshop (temperature higher than +18 C/+64.4F). Note: Do not perform an engine wash before the defogging test. 2. Switch off the engine. 3. Open the hood. 4. Switch off the lights. 5. Leave the vehicle in this state for 60 minutes. 6. Check for formation of condensation, a significant reduction in the formation of condensation must be clearly recognizable (thawing progress). Note: If there is no visible reduction in condensation, check the headlamp for malfunctions. (see Remedy 2) It is not physically possible to defog the headlamps completely. Fogging does not impair the operation or the service life of the headlamp. Remedy 2 A defective headlamp can be identified as follows: 1. Check the headlamp for external damage and that the cover caps and the diaphragm are correctly seated. 2. Check the electrical connectors of the plugs and pins. 3. Check for leak tightness according to LI82.10-P-078307. The test can only be conducted on headlamps. 4. If the headlamp or the rear lamp has any external damage, replace the component part in accordance with the WIS instructions. Note: External damage to the headlamp/rear lamp or faulty seating of the cover caps does not present a warranty or goodwill case. Note: With headlamps, it is possible to install desiccant packs if the problem occurs repeatedly. Open ventilation system LI82.10-P-078302 Closed ventilation system LI82.10-P-078304

-Engine runs rough. -Poor shifting or jerking when accelerating. -Fault codes stored related to mixture formation, injector quantity adjustment, or misfire. Note: One or more of the above symptoms can occur. It is possible that no fault codes are stored. Cause Leaking valve seat in cylinder head. Remedy -Perform cylinder leakage check as noted in WIS group 01.00. If excessive leakage is found determine if leak is from intake or exhaust valves. -If leakage is found from intake or exhaust valves, remove cylinder head and inspect valve seats. -The complete cylinder head must be replaced if valve seat damage is found. The valve seats can not be reworked. -Engine oil and filter should be changed after the repair. Workshop notes cylinder head repair: 1. The intake rocker arm roller is narrower than the exhaust and they must not be interchanged. Mark the rocker arms so they are reinstalled in their original location. 2. Inspect all parts that are being reused (i.e. camshafts, rocker arms) for signs of wear or damage. See WIS doc AH05.20-P-1000-09SZ for examples of normal and abnormal wear. Replace parts with new if damage or wear is found. 3. Check that all rocker arms are correctly located on the camshaft before installing cylinder head cover. Rotate engine at least 2 times and check that there are no problems with rocker arms. 4. The timing chain tensioner can be reused if it extends fully, has no noticeable problems in prior operation, and no chain drive components were replaced. 5. Care must be taken when removing fuel injectors to prevent damage. See WIS doc AR07.03-P-0004-03MM. 6. Cleanliness must be observed during repair to prevent subsequent complaint or engine damage: When cleaning engine block surface, ensure oil ports are sealed to prevent debris from entering oil circuit. Refer to SI01.40-P-0010A. No abrasive materials, sharp-edged tools, or unapproved cleaners should be used on engine block surface. Refer to AR01.00-P-0050-01A. Any debris from cleaning that has entered the cooling jacket should be removed before assembly of engine. The debris can otherwise cause blockage in the cooling circuit leading to engine overheating. If any of the parts listed below are found damaged or in need of replacement during cylinder head valveseat diagnosis or repair, and the vehicle has warranty coverage, they must be claimed on a separate partsonly line. These items are not covered under the cylinder head warranty extension and cannot be included with the claim. Camshafts Camshaft adjustment solenoids Camshaft positioners Fuel injectors Hydraulic valve play compensating elements Roller rocker arms Spark plugs Timing chain Timing chain guide rails Timing chain tensioner

"P0A7F00" stored in the 48 V battery G1/3 and/or is current. Remedy Update the 48V battery to SW 25/12 A0019020424 Then perform the following measures: - Switch on ignition - Read out actual value 209 in XENTRY Diagnosis for G1/3 (48 V battery) "State of Health Capacity-SOHC" -- If the value > 80% doesn't require a healing process -- If the value is < 80%, continue with the following steps Carry out capacity healing procedures: - Discharge 48 V battery in vehicle with ignition "On" and check the SOC of the 48 V battery in the workshop menu of the instrument cluster - At SOC <30%: Stop discharge and lock vehicle - with key out of range; (Bus idle) -Charging the 48V battery - When SOC reaches or exceeds 70%, stop charging and lock the vehicle with the key out of range; (bus idle) - After 1.5h bus idle: Switch on ignition Read out actual value 209 in XENTRY Diagnosis in the G1/3 (48 V battery) "State of Health Capacity-SOHC" - SOH > 90%: Procedure is finished and fault memory erased - SOH < 90%: Repeat the steps again. If the value is still too low after 5 repetitions: Abort healing process and open a TIPS case.

Cause In vehicles with Car Package Release "CPR" 2.1.0 or prior, the calibration value for the straightline stability of the electric power steering is not fully calibrated. Remedy Install Car Package Release 2.1.1 or later. Straightline normalization is then relearned during normal driving followed by a bus sleep. After the update, fault code P063544 may be active and stored in the electric power steering control unit, as the learned end stops are deleted during the update. This does not result in any functional limitations or warning messages; the end stops are learned during normal vehicle use. The fault code is cleared by automatic means after the teachin of the end stops is complete.

The switch lighting flashes at night/in the dark. The following fault codes are stored in the N135 steering wheel electronics control unit (LRE, SWSP174): B104404, B12A04A, and B1E9F96. Cause Hardware does not match standard specifications. Remedy Replace the N135 steering wheel electronics control unit (LRE, SWSP174).

There is an error in the data memory. Active and stored in the electric power steering control unit (N68) Cause The steering limitations of the electric power steering are not fully taught in. Remedy The steering limitations are taught in during normal vehicle use and the fault remains active and stored until the steering limitations have been taught in. The steering limitations can also be taught in manually: 1. Drive at >2 km/h, steer left or right to one of the steering limitations and hold the steering wheel there for at least 1 second. 2. Drive straight ahead at >30 km/h for at least 5 seconds 3. After another bus rest period (vehicle locked for at least 10 minutes and key out of range), the fault is stored and can be deleted.

See Example Noise attachment Cause The vehicle level of the front axle may be too low. The noises when steering can be caused by continuous contact of the end stop buffer with the damper tube. Remedy IMPORTANT: Do not apply document to vehicles outside of the listed validity range. The vehicle level must first be measured using the romess inclinometer (follow WIS instructions!) and the measured values should be compared with the target values in the Wheel Alignment online tool. If the vehicle level is out of tolerance, then the springs on the front axle must be replaced in order to correct the level. The currently installed springs can be pulled up in the XENTRY Parts Information tool through the corresponding selection. How to identify currently installed springs: Check for colored dots on the front springs. If no dots or color markings, please check if there is a parts label that is affixed to the spring. If the MB part number is listed, continue with process listed in the paragraph below. If the part label does not contain an MB part number, is missing or illegible, please check for a barcode label with a 3 digit number. See "Spring Barcode" picture for example. Open a TIPS case with this number and list that it is from the barcode attached to the currently installed spring. If none of the above references can be found, open a TIPS case. How to identify next spring in line with color dots: Navigate to the parts catalog and enter the vehicle VIN/FIN. Navigate to group 32 sub-group 054 (front spring strut) and find the spring. The spring listed in the parts catalog will have a "color marking" indicator. If the dots on the spring and the color listed in the parts catalog is the same then you have the part number of the currently installed spring. If it does not, then you need to clear the vehicle specific filter by using the funnel icon on the right side column of the page and clicking "no filter" at the top and then "apply filter" (see "Clear Vehicle EPC Filter" for how-to pictures). Proceed to finding the spring that matches the color dots on the vehicles currently installed spring. In order to find the correct or next highest spring, the spring filter must be removed in the XENTRY Parts Information tool. The spring item numbers are normally listed in sequence (observe and verify valid SA code for vehicle). The next strongest spring is selected by the ascending, next highest item number (Example: If the currently installed spring ends in "13 00" then then next spring in line is "14 00".) How to identify next spring in line with part number tag: Navigate to the parts catalog and enter the vehicle VIN/FIN and the part number found from the spring. In order to find the correct or next highest spring, the spring filter must be removed in the XENTRY Parts Information tool. To do this, you need to clear the filters by using the funnel icon on the right side column of the page and clicking "no filter" at the top and then "apply filter" (see "Clear Vehicle EPC Filter" for how-to pictures). The spring item numbers are normally listed in sequence (observe and verify valid SA code for vehicle). The next strongest spring is selected by the ascending, next highest item number (Example: If the currently installed spring ends in "13 00" then then next spring in line is "14 00".)

There is an error in the data memory. Active and stored in the electric power steering control unit (N68). Steering continues to operate without functional restrictions. Cause The steering limitations of the electric power steering are not fully taught in. Remedy The steering limitations are taught in during normal vehicle use and the fault remains active and stored until the steering limitations have been taught in. The steering limitations can also be taught in manually: 1. Drive at >2 km/h, steer left or right to one of the steering limitations and hold the steering wheel there for at least 1 second. 2. Then drive straight ahead at >30 km/h for a minimum of 5 seconds 3. After another bus rest period (vehicle locked for at least 10 minutes and key out of range), the fault is stored and can be deleted.

The noise is heard once in each instance when changing direction of travel. Note: Sound file in attachment Cause If the complaint is eliminated by experimentally loosening the outboard collar nut (by 1 turn), the problem is due to cracking of the microweld between the wheel bearing inner race and the joint housing of the side shaft. Note: The collar nut must always be replaced after being loosened. See also LI33.20-P-078406 Remedy Coat contact surface of side shaft with wheel bearing with Molykote paint. To do this, proceed as follows: 1. Remove side shafts 2. Clean contact surface A (see image file in attachment "Outer joint housing before") before coating with Molykote, using "spirit" (free of dust and grease) 3. Coat contact surface A (see image file in attachment "Outer joint housing after") with Molykote and leave to dry for "one hour" in removed condition 4. Reinstall side shafts Note: Before using the antifriction coating (Molykote), stir it or shake it thoroughly for (at least 1 minute).

squeaking, chattering, shuddering B: The windshield is not wiped completely (streaking) C: During the downward movement water is pulled back onto the windshield from the A-pillar (Figure 1) D: After windshield cleaning, water keeps spraying onto the windshield for several wipe cycles (Figure 2) A1: The windshield and wiper blades are contaminated with residues from car washing facilities, identifiable by the water beading. The resulting differences in the friction values between the wiper blades and the windshield can excite the wiper blades to vibrate. Note: It is mostly wax residue from the washer system, but also water-repellent nano-particle coating for paint and/or silicone-based washer fluid, that could cause this problem. A partially dry windshield also has different friction values, which can likewise result in squeaking of the wiper blades A2: The wiper blades are worn by mechanical damage (wiper lip damaged by ice or insect debris, or deformed by long periods of disuse). A3: Incorrect angle of incidence of the wiper arms to the windshield. Because of this, the rubber lip of the wiper blade may not flip over at the reversal point. Cause B: B1: Wax/ dirt residues on the windshield B2: Wiper blades deformed or worn B3: Downforce of wiper arm not OK (Figure 3) Cause C: Water is pulled back onto the windshield by the differential pressure created as the wiper arm moves downwards. Cause D: Washer water collects in the fastening of the wiper blade and is blown onto the windshield by the airstream over several wipe cycles. Note and supporting information: Wiper blades are wear parts which, even when "not used" for long periods (kept in park position), may become permanently deformed and damaged. Further stresses on the rubber wiper blade arise due to various environmental influences which progressively change the effectiveness of the rubber wiper blade and accelerate the aging process. Due to the natural aging process and wear, the wiper blades should be replaced twice a year, preferably in Spring and Fall (see operator's manual). Remedy Remedy A: A1: Cleaning entire windshield with A 000 986 40 71. A2: Checking water's flow behavior after windshield has been cleaned (see Video 1). If, after cleaning, there are still areas with water beading, then the cleaning process must be carried out again until a rejection reaction is no longer present. Note: On the vehicle in the video (Video 1), water still beads on the bottom left of the windshield. The windshield is still not properly clean, even though it appears to be clean. The windshield is only properly clean when there are no more areas on the windshield where water beads. A3: Replace wiper blades with genuine wiper blades. Important: Only exchange wiper blades if windshield no longer has water-repellent areas Note: Replacement of wiper blades is not covered under warranty and can be replaced at the expense of the customer. Remedy B: B1: Clean windshield with intensive cleaner A 000 986 40 71. Important: Do not clean the wiper blades otherwise the graphite coating will be damaged. B2: Replace wiper blades with genuine wiper blades Note: Replacement of wiper blades is not covered under warranty and can be replaced at the expense of the customer. B3: Check the wiper arm for excessive resistance in the bearing. Restore mobility or replace wiper arm if necessary. Remedy C: Problem inherent in design for which there is no technical remedy. Exception: X204 up to 02/2014. In these vehicles, it is possible to install the design configuration of vehicles as of 02/2014. This includes wiper arms (styled arms) with improved behavior in this respect. It is also necessary to replace the wiper blades because the styled arms feature a Top Lock connection (previously Side Lock).

Cause Most reported USB port issues are due to improper use or contamination. Note: Any repair costs must be discussed with the customer beforehand. Common external factors identified include: Fluid intrusion Broken bushings or physical damage See attachments. Remedy If a component needs replacement but shows no visible external damage, submit a detailed TIPS case only when technical support is required. Include details of all connected external devices (such as charging cables, USB drives, and hard drives). If diagnostic results directly indicate component replacement, a TIPS case is not necessary.

Cause Most reported USB port issues are due to improper use or contamination. Note: Any repair costs must be discussed with the customer beforehand. Common external factors identified include: Fluid intrusion Broken bushings or physical damage See attachments. Remedy If a component needs replacement without visible external damage, submit a detailed TIPS case. Include information on all connected external devices (e.g., charging cables, USB drives, hard drives).

Stored DTC Some known erroneous DTC's are: C1016E0 with error ID: SIG_ESP_71 B15BF00 with error ID: SIG_SEMA_C_22 U0420E2 with error ID: SYS_EPS_22 U041629 with error ID: SIG_ESP_12 U013187 U044229 Cause Software status of IDC_GEN6 In some cases, a diagnosis session or a software update may generate fault codes that do not cause any restrictions in customer operations. Remedy If: All driver assist functions operate without restrictions AND There are no persistent driver assist cluster messages (Example: white message for "Driver Assist Systems Inoperative") AND No persistently yellow driver assist cluster icons The DTC's may be ignored. If any of the above are true during PDI or after software update, please check LI54.71-P-080345 or open a TIPS case to the Body/Chassis/Entertainment inbox.

Stored DTC Some known erroneous DTC's are: C1016E0 with error ID: SIG_ESP_71 B15BF00 with error ID: SIG_SEMA_C_22 U0420E2 with error ID: SYS_EPS_22 U041629 with error ID: SIG_ESP_12 U013187 U044229 Cause Software status of IDC_GEN6 In some cases, a diagnosis session or a software update may generate fault codes that do not cause any restrictions in customer operations. Remedy If: All driver assist functions operate without restrictions AND There are no persistent driver assist cluster messages (Example: white message for "Driver Assist Systems Inoperative") AND No persistently yellow driver assist cluster icons The DTC's may be ignored. If any of the above are true during PDI or after software update, please check LI54.71-P-080315 or open a TIPS case to the Body/Chassis/Entertainment inbox.

Stored DTC Cause Software status of IDC_GEN6 In some cases, a diagnosis session or a software update may generate fault codes that do not cause any restrictions in customer operations. Remedy If: All driver assist functions operate without restrictions AND There are no persistent driver assist cluster messages (Example: white message for "Driver Assist Systems Inoperative") AND No persistently yellow driver assist cluster icons The DTC's may be ignored. If any of the above are true during PDI or after software update, please check LI54.71-P-080315 or open a TIPS case to the Body/Chassis/Entertainment inbox.

Stored DTC Cause Under determination. Remedy If: All functions operate as intended AND There are no persistent driver assist cluster messages (Example: white message for "Driver Assist Systems Inoperative") AND No persistently yellow driver assist cluster icons The DTC's may be ignored. If any of the above are true during PDI or after software update, please check LI54.71-P-080315 or open a TIPS case to the Body/Chassis/Entertainment inbox.

NOTE: Although the symptom is similar to a tire or wheel vibration, it is usually readily noticeable that it is distinctly different if it happens at all times or only while braking. Cause Although the cause of the vibration is most likely due to excessive lateral runout on the rotor or hub/wheel bearing, the system as a whole needs to be checked for other possible contributors. 1. Prior collision damage. 2. Excessive vehicle sitting times without rotating components. 3. Wheel bearing/hub lateral runout. 4. Wheel mating interface has been overtightened (did not follow WIS torque procedures). 5. Mating interfaces have been excessively modified (painted, gouged, bent, etc...). Remedy Read through the entire attached worksheet prior to performing. After performing, please review the final page and perform work accordingly. NOTE: This document is not preauthorization or otherwise dealing with warranty. This is intended for diagnostic purposes only. If there are any questions on how to proceed OR The work sheet has been performed and the vehicle has returned with the same concern. Please perform the measurements as seen in the worksheet again and open a TIPS case to the Body, Chassis, and Entertainment team.

AND Fault code C1100FC or C1100FD is Active or Active and Stored in MRR_F_Gen6 (B29/20). Cause The holder for the MRR_F_Gen6 (B29/20) front radar sensor may no longer have the correct alignment (angular position). Remedy Confirm whether the instrument cluster message was already present upon receipt of the vehicle by the end customer. Check if DTC mileage was present prior to vehicle PDI/Sale of vehicle. In this case, submit under warranty with the specified SSL. If vehicle exhibited the instrument cluster message AND DTC mileage was AFTER customer handover, cost settlement under warranty is not possible as it is due to outside damages. Note: Additionally, it is possible to obtain a timestamp for a possible collision, including the date, if the end customer has purchased the "Parking and Collision Alert" digital service. In both cases, the front radar holder must be replaced. After replacing the radar holder, perform calibration in IDC_Gen6 (N62/5).

warning lamps for various driver assistance systems. Examples include but are not limited to: Active Brake Assist Active Lane Keeping Assist Active Parking Assist Cause Software timing at startup. Remedy Conduct a seamless software update on the vehicle to at least MB.OS 1.3.0. Afterwards perform vehicle bus sleep (vehicle locked for at least 10 minutes and key out of range).

Cause Many possible root causes Remedy *Note - This Li does not apply if there are other Li's that apply to your concern OR you have a fault and/or guided test that leads to a root cause. AC Diagnosis (General) Initial Steps Verify Customer Concern Confirm the issue reported by the customer. Compare to Like Vehicle Determine if the behavior is normal by comparing with a similar vehicle. Determine Your Game and Players Identify the diagnostic strategy and involved components/systems. Testing Perform relevant diagnostic tests. Refrigerant Quantity Record the amount of refrigerant recovered and compare it to the specified value (if applicable). Forming Gas is the ONLY approved leak test method. (DYE is NOT approved) TIPS Case Submission Requirements/Warranty Claim Submission Requirements (Template attached to be used for submission of Warranty claim and/or TIPS case) Cooling Capacity Test (If System Has a Charge) *Note - TIPS case is only required if the root cause is not identified or other Li's/documents require a case to be open. Before Repairs Gauge Readings High and Low pressure readings (from machine or separate gauges). Leak Detection (if applicable) PPM of any leaks found. XENTRY Printouts Climate control AVs. HV compressor AVs (for heat and AC systems). Thermometer Readings Left and right dash vents. Center vent, footwell, and/or rear vents (if concern is localized). Ambient Conditions Temperature and humidity from OCP AVs (if available). After Repairs Gauge Readings High and Low pressure readings before and after repairs. Thermometer Readings Left and right dash vents before and after. Center vent, footwell, and/or rear vents before and after (if localized concern). Documentation Complaint Analysis, Game/Players, and Testing Steps. Include expected results and technical justification for the diagnosis. Avoid listing R/I stepsfocus on diagnostic reasoning and root cause. All prior measurements need to be documented on the repair order. OP code usage: 831232 - Max .5 for Cooling Capacity Test 831040 - Only to be utilized if you have a fault code and are actively diagnosing that fault code (MAX 1 hour) 831762 - This includes basic leak check 831285 - This can only be used in extenuating circumstances where a leak cannot be found (MAX 1 hour)

Cause Many possible root causes Remedy AC Diagnosis (General) Initial Steps Verify Customer Concern Confirm the issue reported by the customer. Compare to Like Vehicle Determine if the behavior is normal by comparing with a similar vehicle. Determine Your Game and Players Identify the diagnostic strategy and involved components/systems. Testing Perform relevant diagnostic tests. Refrigerant Quantity Record the amount of refrigerant recovered and compare it to the specified value (if applicable). Forming Gas is the ONLY approved leak test method. (DYE is NOT approved) TIPS Case Submission Requirements/Warranty Claim Submission Requirements Cooling Capacity Test (If System Has a Charge) *Note - TIPS case is only required if the root cause is not identified or other Li's/documents require a case to be open. Before Repairs Gauge Readings High and Low pressure readings (from machine or separate gauges). Leak Detection (if applicable) PPM of any leaks found. XENTRY Printouts Climate control AVs. HV compressor AVs (for heat and AC systems). Thermometer Readings Left and right dash vents. Center vent, footwell, and/or rear vents (if concern is localized). Ambient Conditions Temperature and humidity from OCP AVs (if available). After Repairs Gauge Readings High and Low pressure readings before and after repairs. Thermometer Readings Left and right dash vents before and after. Center vent, footwell, and/or rear vents before and after (if localized concern). Documentation Complaint Analysis, Game/Players, and Testing Steps. Include expected results and technical justification for the diagnosis. Avoid listing R/I stepsfocus on diagnostic reasoning and root cause. All prior measurements need to be documented on the repair order. OP code usage: 831232 - Max .5 for Cooling Capacity Test 831040 - Only to be utilized if you have a fault code and are actively diagnosing that fault code (MAX 1 hour) 831762 - This includes basic leak check 831285 - This can only be used in extenuating circumstances where a leak cannot be found (MAX 1 hour)

Cause Many possible root causes Remedy AC Diagnosis (General) Initial Steps Verify Customer Concern Confirm the issue reported by the customer. Compare to Like Vehicle Determine if the behavior is normal by comparing with a similar vehicle. Determine Your Game and Players Identify the diagnostic strategy and involved components/systems. Testing Perform relevant diagnostic tests. Refrigerant Quantity Record the amount of refrigerant recovered and compare it to the specified value (if applicable). Forming Gas is the ONLY approved leak test method. (DYE is NOT approved) TIPS Case Submission Requirements Cooling Capacity Test (If System Has a Charge) Before Repairs Gauge Readings High and Low pressure readings (from machine or separate gauges). Leak Detection (if applicable) PPM of any leaks found. XENTRY Printouts Climate control AVs. HV compressor AVs (for heat and AC systems). Thermometer Readings Left and right dash vents. Center vent, footwell, and/or rear vents (if concern is localized). Ambient Conditions Temperature and humidity from OCP AVs (if available). After Repairs - Warranty Submission Requirements on the Repair Order Gauge Readings High and Low pressure readings before and after repairs. Thermometer Readings Left and right dash vents before and after. Center vent, footwell, and/or rear vents before and after (if localized concern). Documentation Complaint Analysis, Game/Players, and Testing Steps. Include expected results and technical justification for the diagnosis. Avoid listing R/I stepsfocus on diagnostic reasoning and root cause. All prior measurements need to be documented on the repair order. OP code usage: 831232 - Max .5 for Cooling Capacity Test 831040 - Only to be utilized if you have a fault code and are actively diagnosing that fault code 831762 - This includes basic leak check 831285 - This can only be used in extenuating circumstances where a leak cannot be found

This sound may occur under the following conditions: Driving over uneven or rough road surfaces During cornering / vehicle body movement When there is movement or load shift in the seat base. Cause Insufficient lubrication of components within the seat height adjustment mechanism Remedy Replace the seat height adjuster assembly

or Squeaking noise when steering quickly around the center position Cause Variation in the steering gear due to manufacturing tolerances. Remedy 1. Check the vehicle's MB.OS software release with Xentry and update if necessary. 2. Connect Xentry, switch on the ignition (vehicle not roadworthy and power steering off), and raise the vehicle so that the wheels are not loaded. 3. Navigate to control unit N80, Steering Column Switch Module, actual values tab, and locate "Steering Angle". 4. Turn the steering wheel to full lock left until the mechanical end stop of the steering is reached. Record the steering wheel angle. 5. Perform a full lock to the right until the mechanical end stop is reached. Record the steering wheel angle. 6. Depending on whether the positive or negative value is greater, reposition the steering wheel by one tooth in the relevant direction (refer to AR46.10-P-0100CLA). Positive value is greater => Shift steering wheel one tooth to the right (clockwise) Negative value is greater Shift steering wheel one tooth to the left (counterclockwise) Example steering angle: 450 and -462 => Move the steering wheel one tooth to the left. 7. Perform a wheel alignment. Pay particular attention to adjusting the toe values accordingly. 8. Reset the straight-ahead learned value with XENTRY in the N68 electric power steering control unit. 9. Perform bus sleep (lock the vehicle, keep the key out of range, and leave it locked for at least 15 minutes). 10. Perform a test drive and re-assess. If, after the subsequent test drive, any of the previously mentioned problems persist, please create a TIPS case to the Body/Chassis/Entertainment team.

existing stock must be returned to your facing PDC. The deadline for all dealer returns is no later than Thursday, August 13th, 2026. After August 13th, returns of these parts will no longer be accepted. These parts should be returned via ZSR Special Return, using item category SCM Authorized Part Return. Please include a copy of this NCU as your authorization to return these parts. This procedure will not affect your return allowance. All returned parts will be replaced in accordance with the chart provided below.

After updating the CPR to 1.3.7, a coding mismatch is occurring between the CIVIC174 & IDC control units causing a driver assistance msg in the cluster. We are currently working diligently toward a solution. If you need support, please create an XSS Diagnosis case with necessary ID1 support package and we are happy to support. Thank you for your patience.