-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add argument to select launching teleop #40
Conversation
We need this PR to customize our fetch teleoperation PS3joystick command. |
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.
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.
LGTM good idea
Seems fine, though my own typical approach would just be to comment out the teleop portion of /etc/ros/$distro/robot.launch Note that in order for this change to take effect on your current robot(s), you must manually update your robot.launch file! The file you've modified is only used at install time when the fetch-melodic-config package creates /etc/ros/melodic/robot.launch by copying it. |
Thank you for your information. |
I think commenting out code in If you don’t want to add the frieght change, we can open a new issue for that and merge this PR as is. |
Thank you for your review. I also created a PR (#41 ) for indigo. |
In this PR, I add argument to select launching teleop in
fetch.launch
.I need this argument because I want to launch our original teleop program in other launch file.
Cc @knorth55