It appears that there is now a bug with the Stateflow FSM code generation in Simulink when two FSMs are directly connected. If the names of the ports differ, the destination FSM's port name may be changed in the emitted Input Structure created by Simulink Coder. This appears to be a Matlab bug but I can investigate further.
A workaround is to insert a dummy node between the FSMs (ex. a delay with 0 delay).
It appears that there is now a bug with the Stateflow FSM code generation in Simulink when two FSMs are directly connected. If the names of the ports differ, the destination FSM's port name may be changed in the emitted Input Structure created by Simulink Coder. This appears to be a Matlab bug but I can investigate further.
A workaround is to insert a dummy node between the FSMs (ex. a delay with 0 delay).