Bird
Raised Fist0
ROSframework~5 mins

Twist message structure in ROS

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction

The Twist message structure is used to tell a robot how to move by giving it speed and direction in a simple way.

When you want to control a robot's movement in a straight line or turn.
When sending commands to a robot to move forward, backward, or rotate.
When programming a robot to follow a path or avoid obstacles.
When you need to specify both linear and angular velocity for a robot.
When working with mobile robots that use ROS for navigation.
Syntax
ROS
geometry_msgs/Twist
{
  geometry_msgs/Vector3 linear
  geometry_msgs/Vector3 angular
}

geometry_msgs/Vector3
{
  float64 x
  float64 y
  float64 z
}

The Twist message has two parts: linear and angular.

Each part is a vector with x, y, and z values representing speed in meters per second or radians per second.

Examples
This example moves the robot straight forward at 1 meter per second with no turning.
ROS
Twist twist_msg;
twist_msg.linear.x = 1.0;  // Move forward at 1 m/s
 twist_msg.linear.y = 0.0;
twist_msg.linear.z = 0.0;
twist_msg.angular.x = 0.0;
twist_msg.angular.y = 0.0;
twist_msg.angular.z = 0.0;  // No rotation
This example makes the robot rotate in place without moving forward or sideways.
ROS
Twist twist_msg;
twist_msg.linear.x = 0.0;
twist_msg.linear.y = 0.0;
twist_msg.linear.z = 0.0;
twist_msg.angular.x = 0.0;
twist_msg.angular.y = 0.0;
twist_msg.angular.z = 0.5;  // Rotate at 0.5 rad/s
This example moves the robot forward while turning gently.
ROS
Twist twist_msg;
twist_msg.linear.x = 0.5;  // Move forward slowly
 twist_msg.angular.z = 0.2;  // Turn slowly
// Other values set to 0
Sample Program

This ROS node publishes a Twist message to the cmd_vel topic at 10 times per second. It commands the robot to move forward at 1 meter per second without turning.

ROS
#include <ros/ros.h>
#include <geometry_msgs/Twist.h>

int main(int argc, char **argv) {
  ros::init(argc, argv, "twist_publisher");
  ros::NodeHandle nh;
  ros::Publisher pub = nh.advertise<geometry_msgs::Twist>("cmd_vel", 10);

  ros::Rate rate(10);  // 10 Hz

  while (ros::ok()) {
    geometry_msgs::Twist twist_msg;
    twist_msg.linear.x = 1.0;  // Move forward at 1 m/s
    twist_msg.linear.y = 0.0;
    twist_msg.linear.z = 0.0;
    twist_msg.angular.x = 0.0;
    twist_msg.angular.y = 0.0;
    twist_msg.angular.z = 0.0;  // No rotation

    pub.publish(twist_msg);
    ROS_INFO("Published Twist: linear.x=%.2f angular.z=%.2f", twist_msg.linear.x, twist_msg.angular.z);

    rate.sleep();
  }

  return 0;
}
OutputSuccess
Important Notes

Only the x value in linear and the z value in angular are commonly used for simple ground robots.

Make sure to publish Twist messages at a steady rate to keep the robot moving smoothly.

Zero values mean no movement or rotation in that direction.

Summary

The Twist message tells a robot how fast to move and turn.

It has linear and angular parts, each with x, y, and z values.

Use it to control robot movement in ROS by publishing to the cmd_vel topic.

Practice

(1/5)
1. What does the Twist message in ROS primarily control?
easy
A. The robot's sensor data
B. The robot's battery status
C. The robot's linear and angular velocity
D. The robot's camera feed

Solution

  1. Step 1: Understand the purpose of Twist message

    The Twist message is designed to send velocity commands to a robot, including linear and angular velocities.
  2. Step 2: Identify what linear and angular velocities control

    Linear velocity controls forward/backward movement, and angular velocity controls rotation.
  3. Final Answer:

    The robot's linear and angular velocity -> Option C
  4. Quick Check:

    Twist controls velocity = C [OK]
Hint: Remember Twist = linear + angular velocity control [OK]
Common Mistakes:
  • Confusing Twist with sensor or camera data
  • Thinking Twist controls battery or hardware status
2. Which field in the Twist message controls the robot's forward speed?
easy
A. linear.x
B. angular.z
C. linear.y
D. angular.x

Solution

  1. Step 1: Recall Twist message fields

    Twist has linear and angular parts, each with x, y, z components.
  2. Step 2: Identify forward speed component

    Forward/backward speed is controlled by linear.x, while angular.z controls rotation.
  3. Final Answer:

    linear.x -> Option A
  4. Quick Check:

    Forward speed = linear.x [OK]
Hint: Forward speed is linear.x, rotation is angular.z [OK]
Common Mistakes:
  • Choosing angular.z for forward speed
  • Confusing linear.y with forward movement
3. Given this ROS Python snippet:
from geometry_msgs.msg import Twist
msg = Twist()
msg.linear.x = 1.0
msg.angular.z = 0.5
print(msg.linear.x, msg.angular.z)
What will be the printed output?
medium
A. Error: attribute not found
B. 1.0 0.5
C. 0 0
D. 0.5 1.0

Solution

  1. Step 1: Analyze message assignments

    linear.x is set to 1.0 and angular.z is set to 0.5 explicitly.
  2. Step 2: Understand print statement

    Print outputs linear.x then angular.z values, so output is '1.0 0.5'.
  3. Final Answer:

    1.0 0.5 -> Option B
  4. Quick Check:

    Print linear.x and angular.z = 1.0 0.5 [OK]
Hint: Print shows assigned linear.x and angular.z values [OK]
Common Mistakes:
  • Swapping the order of printed values
  • Expecting default zero values
  • Assuming attribute errors without imports
4. Identify the error in this ROS Python code snippet:
from geometry_msgs.msg import Twist
msg = Twist()
msg.linear.z = 2.0
msg.angular.x = 1.0
print(msg.linear.z, msg.angular.x)
medium
A. linear.z and angular.x are valid fields
B. linear.z is valid but angular.x is invalid
C. angular.x is valid but linear.z is invalid
D. Both linear.z and angular.x are invalid fields

Solution

  1. Step 1: Check Twist message field validity

    Twist message linear and angular parts each have x, y, z components valid for velocity.
  2. Step 2: Confirm linear.z and angular.x usage

    Both linear.z and angular.x are valid fields representing vertical linear velocity and rotation around x-axis respectively.
  3. Final Answer:

    linear.z and angular.x are valid fields -> Option A
  4. Quick Check:

    linear.z and angular.x exist in Twist [OK]
Hint: All x, y, z in linear and angular are valid Twist fields [OK]
Common Mistakes:
  • Assuming only linear.x and angular.z exist
  • Thinking z or x components are invalid
  • Confusing Twist with other message types
5. You want your robot to move forward at 0.5 m/s and rotate clockwise at 1.0 rad/s using a Twist message. Which code snippet correctly sets these velocities?
hard
A. msg.linear.y = 0.5 msg.angular.y = -1.0
B. msg.linear.x = -0.5 msg.angular.z = 1.0
C. msg.linear.z = 0.5 msg.angular.x = 1.0
D. msg.linear.x = 0.5 msg.angular.z = -1.0

Solution

  1. Step 1: Understand forward and rotation directions

    Forward movement uses positive linear.x; clockwise rotation is negative angular.z in ROS coordinate system.
  2. Step 2: Match values to correct fields

    Set linear.x to 0.5 for forward speed and angular.z to -1.0 for clockwise rotation.
  3. Final Answer:

    msg.linear.x = 0.5 msg.angular.z = -1.0 -> Option D
  4. Quick Check:

    Forward = linear.x positive, clockwise = angular.z negative [OK]
Hint: Positive linear.x forward, negative angular.z clockwise rotation [OK]
Common Mistakes:
  • Using negative linear.x for forward
  • Using positive angular.z for clockwise rotation
  • Setting wrong axes like linear.z or angular.x