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

Robot model fails to load properly on Humble #41

Closed
Tejas-Shastha opened this issue Dec 14, 2023 · 2 comments · Fixed by #40
Closed

Robot model fails to load properly on Humble #41

Tejas-Shastha opened this issue Dec 14, 2023 · 2 comments · Fixed by #40

Comments

@Tejas-Shastha
Copy link

On Humble, when I build the main branch and launch the provided KR moveit launch file with fake controllers, I notice that the robot model is not properly loaded with the following message in the terminal:

WARNING:root:Cannot infer URDF from `/home/<user>/workspaces/kuka_ws/install/kuka_kr_moveit_config/share/kuka_kr_moveit_config`. -- using config/kuka_kr.urdf
WARNING:root:Cannot infer SRDF from `/home/<user>/workspaces/kuka_ws/install/kuka_kr_moveit_config/share/kuka_kr_moveit_config`. -- using config/kuka_kr.srdf

In rviz I can see that TF for links1-6, tool and flange are also not available.

@Svastits
Copy link
Member

These warnings are issued by the moveit setup assistant, which expects a different folder structure from the convention in ROS-Industrial also used by us. This does not influence the loading of the robot model.

The reason for the not appearing robot meshes is that currently you have to activate the robot manager node even for fake hardware, as described in the readme). This behaviour will change soon, I would suggest to use this branch, as the scheduling is also optimized there.

@Svastits Svastits linked a pull request Dec 14, 2023 that will close this issue
@Tejas-Shastha
Copy link
Author

you have to activate the robot manager node even for fake hardware, as described in the readme

That was indeed the case, as I unfortunately skipped the very last paragraph of the readme in my haste :)

Thank you for both the tips!

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 a pull request may close this issue.

2 participants