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 functioning of 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 in preparing the automation scenario, it is necessary to hold the dotted arrow from the boundary of the first state to the boundary of the following state.
Dimensions of the each state and the transition can be regulated by dragging the bottom right corner. If the box of state or transition are increased in a certain way, not only the enter 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 certain state, it is enough to choose the position in the state itself, whether this action must be performed on enter in the state or on exit from it. By clicking on chosen button, the full list of commands and action opens, in accordance with specified model. This set includes both external software modules which are described in the 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 enter of on exit from the state.
In preparing the transition between two states, firstly, it is necessary to add the event which must happened for building of the transition and, following that, the condition under which the transition occurs. The events and the conditions are added in a same way as the action on enter 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. For creation of the transition with the several events, it is necessary to use the intermediate states.
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.
In order to start the scenario of automation, it is necessary to assign the one or several objects to it. The objects are launched in the "Objects" tab. There can be opened the full list of created objects any one from which can be assigned to the current final state machine. If necessary, by using special buttons, there may be chosen all objects or no one.
After the objects have been launched, they appear in this tab and are displayed as a list. In the current menu the scenario can be started or stopped on all three objects together. The starting of the automation scenario is indicated via the green line displaying under every object.
However, it is able to view the binding of the scenario to the objects not only in the "Logic" menu. When switching to the "Objects" menu, in the "Automatons" tab, there is able to view a list of all final state machines that have been assigned to the current object or assign them to the new ones. Furthermore, the user can manage the processes of starting and stopping of the automation scenario in any time, remove it if desiring or just view its structure.