{{ post.title }}
글 편집
{{ post.author.name }}
Posted on
| Version | {{ post.target_version }} | Product |
{{ product.name }}
|
|---|---|---|---|
| Tutorial/Manual | {{ post.manual_title }} | Attached File | {{ post.file.upload_filename }} |
When perform the co-simulation using RecurDyn and Simulink, you may sometimes meet unexpected problem.
Usually, they are caused by the reasons as below.
- Path problem (All the related files must be located in the same folder)
- Host Problem (The settings must be set according to the host type (RecurDyn or Simulink)
In this article, the settings and procedures related to the Host type will be described.
For Co-simulation, there are Host and Client.
Host means the application which starts the simulation. (You can select it from [Communicator] - [Control] - [Simulink] in RecurDyn UI)
When RecurDyn is Host, you should start the simulation from RecurDyn, then RecurDyn launches Simulink and co-simulation is performed.
When Simulink is Host, you should start the simulation from Simulink, then Simulink launches RecurDyn and co-simulation is performed.
You should be careful about the below settings and procedures, then you may not meet any problem.
When RecurDyn is Host
- You must create 2 m files (one is for PIN/POUT information, the other is the file to launch Simulink)
- You must use the command 'makerd' to create the RecurDyn block in Simulink model.
- You must close Matlab/Simulink before co-simulation.
- You must start the simulation in RecurDyn.
When Simulink is Host
- You must create 1 m files (for PIN/POUT information)
- You must use the command 'rdlib' to create the RecurDyn block in Simulink model.
- You must close RecurDyn before co-simulation.
- You must start the simulation in Simulink.
