No version for distro humble showing github. Known supported distros are highlighted in the buttons above.
Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange

No version for distro jazzy showing github. Known supported distros are highlighted in the buttons above.
Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange

No version for distro kilted showing github. Known supported distros are highlighted in the buttons above.
Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange

No version for distro lyrical showing github. Known supported distros are highlighted in the buttons above.
Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange

No version for distro rolling showing github. Known supported distros are highlighted in the buttons above.
Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange

Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange

No version for distro galactic showing github. Known supported distros are highlighted in the buttons above.
Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange

No version for distro iron showing github. Known supported distros are highlighted in the buttons above.
Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange

No version for distro melodic showing github. Known supported distros are highlighted in the buttons above.
Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange

No version for distro noetic showing github. Known supported distros are highlighted in the buttons above.
Package symbol

humanoid_base_footprint package from bitbots_main repo

bitbots_blackboard bitbots_body_behavior bitbots_bringup bitbots_cargo bitbots_diagnostic bitbots_docs bitbots_education bitbots_extrinsic_calibration bitbots_ipm bitbots_parameter_blackboard bitbots_player_state bitbots_robot_description bitbots_teleop bitbots_tts bitbots_utils bitbots_whistle_detector system_monitor bitbots_animation_rqt bitbots_animation_server bitbots_emergency bitbots_hcm bitbots_head_mover bitbots_rl_motion bitbots_splines bitbots_msgs bitbots_global_planner bitbots_localization bitbots_localization_handler bitbots_odometry bitbots_path_planning piplus_animations piplus_description bitbots_mujoco_sim bitbots_team_communication bitbots_team_data_sim_rqt bitbots_vision bitbots_ball_filter bitbots_robot_filter audio_common audio_common_msgs biped_interfaces bitbots_tf_buffer domain_bridge dynamic_stack_decider dynamic_stack_decider_visualization game_controller_hsl game_controller_hsl_interfaces humanoid_base_footprint imu_complementary_filter rviz_imu_plugin ipm_image_node ipm_interfaces ipm_library ipm_service launch launch_pytest launch_testing launch_testing_ament_cmake launch_xml launch_yaml test_launch_testing livelybot_bringup livelybot_msg livelybot_oled livelybot_power livelybot_serial serial yesense_imu particle_filter ros2_numpy ros2_python_extension rot_conv soccer_field_map_generator soccer_geometry_msgs soccer_interfaces soccer_model_msgs soccer_vision_2d_msgs soccer_vision_3d_msgs soccer_vision_attribute_msgs soccer_ipm soccer_vision_3d_rviz_markers udp_bridge zed_msgs zed_components zed_ros2 zed_wrapper

ROS Distro
github

Package Summary

Version 1.2.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/bit-bots/bitbots_main.git
VCS Type git
VCS Version main
Last Updated 2026-10-26
Dev Status UNKNOWN
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Publishes a transform to the base footprint of the robot, based on the orientation and position of the feet.

Maintainers

  • Jasper Güldenstein
  • Hamburg Bit-Bots

Authors

  • Jasper Güldenstein

humanoid_base_footprint

Build and Test (humble) Build and Test (jazzy) Build and Test (rolling)

This ROS2 package includes a node which provides the base footprint frame for any humanoid robot following REP - 120.

Only ROS2 Rolling is supported currently.

Installation

Only source installation is available currently. Run the following in your ROS workspace:

git clone https://github.com/ros-sports/humanoid_base_footprint.git src/humanoid_base_footprint
vcs import src < src/humanoid_base_footprint/dependencies.repos --recursive
colcon build

Usage

To run the node:

ros2 run humanoid_base_footprint base_footprint

Description

Definition of the base footprint frame (from here):

The base_footprint is the representation of the robot position on the floor. The floor is usually the level where the supporting leg rests, i.e. z = min(l_sole_z, r_sole_z) where l_sole_z and r_sole_z are the left and right sole height respecitvely. The translation component of the frame should be the barycenter of the feet projections on the floor. With respect to the odom frame, the roll and pitch angles should be zero and the yaw angle should correspond to the base_link yaw angle.

Rationale: base_footprint provides a fairly stable 2D planar representation of the humanoid even while walking and swaying with the base_link.

The node listens to Phase msgs that define the current stance of the robot. By default, it will listen on the walk_support_state topic, but you can define a list of topics on the support_state_topics parameter.

If the links of your robot have non-standard names you can set the following parameters: base_link_frame, r_sole_frame, l_sole_frame, l_sole_frame, odom_frame

The resulting frame will be published as base_footprint but the name can be changed by setting the base_footprint_frame parameter.

CHANGELOG
No CHANGELOG found.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged humanoid_base_footprint at Robotics Stack Exchange