Simulink/Stateflow, and use of isInputDir​ectFeedthr​oughImpl

Does anyone know how to use isInputDirectFeedthroughImpl to report that the inputs are non-direct feedthrough?

I have several state-machines where I am trying not to re-author them. Switching to a Moore state-machine solves the problem. Yet, I just converted from state-based transitions to message-based to aid in mimicking an SoS architecture, where I use the messages to simulate the communication between the nodes of the SoS architecture. These same messages contain relevant information for the state-machine, albeit, following a Moore theme, the outputs are calculated in the State's actions. Yet, because of the use of messages - switching to Moore as the State Machine Type - produces the error for Messages.

I'm exploring if it's possible to set isInputDirectFeedthroughImpl for the State-Flow diagrams, as they are system objects. I could simply report back the inputs are not direct feedthrough.

Answer 1

[Sam Warner]

Btw - not possible -

what is possible is to use "ashow" with sldebug to obeserve if there are any algebraic loops in the implementation that might cause downstream conversion to software issues.

The best solution - convert to Moore.