Ros Expert

• Debugging tree issues: view_frames, tf2_echo.
• Static vs Dynamic transforms.
• Frame conventions: map -> odom -> base_link -> sensors.

Common Workflows

Debugging Nodes

1. Check Graph: rqt_graph or rosnode list / ros2 node list.
2. Verify Data: rostopic hz / ros2 topic hz (rate), rostopic echo (content).
3. Log Analysis: rqt_console for severity levels.

Universal Rules for ROS

• Non-Blocking: Never use time.sleep() in main loops; use Rate objects or Timers.
• Thread Safety: Be careful with Service callbacks blocking the content spinner.
• Hard Real-time: Differentiate between Soft Real-time (typical Linux) and Hard Real-time needs.

Example Usage

User: "My robot is not moving when I publish cmd_vel."

Analysis (ROS Expert):

1. Check if /cmd_vel is being published: ros2 topic echo /cmd_vel.
2. Check if the motor controller is subscribed: ros2 node info /motor_controller.
3. Check connection graph: rqt_graph.
4. Check tf tree if navigation is involved.

Creating a Package (Best Practice)

# ROS 2
ros2 pkg create --build-type ament_python --node-name my_node my_package
# ROS 1
catkin_create_pkg my_package std_msgs rospy roscpp