Clober Navigation

Clober may move & rotate for navigation. Make sure you are operating in a safe environment

Navigation is to move a robot from one location to a specified destination of the given environemnt. For the purpose, a map containing the geometrical information of the robots surroundings is required.

SLAM of the environment allow you to acquire a map

1. Run Navigation Nodes

1.1 Bringup Robot

1. Run a Bringup for the Clober.

  roslaunch clober_bringup base.launch
  

• This can be substituted by running a simulation node

  roslaunch clober_simulation logo_world.launch
  

1.2 Launch Navigation

roslaunch clober_navigation navigation.launch

2. Estimate Initial Pose

Initial Pose Estimation can be performed before Navigation to intialize AMCL parameters which are critical to Navigation quality.

1. Click 2D Pose Estimate Button on the RVIZ menu

2. Click on the map where clober is located and drag the green arrow toward the dirction the robot is facing.

3. Repeat step 1 and 2 to increase data precision.

4. Launch keyboard teleoperation to further increase precision.

    rosrun teleop_twist_keyboard teleop_twist_keyboard.py
    

1. Move the robot back and forth in order to narrow down the estimated location.

2. Terminate the keyboard teleoperation(Ctrl+C) for the next navigation step.

3. Publish 2D Navigation Goal

• On the RVIZ menu click 2D Nav Goal

• Click on the destination and drag the green arrow toward the dirction of the robot on the map.

4. Tuning Guide

You can get more information about Navigation tuning from Basic Navigation Tuning Guide, ROS Navigation Tuning Guide by Kaiyu Zheng, Dynamic Window Approach local planner wiki.

4.1 footprint

• Defined in clober_navigation/config/costmap_common.yaml

  This parameter describes the footprint of the robot used for navigation. Composed of four [x,y] coordinates representing the four corners of the base of the robot

  default:

    footprint: [[-0.202, -0.202], [-0.202, 0.202], [0.202, 0.202], [0.202, -0.202]]
    

4.2 inflation_radius

• Defined in clober_navigation/config/global_costmap.yaml & clober_navigation/config/local_costmap.yaml

  This parameter makes inflation area from the obstacle. Path would be planned in order that it don’t across this area. It is safe that to set this to be bigger than robot radius. For more information, please refer to the costmap_2d wiki.

  default:

  global_costmap.yaml:

  inflation_radius: 0.3
  

  local_costmap.yaml:

  inflation_radius: 0.15
  

4.3 cost_scaling_factor

• Defined in clober_navigation/config/global_costmap.yaml & clober_navigation/config/local_costmap.yaml

  This factor is multiplied by cost value. Because it is an reciprocal propotion, this parameter is increased, the cost is decreased.

  The best path is for the robot to pass through a center of between obstacles. Set this factor to be smaller in order to far from obstacles. For more information, please refer to the costmap_2d wiki

  default:

  global_costmap.yaml:

  inflation_radius: 3.0
  

  local_costmap.yaml:

  inflation_radius: 1.5
  

4.4 base_global_planner

File truncated at 100 lines see the full file

Changelog for package clober_navigation

1.0.4 (2021-09-03)

• add nav param
• test nav
• edit serial odom period
• odom mode 0 check
• Contributors: dev

1.0.3 (2021-08-11)

1.0.2 (2021-08-11)

• add suntech map & nav configuration
• Merge branch 'noetic-devel' of https://github.com/CLOBOT-Co-Ltd/clober into noetic-devel
• modify simulation packages for using rmf
• Contributors: ClobotLucy, clobot-git, dev

1.0.1 (2021-07-12)

1.0.0 (2021-07-12)

• Initial Clober package