Paste a URDF/Xacro file and instantly:
• Preview the robot in 3D
• Validate structure live
• Share public robot links
• Export to Isaac Sim / MuJoCo / SDF
• Auto-fix common URDF problems
No ROS install required.
The goal is to make robot development feel more like modern web development tools.
Playground:
12 (anonymous) posts about the same tool in a little over a month? I think that’s enough, don’t you? You don’t seem to contribute anything else to this community either.
Fair feedback. I got excited sharing progress because I’m building this independently and trying to get it in front of ROS developers.
I’ll slow down on promotion posts and focus more on contributing to discussions, helping others, and sharing technical insights instead of repeated announcements.
Appreciate the honesty.
I agree with Christian this looks like wall-posting. I think the usual way is to share updates in a single topic where you announced your tool (so that people who were interested in it the first time will get notified), and mention only big advancements as new topics.
But otherwise, it’s interesting to see where you’re moving the tool!
does this support Python-based xacro features like xacro.load_yaml() yet, or would I get stuck on robots that rely on those?
For example, Andino uses:
<xacro:property name="caster_wheel_props" value="${xacro.load_yaml(caster_wheel_yaml)}"/>
Since that depends on Python + filesystem access during xacro processing, I’m wondering whether the browser tool can handle those cases or if it currently only supports basic xacro parsing.
Great question and an honest answer: no, not yet.
The playground currently accepts a single pasted xacro string and runs the standard xacro Python package on it server-side. So it handles:
<xacro:property>, <xacro:macro>, <xacro:if> / <xacro:unless>${...} math/string expressions<xacro:arg> defaultsWhat it can’t handle yet, and Andino hits two of them:
xacro.load_yaml(...) needs the YAML file on disk next to the xacro$(find <pkg>) needs a ROS package on the AMENT/ROS_PACKAGE_PATH<xacro:include filename="..."> to a sibling file no workspace contextSo for Andino specifically, the caster_wheel_props line would fail because the YAML never made it into the sandbox.
Multi-file workspace upload (drag a folder, or paste a GitHub repo URL, and we resolve $(find …) + load_yaml against it) is the next thing on the playground roadmap it’s the single biggest gap right now for real robots like Andino, UR, and PAL. If you’d find that useful, I can ping you when it ships; happy to use Andino as the test case so I know it actually works end-to-end and not just on toy URDFs.
In the meantime, if you xacro andino.urdf.xacro > andino.urdf locally and paste the expanded URDF, the 3D preview, validator, auto-fix, USD export etc. all work on it.
@peci1 That makes sense, thanks for clarifying the community expectations.
I’ll keep future updates consolidated into the main thread unless there’s a major new feature or release. I’m still learning how discourse/open-source communities usually handle product updates.
Appreciate the constructive feedback and glad you find the project interesting.