I received a recall notice for this vehicle stating that the wheels may not be safely attached and could come off back in early May. It's been over a month and Mercedes has no solution for the recall at this time. I'm looking to get help with not having to pay my lease since I cannot use the car safely.

While driving at around 35mph, the recently-installed rear left snow tire on the car popped off and was propelled several hundred feet down the road.  Upon reviewing the recall information of the car, it seems likely the indicent was caused by defective wheel bolts.

Complaint USB port not functioning properly. 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.

Complaint USB port not functioning properly. 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).

Complaint At low speeds and light brake pressure, brakes will make a groaning or honking noise. Cause Frictional vibrations with very light brake pressure/modulations. Remedy This condition can be duplicated on most vehicles. To validate, use a like for like reference vehicle. The noise is normal behavior under the conditions listed. With very light brake pressure this noise can be induced/caused due to normal brake pad and brake rotor vibrations. Exchanging brake components will not rectify.

Complaint Noise interference occurs during hands-free phone calls. Cause The interference is due to electromagnetic compatibility (EMC) faults affecting the microphone wiring. This disrupts signal integrity and degrades voice quality. Severity may vary by vehicle configuration. Remedy A corrective measure involving modified wiring harnesses and revised microphone connections is in development. The updated solution is scheduled for release in December 2025. Once the measure is implemented, this bulletin will be updated and versioned accordingly.

Complaint Clanking noise from the area of the speakers in the doors. 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.

Complaint The result from the XENTRY battery test does not match the current state of the battery. 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. 

Complaint 243: Red 12V battery message, white HV warning message, warning message in the IC and if applicable for vehicles with BMS30EB02 yellow HV drive system 465: Red 12V battery message, white HV warning message, warning message in the IC If the initial warning messages are ignored in the same ignition cycle, additional warning messages, e.g. red HV warning message and yellow HV drive system warning message may be shown. The DC/DC converter has stored a combination of the following two fault code groups: 1. P0C3B00, P0E9700, P0E5400, P0C4000. 2. P1D0B00, P1CA000, U011500. In some cases, not all DTCs from one of these groups are triggered. 243: As a consequence, on vehicles with BMS30EB02, the DTC for the auxiliary assembly fuse P0E2F00 can be set. This triggers the yellow HV drive system warning message.  In the ignition cycle in which the red 12 V fault message is displayed, the DC/DC converter does not support the 12 V on-board electrical system. This means the 12 V battery may be discharged in the event of longer use. Cause In individual ignition cycles, this may result in faulty wake-up behavior of the DC/DC converter. The DCDC DTCs and warning messages may appear with a time delay. When accessing the vehicle, the white (243/465) HV warning message is displayed. When the HV system is switched on (charging, 12V supports, precon, ignition on), the yellow HV drive system warning message is displayed on the 243 with BMS30EB02 (see below for details). When the vehicle is started/PT-ready (displayed in the IC), the red 12V battery warning message is displayed for 243 and 465. Since the BMS on 243 uses the HV voltage value to check the auxiliary assembly fuse, the auxiliary assembly DTC can (with BMS30EB02) be stored as a consequence and the second (yellow) HV drive system warning message can be displayed in the IC. Remedy The faulty state of the DC/DC converter can always be rectified with an ignition change with BUS idle. The fact that the red 12 V warning message does not appear again is an indication of this. On vehicles with the yellow hybrid drive system message, it is still displayed because it is not automatically reset once the faulty state is reset. Check the DC/DC converter for functionality via Xentry Diagnostics in the workshop: • Actuate BUCK mode for approx. 30 s • The output current normally jumps to a high value (e.g. 100 A) and then falls slowly to the current specified value e.g. 50 A and then only changes slowly and in small increments. 243 EB311/312 (BMS30EB01): Perform reset of the DC/DC converter, e.g. through a BUS idle or by clearing the fault memory, to exit the faulty state.  243 EB330 (BMS30EB02): Clear the fault memory, since the DTC for the auxiliary assembly fuse and the yellow hybrid drive system warning message are not automatically reset. 465: Perform reset of the DC/DC converter, e.g. through a BUS idle or by clearing the fault memory, to exit the faulty state. !!! Important note: Problems in this area do not have to be invoiced on the damage code for the DC/DC converter 54720. !!! Information: Cause analysis is still ongoing in order to determine a long-term remedy.  In cases in which the fault profile occurs multiple times, replacement of the DC/DC converter can be carried out. This may help delay the fault profile from reoccurring.

Complaint: 243: Red 12V battery message, white HV warning message, warning message in the IC ​​and if applicable for vehicles with BMS30EB02 yellow HV drive system 465: Red 12V battery message, white HV warning message, warning message in the IC If the initial warning messages are ignored, additional further warning messages (e.g. red HV warning message and yellow HV drive system warning message) are displayed. The DC/DC converter has saved the four following fault codes at most: P0C3B00, P0E9700, P0E5400, P0C4000. In some cases, not all of these DTCs are triggered. The following DTCs either be triggered additionally or, in rare cases, without the previous DTCs: P1D0B00, P1CA000, U011500. 243: As a consequence, on vehicles with BMS30EB02, the DTC for the auxiliary assembly fuse P0E2F00 can be set. That triggers the yellow HV drive system warning message. Cause: This may result in incorrect wake-up behavior of the DC/DC converter. The DCDC DTCs and warning messages may appear with a time delay. When accessing the vehicle, the white (243/465) HV warning message is displayed. When the HV system is switched on (charging, 12V supports, precon, ignition on), the yellow HV drive system warning message is displayed on the 243 with BMS30EB02 (see below for details). When the vehicle is started/PT-ready (displayed in the IC), the red 12V battery warning message is displayed for 243 and 465. Since the BMS on 243 uses the HV voltage value to check the auxiliary assembly fuse, the auxiliary assembly DTC can (with BMS30EB02) be stored and the second (yellow) HV drive system warning message can be displayed in the IC. Remedy: Check of the DC/DC converter via XENTRY Diagnosis Actuate BUCK mode for approx. 30 s The output current normally jumps to a high value (e.g. 100 A) and then falls slowly to the current specified value e.g. 50 A and then only changes slowly and in small increments. 243 EB330 (BMS30EB02): Clear the fault memory, since the DTC for the auxiliary assembly fuse and the yellow hybrid drive system warning message can only be reset in this way. 465: Perform a reset of the DC/DC converter, e.g. through a BUS idle or by clearing the fault memory, to exit the error state. Information: Cause analysis is still ongoing in order to determine a long-term remedy. In cases in which the fault profile occurs multiple times, please open a TIPS case.

Complaint: 243: Red 12V battery message, white HV warning message, warning message in the IC ​​and if applicable for vehicles with BMS30EB02 yellow HV drive system 465: Red 12V battery message, white HV warning message, warning message in the IC If the initial warning messages are ignored, additional further warning messages (e.g. red HV warning message and yellow HV drive system warning message) are displayed. The DC/DC converter has saved the four following fault codes at most: P0C3B00, P0E9700, P0E5400, P0C4000. In some cases, not all of these DTCs are triggered. The following DTCs either be triggered additionally or, in rare cases, without the previous DTCs: P1D0B00, P1CA000, U011500. 243: As a consequence, on vehicles with BMS30EB02, the DTC for the auxiliary assembly fuse P0E2F00 can be set. That triggers the yellow HV drive system warning message. Cause: This may result in incorrect wake-up behavior of the DC/DC converter. The DCDC DTCs and warning messages may appear with a time delay. When accessing the vehicle, the white (243/465) HV warning message is displayed. When the HV system is switched on (charging, 12V supports, precon, ignition on), the yellow HV drive system warning message is displayed on the 243 with BMS30EB02 (see below for details). When the vehicle is started/PT-ready (displayed in the IC), the red 12V battery warning message is displayed for 243 and 465. Since the BMS on 243 uses the HV voltage value to check the auxiliary assembly fuse, the auxiliary assembly DTC can (with BMS30EB02) be stored and the second (yellow) HV drive system warning message can be displayed in the IC. Remedy: Check of the DC/DC converter via XENTRY Diagnosis Actuate BUCK mode for approx. 30 s The output current normally jumps to a high value (e.g. 100 A) and then falls slowly to the current specified value e.g. 50 A and then only changes slowly and in small increments. 243 EB330 (BMS30EB02):Clear the fault memory, since the DTC for the auxiliary assembly fuse and the yellow hybrid drive system warning message can only be reset in this way. 465:Perform a reset of the DC/DC converter, e.g. through a BUS idle or by clearing the fault memory, to exit the error state. Information: Cause analysis is still ongoing in order to determine a long-term remedy. In cases in which the fault profile occurs multiple times, please open a TIPS case.

1. Connect XENTRY Diagnosis. 2. Update Battery management system (BMS) control unit software. To do this, select menu item Quick test view → N82/9 – Battery management system (BMS) → Adaptations → Control unit update → Updating of control unit software. Follow the user guidance in XENTRY Diagnosis. Then update the following list of control units in the sequence given below: a) (A26/17) MBUX multimedia system (Head Unit) b) (B29/13) Left rear short-range radar (NBR-LR) c) (N162) Ambiance light (AML) d) (N156/1) Active driving sound compensation (ASX7) e) (A40/11) Multifunction camera (MFK) f) (N32/1) Electrical seat adjustment ‘Driver’ with memory function (ESA ‘Driver’) g) (N32/2) Electrical seat adjustment ‘Front passenger’ with memory function (ESA ‘Front passenger’) h) (N51/8) ADS (Adaptive damping system) i) (N2/10) Supplemental Restraint System (SRS) After the software updates have been completed, SCN coding must be performed for the following control units in the sequence given below: 3. Perform SCN coding in the AC charger for high-voltage battery (SG-LG) control unit. To do so, select menu item Quick test view → N83/11 - AC charger for high-voltage battery (SG-LG) → Adaptations → Control unit update → Updating of SCN coding”. Then follow the user guidance in XENTRY Diagnosis. Update the following list of control units in the same way. a) (N10/6) Front signal acquisition and actuation module (Driver-side SAM) b) (N10/8) Rear signal acquisition and actuation module (Rear SAM) c) (N179) Hand detection system (HE) d) (N62) Parking system (PARK) 4. Disconnect XENTRY Diagnosis.

Mercedes-Benz G580

Filing history

Reported severity

Top reported issues — Mercedes-Benz G580

Recent filings