Inside Mercedes-Benz MB.OS: Architecture, GLB (X244) Versioning, Workshop OTW Flashing & Recall 5496906

With the launch of its latest electric vehicle lineup, Mercedes-Benz has executed the most ambitious architectural transformation in its modern history: transitioning from fragmented, supplier-driven Electronic Control Units (ECUs) to a proprietary, vertically integrated Software-Defined Vehicle (SDV) platform powered by MB.OS (MBOS_VERSION_1_0).

Rolled out across the new CLA, GLB (chassis X244), and GLC with EQ Technology, MB.OS pairs an 800 V electric powertrain architecture with a high-speed zonal computing network (STAR3_5). Yet as early adopters have quickly discovered, owning a software-defined Mercedes-Benz is a very different experience from owning a Tesla. While newly manufactured cars roll off the assembly line with the latest 2.1.x software branch, vehicles delivered just months earlier remain anchored to factory Long-Term Support (LTS) baselines unless owners wait for staged Over-The-Air (OTA) waves—or undergo a multi-day Over-The-Wire (OTW) flashing marathon to 2.1.3 at an official dealership workshop.

Here is the complete technical breakdown of the MB.OS 1.0 architecture, the full GLB EQ (X244) version history up to MB.OS 2.1.6, what actually happens inside the workshop bay during a manual XENTRY OTW upgrade, and details on the DGT / Mercedes-Benz 5496906 eCall safety recall currently underway in Spain.

---

1. The MB.OS 1.0 Platform: CLA, GLB, and GLC with EQ Technology

Historically, legacy automakers built vehicles by stitching together dozens of black-box ECUs from Tier-1 suppliers, each running incompatible firmware. MB.OS 1.0 replaces that patchwork with a unified chip-to-cloud architecture running over the STAR3_5 zonal electronic network and high-speed Automotive Ethernet.

The 800 V Vehicle Lineup

Mercedes-Benz is deploying MB.OS across its core electric-first architectures (MMA — Mercedes Modular Architecture — and MB.EA):

• Mercedes-Benz CLA with EQ Technology: The digital vanguard of the MMA platform, introducing the ultra-efficient 800 V electric drive unit (EDU 2.0), Silicon Carbide (SiC) inverter, two-speed transmission, and the debut implementation of MB.OS 1.0.
• Mercedes-Benz GLB with EQ Technology (Chassis X244): The compact-to-midsize family electric SUV (distinct from the combustion/mild-hybrid X248 chassis). Available as the GLB 200 (58 kWh LFP battery), GLB 250+ (85 kWh usable / 90 kWh gross NMC battery, 200 kW / 272 PS RWD, up to 632 km WLTP), and GLB 350 4MATIC (85 kWh NMC, dual-motor AWD). Its 800 V architecture supports 320 kW DC ultra-fast charging (10–80% SoC in 18 minutes).
• Mercedes-Benz GLC with EQ Technology: The high-volume midsize luxury electric SUV that scales the MB.OS software stack, 800 V ultra-fast charging, and seamless MBUX Superscreen/Hyperscreen integration into the brand’s core global SUV segment.

The Four Core Domains of MB.OS

As illustrated in the system architecture diagram below, MB.OS decouples hardware from software by organizing the vehicle into four independent functional domains, linked to the Mercedes-Benz Intelligent Cloud through the ARTEMIS 5G Telematics Control Unit (TCU, SA-370):

1. Infotainment (MBUX & Cabin Digital): Powered by the GEN20XI3 central head unit driving the MBUX Superscreen (SA-860), Zero Layer interface, generative-AI MBUX Virtual Assistant, 3D Surround Navigation, interior selfie/facial recognition camera (SA-46U), Burmester® 3D surround sound (SA-810), and native third-party streaming apps.
2. Driving & Charging (800 V EQ Powertrain): Coordinates the 800 V Battery Management System (BMS), Silicon Carbide (SiC) inverter, 2-speed automatic gearbox, 320 kW CCS2 DC fast charging (ISO 15118-2 Plug & Charge), 11 kW AC on-board charger, and active thermal preconditioning via the multi-source heat pump.
3. Body & Comfort: Manages zonal body controllers including flush-fitting KEYLESS-GO comfort door handles (SA-87B), Apple Digital Car Key (NFC and Ultra-Wideband proximity), bi-zone THERMOTRONIC climate control (SA-581), memory/massage seats, panoramic roof (SA-416), and 64-color ambient lighting.
4. Automated Driving (MB.DRIVE): Fuses radar, ultrasonic, and camera arrays for MB.DRIVE ASSIST (PC-P20)—comprising DISTRONIC adaptive cruise control, Active Steering Assist (SA-K65), and Active Lane Change Assist (SA-K32)—alongside MB.DRIVE PARKING ASSIST 360 (PC-P47) with 3D 360° cameras and a transparent-hood view (SA-K72).

---

2. GLB with EQ Technology (X244): Complete Software Version History

Tracking real-world connected vehicle telemetry, official Mercedes-Benz technical manuals, and owner reports across European deliveries reveals five distinct software milestones in the GLB (X244) lifecycle during 2026.

Commercial MB.OS Version	Head Unit (GEN20XI3) Raw Build	Release Window & Delivery Method	Modification Code & Manual Edition	Key Features & Changes
v1.2.1	2.0.x	Early 2026 (Factory Launch)	056 · F244 0001 04 (Dec 2025)	Initial launch firmware for early GLB 250+ / 350 4MATIC units. NFC-only Digital Key; lacked UWB proximity unlock and red-light/stop-sign alerts.
v1.3.8	2.1.0	Spring 2026 (April–May Factory LTS)	056 · F244 0008 04 (Apr 2026)	Stabilized 5G ARTEMIS gateway, 320 kW BMS thermal curve tuning, 3 smart charge profiles (Cost, Solar, Green CO₂), 400 V DC charger warning, Car Wash mode integration.
v2.0.0 / v2.0.1	2.1.x	Summer 2026 (July–August Factory)	056 / 057 Transition	First 2.0 branch in factory production. Improved Mercedes me app pairing and home Wallbox synchronization; still used Vodafone eSIM carrier.
v2.1.1 / v2.1.2 / v2.1.3 / v2.1.5	2.1.5	Autumn 2026 (Factory & Workshop OTW)	057 / 807 · F244 0011 04 (Sept 2026)	Active UWB Apple Digital Key (3–4 m passive walk-up unlock), eSIM migration to Deutsche Telekom, split-screen navigation, simultaneous passenger face ID, Apple CarPlay Ultra support. Version 2.1.3 serves as the official workshop OTW release for existing cars.
v2.1.6	2.1.6	Late Oct / Nov 2026 (Public OTA & Workshop OTW)	All X244 (056 & 057)	First major public OTA & XENTRY release: Rim/Curb Protection Warning, Evasive Steering Plus, Proactive Lane Change Assist, Stop Sign & Red Light HUD warnings, PRE-SAFE Curve belt tensioning, AI Avatar gestures.

Detailed Breakdown by Release

1. MB.OS v1.2.1 — Early 2026 Launch Baseline

Delivered on the earliest factory batches of the GLB 250+ and GLB 350 4MATIC in early 2026 (changeYearCode 056). While core 800 V driving and charging worked reliably, early adopters noted that Ultra-Wideband (UWB) hands-free digital key entry and advanced camera-based traffic light warnings were absent, and the MBUX software update screen reported “No updates available” for months.

2. MB.OS v1.3.8 — Spring 2026 Production Baseline (LTS)

Installed at the factory on vehicles produced in April and May 2026 (changeYearCode 056, aligned with the revised April 2026 Service Manual F244 0008 04).

• What it added:
  • Improved 5G stability on the ARTEMIS telematics gateway and refined 800 V BMS thermal management to sustain >250 kW charging between 10% and 45% SoC without premature thermal derating.
  • Expanded Smart Charging from a single cost mode into three selectable profiles: Cost-Optimized, Solar Energy (photovoltaic surplus priority), and Green / Low CO₂ Emissions.
  • Added explicit display warnings (chargingErrorVehicleNoSupport400V) when connecting early 056-spec vehicles (which lack a 400 V DC/DC booster) to legacy 400 V DC fast chargers.
  • Integrated Car Wash Mode awareness into rain/window/sunroof alerts, unified PARKTRONIC and camera interfaces, and added voice control for mechanical cabin elements (such as the panoramic roof sunblind).
• Known quirks in 1.3.x: Intermittent failure of the Easy-Entry/Exit comfort seat retraction (~3 out of 10 exits) and occasional temporary greying-out of the pre-entry climate control toggle in the mobile app.

3. MB.OS v2.0.0 / v2.0.1 — Summer 2026 Factory Transition

Vehicles built in July and August 2026 debuted the 2.0 branch from the factory, refining background app wake-ups and AC Wallbox handshakes while retaining Vodafone as the integrated comfort data provider.

4. MB.OS v2.1.1 / v2.1.2 / v2.1.3 / v2.1.5 — Autumn 2026 Factory Revision & Workshop OTW (057 / 807)

Cars rolling off the production line in September and October 2026 shipped directly with 2.1.1, 2.1.2, or 2.1.5 (documented in the September 2026 Service Manual F244 0011 04), while existing fleet vehicles receiving a manual dealership update via XENTRY OTW are upgraded to MB.OS 2.1.3:

• Active UWB Apple Digital Car Key: Full passive proximity unlocking and starting on UWB-equipped iPhones and Apple Watches from 3–4 meters away without removing the phone from your pocket.
• Comfort Data eSIM Migration to Deutsche Telekom: Replaces the earlier Vodafone pairing workflow with a seamless Deutsche Telekom eSIM backend for native in-car video streaming (YouTube), music, and web browsing.
• UI & Navigation Enhancements: Split-screen navigation showing live motorway service areas and destination weather alongside active route guidance, pre-filtering of incompatible 400 V DC chargers in route planning, trailer-specific traffic sign recognition, and readiness for Apple CarPlay Ultra across the instrument cluster.

Hardware vs. Software in Autumn 2026 (056 vs. 057 Builds): While the computing hardware (GEN20XI3 Head Unit and ARTEMIS 5G TCU) is 100% identical between Spring 2026 (1.3.8) and Autumn 2026 (2.1.5) vehicles, Mercedes-Benz also introduced four physical hardware changes on Autumn 2026 production lines that cannot be added via software:

1. An optional 400 V DC/DC voltage booster converter allowing fast charging on older 400 V DC stations.
2. A dual wireless smartphone charging pad in the center console (up from one slot).
3. The TERRAIN drive mode and Offroad package (Downhill Speed Regulation DSR) on 4MATIC models.
4. A revised physical key fob housing a higher-capacity CR2450 coin cell (replacing the earlier CR2032 key fob).

5. MB.OS v2.1.6 — Late October / November 2026 Public OTA & Workshop Release

MB.OS 2.1.6 is the landmark release that brings the 2.1 software branch to the existing GLB (X244) and CLA fleet via Over-The-Air (OTA) rollout and dealership XENTRY OTW installation. Its official changelog spans four areas:

1. Automated Driving & Parking (MB.DRIVE):
   • Rim & Curb Protection Warning (Felgenschutz-Warnung): Triggers immediate visual pop-up warnings using the 360° camera array (PC-P47) when curbs or low obstacles approach the alloy wheels during low-speed maneuvers.
   • Evasive Steering Function Plus (Ausweichlenk-Funktion Plus): Autonomously executes an evasive steering maneuver within the lane boundaries when an imminent collision risk with vehicles or pedestrians is detected.
   • Proactive Lane Change Assist (Proaktiver Spurwechsel-Assistent): Extends DISTRONIC (PC-P20) on multi-lane highways to automatically overtake slower vehicles and guide the car toward highway exits while the driver keeps hands on the wheel.
   • Stop Sign & Red Light Warning (Stoppschild- und Ampel-Warnung): Projects upcoming red traffic lights and STOP signs onto the driver display and Head-Up Display, issuing visual and acoustic alerts if the vehicle does not decelerate.
2. Infotainment & Navigation (MBUX):
   • Expanded AI Virtual Assistant: Broader natural-language knowledge base for EV charging stations, parking availability, weather, news, and calendar events, plus voice control expanded to French, Italian, Japanese, and Korean.
   • Contextual MBUX Avatar Gestures: The MBUX avatar now displays expressive facial animations matched to cabin actions (such as adjusting THERMOTRONIC temperature or airflow).
   • Custom 3D Surround Navigation Silhouette: Renders an exact 3D model of the GLB SUV (including its specific wheel design) inside the live traffic environment map.
3. Comfort & Safety:
   • PRE-SAFE® Curve Function (PRE-SAFE Kurvenfunktion): Anticipates lateral acceleration before entering sharp bends and gently pre-tensions the driver and front passenger seat belts to improve postural support.
4. System Clean-Up & Stability:
   • Removes the legacy “Navigation announcements during phone calls” toggle and improves graphical frame rates across the Zero Layer interface and STAR3_5 gateway.

---

3. Why Earlier Production Cars Stay on Factory Software: Enterprise LTS vs. Tesla’s Rolling Releases

One of the most common questions among GLB (X244) owners is why vehicles delivered in early production cycles (such as spring deliveries) frequently remain on MB.OS 1.3.8 claiming “Your software is up to date”, while cars rolling off the assembly line in autumn already ship with MB.OS 2.1.5 straight from the factory.

Inspecting the vehicle’s low-level diagnostic telemetry illuminates why this happens. On vehicles running factory version 1.3.8, the underlying hardware status reports:

{
  "softwareArchitecture": "STAR3_5",
  "operatingSystemName": "MBOS_VERSION_1_0",
  "headUnitType": "GEN20XI3",
  "headUnitSoftwareVersionRaw": "2.1.0",
  "tcuHardwareType": "ARTEMIS",
  "remoteUpdateDownload": true,
  "remoteUpdateInstallation": true,
  "remoteUpdateStart": false
}

Because "headUnitSoftwareVersionRaw" is already "2.1.0", the underlying GEN20XI3 head unit and ARTEMIS 5G modem hardware are 100% identical across early and later production batches. Why, then, does Mercedes-Benz hold earlier vehicles on their factory branch for months?

Mercedes-Benz Is Not Tesla: Enterprise LTS vs. Rolling Releases

• Tesla’s Continuous Deployment Model: Tesla treats its fleet like consumer smartphones on a single rolling branch, pushing frequent incremental OTA updates every 3 to 4 weeks across years of vehicle production.
• Mercedes-Benz’s Long-Term Support (LTS) Model: Traditional German automotive engineering treats factory firmware builds like Enterprise LTS server releases. Once a car leaves the factory with a validated build such as 1.3.8, Mercedes-Benz freezes that vehicle’s baseline unless:
  1. A critical cybersecurity vulnerability is discovered in the telematics gateway.
  2. A mandatory safety recall requires modifying powertrain, braking, or emergency systems.
  3. A major consolidated milestone release (such as 2.1.6) completes full homologation and enters staged regional distribution.

How Staged OTA Waves Work on MB.OS

Even after MB.OS 2.1.6 is publicly released, Mercedes-Benz does not open the floodgates to every car at once. Distribution is throttled through strict Staged Rollout Waves filtered by:

• Carline & Baumuster (X244 / 2446131).
• Modification Year Code (changeYearCode: 056 vs. 057).
• Country & eSIM Telecom Carrier (e.g., Spain’s Vodafone/Telefónica M2M routing).
• Sequential VIN Batches.

When your VIN batch is finally flagged for the 2.1.6 OTA:

1. Download Happens Strictly While Driving (nur während der Fahrt): The ARTEMIS 5G modem downloads the multi-gigabyte update payload only while the vehicle is in active driving state. If you park with the download at 91%, the transfer pauses immediately and resumes on your next drive.
2. Pre-Flight Installation Checks: To start installation, the car must have “Automatic online updates” enabled in Settings > System > Software Update, HV battery SoC > 30%, a healthy 12 V starter battery, stable 4G/5G signal, gear selector in P with the parking brake applied, doors locked, and must not be connected to an active DC fast charger.
3. ~80-Minute Unattended Flash: Once authorized on the MBUX screen or Mercedes me app, the car locks itself down for roughly 80 minutes to flash the target modules.

---

4. Forcing a Manual OTW Update at the Workshop: Why It Takes 1 to 2 Days

If you do not want to wait months for your VIN batch to reach the front of the OTA queue, can an official Mercedes-Benz workshop force the update manually?

Yes. Dealership technicians can perform an Over-The-Wire (OTW) update by connecting the vehicle directly to Mercedes-Benz’s central flashing servers in Stuttgart using XENTRY Diagnosis. However, unlike an incremental OTA patch, a full workshop OTW upgrade from 1.3.8 to 2.1.3 (the official workshop release branch on the 2.1 family) across the STAR3_5 zonal architecture is a complex, multi-stage engineering procedure that typically requires one to two full days in the workshop.

Here is an architectural breakdown of everything required to execute a complete manual OTW update and why the process takes so long.

Physical Bay Preparation & Mandatory Safety Protocols

Before XENTRY permits firmware flashing across the vehicle’s Ethernet and CAN buses, the technician must fulfill strict workshop safety prerequisites:

1. High-Speed Diagnostic Link: The vehicle is stationed in a dedicated diagnostic bay and linked to XENTRY via the OBD-II port using DoIP (Diagnostics over IP) for high-throughput Ethernet data transfer.
2. Dedicated 14 V / 100 A Power Stabilizer: Flashing dozens of electronic control units keeps pumps, cooling fans, network gateways, and high-resolution displays awake for hours while the high-voltage DC/DC converter is periodically taken offline. If the 12 V rail dips below strict thresholds mid-flash, an ECU could be permanently bricked. The technician opens the front hood and clamps a heavy-duty 14 V / 100 A external power stabilizer to the 12 V battery terminals. This maintains optimal low-voltage system stability throughout programming without discharging the 800 V traction battery.
3. Window Safety Precaution: Both front windows are rolled completely down while leaving doors unlocked. During body domain controller reboots and actuator tests, central locking mechanisms cycle repeatedly and could otherwise trap keys or diagnostic hardware inside the cabin.
4. Diagnostic Ignition Mode: The vehicle is placed into continuous diagnostic programming mode to prevent automatic sleep timeouts from interrupting active write streams.

The Sequential Multi-Domain ECU Flashing Sequence

Unlike consumer devices that update a single operating system image, an MB.OS vehicle contains dozens of interconnected ECUs distributed across multiple functional zones. When performing a major version upgrade from 1.3.8 to 2.1.3, XENTRY executes a strictly orchestrated multi-hour sequence:

• Hardware Compatibility & Cryptographic Handshake: XENTRY queries each module across the STAR3_5 zonal bus, validates hardware revisions against Stuttgart server master databases, and verifies cryptographic SecOC (Secure On-board Communication) certificates before authorizing flash routines.
• Chassis, Brakes & Dynamics: Diagnostic routines calibrate wheel markers, reset brake wear evaluation registers, and update stability control software.
• Instrument Cluster & GEN20XI3 Head Unit: The central infotainment controller and digital instrument display receive new graphical assets, updated ASSYST PLUS maintenance calculation algorithms, and refreshed tire pressure monitoring (TPMS/RDK) sensor mapping.
• 800 V Battery Management & On-Board Charger (OBC): The high-voltage power electronics domain is flashed, re-initializing the charging inlet locks, coupler actuators, and high-voltage DC fast-charging profile algorithms.
• ARTEMIS 5G Telematics Gateway (TCU): The telematics control unit receives updated modem firmware, emergency eCall communication protocols, and re-initializes encrypted cellular data channels with the backend cloud.
• Body & Comfort Domain: Central gateway modules governing ambient lighting, seat comfort profiles, climate control, and digital door access are reprogrammed and synchronized.

Active System Verification, Sensor Calibration & Bus Sleep Cycle

Once module programming is complete, the update process is still far from over. A comprehensive verification phase is required before the vehicle can be safely returned to service:

1. Stationary Active Verification Mode: The vehicle is switched into an active drive/verification state while stationary in the bay. In this mode, XENTRY monitors sensor telemetry across all high-voltage and low-voltage subsystems under active operational loads.
2. ADAS & Camera Sensor Calibration: Technicians execute diagnostic calibration routines across MB.DRIVE ultrasonic sensors, radar arrays, and 360° surround-view cameras (PC-P47) to ensure all driving assistance safety margins meet factory tolerances.
3. Automated Fault Code Sweep: XENTRY performs a comprehensive scan across all CAN, LIN, and Automotive Ethernet buses, clearing temporary communication loss codes triggered while ECUs were being sequentially flashed and restarted.
4. Deep Bus Sleep & Cloud Masterdata Synchronization: While connected to active diagnostic sessions, onboard controllers continue serving cached baseline values. The newly flashed software version propagates fully to the Mercedes-Benz cloud servers (masterdata) only after XENTRY is disconnected, the hood and windows are secured, and the vehicle enters a 10 to 15-minute deep CAN/Ethernet bus sleep cycle. Upon the subsequent wake-up, the ARTEMIS gateway performs a mutual TLS handshake with Stuttgart, officially updating the vehicle’s cloud profile to the new MB.OS release.

---

5. The Active Safety Recall in Spain: DGT Campaign 5496906 (eCall / ARTEMIS)

In late October and November 2026, owners of the Mercedes-Benz GLB with EQ Technology (X244) in Spain began receiving an official safety recall letter issued jointly by Spain’s Dirección General de Tráfico (DGT — Ministerio del Interior) and Mercedes-Benz España, S.A.U. (dated October 28, 2026).

What Is Recall Campaign 5496906?

• Official Campaign Code: 5496906 (Product safety recall — Activation of the emergency call function).
• Affected Component: The ARTEMIS 5G Communication Module / Telematics Control Unit (TCU) (SA-370).
• Technical Defect: Mercedes-Benz identified that on certain X244 vehicles, the emergency call function (eCall / 112) may not be enabled in the communication module. As the official notice explains:

  “We have detected that in your vehicle there is a possibility that the emergency call function is not enabled in the communication module. Consequently, an emergency call could be placed neither manually nor automatically. In such a case, rescue teams could not be guided to the vehicle, which could aggravate the consequences of an accident.”

• Official Remedy & Duration: An authorized Mercedes-Benz workshop must connect the vehicle to XENTRY Diagnosis and update/re-code the software configuration of the ARTEMIS communication module. The standalone recall operation takes approximately 30 minutes (within a standard workshop reception slot) and is 100% free of charge.

Strategic Advice for Owners: Combine Recall 5496906 with an MB.OS 2.1.3 Workshop Upgrade

If your GLB (X244) or CLA is affected by Recall 5496906 and is still running MB.OS 1.2.1 or 1.3.8, this recall is the ideal opportunity to move your car onto the 2.1.x software branch—specifically MB.OS 2.1.3, the official release applied by dealerships via OTW—without waiting for the staggered 2.1.6 OTA wave:

1. The Car Must Already Be Hooked Up to XENTRY and a 14 V Stabilizer: Because Campaign 5496906 requires putting the vehicle in a diagnostic bay, opening the hood for 14 V power stabilization, and establishing a live XENTRY session with Stuttgart to flash the ARTEMIS TCU, the hardest logistical step is already covered under the recall.
2. What to Request When Booking Your Service Appointment: When scheduling your appointment for Campaign 5496906 at your official dealership, explicitly ask your service advisor:

   “Along with performing DGT Recall Campaign 5496906 on the ARTEMIS communication module, please check XENTRY for available software updates for the GEN20XI3 Head Unit and STAR3_5 domains and apply the update to the MB.OS 2.1 branch (2.1.3).”

3. Mention Known 1.3.8 Symptoms to Justify Warranty Flashing: To allow the dealership to bill the additional XENTRY programming hours under factory warranty, mention any known 1.3.8 symptoms you have experienced—such as intermittent Easy-Entry comfort seat movement failure, occasional 360° camera lag, temporary pre-conditioning button greying-out in the Mercedes me app, or activating full UWB proximity support for Apple Digital Car Key. Just be prepared to leave the vehicle at the workshop for 1 to 2 days while XENTRY completes the full multi-domain OTW cascade!