When a Simscape network has direct feedthrough, it creates an algebraic loop. Typically, the Simulink algebraic loop solver can solve these models without an error. However, the algebraic loop solver cannot solve algebraic loops that contain Stateflow charts. In this case, the Stateflow chart is involved in the algebraic loop.
For a system with discrete signals:
You could work around this error by introducing a delay to the outputs of the Stateflow chart with the "memory" block. The memory block outputs the input from the previous time set. This single-step delay breaks the algebraic loop, and eliminates the source of the error. To read more about the memory block, see the documentation page linked below:
It is worth noting that adding a delay to many signals could cause the simulation to slow down significantly and affect the results. Therefore, it is best to only add delay to the signals causing the algebraic loop. In this case, that means only putting a memory block after the outputs of the Stateflow chart, and not in the larger feedback signal from the physical model subsystem to the control subsystem.
For a system with continuous signals:
As recommended in the following article, do not break the loop with a memory or delay block.
This will introduce discrete signals into an otherwise continuous system, which can increase the potential for incorrect results as well as slow simulation speeds. Instead, use a simple first-order transfer function with a small time constant. The following documentation example also demonstrates this workaround (see the Cycle Manifold subsystem).
Best Answer