-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
change attachForceTorqueSensorToJoint and attachContactSensorToLink
- Loading branch information
Showing
2 changed files
with
45 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
35c239f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice ! Does it work ?
35c239f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it does !
Returned wrench is in link frame for both sensors, child link for
GazeboForceTorqueSensor
.You can get the link in question using
my_sensor->getBaseLinkName()
.Still, for the
ContactSensor
, I inferred that theJointWrench
s in Gazebo contact messages are in link frame, at the CoG. This is not what is stated in the Gazebo documentation, though.I submitted a comment on Gazebo repo here, waiting for confirmation.
A note in the code documentation is there.
So far both sensors appear to be consistent with each other, so this is good news.
I'll upload a simple pendulum example later to orca_demos to demonstrate that.
35c239f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @iadev ! I think a comment on an old commit whose author is not working anymore on Gazebo has quite a low visibility. I would suggest to either open a new issue, or even better do a pull fixing documentation on the Gazebo side (this is typical the way for which it is more probable to get feedback).
Regarding the FT frame, you are using
<frame>child</frame>
so you should not have any problem, but you may be nevertheless be interested in this issue: https://bitbucket.org/osrf/sdformat/issues/130/position-part-of-force_torque-sensor-pose .35c239f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @traversaro, thanks for the follow up !
I didn't take the time to file an issue yet, so I dropped the comment to keep track of it in the meantime.
Concerning the FR frame, yes that's exactly why I forced the use of
<frame>child</frame>
, to avoid any confusion/issues.Thanks for the link to the issue #130, indeed it's interesting to be aware of that !