ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

How to avoid the axis jumping when the orientation is constrainted

asked 2017-11-22 01:11:02 -0600

pdmike gravatar image

updated 2017-11-23 00:33:57 -0600


Now the end-effector's orientation constraints is implemented in my offline simulation in Moveit. It can be seen that the orientation of end-effector is keeping horizontal to the ground. But during the motion, several axis of UR-10 jumps anyway. So do you guys know how to avoid the unexpected pose?


On the other hand, i am using Trac IK to UR-10 and the solve_type is inevitably set as 'speed', which has been changed as 'distance' in kinematics.yaml, when running the c++ code. Will this setting affects the axis jumping?

[ INFO] [1511333074.249636452]: Looking in private handle: /move_group_interface_tutorial for param name: arm/position_only_ik
[ INFO] [1511333074.250346507]: Looking in private handle: /move_group_interface_tutorial for param name: arm/solve_type
[ INFO] [1511333074.251106283]: Using solve type Speed
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2018-01-10 19:06:09 -0600

rmck gravatar image

Late response but I believe this is related to a known moveit namespace issue, reported here:

I resolved it on my system by adding the following code to my movegroup.launch file;

<group ns="move_group">
    <rosparam command="load" file="$(find MY_PACKAGE)/config/kinematics.yaml"/>

This ensured the correct solve type was used.

edit flag offensive delete link more


yes, the parameters of kinematics can been correctly loaded when starting the launch-file. But after that, when i run a code with C++, it still change back to solve type Speed. You can see the last post in link text in Nov is mine.

pdmike gravatar image pdmike  ( 2018-01-10 19:24:56 -0600 )edit

Ahhh right, I see. I also added the same load command to my C++ launch file. That resolved the issue for me. It seems to be a namespace problem. If you ensure the parameters are loaded in the same namespace as your C++ component it should work.

rmck gravatar image rmck  ( 2018-01-10 19:53:07 -0600 )edit

Question Tools



Asked: 2017-11-22 01:11:02 -0600

Seen: 260 times

Last updated: Jan 10 '18