Bug: Assignment blocks in iterator systems produce incorrect output in some cases
| Submitted | Product | Status | ||
|---|---|---|---|---|
| 2018-12-25 | Reactis for Simulink | Resolved in 2018.2.1 (released Feb 07, 2019; release notes) Resolved in 2018.0.3 (released Feb 07, 2019; release notes) Open in 2017.2.4 | ||
|
If an Assignment block located in an iterator (For/While) system is not executed in the first iteration, the value of the input signal at the first iteration is not properly captured. Instead the block uses "0" as the initial data value. | ||||