What NCD 2.0 is
An NCD file contains ECU coding data used by compatible BMW coding workflows. On newer vehicle platforms, the coding workflow may require signed or server-prepared NCD data rather than a locally generated file.
The NCD 2.0 service does not read a vehicle directly. It works with the FA and SVT files supplied by the user and returns a digital archive when the backend successfully prepares the supported files.
The role of FA and SVT
FA (vehicle order) describes the vehicle configuration: model-related data, production information and option codes. SVT describes the ECU and software structure detected for the vehicle.
The two files must represent the same vehicle context. A mismatched FA and SVT pair can point to different ECUs, software versions or coding applications and may therefore be rejected or produce an incomplete result.
Recommended workflow
- Export a fresh FA and SVT from the vehicle or a trusted diagnostic/coding environment.
- Keep the original XML files unchanged. Renaming a file is normally harmless, but editing XML content manually can break namespaces, identifiers or ECU references.
- Upload FA first and SVT second, verify the selected filenames, then start the request. Keep the page open while the backend processes the files.
- After successful preparation, download the ZIP and keep the original FA, SVT and result archive together for traceability.
What the result contains
The archive is named using the vehicle VIN and request time. Inside it, supported NCD files are grouped in ECU folders. A single ECU may contain more than one NCD file when multiple coding applications are present.
The service returns only files successfully prepared by the backend. The number of files depends on the vehicle, its software structure and the supported coding applications in the supplied SVT.
Common causes of a failed request
- FA and SVT belong to different vehicles or different vehicle states.
- One of the XML files is incomplete, malformed or exported in an unsupported form.
- The SVT does not contain the expected ECU/CAFD information.
- A temporary backend or upstream service error occurs. In this case, retry with the same unchanged files before creating new exports.
Before using the files
Always save the original vehicle data and create a backup before coding. Confirm that the target ECU, vehicle voltage and coding environment are suitable for the planned operation.
The service prepares digital files; it does not perform coding on the vehicle and cannot verify every local E-Sys, ISTA or interface configuration.
ONLINETOOL SERVICES
Use the online service
Learn how the BMW NCD 2.0 generator uses matching FA and SVT XML, prepares supported coding files and returns the resulting ZIP archive.
Frequently asked questions
Can I use FA and SVT from different vehicles?
No. They should describe the same vehicle context. A mismatched pair is a common reason for rejection or an unusable result.
Does every ECU always receive an NCD file?
No. The result depends on the supplied SVT, available CAFD entries and backend support for the vehicle software structure.
Are credits deducted if processing fails?
On the online services site, credits are deducted only after the backend successfully prepares the digital result.
Can I edit the XML files before uploading?
Manual editing is not recommended. Export fresh files and upload the originals whenever possible.