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
  • Linear check
  • Angular check

Was this helpful?

Export as PDF
  1. Seirios RNS
  2. Technical Resources
  3. Installation Guide
  4. Pre-installation Checks
  5. Robot Checks

(3/4) Odometry Check

Ensure odometry is working well

Linear check

  • Align the bot appropriately to test 3-4 meters of linear, straight distance without an angular component. Test using the following command in Terminal: rostopic pub /cmd_vel geometry_msgs/Twist "linear: x: 0.0 y: 0.0 z: 0.0 angular: x: 0.0 y: 0.0 z: 0.0"

  • Restart motor

  • Check odom pose is zero.

  • Publish only linear vel x: 0.1 and stop the bot at the 3-4 m mark.

  • Echo the odom topic: rostopic echo /odom.

  • Compare the pose of the updated odom with linear and angular bot travelled (offset 1-2%).

Angular check

  • Align the bot properly. Mark the spot where the bot will begin rotating.

  • Restart the motors.

  • Rotate the bot clockwise. Quaternion should be updated to negative.

  • Restart the motor and rotate the bot anticlockwise. Quaternion should be updated to positive.

  • Restart the motor. Rotate and stop the bot at the original marked spot.

  • Make sure that the angular pose is a 0 rad change.

Validating Odometry Data

We provide you with a script that enables you to verify the odometry data by inputting the velocity and duration. The robot will then move at the specified velocity for the given duration. Subsequently, the script will calculate and provide the distance traveled by the robot based on these inputs.

This will facilitate the verification of your odometry data, making it easier and more efficient for you.

Previous(2/4) Angular Speed Calibration CheckNext(4/4) Straight-line Check

Last updated 2 years ago

Was this helpful?

You can download the script .

1️⃣
✅
🔵
here