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

Order of JointInterface and ActuatorInterface #1745

Open
qiayuanl opened this issue Sep 5, 2024 · 1 comment
Open

Order of JointInterface and ActuatorInterface #1745

qiayuanl opened this issue Sep 5, 2024 · 1 comment
Labels

Comments

@qiayuanl
Copy link

qiayuanl commented Sep 5, 2024

Describe the bug
The order of JointInterface and ActuatorInterface are given by joint_names, and actuator_names, and the order is used in all multip-acutaor-multip-joint transmission mapping.

However, the get_name() use std::set to remove duplicate name, resulting in ascending lexicographical order. As a result, there is no way (expected changing the name of actuators) to set the correct order according to <role> tag in URDF, since the order of interface passing to Transmission::configure() doesn't affect anything.

Environment:

  • OS: Ubuntu22.04
  • Version: Humble
  • Anything that may be unusual about your environment

Additional context
BTW, I can't find any example of usage of <role> tag in URDF.

@qiayuanl qiayuanl added the bug label Sep 5, 2024
@christophfroehlich
Copy link
Contributor

Additional context BTW, I can't find any example of usage of <role> tag in URDF.

Contributions are welcome, maybe in addition to https://github.com/ros-controls/ros2_control_demos/tree/master/example_8

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

No branches or pull requests

2 participants