[bug] Handle case when a xacro has a .urdf extension
See original GitHub issuedescribe the bug (actual behavior)
I have a standard xacro file to create an URDF (that unfortunately cannot be shared here).
It contains meshes on the .stl
format for visuals, and some gazebo
tags.
Running ROS: Preview URDF
show a partial model.
Running xacro manually, and previewing the resulting URDF displays correctly.
expected behavior The full model should be rendered.
screenshots
Rendering the xacro file :
Rendering the resulting URDF after manual conversion :
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
[bug] URDF preview sometimes doesn't load up the model #93
Repro Steps: Active the vscode-ros extension. Open a workspace which are ... Open up an xacro file in the editor. Run URDF preview...
Read more >Tutorial: Using a URDF in Gazebo
This tutorial explains the necessary steps to successfully use your URDF-based robot in Gazebo, saving you from having to create a separate SDF...
Read more >Confused about Xacro and URDF - ROS Answers
Hey together, I am a little bit confused about the use case of xacro and urdf. I my case I have an robot...
Read more >Getting Ready for ROS Part 7: Describing a robot with URDF
Typically, the “main” URDF/xacro has the extension .urdf.xacro , but the “included” ones can vary a little. Sometimes they will just use ...
Read more >(PDF) Understanding Xacro Misunderstandings - ResearchGate
PDF | The Xacro XML macro language extends the Universal Robot Description Format (URDF) and is part of a critical toolchain from geometric....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@PymZoR Thanks for clarifying. I changed this to an improvement, as it would require deep introspection.
I found the cause of the bug. Our xacro file was in fact called
model.urdf
.An elegant fix would be to look after the tag
<robot xmlns:xacro="http://www.ros.org/wiki/xacro">
instead of the file extension.