[robotiq_ft_sensor] Add launch files to start sensor, and Add adjusting offset features for a launch file#11
Open
Michi-Tsubaki wants to merge 4 commits intoTAMS-Group:noetic-develfrom
Conversation
Author
|
Related PR/issue (Why I make this PR here) |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, there is a launch file to start visualizing sensor state in Rviz. However, there are no launch files to start sensor.
In this PR, I added a launch file to start force torque sensor.
roslaunch robotiq_ft_sensor read_sensor.launchMy sensor has an bias. I added a service call scripts to offset this bias and create launch to start this call.
roslaunch robotiq_ft_sensor read_sensor_offset.launch↓
Before
After