Robot Description Issues#

The controller manager launch expands a xacro file into the robot description before it starts anything else. If that expansion fails the launch aborts before any controller loads, and the error comes from xacro rather than from Isaac ROS Deploy.

The Launch Aborts With a xacro or URDF Error#

Symptom#

The launch exits during startup and no controller is loaded. The error text names xacro or a URDF parsing problem, and is easy to lose among the rest of the launch output.

Solution#

Reproduce the expansion by hand to see the error on its own. Each hardware type expands a different xacro file with a different set of arguments. For the Unitree G1:

# hardware_type:=mujoco
xacro $(ros2 pkg prefix --share unitree_g1_description)/urdf/g1_with_ros2_control_full.urdf.xacro \
    mujoco_model_path:=<path_to_mjcf> enable_viewer:=true

# hardware_type:=real
xacro $(ros2 pkg prefix --share unitree_g1_description)/urdf/g1_real_hardware.urdf.xacro \
    network_interface:=<your_interface> mode_machine:=5 with_hands:=true

# hardware_type:=isaacsim
xacro $(ros2 pkg prefix --share unitree_g1_description)/urdf/g1_isaacsim.urdf.xacro \
    joint_states_topic:=/isaac_sim_joint_states \
    joint_commands_topic:=/isaac_sim_joint_commands \
    imu_topic:=/isaac_sim_imu

A successful run prints the expanded URDF to standard output. The xacro files and the arguments each one accepts are in

Source code available on GitHub.

, and the launch file that selects between them is unitree_g1_controller_manager.launch.py.

For a custom robot, run the same check against your own ros2_control xacro. This is the first of the validation steps in How to bring your own embodiment. Passing it is what lets you attribute a later failure to the controller configuration rather than to the description.