differential-drive-model

To model a differential-drive robot in URDF for ROS 2, define a frame hierarchy with base_footprint, base_link, left_wheel_link, right_wheel_link, and caster configurations. Specify fixed base joints, drive wheel joints, inertia, and visual properties for accurate simulation kinematics.

The correct URDF structure for differential drive odometry requires a base_footprint and base_link with properly configured wheel joints. Integrating the optional Gazebo diff-drive plugin ensures consistent odometry computation and ground-truth benchmarking across simulation and real-world Nav2 workflows.

Yes, your ROS 2 robot URDF needs base_footprint for Nav2 compatibility. The mandatory URDF structure specifies base_footprint alongside base_link and wheel links to ensure proper frame transformations and consistent kinematics across navigation and simulation environments.

Yes, you can use this differential drive URDF model for both simulation and real-world deployment. It defines a detailed structure with proper joint configurations and Gazebo plugin integration to ensure consistent odometry and kinematics across both environments.

The best way to configure wheel joints for a ROS 2 differential drive robot is to define left_wheel_link and right_wheel_link with proper drive wheel joints, inertia, and visual properties. This mandatory URDF structure ensures accurate frame transformations and realistic simulation behavior.

Inconsistent odometry between Gazebo and real hardware often stems from an incorrect URDF frame hierarchy. Defining the mandatory base_footprint, base_link, and wheel links with proper joint configurations and Gazebo plugin integration ensures consistent odometry and kinematics across environments.