ELECTRICAL SYSTEM:PROPULSION SYSTEM
2025 Mercedes-Benz AMG SL63 S E
Recalls, owner-reported complaints, investigations and safety data
Overview
Our database contains no NHTSA owner-reported complaints for the 2025 Mercedes-Benz AMG SL63 S E. 1 safety recall has been issued covering this model year; and 111 manufacturer communications are on file.
Complaints are reports submitted by owners and drivers to NHTSA. They are not verified and do not establish that a defect exists.
Safety recalls
1 campaign cover this model year
Recalls apply to specific vehicles, not to every vehicle of a model year. Check your VIN with NHTSA or your manufacturer's dealer to confirm whether a recall affects your vehicle.
Check a VIN on NHTSA.govRecent owner complaints
Reports submitted to NHTSA, shown in the owner's own words
No owner complaints recorded for this model year
Either none have been filed with NHTSA, or this vehicle is too new for reports to have accumulated.
Manufacturer communications
A bulletin sent by a manufacturer to its dealers. Not a recall, and repairs are not necessarily free.
STEERING
Complaint During part of the steering movement, it feels heavier or more difficult to steer in the same spot every time. OR Rattling, humming, dry sliding/gravel noise from the electric steering system when steering (see attachment). Complaint does not impact the ability to safely steer or control the vehicle. Cause Ball screw drive (KGT) of electric steering damaged by: 1. External force due to: ‑ Hitting the curb/posts with the front wheels. ‑ Driving over obstacles (e.g. pothole/ threshold/ speed bump/ gully) at an inappropriate speed. 2. Corrosion/ water ingress through a damaged boot (see attachment). ‑ Cracks (1) ‑ High pressure cleaner (2) ‑ Animal bite (3) See various examples listed in the attachments for examples of outside influence. Remedy Remove boot clamps closest to steering gear housing on both left and right (as seen in "Steering Rack Boot Clamp Location"). Pull back boot and inspect for rust, broken end stops, water, or any other anomalies. Replace electric steering. Note: Steering gears replaced due to outside influence or damage must not be claimed under warranty!
POWER TRAIN
Complaint • Harsh 1‑2, 2‑3, and/or 3‑4 shift • Jerky shifting • Jolting when accelerating from stop Cause Insufficient software application causing elevated K81/K27/B05 fill time adaptations and elevated torque adaptations for concerning shift. Note: Shift quality in E Performance models can be affected if the HV Battery state of charge (SOC) reaches 25% or below. Remedy Check VGS software level, and follow relevant remedy instructions. (see attachment) AMG 43 models with VGS software levels up to 22A: As of 4/18/2025, an aftersales software improvement has been released. This software has been implemented in production as of model year 2024, however this LI should still be followed if the concern is present. 232 ‑ A0009025699 206 ‑ A0009025599 Please ensure your Xentry machine is up to date with the latest Add Ons and continue with the following steps: Note: ALL steps must be performed to rectify concern 1. Perform software update all control units included in VGS software update. 2. Check transmission oil level and correct, if necessary (transmission oil temperature > 60 °C) 3. Perform Xentry Valve Flushing procedure at least 3x 4. Perform resetting of deceleration values (VGS > Special Procedures > Special procedure > Resetting learned values Deceleration mode) 5. Perform a standstill adaptation, then read out new EEPROM data 6. Perform driving adaptation(s) while adhering to the below parameters for at least 20‑30 miles. Note: There is no menu in Xentry for this procedure. We recommend displaying the torque in the instrument cluster. If all below parameters are met at the time the shift, a driving adaptation will automatically occur. Harsh 1‑2 Perform a driving adaptation of 4‑5 (adapts K81 for the 1‑2 shift) Harsh 2‑3 Perform a driving adaptation of 6‑7 (adapts B05 for the 2‑3 shift) Harsh 3‑4 Perform a driving adaptation of 3‑4 (adapts K27 directly) ‑ See attached PDF for min/max torque, and RPM parameters ‑ Transmission oil temperature > 30°C (>86°F) ‑ Level track (no incline/decline) ‑ Slippery drive program ‑ Display the torque in the instrument cluster ‑ Constant engine torque ‑ Do not shift via paddle AMG 63 models with VGS software levels up to 22A: No aftersales software resolution is planned. Perform above steps and release the vehicle. If the vehicle returns and already had ALL steps in this LI performed on a previous visit, or has software level 23A and newer: Please submit a TIPS case to the Powertrain inbox and ensure the following is included: ‑ Initial Quick Test w/ Freeze Frame Data ‑ VGS Control Unit Log ‑ Initial EEPROM (before any adaptations or Xentry procedures were performed) ‑ Detailed vehicle history of the complaint
ELECTRICAL SYSTEM
Complaint Traffic sign symbol for "Traffic Sign Assist" is blinking in instrument cluster without obvious cause usually with one of the following scenarios: • Flashing without a speed limit ("‑ ‑"). • Flashing when current vehicle speed is under speed limit. • Flashing between US speed limit symbol and European speed limit symbol. NOTE: • Verify that the concern falls under one of the attachment videos. If not, then it is outside of the scope of this LI. • This also does not cover "Traffic Sign Inoperative" messages on the instrument cluster. Cause There are two identified reasons for this concern: 1. Country code information stored incorrectly at a particular geographic latitude range. 2. Incorrect reference data when the vehicle is started and a GPS signal is not immediately available. Remedy Update head unit software to latest version and the re‑check function in the same location. If vehicle is still exhibiting one of the symptoms as described exactly as in the complaint section or as shown in the video attachments, open a TIPS case to the Body/Chassis/Entertainment inbox with the following: • Video of the concern. • Exact location (latitude and longitude is best)
ELECTRICAL SYSTEM
Complaint The following most common complaints may be observed: • Brief connectivity interruptions when using Apple CarPlay over Wi-Fi • Audio cuts out • Device not recognized • No operation possible Cause There are multiple possible causes for an iPhone disconnecting from a vehicle’s head unit while using Apple CarPlay. These include hardware, software, and environmental factors: Environmental Interference External Sources: • Passing under toll bridges, driving near airports, or areas with heavy electronic interference (e.g., as described in LI82.85-P-076157) can cause connection drops. Cellular Networks: • Interference from nearby cell towers operating on similar frequencies (usually 2.4GHz or 5GHz) can disrupt the signal. Storage Location: • Keeping your phone in a handbag or surrounded by other objects inside the vehicle can create physical or electronic interference. Device and Software Issues Head Unit Software/Hardware: • Outdated firmware, bugs, or hardware faults in the vehicle’s head unit can prevent a stable connection. iPhone Software/Hardware: • Similar issues in the iPhone, including buggy iOS updates or hardware problems, may affect performance. Reset or Reboot:• Automatic rebooting or resetting of either the head unit or the iPhone will temporarily disrupt CarPlay. Connection and Settings Wired Connections: • Faulty Cable: A damaged or poor-quality USB cable can cause intermittent or total loss of connection. • USB Port Issues: Dust, debris, or physical damage in the USB port of either the head unit or the iPhone can also lead to disconnects. Wireless Connections: • Intermittent Bluetooth/Wi-Fi: Unstable wireless communication (Bluetooth/Wi-Fi) can frequently break the Car- Play connection. Power Management: • Battery Saver Mode: Enabling low power mode may restrict background processes, affecting CarPlay. • Vehicle’s Electrical System: Unstable power delivery from the car’s battery or electrical interruptions can cause the head unit to malfunction. Phone & App Configuration Phone Settings: • Incorrect or conflicting settings (especially Bluetooth or Wi-Fi) on your iPhone can interfere with the CarPlay link. • Third-Party Apps/Profiles: • Installed apps or configuration profiles may conflict with CarPlay’s operation. • Native apps are apple maps, apple music, audio books, apple news, podcasts, messages and phone. All other apps are considered third party apps. App Conflicts: • Running conflicting apps that require similar system resources as CarPlay can cause instability. Mobile Data Plan: • Streaming from online sources without sufficient mobile data can result in lost connectivity. Other Factors Heat & Overheating: • If either the phone or the head unit overheats, they may disable certain functions to prevent damage, leading to disconnection. User Actions: • Accidentally disconnecting the device in settings, or physically moving or bumping the phone or cable, may disrupt the connection. Remedy FUP6 (E605.8) software has been released for the following chassis: 118, 177, 243,247,206,254,167,294,295,296,223, 297. Flash available software for the head unit and test for function. The LI will be updated once available for the remaining chassis. If the complaint remains after the SW update please continue with the steps below. Guided Diagnostic Path for Apple CarPlay Connection Issues: Please follow the steps below to systematically diagnose and resolve CarPlay concerns:Update Devices: • Ensure the iPhone is updated to the latest available iOS version. • Ensure the vehicle’s head unit is updated to the latest software version available. Isolate the Issue: • Check whether the symptom persists with another iPhone running the latest iOS version. • Test both wireless and wired CarPlay connections: • Does the issue only occur with wireless CarPlay? • Does the wired connection to the phone function correctly? Further Troubleshooting Steps: • Reboot the iPhone. See attachment for further instructions.
ELECTRICAL SYSTEM
Complaint Customer Complaint: - AC charging is not possible. - The departure time, charging pause, location-based charging or target SOC limit is automatically set to 50% or to a random value in the Mercedes me application or in the charging settings on the head unit display. (Picture 1 & 3) - Incorrect notifications appear in the Mercedes me application for charging-related functions. (Picture 2) Related DTCs in quick test: No related fault codes (DTCs) are stored in the relevant control units. CPC3 - N127 (Drivetrain control unit) OBL223_GEN4 - N83/11 (Alternating current charger for high-voltage battery) DCB223 - N116/5 - Direct current charge connection unit (DCCU) Picture1 The target SOC limit is automatically set to 50% or any random values during charging. Picture 2 Incorrect notification Example “Unable to unlock charging cable. Picture 3 Incorrect settings of charge interruption or pause. (If applicable) Cause - The Customer shares their Mercedes me credentials (password) with a third-party application, for example, a wall box application. This causes the Mercedes Benz backend server to receive random requests to reset the maximum SOC, departure time, charging pause, etc. - Charging settings are set incorrectly, for example, incorrect departure time, charging program, charging interruption/ pause, etc. Remedy The remedies below may vary depending on the customer complaint. Refer to the remedy that best matches the customer complaint. Remedy 1: The target SOC limit is automatically set to 50% or to random values during charging. - Change the Mercedes me login password on the Mercedes me homepage. (My Account > Login and Security > Reset). (Refer to Annex 1). Previously granted authorizations should then be revoked so that the charging settings can no longer be changed by external applications. Advise customers not to share the new password again. - Are there any sub-users? If yes, revoke their rights and reassess the function. -If differences between the vehicle and the Mercedes me app are visible, a new synchronization is recommended. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. Remedy 2: Incorrect notifications in the Mercedes me app for charging-related functions. - Restart synchronization between the app and backend. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. (Refer to Annex 2) Remedy 3: Incorrect charge interruption or pause setting. - Perform a factory reset of the head unit (A26/17). (Home > Functions > System > Reset), or turn off/correct all charging settings. (Refer to Annex 3) Additional Information: (Good to know) The LED on the charging inlet or socket indicates whether charging is completed or paused. 1) If the target SOC is reached, the charging inlet LED lights up Blue/Green without flashing. 2) If charging is paused, the charging inlet LED lights up orange without flashing. Additionally, the head unit charging settings display a charging pause. Note: Do not replace any hardware components for these complaints. If the complaint cannot be solved, please contact via TIPS or CAC.
ELECTRICAL SYSTEM
Complaint 1. General Diagnostic Tips 2. 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.
Manufacturers file copies of the bulletins they send to dealers with NHTSA. These often describe diagnostic or repair procedures for a known condition. They are not recalls: repairs described in a bulletin are usually only free if the vehicle is still under warranty or the manufacturer has extended coverage.
Compare model years
Complaint and recall counts across every year of this model
| Year | Complaints | Recalls | Investigations | Issue Index |
|---|---|---|---|---|
| 2025Viewing | 0 | 1 | 0 | — |
| 2024 | 0 | 2 | 0 | — |
Higher-selling and older vehicles accumulate more reports. Counts are not failure rates and are not directly comparable between vehicles that sold in very different numbers. Older model years have had longer for reports to accumulate.