Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_driver at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | Apache-2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/realmanrobot/ros2_rm_robot.git |
| VCS Type | git |
| VCS Version | humble |
| Last Updated | 2026-10-30 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- xtark
Authors
Launch examples
After building and sourcing the workspace, for an RM65 with integrated force sensing:
# Connect to the real robot (generation 3 and 4 both use the base model)
ros2 launch rm_driver rm_driver.launch.py \
arm_type:=65
# Note: Generation 4 software 1.0.6 and later names the former 6fb end link 6f.
# rm_driver and rm_control only need a base model, such as 63, 65, 75, eco63 or eco65.
# The naming difference does not change these launch arguments.
This package is part of the real-robot control chain; Gazebo uses simulation controllers. arm_type selects the base-family configuration. See the generation-specific model table.
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
The unified entry point is recommended:
ros2 launch rm_driver rm_driver.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Supported complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also accepted; see the complete model table. -
driver_config(default:auto): driver YAML path for a single-arm model. -
left_driver_config/right_driver_config(default:auto): left- and right-arm driver YAML paths for RX75.
The suffix identifies the complete model; Driver still selects the existing family YAML. For example, 65-6fb and 65 both use rm_65_config.yaml.
RX75 (including rx75-6fb and rx75-6fb-v) uses separate left and right configurations; override them with left_driver_config and right_driver_config. driver_config is valid only for single-arm models, while the left/right arguments are valid only for RX75. Invalid combinations or missing files fail immediately.
The eight legacy model entry points (63, 65, 75, eco62, eco63, eco65, gen72, and rx75) are now compatibility wrappers, and their existing commands remain supported.
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_
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.

File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| ament_index_python | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| std_msgs | |
| sensor_msgs | |
| geometry_msgs | |
| rm_ros_interfaces |
System Dependencies
| Name |
|---|
| python3-yaml |
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |