Simcenter 3D Solutions About Simcenter 3D Motion Model Export

Introduction

This functionality allows you to export Simcenter 3D Motion mechanism models to be executed in outside integration environments or within real-time applications and it's ideal for sharing expert authored models with consumers in other teams or at suppliers.

The license to Export the model is checked during the export process from the Simcenter 3D Motion environment, and then not checked at runtime on a consumer machine.

Software and licensing requirements

• Enabled by the SC30577 Simcenter 3D Motion Model Export license.
• In terms of software version, this functionality works with Simcenter 3D 2212, 2306 (and future versions).
• Visual Studio C++ 2019 compiler.
• MATLAB (refer to Simcenter 3D Motion – MATLAB/Simulink compatibility matrix )
  • MATLAB 2019b (patched with Visual Studio 2019 support) is required for integration with Concurrent.

Using the Simcenter 3D Motion Model Export feature

Whilst the Simcenter 3D Motion Model Export setup and workflow resemble the Co-simulation ones, there are key differences between the two scenarios.

To highlight these differences, that will be mainly observed in the Solution settings, we shall look into two of the interfaces with whom Simcenter 3D Motion can interact with:

• MATLAB/Simulink
• FMI/FMU

• Simcenter Amesim
• Procyon
• Concurrent
• dSPACE DS1006
• dSPACE SCALEXIO

Model preparation

In terms of preparing a Simcenter 3D Motion model for a Model Export scenario, the steps to follow are identical to a Co-simulation scenario.

1. Create Control Inputs to measure or extract specific Motion data from the model (displacement, velocity, etc.) and store those into Control Ports.
2. Create Mechatronics Interface with input ports (from Motion) and output ports (from external software).
   • Note that the Mechatronics Interface will be of type Export.
3. Create Control Outputs that will use the signals from the Mechatronics Output Ports and apply them as forces, torques in the Motion model.

Solution settings, packaging, and running

In the Solution settings, Analysis Options, we will follow with defining our objective and platform:

• Objective: Export to External Platform (Fig. 1.1)
• External Platform: FMI or Simulink (Fig. 1.2)

Fig. 1: Solution setting - Analysis Options

    
Once we pick the export format, the next important option is related to the Motion Solver integration method and packaging. These options are defined in the Dynamic Properties of the Solution settings. (Fig. 2)

1. Integration Method = BDF
   • This option will use the variable step BDF solver, leading to a standard Co-simulation scenario.
   • Model Export license is not needed.
   • Motion Solver installation is required on the target machine.
   • Motion Solver (and other) licenses will be required at runtime.
2. Integration Method = Real-time BDF (Fig. 2.1)
   • This option will use the fixed step BDF solver.
   • Model Export license is required and checked during export.
   • Other Motion licenses (or tokens) will be required during export depending on the features and elements that are present in your Motion mechanism.
   • Packaging option can be set through the Compile setting (Fig. 2.2), which specifies whether the solver input file is compiled into the interface block.
     • (a): Compile = NO - you can solve the exported model in the external platform independent of the original Simcenter 3D model.
     • (b): Compile = YES - you can solve the exported model in the external platform only when the original Simcenter 3D model resides in its original location.
   • Target environment requirements:
     • No Motion Solver installation is required on the target machine.
     • No licenses will be required at runtime.

Fig. 2: Solution setting - Dynamic Properties

Conclusion

As mentioned in the introduction and highlighted in the packaging and running notes, the major advantage of the Simcenter 3D Motion Model Export feature is that licenses are only checked during the export process from the Simcenter 3D Motion environment, and then not checked at runtime on a consumer machine.
The export process can package the Motion model in various formats, for different supported platforms, such as:

• Simcenter Amesim
• MATLAB/Simulink
• FMI
• Procyon
• Concurrent
• dSPACE DS1006
• dSPACE SCALEXIO