[Arived26derchi]

Hello everyone,

When trying to code the country, both KAFAS4 coding files were corrupted. Initially, they would not restore. I put the car to sleep, and after waking it up, I restored and coded them using the original FA while holding the Ctrl key. Before the sleep cycle, the errors were the same as at the beginning of the thread.

However, FDL coding still does not work — the files get corrupted again.

[Rajco]

Try to virgin the kafas and code again, maybe this will help you

[Meks_Ua]

Hi, this might be useful for you:

My KAFAS coding got messed up when I tried to code it based on the vehicle’s FA (the configuration stored in the car), as I thought it was the original factory FA.

My error was:

<Caf's werden gesucht>
Read NCD
NCD-Coding 1: "CAFD_00004101.CAF.012_005_020.NCD"
TAL calculation started.
TAL execution started.
<>
Read SVT before TAL execution started.
Checking Mirror-Protocol started
Mirror-Protocol: no token required
Flashing does not require a Programming Protection "BASIC/PLUS" token
TAL execution started.
<httpServerActivation: true>
<isDeactivateHttp: false>
<ExecutionID=2026/08/22-16:39:57.896>
<[] prepareTALExecution started [PROGRESS]>
<[] prepareTALExecution finished [PROGRESS]>
<[] prepareVehicleForCoding started [PROGRESS]>
<[] prepareVehicleForCoding finished [PROGRESS]>
<[KAFAS4 - 5D] prepareECUforCoding started [PROGRESS]>
<[KAFAS4 - 5D] prepareECUforCoding finished [PROGRESS]>
<[KAFAS4 - 5D] authenticateECUforCoding started [PROGRESS]>
<[KAFAS4 - 5D] authenticateECUforCoding finished [PROGRESS]>
<[KAFAS4 - 5D - cafd_00004101-012_005_020] Transaction type: cdDeploy;  Message: TA started [TRANSACTION]>
<[KAFAS4 - 5D - cafd_00004101-012_005_020] Transaction type: cdDeploy;  Message: TA finished [TRANSACTION]>
<[KAFAS4 - 5D] finalizeECUCoding started [PROGRESS]>
<[KAFAS4 - 5D] finalizeECUCoding error [PROGRESS]>
<[] job failed with negative response error:
code: coding signature not correct
description: no detailed description available; LinkName: KAFAS4_5D_ETHERNET
severity: ERROR
[THROWABLE]>
<[KAFAS4 - 5D] There was an error during TAL execution, please check the log files. [WARN]>
<[KAFAS4 - 5D] - [Exception - KAFAS4 - 5d] job failed with negative response error:
code: coding signature not correct
description: no detailed description available; LinkName: KAFAS4_5D_ETHERNET
severity: ERROR
>
<[] finalizeVehicleCoding started [PROGRESS]>
<[] finalizeVehicleCoding finished [PROGRESS]>
<[] finalizeTALExecution started [PROGRESS]>
<[] finalizeTALExecution finished [PROGRESS]>
<TAL execution finished [TAL_EXECUTION_FINISHED]>
TAL-Execution finished with status: "FinishedWithError".
TAL execution finished. Duration: "34s".
<>
Read SVT after TAL execution started.
Read SVT after TAL execution finished.
TAL execution finished.

I couldn’t figure out what was causing it for a long time. However, I then decided to compare the FA stored in the car with the original FA from when the car left the factory. That’s where the problem was.

The car had 360° cameras retrofitted, and the FA had been modified. In my case, option **3AG** had been removed and **5ND** had been added.

After restoring the FA to the original factory configuration, I was able to code KAFAS based on the FA without any errors.