RoPod/Tutorials/RoPod simulation software: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
<div style="width: 40%; float: right;"><center>{{:RoPod_Table_Menu}}</center></div>
<div style="width: 40%; float: right;"><center>{{:RoPod_Table_Menu}}</center></div>
<div STYLE="float: left; width:60%">


= Install ROPOD Basis Software =
= Install ROPOD Basis Software =
Line 25: Line 27:




In the next part of the tutorial we are going to see how [[ RoPod/Tutorials/Matlab and a ROS node interface | Matlab and ROS can communicate]].


</div>
</div>

Latest revision as of 13:21, 25 March 2021

Install ROPOD Basis Software

Clone the main repository with the .rosinstall containing the tree structure of the whole software.

   git clone https://github.com/tue-ropod/tree-devpc.git

Switch to feature/tracking branck.

   cd tree-devpc
   git checkout feature/remove_ed_dependency

Open the .rosinstall from the shell just to inspect it.

   gedit .rosinstall

This file is a compilation of other repositories that need to be setup and all together compose the ROPOD software. You can now close it and run the installation script. It will install all the different repositories in your home directory. To install run:

   ./install_software


The ./install_software command makes some changes to your .bashrc file. In order for these changes to take effect, you need to close your terminal and open a new one (if using Terminator, fully close it and open a new instance).

Take a look at the structure of Ropod-repository. All packages were now placed in the ~/ropod-project-software/catkin_workspace/src folder. This folder contains 3 other folders:

  • functionalities: Here, all non-standard ros-packages are placed, such as ED, but also packages for localization, navigation, etc.
  • platform: Files corresponding to specific platforms located in this folder, while general files for getting the communication with the sensors to work is placed in the robot_common sub-folder
  • applications: In order to configure the robot for specific use-cases, all the relevant files are placed here.