Robot frame conventions (base_link, odom, map) in ROS

Introduction

Robot frame conventions help us understand where the robot is and how it moves. They give a clear way to talk about the robot's position and orientation in the world.

When you want to track the robot's position relative to its starting point.

When you need to map the environment and know where obstacles are.

When you want to control the robot's movement precisely.

When you want to combine sensor data from different sources.

When you want to share robot position data with other systems or robots.

Syntax

ROS

# Typical ROS frames:
# base_link: Robot's center frame
# odom: Odometry frame, tracks robot movement over time
# map: Fixed world frame, global reference

# Example of frame relationship:
# map -> odom -> base_link

base_link is the robot's own center point, like its body.

odom tracks how the robot moves from where it started, but can drift over time.

Examples

This frame moves with the robot and is the main reference for its parts.

ROS

# base_link frame example
# Represents the robot's center
# Used for sensors and movement commands

base_link

This frame helps track how far and where the robot has moved since it started.

ROS

# odom frame example
# Tracks robot's position relative to start
# Updated by wheel encoders or sensors

odom -> base_link

This frame stays fixed in the world and helps the robot know its global position.

ROS

# map frame example
# Fixed global frame
# Used for navigation and mapping

map -> odom -> base_link

Sample Program

This code listens for the robot's position in the global map frame. It prints the robot's x and y coordinates as it moves.

ROS

# ROS Python example showing frame usage
import rospy
from tf2_ros import Buffer, TransformListener

rospy.init_node('frame_listener')
buffer = Buffer()
listener = TransformListener(buffer)

rate = rospy.Rate(1)  # 1 Hz
while not rospy.is_shutdown():
    try:
        # Get transform from map to base_link
        trans = buffer.lookup_transform('map', 'base_link', rospy.Time(0))
        print(f"Robot position in map frame: x={trans.transform.translation.x:.2f}, y={trans.transform.translation.y:.2f}")
    except Exception as e:
        print("Waiting for transform...")
    rate.sleep()

Important Notes

The odom frame can drift over time because it relies on wheel movement.

The map frame is corrected by sensors like GPS or SLAM to stay accurate.

Understanding these frames helps you combine sensor data and control the robot well.

Summary

base_link is the robot's own center frame.

odom tracks movement from start but can drift.

map is a fixed global frame for navigation.

Practice

1. Which ROS frame represents the robot's own center point and moves with it?

easy

A. map

B. base_link

C. odom

D. world

Solution

1. Step 1: Understand the role of base_link

   base_link is the frame fixed to the robot itself, representing its center.

2. Step 2: Compare with other frames

   odom tracks movement but can drift, map is a fixed global frame, and world is not a standard ROS frame here.

3. Final Answer:

   base_link -> Option B

4. Quick Check:

   Robot center frame = base_link [OK]

Hint: Remember: base_link moves with the robot itself [OK]

Common Mistakes:

• Confusing odom as robot center
• Thinking map moves with robot
• Assuming world is standard ROS frame

2. Which of the following is the correct way to refer to the odometry frame in ROS?

easy

A. odom

B. odom_frame

C. map

D. base_link

Solution

1. Step 1: Identify the standard odometry frame name

   The standard ROS frame for odometry is odom.

2. Step 2: Check other options

   base_link is robot center, map is global frame, and odom_frame is not a standard name.

3. Final Answer:

   odom -> Option A

4. Quick Check:

   Odometry frame = odom [OK]

Hint: Odom frame is just 'odom', no extra suffix [OK]

Common Mistakes:

• Adding '_frame' suffix incorrectly
• Mixing base_link with odom
• Using map instead of odom

3. Given a robot moving in a room, which frame will show drift over time due to sensor noise?

medium

A. world

B. map

C. base_link

D. odom

Solution

1. Step 1: Understand frame drift

   The odom frame tracks movement from start but can accumulate errors causing drift.

2. Step 2: Compare with other frames

   map is fixed and does not drift, base_link moves with robot, world is not standard here.

3. Final Answer:

   odom -> Option D

4. Quick Check:

   Drifting frame = odom [OK]

Hint: Odom drifts; map stays fixed [OK]

Common Mistakes:

• Thinking map drifts
• Confusing base_link with odom
• Assuming world is used here

4. You notice your robot's position drifts over time when using the odom frame. What is the best way to fix this issue?

medium

A. Use the map frame for global localization

B. Switch to using the base_link frame for navigation

C. Reset the odom frame periodically

D. Ignore the drift as it is normal

Solution

1. Step 1: Understand the cause of drift

   The odom frame drifts due to sensor noise and integration errors over time.

2. Step 2: Choose a frame that corrects drift

   The map frame is fixed globally and used for localization to correct odom drift.

3. Final Answer:

   Use the map frame for global localization -> Option A

4. Quick Check:

   Fix drift with map frame [OK]

Hint: Use map frame to correct odom drift [OK]

Common Mistakes:

• Using base_link which moves with robot
• Resetting odom often is impractical
• Ignoring drift causes navigation errors

5. You want to build a navigation system that uses sensor data to update the robot's position on a fixed map. Which sequence of frames should you use to correctly represent the robot's position relative to the world?

hard

A. odom -> base_link -> map

B. base_link -> odom -> map

C. map -> odom -> base_link

D. base_link -> map -> odom

Solution

1. Step 1: Understand frame hierarchy

   The robot's position is relative to base_link, which is relative to odom, and odom is relative to map.

2. Step 2: Determine correct parent-child order

   The correct chain is map (global fixed frame) -> odom (local odometry) -> base_link (robot center).

3. Final Answer:

   map -> odom -> base_link -> Option C

4. Quick Check:

   Global to robot: map -> odom -> base_link [OK]

Hint: Frame chain goes from map down to base_link [OK]

Common Mistakes:

• Reversing frame order
• Putting base_link as parent of odom
• Ignoring map as global frame