SRRC Wiki

Service Robotics Research Center
at Ulm University of Applied Sciences

User Tools

Site Tools


tutorials:flexible-navigation-stack-selenv:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tutorials:flexible-navigation-stack-selenv:start [2021/05/22 17:50]
Christian Schlegel [Update CDL-Lookup Files]
tutorials:flexible-navigation-stack-selenv:start [2021/05/22 17:58] (current)
Christian Schlegel [Update the System Parameters]
Line 46: Line 46:
 {{ tutorials:​flexible-navigation-stack-selenv:​S02_00_FNS_NewEnvironment_system_params.png | }} {{ tutorials:​flexible-navigation-stack-selenv:​S02_00_FNS_NewEnvironment_system_params.png | }}
  
-Since the flexible navigation stack remains the same, we don't have to modify the other models in the system projecti.e. Component Architecture,​ Deployment, Target, etc.+Since //​SystemWebotsRobotino3NavigationNew//​ and //​SystemWebotsRobotino3Navigation//​ use the same flexible navigation stack, we don't have to modify the other models in the system project ​(i.e. Component Architecture,​ Deployment, Target, etc.).
  
 ==== Update the Maps ==== ==== Update the Maps ====
Line 102: Line 102:
 ==== Deploying and Executing the System ==== ==== Deploying and Executing the System ====
  
-**Step ​5.a:** Right click on the project → Run Code-Generation. This step is required if there is any change in models of the project(i.e any file inside the model folder). In this tutorial, we modified the System ​parameters, ​code-generation generates the updated configuration files(i.e *.ini files). You can look at the generated configuration files in ''​smartsoft/​src-gen/​params''​ and ''​smartsoft/​src-gen/​combined-ini-files'' ​folders.+**Step ​1:** Right click on //project// → //Run Code-Generation//. This step is required if there is any change in models of the project (i.eany file inside the model folder). In this tutorial, we modified the system ​parameters ​and thuswe need to do this step to generate ​updated configuration files (i.e *.ini files). You can look at the generated configuration files in the folders ​''​smartsoft/​src-gen/​params''​ and ''​smartsoft/​src-gen/​combined-ini-files''​.
  
 {{ tutorials:​flexible-navigation-stack-selenv:​S05_00_FNS_NewEnvironment_code_generation.png | }} {{ tutorials:​flexible-navigation-stack-selenv:​S05_00_FNS_NewEnvironment_code_generation.png | }}
  
-Verify that there are no errors during the code generation by looking at the Console ​terminal: ​+Verify that there are no errors during the code generation by looking at the console ​terminal: ​
  
 {{ tutorials:​flexible-navigation-stack-selenv:​S05_01_FNS_NewEnvironment_verify_code_generation.png | }} {{ tutorials:​flexible-navigation-stack-selenv:​S05_01_FNS_NewEnvironment_verify_code_generation.png | }}
  
-**Step ​5.b:** We now deploy the system by clicking the Deployment Action from the right-click menu of the project: ​+**Step ​2:** We now deploy the system by clicking the //Deployment Action// from the right-click menu of the project: ​
  
 {{ tutorials:​flexible-navigation-stack-selenv:​S05_02_FNS_NewEnvironment_deployment.png | }} {{ tutorials:​flexible-navigation-stack-selenv:​S05_02_FNS_NewEnvironment_deployment.png | }}
  
-It depends on your configuration whether you are being asked for credentials of the configured login account. Finally, you see the following pop-up window which tells you that the deployment was successful:+It depends on your configuration whether you are asked for credentials of the configured login account. Finally, you see the following pop-up window which tells you that the deployment was successful:
  
 {{ tutorials:​flexible-navigation-stack-selenv:​S05_03_FNS_NewEnvironment_deployment_popup.png | }} {{ tutorials:​flexible-navigation-stack-selenv:​S05_03_FNS_NewEnvironment_deployment_popup.png | }}
  
-**Step ​5.c:** You can now start your system by clicking Yes. A terminal window will open and show the scenario control menu. Choose menu-start to start the scenario. Further terminals open automatically (one for each component and one additional window for the naming service). Note that they may not be visible initially in case they overlap. Choose menu-stop to stop the scenario. ​+**Step ​3:** You can now start your system by clicking ​//Yes//. A terminal window will open and show the scenario control menu. Choose ​//menu-start// to start the scenario. Further terminals open automatically (one for each component and one additional window for the naming service). Note that they may not be visible initially in case they overlap. Choose ​//menu-stop// to stop the scenario. ​
  
 {{ tutorials:​flexible-navigation-stack-selenv:​S05_04_FNS_NewEnvironment_scenario_control_window.png | }} {{ tutorials:​flexible-navigation-stack-selenv:​S05_04_FNS_NewEnvironment_scenario_control_window.png | }}
  
-**Step ​5.d:** Wait until the webots simulator is up and all the components ​are started running. ​ Look for the terminal which contains the ComponentTCLSequencer.+**Step ​4:** Wait until the webots simulator is up and all the components started ​and are running. Look for the terminal ​window ​which contains the //ComponentTCLSequencer//.
  
 {{ tutorials:​flexible-navigation-stack-selenv:​S05_05_FNS_NewEnvironment_scenario_running.png | }} {{ tutorials:​flexible-navigation-stack-selenv:​S05_05_FNS_NewEnvironment_scenario_running.png | }}
  
-In the menu, select ​"5 - Approach location" ​and enter one of the offered names for locations.+In the menu, select ​//5 - Approach location// and enter one of the offered names for locations.
  
 Now, the robot navigates to this destination and stops there. Now, the robot navigates to this destination and stops there.
tutorials/flexible-navigation-stack-selenv/start.1621698642.txt.gz · Last modified: 2021/05/22 17:50 by Christian Schlegel