Component Protection and Immobilizer Faults in Dallas

Why does a used module refuse to work in a different European car?

A used MMI unit from a salvage yard goes into an Audi A4 and the screen reads component protection active. A second-hand DME goes into a BMW 335i and the engine cranks without firing. A replacement EIS from a wrecked Mercedes is fitted to a C-Class and the key will not turn. A keyless vehicle module from another Range Rover is plugged in and the Range Rover will neither unlock nor start. Every one of those parts was working an hour before it was removed from its donor, and every one of them is refusing to work now for the same reason: the manufacturer tied it to the identity of the vehicle it came from.

The immobiliser reference records that electronic immobilizers became mandatory on new cars sold in Germany from 1998, and the European manufacturers built their systems outward from that requirement. The original idea was that a key, an immobilizer module and an engine controller share a secret, so that a thief with a stolen engine controller or a copied key cannot start the car. Over the following two decades the same idea spread to radios, clusters, gateways and body modules, partly to deter theft of the parts themselves and partly to keep the configuration of the car under the manufacturer's control. The result for a used-car buyer in Dallas is that a car assembled from salvage parts can look complete and still be unable to start, and that a cheap used module is only cheap if someone can make it work.

This article walks through the four systems we deal with most often, the Volkswagen Group's component protection, BMW's CAS, FEM and BDC with the ISN, Mercedes-Benz FBS3 and FBS4 with the EIS, and Jaguar Land Rover's KVM and BCM, then explains what a pre-purchase inspection scan reveals, what it costs to resolve each case and where only the dealer can.

What is VAG component protection, and which parts trigger it?

Component protection, Komponentenschutz in the German documentation, is the Volkswagen Group's scheme for tying individual control units to a vehicle. Each protected module stores the VIN of the car it was first installed in. When the gateway finds a module reporting a different VIN, it flags component protection, and the module runs in a restricted mode: the MMI or radio shows the message and refuses audio and navigation, the instrument cluster may show reduced information, a gateway may block functions, and an engine controller may run but with faults logged.

The platforms where this matters most are the ones the brief of this site deals with daily. The MQB platform reference dates the modular transverse architecture from 2012, with the Audi A3 and Volkswagen Golf among the first cars on it, and the longitudinal MLB platform under the A4, A5, A6, Q5 and Q7 uses the same protection scheme. On these cars the protected modules commonly include the infotainment main unit, the display, the instrument cluster, the gateway, the engine and transmission controllers, the parking aid and camera modules, the headlights on some models and the airbag controller.

Removing component protection is an online operation. ODIS connects to the manufacturer's servers, the module's identity is checked against the donor VIN and the receiving VIN, and the protection is cleared and rewritten to the new car. Historically this was a dealer-only function; it is now available to independent shops with the proper access level, and it is one of the reasons our module programming service runs ODIS with an OEM subscription rather than relying on VCDS alone. VCDS reads the component protection fault clearly and is the right tool for most Audi coding, but it cannot clear the protection, which is where many home repairs stall.

Two practical points. First, a module that has been cleared for one car can be cleared again for another, so a used part with a history is not a dead end. Second, the online clearance is per component, so a dash full of salvage modules is cleared and paid for module by module, and the estimate will say so.

How do BMW CAS, FEM and BDC tie the engine controller to the car through the ISN?

BMW's immobilizer family has three generations that an owner is likely to meet. The CAS, Car Access System, served the E-series cars from the early 2000s through the E90 3 Series, E60 5 Series and their relatives. The FEM, Front Electronic Module, took over on the F-series compact and mid-size cars such as the F30 3 Series and F20 1 Series, combining the body domain, the lighting and the immobilizer in one unit. The BDC, Body Domain Controller, is its successor on the later F-series and the G-series cars.

In each generation the immobilizer module, the engine controller and the keys share the ISN, the individual serial number. The DME will only start the engine when the ISN it holds matches the one the CAS, FEM or BDC presents during the start sequence, and the keys are recognized by the immobilizer module in turn. A used DME therefore carries the ISN of its donor, and installed as-is it will crank and not run, with an immobilizer fault logged in both modules. A used CAS or FEM presents the wrong ISN to the original DME and the same thing happens from the other direction, with the added problem that the existing keys are strangers to the new module.

The fix is ISN alignment. The ISN is read from the module that is staying, whether that is the DME or the immobilizer module, and written to the module that is arriving, or the arriving module is reset to a delivery state and programmed through ISTA so that it learns the car's identity. Newer DMEs, the MEVD17 and later Bosch units on the N20, N55, B48 and B58 engines, need bench work with a tool such as AVDI or Abrites to read and write the ISN, while older MSV and MSD units can often be handled on the car. After alignment the module is programmed to the current software level through a J2534 interface and coded for the car's options, and keys are added through the immobilizer module.

The FEM and BDC add a complication on the key side. Adding a key to a FEM or BDC car requires the module to be put into a programming state that involves reading its memory on the bench on many models, which is a longer job than the CAS era, and it is why the ranges for FEM and BDC work are higher than for a CAS. The companion post on module programming and coding goes into the programming step in more depth.

What do Mercedes-Benz FBS3 and FBS4 mean for a used EIS, ESL or engine controller?

Mercedes-Benz calls its immobilizer the drive authorization system, FBS, and the generation decides almost everything about what an independent shop can do. FBS3 covers the cars from the early 2000s through roughly 2013, including the W204 C-Class, W211 and W212 E-Class, W221 S-Class and the ML and GL of the period. In an FBS3 car the EIS, the electronic ignition switch, holds the keys, and the ESL, the electronic steering lock, the engine controller and the transmission controller are each tied to the EIS. A used EIS, ESL, ECU or TCU from another FBS3 car is locked to its donor, but the FBS3 generation can be handled: the modules can be renewed, aligned or in some cases virginized with the AVDI and Abrites tools, keys can be produced from EIS data, and the result is coded with XENTRY.

FBS4 arrived with the W222 S-Class and the W205 C-Class and spread across the range from about 2014. In an FBS4 car the key is manufactured against the VIN at the factory and distributed through the dealer against proof of ownership; the EIS, ESL, ECU and TCU use stronger authentication, and used modules cannot be virginized with aftermarket tools. What an independent shop running XENTRY can do on an FBS4 car is diagnose a failed EIS or ESL, replace it with a new unit ordered for the VIN, perform the SCN coding and the related module work, and handle the DME or TCU replacement with a new part. What it cannot do is produce an FBS4 key or revive a used FBS4 EIS, and a shop that claims otherwise should be asked how.

The practical consequence for a used-car buyer is that an FBS4 Mercedes with a missing or damaged key, or with an EIS from another car, is a dealer problem and a potentially expensive one, while the same situation on an FBS3 car is routine. The W204 and W212 that are so common on the Dallas used market sit on the convenient side of that line, and our Mercedes repair page sets out the EIS and ESL work in detail.

How does Jaguar Land Rover lock the KVM and BCM to the VIN?

On the Jaguar and Land Rover side the keyless vehicle module, the KVM, handles the keys and the start authorization on the L322 Range Rover, the L319 Discovery, the Jaguar XF and the XK, with the body control module and the engine controller tied to it. On the L405, L494 and the later Jaguars the body control module, the BCM, and the RFA module take over those duties. In each case the modules hold the VIN and a security pairing, and a used unit from another vehicle presents the wrong identity.

The repair uses SDD or Pathfinder to program a new or used module to the vehicle and to add keys, and on the earlier KVM vehicles the AVDI and Abrites tools are used to prepare a used module before SDD programs it. Two Land Rover specifics make this work slower than the equivalent on an Audi. The modules frequently need the current software loaded as part of the pairing, which takes time through the online session, and the KVM on older vehicles is also the home of a number of comfort and locking functions that need their configuration restored afterward. The Land Rover repair page and the Jaguar repair page list the other electrical items, from the parking brake module to the air suspension calibration, that tend to accompany a module visit on these vehicles.

Key data for all four manufacturers reaches a professional shop through the secure data release model that the National Automotive Service Task Force operates, described at NASTF. Registration there, with the background checks and audit trail it requires, is what allows an independent shop to obtain security data legitimately, and it is the first thing to ask a shop that offers immobilizer work.

What does a pre-purchase scan reveal about swapped modules and immobilizer faults?

A listing cannot tell you whether a car was assembled from parts, but a full module scan can. In a pre-purchase inspection we connect the brand's own application, ISTA, XENTRY, ODIS, PIWIS, SDD or Pathfinder depending on the car, and read every control unit. The scan returns, for each module, the VIN it reports, its hardware and software part numbers, its coding and its fault memory, and the readout tells a story that the seller may not know themselves.

A radio or MMI reporting a VIN that differs from the chassis has been replaced from another car, and if component protection is active the seller has been living with a dead screen or has muted the message. An instrument cluster whose stored mileage disagrees with the mileage recorded in the engine controller, the gateway or the transmission has been swapped, and the odometer on the dash is not the car's mileage. An engine controller with an ISN or drive authorization fault, or an immobilizer module reporting fewer keys than the seller hands over, points at a car whose security chain has been disturbed. Modules that the car should have but that do not answer the scan have been removed, which on a salvage rebuild is common.

The scan also shows the software levels across the car. A gateway several versions behind the rest of the modules, or a module at a level that never shipped with that model year, indicates a used part that was never updated, and that is a frequent cause of the random warning lights and intermittent no-start complaints on cars with a salvage history. All of this is in the written report, with the VIN discrepancies and immobilizer faults listed first because they are the findings that change the price or end the negotiation.

The policy backdrop is relevant because it is why independent shops can do this work. The Federal Trade Commission's 2021 report to Congress, Nixing the Fix, examined restrictions on repair across industries and observed that they "have steered consumers into manufacturers' repair networks or to replace products before the end of their useful lives", per the FTC report. Immobilizer and component-protection access is exactly the kind of restriction that report discusses, and the access programs that now exist are what keep a used module repairable outside the dealer.

What does it cost to resolve, and when can only the dealer do it?

The ranges below are typical for an independent European shop in Dallas and assume the diagnostic session has already identified what is locked and why.

Situation	Typical Dallas range	What moves it
VAG component protection cleared online, per component	$180–$320	Number of protected modules, whether a software update is needed
Programming and coding labor for a customer-supplied or used module	$250–$650	Brand, ISN alignment or virginizing steps, online programming time
BMW FEM or BDC supplied, programmed and coded	$650–$1,400	Bench read required, number of keys added, software level
BMW CAS supplied, programmed and aligned to the DME	$600–$1,100	Generation of CAS, keys added, DME alignment method
Mercedes-Benz EIS or ESL supplied and coded, FBS3 or FBS4	$650–$1,900	FBS generation, whether a dealer-sourced key is also needed
Jaguar Land Rover BCM or KVM supplied and programmed	$700–$1,600	KVM or BCM vehicle, software update time, keys programmed
Extra key programmed alongside an existing working key	$220–$450	Brand, key type, FBS4 keys excluded
All keys lost	$450–$950	Brand, bench work on FEM or BDC, dealer-sourced key on FBS4

Dealer quotes for the same module work are commonly higher, and a dealer will often decline to install a used module at all, which is a legitimate policy but one that turns a few hundred dollars of clearance work into a new part at list price. The dealer-only cases, to be explicit, are FBS4 keys and used FBS4 immobilizer components on Mercedes-Benz, certain security functions behind the newest VAG gateways, and any module that the manufacturer will only release against the VIN. In those cases we diagnose, we tell you what to order and we complete the coding once the part arrives.

The labor behind these ranges is specialized. The Bureau of Labor Statistics puts automotive service technician and mechanic employment at 805,600 in 2024, with a median wage of $23.88 per hour, with about 33,600 openings projected each year on average over the decade, per the BLS handbook. Technicians who hold NASTF registration and work with AVDI, Abrites and five manufacturers' applications are a small fraction of that group, which is why the programming labor line exists separately from the part.

Modules we supply, keys we produce and the programming labor itself are protected by the 2-year/24,000-mile warranty, that is 2 years parts and 2 years labor, up to 24,000 miles, nationwide. For a module you supply, the coverage applies to our programming work, and the invoice records the VIN, the part numbers and the software versions so the history travels with the car.

Does an independent immobilizer repair affect the warranty, and what else should you check?

For a car still within its factory warranty, an independent repair does not void coverage. Under the Magnuson-Moss Warranty Act, codified at 15 U.S.C. 2302, a warrantor may not condition coverage on a named brand of part or service, and the FTC's consumer guidance explains that a dealer must show the independent work caused a failure before denying a claim, per the FTC. A documented ISN alignment or component protection clearance, with the software versions recorded, is the kind of record that protects you if a question arises.

Before buying any used European car, look the VIN up in the NHTSA recall database, because open recalls are repaired at no charge by the dealer and the list tells you how attentively the car was maintained. And remember that a car with an immobilizer fault and a lit check engine light has a registration problem in Dallas County as well as a mechanical one, since the Texas Department of Public Safety lists 17 emissions counties, including Dallas, Collin, Denton and Tarrant, where gasoline cars 2 through 24 years old must pass the OBD emissions test.

How do you avoid buying these problems in the first place?

Insist on the scan before money changes hands, and insist that the scan is run with the manufacturer's application rather than a generic reader, because a generic tool does not read the VIN stored in each module or the immobilizer fault memory. Count the keys and have each one tested in the car, since a key that opens the doors but will not start the engine is a key that was never programmed. Ask the seller directly whether any module has been replaced and compare the answer with the readout. Treat a salvage or rebuilt title as a reason for a module-by-module VIN check rather than a reason to skip it.

On the three brands where the line between independent and dealer matters most, know which side of the line the car sits on. An FBS3 Mercedes-Benz, an E-series or early F-series BMW and an MQB Audi with a component protection message are all cars an independent shop in east Dallas resolves routinely with the tools named above. An FBS4 Mercedes-Benz with key problems, or any car whose immobilizer module is missing entirely, is a dealer-dependent purchase that should be priced as one. If you have a car in mind, or a used module that is refusing to cooperate in a car you already own, call or text (817) 765-6604 with the VIN and a description of the message on the dash, and we will tell you which category you are in. Our key programming and module programming pages list the brands and modules we handle, and service is available in Spanish.

Where do these figures come from?

• Immobiliser reference: the 1998 German requirement and the principle of pairing key, immobilizer and engine controller.
• Volkswagen Group MQB platform reference: the 2012 introduction and the models built on it.
• NASTF: the secure data release model through which registered shops obtain key and immobilizer data.
• FTC, Nixing the Fix: the 2021 report and the quoted finding on repair restrictions.
• Warranty law: the statute at 15 U.S.C. 2302 and the FTC consumer guidance on independent repair and claims.
• NHTSA recall lookup: open recalls by VIN before purchase.
• BLS handbook: the technician employment and wage figures quoted in the cost section.
• Texas DPS emission inspection criteria: emissions counties and the vehicle age bracket.
• Module and key ranges: typical independent-shop figures in Dallas from the shop's key programming, module programming and pre-purchase inspection pages; the estimate for a specific car follows the module scan.