Sign in to continue
Upload a CAFD file and provide FA elements to generate coded NCD output. The server resolves FP files, evaluates conditions, and builds the NCD S-record.
Upload a CAFD file to inspect its internal structure: data groups, functions, main series mappings, and FP IDs.
Select coding scripts to apply to this CAFD. Move scripts from Available → Selected, then Apply to preview changes in the structure below.
Load an eSys FA XML file to inspect vehicle order data: series, type key, SA/E/HO codes.
Compare two eSys FA XML files to identify differences in SA codes, E codes, HO codes, series, and type key.
Load an eSys SVT XML file to inspect ECU list, software parts, diagnostic addresses and bus connections.
Compare two eSys SVT XML files to identify added, removed, or changed ECUs and software parts.
| ECU | SGBM ID | Function | Data Group | Comment | Actions |
|---|
| SGBM ID | ECU Name | Block Address | Actions |
|---|
Upload an NCD file to parse its structure or sign it with a BTLD profile key.
Search SGBM numbers and descriptions from PSdZ reference data. Also browse BTLD RSA signing keys.
| SGBM Nr | Description |
|---|
| BTLD Ref | Type | Actions |
|---|
Load FA1 (Main), FA2 (Compare) and SVT XML files. Calculate identifies which CAFD parameters differ between the two vehicle orders per ECU.
Generate V0.5.2-compatible activation keys from a machine code. Uses MD5 + AES-128-CBC.
Upload an NCD file, select coding scripts to apply, then download the modified NCD for E-Sys.
Import FDL XML cheat files, create new scripts manually, or edit existing ones.
| ECU | SGBM | Description | Person | Group | Series | Changes | Actions |
|---|
Choose which script authors you want to see. Your own scripts are always visible.