B2005–B2013 Airbag Control Module (J234): Missing Datasets / End-of-Line Programming not performed
The ECU has logged a fault on B2005. The definition below is the exact wording the standard uses for this code.
Can you drive it? This is a restraint-system fault. The airbag or belt tensioner may not deploy in a crash, and in some failure modes may deploy when it shouldn't. Have it looked at before carrying passengers.
Which code is which
Same fault, different cylinder or bank — diagnosed the same way. Several set together usually means one shared cause.
| Code | Definition | Severity |
|---|---|---|
B2005 | Airbag Control Module (J234): Missing Datasets / End-of-Line Programming not performed | Safety system |
B2013 | Airbag Control Module (J234): Missing Datasets / End-of-Line Programming not performed | Safety system |
The definition
B2005: Airbag Control Module (J234): Missing Datasets / End-of-Line Programming not performed.
B2005 is a manufacturer-specific body code (an interior or comfort system). Its meaning is set by the carmaker rather than by the SAE standard, so a generic OBD-II reader will often show it as an unknown code or misread it.
What to check first
Cheapest and fastest checks first:
- Read the freeze-frame data stored with the fault - engine speed, load and temperature at the moment it logged tell you whether this happens cold, hot or under load.
- Check the connector at the part for corrosion, and that it is fully seated.
- Clear the code and see whether it returns, and under what conditions.
What actually causes this on a VAG
This is not a wiring or sensor fault. The airbag control unit is telling you it has never been given the data it needs for this specific car: the end-of-line coding and dataset that the factory, or a properly equipped workshop, writes into it. Until that is done the airbag light stays on, and you should assume the restraint system will not fire in a crash, no matter how healthy the airbags and sensors themselves are. It almost always follows recent work on the car, so start by finding out what was done rather than by testing anything. Read the plain-text description your tool shows next to the code as well, because the module names the data it is missing.
Most likely causes, in order
- A replacement module was fitted but never coded. By far the most common reason. New airbag control units arrive blank and need variant coding plus the vehicle's dataset written in, which on most modern VAG cars means a workshop with manufacturer online access. Ask whoever last worked on the car: accident repair, dashboard or windscreen work, or a module bought online all point this way.
- A coding session that was interrupted. The cheapest possibility, so rule it out first. If programming dropped out part way through, from a flat battery or a lost connection, the module can be left holding incomplete data. It will usually complete on a second attempt with a proper charger connected to the car.
- A used module from another car. A second-hand unit carries the donor car's dataset, and may also carry that car's crash data, which can leave it permanently locked so that no amount of programming will bring it back. Find out where the module came from before spending anything on diagnosis.
- Wrong variant of module for this car. A unit built for a different specification or market can refuse to accept the dataset. Confirm the fitted module is the correct part for your exact model, engine and equipment level before repeating the programming.
Worth knowing: Treat the car as having no airbag protection until that light is out. A module that has never been coded is not standing by waiting for an impact, it is inactive, and that includes the belt tensioners. Two things follow. First, no amount of new airbags, seat belts or sensors will clear a coding fault, so do not let anyone start replacing restraint parts on the strength of this code. Second, a cheap used airbag module from a breaker is usually a false economy: many still hold crash data from the donor car, and the correct dataset generally can only be written by a workshop with manufacturer online access, so budget for the programming and not just for the box.
Reading the code is the easy part
A code names the circuit that complained. What tells you why is watching the sensor behind it while the engine runs — and that is where a code reader stops and a diagnostic tool starts.
VAGPULSE reads every module in a VW, Audi, Skoda or SEAT — not just the engine — shows the live measuring blocks behind this fault, gives you the freeze-frame conditions it was logged under, and clears it once you have fixed it. It also does what a generic OBD reader cannot on a VAG: service resets, coding, adaptations, and Stage 1–3 flashing with your original file saved first.
$249 once. No subscription, unlimited cars. Windows 10/11.
See VAGPULSE — $249 Look up another codeSoftware downloads instantly · cable ships September 30 · cable guarantee — refund if it won't connect
Prefer to work on your phone? The VAGPULSE Android app is a free download and its demo mode runs against a sample car with no hardware at all, so you can see exactly what it reads before spending anything. Reading your car with it needs the VAGPULSE cable, which comes with the licence.
Common questions
What does B2005 mean?
B2005 means Airbag Control Module (J234): Missing Datasets / End-of-Line Programming not performed. It is logged when the ECU sees this circuit outside its expected operating window.
Can I drive with B2005?
This is a restraint-system fault. The airbag or belt tensioner may not deploy in a crash, and in some failure modes may deploy when it shouldn't. Have it looked at before carrying passengers.