Difference between revisions of "CoSimulation with Simulink"
(Created page with "==Workflow== The idea is to partition the whole model such that the IP protected S-function runs in Simulink and the rest of the model executes in SimWB. # Partition the mod...") |
|||
Line 3: | Line 3: | ||
# Partition the model such that IP protected S-functions that do not have source code into a separate model. | # Partition the model such that IP protected S-functions that do not have source code into a separate model. | ||
− | # Use the [http:// | + | # Use the [http://license.simwb.com/simwbdoc/UserManuals/MLToolkit/simwb_blocks_udp.html SimWB UDP blocks] in the above model and configure them such that data can be sent to and from the IP protected portion to SimWB. |
# Create another model that has rest of the logic and send it to SimWB using SimWB ML Toolkit. | # Create another model that has rest of the logic and send it to SimWB using SimWB ML Toolkit. | ||
# Use the NETIO I/O device to map the model input and output to the Simulink data configured in Step 2. | # Use the NETIO I/O device to map the model input and output to the Simulink data configured in Step 2. |
Latest revision as of 12:46, 24 October 2017
Workflow
The idea is to partition the whole model such that the IP protected S-function runs in Simulink and the rest of the model executes in SimWB.
- Partition the model such that IP protected S-functions that do not have source code into a separate model.
- Use the SimWB UDP blocks in the above model and configure them such that data can be sent to and from the IP protected portion to SimWB.
- Create another model that has rest of the logic and send it to SimWB using SimWB ML Toolkit.
- Use the NETIO I/O device to map the model input and output to the Simulink data configured in Step 2.