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:
# Start trajectory control (generation 3 and 4 both use the base model)
ros2 launch rm_control rm_control.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. Start rm_driver first. See the generation-specific model table.
Content
- 1.rm_control Package Description
- 2.rm_control Package Function
- 2.1Basic use of the package
- 2.2Advanced use of the package
- 3.rm_control Package Architecture Description
- 3.1Overview of Package Files
- 4.rm_control Topic Description
rm_control_Package_Description
rm_control is a function package for realizing the moveit2 control of a real robotic arm. The package is mainly used to further subdivide the path points planned by moveit2, and give the subdivided path points to rm_driver in a through-transmission way to realize the planning and running of the robotic arm. This package is introduced in detail in 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。
rm_control_Package_Function
Basic_use_of_the_package
The unified entry point is recommended:
ros2 launch rm_control rm_control.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also supported; see the complete model table. -
follow(default:auto): accepts onlyauto,true, orfalse;autoselects low-follow mode (false) for all models; usefollow:=trueto select high-follow mode.
Selecting rx75 creates both the left_arm and right_arm control nodes. 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 run the rm_control package.
rm@rm-desktop:~$ ros2 launch rm_control rm_<arm_type>_control.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_control rm_65_control.launch.py
The following screen appears in the interface after successful node startup.
It does not play a role when the node of the package is launched alone. It needs to be combined with the rm_driver package and the relevant nodes of moveit2 to play a role. For details, please refer to the relevant content of “rm_moveit2_config Detailed Description”.
Advanced_use_of_the_package
The following mode is configured directly through the unified launch entry; editing a launch file and rebuilding the workspace are not required:
ros2 launch rm_control rm_control.launch.py arm_type:=65 follow:=true
follow:=true selects high-follow mode, while follow:=false selects low-follow mode. High-follow mode tracks the transmitted trajectory more closely and requires suitable transmission rate, velocity, and acceleration settings. Low-follow mode has a lower usage threshold, but points that cannot be reached in time may be discarded. The default and follow:=auto both select low-follow mode; use follow:=true to opt into high-follow mode.
The user-facing arm_type value is the canonical model string listed in the basic-use section. The numeric values 65, 651, 634, 632, 621, 75, and 72 are internal node-parameter mappings maintained by the unified launch file; they are not values that users should pass to the arm_type launch argument.
rm_control_Package_Architecture_Description
Overview_of_package_files
The current rm_control package is composed of the following files.
``` ├── CMakeLists.txt # compilation rule file ├── doc
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| rclcpp_action | |
| control_msgs | |
| std_msgs | |
| sensor_msgs | |
| rm_ros_interfaces |
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_control 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:
# Start trajectory control (generation 3 and 4 both use the base model)
ros2 launch rm_control rm_control.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. Start rm_driver first. See the generation-specific model table.
Content
- 1.rm_control Package Description
- 2.rm_control Package Function
- 2.1Basic use of the package
- 2.2Advanced use of the package
- 3.rm_control Package Architecture Description
- 3.1Overview of Package Files
- 4.rm_control Topic Description
rm_control_Package_Description
rm_control is a function package for realizing the moveit2 control of a real robotic arm. The package is mainly used to further subdivide the path points planned by moveit2, and give the subdivided path points to rm_driver in a through-transmission way to realize the planning and running of the robotic arm. This package is introduced in detail in 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。
rm_control_Package_Function
Basic_use_of_the_package
The unified entry point is recommended:
ros2 launch rm_control rm_control.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also supported; see the complete model table. -
follow(default:auto): accepts onlyauto,true, orfalse;autoselects low-follow mode (false) for all models; usefollow:=trueto select high-follow mode.
Selecting rx75 creates both the left_arm and right_arm control nodes. 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 run the rm_control package.
rm@rm-desktop:~$ ros2 launch rm_control rm_<arm_type>_control.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_control rm_65_control.launch.py
The following screen appears in the interface after successful node startup.
It does not play a role when the node of the package is launched alone. It needs to be combined with the rm_driver package and the relevant nodes of moveit2 to play a role. For details, please refer to the relevant content of “rm_moveit2_config Detailed Description”.
Advanced_use_of_the_package
The following mode is configured directly through the unified launch entry; editing a launch file and rebuilding the workspace are not required:
ros2 launch rm_control rm_control.launch.py arm_type:=65 follow:=true
follow:=true selects high-follow mode, while follow:=false selects low-follow mode. High-follow mode tracks the transmitted trajectory more closely and requires suitable transmission rate, velocity, and acceleration settings. Low-follow mode has a lower usage threshold, but points that cannot be reached in time may be discarded. The default and follow:=auto both select low-follow mode; use follow:=true to opt into high-follow mode.
The user-facing arm_type value is the canonical model string listed in the basic-use section. The numeric values 65, 651, 634, 632, 621, 75, and 72 are internal node-parameter mappings maintained by the unified launch file; they are not values that users should pass to the arm_type launch argument.
rm_control_Package_Architecture_Description
Overview_of_package_files
The current rm_control package is composed of the following files.
``` ├── CMakeLists.txt # compilation rule file ├── doc
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| rclcpp_action | |
| control_msgs | |
| std_msgs | |
| sensor_msgs | |
| rm_ros_interfaces |
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_control 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:
# Start trajectory control (generation 3 and 4 both use the base model)
ros2 launch rm_control rm_control.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. Start rm_driver first. See the generation-specific model table.
Content
- 1.rm_control Package Description
- 2.rm_control Package Function
- 2.1Basic use of the package
- 2.2Advanced use of the package
- 3.rm_control Package Architecture Description
- 3.1Overview of Package Files
- 4.rm_control Topic Description
rm_control_Package_Description
rm_control is a function package for realizing the moveit2 control of a real robotic arm. The package is mainly used to further subdivide the path points planned by moveit2, and give the subdivided path points to rm_driver in a through-transmission way to realize the planning and running of the robotic arm. This package is introduced in detail in 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。
rm_control_Package_Function
Basic_use_of_the_package
The unified entry point is recommended:
ros2 launch rm_control rm_control.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also supported; see the complete model table. -
follow(default:auto): accepts onlyauto,true, orfalse;autoselects low-follow mode (false) for all models; usefollow:=trueto select high-follow mode.
Selecting rx75 creates both the left_arm and right_arm control nodes. 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 run the rm_control package.
rm@rm-desktop:~$ ros2 launch rm_control rm_<arm_type>_control.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_control rm_65_control.launch.py
The following screen appears in the interface after successful node startup.
It does not play a role when the node of the package is launched alone. It needs to be combined with the rm_driver package and the relevant nodes of moveit2 to play a role. For details, please refer to the relevant content of “rm_moveit2_config Detailed Description”.
Advanced_use_of_the_package
The following mode is configured directly through the unified launch entry; editing a launch file and rebuilding the workspace are not required:
ros2 launch rm_control rm_control.launch.py arm_type:=65 follow:=true
follow:=true selects high-follow mode, while follow:=false selects low-follow mode. High-follow mode tracks the transmitted trajectory more closely and requires suitable transmission rate, velocity, and acceleration settings. Low-follow mode has a lower usage threshold, but points that cannot be reached in time may be discarded. The default and follow:=auto both select low-follow mode; use follow:=true to opt into high-follow mode.
The user-facing arm_type value is the canonical model string listed in the basic-use section. The numeric values 65, 651, 634, 632, 621, 75, and 72 are internal node-parameter mappings maintained by the unified launch file; they are not values that users should pass to the arm_type launch argument.
rm_control_Package_Architecture_Description
Overview_of_package_files
The current rm_control package is composed of the following files.
``` ├── CMakeLists.txt # compilation rule file ├── doc
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| rclcpp_action | |
| control_msgs | |
| std_msgs | |
| sensor_msgs | |
| rm_ros_interfaces |
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_control 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:
# Start trajectory control (generation 3 and 4 both use the base model)
ros2 launch rm_control rm_control.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. Start rm_driver first. See the generation-specific model table.
Content
- 1.rm_control Package Description
- 2.rm_control Package Function
- 2.1Basic use of the package
- 2.2Advanced use of the package
- 3.rm_control Package Architecture Description
- 3.1Overview of Package Files
- 4.rm_control Topic Description
rm_control_Package_Description
rm_control is a function package for realizing the moveit2 control of a real robotic arm. The package is mainly used to further subdivide the path points planned by moveit2, and give the subdivided path points to rm_driver in a through-transmission way to realize the planning and running of the robotic arm. This package is introduced in detail in 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。
rm_control_Package_Function
Basic_use_of_the_package
The unified entry point is recommended:
ros2 launch rm_control rm_control.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also supported; see the complete model table. -
follow(default:auto): accepts onlyauto,true, orfalse;autoselects low-follow mode (false) for all models; usefollow:=trueto select high-follow mode.
Selecting rx75 creates both the left_arm and right_arm control nodes. 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 run the rm_control package.
rm@rm-desktop:~$ ros2 launch rm_control rm_<arm_type>_control.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_control rm_65_control.launch.py
The following screen appears in the interface after successful node startup.
It does not play a role when the node of the package is launched alone. It needs to be combined with the rm_driver package and the relevant nodes of moveit2 to play a role. For details, please refer to the relevant content of “rm_moveit2_config Detailed Description”.
Advanced_use_of_the_package
The following mode is configured directly through the unified launch entry; editing a launch file and rebuilding the workspace are not required:
ros2 launch rm_control rm_control.launch.py arm_type:=65 follow:=true
follow:=true selects high-follow mode, while follow:=false selects low-follow mode. High-follow mode tracks the transmitted trajectory more closely and requires suitable transmission rate, velocity, and acceleration settings. Low-follow mode has a lower usage threshold, but points that cannot be reached in time may be discarded. The default and follow:=auto both select low-follow mode; use follow:=true to opt into high-follow mode.
The user-facing arm_type value is the canonical model string listed in the basic-use section. The numeric values 65, 651, 634, 632, 621, 75, and 72 are internal node-parameter mappings maintained by the unified launch file; they are not values that users should pass to the arm_type launch argument.
rm_control_Package_Architecture_Description
Overview_of_package_files
The current rm_control package is composed of the following files.
``` ├── CMakeLists.txt # compilation rule file ├── doc
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| rclcpp_action | |
| control_msgs | |
| std_msgs | |
| sensor_msgs | |
| rm_ros_interfaces |
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_control 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:
# Start trajectory control (generation 3 and 4 both use the base model)
ros2 launch rm_control rm_control.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. Start rm_driver first. See the generation-specific model table.
Content
- 1.rm_control Package Description
- 2.rm_control Package Function
- 2.1Basic use of the package
- 2.2Advanced use of the package
- 3.rm_control Package Architecture Description
- 3.1Overview of Package Files
- 4.rm_control Topic Description
rm_control_Package_Description
rm_control is a function package for realizing the moveit2 control of a real robotic arm. The package is mainly used to further subdivide the path points planned by moveit2, and give the subdivided path points to rm_driver in a through-transmission way to realize the planning and running of the robotic arm. This package is introduced in detail in 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。
rm_control_Package_Function
Basic_use_of_the_package
The unified entry point is recommended:
ros2 launch rm_control rm_control.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also supported; see the complete model table. -
follow(default:auto): accepts onlyauto,true, orfalse;autoselects low-follow mode (false) for all models; usefollow:=trueto select high-follow mode.
Selecting rx75 creates both the left_arm and right_arm control nodes. 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 run the rm_control package.
rm@rm-desktop:~$ ros2 launch rm_control rm_<arm_type>_control.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_control rm_65_control.launch.py
The following screen appears in the interface after successful node startup.
It does not play a role when the node of the package is launched alone. It needs to be combined with the rm_driver package and the relevant nodes of moveit2 to play a role. For details, please refer to the relevant content of “rm_moveit2_config Detailed Description”.
Advanced_use_of_the_package
The following mode is configured directly through the unified launch entry; editing a launch file and rebuilding the workspace are not required:
ros2 launch rm_control rm_control.launch.py arm_type:=65 follow:=true
follow:=true selects high-follow mode, while follow:=false selects low-follow mode. High-follow mode tracks the transmitted trajectory more closely and requires suitable transmission rate, velocity, and acceleration settings. Low-follow mode has a lower usage threshold, but points that cannot be reached in time may be discarded. The default and follow:=auto both select low-follow mode; use follow:=true to opt into high-follow mode.
The user-facing arm_type value is the canonical model string listed in the basic-use section. The numeric values 65, 651, 634, 632, 621, 75, and 72 are internal node-parameter mappings maintained by the unified launch file; they are not values that users should pass to the arm_type launch argument.
rm_control_Package_Architecture_Description
Overview_of_package_files
The current rm_control package is composed of the following files.
``` ├── CMakeLists.txt # compilation rule file ├── doc
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| rclcpp_action | |
| control_msgs | |
| std_msgs | |
| sensor_msgs | |
| rm_ros_interfaces |
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_control 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:
# Start trajectory control (generation 3 and 4 both use the base model)
ros2 launch rm_control rm_control.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. Start rm_driver first. See the generation-specific model table.
Content
- 1.rm_control Package Description
- 2.rm_control Package Function
- 2.1Basic use of the package
- 2.2Advanced use of the package
- 3.rm_control Package Architecture Description
- 3.1Overview of Package Files
- 4.rm_control Topic Description
rm_control_Package_Description
rm_control is a function package for realizing the moveit2 control of a real robotic arm. The package is mainly used to further subdivide the path points planned by moveit2, and give the subdivided path points to rm_driver in a through-transmission way to realize the planning and running of the robotic arm. This package is introduced in detail in 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。
rm_control_Package_Function
Basic_use_of_the_package
The unified entry point is recommended:
ros2 launch rm_control rm_control.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also supported; see the complete model table. -
follow(default:auto): accepts onlyauto,true, orfalse;autoselects low-follow mode (false) for all models; usefollow:=trueto select high-follow mode.
Selecting rx75 creates both the left_arm and right_arm control nodes. 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 run the rm_control package.
rm@rm-desktop:~$ ros2 launch rm_control rm_<arm_type>_control.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_control rm_65_control.launch.py
The following screen appears in the interface after successful node startup.
It does not play a role when the node of the package is launched alone. It needs to be combined with the rm_driver package and the relevant nodes of moveit2 to play a role. For details, please refer to the relevant content of “rm_moveit2_config Detailed Description”.
Advanced_use_of_the_package
The following mode is configured directly through the unified launch entry; editing a launch file and rebuilding the workspace are not required:
ros2 launch rm_control rm_control.launch.py arm_type:=65 follow:=true
follow:=true selects high-follow mode, while follow:=false selects low-follow mode. High-follow mode tracks the transmitted trajectory more closely and requires suitable transmission rate, velocity, and acceleration settings. Low-follow mode has a lower usage threshold, but points that cannot be reached in time may be discarded. The default and follow:=auto both select low-follow mode; use follow:=true to opt into high-follow mode.
The user-facing arm_type value is the canonical model string listed in the basic-use section. The numeric values 65, 651, 634, 632, 621, 75, and 72 are internal node-parameter mappings maintained by the unified launch file; they are not values that users should pass to the arm_type launch argument.
rm_control_Package_Architecture_Description
Overview_of_package_files
The current rm_control package is composed of the following files.
``` ├── CMakeLists.txt # compilation rule file ├── doc
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| rclcpp_action | |
| control_msgs | |
| std_msgs | |
| sensor_msgs | |
| rm_ros_interfaces |
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_control 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:
# Start trajectory control (generation 3 and 4 both use the base model)
ros2 launch rm_control rm_control.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. Start rm_driver first. See the generation-specific model table.
Content
- 1.rm_control Package Description
- 2.rm_control Package Function
- 2.1Basic use of the package
- 2.2Advanced use of the package
- 3.rm_control Package Architecture Description
- 3.1Overview of Package Files
- 4.rm_control Topic Description
rm_control_Package_Description
rm_control is a function package for realizing the moveit2 control of a real robotic arm. The package is mainly used to further subdivide the path points planned by moveit2, and give the subdivided path points to rm_driver in a through-transmission way to realize the planning and running of the robotic arm. This package is introduced in detail in 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。
rm_control_Package_Function
Basic_use_of_the_package
The unified entry point is recommended:
ros2 launch rm_control rm_control.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also supported; see the complete model table. -
follow(default:auto): accepts onlyauto,true, orfalse;autoselects low-follow mode (false) for all models; usefollow:=trueto select high-follow mode.
Selecting rx75 creates both the left_arm and right_arm control nodes. 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 run the rm_control package.
rm@rm-desktop:~$ ros2 launch rm_control rm_<arm_type>_control.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_control rm_65_control.launch.py
The following screen appears in the interface after successful node startup.
It does not play a role when the node of the package is launched alone. It needs to be combined with the rm_driver package and the relevant nodes of moveit2 to play a role. For details, please refer to the relevant content of “rm_moveit2_config Detailed Description”.
Advanced_use_of_the_package
The following mode is configured directly through the unified launch entry; editing a launch file and rebuilding the workspace are not required:
ros2 launch rm_control rm_control.launch.py arm_type:=65 follow:=true
follow:=true selects high-follow mode, while follow:=false selects low-follow mode. High-follow mode tracks the transmitted trajectory more closely and requires suitable transmission rate, velocity, and acceleration settings. Low-follow mode has a lower usage threshold, but points that cannot be reached in time may be discarded. The default and follow:=auto both select low-follow mode; use follow:=true to opt into high-follow mode.
The user-facing arm_type value is the canonical model string listed in the basic-use section. The numeric values 65, 651, 634, 632, 621, 75, and 72 are internal node-parameter mappings maintained by the unified launch file; they are not values that users should pass to the arm_type launch argument.
rm_control_Package_Architecture_Description
Overview_of_package_files
The current rm_control package is composed of the following files.
``` ├── CMakeLists.txt # compilation rule file ├── doc
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| rclcpp_action | |
| control_msgs | |
| std_msgs | |
| sensor_msgs | |
| rm_ros_interfaces |
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_control 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:
# Start trajectory control (generation 3 and 4 both use the base model)
ros2 launch rm_control rm_control.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. Start rm_driver first. See the generation-specific model table.
Content
- 1.rm_control Package Description
- 2.rm_control Package Function
- 2.1Basic use of the package
- 2.2Advanced use of the package
- 3.rm_control Package Architecture Description
- 3.1Overview of Package Files
- 4.rm_control Topic Description
rm_control_Package_Description
rm_control is a function package for realizing the moveit2 control of a real robotic arm. The package is mainly used to further subdivide the path points planned by moveit2, and give the subdivided path points to rm_driver in a through-transmission way to realize the planning and running of the robotic arm. This package is introduced in detail in 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。
rm_control_Package_Function
Basic_use_of_the_package
The unified entry point is recommended:
ros2 launch rm_control rm_control.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also supported; see the complete model table. -
follow(default:auto): accepts onlyauto,true, orfalse;autoselects low-follow mode (false) for all models; usefollow:=trueto select high-follow mode.
Selecting rx75 creates both the left_arm and right_arm control nodes. 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 run the rm_control package.
rm@rm-desktop:~$ ros2 launch rm_control rm_<arm_type>_control.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_control rm_65_control.launch.py
The following screen appears in the interface after successful node startup.
It does not play a role when the node of the package is launched alone. It needs to be combined with the rm_driver package and the relevant nodes of moveit2 to play a role. For details, please refer to the relevant content of “rm_moveit2_config Detailed Description”.
Advanced_use_of_the_package
The following mode is configured directly through the unified launch entry; editing a launch file and rebuilding the workspace are not required:
ros2 launch rm_control rm_control.launch.py arm_type:=65 follow:=true
follow:=true selects high-follow mode, while follow:=false selects low-follow mode. High-follow mode tracks the transmitted trajectory more closely and requires suitable transmission rate, velocity, and acceleration settings. Low-follow mode has a lower usage threshold, but points that cannot be reached in time may be discarded. The default and follow:=auto both select low-follow mode; use follow:=true to opt into high-follow mode.
The user-facing arm_type value is the canonical model string listed in the basic-use section. The numeric values 65, 651, 634, 632, 621, 75, and 72 are internal node-parameter mappings maintained by the unified launch file; they are not values that users should pass to the arm_type launch argument.
rm_control_Package_Architecture_Description
Overview_of_package_files
The current rm_control package is composed of the following files.
``` ├── CMakeLists.txt # compilation rule file ├── doc
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| rclcpp_action | |
| control_msgs | |
| std_msgs | |
| sensor_msgs | |
| rm_ros_interfaces |
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_control 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:
# Start trajectory control (generation 3 and 4 both use the base model)
ros2 launch rm_control rm_control.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. Start rm_driver first. See the generation-specific model table.
Content
- 1.rm_control Package Description
- 2.rm_control Package Function
- 2.1Basic use of the package
- 2.2Advanced use of the package
- 3.rm_control Package Architecture Description
- 3.1Overview of Package Files
- 4.rm_control Topic Description
rm_control_Package_Description
rm_control is a function package for realizing the moveit2 control of a real robotic arm. The package is mainly used to further subdivide the path points planned by moveit2, and give the subdivided path points to rm_driver in a through-transmission way to realize the planning and running of the robotic arm. This package is introduced in detail in 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。
rm_control_Package_Function
Basic_use_of_the_package
The unified entry point is recommended:
ros2 launch rm_control rm_control.launch.py arm_type:=65
Unified launch arguments:
-
arm_type(required):63,63_iii,65,75,eco62,eco63,eco65,gen72,gen72_ii, orrx75. Complete selectors such as65-6fb,eco63-6fb, andrx75-6fb-vare also supported; see the complete model table. -
follow(default:auto): accepts onlyauto,true, orfalse;autoselects low-follow mode (false) for all models; usefollow:=trueto select high-follow mode.
Selecting rx75 creates both the left_arm and right_arm control nodes. 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 run the rm_control package.
rm@rm-desktop:~$ ros2 launch rm_control rm_<arm_type>_control.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_control rm_65_control.launch.py
The following screen appears in the interface after successful node startup.
It does not play a role when the node of the package is launched alone. It needs to be combined with the rm_driver package and the relevant nodes of moveit2 to play a role. For details, please refer to the relevant content of “rm_moveit2_config Detailed Description”.
Advanced_use_of_the_package
The following mode is configured directly through the unified launch entry; editing a launch file and rebuilding the workspace are not required:
ros2 launch rm_control rm_control.launch.py arm_type:=65 follow:=true
follow:=true selects high-follow mode, while follow:=false selects low-follow mode. High-follow mode tracks the transmitted trajectory more closely and requires suitable transmission rate, velocity, and acceleration settings. Low-follow mode has a lower usage threshold, but points that cannot be reached in time may be discarded. The default and follow:=auto both select low-follow mode; use follow:=true to opt into high-follow mode.
The user-facing arm_type value is the canonical model string listed in the basic-use section. The numeric values 65, 651, 634, 632, 621, 75, and 72 are internal node-parameter mappings maintained by the unified launch file; they are not values that users should pass to the arm_type launch argument.
rm_control_Package_Architecture_Description
Overview_of_package_files
The current rm_control package is composed of the following files.
``` ├── CMakeLists.txt # compilation rule file ├── doc
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch | |
| launch_ros | |
| ament_lint_auto | |
| ament_lint_common | |
| rclcpp | |
| rclcpp_action | |
| control_msgs | |
| std_msgs | |
| sensor_msgs | |
| rm_ros_interfaces |
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_control at Robotics Stack Exchange
|
rm_control package from rm_control reporm_common rm_control rm_dbus rm_gazebo rm_hw rm_msgs rm_referee rm_vt |
ROS Distro
|
Package Summary
| Version | 0.1.20 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/rm-controls/rm_control.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-05 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Qiayuan Liao
Authors
- Qiayuan Liao
Changelog for package rm_control
0.1.20 (2023-06-20)
- Merge branch 'master' into suggest_fire
- Merge branch 'rm-controls:master' into master
- Merge branch 'dev/ui_refact' into dev/balance_cmd_send
- Merge branch 'master' into dev/ui_refact # Conflicts: # rm_referee/include/rm_referee/common/protocol.h # rm_referee/src/ui/graph.cpp
- Merge pull request #146 from ye-luo-xi-tui/master 0.1.19
- Merge branch 'rm-controls:master' into master
- Contributors: 1moule, ye-luo-xi-tui, yuchen, 王湘鈜
0.1.19 (2023-05-03)
- Merge branch 'master' into multi_dof_controller # Conflicts: # rm_common/include/rm_common/decision/command_sender.h # rm_msgs/CMakeLists.txt
- Merge branch 'master' into one_click_turn_cmd_sender
- Merge branch 'master' into switch_camera_command_sender # Conflicts: # rm_referee/include/rm_referee/ui/trigger_change_ui.h # rm_referee/src/ui/trigger_change_ui.cpp
- Merge pull request #120 from ye-luo-xi-tui/master 0.1.18
- Contributors: 1moule, LSY, ye-luo-xi-tui
0.1.18 (2023-03-25)
- Merge branch 'master' into acceleration # Conflicts: # rm_common/include/rm_common/decision/command_sender.h
- Merge pull request #104 from ye-luo-xi-tui/master 0.1.17
- Contributors: ye-luo-xi-tui, yezi
0.1.17 (2023-02-21)
- Merge branch 'rm-controls:master' into master
- Merge pull request #84 from ye-luo-xi-tui/master 0.1.16
- Contributors: ye-luo-xi-tui, 吕骏骐
0.1.16 (2022-11-24)
- Merge branch 'dev'
- Merge branch 'rm-controls:master' into master
- Merge branch 'master' into rm_referee_pr
- Merge pull request #74 from ye-luo-xi-tui/dev Update 0.1.15
- Merge branch 'master' into referee # Conflicts: # rm_common/include/rm_common/decision/service_caller.h # rm_msgs/CMakeLists.txt # rm_msgs/msg/referee/GameRobotStatus.msg # rm_msgs/msg/referee/GameStatus.msg
- Merge branch 'master' into referee1
- Contributors: ye-luo-xi-tui, yezi, yuchen, 吕骏骐
0.1.15 (2022-09-02)
0.1.14 (2022-06-16)
0.1.13 (2022-06-12)
0.1.12 (2022-06-11)
- Merge pull request #59 from ye-luo-xi-tui/master 0.1.11
- Contributors: QiayuanLiao
0.1.11 (2022-06-10)
- Merge remote-tracking branch 'origin/master'
- Contributors: QiayuanLiao, YuuinIH, qiayuan, yezi
0.1.10 (2022-05-22)
- Merge pull request #45 from ye-luo-xi-tui/master Add rm_dbus to metapackage's package.xml
- Add rm_dbus to metapackage's package.xml.
- Contributors: QiayuanLiao, yezi
0.1.9 (2022-3-28)
- Separate rm_description out of rm_control
- Revert "Update package.xml" This reverts commit a46a8b40dffc0c5fa61981d9ca862a7f1da7e559.
- Update package.xml
- Merge remote-tracking branch 'origin/master'
- Contributors: Jie j, YuuinIH
0.1.8 (2021-12-7)
- Merge branch 'master' into gimbal/opti_or_simplify
File truncated at 100 lines see the full file