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

[libgazebo_ros2_control] and [libgazebo_ros_control.so] causes different behavior in FT-sensor published wrench values. #1512

Open
hazeezadebayo opened this issue Nov 7, 2023 · 0 comments

Comments

@hazeezadebayo
Copy link

Hi everyone!

In this package - https://github.com/hazeezadebayo/ft_ws -, I have provided ros1 (noetic) and ros2 (humble) environments for FT-sensor with libgazebo ros/ros2 control using docker for easy reproducibility. The URDFs are exactly the same with the respective implementations regarding the ros-distro of use. The problem here is that, at start-up FT values at all joints are exactly same for both distros. However, once motion is commanded, the discrepancies start and the values are no longer the same. As a personal test, I implemented Moveit dynamic solver to generate torques to control the arm on ROS2 and the command values generated validates the ros1 implementation FT values and not the ros2's. Any help or suggestion would be appreciated.

My Gazebo version is 11.11.0 - Copyright (C) 2012 Open Source Robotics Foundation.

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

No branches or pull requests

1 participant