Update Data Files

This page explains how to update and migrate project input files (ECU Extract, Diagnostic Data, Communication Extract) when moving from DaVinci Configurator Classic Version 5 to DaVinci Configurator Classic Version 6.

Prerequisites

Input Files Location

Item Default Location Notes

Preserved DPA inputs

Input/Preprocessing (when --dest-dir was used)

Configured in the DPA <Display> section; if no --dest-dir was provided during migration, files remain in their original locations and are referenced from there.

DDM JSON (diagnostics)

Input/OEMInput/Preprocessing

File names end with _dvarjson.json; used as input for conversion to ARXML.

Preprocessing metadata

Input/OEMInput/Preprocessing/file_preprocessing_data.json

Supports Ecu Extract Producer analyze-migration to generate an additional Ecu Extract Producer script.

Update/Migrate Input Files

  1. Review preserved inputs

    1. Open Input/Preprocessing (and Input/OEMInput/Preprocessing for diagnostics) and verify all referenced files exist.

    2. If files were not copied (no --dest-dir), ensure paths in Settings/*.json point to their current locations.

  2. Configure tool paths

    1. In Scripts/config.*, set CLI to the DaVinci Configurator Classic CLI executable and, if needed, DVARJSON to the DaVinci-AUTOSAR-JSON executable.

    2. Use absolute paths or environment variables; see examples in Execute Update Workflow Script.

  3. Convert Diagnostic Data (if you have DDM JSON)

    1. Use DaVinci-AUTOSAR-JSON to convert each _dvarjson.json file to ARXML.

    2. The command is documented at Convert DDM.

    3. Output ARXML files are written next to the JSON and end with _converted.arxml.

  4. Import Diagnostic Modules

    1. Use DaVinci Configurator Classic CLI ddm import diagnostic-modules to import the converted ARXML files, variant-aware if applicable.

    2. Follow Import Diagnostic Modules.

  5. Derive ECUC from ECU Extract

    1. Provide your ECU Extract (ARXML). If your inputs are multiple formats (DBC, system description, multiple extracts), preprocess them with Ecu Extract Producer first; see Generate ECU Extract.

    2. Run DaVinci Configurator Classic CLI project derive-ecuc to integrate the ECUC into the project.

    3. Detailed steps: Derive ECUC.

  6. Execute the Update Workflow Script (optional but recommended)

    1. Navigate to Scripts and execute update_workflow.bat (Windows) or update_workflow.sh (Linux).

    2. Run it from the Scripts directory to keep relative paths valid.

    3. The script chains the required CLI calls (derive-ecuc, dvarjson ddm convert, ddm import diagnostic-modules, import module, project update).

Communication Extract Handling

  • DaVinci Configurator Classic Version 6 no longer distinguishes at load time; the same ARXMLs from the migrated project are used.

  • Either Communication Extract or ECU Extract is referenced as harmonizedExtract in Settings/ArxmlProjectContent.json.

  • No additional flag is required; verify harmonizedExtract.fileList points to your extract ARXMLs.

Verify the Update

  • Check CLI/log output for success messages and counts of imported diagnostic modules.

  • Verify generated ECUC resides under Output/Config/EcuConfig and appears in the configuration.

  • Confirm any converted DDM ARXMLs and structured extract under Output/Config were created.

  • If issues occur, re-check paths in Scripts/config.* and Settings/*.json.

Next Steps

  • After you completed updating your input and other data files, proceed to linking your Vector tools, see Link Tools as well as the respective tool help for more information.