Package Modelica.​StateGraph.​Examples
Examples to demonstrate the usage of the components of the StateGraph library

Information

This icon indicates a package that contains executable examples.

Extends from Modelica.​Icons.​ExamplesPackage (Icon for packages containing runnable examples).

Package Contents

Model Modelica.​StateGraph.​Examples.​FirstExample
A first simple StateGraph example

Information

This icon indicates an example. The play button suggests that the example can be executed.

Extends from Modelica.​Icons.​Example (Icon for runnable examples).

Model Modelica.​StateGraph.​Examples.​FirstExample_Variant2
A variant of the first simple StateGraph example

Information

This icon indicates an example. The play button suggests that the example can be executed.

Extends from Modelica.​Icons.​Example (Icon for runnable examples).

Model Modelica.​StateGraph.​Examples.​FirstExample_Variant3
A variant of the first simple StateGraph example

Information

This icon indicates an example. The play button suggests that the example can be executed.

Extends from Modelica.​Icons.​Example (Icon for runnable examples).

Model Modelica.​StateGraph.​Examples.​ExecutionPaths
Example to demonstrate parallel and alternative execution paths

Information

This is an example to demonstrate in which way parallel activities can be modelled by a StateGraph. When transition1 fires (after 1 second), two branches are executed in parallel. After 6 seconds the two branches are synchronized in order to arrive at step6.

Before simulating the model, try to figure out whether which branch of the alternative sequence is executed. Note, that alternatives have priorities according to the port index (alternative.split[1] has a higher priority to fire as alternative.split[2]).

Extends from Modelica.​Icons.​Example (Icon for runnable examples).

Model Modelica.​StateGraph.​Examples.​ShowCompositeStep
Example to demonstrate parallel activities described by a StateGraph

Information

This is the same example as "ExecutionPaths". The only difference is that the alternative paths are included in a "CompositeStep".

Extends from Modelica.​Icons.​Example (Icon for runnable examples).

Model Modelica.​StateGraph.​Examples.​ShowExceptions
Example to demonstrate how a hierarchically structured StateGraph can suspend and resume actions on different levels

Information

CompositeStep "compositeStep" is a hierarchical StateGraph consisting of two other subgraphs. Whenever component "compositeStep" is suspended, all steps with in "compositeStep" are deactivated. By entering "compositeStep" via its "resume" port, all steps within "compositeStep" are activated according to their setting before leaving the "compositeStep" via its "suspend" port.

Extends from Modelica.​Icons.​Example (Icon for runnable examples).

Model Modelica.​StateGraph.​Examples.​ControlledTanks
Demonstrating the controller of a tank filling/emptying system

Information

With this example the controller of a tank filling/emptying system is demonstrated. This example is from Dressler (2004), see Literature. The basic operation is to fill and empty the two tanks:

1. Valve 1 is opened and tank 1 is filled.
2. When tank 1 reaches its fill level limit, valve 1 is closed.
3. After a waiting time, valve 2 is opened and the fluid flows from tank 1 into tank 2.
4. When tank 1 is empty, valve 2 is closed.
5. After a waiting time, valve 3 is opened and the fluid flows out of tank 2
6. When tank 3 is empty, valve 3 is closed

The above "normal" process can be influenced by three buttons:

• Button start starts the above process. When this button is pressed after a "stop" or "shut" operation, the process operation continues.
• Button stop stops the above process by closing all valves. Then, the controller waits for further input (either "start" or "shut" operation).
• Button shut is used to shutdown the process, by emptying at once both tanks. When this is achieved, the process goes back to its start configuration. Clicking on "start", restarts the process.

Extends from Modelica.​Icons.​Example (Icon for runnable examples).