PoseSensor
semantic component (backport #1775)
#1786
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a new semantic components for robots or sensors that can meassure a cartesian pose. I will add a PR for a
pose_broadcaster
controller using this toros2_controllers
shortly.My use-case for this functionality is for robots that can provide their cartesian TCP pose in addition to their normal joint state (e.g. UR and Kuka arms). This can be more accurate than forward kinematics, as the robot can use its factory calibration for determining this pose. In the future, there could also be different kinds of sensors implementing this (e.g. mocap) to allow their data to be used in a controller.
I tried my best to keep the implementation close to the existing fts and imu components. The tests should also cover similar use, in particular loading of the controller and lifecycle transitions as well as verifying a published pose.
This is an automatic backport of pull request #1775 done by Mergify.