How to Export BMW FA and SVT Files in E-Sys

What FA and SVT contain

FA, also called the vehicle order, describes the vehicle configuration used by BMW diagnostic and coding systems. It includes model-related information, production data and equipment codes. SVT is the software variant table. It lists control units and the software elements detected in the vehicle.

For an NCD 2.0 request, the safest input is a freshly read FA and an SVT Actual from the same vehicle and the same working session. The files provide different parts of the context and are evaluated together.

Preparation before connecting

• Use a stable diagnostic interface appropriate for the vehicle platform.
• Keep the vehicle voltage stable. Reading data is a low-load operation, but an interrupted session can still produce incomplete files.
• Open the correct E-Sys project or target for the vehicle series.
• Create a dedicated folder named with the VIN and date so that files from different vehicles are not mixed.

This guide covers reading and saving only. Do not start TAL processing, flashing, coding or VCM write operations when the goal is merely to export input files.

Export the FA file

1. Connect E-Sys to the vehicle and confirm that the connection is active.
2. Open the vehicle order or VCM area used to read FA from the connected vehicle.
3. Run the read operation and wait until the FA tree is populated.
4. Save or export the FA as an XML file into the dedicated vehicle folder.
5. Confirm that the saved file is not empty and that the VIN shown in the data belongs to the connected vehicle.

The exact button names can differ between E-Sys releases and launcher configurations. The important point is to save the original XML representation after a successful read, not a screenshot or a manually copied text fragment.

Export SVT Actual

1. Without changing vehicles or projects, open the SVT or ECU read area.
2. Read the current ECU/software structure from the vehicle.
3. Choose the result representing the actual detected state, commonly labelled SVT Actual or SVT ist.
4. Save the result as XML in the same folder as the FA.
5. Check that the file contains ECU entries and is larger than a few bytes.

Do not substitute an SVT Target generated for programming. A target table represents a planned state, while an NCD preparation request normally needs the current detected structure unless the service explicitly requests another format.

Verify the pair before upload

Common export mistakes

• Saving SVT Target instead of SVT Actual.
• Combining a recently exported FA with an old SVT stored for another software state.
• Renaming files so aggressively that the user can no longer identify their origin. Renaming alone does not normally alter XML, but traceability matters.
• Opening and resaving XML in software that changes encoding or removes namespaces.
• Uploading only one file or a screenshot of the E-Sys screen.

Safe next step

Keep an untouched backup of both files. Upload copies to the service, verify the detected VIN and file names, and review the result count before downloading the archive. The generated files should still be used only with a suitable coding environment and a verified vehicle context.