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
| Component | What it does | For integration |
|---|---|---|
ros2_ (one process per robot) | Runs controller_manager, the hardware interface and the PLEM real-time threads in one process | Required. Most control and status interfaces come from here |
robot_ | Publishes the URDF as TF | Required |
move_ + plan_ | Passes plem/ requests to MoveIt planning | Optional |
| Gripper driver | Provides gripper_ | When a gripper is fitted |
| Cameras, nvblox and other perception nodes | See the real cell and avoid what is in it | Optional |
plem-server + rosbridge | Connects the Teaching Pendant and Plem Lab web UIs | Not 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: Licenses | Not 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_ action and plem/. Add the rest only when you need it.
| You want to | You need |
|---|---|
| Run trajectories, use the gripper | The base setup |
| Plan to a target pose or a straight line, then run it | MoveIt (plem/) |
| Avoid self-collision | MoveIt + cuMotion. ROS 2 Humble (JetPack 6) devices and supported models only (Launching the stack) |
| Avoid real objects in the cell | All of the above + cameras and the perception stack + calibration |
Collision avoidance (COLLISION_) and a straight-line move (MOVEL_) cannot be requested together. When the perception stack starts and when it falls back to cameras only is in Launching the stack.