TF tree concept in ROS - Mini Project: Build & Apply

Building a Simple TF Tree in ROS

📖 Scenario: You are working on a robot that needs to understand the positions of its parts relative to each other. To do this, you will create a simple TF tree that shows how different parts of the robot connect in space.

🎯 Goal: Build a basic TF tree in ROS by defining frames and their relationships using tf2_ros. You will create a broadcaster node that publishes the transforms between frames.

📋 What You'll Learn

Create a ROS node that broadcasts transforms

Define a parent frame called world

Define a child frame called base_link connected to world

Define a child frame called camera_link connected to base_link

Publish the transforms continuously

💡 Why This Matters

🌍 Real World

Robots use TF trees to understand where their parts are relative to each other and the world. This helps with navigation, manipulation, and sensor data interpretation.

💼 Career

Knowing how to create and manage TF trees is essential for robotics engineers working with ROS to build reliable and spatially aware robot systems.

1

Create the ROS node and import necessary libraries

Write the first lines of code to import rclpy and tf2_ros, and create a ROS node called tf_broadcaster_node.

ROS

# Import rclpy and tf2_ros
# Create a ROS node named 'tf_broadcaster_node'
# Your code here

Hint

Use import statements for rclpy and tf2_ros. Then create a node with Node('tf_broadcaster_node').

2

Set up the TransformBroadcaster and define the parent frame

Add code to create a TransformBroadcaster attached to the node. Define the parent frame as world in your transform message.

ROS

import rclpy
from rclpy.node import Node
import tf2_ros

rclpy.init()
node = Node('tf_broadcaster_node')
# Create a TransformBroadcaster attached to node
# Define parent frame as 'world' in the transform
# Your code here

Hint

Create the broadcaster with tf2_ros.TransformBroadcaster(node). Set transform.header.frame_id = 'world' to define the parent frame.

3

Define child frames and set transform details

Set the child frame of the transform to base_link. Set the translation to x=1.0, y=0.0, z=0.0 and rotation to no rotation (x=0, y=0, z=0, w=1). Then create a second transform for camera_link as a child of base_link with translation x=0.5, y=0.0, z=1.0 and no rotation.

ROS

import rclpy
from rclpy.node import Node
import tf2_ros
from geometry_msgs.msg import TransformStamped

rclpy.init()
node = Node('tf_broadcaster_node')

broadcaster = tf2_ros.TransformBroadcaster(node)

transform = TransformStamped()
transform.header.frame_id = 'world'
# Set child frame to 'base_link' and translation x=1.0, y=0.0, z=0.0
# Set rotation to x=0, y=0, z=0, w=1
# Create second transform for 'camera_link' child of 'base_link' with translation x=0.5, y=0.0, z=1.0 and no rotation
# Your code here

Hint

Set child_frame_id and translation/rotation fields exactly as described. Create a second TransformStamped for the camera frame.

4

Publish the transforms continuously in a loop

Write a loop that updates the header timestamps of both transforms with the current time from the node, then broadcasts both transforms continuously. Use rclpy.spin_once(node) inside the loop to keep the node alive.

ROS

import rclpy
from rclpy.node import Node
import tf2_ros
from geometry_msgs.msg import TransformStamped

rclpy.init()
node = Node('tf_broadcaster_node')

broadcaster = tf2_ros.TransformBroadcaster(node)

transform = TransformStamped()
transform.header.frame_id = 'world'
transform.child_frame_id = 'base_link'
transform.transform.translation.x = 1.0
transform.transform.translation.y = 0.0
transform.transform.translation.z = 0.0
transform.transform.rotation.x = 0.0
transform.transform.rotation.y = 0.0
transform.transform.rotation.z = 0.0
transform.transform.rotation.w = 1.0

transform2 = TransformStamped()
transform2.header.frame_id = 'base_link'
transform2.child_frame_id = 'camera_link'
transform2.transform.translation.x = 0.5
transform2.transform.translation.y = 0.0
transform2.transform.translation.z = 1.0
transform2.transform.rotation.x = 0.0
transform2.transform.rotation.y = 0.0
transform2.transform.rotation.z = 0.0
transform2.transform.rotation.w = 1.0

# Publish transforms continuously with updated timestamps
# Your code here

Hint

Use a while rclpy.ok(): loop. Update header.stamp with current time from node.get_clock().now().to_msg(). Send both transforms with broadcaster.sendTransform(). Call rclpy.spin_once(node) to keep the node alive.

Practice

1. What is the main purpose of the TF tree in ROS?

easy

A. To store sensor data logs

B. To control robot speed

C. To manage robot battery levels

D. To organize all robot parts and sensors in space

Solution

1. Step 1: Understand the role of TF tree

   The TF tree keeps track of coordinate frames for robot parts and sensors.

2. Step 2: Identify the main purpose

   It organizes these frames in space to help with position and orientation conversions.

3. Final Answer:

   To organize all robot parts and sensors in space -> Option D

4. Quick Check:

   TF tree = organize robot parts in space [OK]

Hint: TF tree = robot parts positions map [OK]

Common Mistakes:

• Thinking TF tree stores sensor data logs
• Confusing TF tree with battery management
• Assuming TF tree controls robot speed

2. Which command correctly shows the TF tree structure in ROS?

easy

A. rosrun tf list_frames

B. rosrun tf tf_echo

C. rosrun tf view_frames

D. rosrun tf show_tree

Solution

1. Step 1: Recall commands for TF tree visualization

   The command view_frames generates a PDF showing the TF tree structure.

2. Step 2: Identify the correct command

   tf_echo shows transform between two frames, not the whole tree. Other options are invalid.

3. Final Answer:

   rosrun tf view_frames -> Option C

4. Quick Check:

   View TF tree = view_frames command [OK]

Hint: Use view_frames to see full TF tree [OK]

Common Mistakes:

• Using tf_echo to view entire tree
• Assuming list_frames or show_tree exist
• Confusing tf_echo output with tree structure

3. What will the command rosrun tf tf_echo base_link camera_link output?

medium

A. The transform (position and rotation) from base_link to camera_link

B. A list of all frames in the TF tree

C. An error saying command not found

D. The battery status of the robot

Solution

1. Step 1: Understand tf_echo command

   tf_echo shows the transform between two frames at the current time.

2. Step 2: Identify output for given frames

   It outputs position and rotation from base_link to camera_link.

3. Final Answer:

   The transform (position and rotation) from base_link to camera_link -> Option A

4. Quick Check:

   tf_echo base_link camera_link = transform output [OK]

Hint: tf_echo shows transform between two frames [OK]

Common Mistakes:

• Thinking tf_echo lists all frames
• Expecting battery info from tf_echo
• Assuming tf_echo command is invalid

4. You run rosrun tf tf_echo base_link camera_link but get an error: "Lookup would require extrapolation into the future." What is the likely cause?

medium

A. The command syntax is incorrect

B. The TF data is not being published or is delayed

C. The robot battery is low

D. The frames base_link and camera_link do not exist

Solution

1. Step 1: Understand the error message

   "Lookup would require extrapolation into the future" means TF data timestamps are not synchronized or missing.

2. Step 2: Identify cause

   This usually happens if TF broadcaster is not publishing or data is delayed.

3. Final Answer:

   The TF data is not being published or is delayed -> Option B

4. Quick Check:

   Extrapolation error = missing or delayed TF data [OK]

Hint: Check if TF broadcaster is running when error appears [OK]

Common Mistakes:

• Assuming syntax error causes this message
• Thinking battery level affects TF lookup
• Believing frames do not exist without checking

5. If a robot has frames: base_link, odom, and map, which TF tree structure correctly represents their typical relationship?

hard

A. map -> odom -> base_link

B. base_link -> odom -> map

C. odom -> map -> base_link

D. base_link -> map -> odom

Solution

1. Step 1: Recall typical TF tree hierarchy

   Usually, map is the fixed world frame, odom tracks odometry relative to map, and base_link is robot base relative to odom.

2. Step 2: Arrange frames in correct parent-child order

   The chain is map (world) -> odom -> base_link.

3. Final Answer:

   map -> odom -> base_link -> Option A

4. Quick Check:

   TF tree typical order = map to odom to base_link [OK]

Hint: World frame (map) is parent of odom, which is parent of base_link [OK]

Common Mistakes:

• Reversing parent-child frame order
• Confusing odom as world frame
• Placing base_link as parent of map