In this question we see how to solve the problem when running catkin_make on a Catkin Workspace: The specified base path /home/user/catkin_ws contains a CMakeLists.txt but catkin_make must be invoked in the root of workspace
A: The problem is because the user had a CMakeLists.txt on the root folder of the Workspace (~/catkin_ws/CMakeLists.txt). The file must be on the src folder: ~/catkin_ws/src/CMakeLists.txt
Q: Need information on aerodynamic parameters of lift-drag plugin A: You have to calculate the area for the new shapes and also decide the axis for the front and upwards forces.
Q: I created a custom gazebo world for my turtleBot containing several walls and saved it as a .world file. However when I run the world file the walls that i created do not load.
A: Here you can see a simple example of how to launch a simple Gazebo world with a wall in it.
When developing for ROS, you will have to create the URDF of your robot. If your robot is complex and contains lots of different joints, you would like to test how is it going and if you are building the model properly. Here we provide you with a method to check the status of your robot URDF model.
You have to create the URDF, add the ros control plugin, and include a config file to configure the plugin. Let’s see how to do it step-by-step:
Step 0. Create a project in ROS Development Studio(ROSDS)
ROSDS helps you follow our tutorial in a fast pace without dealing without setting up an environment locally. If you haven’t had an account yet, you can create a free account here. Please create a ROSject then open it.
Step 1. Create a URDF model
At first, let’s create a package for our code.
cd ~/catkin_ws/src
catkin_create_pkg simple_example_description ropy
cd simple_example_dexcription
mkdir launch
mkdir config
mkdir urdf
Then we create a URDF description called robot.urdf under the urdf folder with the following content
For each link, there are 3 parts: inertia define the physical property of the link, the collision part define the behavior while collision occurs, and the visual part define the visualization of the link in the simulation.
Since we also want to control the robot, we have to include the gazebo plugin and define the type of the transmission.
Then we also need a config.yaml file under the config folder for the parameter of the controller with the following content.