Xacro Support

Many real robot descriptions — especially ROS-native ones like the Franka Emika Panda and FR3 — aren’t published as a plain URDF at all, but as Xacro (.xacro), an XML macro language layered on top of URDF. ARMOR expands Xacro on-device, so you can import a robot straight from its native repository without running a separate build step first.

What gets expanded

When you load a .xacro file (or select a folder whose entry point is one), ARMOR’s Xacro preprocessor resolves:

The result is expanded into a real, in-memory URDF — links, joints, and mesh references — the same representation ARMOR uses for any other robot, so every editor, viewer, and export feature works identically afterward. There’s nothing in the app that distinguishes a robot that started as Xacro from one that started as a plain URDF once it’s imported.

Franka Emika Panda robot arm rendered in ARMOR's 3D viewer, imported from the gallery's Xacro-only source repository

The Franka Emika Panda, imported straight from its Xacro-only source repository — same viewer, editor, and export tools as any other robot.

Importing a Xacro file from your device

Xacro expansion is not limited to gallery links. A .xacro file you pick with Select File, or find inside a folder you pick with Select Directory, is expanded on your device by the same preprocessor. The import screen shows Expanding xacro while it works. When you pick a folder, a plain .urdf file is listed ahead of a .xacro file, so a package that ships both offers the one that needs no expansion first.

There is no screen for entering Xacro arguments. ARMOR uses the default value that each <xacro:arg> declares in the file itself. For a Franka FR3 file, whose hand argument defaults to false, that means the arm imports without the gripper hand. To get a different variant, use the matching gallery entry, which supplies the arguments for you, or change the default in the file before importing.

What this means in practice

Next Steps