-
Notifications
You must be signed in to change notification settings - Fork 172
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
Error when I use move_to_start #107
Comments
I have modify the move_to_start_launch file like this:
And then run the move_to_start.py in an other terminal.
When I run move_to_start.py I get that in the first terminal:
And in the second one I get that:
|
In fact the effort_joint_trajectory_controller and position_joint_trajectory_controller are only generate with franka_ros default_controllers.yaml file but this file is never used in move_group.launch |
For both of you, the controller_spawner is started within the wrong namespace as stated in #97 (comment):
Looks like this is a bug only recently introduced by #106. Please try the previous commit cfe7d44, or alternatively the fixup #108. |
I try that fix: But the panda_moveit_config/config/ros_controller.yaml is empty. |
Here is the diff I made to make it work
and
|
It seems it worls for me also. Thank you @arnauddomes |
hello
Following the previous discussion on that issue:
#97
I work on Noetic on Ubuntu 20.04. I have trouble to use move_to_start.launch from franka_ros. I modified the move_to_start.launch file according to @rhaschke advice.
I get that log:
The text was updated successfully, but these errors were encountered: