DaVinci Project Settings

The settings are now stored in a JSON-based format, providing a structured and flexible way to manage configuration. Editing is supported through an integrated schema, ensuring validation and guidance.

IDE Support and Extensions

These settings include essential project details such as directories and file locations, references, generator-related options, input file configurations, and overall tool preferences.

General Settings

The General.json settings file contains key configuration entries that define the overall structure and behavior of your project. It includes references to workspaces, ECUC settings, environment details, generation options, and additional project-specific parameters. By editing this file, you can customize how the project integrates with other tools, manages output directories, and applies specific use cases or post-build options.

Table 1. Content of General.json
Configuration Area	Description
Project Name & Version	Define the project name and version for identification.
References	Set the path to the DaVinci Developer Classic workspace.
Script Locations	List of scriot locations.
ECUC Configuration	Configure the active ECUC root package and ECUC splitter options.
Environment	Define target platform details such as compiler and derivative.
Module-Specific Derivatives	Add specific derivatives for individual modules.
Post-Build Support	Enable or disable post-build loadable and selectable support.
Project Type & Target	Specify project type and target type.
Use Cases	Activate specific use cases.
External File Supervision	List supervised files with ID, hash, and path for integrity checks.
Folder Paths	Configure output directories for: Generated module files, Virtual target files, Logs, Measurement/calibration data, Source templates, Sync job data, Trace files.
Miscellaneous	Define A2L generator settings, debug data generation, and additional parameters.
Post-Build Loadable	Set configuration phase and RTE data freeze details.
SWC Template Generation	Configure generation mode and component list.
Variance	Define evaluated variant set with AUTOSAR path.
Merge & Collaboration Flags	Control unsafe transaction marker and merge conflict handling.

Input File Processing Settings

The Ifp.json settings file defines project-specific configurations for AUTOSAR-based communication module definition settings, allowing users to control special derivations for LdCom and ComM, communication controller assignments and module definition mappings.

Table 2. Content of Ifp.json
Configuration Area	Description
Communication Controller Mappings	Maps communication controllers to clusters. Essential for defining communication topology.
Derivation	Sets the derivation version. Used for compatibility with AUTOSAR versions.
Module Definition Mappings	Maps module configurations to AUTOSAR module definitions. Critical for ensuring correct linkage between configuration and implementation.

See Set Input File Processing Settings for more details how and when to configure these settings.

Generator Settings

The Generator.json Settings file defines how the generator behaves, including which modules to generate, the execution order of external steps, target environments, and validation options. It allows users to customize generation workflows and integrate additional tools or scripts.

Table 3. Content of Generator.json
Configuration Area	Description
Automatic On Demand Validation	Controls whether validation runs automatically when generation is triggered. Useful for ensuring configuration consistency without manual validation.
External Generation Step Order	Defines the execution order of external generation steps. Helps organize complex generation workflows.
External Generation Steps	Configures custom external generation steps, including command line calls, execution type, and transformation settings. Enables integration of additional tools or scripts.
Generation Target	Specifies the target for generation: `Real Target`, `Virtual Target`, or both. Determines where generated artifacts will be applied.
Generators Without Module Definition	Indicates which generators without a module definition reference should be executed by default. Useful for handling special generators.

Arxml File Settings

The ArxmlProjectContent.json setting file defines all directory and file locations for ARXML resources that DaVinci Configurator Classic Version 6 loads. It specifies which ARXML files and folders should be included in the project.

Table 4. Content of ArxmlProjectContent.json
Configuration Area	Description
Application Component	Define directories for application component description files.
Additional BSW Packages	Specify locations for extra BSW-packages.
Definition Restrictions	Configure restrictions for definitions within the project.
ECUC Configuration	Set the active ECUC configuration file. Include external ECUC files from other projects (read-only). Add recommended user-authored ECUC files. Configure ECUC splitters.
FlatMap and FlatExtract	Define files for FlatMap and FlatExtract configurations.
IFP Files	Configure initial ECUC, recommended IFP ECUC, diagnostic ECUC, and harmonized extract files.
Internal Behavior	Set the directory for internal behavior description files.
Platform Types	Define the location for standard AUTOSAR platform type files.
Software Components	Specify directories for service component description files.
Structured Extract	Configure internal and external structured extract directories.
Timing Extensions	Add directories for timing extension configurations.
Variance Configuration	Define the file for variance settings.

Acknowledgement Settings

This file contains acknowledgements for validation messages.

This file is not intended for manual editing.

Table 5. Content of Acknowledgement.json
Configuration Area	Description
com.vector.cfg.consistency	Root element for all acknowledgement data. Organizes entries for validation message acknowledgements.
ACK_*	Represents an individual acknowledgement entry. Each entry corresponds to a specific validation message that was acknowledged.
DESCRIPTION.ResultId	Stores the unique result ID of the validation message being acknowledged.
DESCRIPTION.Severity	Indicates the severity level of the validation message (e.g., Warning, Error).
DESCRIPTION.AcknowledgementComment	Contains a comment explaining why the message was acknowledged.
DESCRIPTION.IsOnDemand	Boolean flag showing if the acknowledgement was created on demand.
DESCRIPTION.ResultDescription	Provides a description of the validation result for reference.
Encoded.AcknowledgementDataEncoding	Specifies the encoding format used for acknowledgement data.

Miscellaneous Settings

This Misc.json file is used to store miscellaneous configuration data and acknowledgements.

Table 6. Content of Misc.json
Configuration Area	Description
Misc	Holds miscellaneous configuration entries. Useful for storing custom settings or feature flags as string or boolean values.
Acknowledgements	Stores acknowledgement data for validation messages. Typically used to track which messages have been acknowledged by the user or tool.
Nested Object Or String Or Boolean	Allows nested structures for complex settings. Enables hierarchical configuration without strict schema limitations.

Generate Schema Files

For every new DaVinci Project, schema files are automatically generated and referenced in the settings files. These schemas ensure that configuration entries are validated and provide extension support for project-specific and accurate data. If the BSW package changes during configuration, you must regenerate the schema files to maintain consistency and prevent errors.

Open the DaVinci Configurator Classic CLI and run the following command:

$ dvcfg-b project generate-schema -p="/Path/To/DaVinci/Project" -b="/Path/To/BSW/Package"

The generated schema files will be available in the /Output/Schema directory.