I understand that you are facing issue while controlling the execution of a Simscape model using a Triggered Subsystem, but as you mentioned, there might be conflicts with the solver configuration block. Here are a few alternative methods you can consider:
- Function-Call Subsystem: Instead of using a Triggered Subsystem, you can use a Function-Call Subsystem to control the execution of your Simscape model. You can create a custom function that triggers the subsystem's execution and incorporate it into your simulation workflow.
- Simulink Control Signals: You can control the execution of a Simscape model using Simulink control signals such as enable/disable signals. You can use Signal Routing blocks or control logic to enable or disable specific parts of the model based on your requirements.
- Simulation Callbacks: Utilize Simulink's simulation callbacks to define custom behaviour before and after simulation steps. You can create functions to control when and how the simulation progresses.
Refer to this documentation for more information:
