Skip to main content

Architecture

This page covers only what you need for integration: what runs where, how a command reaches the drives, and what is optional.

One robot​

ComponentWhat it doesFor integration
ros2_control_node (one process per robot)Runs controller_manager, the hardware interface and the PLEM real-time threads in one processRequired. Most control and status interfaces come from here
robot_state_publisherPublishes the URDF as TFRequired
move_group + plan_trajectory_serverPasses plem/plan_trajectory requests to MoveIt planningOptional
Gripper driverProvides gripper_action_server/gripper_commandWhen a gripper is fitted
Cameras, nvblox and other perception nodesSee the real cell and avoid what is in itOptional
plem-server + rosbridgeConnects the Teaching Pendant and Plem Lab web UIsNot needed for ROS 2 integration, but launched by default
plem-telemetry (registered devices)Collects operation records. What it collects and how to turn it off: LicensesNot needed

With several robots, each robot gets its own process and namespace, so its control and status interfaces are separate too. Robots start one after another, 1 s apart. The web UI connection starts once, under the first robot.

The MoveIt IK solver is pick_ik on ROS 2 Humble devices and TRAC-IK on Jazzy devices.

How a command reaches the drives​

The rates in the diagram come from the controller configuration and the hardware interface.

  • A trajectory travels as one goal and is sampled every cycle inside the device. The client does not need to send commands at the control rate.
  • The network affects only goal delivery, acceptance, start and cancel. Once a goal is accepted, its execution timing does not depend on the network.
  • The controller_manager rate is separate from the real-time bus rate. Leave it as it is when you raise the bus rate.
  • The torque and EtherCAT threads try to get real-time scheduling. If they cannot, they keep running best-effort.

What is optional​

Motion control needs only the standard follow_joint_trajectory action and plem/set_mode. Add the rest only when you need it.

You want toYou need
Run trajectories, use the gripperThe base setup
Plan to a target pose or a straight line, then run itMoveIt (plem/plan_trajectory)
Avoid self-collisionMoveIt + cuMotion. ROS 2 Humble (JetPack 6) devices and supported models only (Launching the stack)
Avoid real objects in the cellAll of the above + cameras and the perception stack + calibration

Collision avoidance (COLLISION_AWARE) and a straight-line move (MOVEL_LIN) cannot be requested together. When the perception stack starts and when it falls back to cameras only is in Launching the stack.