Skip to content

Conversation

@saikishor
Copy link
Member

@saikishor saikishor commented Dec 10, 2025

This PR add changes that are needed to support torque and force command and state interfaces. Basically, it remaps to the effort part of the interface.

Copy link
Collaborator

@eholum-nasa eholum-nasa left a comment

Choose a reason for hiding this comment

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

Nice! Is the difference for say, prismatic vs revolute joints?

The only other comment I have, because of the question on the test robot, is that it's probably worth updating the README to show that effort/force/torque interfaces are supported, but that the differences are exclusively semantic... We could also just add a note?

**Note:** The `torque` and `force` command/state interfaces are semantically equivalent to `effort`, and map to the same underlying data in the sim.

saikishor and others added 2 commits December 15, 2025 20:14
Co-authored-by: Erik Holum <erik.holum@nasa.gov>
Co-authored-by: Erik Holum <erik.holum@nasa.gov>
Copy link
Collaborator

@eholum-nasa eholum-nasa left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks!

@saikishor saikishor merged commit 92fa27a into ros-controls:main Dec 15, 2025
5 checks passed
@saikishor saikishor deleted the support_torque_force_interfaces branch December 15, 2025 19:19
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.

2 participants