Major Changes Between DaVinci Configurator Classic Version 5 and DaVinci Configurator Classic Version 6

This chapter highlights the major changes between DaVinci Configurator Classic Version 5 and DaVinci Configurator Classic Version 6. It explains which core concepts have been updated, why these changes were made, and how they affect your workflow. Understanding these differences will help you adapt quickly and take full advantage of the new capabilities in the latest version.

Project Creation

The project creation process is now fully supported through the CLI, providing a streamlined and efficient way to initiate projects. The graphical user interface has been simplified and now only allows users to create empty projects. Additional workspaces beyond the one from DaVinci Configurator Classic are not created automatically. Instead, connections to other workspaces must be established manually via references.

The project structure has been redesigned, and project settings are no longer configurable through the graphical user interface but are edited directly in JSON files. This shift enhances transparency and control over project configurations.

Input File Processing

The input file process has been fundamentally redesigned to improve transparency and flexibility. The former Input File Assistant, previously tied to the graphical user interface, is now decoupled and enables cacheable steps. This approach ensures that each user action is explicit and traceable.

To prepare ECUC extracts, the new tool EcuXPro is introduced. It handles all preprocessing tasks, including variant extraction, before the data can be derived in the Configurator. By separating these steps, the workflow becomes more structured and easier to automate, while maintaining full control over the input data preparation.

Interactions with DaVinci Developer Classic

This section outlines the workflow boundaries and design responsibilities between DaVinci Configurator Classic Version 6 and DaVinci Developer Classic.

Starting with DaVinci Configurator Classic Version 6 no longer invokes functionality from DaVinci Developer Classic. This separation significantly improves flexibility, transparency, and maintainability in tool execution. DaVinci Configurator Classic Version 6 is now focused exclusively on ECUC modeling and the configuration of associated service components. All activities related to Software Component design remain the responsibility of DaVinci Developer Classic, ensuring a clear division of tasks and streamlined processes.

General Interaction

Due to the distinct use cases of DaVinci Developer Classic and DaVinci Configurator Classic Version 6, there is now a clearer separation between SWC Design and BSW Config. That means, SWC Design modeling shall not be done in DaVinci Configurator Classic Version 6 anymore, and its responsibility is taken over by DaVinci Developer Classic.

However, DaVinci Configurator Classic Version 6 provides possibilities to create service software components and corresponding connections in GUI, as well as extensive possibilities in SWC Design via Automation Interface. Since some model parts are highly dependent on the BSW configuration (e.g. service components) it will not be moved completely into DaVinci Developer Classic.

Since both tools can provide modeling approaches to the user, it is important to think about file handling and file priorities. Therefore, the following conditions will apply:

  • SWC Design created within DaVinci Configurator Classic Version 6 will be read-only in DaVinci Developer Classic.

  • SWC Design created within DaVinci Developer Classic will be read-only in DaVinci Configurator Classic Version 6.

These principles are realized on file level where both tools have their own files which are known by the other tool. Furthermore, it is important to shortly mention that both tools are now working on the same model level. That means, DaVinci Developer Classic and DaVinci Configurator Classic Version 6 are modeling on the Structured Extract. In contrast, the structured model (containing composition hierarchy) was flattened out by DaVinci Configurator Classic Version 5, and all modifications made within DaVinci Configurator Classic Version 5 have been populated on the Flat Extract without being noticed by DaVinci Developer Classic.

Service Components and Connections

In DaVinci Configurator Classic Version 6, service component prototypes and service connectors created in DaVinci Configurator Classic are now visible in DaVinci Developer Classic, providing a more complete view of the SWC design. However, objects created in other tools remain read-only in DaVinci Developer Classic. After migration, data mappings, software components, or connections from DaVinci Configurator Classic Version 5 may no longer be editable in the GUI.

Available editing options:

  • Manual changes at ARXML file level

  • Scripting via Automation Interface

OEM input is read-only from tooling perspective. Scripting can be used as a pre-processing step.

Migration of application components (including connections) into the DaVinci Developer Classic workspace is not supported by any tool functionality.

Variant Handing

If an updated Evaluated Variant Set is loaded with a DaVinci Developer Classic workspace, three use cases can occur relative to the content of the last loaded EVS file version:

  • variants are added,

  • variants are deleted, or

  • values are changed.

In the case of an added variant, the user will be able to choose the new variant for variation points. A deleted variant which was already used in the model can cause unwanted behavior and variation points can be marked as invariant.

Contract Header and Implementation Template Generation

Even if the Contract Header und Implementation Template Generation is already supported by DaVinci Configurator Classic Version 6, the current versions of DaVinci Developer Classic will still contain DaVinci Configurator Classic Version 5 components as part of the installation.

Explore More Capabilities

Discover some of the latest enhancements and updates that bring new capabilities and refinements to existing features.

Comparison Mode

The new Non-GUI Comparison Mode allows you to merge a DaVinci Developer Classic workspace without opening the tool, enabling faster and automated workflows. Additionally, .dvjson format is now supported for this process. With DaVinci Configurator Classic Version 6, DaVinci Developer Classic is no longer invoked during this operation.

Support Request Package

If you need assistance, you can send our support team a SRP, which can be triggered directly in DaVinci Configurator Classic Version 6.

For details, see: Get Help.

If providing DaVinci Developer Workspace data is required, the files must be manually packaged from the file system.

Model Consistency Checks

To verify the SWC design and detect inconsistencies within the DaVinci Developer Classic workspace, you can use the terminal command. With this change, the responsibility for validating SWC design has shifted to DaVinci Developer Classic.

Workspace Conversion

The workspace conversion is necessary to apply the Extendable External workflow.

Please make sure that you have clarified your need to switch to the Extendable External workflow with chapter 4.4 before using it.

It converts the DaVinci Developer Classic workspace so that model objects from the OEM input will be part of the ECU Extract exclusively and will not be present as duplicates in the DaVinci Developer Classic model.