Skip to main content

ROS 2 integration

In the Apex architecture, the robot's onboard controller runs the ROS 2 nodes for robot control, teleoperation, cameras, and recording: a Tianzhun or Lingjing Thor controller on current robots, or an Orin on earlier ones. Apex Teleop on the host PC manages the connection and the operator workflow.

Interface references​

Robot or deviceReference
Marvin ProMarvin Pro ROS 2 interfaces: namespace, safety rules, input arbitration, topics, services, network ports, and topic rates
Skye and LunaSkye and Luna ROS 2 interfaces: joint differences, whole-body commands, services, and the mobile base
Head and wrist camerasCamera ROS topics
RealSense camerasRealSense cameras (ROS 2)
Topics allowed for recording and forwardingTopic whitelist

Confirm topic names, message types, units, frames, and update behavior on your installed release before writing a client. The output of ros2 topic list -t on the robot is authoritative.

Load the Apex ROS 2 environment​

Log in to the robot's controller (see Connect to the Orin or Thor) and load the environment in every new terminal:

source /etc/apex/apex_ros_env.sh

On Marvin Pro, Apex nodes run in the tj namespace by default, so core interfaces are under /tj/.... Applications written for the older /control/... and /info/... paths need updating.

Keep interfaces distinct​

InterfaceRole
Marvin motion SDKCommunication with the robot controller
Apex ROS 2 interfacesRobot-side application integration and telemetry
Apex desktop applicationOperator connection, mode selection, and recording

ROS 2 integration does not imply that every SDK function is exposed as a topic or service. Do not assume Luna/Skye message definitions or controller settings apply to Marvin Pro.

Before sending commands​

Confirm which process owns robot control, how control is handed over, and which coordinate frame and units the command uses. Read the safety requirements and input arbitration rules in the interface reference for your robot, and Operation modes and input sources.