Multi-Version Co-Simulation for Simulink

Integrate Simulink models for different release versions for co-simulation

As your models become more complex, they may consist of components from different Simulink versions. Under certain conditions, upgrading all components to the same version may not be feasible, and you may require a method to co-simulate these diverse components from varying Simulink versions. This support package is designed specifically for this purpose. With this support package, you can co-simulate different models from various versions (the previous 6 releases are tested for backward compatibility) using multiple MATLAB sessions.

When to use this support package:

• Existing models that are qualified in a previous version.
• Models with a significant computational load.
• Given each model runs in its own MATLAB session, the component must be substantial enough to justify the cost of another MATLAB instance.
• Need to resolve workspace and path clashes.
• Need to debug child models in the previous version.
• Child models that don’t support code generation.

Multi-version co-simulation requirements:

• Specific MATLAB version needs to be preinstalled on your machine for tool coupling co-simulation
• Components must support model reference.
• Runs as a single instance in its own session.
• All data exchange occurs through root IO ports.
• Data exchange is at fixed intervals.
• Continuous signals should use numerical compensation.
• Parameters are specified through model arguments.
• Data Store Read/Write does not cross into the parent.
• Function calls do not call into the parent.

Link to documentation: https://www.mathworks.com/help/simulink/ug/perform-multiversion-co-simulation.html

Note: If only version compatibility is needed, you may consider using a protected model, which typically runs faster than multi-version co-simulation. FMU export is recommended when using Simulink models in other 3rd party tools.