You can't write any coding file to car without connection to car.

 

I want to update only offline the stored NCD Files, but not write it to vehicle at the time.

That is clear for me that I need to go into the vehicle and connect for write it to ECUs

 

Well, I don't know anyway to VO Code an .ncd file. You can only VO Code ECU while connected, and then read the .ncd back from it.

 

You can modify the FA file and do the FP checks in E-Sys without being connected, but I don't know of a way to apply the FDL changes from the new FA to the .ncd files without being connected to the car.

 

Thanks for the information!

 

OK, I understood now that a connection to the car is required, but:
Now I add any new option to the FA and then press on "calculate FP" . Is there any way to generate the new ncd-files (for comparing reason with the original) without write them to the car, or do I need to code (write) it to the ECUs and read it back to get the actual ncd files?

 

E-Sys Coding-Verification:

Create a factory default .ncd file based on your FA/VO.

Save your FA to file and change/add the SALAPA elements you need (e.g add 8TD and 8TH) to a file.
Save your SVTActual (SVTIst) to file.

In expert mode go to the Coding-Verification screen.
Load the FA/VO and Right click on it to 'Calculate FP'.

On the 'Complete Verification' section, select 'Verification by SVT' and select your SVTActual file you just saved.

On the 'Settings' section, enter a Trace Directory and select the 'NCD-Trace' checkbox.

Once that is done you can either select the CAF's you want to validate (quicker) or hit the 'Start Complete Verification' button (slow).

When the process finishes, you'll have all the NCD trace files that the validation process generated in the 'Trace' directory/folder you specified. You can then open these files and look at the values with the FDL Editor.

You can also add these files to your ECU in the coding screen by right clicking on the CAFD item and selecting NEW> FDL.

 

How to create a factory default .ncd file based on your FA/VO?

 

Do as I just wrote above using factory original FA.

 

Yes, I have the factory original FA.
But what is the step to create the factory default .ncd file? Is there any "create ncd" Button?

 

I just wrote above in great detail exactly how to do it using E-Sys Coding-Verification:

All BMWs - Offline VO coding with ESYS

Hi, does anyone know if it is possible to code a VO option with ESYS without connect it to the vehicle? The FA, SVT and NCD files have already been read out and saved. This means that the saved NCD files should be updated by the VO coding. I assume that the changed NCD files can later be written...

www.bimmerfest.com

I don't know what more you can possibly need.

 

Sorry, was not clear for me :-(
Dou you mean in expert mode go to the Coding-Verification screen and perform the steps with original FA (salapa) and then with changed FA (changed salapa)?

 

Yes, and then you can compare the resulting .ncd trace files.

 

Ok, understood now!
The next Issue is, I selected all and started complete verification. Now it runs endless and generates hundreds of ncd-files, but in real I have only 28 ECUs.
How can I find out in advance which NCD files will be affected by the FA change (e.g. new oprion added)?
Then I would only generate and compare the few.

 

As written:

"Once that is done you can either select the CAF's you want to validate (quicker) or hit the 'Start Complete Verification' button (slow)."

You can see what CAFD's your ECU's currently have, so select only those.

 

Understood!
Can they be selected from the stored svt file or do I need to select all the (at least 28) manually?

 

I think only manual but you can select all at once. You have to play with it yourself.

 

I found an adequate way to do it
I selected in Tab "Expert Mode" the Menu for "NCD preparation" (below Coding-Verification).
And the switched to tab "NCD preparation from SVT". It generates exactly the necessary ncd files

 

I found an adequate way to do it
I selected in Tab "Expert Mode" the Menu for "NCD preparation" (below Coding-Verification).
And the switched to tab "NCD preparation from SVT". It generates exactly the necessary ncd files

 

Now I'm confused!
If I compare the generated ncd files with the original ncd files with BimmerUtility, there are drastic differences.
The generated ncd files don't seem to make any sense. In addition, the generated ncd files cannot be opened in the BimmerUtility FDL Editor. BimmerUtility hangs and is being terminated by Windows

 

However, generating an ncd file with the "Coding Verification" method seems to work .
I generated a specific ncd file and then compared it with the original ncd file. Is identical (except for the signature)!

Attention: ESYS obviously has an issue with "NCD preparation from SVT"