-
Notifications
You must be signed in to change notification settings - Fork 340
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
effort_controllers/joint_position_controller from ROS1 #373
Comments
To be more specific, I am trying to control an arm to a set joint position, but with limited torque, so that when an external force (larger than the torque limit) is present, the arm will deviate from the position (with some kind of compliant behavior). Once the external force is gone or become smaller, the arm will tend to move back to the set joint position. Basically some kind of passive motion. Back in ROS1, I can achieve such behavior with effort_controllers/joint_position_controller. I am wondering if ros2_controller has something similar to this. |
This functionality is currently missing but it's fairly straight forward to
port it from ROS1. I'd happily review a PR for this
…On Tue, 5 Jul 2022, 20:15 Tianyu Li, ***@***.***> wrote:
To be more specific, I am trying to control an arm to a set joint
position, but with limited torque, so that when an external force (larger
than the torque limit) is present, the arm will deviate from the position
(with some kind of compliant behavior). Once the external force is gone or
become smaller, the arm will tend to move back to the set joint position.
Basically some kind of passive motion. Back in ROS1, I can achieve such
behavior with effort_controllers/joint_position_controller. I am wondering
if ros2_controller has something similar to this.
—
Reply to this email directly, view it on GitHub
<#373 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA24PYKEJUYLOV3YZQVUCD3VSSCWXANCNFSM52HIHHKA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
It needs revival :) |
@tonylitianyu you wanted to contribute to this. Is this still the case? |
@destogl Given my recent schedule, it would be difficult. Sorry about that. |
There was a sync a few days ago. If you |
@bmagyar I tried that, but i still seem to be getting errors while building. To give you an idea of my setup:
here is the error message I get while building. |
Have you tried with --allow-overriding as per the error message? We
generally do not recommend having the same package you are trying to build
from source installed as binary too as ros2 seems to still have issues with
it.
…On Wed, 9 Nov 2022, 20:57 Aadiv Shah, ***@***.***> wrote:
@bmagyar <https://github.com/bmagyar> I tried that, but i still seem to
be getting errors while building. To give you an idea of my setup:
- Ubuntu 22.04
- ROS2 Humble
- In my home directory, ros2 workspace (ros2_ws)
- I have the binary install of ros2_controls and ros2_controllers
(ros-humble-ros2-control and ros-humble-ros2-controllers)
- In ~/ros2_ws/src i have cloned the effort_controllers package from
here
<https://github.com/ros-controls/ros2_controllers/tree/effort_group_position_controller/effort_controllers>
here
<https://drive.google.com/file/d/1OT8YuICxlYe7KYcne9Gp1ZbFrBrXBSrg/view?usp=sharing>
is the error message I get while building.
—
Reply to this email directly, view it on GitHub
<#373 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA24PYKPTOVMIRPMIP34IRDWHP6ZPANCNFSM52HIHHKA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@bmagyar yes I did try, it is still giving me build issues/issues in the code itself as shown in the attached file. Besides, I removed the binary install for the “effort_controllers” package, and I was getting the same errors |
ros1_controllers has effort_controllers/joint_position_controller that accepts position commands and targets an effort-controlled joint. But in this repo, the effort_controllers only accept group effort commands. Is it moved somewhere else or the feature is still missing?
The text was updated successfully, but these errors were encountered: