Open osrf-migration opened 8 years ago
Original comment by Joseph Coombe (Bitbucket: Joseph Coombe).
Is this a bug and, if so, how serious?
I'm working on a Gazebo Plugin that controls a joint using force-feedback, and I'm curious if/how this might affect the controller.
Thanks!
Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
This was initially submitted as pull request #2110 by @vorndamme though it did not include a test, so it was moved to this issue while a test is written.
Original description:
Changed calculation of parent link force/torque. Force on child is calculated in world frame (was child frame before), where the parent force/torque can simply be the negative of the child force/torque (before, parent force/torque was set to the negative child force/torque, which was specified in child link frame and was added to the overall torque in parent link frame). Now all torques are calculated in world frame, summed up and transformed into child and parent frame in the end.
patch: