Packages and ROS API
robomaster_ros2 contains the hardware server, parameter server, network
helpers and device drivers. robomaster_interface defines their custom
messages and services. robomaster_examples supplies waypoint/trajectory
examples, fleet diagnostics and joystick control. Simulation is documented
separately in Simulation.
Namespaces and availability
The server uses root fleet services. Each device node is created in its own
namespace: a device named rmtt_1 has node name /rmtt_1/rmtt_1 and topics
such as /rmtt_1/image. Replace <name> below with the configured name.
Sensor flags and detected model capabilities control endpoint creation; not
every robot provides every endpoint.
Server services
Endpoint |
Service type |
Behavior |
|---|---|---|
|
AddDrone |
Register an RMTT with address, camera and optional external-pose settings. |
|
RemoveRobot |
Remove an RMTT by name and type |
|
AddRobot |
Advertised, but the current handler is unimplemented. |
|
Trigger |
Created only while at least one drone is registered. |
Custom service names refer to robomaster_interface/srv. Trigger,
Empty and SetBool refer to std_srvs/srv.
Drone services
Relative endpoint |
Type |
Behavior |
|---|---|---|
|
Trigger |
Serial number, battery percentage and flight state. |
|
SetSpeed |
Set SDK movement speed; this does not change the normalized cmd_vel interface. |
|
Takeoff |
Height in metres and a sync flag. |
|
Trigger |
Landing or emergency landing. |
|
Empty |
Stop RC commands, stop motors, or reboot. |
|
SetBool |
Control the flight motion gate. |
|
TelloLED / TelloMled |
External-module RGB and matrix LEDs. |
|
Move / GoTo |
May be advertised with external positioning, but callbacks are unimplemented. |
Ground robot services
Relative endpoint |
Type |
Availability / behavior |
|---|---|---|
|
Trigger |
EP/Core/S1 identity and DDS-cached battery percentage. |
|
SetBool |
Control chassis/gimbal motion gate; does not guard the current arm stream. |
|
MoveChassis |
Tracked chassis movement. |
|
Empty |
Close the device connection. |
|
RobotLED |
Chassis armor LEDs. |
|
SetArmorSensitivity |
Available when armor support is enabled. |
|
MoveGimbal / Trigger |
Models with a gimbal. |
|
GimbalLED / BlasterLED / Fire |
Models with a gimbal/blaster. |
|
MoveArm |
EP Core relative/absolute arm actions with optional completion wait. |
|
Trigger |
EP Core tracked-action lifecycle. |
|
Gripper |
EP Core percentage command, accepted asynchronously. |
|
GripperCommand / SetGripperMode |
EP Core named operations and timed/feedback control. |
Topics and units
The endpoint is /<name>/<topic> unless stated otherwise. Standard message
names below come from geometry_msgs/msg or sensor_msgs/msg; named
RoboMaster messages come from robomaster_interface/msg.
Device / topic |
Message |
Direction / semantics |
|---|---|---|
Both: |
sensor_msgs/Image |
Published raw bgr8 frames; best-effort, volatile, depth 1. |
Drone: |
Twist |
Subscribed normalized RC inputs in [-1, 1]; not m/s or rad/s. |
Drone: |
Range |
Enabled distance sensors. |
Drone: |
QuaternionStamped |
Enabled attitude telemetry. |
Drone: |
FluidPressure / Imu / TelloMpad |
Optional telemetry; barometer/IMU unit handling remains incomplete. |
Drone: |
Pose |
Republished external-pose input when enabled. |
Ground: |
Twist |
Subscribed chassis translation in m/s and yaw in rad/s. |
Ground: |
PoseStamped |
DDS position with quaternion orientation from chassis attitude. |
Gimbal: |
GimbalVel |
Subscribed pitch/yaw speed in degrees/second. |
Gimbal: |
GimbalAngle |
Enabled angle feedback. |
EP Core: |
Twist |
Subscribed X/Z stream velocities in m/s; independent of the motion gate. |
EP Core: |
PointStamped |
Enabled legacy arm DDS feedback; service command units must not be inferred from this topic. |
EP Core: |
ArmActionStatus |
Tracked service action ID, state, progress and completion. |
EP Core: |
GripperState |
Hardware endpoint status plus estimated percentage, mode and operation state. |
Armor: |
ArmorHit / IrHit |
Event topics; silence can be normal. |
External pose subscriptions use the configured ext_pose_topic_name and
ext_pose_topic_type. There is no fixed external_position input topic.
The real driver does not create a positioning system from these settings.
Camera publication is direct; the driver creates no compressed image topic or camera bridge. Most other topics use reliable QoS. Arm velocity uses depth 20 and gimbal velocity depth 60. See Using the hardware driver for lifecycle/units and Fleet diagnostics and joystick control for current example limitations.