husarion_components_description

URDF models of sensors and other components offered alongside Husarion robots.

Overview

Components (cameras, lidars, frames, manipulators, …) are attached to a robot from a single YAML config: a list of entries, each picking a component by its type code and placing it on a parent link. Husarion robot packages (e.g. rosbot_description) read this config and build the URDF for you; you can also instantiate a component’s xacro macro directly (see Advanced).

Build

# create workspace folder and clone husarion_components_description
mkdir -p ros2_ws/src
cd ros2_ws
git clone https://github.com/husarion/husarion_components_description.git src/husarion_components_description

# in case the package will be used within simulation
export HUSARION_ROS_BUILD_TYPE=simulation

rosdep update --rosdistro $ROS_DISTRO
rosdep install -i --from-path src --rosdistro $ROS_DISTRO -y
colcon build

Usage via config

List the components you want under components:. Each entry selects a type — an intuitive name or its historical code (both work, see Available components) — and where to mount it:

components:
  - type: rplidar_s3        # intuitive name
    parent_link: cover_link
    xyz: 0.0 0.0 0.2
    rpy: 0.0 0.0 0.0

  - type: CAM06             # or the historical code (here: zed_x)
    name: front
    parent_link: camera_mount_link
    xyz: -0.01 0.0 0.02
    rpy: 0.0 0.0 0.0

  - type: RCK
    name: rack
    parent_link: mount_link
    xyz: 0.0 0.0 0.0
    rpy: 0.0 0.0 0.0
    elements:
      - length: 0.42
        xyz: 0.185 0.0 0.21
        rpy: 0.0 0.0 1.5708
      - length: 0.2
        xyz: 0.185 0.2 0.1
        rpy: 0.0 1.5708 0.0
      - length: 0.2
        xyz: 0.185 -0.2 0.1
        rpy: 0.0 1.5708 0.0

Config schema

Some types accept extra fields (e.g. RCK takes elements, custom takes package/file).

Available components

Put the Name in type: (recommended) or the Code — both resolve to the same component. Some devices have no code (e.g. rplidar_c1) and are selected by name only. A few short aliases also work: astra, realsense, oak, wibotic.

Frames & mounts

Cameras

File truncated at 100 lines see the full file

Changelog for package husarion_components_description

0.1.1 (2026-06-29)

• Add readable component-type names
• Add LPX-E3/T1, Velodyne & Astra meshes; improve RPLidar meshes (#23)
• rack example (#22)
• Add all rplidar mesh models
• Add custom component type for user URDF/mesh (#21)
• Use upstream zed_description for ZED camera URDF (#20)
• Rails elements (#17)
• Fix os0-32 ranges (#16)
• Add reling component (#15)
• Contributors: Dawid Kmak, Jakub Delicat, Rafal Gorecki, rafal-gorecki

0.1.0 (2025-12-12)

• Add tf_prefix arg and fix depthai reference frame for camera (#14)
• Add meshes (#13)
  • Add Ouster mesh
  • Add wibotic meshes and fixes
  • Make wibotic station more universal (change root_link, edit height of elements)
  • apriltag_height -> apriltag_mount_height
• Fixed teltonika antenna link (#12)
• Replace / with _ in bridge node name ([#11 <https://github.com/husarion/husarion_components_description/issues/11>]{.title-ref}
• Big clean up + frame standarization (#9)
• Fix default device_name
• Add missing lidar
• Fix ouster visual (#6)
• Contributors: Dawid Kmak, Jakub Delicat, Rafal Gorecki, husarafal

0.0.2 (2025-08-06)

• Fix stereolabs zed origin (#7)
• Zed add CAM05 and update ZED urdf (#5)
• fix rplidar visual (#4)
• Add visuals (#2)
• Move code from ros_components_description (#1)
• Initial commit
• Contributors: Dawid Kmak, Dominik Nowak, Rafal Gorecki