FSM Semantic Limitations

FSM state slave models and all related properties are not supported.
To avoid additional code overhead, the code generator does not implement the current state memory as well as the associated current state enumeration data structure of instantiated FSM models.
Only internal event elements are supported for FSM models, used to represent local and typeless asynchronous timer events.
In case of a single FSM model is directly used as generator input model, it must not contain external memory elements.
The set of supported action statements is restricted in terms of unsupported design elements and data types.

Significant features of the MLDesigner FSM semantic

Feature	Supported	Comment
Input Ports	yes
Output Ports	yes
Internal Memories	yes
External Memories	limited	not supported in case of single FSM input models
Internal Special Events	yes	considered as local and typeless asynchronous timer events
External Special Events	no
Internal Events Property	no	related to state slave models
Parameters	yes
Current State Memory	no
Current State Data Structure	no	related to current state memory
State XOR-Decomposition	yes
State Slave Model	no
State Logical Name	yes	used for FSM debugging
State Entry Action	limited	depends on supported statements
State Exit Action	limited	depends on supported statements
Transition Event Expression	yes
Transition Guard Expression	limited	depends on supported statements
Transition Action	limited	depends on supported statements
Transition Label	no	not required
Transition Preemptive Flag	no	related to state slave models
Transition Entry Type	no	related to state slave models
Static History States	yes
Recursive History States	yes
Default Entrance Action	limited	depends on supported statements
Additional Code Property	no

Built-in Function	Supported
CancelEvent	only with integer event ID
EventIsScheduled	yes
EventResidualTime	yes
ReadCurrentEvent	no
ScheduleEvent	only with 3 arguments and integer event ID