Bug: Mismatch between Simulator and simulation in Simulink due to delayed input value in Stateflow
| Submitted | Product | Status | ||
|---|---|---|---|---|
| 2025-12-10 | Reactis for Simulink | Resolved in 2025.2.1 (released Jan 19, 2026; release notes) | ||
|
Simulator does not match behavior of simulation in Simulink because a boolean input variable in a Stateflow chart has the value of the Simulink input from the previous step, not the current step. This occurs when the boolean input signal comes from a "Detect Increase" library block and the block and the chart are inside a function-call subsystem triggered by a top-level input. | ||||