By designing a new automation scenario in the dialogue box of a final state machine creation, firstly, a name and a description of the scenario are entered, and the model is specified created in advance in which all parameters characterizing the operation of the connected device are set.
The new scenario will be created with a minimal set of elements in the working area.
Any scenario consists next elements:
|Initial state||Marking the start of scenario execution|
|State||Here specifies that actions must be performed on enter and exit from it|
|Transition||Here sets an event and a condition that must be fulfilled by transition from one state to another|
|Final state||Designation of the end of scenario execution|
In order to build the transition between the object states, the dotted arrow should be held from the boundary of the first state to the boundary of the following state.
Dimensions of each state and the transition can be regulated by dragging the bottom right corner. If the box of state or transition is increased in a certain way, not only the entry field for the name, but the description becomes available too.
Any transition or state can be deleted.
The toolbar is located in the bottom part of the editor working area.
|Name||Icon||Purpose and description|
|Editor (v1)||Editor of the version 1|
|Editor (v2)||Editor of the version 2. Interface of the second version differentiate from the first one contrastly, therefore, user is able to choose such editor that will be easier to work. Furthermore, the logic of the scenarios building will not change due to switching one editor to another, the scenario structure saves.|
|Code||The alternative presentation of the automation scenario in json format|
|Objects||Selection of the one or several objects on which the current final state machine should be started|
|Start||Start of the automation scenario on the selected object|
|Stop||Stop of the automation scenario on the selected object|
In the editor (v2) the next instruments are available:
|Name||Icon||Purpose and description|
|Save||Saving alterations in the final state machine|
|State||Adding a new state to the final state machine|
Not saved changes are not deleted during switching between the interface sections, but they may be lost if the page will be reloaded or closed.
In order to launch an action on a particular state, the position in the state itself should be selected, whether this action must be performed on entering in the state or on exit from it. By clicking on the chosen button, the full list of commands and action opens, in accordance with the specified model. This set includes both external software modules which are described in every model by default, and such commands which were added by the user. Precisely from this drop-down list box there are chosen such one or several commands that should be executed on entering of on exit from the state.
In preparing the transition between two states, firstly, it is necessary to add the event which must be occurred to build the transition and, following that, the condition under which the transition occurs. The events and conditions are added similarly to the action on entering and exit from the state. The full drop-down list box of the events is opened to the user. All events from the device model are available for selection: both the events existing in the model by default and the user-defined events.
By describing the transition between the states, only one event can be specified. The intermediate states should be used to create a transition with several events.
After the event selection, the transition condition is set, which is then saved. If necessary, it is possible to restore the previous condition and add the new one.