-
Notifications
You must be signed in to change notification settings - Fork 123
Provide force-torque sensor data through gz_system to controller_manager - fixes to original PR #610
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
Conversation
Can this PR be also backported to humble? |
we can try ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In principle, LGTM.
Could you please have a look and add this to one of the examples, where [a test exist tests? At least we have a smoke test then and see if the system is launched successfully. Maybe here, or as followup PR, we can test if the interfaces were exported successfully and data is received.
Hi @christophfroehlich, I've successfully run |
I suggest adding a separate demo launch file, and moving also the IMU from example_velocity to it (can be done in a separate PR, as you like). Please update also the docs with necessary changes for using the new sensor, maybe by adding a new subsection here. Thanks! |
Hi @christophfroehlich , I've added files for force torque sensor tests. Unfortunately, I cannot test it on my own setup due to different ROS2 version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding docs and test, I added some requests and further questions
</gazebo> | ||
|
||
<gazebo> | ||
<!-- Joint state publisher --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- Joint state publisher --> |
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've left it because it is in every cart
test.
|
||
force_torque_sensor_broadcaster: | ||
type: force_torque_sensor_broadcaster/ForceTorqueSensorBroadcaster |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
force_torque_sensor_broadcaster: | |
type: force_torque_sensor_broadcaster/ForceTorqueSensorBroadcaster |
doc/index.rst
Outdated
<topic>force_torque_sensor</topic> | ||
</sensor> | ||
|
||
It is important to add this as `reference` sensor in the ``<gazebo>`` tag in your URDF file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please explain. Do you mean the ros2_control tag, i.e.
<sensor name="force_torque_sensor" type="force_torque">
<state_interface name="force.x"/>
<state_interface name="force.y"/>
<state_interface name="force.z"/>
<state_interface name="torque.x"/>
<state_interface name="torque.y"/>
<state_interface name="torque.z"/>
</sensor>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added this comment as it is not directly URDF sensor but SDF, so I've wanted to clarify that is should be defined in <gazebo>
tag in URDF like this:
<gazebo reference="slider_to_cart">
<sensor name="force_torque_sensor" type="force_torque">
<update_rate>10.0</update_rate>
<always_on>true</always_on>
<visualize>true</visualize>
<topic>force_torque_sensor</topic>
</sensor>
</gazebo>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we really need this?
The plugin can also be added to a gazebo tag in the urdf, see here.
If it is really needed, please remove the comment section from this file and add a reference where got this file from.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For ROS2 Humble it is advised to add IMU
and Force-Torque
plugins to world .sdf
file, explained in this issue. I'm not sure if it was changed in newer versions. There is also explanation why IMU
plugin works in URDF file and Force-Torque
not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com>
Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com>
https://github.com/Mergifyio backport kilted jazzy humble |
✅ Backports have been created
|
…ger - fixes to original PR (#610) Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com> Co-authored-by: Kevin DeMarco <kevin@kevindemarco.com> Co-authored-by: Alejandro Hernández Cordero <ahcorde@gmail.com> (cherry picked from commit a678ab9) # Conflicts: # gz_ros2_control/src/gz_system.cpp
…ger - fixes to original PR (backport #610) (#623) * Provide force-torque sensor data through gz_system to controller_manager - fixes to original PR (#610) Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com> Co-authored-by: Kevin DeMarco <kevin@kevindemarco.com> Co-authored-by: Alejandro Hernández Cordero <ahcorde@gmail.com> (cherry picked from commit a678ab9)
…ger - fixes to original PR (backport #610) (#624) * Provide force-torque sensor data through gz_system to controller_manager - fixes to original PR (#610) Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com> Co-authored-by: Kevin DeMarco <kevin@kevindemarco.com> Co-authored-by: Alejandro Hernández Cordero <ahcorde@gmail.com> (cherry picked from commit a678ab9)
This PR is a fixed version of #273 by Kevin DeMarco , unfortunately the author of original PR has not made any changes since 2024, so I've made this one in order to finally have hardware interface for
ForceTroque
sensor. I've tried to preserve the authorship and committer-ship of the commits made by the first PR submitter.