Why does the Switch block produce incorrect results if it is driven by the output from a Selector block in Simulink 5.1 (R13SP1)?

This problem occurs if the input to the Selector block is constant.

Answer 1

[MathWorks Support Team]

This bug has been fixed for Release 14 (R14). For previous releases, please read below for any possible workarounds:

This has been verified as a bug in Simulink 5.1 (R13SP1) in the way that the Switch handles an input from a Selector block.

Currently, to work around this issue, make sure that the input to the Selector block is not constant. For example, if the input is from a Constant block, make the constant value tunable.