cartesian motion controller leads to bizzare movement

[shrutichakraborty]

Hello @fzi-admin @fmauch ,

I am using the cartesian motion controller with ur10e robot on ros2. after launching the robot and switching the controller, the robot makes some abrupt small motions even though nothing is commanded. Is this expected behaviour?

Also I want to know which frame should the target_pose be in? I am assuming it should be the same frame as the end efffector.

Thanks!

[stefanscherzinger]

@shrutichakraborty
I'm picking up older issues, sorry for not responding earlier.

after launching the robot and switching the controller, the robot makes some abrupt small motions even though nothing is commanded. Is this expected behaviour?

This sounds a little like what I experienced in this issue. Is this still happening today?

Also I want to know which frame should the target_pose be in?

The target_frame is with respect to the specified robot_base_link. The controllers will complain if that frame is not specified correctly in the message's header.

[shrutichakraborty]

@shrutichakraborty I'm picking up older issues, sorry for not responding earlier.

after launching the robot and switching the controller, the robot makes some abrupt small motions even though nothing is commanded. Is this expected behaviour?

This sounds a little like what I experienced in this issue. Is this still happening today?

Also I want to know which frame should the target_pose be in?

The target_frame is with respect to the specified robot_base_link. The controllers will complain if that frame is not specified correctly in the message's header.

Hi @stefanscherzinger, thanks for your response, after tuning the error_scale and iterations parameters I was able to get a setup where there is no longer bizzare movements on switching controller; However, when commanding positions, I still have the issue where I see the robot vibrate (or wobble) around the end effector once it reaches (or gets close to) the commanded pose. I don't know if the issue here can be resolved by tuning the parameters but I have so far not found any combination that avoids this behaviour.. Any suggestions?