BMW Online ToolPROFESSIONAL SOFTWARE
ENRU
Telegram

Signed BMW NCD: preparation, application and checks

Before applying an NCD, match it to the vehicle, CAFD and software, then select that particular result in E-Sys. Downloading the file completes data preparation; the write and vehicle checks come afterwards.

Match data to the unit

NCD contains coding settings. CAFD identifies their description and version. Compare the required CAFD entries with the result information, particularly after replacement or a software update. One unit may have several entries.

NCD does not install firmware or supply a feature permission such as FSC. FA describes the intended configuration and SVT describes the units. The preparation service uses this pair to produce available signed NCD and determines 2.0 or 3.0 from the input data.

Preserve the signature

Secure Coding requires signed data. The signature allows checks of origin and changes after signing; a file name containing signed does not perform that check. Authentic data must still suit the vehicle and unit.

Keep the received file unchanged. Edited data require a new signature; saving edited signed data in E-Sys starts signing. Viewing a prepared file does not require editing or saving it.

Example

For E-Sys 25.10.01, with the connection and appropriate data established:

  1. In Coding, read or load FA and activate it to calculate the vehicle profile.
  2. Read SVT and find the unit and CAFD. Read (ECU) retrieves unit information; Read (VCM) retrieves configuration management records.
  3. If needed, read existing settings using Read Coding Data. NCD appears beneath CAFD and a copy is saved in CAF.
  4. Separately select the prepared NCD for the appropriate CAFD. A vehicle read and a service result are different files.
  5. Check the selection and use Code NCD according to the job procedure. Ordinary coding does not establish that the received file is selected.
  6. Inspect the report for the unit, then check its function and relevant diagnostic messages.

These actions describe E-Sys. ISTA Secure Coding follows its own procedure.

Handle an incomplete result or rejection

Compare required CAFD with the received NCD. Resolve missing data before writing to that unit; another unit's file cannot replace it.

Keep the exact rejection and report. For a signature error, check the original file and absence of edits. For a mismatch, check CAFD and installed software. If writing succeeds but the function fails, investigate its equipment, settings and permission requirements separately.

Related guides