Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide force-torque sensor data through gz_system to controller_manager #273

Open
wants to merge 4 commits into
base: rolling
Choose a base branch
from

Conversation

SyllogismRXS
Copy link

This PR provides force-torque sensor data to Gazebo's controller_manager in a similar way to how the IMU data is currently provided. I made this change in order to test the ros2_controllers' admittance_controller in Gazebo/Ignition 6.16.0.

sim::Entity sim_ft_sensors_ = sim::kNullEntity;

/// \brief An array per FT
std::array<double, 6> ft_sensor_data_;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

include <array>

}
}

static const std::map<std::string, size_t> interface_name_map = {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

include <cstddef>

@Nibanovic
Copy link

Rebased to master and tested with gazebo Harmonic on ros2 rolling

Can confirm everything works as expected:

  • instantiated force_torque_sensor in URDF
  • ran gazebo + ros2_control

state_interfaces set up as expected.

  • connected force_torque_sensor_broadcaster controller to those state_interfaces

Echoed wrench topic shows the same values as gazebo sensor topic.

In my opinion, this feature can be merged after rebasing branch to master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants