wiki:features
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
wiki:features [2012/10/22 19:58] – pmueller | wiki:features [2022/12/22 08:06] – webmin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Features ====== | + | ~~NOTOC~~ |
- | ===== Overview | + | ====== Features |
- | A statechart | + | A state machine diagram |
- | {{: | + | {{: |
- | An important aspect of statecharts | + | An important aspect of state diagrams |
- | SinelaboreRT was built especially for embedded real-time developers. It focuses on just one task: code generation from state-chart | + | SinelaboreRT was built especially for embedded real-time developers. It focuses on just one task: code generation from state diagrams. A command line tool and a configuration file is all what is needed. |
The generated code is based on nested switch/case and if/ | The generated code is based on nested switch/case and if/ | ||
Line 18: | Line 18: | ||
<code bash> | <code bash> | ||
- | java -jar codegen.jar -p CADIFRA -o oven.cdd | + | java -cp " |
</ | </ | ||
Line 32: | Line 32: | ||
- | ===== Supported State Chart Elements ===== | + | ===== Supported State Diagram Design |
**Hierarchical state definition**: | **Hierarchical state definition**: | ||
+ | |||
+ | ** Regions **: Regions allow to model parallel behavior within the same state machine diagram. The benefit of using regions is to explicitly show the this parallel behavior instead of creating different state diagrams. | ||
**Transitions**: | **Transitions**: | ||
Line 46: | Line 48: | ||
**Interactive Test and Simulation**: | **Interactive Test and Simulation**: | ||
- | {{: | + | {{: |
**Debugging / Trace Support**: In the *_dbg.h file two helper functions are provided that are useful for debugging state machines. The function *_GetNameByState(id) returns the name of the state the function *_GetNameByEvent(id) returns the name of an event each identified by its id. Trace statements can be automatically added to the machine. This allows to follow the flow of events. | **Debugging / Trace Support**: In the *_dbg.h file two helper functions are provided that are useful for debugging state machines. The function *_GetNameByState(id) returns the name of the state the function *_GetNameByEvent(id) returns the name of an event each identified by its id. Trace statements can be automatically added to the machine. This allows to follow the flow of events. | ||
- | **Integrated State-Diagram Editor**: Using the command line flag '' | + | **Integrated State-Diagram Editor**: Using the command line flag '' |
- | [[wiki: | + | [[wiki: |
wiki/features.txt · Last modified: 2023/03/08 10:14 by webmin