Skip to content
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

remove use_mock_hardware from moveit launchfile #853

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

fdurchdewald
Copy link
Contributor

The scaled JTC can be used on fake hardware as well. Therefore, there is no real reason for keeping the use_mock_hardware argument in the MoveIt launch file.

@fmauch
Copy link
Collaborator

fmauch commented Oct 25, 2023

@fdurchdewald Could you please fix the duplicated target in the usage.rst file? Thanks!

@fmauch fmauch self-requested a review November 9, 2023 14:17
@fmauch fmauch linked an issue Nov 9, 2023 that may be closed by this pull request
2 tasks
@destogl
Copy link
Contributor

destogl commented Nov 15, 2023

@fdurchdewald does this means that you will have different robot descriptions used on driver launch and MoveIt launch

@fmauch
Copy link
Collaborator

fmauch commented Nov 15, 2023

@fdurchdewald does this means that you will have different robot descriptions used on driver launch and MoveIt launch

No, we should remove the description from the moveit launch. AFAIK it takes the one from the RSP's description topic by now.

@fmauch
Copy link
Collaborator

fmauch commented Nov 19, 2023

Before merging this, we should consider UniversalRobots/Universal_Robots_ROS2_Gazebo_Simulation#22

What do we do about the scaled jtc in gazebo? Probably we should still provide an option for the default controller.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

remove use_mock_hardware from moveit launchfile
3 participants