FAQ 323: ConfigurationDesk/Bus Manager Migration Principles

Question

I would like to migrate an existing ConfigurationDesk/Bus Manager project. Is the intended migration step supported? Why do I get the following error message?

An exception occurred while loading the application:
Missing Plugins:
<plugin name> (version '<plugin version>')

OR

Error in project handler: The serialized data to be loaded satisfies version ‘X.Y' of model part <module name>. This version is newer than the version currently held by the data kernel ... .

Solution

The reported error message usually appears if the respective ConfigurationDesk Project has been stored with a different ConfigurationDesk/Bus Manager Version.

Imagine the following Situation. A ConfigurationDesk project has been set up und stored with a particular ConfigurationDesk variant, e.g., ConfigurationDesk 22.1p1. The following situation will appear if the project will be opened with ConfigurationDesk 22.1 without the patch.

It is recommended using identical ConfigurationDesk/Bus Manager variants, that match with the related  frameworks and plugins.

The FAQ lists some major principles when applying a migration step to a ConfigurationDesk/Bus Manager project.

The following principles needs to be considered:

1. A saved ConfigurationDesk/Bus Manager project can be opened without problems, if identical ConfigurationDesk/Bus Manager variants are used for storing and opening.
2. A project downgrade is not supported. ConfigurationDesk does not offer a “Save as” feature (as known to MATLAB users) to convert a stored ConfigurationDesk/Bus Manager project to a version prior to the currently used ConfigurationDesk/Bus Manager variant.
   For example, a ConfigurationDesk project stored with ConfigurationDesk 6.7 cannot be saved in a compatible version for handling the project with ConfigurationDesk 6.5.
3. A migration scheme is implemented for subsequently released ConfigurationDesk/Bus Manager variants. For example, you can open a project stored with ConfigurationDesk 6.7p2 with ConfigurationDesk 6.7p3 or 6.7p4.
   But there might be migration step gaps when you switch between ConfigurationDesk variants belonging to different dSPACE Releases. The release timeline is essential for the migration scheme.
   The migration step from ConfigurationDesk 6.7p4 (as part of dSPACE Release 2021-A) to ConfigurationDesk 22.1 (as part of dSPACE Release 2022-A) is not possible, because ConfigurationDesk 6.7p4 has been released after the release date of ConfigurationDesk 22.1.
   Please refer to the migration diagrams available at Bus Manager Compatibility
4. A Hotfix, Patch or Service Pack might affect the migration scheme. It could be possible that a Hotfix, Patch or Service pack increases a plugin version. Consequently, it could be possible that you cannot migrate to a subsequent ConfigurationDesk variant temporarily.