Graphical User Interface for SMACHA¶
After launching the GUI the window will look as follows:
Overview of the SMACHA GUI
The GUI is divided into three parts. First, on the left side there is the block list and general functions. In the middle there is the block placement grid and on the right side there is the block parameter menu.
- The block list: Here, all loaded blocks are shown. They are either loaded from a local folder or from the SMACHA server. Double click adds a block to the block grid.
- General functions: Selected containers can be deleted, SMACHA script generated, the workspace can be saved/loaded and or the application can be terminated.
- Block grid: Any block from the block list can be added here by double clicking it. Selecting one block opens the parameter menu on the right side.
- Sequence starters: Any sequence must start at either the
- Blocks: A selected block. Selection opens the parameter menu on the right. Pressing
<Ctrl>allows the selection of multiple blocks. This opens the container menu instead of the parameter menu on the right side. Right click on a block removes the block and any of its connections.
- Parameter/Container menu Parameter menu or container menu is shown here.
The block list¶
This list shows all blocks, where one block resembles one SMACHA state. Double click adds the block to the block grid. The ROS launch file located in
src/smacha_gui/launch/gui.launch sets the option from where the blocks are loaded.
If the SMACHA server is set to
/smacha/templates as in the following example
<arg name="path_smachaservertemplate" default="/smacha/templates"/>
blocks will be loaded from there. Set it to an empty value, to ignore the server:
<arg name="path_smachaservertemplate" default=""/>
In this case, blocks will be loaded from the local hard drive. The GUI tries to locate all blocks in the local block folder:
<arg name="path_blocks" default="$(find smacha_gui)/blocks.conf"/>
To load blocks from the server and the local folder, please define the SMACHA server as shown in the first example and add the blocks to the variable
<arg name="path_blocks_alwaysload" default="[Robot0Start.conf, Robot1Start.conf]"/>
In this example, the blocks
Robot1Start are always loaded. They are the blocks, which define the start points of any sequence.
The buttons include:
- Delete Container: This button will remove a container from the block list. First, select the container in the list. Afterwards, this button will remove the container.
- Generate Code: This button will create SMACHA script based on the block sequences.
- Save: This will store the workspace to a user defined file.
- Load: This will load the workspace from a user defined file.
- Quit: This will terminate the application.
A new button is always placed on the first empty cell on the grid. The grid has a fixed size of 4x19 cells. Cells can be moved freely on the grid.
Any SMACHA state sequence starts at either
Robot1Start. Blocks, which are not connected to a sequence starting from any of those two blocks are ignored during SMACHA script generation. The blocks are loaded from the files
If one of the sequence starters is removed from the grid, it can be re-added by double clicking on it in the block menu. If multiple Starters for the same robot are present on the workspace, the most upper left is chosen.
<Ctrl> allows to select multiple blocks. This will open the container menu on the right side, which allows to combine the selected blocks to a container.
One block may have multiple outputs to allow branching, but must have only one input. A
Data connection allows to transfer results from one block to another.
Mandatory ROS services¶
The GUI depends on several ROS services.
The roscore can be started via
and opens a ROS server.
The SMACHA server can be started via
roslaunch industrial_solutions reconcell_smacha_server.launch
and it is used to load SMACHA templates, which act as blocks, and to create SMACHA script.
The mongo database can started via
roslaunch mongodb_store mongodb_store.launch
and it is used to load additional block parameters.
The rosapi can started via
rosrun rosapi rosapi_node
and it is used to load a list of ROS services and their corresponding service parameters.
Adapting the launch file¶
An example launch file is as follows:
<launch> <!-- Arguments --> <!-- Template Folder --> <!-- Path to folder containing blocks*.conf files on hard drive. This folder must always exist to store container blocks. --> <arg name="path_blocks" default="$(find smacha_gui)/blocks.conf"/> <!-- This templates will always be loaded from file. They are searched for in path_blocks --> <!-- <arg name="path_blocks_alwaysload" default="[Robot0Start.conf, Robot1Start.conf, ServiceState.conf]"/> --> <arg name="path_blocks_alwaysload" default="[Robot0Start.conf, Robot1Start.conf]"/> <!-- Path to SMACHA Server. If this variable is set, the here given SMACHA Server is used to load templates. Please mind that the gui templates contain additional information and are not the standard SMACHA templates. --> <!-- <arg name="path_smachaservertemplate" default="/smacha/templates"/> --> <!-- <arg name="path_smachaservertemplate" default=""/> --> <arg name="path_smachaservertemplate" default="/smacha/templates"/> <!-- Path to SMACHA Generate Server. --> <!-- <arg name="path_smachagenerategenerate" default="/smacha/generate"/> --> <arg name="path_smachaservergenerate" default="/smacha/generate"/> <!-- Launch the dynamic_script_generate_service_example node --> <node pkg="smacha_gui" name="smacha_gui" type="smacha_gui_node" output="screen"> <!-- Parameters --> <!-- Local template folder --> <param name="path_blocks" value="$(arg path_blocks)"/> <!-- SMACHA Server Templates --> <param name="path_smachaservertemplate" value="$(arg path_smachaservertemplate)"/> <!-- SMACHA Server Generate --> <param name="path_smachaservergenerate" value="$(arg path_smachaservergenerate)"/> <!-- Local template always load list --> <param name="path_blocks_alwaysload" value="$(arg path_blocks_alwaysload)"/> </node> </launch>
This variable holds the path on the local hard drive to
- Load (if the SMACHA server is not set, see below) blocks.
- Store containers.
- Load blocks from the always-load list (see below).
Files listed in this variable must exist in the folder defined by
path_blocks. They are always loaded and diplayed, regardless of settings of the SMACHA server.
This variable points to the ROS SMACHA template service. If it is set, templates are loaded from the server, otherwise from
This variable points to the SMACHA generate service. It is used to create SMACHA script from SMACHA templates.