Hi Khaled,
It would be helpful if you can share the model that is causing the said issue. Stop Simulation block as per the documentation supports Code generation. When translated into code, this block operates through a boolean variable alongside a set of getter and setter functions. It's important to note that the Stop Simulation block will not halt the execution within the current active timestep. Instead, it completes the ongoing timestep's execution and prevents any further timesteps from being executed.
This behavior is mirrored in the code that's generated. Within the step function, the setter function is utilized to mark the boolean variable as true. However, the function doesn't terminate immediately but completes its planned execution. It is then the job of the main function to regularly check, via the getter function, whether the Stop Simulation boolean was set to true in the preceding run. Based on this check, the main function makes the decision on whether to proceed with invoking the step_function.
I recommend generating the code to examine the main.c and model.c files directly. This will allow you to see how the Stop Simulation functionality is implemented in practice.
Refer to the following documentation to know more about the Stop Simulation block:
Hope this Helps!
