![]() |
rm_driver package from ros2_rm_robot repocontrol_arm_move force_position_control get_arm_state rm_bringup rm_control rm_description rm_doc rm_driver rm_example rm_gazebo rm_install rm_63_config rm_65_config rm_75_config rm_eco63_config rm_eco65_config rm_gen72_config rm_ros_interfaces |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.0.0 |
License | TODO: License declaration |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | ROS2 was developed for the Realman robot (http://www.realman-robotics.com/). |
Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-06-09 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- xtark
Authors
Content
- 1.rm_driver package description
- 2.rm_driver package use
- 2.1 Basic use of the package
- 2.2 Advanced use of the package
- 3.rm_driver package architecture description
- 3.1 Overview of Package Files
- 4.rm_driver topic description
1. rm_driver package description
rm_driver package is very important in the ROS2 robotic arm package. This package realizes the function of controlling the robotic arm through communication between ROS and the robotic arm. The package will be introduced in detail in the following text through the following aspects:
- 1.Package use.
- 2.Package architecture description.
- 3.Package topic description.
Through the introduction of the three parts, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
- 3.Familiar with the topic related to the package for easy development and use.
Source code address:https://github.com/RealManRobot/ros2_rm_robot.git.
2. rm_driver package use
2.1 Basic use of the package
First, after configuring the environment and completing the connection, we can directly start the node and control the robotic arm through the following command. The current control is based on the fact that we have not changed the IP of the robotic arm, which is still 192.168.1.18. rm@rm-desktop:~$ ros2 launch rm_driver rm_
_driver.launch.py In practice, the above needs to be replaced by the actual model of the robotic arm. The available models of the robotic arm are 65, 63, eco65、eco63, gen72 and 75. The following screen will appear if the underlying driver is successfully started.  2.2 Advanced use of the package
When our robotic arm’s IP is changed, our start command is invalid. If we use the above command directly, we cannot successfully connect to the robotic arm. We can re-establish the connection by modifying the following configuration file. The configuration file is located in the config folder under our rm_driver package.
The contents of the configuration file are as follows:
rm_driver:
ros__parameters:
#robot param
arm_ip: "192.168.1.18" # Set the IP address for the TCP connection
tcp_port: 8080# # Set the port for the TCP connection
arm_type: "RM_65" # set the robotic arm model
arm_dof: 6 # Set the degree of freedom of the robotic arm
udp_ip: "192.168.1.10" # set the udp active reporting IP address
udp_cycle: 5 # the active reporting cycle of UDP, which needs to be a multiple of 5.
udp_port: 8089 # Set the udp active reporting port
udp_force_coordinate: 0 # Set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system, 1 is the current work coordinate system, and 2 is the current tool coordinate system
udp_hand: false # Set the udp hand reporting enable
udp_plus_base: false # Set the udp plus base reporting enable
udp_plus_state: false # Set the udp plus state reporting enable
trajectory_mode: 0 #When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
radio: 0 #Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
arm_joints: ["joint1", "joint2", "joint3", "joint4", "joint5", "joint6"]
There are mainly the following parameters.
- arm_ip: This parameter represents the current IP of the robotic arm
- tcp_port: set the port when TCP is connected.
- arm_type: This parameter represents the current model of the robotic arm. The parameters that can be selected are RM_65 (65 series), RM_eco65 (ECO65 series), RM_eco63 (ECO63 series), RM_63 (63 series),GEN_72 (GEN72 series) and RM_75 (75 series).
- arm_dof: set the degree of freedom of the robotic arm. 6 is 6 degrees of freedom, and 7 is 7 degrees of freedom.
- udp_ip: set the udp active reporting IP address.
- udp_cycle: the active reporting cycle of UDP, which needs to be a multiple of 5.
- udp_port: set the udp active reporting port.
- udp_force_coordinate: set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system (original data), 1 is the current work coordinate system, and 2 is the current tool coordinate system.
- trajectory_mode:When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
- radio:Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
- In practice, we choose the corresponding launch file to start, which will automatically select the correct model. If there are special requirements, you can modify the corresponding parameters here. After modification, recompile the configuration in the workspace directory, and then the modified configuration will take effect. Run the colcon build command in the workspace directory.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
![]() |
rm_driver package from ros2_rm_robot repocontrol_arm_move force_position_control get_arm_state rm_bringup rm_control rm_description rm_doc rm_driver rm_example rm_gazebo rm_install rm_63_config rm_65_config rm_75_config rm_eco63_config rm_eco65_config rm_gen72_config rm_ros_interfaces |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.0.0 |
License | TODO: License declaration |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | ROS2 was developed for the Realman robot (http://www.realman-robotics.com/). |
Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-06-09 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- xtark
Authors
Content
- 1.rm_driver package description
- 2.rm_driver package use
- 2.1 Basic use of the package
- 2.2 Advanced use of the package
- 3.rm_driver package architecture description
- 3.1 Overview of Package Files
- 4.rm_driver topic description
1. rm_driver package description
rm_driver package is very important in the ROS2 robotic arm package. This package realizes the function of controlling the robotic arm through communication between ROS and the robotic arm. The package will be introduced in detail in the following text through the following aspects:
- 1.Package use.
- 2.Package architecture description.
- 3.Package topic description.
Through the introduction of the three parts, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
- 3.Familiar with the topic related to the package for easy development and use.
Source code address:https://github.com/RealManRobot/ros2_rm_robot.git.
2. rm_driver package use
2.1 Basic use of the package
First, after configuring the environment and completing the connection, we can directly start the node and control the robotic arm through the following command. The current control is based on the fact that we have not changed the IP of the robotic arm, which is still 192.168.1.18. rm@rm-desktop:~$ ros2 launch rm_driver rm_
_driver.launch.py In practice, the above needs to be replaced by the actual model of the robotic arm. The available models of the robotic arm are 65, 63, eco65、eco63, gen72 and 75. The following screen will appear if the underlying driver is successfully started.  2.2 Advanced use of the package
When our robotic arm’s IP is changed, our start command is invalid. If we use the above command directly, we cannot successfully connect to the robotic arm. We can re-establish the connection by modifying the following configuration file. The configuration file is located in the config folder under our rm_driver package.
The contents of the configuration file are as follows:
rm_driver:
ros__parameters:
#robot param
arm_ip: "192.168.1.18" # Set the IP address for the TCP connection
tcp_port: 8080# # Set the port for the TCP connection
arm_type: "RM_65" # set the robotic arm model
arm_dof: 6 # Set the degree of freedom of the robotic arm
udp_ip: "192.168.1.10" # set the udp active reporting IP address
udp_cycle: 5 # the active reporting cycle of UDP, which needs to be a multiple of 5.
udp_port: 8089 # Set the udp active reporting port
udp_force_coordinate: 0 # Set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system, 1 is the current work coordinate system, and 2 is the current tool coordinate system
udp_hand: false # Set the udp hand reporting enable
udp_plus_base: false # Set the udp plus base reporting enable
udp_plus_state: false # Set the udp plus state reporting enable
trajectory_mode: 0 #When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
radio: 0 #Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
arm_joints: ["joint1", "joint2", "joint3", "joint4", "joint5", "joint6"]
There are mainly the following parameters.
- arm_ip: This parameter represents the current IP of the robotic arm
- tcp_port: set the port when TCP is connected.
- arm_type: This parameter represents the current model of the robotic arm. The parameters that can be selected are RM_65 (65 series), RM_eco65 (ECO65 series), RM_eco63 (ECO63 series), RM_63 (63 series),GEN_72 (GEN72 series) and RM_75 (75 series).
- arm_dof: set the degree of freedom of the robotic arm. 6 is 6 degrees of freedom, and 7 is 7 degrees of freedom.
- udp_ip: set the udp active reporting IP address.
- udp_cycle: the active reporting cycle of UDP, which needs to be a multiple of 5.
- udp_port: set the udp active reporting port.
- udp_force_coordinate: set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system (original data), 1 is the current work coordinate system, and 2 is the current tool coordinate system.
- trajectory_mode:When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
- radio:Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
- In practice, we choose the corresponding launch file to start, which will automatically select the correct model. If there are special requirements, you can modify the corresponding parameters here. After modification, recompile the configuration in the workspace directory, and then the modified configuration will take effect. Run the colcon build command in the workspace directory.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
![]() |
rm_driver package from ros2_rm_robot repocontrol_arm_move force_position_control get_arm_state rm_bringup rm_control rm_description rm_doc rm_driver rm_example rm_gazebo rm_install rm_63_config rm_65_config rm_75_config rm_eco63_config rm_eco65_config rm_gen72_config rm_ros_interfaces |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.0.0 |
License | TODO: License declaration |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | ROS2 was developed for the Realman robot (http://www.realman-robotics.com/). |
Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-06-09 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- xtark
Authors
Content
- 1.rm_driver package description
- 2.rm_driver package use
- 2.1 Basic use of the package
- 2.2 Advanced use of the package
- 3.rm_driver package architecture description
- 3.1 Overview of Package Files
- 4.rm_driver topic description
1. rm_driver package description
rm_driver package is very important in the ROS2 robotic arm package. This package realizes the function of controlling the robotic arm through communication between ROS and the robotic arm. The package will be introduced in detail in the following text through the following aspects:
- 1.Package use.
- 2.Package architecture description.
- 3.Package topic description.
Through the introduction of the three parts, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
- 3.Familiar with the topic related to the package for easy development and use.
Source code address:https://github.com/RealManRobot/ros2_rm_robot.git.
2. rm_driver package use
2.1 Basic use of the package
First, after configuring the environment and completing the connection, we can directly start the node and control the robotic arm through the following command. The current control is based on the fact that we have not changed the IP of the robotic arm, which is still 192.168.1.18. rm@rm-desktop:~$ ros2 launch rm_driver rm_
_driver.launch.py In practice, the above needs to be replaced by the actual model of the robotic arm. The available models of the robotic arm are 65, 63, eco65、eco63, gen72 and 75. The following screen will appear if the underlying driver is successfully started.  2.2 Advanced use of the package
When our robotic arm’s IP is changed, our start command is invalid. If we use the above command directly, we cannot successfully connect to the robotic arm. We can re-establish the connection by modifying the following configuration file. The configuration file is located in the config folder under our rm_driver package.
The contents of the configuration file are as follows:
rm_driver:
ros__parameters:
#robot param
arm_ip: "192.168.1.18" # Set the IP address for the TCP connection
tcp_port: 8080# # Set the port for the TCP connection
arm_type: "RM_65" # set the robotic arm model
arm_dof: 6 # Set the degree of freedom of the robotic arm
udp_ip: "192.168.1.10" # set the udp active reporting IP address
udp_cycle: 5 # the active reporting cycle of UDP, which needs to be a multiple of 5.
udp_port: 8089 # Set the udp active reporting port
udp_force_coordinate: 0 # Set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system, 1 is the current work coordinate system, and 2 is the current tool coordinate system
udp_hand: false # Set the udp hand reporting enable
udp_plus_base: false # Set the udp plus base reporting enable
udp_plus_state: false # Set the udp plus state reporting enable
trajectory_mode: 0 #When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
radio: 0 #Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
arm_joints: ["joint1", "joint2", "joint3", "joint4", "joint5", "joint6"]
There are mainly the following parameters.
- arm_ip: This parameter represents the current IP of the robotic arm
- tcp_port: set the port when TCP is connected.
- arm_type: This parameter represents the current model of the robotic arm. The parameters that can be selected are RM_65 (65 series), RM_eco65 (ECO65 series), RM_eco63 (ECO63 series), RM_63 (63 series),GEN_72 (GEN72 series) and RM_75 (75 series).
- arm_dof: set the degree of freedom of the robotic arm. 6 is 6 degrees of freedom, and 7 is 7 degrees of freedom.
- udp_ip: set the udp active reporting IP address.
- udp_cycle: the active reporting cycle of UDP, which needs to be a multiple of 5.
- udp_port: set the udp active reporting port.
- udp_force_coordinate: set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system (original data), 1 is the current work coordinate system, and 2 is the current tool coordinate system.
- trajectory_mode:When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
- radio:Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
- In practice, we choose the corresponding launch file to start, which will automatically select the correct model. If there are special requirements, you can modify the corresponding parameters here. After modification, recompile the configuration in the workspace directory, and then the modified configuration will take effect. Run the colcon build command in the workspace directory.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
![]() |
rm_driver package from ros2_rm_robot repocontrol_arm_move force_position_control get_arm_state rm_bringup rm_control rm_description rm_doc rm_driver rm_example rm_gazebo rm_install rm_63_config rm_65_config rm_75_config rm_eco63_config rm_eco65_config rm_gen72_config rm_ros_interfaces |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.0.0 |
License | TODO: License declaration |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | ROS2 was developed for the Realman robot (http://www.realman-robotics.com/). |
Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-06-09 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- xtark
Authors
Content
- 1.rm_driver package description
- 2.rm_driver package use
- 2.1 Basic use of the package
- 2.2 Advanced use of the package
- 3.rm_driver package architecture description
- 3.1 Overview of Package Files
- 4.rm_driver topic description
1. rm_driver package description
rm_driver package is very important in the ROS2 robotic arm package. This package realizes the function of controlling the robotic arm through communication between ROS and the robotic arm. The package will be introduced in detail in the following text through the following aspects:
- 1.Package use.
- 2.Package architecture description.
- 3.Package topic description.
Through the introduction of the three parts, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
- 3.Familiar with the topic related to the package for easy development and use.
Source code address:https://github.com/RealManRobot/ros2_rm_robot.git.
2. rm_driver package use
2.1 Basic use of the package
First, after configuring the environment and completing the connection, we can directly start the node and control the robotic arm through the following command. The current control is based on the fact that we have not changed the IP of the robotic arm, which is still 192.168.1.18. rm@rm-desktop:~$ ros2 launch rm_driver rm_
_driver.launch.py In practice, the above needs to be replaced by the actual model of the robotic arm. The available models of the robotic arm are 65, 63, eco65、eco63, gen72 and 75. The following screen will appear if the underlying driver is successfully started.  2.2 Advanced use of the package
When our robotic arm’s IP is changed, our start command is invalid. If we use the above command directly, we cannot successfully connect to the robotic arm. We can re-establish the connection by modifying the following configuration file. The configuration file is located in the config folder under our rm_driver package.
The contents of the configuration file are as follows:
rm_driver:
ros__parameters:
#robot param
arm_ip: "192.168.1.18" # Set the IP address for the TCP connection
tcp_port: 8080# # Set the port for the TCP connection
arm_type: "RM_65" # set the robotic arm model
arm_dof: 6 # Set the degree of freedom of the robotic arm
udp_ip: "192.168.1.10" # set the udp active reporting IP address
udp_cycle: 5 # the active reporting cycle of UDP, which needs to be a multiple of 5.
udp_port: 8089 # Set the udp active reporting port
udp_force_coordinate: 0 # Set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system, 1 is the current work coordinate system, and 2 is the current tool coordinate system
udp_hand: false # Set the udp hand reporting enable
udp_plus_base: false # Set the udp plus base reporting enable
udp_plus_state: false # Set the udp plus state reporting enable
trajectory_mode: 0 #When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
radio: 0 #Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
arm_joints: ["joint1", "joint2", "joint3", "joint4", "joint5", "joint6"]
There are mainly the following parameters.
- arm_ip: This parameter represents the current IP of the robotic arm
- tcp_port: set the port when TCP is connected.
- arm_type: This parameter represents the current model of the robotic arm. The parameters that can be selected are RM_65 (65 series), RM_eco65 (ECO65 series), RM_eco63 (ECO63 series), RM_63 (63 series),GEN_72 (GEN72 series) and RM_75 (75 series).
- arm_dof: set the degree of freedom of the robotic arm. 6 is 6 degrees of freedom, and 7 is 7 degrees of freedom.
- udp_ip: set the udp active reporting IP address.
- udp_cycle: the active reporting cycle of UDP, which needs to be a multiple of 5.
- udp_port: set the udp active reporting port.
- udp_force_coordinate: set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system (original data), 1 is the current work coordinate system, and 2 is the current tool coordinate system.
- trajectory_mode:When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
- radio:Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
- In practice, we choose the corresponding launch file to start, which will automatically select the correct model. If there are special requirements, you can modify the corresponding parameters here. After modification, recompile the configuration in the workspace directory, and then the modified configuration will take effect. Run the colcon build command in the workspace directory.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
![]() |
rm_driver package from ros2_rm_robot repocontrol_arm_move force_position_control get_arm_state rm_bringup rm_control rm_description rm_doc rm_driver rm_example rm_gazebo rm_install rm_63_config rm_65_config rm_75_config rm_eco63_config rm_eco65_config rm_gen72_config rm_ros_interfaces |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.0.0 |
License | TODO: License declaration |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | ROS2 was developed for the Realman robot (http://www.realman-robotics.com/). |
Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-06-09 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- xtark
Authors
Content
- 1.rm_driver package description
- 2.rm_driver package use
- 2.1 Basic use of the package
- 2.2 Advanced use of the package
- 3.rm_driver package architecture description
- 3.1 Overview of Package Files
- 4.rm_driver topic description
1. rm_driver package description
rm_driver package is very important in the ROS2 robotic arm package. This package realizes the function of controlling the robotic arm through communication between ROS and the robotic arm. The package will be introduced in detail in the following text through the following aspects:
- 1.Package use.
- 2.Package architecture description.
- 3.Package topic description.
Through the introduction of the three parts, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
- 3.Familiar with the topic related to the package for easy development and use.
Source code address:https://github.com/RealManRobot/ros2_rm_robot.git.
2. rm_driver package use
2.1 Basic use of the package
First, after configuring the environment and completing the connection, we can directly start the node and control the robotic arm through the following command. The current control is based on the fact that we have not changed the IP of the robotic arm, which is still 192.168.1.18. rm@rm-desktop:~$ ros2 launch rm_driver rm_
_driver.launch.py In practice, the above needs to be replaced by the actual model of the robotic arm. The available models of the robotic arm are 65, 63, eco65、eco63, gen72 and 75. The following screen will appear if the underlying driver is successfully started.  2.2 Advanced use of the package
When our robotic arm’s IP is changed, our start command is invalid. If we use the above command directly, we cannot successfully connect to the robotic arm. We can re-establish the connection by modifying the following configuration file. The configuration file is located in the config folder under our rm_driver package.
The contents of the configuration file are as follows:
rm_driver:
ros__parameters:
#robot param
arm_ip: "192.168.1.18" # Set the IP address for the TCP connection
tcp_port: 8080# # Set the port for the TCP connection
arm_type: "RM_65" # set the robotic arm model
arm_dof: 6 # Set the degree of freedom of the robotic arm
udp_ip: "192.168.1.10" # set the udp active reporting IP address
udp_cycle: 5 # the active reporting cycle of UDP, which needs to be a multiple of 5.
udp_port: 8089 # Set the udp active reporting port
udp_force_coordinate: 0 # Set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system, 1 is the current work coordinate system, and 2 is the current tool coordinate system
udp_hand: false # Set the udp hand reporting enable
udp_plus_base: false # Set the udp plus base reporting enable
udp_plus_state: false # Set the udp plus state reporting enable
trajectory_mode: 0 #When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
radio: 0 #Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
arm_joints: ["joint1", "joint2", "joint3", "joint4", "joint5", "joint6"]
There are mainly the following parameters.
- arm_ip: This parameter represents the current IP of the robotic arm
- tcp_port: set the port when TCP is connected.
- arm_type: This parameter represents the current model of the robotic arm. The parameters that can be selected are RM_65 (65 series), RM_eco65 (ECO65 series), RM_eco63 (ECO63 series), RM_63 (63 series),GEN_72 (GEN72 series) and RM_75 (75 series).
- arm_dof: set the degree of freedom of the robotic arm. 6 is 6 degrees of freedom, and 7 is 7 degrees of freedom.
- udp_ip: set the udp active reporting IP address.
- udp_cycle: the active reporting cycle of UDP, which needs to be a multiple of 5.
- udp_port: set the udp active reporting port.
- udp_force_coordinate: set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system (original data), 1 is the current work coordinate system, and 2 is the current tool coordinate system.
- trajectory_mode:When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
- radio:Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
- In practice, we choose the corresponding launch file to start, which will automatically select the correct model. If there are special requirements, you can modify the corresponding parameters here. After modification, recompile the configuration in the workspace directory, and then the modified configuration will take effect. Run the colcon build command in the workspace directory.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
![]() |
rm_driver package from ros2_rm_robot repocontrol_arm_move force_position_control get_arm_state rm_bringup rm_control rm_description rm_doc rm_driver rm_example rm_gazebo rm_install rm_63_config rm_65_config rm_75_config rm_eco63_config rm_eco65_config rm_gen72_config rm_ros_interfaces |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.0.0 |
License | TODO: License declaration |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | ROS2 was developed for the Realman robot (http://www.realman-robotics.com/). |
Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-06-09 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- xtark
Authors
Content
- 1.rm_driver package description
- 2.rm_driver package use
- 2.1 Basic use of the package
- 2.2 Advanced use of the package
- 3.rm_driver package architecture description
- 3.1 Overview of Package Files
- 4.rm_driver topic description
1. rm_driver package description
rm_driver package is very important in the ROS2 robotic arm package. This package realizes the function of controlling the robotic arm through communication between ROS and the robotic arm. The package will be introduced in detail in the following text through the following aspects:
- 1.Package use.
- 2.Package architecture description.
- 3.Package topic description.
Through the introduction of the three parts, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
- 3.Familiar with the topic related to the package for easy development and use.
Source code address:https://github.com/RealManRobot/ros2_rm_robot.git.
2. rm_driver package use
2.1 Basic use of the package
First, after configuring the environment and completing the connection, we can directly start the node and control the robotic arm through the following command. The current control is based on the fact that we have not changed the IP of the robotic arm, which is still 192.168.1.18. rm@rm-desktop:~$ ros2 launch rm_driver rm_
_driver.launch.py In practice, the above needs to be replaced by the actual model of the robotic arm. The available models of the robotic arm are 65, 63, eco65、eco63, gen72 and 75. The following screen will appear if the underlying driver is successfully started.  2.2 Advanced use of the package
When our robotic arm’s IP is changed, our start command is invalid. If we use the above command directly, we cannot successfully connect to the robotic arm. We can re-establish the connection by modifying the following configuration file. The configuration file is located in the config folder under our rm_driver package.
The contents of the configuration file are as follows:
rm_driver:
ros__parameters:
#robot param
arm_ip: "192.168.1.18" # Set the IP address for the TCP connection
tcp_port: 8080# # Set the port for the TCP connection
arm_type: "RM_65" # set the robotic arm model
arm_dof: 6 # Set the degree of freedom of the robotic arm
udp_ip: "192.168.1.10" # set the udp active reporting IP address
udp_cycle: 5 # the active reporting cycle of UDP, which needs to be a multiple of 5.
udp_port: 8089 # Set the udp active reporting port
udp_force_coordinate: 0 # Set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system, 1 is the current work coordinate system, and 2 is the current tool coordinate system
udp_hand: false # Set the udp hand reporting enable
udp_plus_base: false # Set the udp plus base reporting enable
udp_plus_state: false # Set the udp plus state reporting enable
trajectory_mode: 0 #When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
radio: 0 #Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
arm_joints: ["joint1", "joint2", "joint3", "joint4", "joint5", "joint6"]
There are mainly the following parameters.
- arm_ip: This parameter represents the current IP of the robotic arm
- tcp_port: set the port when TCP is connected.
- arm_type: This parameter represents the current model of the robotic arm. The parameters that can be selected are RM_65 (65 series), RM_eco65 (ECO65 series), RM_eco63 (ECO63 series), RM_63 (63 series),GEN_72 (GEN72 series) and RM_75 (75 series).
- arm_dof: set the degree of freedom of the robotic arm. 6 is 6 degrees of freedom, and 7 is 7 degrees of freedom.
- udp_ip: set the udp active reporting IP address.
- udp_cycle: the active reporting cycle of UDP, which needs to be a multiple of 5.
- udp_port: set the udp active reporting port.
- udp_force_coordinate: set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system (original data), 1 is the current work coordinate system, and 2 is the current tool coordinate system.
- trajectory_mode:When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
- radio:Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
- In practice, we choose the corresponding launch file to start, which will automatically select the correct model. If there are special requirements, you can modify the corresponding parameters here. After modification, recompile the configuration in the workspace directory, and then the modified configuration will take effect. Run the colcon build command in the workspace directory.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
![]() |
rm_driver package from ros2_rm_robot repocontrol_arm_move force_position_control get_arm_state rm_bringup rm_control rm_description rm_doc rm_driver rm_example rm_gazebo rm_install rm_63_config rm_65_config rm_75_config rm_eco63_config rm_eco65_config rm_gen72_config rm_ros_interfaces |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.0.0 |
License | TODO: License declaration |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | ROS2 was developed for the Realman robot (http://www.realman-robotics.com/). |
Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-06-09 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- xtark
Authors
Content
- 1.rm_driver package description
- 2.rm_driver package use
- 2.1 Basic use of the package
- 2.2 Advanced use of the package
- 3.rm_driver package architecture description
- 3.1 Overview of Package Files
- 4.rm_driver topic description
1. rm_driver package description
rm_driver package is very important in the ROS2 robotic arm package. This package realizes the function of controlling the robotic arm through communication between ROS and the robotic arm. The package will be introduced in detail in the following text through the following aspects:
- 1.Package use.
- 2.Package architecture description.
- 3.Package topic description.
Through the introduction of the three parts, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
- 3.Familiar with the topic related to the package for easy development and use.
Source code address:https://github.com/RealManRobot/ros2_rm_robot.git.
2. rm_driver package use
2.1 Basic use of the package
First, after configuring the environment and completing the connection, we can directly start the node and control the robotic arm through the following command. The current control is based on the fact that we have not changed the IP of the robotic arm, which is still 192.168.1.18. rm@rm-desktop:~$ ros2 launch rm_driver rm_
_driver.launch.py In practice, the above needs to be replaced by the actual model of the robotic arm. The available models of the robotic arm are 65, 63, eco65、eco63, gen72 and 75. The following screen will appear if the underlying driver is successfully started.  2.2 Advanced use of the package
When our robotic arm’s IP is changed, our start command is invalid. If we use the above command directly, we cannot successfully connect to the robotic arm. We can re-establish the connection by modifying the following configuration file. The configuration file is located in the config folder under our rm_driver package.
The contents of the configuration file are as follows:
rm_driver:
ros__parameters:
#robot param
arm_ip: "192.168.1.18" # Set the IP address for the TCP connection
tcp_port: 8080# # Set the port for the TCP connection
arm_type: "RM_65" # set the robotic arm model
arm_dof: 6 # Set the degree of freedom of the robotic arm
udp_ip: "192.168.1.10" # set the udp active reporting IP address
udp_cycle: 5 # the active reporting cycle of UDP, which needs to be a multiple of 5.
udp_port: 8089 # Set the udp active reporting port
udp_force_coordinate: 0 # Set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system, 1 is the current work coordinate system, and 2 is the current tool coordinate system
udp_hand: false # Set the udp hand reporting enable
udp_plus_base: false # Set the udp plus base reporting enable
udp_plus_state: false # Set the udp plus state reporting enable
trajectory_mode: 0 #When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
radio: 0 #Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
arm_joints: ["joint1", "joint2", "joint3", "joint4", "joint5", "joint6"]
There are mainly the following parameters.
- arm_ip: This parameter represents the current IP of the robotic arm
- tcp_port: set the port when TCP is connected.
- arm_type: This parameter represents the current model of the robotic arm. The parameters that can be selected are RM_65 (65 series), RM_eco65 (ECO65 series), RM_eco63 (ECO63 series), RM_63 (63 series),GEN_72 (GEN72 series) and RM_75 (75 series).
- arm_dof: set the degree of freedom of the robotic arm. 6 is 6 degrees of freedom, and 7 is 7 degrees of freedom.
- udp_ip: set the udp active reporting IP address.
- udp_cycle: the active reporting cycle of UDP, which needs to be a multiple of 5.
- udp_port: set the udp active reporting port.
- udp_force_coordinate: set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system (original data), 1 is the current work coordinate system, and 2 is the current tool coordinate system.
- trajectory_mode:When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
- radio:Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
- In practice, we choose the corresponding launch file to start, which will automatically select the correct model. If there are special requirements, you can modify the corresponding parameters here. After modification, recompile the configuration in the workspace directory, and then the modified configuration will take effect. Run the colcon build command in the workspace directory.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
![]() |
rm_driver package from ros2_rm_robot repocontrol_arm_move force_position_control get_arm_state rm_bringup rm_control rm_description rm_doc rm_driver rm_example rm_gazebo rm_install rm_63_config rm_65_config rm_75_config rm_eco63_config rm_eco65_config rm_gen72_config rm_ros_interfaces |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.0.0 |
License | TODO: License declaration |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | ROS2 was developed for the Realman robot (http://www.realman-robotics.com/). |
Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-06-09 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- xtark
Authors
Content
- 1.rm_driver package description
- 2.rm_driver package use
- 2.1 Basic use of the package
- 2.2 Advanced use of the package
- 3.rm_driver package architecture description
- 3.1 Overview of Package Files
- 4.rm_driver topic description
1. rm_driver package description
rm_driver package is very important in the ROS2 robotic arm package. This package realizes the function of controlling the robotic arm through communication between ROS and the robotic arm. The package will be introduced in detail in the following text through the following aspects:
- 1.Package use.
- 2.Package architecture description.
- 3.Package topic description.
Through the introduction of the three parts, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
- 3.Familiar with the topic related to the package for easy development and use.
Source code address:https://github.com/RealManRobot/ros2_rm_robot.git.
2. rm_driver package use
2.1 Basic use of the package
First, after configuring the environment and completing the connection, we can directly start the node and control the robotic arm through the following command. The current control is based on the fact that we have not changed the IP of the robotic arm, which is still 192.168.1.18. rm@rm-desktop:~$ ros2 launch rm_driver rm_
_driver.launch.py In practice, the above needs to be replaced by the actual model of the robotic arm. The available models of the robotic arm are 65, 63, eco65、eco63, gen72 and 75. The following screen will appear if the underlying driver is successfully started.  2.2 Advanced use of the package
When our robotic arm’s IP is changed, our start command is invalid. If we use the above command directly, we cannot successfully connect to the robotic arm. We can re-establish the connection by modifying the following configuration file. The configuration file is located in the config folder under our rm_driver package.
The contents of the configuration file are as follows:
rm_driver:
ros__parameters:
#robot param
arm_ip: "192.168.1.18" # Set the IP address for the TCP connection
tcp_port: 8080# # Set the port for the TCP connection
arm_type: "RM_65" # set the robotic arm model
arm_dof: 6 # Set the degree of freedom of the robotic arm
udp_ip: "192.168.1.10" # set the udp active reporting IP address
udp_cycle: 5 # the active reporting cycle of UDP, which needs to be a multiple of 5.
udp_port: 8089 # Set the udp active reporting port
udp_force_coordinate: 0 # Set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system, 1 is the current work coordinate system, and 2 is the current tool coordinate system
udp_hand: false # Set the udp hand reporting enable
udp_plus_base: false # Set the udp plus base reporting enable
udp_plus_state: false # Set the udp plus state reporting enable
trajectory_mode: 0 #When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
radio: 0 #Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
arm_joints: ["joint1", "joint2", "joint3", "joint4", "joint5", "joint6"]
There are mainly the following parameters.
- arm_ip: This parameter represents the current IP of the robotic arm
- tcp_port: set the port when TCP is connected.
- arm_type: This parameter represents the current model of the robotic arm. The parameters that can be selected are RM_65 (65 series), RM_eco65 (ECO65 series), RM_eco63 (ECO63 series), RM_63 (63 series),GEN_72 (GEN72 series) and RM_75 (75 series).
- arm_dof: set the degree of freedom of the robotic arm. 6 is 6 degrees of freedom, and 7 is 7 degrees of freedom.
- udp_ip: set the udp active reporting IP address.
- udp_cycle: the active reporting cycle of UDP, which needs to be a multiple of 5.
- udp_port: set the udp active reporting port.
- udp_force_coordinate: set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system (original data), 1 is the current work coordinate system, and 2 is the current tool coordinate system.
- trajectory_mode:When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
- radio:Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
- In practice, we choose the corresponding launch file to start, which will automatically select the correct model. If there are special requirements, you can modify the corresponding parameters here. After modification, recompile the configuration in the workspace directory, and then the modified configuration will take effect. Run the colcon build command in the workspace directory.
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
![]() |
rm_driver package from ros2_rm_robot repocontrol_arm_move force_position_control get_arm_state rm_bringup rm_control rm_description rm_doc rm_driver rm_example rm_gazebo rm_install rm_63_config rm_65_config rm_75_config rm_eco63_config rm_eco65_config rm_gen72_config rm_ros_interfaces |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.0.0 |
License | TODO: License declaration |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | ROS2 was developed for the Realman robot (http://www.realman-robotics.com/). |
Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-06-09 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- xtark
Authors
Content
- 1.rm_driver package description
- 2.rm_driver package use
- 2.1 Basic use of the package
- 2.2 Advanced use of the package
- 3.rm_driver package architecture description
- 3.1 Overview of Package Files
- 4.rm_driver topic description
1. rm_driver package description
rm_driver package is very important in the ROS2 robotic arm package. This package realizes the function of controlling the robotic arm through communication between ROS and the robotic arm. The package will be introduced in detail in the following text through the following aspects:
- 1.Package use.
- 2.Package architecture description.
- 3.Package topic description.
Through the introduction of the three parts, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
- 3.Familiar with the topic related to the package for easy development and use.
Source code address:https://github.com/RealManRobot/ros2_rm_robot.git.
2. rm_driver package use
2.1 Basic use of the package
First, after configuring the environment and completing the connection, we can directly start the node and control the robotic arm through the following command. The current control is based on the fact that we have not changed the IP of the robotic arm, which is still 192.168.1.18. rm@rm-desktop:~$ ros2 launch rm_driver rm_
_driver.launch.py In practice, the above needs to be replaced by the actual model of the robotic arm. The available models of the robotic arm are 65, 63, eco65、eco63, gen72 and 75. The following screen will appear if the underlying driver is successfully started.  2.2 Advanced use of the package
When our robotic arm’s IP is changed, our start command is invalid. If we use the above command directly, we cannot successfully connect to the robotic arm. We can re-establish the connection by modifying the following configuration file. The configuration file is located in the config folder under our rm_driver package.
The contents of the configuration file are as follows:
rm_driver:
ros__parameters:
#robot param
arm_ip: "192.168.1.18" # Set the IP address for the TCP connection
tcp_port: 8080# # Set the port for the TCP connection
arm_type: "RM_65" # set the robotic arm model
arm_dof: 6 # Set the degree of freedom of the robotic arm
udp_ip: "192.168.1.10" # set the udp active reporting IP address
udp_cycle: 5 # the active reporting cycle of UDP, which needs to be a multiple of 5.
udp_port: 8089 # Set the udp active reporting port
udp_force_coordinate: 0 # Set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system, 1 is the current work coordinate system, and 2 is the current tool coordinate system
udp_hand: false # Set the udp hand reporting enable
udp_plus_base: false # Set the udp plus base reporting enable
udp_plus_state: false # Set the udp plus state reporting enable
trajectory_mode: 0 #When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
radio: 0 #Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
arm_joints: ["joint1", "joint2", "joint3", "joint4", "joint5", "joint6"]
There are mainly the following parameters.
- arm_ip: This parameter represents the current IP of the robotic arm
- tcp_port: set the port when TCP is connected.
- arm_type: This parameter represents the current model of the robotic arm. The parameters that can be selected are RM_65 (65 series), RM_eco65 (ECO65 series), RM_eco63 (ECO63 series), RM_63 (63 series),GEN_72 (GEN72 series) and RM_75 (75 series).
- arm_dof: set the degree of freedom of the robotic arm. 6 is 6 degrees of freedom, and 7 is 7 degrees of freedom.
- udp_ip: set the udp active reporting IP address.
- udp_cycle: the active reporting cycle of UDP, which needs to be a multiple of 5.
- udp_port: set the udp active reporting port.
- udp_force_coordinate: set the base coordinate of the six-axis force when the system is forced, where 0 is the sensor coordinate system (original data), 1 is the current work coordinate system, and 2 is the current tool coordinate system.
- trajectory_mode:When the high following mode is set, multiple modes are supported, including 0- complete transparent transmission mode, 1- curve fitting mode and 2- filtering mode.
- radio:Set the smoothing coefficient in curve fitting mode (range 0-100) or the filter parameter in filtering mode (range 0-1000). The higher the value, the better the smoothing effect.
- In practice, we choose the corresponding launch file to start, which will automatically select the correct model. If there are special requirements, you can modify the corresponding parameters here. After modification, recompile the configuration in the workspace directory, and then the modified configuration will take effect. Run the colcon build command in the workspace directory.
File truncated at 100 lines see the full file