A state machine is a behavioral model. It consists of a finite number of states and is therefore also called a finite state machine (FSM). Based on the current state and a given input, the machine performs state transitions and generates outputs.
A single state chart may become very large and complex. embedded systems may consist of many state machines and other components. To understand the behavior of state machines within their execution context and their impact on the overall behavior of a system, the application of execution analysis and visualization are a proper way to gain this understanding.
This extension enables the simulation and visualization of YAKINDU state chart models.
It helps users to create a state machine model (simulation with reference data) and to execute and trace the created state machine.
impulse YAKINDU is availabe with impulse 2.1.x.
With the State Chart Simulator Production you can feed YAKINDU State Chart models with reference data and display the result of the simulation in diagrams and charts.
Instead of a step-by-step procedure, the simulation is carried out in one go.
The simulator can be fed with reference or with online data. This allows to test the behaviour of the statemachine with real process/application data.
With the expandable concept of signal ports, any signal source can be connected. This can be simple data connections over TCP, UDP using a configurable reader, external libraries, CAN Bus adapter or complex hardware interfaces.
To enable model-level debugging of the state machine implementations, YAKINDU generated code can be instrumented to generate so called YET (YAKINDU Execution Trace) traces.
Capture online or offline traces from the executable (e.g., embedded device) and visualize them with the state chart and other plots.
YAKINDU Statechart Tools (itemis) offer an integrated modeling environment for the specification and development of reactive, event-driven systems based on the concept of state machines. The State Chart production simulates YAKINDU state chart models and generates a signal with the resulting state and variable information.
Platforms: |
|
|||
Requirements: |
|
|||
Known limitations: |
|
|||
Status: |
|
|||
Input signals: |
|
|||
Output signal: |
|
|||
Parameters: |
|
|||
Tutorials: |
YAKINDU Statechart Tools (itemis) offer an integrated modeling environment for the specification and development of reactive, event-driven systems based on the concept of state machines. The state chart plot allows the display of the current states (on- or offline data) at the current cursor position.
Platforms: |
|
|||
Requirements: |
|
|||
Known limitations: |
|
|||
Status: |
|
|||
Extensibility: |
|
|||
Supported signal types: |
|
|||
Chart Parameters: |
|
|||
Plot Parameters: |
|
|||
Tutorials: |
YAKINDU Statechart Tools (itemis) offer an integrated modeling environment for the specification and development of reactive, event-driven systems based on the concept of state machines. The YET (YAKINDU Execution Tracing) format is a text format for the output of information generated by state charts.
Platforms: |
|
|||
Requirements: |
|
|||
Known limitations: |
|
|||
Status: |
|
|||
Operations: |
|
|||
Parameters: |
|
|||
Configuration: |
|
|||
Tutorials: |