After an ECU swap, flash or an aborted calibration, the level control reports “no end-of-line programming performed” or “control module not coded”. We restore missing parameter/EOL datasets – via ODIS/SVM parameterization or a VCP ZDC/EOL upload, including coding, basic settings and ride-height calibration.
B201310490624U101313636352
Send us the Auto-Scan & part/software number – we’ll tell you honestly whether parameterization is possible.
If the level-control unit (address 34) is missing its end-of-line programming or coding, the air suspension behaves abnormally – usually right after work on the control unit.
The car stays low or uneven, no longer rises to normal level and can’t be adjusted.
“Air suspension fault / visit workshop”, inactive level control and a fault-memory entry in control unit 34.
The Auto-Scan shows B2013 10490624 “no end-of-line programming performed” and/or U1013 13636352 “control module not coded”.
Both entries come from the air-suspension control unit, but describe different states. A clean repair has to keep them apart.
The control unit is missing its factory end-of-line (EOL) programming. Typical for a brand-new or replaced unit that was never given the vehicle-specific end data. Without this dataset the level control won’t start operating.
The control unit has no valid coding matching the vehicle and equipment. This can occur in addition to the missing end-of-line programming – or on its own, e.g. after a software update or a reset coding.
Important: coding alone (against U1013) doesn’t help if the end-of-line programming (B2013) is missing – and vice versa. That’s why we check both separately.
“Air-suspension data deleted” almost always has a concrete trigger. The most common ones:
A new, used or reprogrammed level-control unit does not automatically carry the vehicle-specific end-of-line data.
An interrupted basic setting or calibration (e.g. a voltage drop) can leave the dataset incomplete or invalid.
Coding or parameter data doesn’t match the vehicle/equipment or is missing entirely – e.g. after a reset, wrong coding or data loss.
VCDS is strong at reading, coding and basic settings. However, it usually cannot recreate a missing factory dataset.
Read faults, code the control unit, run adaptations and basic settings. For many level-control tasks that is exactly right.
If the end-of-line programming (B2013) is absent, the actual factory dataset is missing. It is restored via an ODIS/SVM parameterization or a VCP ZDC/EOL data upload – provided the vehicle and control unit support it.
A structured path from diagnosis to a calibrated level control – depending on what your vehicle and control unit support.
Evaluate the Auto-Scan, part/software number and fault picture. We clarify whether only the coding (U1013) or also the end-of-line programming (B2013) is missing.
Parameterization via ODIS/SVM or a ZDC/EOL upload via VCP – where supported. This brings the missing factory dataset back into the control unit.
Set the correct coding, run basic settings and align adaptations with the vehicle and equipment.
Clean the fault memory and check that U1013/B2013 disappear for good with no follow-up faults.
Calibrate the vehicle height so the level control works at the correct target values again.
Verify function while stationary, check the control behaviour and document the results.
We give no compatibility or success guarantee before checking the vehicle and control unit. Some part numbers and configurations cannot be parameterized – we tell you openly before anything is done.
Air suspensions with level control (addr. 34) appear across the whole group. Typical candidates for parameterization – whether your vehicle is among them we clarify via Auto-Scan.
Common cases: A6/A7 (C7, C8), A8 (D4, D5), Q7 (4L, 4M), Q8, allroad models and e-tron with adaptive air suspension.
A classic is the VW Touareg (7L, 7P, CR) with air suspension; likewise models with comparable level control in the group.
Porsche/Bentley platforms within the group use similar control units too. Just tell us your model – we’ll check the specific part number.
With these four details we can assess your fault picture in advance and tell you whether a recovery is possible.
Model, model year and the complete vehicle identification number (VIN).
A full Auto-Scan across all control units as a text file.
Part number and software level of the air-suspension control unit (addr. 34).
A photo/screenshot of the fault entry U1013 or B2013.
Answered briefly and honestly – without marketing promises.
No. Both entries concern the air-suspension control unit (address 34, level control) but describe different states. B2013/10490624 means “no end-of-line programming performed” – the unit is missing its factory end-of-line programming. U1013/13636352 means “control module not coded”. They often occur together but should be assessed separately.
Often not. VCDS can code and run basic settings, but it usually cannot recreate a missing or invalid parameter/EOL dataset. If the dataset is entirely missing after an ECU swap or flash, parameterization via ODIS/SVM or a ZDC/EOL upload via VCP is required – provided the vehicle or control unit supports it.
It depends on the vehicle, the fitted control unit and the cause. That’s why we first check your Auto-Scan and the part/software number and then quote a transparent fixed price or time window. We give no success or compatibility guarantee before checking the vehicle and control unit.
Vehicle, model year and VIN, a complete VCDS Auto-Scan, the part and software number of the air-suspension control unit, and a screenshot of the fault entry. With that we can assess in advance whether parameterization is possible.
In some cases yes; in many cases an on-site diagnosis is sensible or required – especially for basic settings and ride-height calibration, which must be carried out on the stationary vehicle. We decide this together based on your data.
Yes. After writing the dataset we perform coding, basic settings, clear the faults and calibrate the ride height (level control). Only then does the air suspension work reliably at its target values again.
Send us the Auto-Scan, part/software number and a screenshot of the fault. We check your case and tell you honestly whether and how U1013 / B2013 can be fixed.