OnlineTool After coding, establish that the data were written to the correct unit and the vehicle behaves as intended. E-Sys reports the write result; the vehicle check shows the practical outcome.
This guide starts after coding. The report procedure follows the E-Sys 25.10.01 manual.
1. Wait for the report
E-Sys shows progress and messages during coding, then opens a results window.
A completed progress bar shows that processing has ended. It does not establish successful writing: errors may be present in messages or the final report.
Find the coded unit and its CAFD entries in the report. CAFD describes coding parameters with its own identifier and version. If a unit has several entries, check all those included in the job.
The manual's successful write example shows cDeploy Finished and a report heading containing 0 Errors. These refer to the completed operation. They do not establish that every vehicle function was tested.
Select Save in the report window. Keep the report in the job folder with the input data and files used, preserving the result of this particular run.
2. Check the vehicle function
Return to the reason for coding. After a unit replacement, check its equipment. After changing a setting, check the function's new behaviour.
For navigation, open it and check route calculation. A “Navigation” menu item alone does not show that the function works fully.
Read diagnostic faults and assess messages relevant to the work. Save them if the function does not work or the result is uncertain.
If writing succeeds but the function fails, the cause may be outside coding. Navigation may still need appropriate maps or a valid permission. A successful settings write does not check these requirements.
3. Read the written data if needed
To view the unit's current settings after coding:
- In Expert Mode → Coding, find the unit and its CAFD.
- Select the required entry and perform Read Coding Data.
- Wait for a successful read. NCD appears beneath CAFD, and a copy is saved in the CAF folder of the E-Sys data directory.
Keep this copy separate from the file used for writing. Label it as a read after coding to distinguish the prepared result from the retrieved data.
Reading again retrieves the current unit data. The presence of a file does not establish that the function works; check it in the vehicle.
If there is an error
Keep the full message and report. Record the selected unit and CAFD, the file used and what happened before the error.
Investigate the stated cause. For a data mismatch, compare the file with the unit and CAFD version. For a signature error, check that the original received signed file was selected without edits.
Repeating the same write without identifying the cause does not explain a rejection.
Example
If coding a replacement head unit finishes without errors but navigation cannot calculate a route, save the report and vehicle message. Check maps and navigation permission according to the actual symptom.
Completion requires both a successful write to the intended unit and the expected function working in the vehicle.
Check the NCD used for writing
For a rejection, inspect the message and selected CAFD first. Check the original NCD and its preparation details against the unit data.