Hi Samuel,
I understand that you have implemented a finite state machine using Stateflow within a Simulink model. Simulink States provide a convenient way to represent operating modes and transition between them.
Regarding your concern about accessing Simulink subsystem state variables, it is understandable that using a “Delay” block as a workaround might feel like a hack. And I also understand your concern about using a “Data Store Memory” block and the potential messiness it may introduce, especially if you want to keep the variable local to each state. While there isn't a dedicated "Internal State Data” block in Simulink, there are alternative approaches you can consider:
- Simulink Bus objects: You can create a “Simulink Bus” object that contains all the variables you need for your internal state. Each state can have its own instance of the bus object, allowing you to keep the variables local to each state. You can then use “Simulink Bus Selector” blocks to access the specific variables you need within each state. https://www.mathworks.com/help/simulink/ug/when-to-use-bus-objects.html#brin2jr-1
- Simulink Function blocks: “Simulink Function” blocks allow you to define reusable functions that can be called from multiple locations within your Simulink model. You can create a “Simulink Function” block for each state and define local variables within each function block. This way, each state will have its own set of local variables. https://www.mathworks.com/help/rtw/ug/generate-code-for-a-model-with-simulink-functions.html
- S-Function block: If you require more flexibility and control over the internal state variables, you can consider using a MATLAB “S-Function” block. S-Function blocks allow you to write custom C or MATLAB code to implement your state machine logic. You can define and update your internal state variables directly within the “S-Function” block’s code. https://www.mathworks.com/help/simulink/sfg/what-is-an-s-function.html
I hope this helps.
