yahboom
HomeLearn
Solution
Blog
Online Store
About Us
EN/中文
SLAM LiDAR📖
01.Version differences
  • 1.About SLAM Lidar
02.SLAM Lidar (A1, A2, S1, S2, S3, C1)
  • 1.How to use lidar
03.Linux basic course
  • 1.Introduction to Linux system
  • 2.Ubuntu file system
  • 3.Ubuntu common commands
  • 4.Ubuntu common editors
  • 5.Ubuntu software operation commands
  • 6.Virtual machine installation
  • 7.SSH remote control
  • 8.VNC remote control
  • 9.Transfer files remotely
  • 10.Driver library and communication
  • 11.Static IP and hotspot mode
  • 12.Bind device ID
  • 13.Capacity expansion and resource allocation
  • 14.Update system software sources
  • 15.Set root user password
  • 16.sudo free password
  • 17.Connect to WiFi network
  • 18.View system version
  • 19.Customized service management
  • 20.Back up system image
04.ROS1 basic course
  • 1.ROS introduction
  • 2.ROS installation
  • 3.ROS common command tools
  • 4.ROS workspace
  • 5.ROS function package
  • 6.ROS node
  • 7.ROS topic publisher
  • 8.ROS topic subscribers
  • 9.ROS service client
  • 10.ROS service server
  • 11.ROS action client
  • 12.ROS action server
  • 13.ROS custom message reception
  • 14.ROS-launch file
  • 15.ROS-TF transformation
  • 16.ROS parameter service
  • 17.ROS-rviz use
  • 18.ROS-rqt tool usage
  • 19.Topic message recording and playback
  • 20.urdf model introduction
  • 21.gazebo introduction
  • 22.ROS distributed communication
05.ROS1 lidar course
  • 0.ReadMe
  • 1.Preparation
  • 2.Handheld lidar mapping
  • 3.Lidar avoiding
  • 4.Lidar guard
  • 5.Lidar follow
  • 6.Lidar mapping
  • 7.rrt_exploration mapping algorithm
  • 8.Navigation and avoiding
  • 9.APP Mapping and Navigation
  • 10.RTAB 3D mapping and navigation
06.ROS2 basic course
  • 1.Introduction to ROS2
  • 2.ROS2 install Humble
  • 3.ROS2 development environment
  • 4.ROS2 workspace
  • 5.ROS2 function package
  • 6.ROS2 node
  • 7.ROS2 topic communication
  • 8.ROS2 service communication
  • 9.ROS2 action communication
  • 10.ROS2 custom interface message
  • 11.ROS2 parameter service case
  • 12.ROS2 meta-function package
  • 13.ROS2 distributed communication
  • 14.ROS2 DDS
  • 15.ROS2 time related API
  • 16.ROS2 common command tools
  • 17.ROS2 rviz2 use
  • 18.ROS2 rqt toolbox
  • 19.ROS2 Launch startup file configuration
  • 20.ROS2 recording and playback tool
  • 21.ROS2 URDF model
  • 22.ROS2 Gazebo simulation platform
  • 23.ROS2 TF2 coordinate transformation
07.ROS2 lidar course
  • 0.ReadMe
  • 1.Preparation
  • 2.Handheld lidar mapping
  • 3.Lidar avoiding
  • 4.Lidar follow
  • 5.Lidar guard
  • 6.gmapping mapping
  • 7.cartographer mapping
  • 8.Navigation and avoiding
  • 9.APP Mapping and Navigation
  • 10.RTAB 3D mapping and navigation
  • 11.Lidar patrol
08.Mapper M2 lidar course
  • 1.How to use M2M2lidar
09.High-speed version A1 lidar usage tutorial
  • 1.Preparation before using the high-speed version of A1 lidar
10.RaspberryPi5 Docker course
  • 1.Overview and installation
  • 2.Common commands
  • 3.Understand and publish images
  • 4.Hardware interaction data processing
  • 5.Enter docker container
  • 6.Update docker images
  • 7.Docker container to install ROS using accessories
Download
  • Code
  • VM File
  • Data Sheet
  • Just for Mapper M2 Lidar
  • Model File
  • PC_Software
  • ROS2_Basic_VM
Download ZIP

Welcome to SLAM LiDAR repository

20.urdf model introduction

20.urdf model introduction

URDF is the robot description format in ROS. Its full name is Unified Robot Description Format, which describes the robot's appearance, physical attributes, joint types, etc. URDF files are written in XML language. Let's first understand the commonly used XML tags in URDF files.

20.1 tag

20.1.1 Introduction

In the URDF descriptive language, links are used to describe physical properties. It can be detailed as a human arm, which represents a whole body and has the following tags:

  • tag: describes the visual display, including size\color\shape.
  • tag: describes collision properties.
  • tag: describes physical inertia.

Each link will be regarded as a coordinate system. The usage example is as follows:

<link name="link1"> 
    <visual> 
        <origin xyz="0 0 0" rpy="0 0 0" />
        <geometry> 
            <mesh filename="package://dofbot_moveit/meshes/link1.STL" /> 
        </geometry> 
        <material name=""> 
            <color rgba="0 0.627450980392157 0.235294117647059 1" /> 
        </material> 
    </visual> 
    <collision> 
        <origin xyz="0 0 0" rpy="0 0 0" /> 
        <geometry> 
            <mesh filename="package://dofbot_moveit/meshes/link1.STL" /> 
        </geometry> 
    </collision> 
</link>

The name attribute in the tag is required, describes the current link name, and is unique. In the sample code you can see the following sets of tags:

  • The tag describes the pose information; the xyz attribute describes the coordinate position in the general environment, and the rpy attribute describes its own posture.

  • The tag describes the shape; the main function of the mesh attribute is to load the texture file, and the filename attribute is the file address of the texture path. The tag also includes other tag descriptions:

    • box describes the length, width and height of the box through the size attribute.
    • cylinder is cylindrical . The length attribute describes the height of the cylinder, and the radius attribute describes the radius of the cylinder.
    • sphere spherical , describing the radius of the sphere through the radius attribute.
  • The tag describes the material; the name attribute is required, can be empty, and can be repeated. Red, green, blue, and transparency are described through the rgba attribute in the tag, separated by spaces. The color range is [0-1].

20.2 tag

20.2.1 Introduction

Describe the relationship between two joints. Movement position and speed limits. Kinematic and dynamic properties. It can be imagined as the joints of the human body, which include the following types:

  • fixed: fixed joint. No movement is allowed and it serves as a connection.
  • continuous: rotating joint. Can continue to rotate, there is no limit on the rotation angle.
  • revolute: rotate joint. Similar to continuous, there is a limit to the rotation angle.
  • prismatic: sliding joint. Move along a certain axis, with position restrictions.
  • floating: floating joint.
  • planar: plane joint.

A pair of tags also have the following sub-tags:

  • and represent two s to be connected, corresponding to the name attribute in ; use as a reference here, and rotates around .
  • refers to the relative position of the rotating joint to the coordinate system where the parent is located.
  • indicates which axis the corresponding rotates around.
  • mainly limits . The lower attribute and upper attribute limit the arc range of rotation, and the effort attribute limits the force range during rotation. (positive or negative value value, unit is Newton or N), velocity attribute limits the speed during rotation, unit is meter/second or m/s.

Sample code is as follows,

xxxxxxxxxx
<joint name="joint1" type="revolute"> 
    <origin xyz="0 0 0.06605" rpy="-0.010805 0 0" /> 
    <parent link="base_link" /> 
    <child link="link1" /> 
    <axis xyz="0 0 1" /> 
    <limit effort="30" velocity="1.0" lower="-1.5708" upper="1.5708"/> 
</joint>

20.3 tag

The tag is the top tag of the complete robot model. It is placed at the head and tail ends. It contains and . The name of the robot can be set in the tag. The usage is as follows:

xxxxxxxxxx
<robot name="robot_name">
    <link>
        ...
    </link>
    <joint>
        ...
    </joint>
    
    <link>
        ...
    </link>
    <joint>
        ...
    </joint>
<robot>

20.4 Create urdf function package

Generally, urdf files will be placed independently in a function package. Create the learn_urdf function package under src of the original workspace and enter it in the terminal.

xxxxxxxxxx
cd ~/ros_ws/src
catkin_create_pkg learn_urdf urdf xacro

Then return to the workspace, compile,

xxxxxxxxxx
cd ~/ros_ws
catkin_make

After compilation is completed, four new folders need to be created in the directory of the function package, namely:

  • urdf: used to store written urdf model files
  • meshes: used to store rendering files for links in URDF
  • launch: used to store the launch file that starts the display urdf
  • config: rviz file used to store the urdf model

20.5 Write launch to start urdf

In the launch folder under the learn_urdf function package, create a new file named display.launch and copy the following content into it,

​x
<launch>

    <param name="robot_description" command="$(find xacro)/xacro --inorder $(find learn_urdf)/urdf/dofbot.urdf" />

    <node name="joint_state_publisher_gui" pkg="joint_state_publisher_gui" type="joint_state_publisher_gui"/>
    
    <node name="robot_state_publisher" pkg="robot_state_publisher" type="robot_state_publisher" />
    
</launch>

Exit after saving and reopen the terminal for input.

xxxxxxxxxx
roslaunch learn_urdf display.launch

image-20231027104402651

The GUI interface on the right can control the movement of the robotic arm through the slider. Now open rviz to display the robot arm, terminal input,

xxxxxxxxxx
rviz

image-20231027104631306

As shown in the picture above, set [Fixed Frame] to base_link, then click [Add], select [By display type], select [RobotModel], and finally click [OK].

image-20231027104857854

Parse launch files,

xxxxxxxxxx
<param name="robot_description" command="$(find xacro)/xacro --inorder $(find learn_urdf)/urdf/dofbot.urdf" />

Set the urdf model to be loaded.

xxxxxxxxxx
<node name="joint_state_publisher_gui" pkg="joint_state_publisher_gui" type="joint_state_publisher_gui"/>

Run the joint_state_publisher node to publish the joint status of the robot, and the joint can be controlled through the UI interface.

xxxxxxxxxx
<node name="robot_state_publisher" pkg="robot_state_publisher" type="robot_state_publisher" />

Run the robot_state_publisher node, publish tf, and organize it into three-dimensional attitude information for publication.

Topic message recording and playback
gazebo introduction

COMPANY

  • About us
  • Team Style
  • Blog

LEARNING & EXPLORATION

  • Tutorials
  • Edge AI hardware
  • Educational robots
  • Embedded intelligent hardware

WHERE TO BUY

  • Yahboom Online Store
  • Amazon
  • Alibaba
  • AliExpress
  • Mercado

TECHNOLOGY SUPPORT

  • Email: support@yahboom.com

BE A DISTRIBUTOR

  • Email: sales@yahboom.com
QR Code

Copyright © 2017-2026 Yahboom. All Rights Reserved.

EN/中文