-
Notifications
You must be signed in to change notification settings - Fork 310
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
initial_value params for state interfaces not respected #817
Comments
This is definitely not the behavior you want to have. So, what happens is that JTC gets the initial values from hardware interface after it is started. If those values are wrong, then this can happen.
|
Hi @destogl, Many thanks for the reply and apologies for the late follow up, I wasn't subscribed to repo notifications and just enabled that.
|
@Yadunund and news? |
Closing because this does not seem to be related directly to the framework. Feel free to reopen. |
Thanks @destogl, I think this is most likely an issue with the implemented hardware_interface. |
The issue is indeed with the |
Background
Hi all,
My setup is as follows:
I've been using the
JointTrajectoryController
to command a couple of ABB industrial robots. I'm using this hardware interface implementation. I notice that once the controller starts and the command interfaces are claimed (both position and velocity), the robot always gets commanded to reach0.0
joint value for all its joints. This is despite explicitly specifying theinitial_value
params for each position and velocity state interface in theros_control.xacro
file.My expectation is that once the interfaces are claimed by the controller, the robot will continue to remain idle in it current joint configuration (as specified by the
initial_value
param) and not move to 0.0 joint values.Is this happening due to an error I might have made in my
ros2_control.xacro
orcontrollers.yaml
files? Or could it be due to the implementation of the hardware_interface itself? Any insights would greatly help me in debugging this problem.Thanks in advance!
Edit
I should add that once the robot does move to 0.0 joint values, i'm able to execute trajectories without any problems. It's just the initial movement that I would like to avoid.
The text was updated successfully, but these errors were encountered: