Glossary
Terms that come up across these docs, with links to the pages that explain them in full.
Platform
PLEM: the platform these docs describe (Overview). Its full name is "PLEM Robot Control Platform". The command on the device is lowercase plem.
Everyday terms
Stack: the robot control programs plem launches. Press s in Robot Control to start or stop it.
Profile: one robot's hardware configuration: model, serial number, gripper, F/T sensor, camera. Model and serial number are preset to the delivered configuration.
Launch: bringing the stack up. What comes up when: Launching the stack.
Robot state
Robot mode: what the robot can do right now. The TUI and the Teaching Pendant show it with short labels.
| Mode | TUI | Pendant | Meaning |
|---|---|---|---|
| BRAKED | BRAKE | BRAKED | Brakes engaged |
| TRAJECTORY | TRAJ | TRAJ | Brakes released, follows trajectories |
| FREEDRIVE | FREE | FREE | Brakes released, you guide the arm by hand |
| STOPPING | STOP | STOPPING... | Decelerating during a mode change. You cannot request it |
| ERROR | ERR | A value reserved in the message definition. PLEM does not publish it |
Safety mode: NORMAL or PROTECTIVE_. It is a separate axis from the robot mode and takes priority over it.
Protective Stop (P-STOP): a stop the stack triggers by itself. The brakes engage and it does not clear on its own. See Stops and safety.
Emergency Stop (E-Stop): the physical stop button. PLEM cannot read it. If the button stops a running axis, the stack enters a Protective Stop, which you clear after releasing the button (Stops and recovery).
Freedrive: a mode in which you move the robot by hand. PLEM compensates for gravity and Coriolis forces and does not hold a position.
TCP (Tool Center Point): the point where the robot does its work. With a gripper or tool attached, it is the tip of that tool.
Measured kinematics: kinematic values measured for one robot unit. A registered robot is checked at launch and then uses these values in place of the model's nominal ones; if the check fails, the launch stops. Supported models: Supported hardware.
F/T sensor: a sensor on the tool that measures force and torque. Values are in the sensor frame <robot name>_, without gravity compensation. See F/T sensor.
Communication and control
EtherCAT: the industrial real-time network between the controller and the robot's joint drives. PLEM uses one EtherCAT master per robot.
Control period: how often torque is computed and sent to the drives. The default is 1 kHz.
ADRC: the default torque controller. An observer estimates disturbances and compensates for them, and the external force overload guard uses that estimate.
Torque controller plugin: a control law you write and load yourself. See Custom torque controller.
CycloneDDS: the ROS 2 middleware (RMW) PLEM uses. By default it is open only inside the device. See ROS 2 interfaces.
Servo drive bus, plem drive, approval: running EtherCAT servo drives directly, without a robot arm, and the tool for it. plem drive and plem-drive are the same tool. A drive that passes the bench gets an approval record (approval block) inside its model file. See Servo drives.
Axis, stream axis (drive bus): an axis is one CiA 402 axis in a drive model file and shows up in ROS as a joint of the same name. Velocity (csv) and torque (cst) axes take a command every cycle, so they are called stream axes. Position (csp) axes move along trajectories. See Bus API.
Release (drive bus): releasing the brakes and putting every axis in Operation enabled. It is the service field release_ and Python release().
Planning and perception
MoveIt: the robot motion planning framework. PLEM's planning requests run on it.
cuMotion: a GPU-accelerated planner that plans paths around collisions.
ESDF (environment map): a map of the surrounding space built from the camera. Avoiding real objects in the cell needs it.
Hand-eye calibration, current value: measuring where and how the camera is mounted relative to the robot's tool. The "Current value" card on the Teaching Pendant shows the value the robot uses now. See Hand-eye calibration.
Running programs
Waypoint: a saved, named joint pose. Move nodes refer to it by a fixed ID (waypoint_), so renaming it keeps the link. See Motion.
Job, deployment: a program sent to the robot to run (the server calls it a deployment). The Pendant shows only "Job". ▶ validates, creates the Job and starts it. See Run.
Checkpoint: where a Job stopped by a Protective Stop resumes. The robot must be close enough to the resume pose. See Run.
Lane (motion, auxiliary): a branch that runs at the same time as others inside a parallel block. Nodes that move the robot can go only in the one motion lane. See Nodes.
Variable: a value that belongs to a robot, not to a program. It keeps its value after a run ends. See Nodes.
Software
Namespace: the ROS 2 namespace each robot gets. It is the robot ID.
Overlay: the standard ROS 2 way to put your own workspace on top of the base install (/opt/). Controllers you build are found this way.
Teaching Pendant, Plem Lab: the two browser tools. The Pendant is for building and running programs; Lab is for controller tuning and signal monitoring.
plem code (beta): an interactive assistant you run with plem code in a terminal on the device.
Telemetry agent: a program that runs with the robot stack on a registered device and sends robot operation records. What it collects and how to turn it off: Licenses.
Docs version: v0.11.1 (2026-11-11)