The confirmed data path is /imu_broadcaster/imu, identified as a ROS 2 topic after the ROSbot 2 PRO documentation was updated. The available evidence does not confirm a separate /imu topic or state whether roll, pitch, and yaw are published directly.
Use the Confirmed IMU Topic
Look for /imu_broadcaster/imu instead of assuming the topic name is /imu. First list the active topics, then verify that the confirmed topic appears and produces IMU data.
Check the ROS Environment
The reported setup mixes a ROS 1 command—rosrun teleop_twist_keyboard teleop_twist_keyboard.py—with a topic later identified specifically as ROS 2. The evidence also asks whether the installed OS image uses ROS Noetic. Establish which ROS environment is running before interpreting a missing topic; the evidence does not establish that the ROS 1 and ROS 2 procedures are interchangeable.
Verify the Deployment Configuration
- Confirm that the installed OS image is the ROSbot 2 PRO image intended for ROS Noetic if following the referenced Noetic procedure.
- Compare the robot's
compose.yamlfile exactly with the current ROSbot 2 PRO quick-start configuration. - List the available topics and check specifically for
/imu_broadcaster/imu. - If the topic remains absent, record the installed firmware and configuration revisions before escalating through the manufacturer's official support channel.
A reproduced case suggested a slight incompatibility between the latest firmware and the referenced file, but this remained a hypothesis in the evidence. Treat configuration mismatch and firmware compatibility as separate checks until the topic test confirms the cause.
Separate IMU and Motion Symptoms
The same report noted that battery, buttons, cmd_ser, and velocity were absent, while keyboard teleoperation produced no usage output and no robot motion. These symptoms show that the issue may extend beyond one IMU topic, but the evidence does not prove a common root cause. Verify the environment and deployment first, then retest topic discovery and teleoperation independently.
FAQ
What is the ROSbot 2 PRO IMU topic?
The confirmed ROS 2 topic is /imu_broadcaster/imu. The evidence does not confirm that a separate /imu topic exists.
Why is /imu_broadcaster/imu missing on ROSbot 2 PRO?
Check the installed OS and ROS environment, then compare compose.yaml exactly with the current quick-start configuration. A firmware-to-configuration incompatibility was suspected in one reproduced case but was not confirmed.
Does the ROSbot IMU topic publish roll, pitch, and yaw directly?
The evidence confirms access to IMU data through /imu_broadcaster/imu, but it does not specify whether roll, pitch, and yaw are direct fields. Inspect the topic's message contents before selecting any orientation conversion.
