Just upgrade to a new version and it is compatible.
Simplified Migration
Cross-release compatibility saves effort on migration.
Enhanced Flexibility
Use the latest features when you need them.
Fewer Patches
Reduced number of patches and no more waiting time for bug fixes.
Long-Term Support
Use your current major Release while getting latest versions.
What is Cross-Release Compatibility?
With the new cross-release compatibility, you can easily upgrade to a new ConfigurationDesk or Bus Configuration Tools version. You can keep other products of your dSPACE tool chain untouched.
Beginning with the Release 2024-A, you can use newer ConfigurationDesk or Bus Configuration Tools versions in combination with other products of older dSPACE releases. This is valid for a time period of 2 years. This means that after that 2-year period, a new cross-release compatibility phase starts. Starting with Release 2026-A, the Ethernet Configuration Package, the DDS Configuration Tool, and the FlexRay Configuration Package also support cross-release compatibility.
Overall, just hop on the new ConfigurationDesk or Bus Configuration Tools version, enjoy the new features, and take advantage of the quicker availability of bug fixes. Also, do not worry about a full release migration. The compatibility to your dSPACE tool chain remains unaffected!
Simplified Migration
With cross-release compatibility, your migration path will be immensely simplified. Gone are the days when upgrading one dSPACE product required you to upgrade the whole tool chain. Instead, just install and use the latest versions of ConfigurationDesk or Bus Configuration Tools without having to worry about migrating all other dSPACE products as well. Your artifacts, such as project or container files from earlier versions, can still be reused with later versions even after the two-year period has expired.
Enhanced Flexibility
Just use the latest features when you need them. Cross-release compatibility allows you to easily use the latest features of ConfigurationDesk or Bus Configuration Tools without having to worry about compatibility and dependance on major Releases for a 2-year time frame. New releases are available to use as soon as the features are ready.
Reduced Number of Patches
4 releases a year are all you need. Thanks to cross-release compatibility, you are dealing with fewer patches that have to be installed. For this, it is recommended to follow the newest ConfigurationDesk or Bus Configuration Tools version as soon as it is available to get bug fixes and security fixes.
Long-Term Support
Once installed, you can use your current major Release while getting the latest versions of other products. Therefore, you can always stay up to date easily with new ConfigurationDesk or Bus Configuration Tools versions. The support and compatibility last for a two-year time period.
What does cross-release compatibility look like? What are future upgrade possibilities for ConfigurationDesk or Bus Configuration Tools ?
Base Release - What is it?
The base release describes the main release on which the rest of your dSPACE tool chain products are based and that you have installed on your system. This continues to follow the twice a year update scheme. Which base release you are using and especially, which Model Interface Package for Simulink (MIPS) version you have, determines which MATLAB versions are compatible.
The extensive tests of our tool chain ensure the compatibility with different products of the base release.
The following illustration shows an example of a 2026-A base release with following compatible MATLAB versions:
Example sequence of ConfigurationDesk versions:
Name of ConfigurationDesk Versions Release Date
ConfigurationDesk 2026-A (26.2) June 2026
ConfigurationDesk 2026-A (26.3) Aug. 2026 (intermediate)
ConfigurationDesk 2026-B (26.4) Nov. 2026
ConfigurationDesk 2026-B (27.1) Feb. 2027 (intermediate)
ConfigurationDesk 2027-A (27.2) May 2027
What are the license requirements?
To run a specific version of a product, the maintenance end date of the license(s) on the CmContainer must be later than the release date of the product version. The maintenance end date equals the end date of your Software Maintenance Service (SMS) contract.
When you purchase a product six months of SMS are included. The SMS period can be extended by a new SMS contract.
For new ConfigurationDesk or Bus Configuration Tools versions, you can find the minimum required maintenance end date (product release date) on the respective download page. Alternatively, check out FAQ 093 describing where to find the maintenance end date.
Stay tuned
You would like to find out what advantages are waiting for you with the cross-release compatibility?
Feel free to check out our ConfigurationDesk or Bus Configuration Tools updates page!
You will find the corresponding links below.
