Hi,
You're on the right track with exploring different approaches to run your Simulink model from C++. Here's a breakdown of the limitations you encountered and some alternative solutions:
1. Using "sim" Command with Internal States:
The issue is that the sim command with a fixed stop time resets the model states. Here are some alternative approaches:
- State Updates: Instead of setting a stop time, use a zero-crossing detection block in your Simulink model to trigger a single simulation step. This block outputs a signal when a specific condition is met (e.g., a timer reaches a specific value). Connect the block's output to a stop simulation block to terminate the simulation after one step. Inside your C++ code, after retrieving the output, reset the trigger signal in the model (using "set_param") before providing new inputs for the next iteration.
- External Mode: Consider setting your model to "External" mode. This allows Simulink to run for one step whenever an external trigger is received. You can trigger the simulation step from your C++ code using "set_param" with SimulationCommand set to "update".
2. Simulink Debugger:
The debugger doesn't allow input port manipulation directly. However, you can combine it with other approaches:
- Set Breakpoint and Update Inputs: Set a breakpoint at the beginning of your model. In the C++ code, use "set_param" to update the input values before resuming the simulation using the debugger. This allows you to inspect the model state after one step but requires manual intervention.
3. set_param with ExternalInput:
The challenge here is that ExternalInput doesn't update dynamically. Here's a potential solution:
- Temporary Model Modification: Consider temporarily modifying your Simulink model within your C++ code. You can create a copy of the original model, update the ExternalInput data, run the simulation with set_param commands, and then discard the modified model.
Hope it helps.
