docs.movel.ai
English
English
  • Main
  • Seirios RNS
    • RNS Features
      • Core
        • 🧭Dashboard
        • 🕹️Teleoperation
        • 🗺️Mapping
        • 🔫Tasks
        • ⛽Stations
        • 🎯Localiser
        • 🚩Task Manager
      • Supplementary
        • ⚙️Behavioral & Interface
        • ✏️Map Editor
        • 🚦Queue Manager
        • 🥁Non-Fully Qualified Tasks
      • Robotics
        • 🚧Kerb-and-ramp navigation
        • 🦿Anti-shin buster
    • Technical Resources
      • Installation Guide
        • 1️⃣Pre-installation Checks
          • ✅Software Checks
          • ✅Robot Checks
            • 🔵(0.5/4) Before Starting Robot Checks
            • 🔵(1/4) Linear Speed Calibration Check
            • 🔵(2/4) Angular Speed Calibration Check
            • 🔵(3/4) Odometry Check
            • 🔵(4/4) Straight-line Check
        • 2️⃣'Easy-deploy' for Seirios
          • Installing docker
          • Installing Seirios RNS
          • Starting Seirios
        • 3️⃣Hardware Integration
        • 4️⃣Navigation Tuning
        • 5️⃣Full Licence Activation
      • REST APIs
      • Hardware Related
      • External Process Handler
      • TEB Tuning Guide
      • Pebble Tuning Guide
      • Kudan Integration
      • Clone Your Robot
      • Import Multiple Stations to Seirios RNS from Excel File
    • FAQs
      • Hardware Related
      • Interface Related
      • RNS FAQ
    • Downloadable Links
  • SEIRIOS FMS
    • Getting Started
      • General Concepts
      • Quick Start
    • Features
      • Core Features
        • Dashboard
      • Management Features
    • Technical Resources
      • FMS Installation Guide
        • Ubuntu
        • Windows
      • RNS Plugin Installation Guide
        • Ubuntu
        • Windows
      • Concepts
        • Map System
        • Tasks
        • Traffic Management
      • Robot Integration Manual
        • Getting Started
        • SDK & Communication Protocols
        • Capabilities
          • Connection
          • Teleoperation
          • Pose
          • LiDAR
          • Emergency Stop
          • Camera
          • Mapping
          • Navigation
          • Localization
          • Queueing
          • Traffic Management
        • Deployment
        • Tutorial: Integrating Robotis Turtlebot3 Simulation
          • 1. Setup Robot Plugin & Establish Connection
          • 2. Integrating Teleoperation
          • 3. Manage the SLAM Node dynamically
          • 4. Integrating the Mapping process
          • 5. Manage the Navigation Node dynamically
          • 6. Integrating the Navigation process
          • 7. Integrating Localization
          • 8. Integrating the Queueing Operations
          • 9. Containerizing the Robot Plugin
    • FAQs
  • Seirios Simple
    • Device Minimum Resolutions
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Seirios RNS
  2. Technical Resources
  3. Installation Guide

Navigation Tuning

PreviousHardware IntegrationNextFull Licence Activation

Last updated 1 year ago

Was this helpful?

Taking the node “/motors_ctrl” as an example. It is publishing to “/odom” topic with “nav_msgs/Odometry” message type, along with the other topics in the list. It also subscribes to “/cmd_vel” topic with message type “geometry_msgs/Twist”

  1. Go into the folder ‘/home/<user>/catkin_ws/movel_ai/config/movel/config/’

  2. In the parameter file costmap_common_params.yaml, ensure that the robot footprint is defined correctly.

    1. If the robot footprint is a polygon, configure the footprint parameter and comment out robot_radius. For example:

      footprint: [[0.2, 0.2], [-0.2, 0.2], [-0.2, -0.2], [0.2, -0.2]]
      #robot_radius: 0.18
  3. Here, the robot has a square footprint with the xy coordinates of the four corners as shown, while robot_radius is commented out.

    1. If the robot footprint is circular, configure the robot_radius parameter and comment out footprint. For example:

      #footprint: [[0.2, 0.2], [-0.2, 0.2], [-0.2, -0.2], [0.2, -0.2]]
      robot_radius: 0.18
  4. In base_local_planner_params.yaml:

    1. Go to “#Robot” section. To tune the speed of the robot, configure max_vel_x for linear speed, and max_vel_theta for angular speed.

      1. If the robot is not reaching the max speed, increase acc_lim_x and acc_lim_theta.

      2. In footprint_model, select a suitable model type and configure the corresponding parameters.

    2. In “#Obstacles” section, tune the value of min_obstacle_dist to set how far away the robot should keep away from obstacles. Reduce this parameter value if the robot is required to go through narrow spaces.

  5. If the autonomous navigation motion is jerky, go to “catkin_ws/movel_ai/config/cmd_vel_mux/config”, find cmd_vel_mux.yaml, and increase the value set for timeout_autonomous.

  6. For in depth tuning of base_local_planner_params.yaml, refer to .

4️⃣
http://wiki.ros.org/teb_local_planner