Package Summary
| Version | 1.7.1 |
| License | BSD |
| 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
Additional Links
Maintainers
- Kaola
Authors
- Kaola
Launch examples
After building and sourcing the workspace, simulate an RM65 with integrated force sensing in Gazebo:
# Simulation (generation 3 and 4 both retain the 6fb model name)
ros2 launch rm_gazebo rm_gazebo.launch.py \
arm_type:=65-6fb
This package starts Gazebo simulation, which does not connect to a controller or depend on its software version. Generation 4 software 1.0.6 and later names the former 6fb end link 6f; keep 65-6fb when simulating the same geometry. See the generation-specific model table.
Content
- 1.rm_gazebo Package Description
- 2.rm_gazebo Package Running
- 2.1Control of the simulation robotic arm
- 3.rm_gazebo Package Architecture Description
- 3.1Overview of Package Files
rm_gazebo_Package_Description
rm_gazebo is mainly used for realizing the simulation function of robot arm Moveit2 planning. We build a virtual robotic arm in the simulation environment of Gazebo, and then control the virtual robot arm in Gazebo through Moveit2. This package is introduced in detail in the following aspects.
- 1.Package use.
- 2.Package architecture description. Through the introduction of this part, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
Source code address: https://github.com/RealManRobot/ros2_rm_robot.git。
rm_gazebo_Package_Running
Control_of_the_simulation_robotic_arm
After the installation of the environment and the package, we can run the rm_gazebo package.
The unified entry is the recommended way to launch the Gazebo world and robot:
rm@rm-desktop:~$ ros2 launch rm_gazebo rm_gazebo.launch.py arm_type:=65-6fb
The unified entry accepts:
-
arm_type: required; selects the model and end-link version, e.g.65,65-6fb, orrx75-6fb-v. Bare families select the standard version. See the supported selections. -
model: defaults toauto, preferring colored DAE when available and otherwise using STL.model:=stlselects original STL;model:=daerequires DAE. Legacy entries also accept this argument.
This branch retains Gazebo Fortress. Gazebo and the accompanying MoveIt RViz2 use the same visuals; existing joint, collision and control settings are retained.
-
start_gazebo: defaulttrue. Set it tofalseonly to reuse an already running Gazebo world namedempty. This skips the Gazebo process itself, but robot spawning, the/world/empty/clockbridge, and controller spawning still run. If the external world is absent or entity creation times out, launch returns a non-zero status and does not attempt to start the controllers. -
joint_states_topic: onlyautois currently supported. It resolves to/joint_statesfor normal arms and/joint_state_broadcaster/joint_statesfor RX75. -
use_sim_time: controls simulation time forrobot_state_publisher, defaulttrue.
The catalog covers 10 robot models and 21 supported model/variant combinations. All 21 legacy gazebo_*_demo.launch.py entries remain available with their original arguments and defaults. For example:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_65_demo.launch.py
Press Ctrl+C to stop the simulation. The launcher forwards the signal to the Gazebo server, GUI, and ros2_control, waits for resource cleanup, and records this user-requested shutdown as a clean exit. Qt/QML compatibility warnings are suppressed only inside the Gazebo child process; Gazebo and ROS warnings and errors remain visible.
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6f_demo.launch.py
The command to start the integrated six-axis force version is currently available for 63, 63_III, 65, 75, eco63, eco65, and rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_demo.launch.py
The command to start the vision-enabled integrated six-axis force version is currently only available for rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_v_demo.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_<arm_type>_config gazebo_moveit_demo.launch.py
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
```
rm@rm-desktop:~$ ros2 launch rm_
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_gazebo at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | BSD |
| 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
Additional Links
Maintainers
- Kaola
Authors
- Kaola
Launch examples
After building and sourcing the workspace, simulate an RM65 with integrated force sensing in Gazebo:
# Simulation (generation 3 and 4 both retain the 6fb model name)
ros2 launch rm_gazebo rm_gazebo.launch.py \
arm_type:=65-6fb
This package starts Gazebo simulation, which does not connect to a controller or depend on its software version. Generation 4 software 1.0.6 and later names the former 6fb end link 6f; keep 65-6fb when simulating the same geometry. See the generation-specific model table.
Content
- 1.rm_gazebo Package Description
- 2.rm_gazebo Package Running
- 2.1Control of the simulation robotic arm
- 3.rm_gazebo Package Architecture Description
- 3.1Overview of Package Files
rm_gazebo_Package_Description
rm_gazebo is mainly used for realizing the simulation function of robot arm Moveit2 planning. We build a virtual robotic arm in the simulation environment of Gazebo, and then control the virtual robot arm in Gazebo through Moveit2. This package is introduced in detail in the following aspects.
- 1.Package use.
- 2.Package architecture description. Through the introduction of this part, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
Source code address: https://github.com/RealManRobot/ros2_rm_robot.git。
rm_gazebo_Package_Running
Control_of_the_simulation_robotic_arm
After the installation of the environment and the package, we can run the rm_gazebo package.
The unified entry is the recommended way to launch the Gazebo world and robot:
rm@rm-desktop:~$ ros2 launch rm_gazebo rm_gazebo.launch.py arm_type:=65-6fb
The unified entry accepts:
-
arm_type: required; selects the model and end-link version, e.g.65,65-6fb, orrx75-6fb-v. Bare families select the standard version. See the supported selections. -
model: defaults toauto, preferring colored DAE when available and otherwise using STL.model:=stlselects original STL;model:=daerequires DAE. Legacy entries also accept this argument.
This branch retains Gazebo Fortress. Gazebo and the accompanying MoveIt RViz2 use the same visuals; existing joint, collision and control settings are retained.
-
start_gazebo: defaulttrue. Set it tofalseonly to reuse an already running Gazebo world namedempty. This skips the Gazebo process itself, but robot spawning, the/world/empty/clockbridge, and controller spawning still run. If the external world is absent or entity creation times out, launch returns a non-zero status and does not attempt to start the controllers. -
joint_states_topic: onlyautois currently supported. It resolves to/joint_statesfor normal arms and/joint_state_broadcaster/joint_statesfor RX75. -
use_sim_time: controls simulation time forrobot_state_publisher, defaulttrue.
The catalog covers 10 robot models and 21 supported model/variant combinations. All 21 legacy gazebo_*_demo.launch.py entries remain available with their original arguments and defaults. For example:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_65_demo.launch.py
Press Ctrl+C to stop the simulation. The launcher forwards the signal to the Gazebo server, GUI, and ros2_control, waits for resource cleanup, and records this user-requested shutdown as a clean exit. Qt/QML compatibility warnings are suppressed only inside the Gazebo child process; Gazebo and ROS warnings and errors remain visible.
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6f_demo.launch.py
The command to start the integrated six-axis force version is currently available for 63, 63_III, 65, 75, eco63, eco65, and rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_demo.launch.py
The command to start the vision-enabled integrated six-axis force version is currently only available for rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_v_demo.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_<arm_type>_config gazebo_moveit_demo.launch.py
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
```
rm@rm-desktop:~$ ros2 launch rm_
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_gazebo at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | BSD |
| 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
Additional Links
Maintainers
- Kaola
Authors
- Kaola
Launch examples
After building and sourcing the workspace, simulate an RM65 with integrated force sensing in Gazebo:
# Simulation (generation 3 and 4 both retain the 6fb model name)
ros2 launch rm_gazebo rm_gazebo.launch.py \
arm_type:=65-6fb
This package starts Gazebo simulation, which does not connect to a controller or depend on its software version. Generation 4 software 1.0.6 and later names the former 6fb end link 6f; keep 65-6fb when simulating the same geometry. See the generation-specific model table.
Content
- 1.rm_gazebo Package Description
- 2.rm_gazebo Package Running
- 2.1Control of the simulation robotic arm
- 3.rm_gazebo Package Architecture Description
- 3.1Overview of Package Files
rm_gazebo_Package_Description
rm_gazebo is mainly used for realizing the simulation function of robot arm Moveit2 planning. We build a virtual robotic arm in the simulation environment of Gazebo, and then control the virtual robot arm in Gazebo through Moveit2. This package is introduced in detail in the following aspects.
- 1.Package use.
- 2.Package architecture description. Through the introduction of this part, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
Source code address: https://github.com/RealManRobot/ros2_rm_robot.git。
rm_gazebo_Package_Running
Control_of_the_simulation_robotic_arm
After the installation of the environment and the package, we can run the rm_gazebo package.
The unified entry is the recommended way to launch the Gazebo world and robot:
rm@rm-desktop:~$ ros2 launch rm_gazebo rm_gazebo.launch.py arm_type:=65-6fb
The unified entry accepts:
-
arm_type: required; selects the model and end-link version, e.g.65,65-6fb, orrx75-6fb-v. Bare families select the standard version. See the supported selections. -
model: defaults toauto, preferring colored DAE when available and otherwise using STL.model:=stlselects original STL;model:=daerequires DAE. Legacy entries also accept this argument.
This branch retains Gazebo Fortress. Gazebo and the accompanying MoveIt RViz2 use the same visuals; existing joint, collision and control settings are retained.
-
start_gazebo: defaulttrue. Set it tofalseonly to reuse an already running Gazebo world namedempty. This skips the Gazebo process itself, but robot spawning, the/world/empty/clockbridge, and controller spawning still run. If the external world is absent or entity creation times out, launch returns a non-zero status and does not attempt to start the controllers. -
joint_states_topic: onlyautois currently supported. It resolves to/joint_statesfor normal arms and/joint_state_broadcaster/joint_statesfor RX75. -
use_sim_time: controls simulation time forrobot_state_publisher, defaulttrue.
The catalog covers 10 robot models and 21 supported model/variant combinations. All 21 legacy gazebo_*_demo.launch.py entries remain available with their original arguments and defaults. For example:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_65_demo.launch.py
Press Ctrl+C to stop the simulation. The launcher forwards the signal to the Gazebo server, GUI, and ros2_control, waits for resource cleanup, and records this user-requested shutdown as a clean exit. Qt/QML compatibility warnings are suppressed only inside the Gazebo child process; Gazebo and ROS warnings and errors remain visible.
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6f_demo.launch.py
The command to start the integrated six-axis force version is currently available for 63, 63_III, 65, 75, eco63, eco65, and rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_demo.launch.py
The command to start the vision-enabled integrated six-axis force version is currently only available for rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_v_demo.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_<arm_type>_config gazebo_moveit_demo.launch.py
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
```
rm@rm-desktop:~$ ros2 launch rm_
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_gazebo at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | BSD |
| 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
Additional Links
Maintainers
- Kaola
Authors
- Kaola
Launch examples
After building and sourcing the workspace, simulate an RM65 with integrated force sensing in Gazebo:
# Simulation (generation 3 and 4 both retain the 6fb model name)
ros2 launch rm_gazebo rm_gazebo.launch.py \
arm_type:=65-6fb
This package starts Gazebo simulation, which does not connect to a controller or depend on its software version. Generation 4 software 1.0.6 and later names the former 6fb end link 6f; keep 65-6fb when simulating the same geometry. See the generation-specific model table.
Content
- 1.rm_gazebo Package Description
- 2.rm_gazebo Package Running
- 2.1Control of the simulation robotic arm
- 3.rm_gazebo Package Architecture Description
- 3.1Overview of Package Files
rm_gazebo_Package_Description
rm_gazebo is mainly used for realizing the simulation function of robot arm Moveit2 planning. We build a virtual robotic arm in the simulation environment of Gazebo, and then control the virtual robot arm in Gazebo through Moveit2. This package is introduced in detail in the following aspects.
- 1.Package use.
- 2.Package architecture description. Through the introduction of this part, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
Source code address: https://github.com/RealManRobot/ros2_rm_robot.git。
rm_gazebo_Package_Running
Control_of_the_simulation_robotic_arm
After the installation of the environment and the package, we can run the rm_gazebo package.
The unified entry is the recommended way to launch the Gazebo world and robot:
rm@rm-desktop:~$ ros2 launch rm_gazebo rm_gazebo.launch.py arm_type:=65-6fb
The unified entry accepts:
-
arm_type: required; selects the model and end-link version, e.g.65,65-6fb, orrx75-6fb-v. Bare families select the standard version. See the supported selections. -
model: defaults toauto, preferring colored DAE when available and otherwise using STL.model:=stlselects original STL;model:=daerequires DAE. Legacy entries also accept this argument.
This branch retains Gazebo Fortress. Gazebo and the accompanying MoveIt RViz2 use the same visuals; existing joint, collision and control settings are retained.
-
start_gazebo: defaulttrue. Set it tofalseonly to reuse an already running Gazebo world namedempty. This skips the Gazebo process itself, but robot spawning, the/world/empty/clockbridge, and controller spawning still run. If the external world is absent or entity creation times out, launch returns a non-zero status and does not attempt to start the controllers. -
joint_states_topic: onlyautois currently supported. It resolves to/joint_statesfor normal arms and/joint_state_broadcaster/joint_statesfor RX75. -
use_sim_time: controls simulation time forrobot_state_publisher, defaulttrue.
The catalog covers 10 robot models and 21 supported model/variant combinations. All 21 legacy gazebo_*_demo.launch.py entries remain available with their original arguments and defaults. For example:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_65_demo.launch.py
Press Ctrl+C to stop the simulation. The launcher forwards the signal to the Gazebo server, GUI, and ros2_control, waits for resource cleanup, and records this user-requested shutdown as a clean exit. Qt/QML compatibility warnings are suppressed only inside the Gazebo child process; Gazebo and ROS warnings and errors remain visible.
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6f_demo.launch.py
The command to start the integrated six-axis force version is currently available for 63, 63_III, 65, 75, eco63, eco65, and rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_demo.launch.py
The command to start the vision-enabled integrated six-axis force version is currently only available for rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_v_demo.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_<arm_type>_config gazebo_moveit_demo.launch.py
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
```
rm@rm-desktop:~$ ros2 launch rm_
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_gazebo at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | BSD |
| 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
Additional Links
Maintainers
- Kaola
Authors
- Kaola
Launch examples
After building and sourcing the workspace, simulate an RM65 with integrated force sensing in Gazebo:
# Simulation (generation 3 and 4 both retain the 6fb model name)
ros2 launch rm_gazebo rm_gazebo.launch.py \
arm_type:=65-6fb
This package starts Gazebo simulation, which does not connect to a controller or depend on its software version. Generation 4 software 1.0.6 and later names the former 6fb end link 6f; keep 65-6fb when simulating the same geometry. See the generation-specific model table.
Content
- 1.rm_gazebo Package Description
- 2.rm_gazebo Package Running
- 2.1Control of the simulation robotic arm
- 3.rm_gazebo Package Architecture Description
- 3.1Overview of Package Files
rm_gazebo_Package_Description
rm_gazebo is mainly used for realizing the simulation function of robot arm Moveit2 planning. We build a virtual robotic arm in the simulation environment of Gazebo, and then control the virtual robot arm in Gazebo through Moveit2. This package is introduced in detail in the following aspects.
- 1.Package use.
- 2.Package architecture description. Through the introduction of this part, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
Source code address: https://github.com/RealManRobot/ros2_rm_robot.git。
rm_gazebo_Package_Running
Control_of_the_simulation_robotic_arm
After the installation of the environment and the package, we can run the rm_gazebo package.
The unified entry is the recommended way to launch the Gazebo world and robot:
rm@rm-desktop:~$ ros2 launch rm_gazebo rm_gazebo.launch.py arm_type:=65-6fb
The unified entry accepts:
-
arm_type: required; selects the model and end-link version, e.g.65,65-6fb, orrx75-6fb-v. Bare families select the standard version. See the supported selections. -
model: defaults toauto, preferring colored DAE when available and otherwise using STL.model:=stlselects original STL;model:=daerequires DAE. Legacy entries also accept this argument.
This branch retains Gazebo Fortress. Gazebo and the accompanying MoveIt RViz2 use the same visuals; existing joint, collision and control settings are retained.
-
start_gazebo: defaulttrue. Set it tofalseonly to reuse an already running Gazebo world namedempty. This skips the Gazebo process itself, but robot spawning, the/world/empty/clockbridge, and controller spawning still run. If the external world is absent or entity creation times out, launch returns a non-zero status and does not attempt to start the controllers. -
joint_states_topic: onlyautois currently supported. It resolves to/joint_statesfor normal arms and/joint_state_broadcaster/joint_statesfor RX75. -
use_sim_time: controls simulation time forrobot_state_publisher, defaulttrue.
The catalog covers 10 robot models and 21 supported model/variant combinations. All 21 legacy gazebo_*_demo.launch.py entries remain available with their original arguments and defaults. For example:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_65_demo.launch.py
Press Ctrl+C to stop the simulation. The launcher forwards the signal to the Gazebo server, GUI, and ros2_control, waits for resource cleanup, and records this user-requested shutdown as a clean exit. Qt/QML compatibility warnings are suppressed only inside the Gazebo child process; Gazebo and ROS warnings and errors remain visible.
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6f_demo.launch.py
The command to start the integrated six-axis force version is currently available for 63, 63_III, 65, 75, eco63, eco65, and rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_demo.launch.py
The command to start the vision-enabled integrated six-axis force version is currently only available for rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_v_demo.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_<arm_type>_config gazebo_moveit_demo.launch.py
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
```
rm@rm-desktop:~$ ros2 launch rm_
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_gazebo at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | BSD |
| 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
Additional Links
Maintainers
- Kaola
Authors
- Kaola
Launch examples
After building and sourcing the workspace, simulate an RM65 with integrated force sensing in Gazebo:
# Simulation (generation 3 and 4 both retain the 6fb model name)
ros2 launch rm_gazebo rm_gazebo.launch.py \
arm_type:=65-6fb
This package starts Gazebo simulation, which does not connect to a controller or depend on its software version. Generation 4 software 1.0.6 and later names the former 6fb end link 6f; keep 65-6fb when simulating the same geometry. See the generation-specific model table.
Content
- 1.rm_gazebo Package Description
- 2.rm_gazebo Package Running
- 2.1Control of the simulation robotic arm
- 3.rm_gazebo Package Architecture Description
- 3.1Overview of Package Files
rm_gazebo_Package_Description
rm_gazebo is mainly used for realizing the simulation function of robot arm Moveit2 planning. We build a virtual robotic arm in the simulation environment of Gazebo, and then control the virtual robot arm in Gazebo through Moveit2. This package is introduced in detail in the following aspects.
- 1.Package use.
- 2.Package architecture description. Through the introduction of this part, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
Source code address: https://github.com/RealManRobot/ros2_rm_robot.git。
rm_gazebo_Package_Running
Control_of_the_simulation_robotic_arm
After the installation of the environment and the package, we can run the rm_gazebo package.
The unified entry is the recommended way to launch the Gazebo world and robot:
rm@rm-desktop:~$ ros2 launch rm_gazebo rm_gazebo.launch.py arm_type:=65-6fb
The unified entry accepts:
-
arm_type: required; selects the model and end-link version, e.g.65,65-6fb, orrx75-6fb-v. Bare families select the standard version. See the supported selections. -
model: defaults toauto, preferring colored DAE when available and otherwise using STL.model:=stlselects original STL;model:=daerequires DAE. Legacy entries also accept this argument.
This branch retains Gazebo Fortress. Gazebo and the accompanying MoveIt RViz2 use the same visuals; existing joint, collision and control settings are retained.
-
start_gazebo: defaulttrue. Set it tofalseonly to reuse an already running Gazebo world namedempty. This skips the Gazebo process itself, but robot spawning, the/world/empty/clockbridge, and controller spawning still run. If the external world is absent or entity creation times out, launch returns a non-zero status and does not attempt to start the controllers. -
joint_states_topic: onlyautois currently supported. It resolves to/joint_statesfor normal arms and/joint_state_broadcaster/joint_statesfor RX75. -
use_sim_time: controls simulation time forrobot_state_publisher, defaulttrue.
The catalog covers 10 robot models and 21 supported model/variant combinations. All 21 legacy gazebo_*_demo.launch.py entries remain available with their original arguments and defaults. For example:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_65_demo.launch.py
Press Ctrl+C to stop the simulation. The launcher forwards the signal to the Gazebo server, GUI, and ros2_control, waits for resource cleanup, and records this user-requested shutdown as a clean exit. Qt/QML compatibility warnings are suppressed only inside the Gazebo child process; Gazebo and ROS warnings and errors remain visible.
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6f_demo.launch.py
The command to start the integrated six-axis force version is currently available for 63, 63_III, 65, 75, eco63, eco65, and rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_demo.launch.py
The command to start the vision-enabled integrated six-axis force version is currently only available for rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_v_demo.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_<arm_type>_config gazebo_moveit_demo.launch.py
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
```
rm@rm-desktop:~$ ros2 launch rm_
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_gazebo at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | BSD |
| 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
Additional Links
Maintainers
- Kaola
Authors
- Kaola
Launch examples
After building and sourcing the workspace, simulate an RM65 with integrated force sensing in Gazebo:
# Simulation (generation 3 and 4 both retain the 6fb model name)
ros2 launch rm_gazebo rm_gazebo.launch.py \
arm_type:=65-6fb
This package starts Gazebo simulation, which does not connect to a controller or depend on its software version. Generation 4 software 1.0.6 and later names the former 6fb end link 6f; keep 65-6fb when simulating the same geometry. See the generation-specific model table.
Content
- 1.rm_gazebo Package Description
- 2.rm_gazebo Package Running
- 2.1Control of the simulation robotic arm
- 3.rm_gazebo Package Architecture Description
- 3.1Overview of Package Files
rm_gazebo_Package_Description
rm_gazebo is mainly used for realizing the simulation function of robot arm Moveit2 planning. We build a virtual robotic arm in the simulation environment of Gazebo, and then control the virtual robot arm in Gazebo through Moveit2. This package is introduced in detail in the following aspects.
- 1.Package use.
- 2.Package architecture description. Through the introduction of this part, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
Source code address: https://github.com/RealManRobot/ros2_rm_robot.git。
rm_gazebo_Package_Running
Control_of_the_simulation_robotic_arm
After the installation of the environment and the package, we can run the rm_gazebo package.
The unified entry is the recommended way to launch the Gazebo world and robot:
rm@rm-desktop:~$ ros2 launch rm_gazebo rm_gazebo.launch.py arm_type:=65-6fb
The unified entry accepts:
-
arm_type: required; selects the model and end-link version, e.g.65,65-6fb, orrx75-6fb-v. Bare families select the standard version. See the supported selections. -
model: defaults toauto, preferring colored DAE when available and otherwise using STL.model:=stlselects original STL;model:=daerequires DAE. Legacy entries also accept this argument.
This branch retains Gazebo Fortress. Gazebo and the accompanying MoveIt RViz2 use the same visuals; existing joint, collision and control settings are retained.
-
start_gazebo: defaulttrue. Set it tofalseonly to reuse an already running Gazebo world namedempty. This skips the Gazebo process itself, but robot spawning, the/world/empty/clockbridge, and controller spawning still run. If the external world is absent or entity creation times out, launch returns a non-zero status and does not attempt to start the controllers. -
joint_states_topic: onlyautois currently supported. It resolves to/joint_statesfor normal arms and/joint_state_broadcaster/joint_statesfor RX75. -
use_sim_time: controls simulation time forrobot_state_publisher, defaulttrue.
The catalog covers 10 robot models and 21 supported model/variant combinations. All 21 legacy gazebo_*_demo.launch.py entries remain available with their original arguments and defaults. For example:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_65_demo.launch.py
Press Ctrl+C to stop the simulation. The launcher forwards the signal to the Gazebo server, GUI, and ros2_control, waits for resource cleanup, and records this user-requested shutdown as a clean exit. Qt/QML compatibility warnings are suppressed only inside the Gazebo child process; Gazebo and ROS warnings and errors remain visible.
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6f_demo.launch.py
The command to start the integrated six-axis force version is currently available for 63, 63_III, 65, 75, eco63, eco65, and rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_demo.launch.py
The command to start the vision-enabled integrated six-axis force version is currently only available for rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_v_demo.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_<arm_type>_config gazebo_moveit_demo.launch.py
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
```
rm@rm-desktop:~$ ros2 launch rm_
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_gazebo at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | BSD |
| 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
Additional Links
Maintainers
- Kaola
Authors
- Kaola
Launch examples
After building and sourcing the workspace, simulate an RM65 with integrated force sensing in Gazebo:
# Simulation (generation 3 and 4 both retain the 6fb model name)
ros2 launch rm_gazebo rm_gazebo.launch.py \
arm_type:=65-6fb
This package starts Gazebo simulation, which does not connect to a controller or depend on its software version. Generation 4 software 1.0.6 and later names the former 6fb end link 6f; keep 65-6fb when simulating the same geometry. See the generation-specific model table.
Content
- 1.rm_gazebo Package Description
- 2.rm_gazebo Package Running
- 2.1Control of the simulation robotic arm
- 3.rm_gazebo Package Architecture Description
- 3.1Overview of Package Files
rm_gazebo_Package_Description
rm_gazebo is mainly used for realizing the simulation function of robot arm Moveit2 planning. We build a virtual robotic arm in the simulation environment of Gazebo, and then control the virtual robot arm in Gazebo through Moveit2. This package is introduced in detail in the following aspects.
- 1.Package use.
- 2.Package architecture description. Through the introduction of this part, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
Source code address: https://github.com/RealManRobot/ros2_rm_robot.git。
rm_gazebo_Package_Running
Control_of_the_simulation_robotic_arm
After the installation of the environment and the package, we can run the rm_gazebo package.
The unified entry is the recommended way to launch the Gazebo world and robot:
rm@rm-desktop:~$ ros2 launch rm_gazebo rm_gazebo.launch.py arm_type:=65-6fb
The unified entry accepts:
-
arm_type: required; selects the model and end-link version, e.g.65,65-6fb, orrx75-6fb-v. Bare families select the standard version. See the supported selections. -
model: defaults toauto, preferring colored DAE when available and otherwise using STL.model:=stlselects original STL;model:=daerequires DAE. Legacy entries also accept this argument.
This branch retains Gazebo Fortress. Gazebo and the accompanying MoveIt RViz2 use the same visuals; existing joint, collision and control settings are retained.
-
start_gazebo: defaulttrue. Set it tofalseonly to reuse an already running Gazebo world namedempty. This skips the Gazebo process itself, but robot spawning, the/world/empty/clockbridge, and controller spawning still run. If the external world is absent or entity creation times out, launch returns a non-zero status and does not attempt to start the controllers. -
joint_states_topic: onlyautois currently supported. It resolves to/joint_statesfor normal arms and/joint_state_broadcaster/joint_statesfor RX75. -
use_sim_time: controls simulation time forrobot_state_publisher, defaulttrue.
The catalog covers 10 robot models and 21 supported model/variant combinations. All 21 legacy gazebo_*_demo.launch.py entries remain available with their original arguments and defaults. For example:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_65_demo.launch.py
Press Ctrl+C to stop the simulation. The launcher forwards the signal to the Gazebo server, GUI, and ros2_control, waits for resource cleanup, and records this user-requested shutdown as a clean exit. Qt/QML compatibility warnings are suppressed only inside the Gazebo child process; Gazebo and ROS warnings and errors remain visible.
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6f_demo.launch.py
The command to start the integrated six-axis force version is currently available for 63, 63_III, 65, 75, eco63, eco65, and rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_demo.launch.py
The command to start the vision-enabled integrated six-axis force version is currently only available for rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_v_demo.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_<arm_type>_config gazebo_moveit_demo.launch.py
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
```
rm@rm-desktop:~$ ros2 launch rm_
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_gazebo at Robotics Stack Exchange
Package Summary
| Version | 1.7.1 |
| License | BSD |
| 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
Additional Links
Maintainers
- Kaola
Authors
- Kaola
Launch examples
After building and sourcing the workspace, simulate an RM65 with integrated force sensing in Gazebo:
# Simulation (generation 3 and 4 both retain the 6fb model name)
ros2 launch rm_gazebo rm_gazebo.launch.py \
arm_type:=65-6fb
This package starts Gazebo simulation, which does not connect to a controller or depend on its software version. Generation 4 software 1.0.6 and later names the former 6fb end link 6f; keep 65-6fb when simulating the same geometry. See the generation-specific model table.
Content
- 1.rm_gazebo Package Description
- 2.rm_gazebo Package Running
- 2.1Control of the simulation robotic arm
- 3.rm_gazebo Package Architecture Description
- 3.1Overview of Package Files
rm_gazebo_Package_Description
rm_gazebo is mainly used for realizing the simulation function of robot arm Moveit2 planning. We build a virtual robotic arm in the simulation environment of Gazebo, and then control the virtual robot arm in Gazebo through Moveit2. This package is introduced in detail in the following aspects.
- 1.Package use.
- 2.Package architecture description. Through the introduction of this part, it can help you:
- 1.Understand the package use.
- 2.Familiar with the file structure and function of the package.
Source code address: https://github.com/RealManRobot/ros2_rm_robot.git。
rm_gazebo_Package_Running
Control_of_the_simulation_robotic_arm
After the installation of the environment and the package, we can run the rm_gazebo package.
The unified entry is the recommended way to launch the Gazebo world and robot:
rm@rm-desktop:~$ ros2 launch rm_gazebo rm_gazebo.launch.py arm_type:=65-6fb
The unified entry accepts:
-
arm_type: required; selects the model and end-link version, e.g.65,65-6fb, orrx75-6fb-v. Bare families select the standard version. See the supported selections. -
model: defaults toauto, preferring colored DAE when available and otherwise using STL.model:=stlselects original STL;model:=daerequires DAE. Legacy entries also accept this argument.
This branch retains Gazebo Fortress. Gazebo and the accompanying MoveIt RViz2 use the same visuals; existing joint, collision and control settings are retained.
-
start_gazebo: defaulttrue. Set it tofalseonly to reuse an already running Gazebo world namedempty. This skips the Gazebo process itself, but robot spawning, the/world/empty/clockbridge, and controller spawning still run. If the external world is absent or entity creation times out, launch returns a non-zero status and does not attempt to start the controllers. -
joint_states_topic: onlyautois currently supported. It resolves to/joint_statesfor normal arms and/joint_state_broadcaster/joint_statesfor RX75. -
use_sim_time: controls simulation time forrobot_state_publisher, defaulttrue.
The catalog covers 10 robot models and 21 supported model/variant combinations. All 21 legacy gazebo_*_demo.launch.py entries remain available with their original arguments and defaults. For example:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_65_demo.launch.py
Press Ctrl+C to stop the simulation. The launcher forwards the signal to the Gazebo server, GUI, and ros2_control, waits for resource cleanup, and records this user-requested shutdown as a clean exit. Qt/QML compatibility warnings are suppressed only inside the Gazebo child process; Gazebo and ROS warnings and errors remain visible.
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6f_demo.launch.py
The command to start the integrated six-axis force version is currently available for 63, 63_III, 65, 75, eco63, eco65, and rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_demo.launch.py
The command to start the vision-enabled integrated six-axis force version is currently only available for rx75:
rm@rm-desktop:~$ ros2 launch rm_gazebo gazebo_<arm_type>_6fb_v_demo.launch.py
In practice, the above
rm@rm-desktop:~$ ros2 launch rm_<arm_type>_config gazebo_moveit_demo.launch.py
The command to start the six-axis force version is currently available for 63, 65, 75, and eco65:
```
rm@rm-desktop:~$ ros2 launch rm_
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| rm_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged rm_gazebo at Robotics Stack Exchange
|
rm_gazebo 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
Maintainers
- Qiayuan Liao
Authors
- Qiayuan Liao
Package Name
Overview
This is a template: replace, remove, and add where required. Describe here what this package does and what it’s meant for in a few sentences.
Keywords: example, package, template
Or, add some keywords to the Bitbucket or GitHub repository.
License
The source code is released under a BSD 3-Clause license.
Author: Péter Fankhauser
Affiliation: ANYbotics
Maintainer: Péter Fankhauser, pfankhauser@anybotics.com
The PACKAGE NAME package has been tested under [ROS] Indigo, Melodic and Noetic on respectively Ubuntu 14.04, 18.04 and 20.04. This is research code, expect that it changes often and any fitness for a particular purpose is disclaimed.

Installation
Installation from Packages
To install all packages from the this repository as Debian packages use
sudo apt-get install ros-noetic-...
Or better, use rosdep:
sudo rosdep install --from-paths src
Building from Source
Dependencies
- Robot Operating System (ROS) (middleware for robotics),
-
roboticsgroup_upatras_gazebo_plugins
sudo rosdep install –from-paths src
Building
To build from source, clone the latest version from this repository into your catkin workspace and compile the package using
cd catkin_workspace/src
git clone https://github.com/ethz-asl/ros_best_practices.git
cd ../
rosdep install --from-paths . --ignore-src
catkin_make
Unit Tests
Run the unit tests with
catkin_make run_tests_ros_package_template
Static code analysis
Run the static code analysis with
catkin_make roslint_ros_package_template
Usage
Describe the quickest way to run this software, for example:
Run the main node with
roslaunch ros_package_template ros_package_template.launch
Config files
Config file folder/set 1
- config_file_1.yaml Shortly explain the content of this config file
Config file folder/set 2
- …
Launch files
-
launch_file_1.launch: shortly explain what is launched (e.g standard simulation, simulation with gdb,…)
Argument set 1
-
argument_1Short description (e.g. as commented in launch file). Default:default_value.
Argument set 2
...
-
File truncated at 100 lines see the full file
Changelog for package rm_gazebo
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
- Merge pull request #1 from rm-controls/master 1
- 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 dev/polygon_ui
- Merge pull request #107 from chenhuiYu00/gazebo_imu_reserve Fix imu problem in gazebo simulation.
- Use list instead of vector.
- Merge branch 'master' into gazebo_imu_reserve
- Pre-allocate imu vector memory.
- Merge pull request #106 from YoujianWu/work Delete dependence roslint.
- Run pre-commit.
- Delete dependence roslint.
- 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: Kook, ye-luo-xi-tui, yezi, yuchen
0.1.17 (2023-02-21)
- Merge pull request #99 from ye-luo-xi-tui/master Fix bug
- Fix bug.
- Add gravity.
- Merge branch 'rm-controls:master' into master
- Merge pull request #84 from ye-luo-xi-tui/master 0.1.16
- Merge branch 'rm-controls:master' into master
- Contributors: ye-luo-xi-tui, yezi, 吕骏骐
0.1.16 (2022-11-24)
- Merge branch 'master' into new_ui_test
- Merge branch 'master' into dev/command_sender
- Merge pull request #79 from ye-luo-xi-tui/rm_imu_handle Add RmImuSensorInterface and add a service to enable or disable imus in rm_gazebo
- Add RmImuSensorInterface.
- Add a service to enable or disable imus.
- 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
File truncated at 100 lines see the full file
Package Dependencies
| Deps | Name |
|---|---|
| catkin | |
| rm_description | |
| roboticsgroup_upatras_gazebo_plugins | |
| roscpp | |
| rm_common | |
| gazebo_ros | |
| gazebo_ros_control |
System Dependencies
| Name |
|---|
| gazebo |
Dependant Packages
Launch files
- launch/big_resource.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer,sentry]
- load_chassis [default: true]
- load_gimbal [default: false]
- load_shooter [default: false]
- load_arm [default: true]
- paused [default: false]
- roller_type [default: simple] — simple or realistic
- launch/empty_world.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer,sentry,rmua]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- roller_type [default: simple] — simple or realistic
- launch/exchange_station.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.0]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/rmuc.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.0]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/rmul2026.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.7]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/sentry_world.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: -0.06]
- z_pos [default: 0.06]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/series_legged_world.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.0]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/slope.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.0]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/small_resource.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.0]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/step.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.0]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/step_down.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.0]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/stone.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.0]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- launch/vmc_test.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer,sentry,rmua]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]
- roller_type [default: simple] — simple or realistic
- launch/warthog_race_world.launch
-
- robot_type [default: $(env ROBOT_TYPE)] — Robot type [standard, auto, hero, engineer]
- x_pos [default: 0.0]
- y_pos [default: 0.0]
- z_pos [default: 0.0]
- load_chassis [default: true]
- load_gimbal [default: true]
- load_shooter [default: true]
- load_arm [default: true]
- paused [default: false]