Depth camera integration in ROS - Step-by-Step Execution

Concept Flow - Depth camera integration

Start ROS Node

↓

Initialize Depth Camera Driver

↓

Subscribe to Depth Image Topic

↓

Receive Depth Image Data

↓

Process Depth Data (e.g., filtering)

↓

Publish Processed Data or Use in Application

↓

Loop: Wait for Next Depth Frame

The ROS node starts, initializes the depth camera driver, subscribes to the depth image topic, processes incoming depth data, and uses or publishes the results continuously.

Execution Sample

ROS

import rclpy
from sensor_msgs.msg import Image

def depth_callback(msg):
    print(f"Received depth frame with width {msg.width}")

rclpy.init()
node = rclpy.create_node('depth_listener')
subscription = node.create_subscription(Image, '/camera/depth/image_raw', depth_callback, 10)
rclpy.spin(node)

This ROS 2 Python node subscribes to the depth camera's raw image topic and prints the width of each received depth frame.

Execution Table

Step	Action	ROS Topic	Message Received	Callback Output
1	Node initialized	-	-	-
2	Subscribed to depth image topic	/camera/depth/image_raw	-	-
3	Depth frame received	/camera/depth/image_raw	Image(width=640, height=480)	Print: Received depth frame with width 640
4	Depth frame received	/camera/depth/image_raw	Image(width=640, height=480)	Print: Received depth frame with width 640
5	No new frame	-	-	Waiting for next frame

💡 Execution continues indefinitely until node is shut down.

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
msg.width	N/A	640	640	640
msg.height	N/A	480	480	480

Key Moments - 2 Insights

Why does the callback print the width each time a frame arrives?

Because the callback function runs every time a new depth image message is received on the subscribed topic, as shown in execution_table steps 3 and 4.

What happens if no depth frames are published?

The node waits and does nothing until a new message arrives, as shown in execution_table step 5 where it waits for the next frame.

Visual Quiz - 3 Questions

Look at the execution table, what is printed when the first depth frame is received?

A Received depth frame with width 640

B Depth frame not received

C Node initialized

D Subscribed to topic

💡 Hint

Check execution_table row 3 under Callback Output.

At which step does the node subscribe to the depth image topic?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the Action column in execution_table.

If the depth image width changed to 800, how would the callback output change?

A Print: Received depth frame with width 640

B Print: Received depth frame with width 800

C No output printed

D Error message

💡 Hint

Refer to variable_tracker for msg.width values and callback print format.

Concept Snapshot

ROS Depth Camera Integration:
- Initialize ROS node
- Subscribe to depth image topic (e.g., /camera/depth/image_raw)
- Define callback to process each depth frame
- Callback receives Image messages with width, height, and data
- Use or publish processed depth data continuously
- Node runs until manually stopped

Full Transcript

This example shows how a ROS 2 node integrates a depth camera by subscribing to its depth image topic. The node initializes, subscribes to /camera/depth/image_raw, and waits for depth frames. Each time a frame arrives, the callback prints the frame width. The process repeats indefinitely, demonstrating continuous depth data reception and processing in ROS.

Practice

1. What is the main purpose of integrating a depth camera in a ROS robot system?

easy

A. To send commands to other robots

B. To measure distances and perceive 3D space around the robot

C. To control the robot's motors directly

D. To store large amounts of data on the robot

Solution

1. Step 1: Understand depth camera function

   A depth camera captures distance information and 3D structure of the environment.

2. Step 2: Identify its role in ROS

   In ROS, depth cameras help robots sense obstacles and navigate safely by providing spatial data.

3. Final Answer:

   To measure distances and perceive 3D space around the robot -> Option B

4. Quick Check:

   Depth camera = 3D sensing [OK]

Hint: Depth cameras help robots see distance and shapes [OK]

Common Mistakes:

• Confusing depth camera with motor control
• Thinking it stores data instead of sensing environment
• Assuming it sends commands to other robots

2. Which ROS launch file command correctly starts a depth camera node named depth_camera_node?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall ROS launch syntax for nodes

   ROS launch files use the <node> tag with attributes pkg, type, and name to start nodes.

2. Step 2: Match correct syntax

   uses , which is correct syntax.

3. Final Answer:

   <launch><node pkg="camera_pkg" type="depth_camera_node" name="depth_camera_node"/></launch> -> Option A

4. Quick Check:

   Use <node> tag with pkg and type [OK]

Hint: Use <node> tag with pkg and type attributes [OK]

Common Mistakes:

• Using incorrect tags like <start> or <run>
• Missing the name attribute
• Confusing node and type attributes

3. Given this ROS Python snippet subscribing to a depth image topic, what will be printed when a message arrives?

import rospy
from sensor_msgs.msg import Image

def callback(data):
    print(f"Received depth image with width: {data.width}")

rospy.init_node('depth_listener')
rospy.Subscriber('/camera/depth/image_raw', Image, callback)
rospy.spin()

medium

A. No output because callback is never called

B. Received depth image with width: data.width

C. Error: 'Image' object has no attribute 'width'

D. Received depth image with width: 640

Solution

1. Step 1: Understand the callback function

   The callback prints the width attribute of the received Image message.

2. Step 2: Recognize typical Image message fields

   sensor_msgs/Image messages include a width field with the image width, e.g., 640 pixels.

3. Final Answer:

   Received depth image with width: 640 -> Option D

4. Quick Check:

   Image.width prints actual width value [OK]

Hint: Image messages have width attribute with pixel count [OK]

Common Mistakes:

• Thinking width is a string 'data.width'
• Assuming Image message lacks width attribute
• Believing callback never triggers

4. You wrote this ROS launch snippet to start a depth camera node but get an error:

<launch>
  <node pkg="camera_pkg" type="depth_camera" name="depth_camera"/>
</launch>

What is the likely cause of the error?

medium

A. Missing closing tag for <launch>

B. The package 'camera_pkg' is not installed

C. The node type 'depth_camera' does not match the executable name

D. The node name cannot be the same as the package name

Solution

1. Step 1: Check node type and executable name

   The 'type' attribute must exactly match the executable file name in the package.

2. Step 2: Identify mismatch causing error

   If the executable is named 'depth_camera_node' but 'depth_camera' is used, ROS cannot find it.

3. Final Answer:

   The node type 'depth_camera' does not match the executable name -> Option C

4. Quick Check:

   Node type must match executable name [OK]

Hint: Node type must exactly match executable filename [OK]

Common Mistakes:

• Assuming missing closing tag causes error
• Ignoring package installation issues
• Thinking node name conflicts cause this error

5. You want to visualize depth data from a ROS topic /camera/depth/image_raw using OpenCV in Python. Which code snippet correctly converts the ROS Image message to an OpenCV image for display?

hard

A. from cv_bridge import CvBridge
bridge = CvBridge()
cv_image = bridge.imgmsg_to_cv2(data, desired_encoding='passthrough')

B. import cv2
cv_image = cv2.imread('/camera/depth/image_raw')

C. cv_image = data.data.decode('utf-8')

D. cv_image = numpy.array(data)

Solution

1. Step 1: Use cv_bridge to convert ROS Image

   cv_bridge provides imgmsg_to_cv2 to convert ROS Image messages to OpenCV format.

2. Step 2: Apply correct conversion call

   from cv_bridge import CvBridge bridge = CvBridge() cv_image = bridge.imgmsg_to_cv2(data, desired_encoding='passthrough') uses bridge.imgmsg_to_cv2 with 'passthrough' encoding, which preserves depth data correctly.

3. Final Answer:

   from cv_bridge import CvBridge bridge = CvBridge() cv_image = bridge.imgmsg_to_cv2(data, desired_encoding='passthrough') -> Option A

4. Quick Check:

   Use cv_bridge.imgmsg_to_cv2 for ROS to OpenCV [OK]

Hint: Use cv_bridge to convert ROS Image to OpenCV image [OK]

Common Mistakes:

• Trying to read ROS topic as file with cv2.imread
• Decoding raw data as UTF-8 string
• Directly converting data to numpy array without bridge