Skip to main content

Robot Control

Press Start on Start session and this screen opens. Press s to launch the stack. When the launch finishes, the screen fills in as below.

Robot Control with the stack running. The header reads plem / Session · 1 robot with the EtherCAT master count and domain. ROBOTS at the top left holds ballet_1 with ● TRAJ indy7_v3 below it, JOINT MOVE sits under it, LOG · ballet_1 in the middle shows a GRIP rg6 chip and the launch log, and SYSTEM on the right shows EtherCAT eth0, slave dots 7/7, WKC, TRAJ, NORMAL, CPU, Memory, Domain, Controller and Workspace with WEB · ballet-1.local listing Pendant :8080/web and Lab :8080/lab. The state line reads Running · 1 robot and ballet_1: Ready to move, above the key bar.

AreaWhat it shows
HeaderScreen name (Session · N robots), EtherCAT master count, ROS domain and installed version. ↑0.x.y next to the version means a newer version exists (Update)
ROBOTS (top left)The launched robots, two lines each: the name, then the link dot, mode and model
JOINT MOVE (bottom left)Joint targets and moving to saved poses
LOG (middle)Gripper and F/T sensor chips, the stack log and robot events
SYSTEM (right)EtherCAT, mode, safety state, slaves, CPU and memory, ROS domain, controller, workspace, web addresses
State line (first line at the bottom)One sentence on what is true now (below)
Key bar (last line)The keys you can press now. Only the key letter is coloured

The state line reads one of these.

  • Not running — press s to start: the stack is off.
  • Green ● Running · N robots, followed by the selected robot's mode in words: Brakes on · Ready to move · FreeDrive · move by hand · Stopping · Error, in the same colour as the robot list.
  • While stopping: an orange spinner and the current step (Stopping the stack).
  • Bold red ■ P-STOP on <robot>: a Protective Stop.
  • Bold red ✖ EtherCAT link down · <robot>: the selected robot lost its link. When another robot's bus goes down, that robot shows P-STOP.

When the window is narrower than 130 columns, the SYSTEM pane folds away. The Protective Stop and link-down sentences still appear on the state line.

SYSTEM​

] shows or hides this pane. On a narrow window it starts folded, so open it with ].

RowShowsMeaning
EtherCATeth0 / red ✖ eth0The bus interface. A red ✖ means the link is down
Slaves● ● ● ● ● ● ● 7/7One dot per EtherCAT device on the selected robot's master, servo drives and other devices alike. Green = running (OP), orange = starting, red = link down or error. The numbers are running/total
WKC7/7 green / redEtherCAT working counter (current/expected). It need not equal the device count. Red means some devices missed this cycle
ModeTRAJ green · FREE orange · BRAKE grey · STOP orange · ERR redThe selected robot's mode: Trajectory · Freedrive · brake · stopping · error
SafetyNORMAL green / P-STOP redProtective Stop or not. On red, see Stops and recovery
CPU · Memory42% · 5.1 / 16 GB (32%)Device load, refreshed every 3 seconds
Domain42 / red 0 · sharedThe ROS domain applied to this plem run. Red means none is set and the default 0 is in use. A value changed in Settings shows here only after plem is run again
ControllerADRC · PID · Plugin <file>The selected robot's torque controller
Workspaceunset · ~/ws ✓ · ~/ws !build · ~/ws !missingThe registered user workspace and whether it is built
WEB · <device address>Pendant :8080/web · Lab :8080/labThe web tools to open from another computer's browser while the stack runs. A tool turned off in Start session is not listed

Robot list​

Each robot takes two lines: its name in bold, then ● <mode> <model>. The model is the robot model in its profile.

  • A green ● means ROS 2 is connected. A grey ○ means not yet.
  • During a Protective Stop the mode reads red P-STOP. In the recovery Freedrive it reads FREE P-STOP: the brakes are open and the arm moves by hand.
  • With several robots, ← moves focus to the list and → to the log. The robot you select is the target of joint moves and the log.
  • [ hides or shows the whole left column.

Brake and Freedrive​

r releases the brake into Trajectory (TRAJ), and from any other mode it brakes. f switches between brake and Freedrive (FREE), where you move the arm by hand. The key bar names what each key will do next, for example release brake or end freedrive.

caution
r while the robot moves

r during motion requests the brake, and the robot can stop abruptly. Do not treat the robot as stopped until the robot row and SYSTEM Mode show BRAKE (state line Brakes on).

f enters Freedrive only from the brake.

  • From Trajectory it only brakes first and shows Braking first. Press f again after BRAKED to enter FreeDrive. Press f again once braked.
  • Before launch it shows Press s to launch first.
  • While connecting it shows ROS2 connecting — try again in a moment.

After a switch is accepted, the TUI checks the hardware state again. If one of these lines appears in the log, follow Stops and recovery.

  • During a Protective Stop: mode change acknowledged but PROTECTIVE_STOP is active — motion will be blocked by hardware.
  • A joint outside its design range: … joints beyond URDF design range … Press [R] to attempt FreeDrive recovery.
Before the robot moves

Releasing the brake with r lets the robot take commands. Make sure no people or objects are in its reach, and stay within reach of the Emergency Stop. No key on this screen replaces the physical Emergency Stop.

Joint move​

In JOINT MOVE at the bottom left you type joint targets or move to a saved pose. It works only when the stack was launched with Motion planning, and the robot moves only in Trajectory (TRAJ).

ROBOTS above (ballet_1 with ● TRAJ indy7_v3 below it) and the joint move pane below. Two columns, current and target, list the current angles of J0–J5 and empty target fields. Below them POSES add delete and four poses: zero pos, packaging pos, jog left pos, jog right pos. Reset and Move sit at the bottom right.

Saved poses are the poses list in ~/.plem/settings.yaml. On the first run four default poses are written there; after that the file is used as it is, so you can add or delete here or edit the file. If you delete them all, the list stays empty and the defaults do not come back.

Typing targets​

  1. Type target angles in degrees in the target column. A blank joint keeps its current position.
  2. Press Move, or Enter in a field. Reset clears the inputs.
  3. The result appears on the line just above Reset and Move. On success the inputs clear; on failure they stay.
A successful Move means accepted, not arrived

Success means the planner accepted the command.

  • This pane does not show progress or completion, and there is no cancel. Watch the current column reach the target and stop.
  • Other controls are not blocked once the command is accepted. Until you see the robot stop, do not start anything else that moves it: a Pendant run, a jog, a calibration.

A value that is not a number turns red, and not a number appears below. A value outside the joint limit shows the allowed range. The move goes to the target in one motion, so a large angle change makes a large motion. Clear the reach first.

Keys inside a target field

Target fields take only digits, a sign and a decimal point. Every other key acts as a screen key even with the cursor in a field: r brakes, s stops, q quits, a and d add and delete poses.

Poses​

ActionWhat it does
↑ ↓ on the listPreviews that pose's values in the target fields. If you typed values yourself, they are kept and edits kept — enter loads '…' appears
Enter or click on the listFills the target fields with that pose. Asks before overwriting only if you typed values yourself. The robot moves only when you press Move
aSaves the target values as a new pose. Every joint must be filled
dDeletes the highlighted pose, after confirmation

The four default poses are for 6-axis robots whose joints are named joint0–joint5, which covers every supported model. The screen shows them as J0–J5.

PoseJ0J1J2J3J4J5
zero pos000000
packaging pos001580−1580
jog left pos−20−40−110−20400
jog right pos204011020−400

When the pane is unavailable, it says why and hides Reset and Move.

  • Available once the robot is running.
  • waiting for ROS2 connection
  • MoveIt disabled for this launch
  • waiting for joints / URDF
  • URDF arm chain unresolved — Joint Move disabled (see log)

Log​

The LOG pane mixes two streams.

  • The output of the launched stack, always shown.
  • Robot events (link, mode, safety, limits), for the selected robot only.

The screen keeps the last 1000 lines, and the log is also written to files under ~/.plem/log/. Where to find them is in Troubleshooting › Asking for support.

PrefixMeaning
[RT]A real-time control loop event (PROTECTIVE_STOP, BRAKE_ENGAGE, PROTECTIVE_FLOOR_VIOLATION and others), with severity= INFO · WARN · ERROR · CRITICAL. Repeats of the same event within 5 seconds are folded, and their count follows as (xN more in 5s)
[SAFETY]A safety state change, for example [SAFETY] NORMAL → PROTECTIVE_STOP
[LIMIT]A joint left or came back inside its design range
[RECOVER]Progress of an R recovery
[CRASH]A stack process ended unexpectedly
[ERROR]A stack management error: a failed pre-launch check (no EtherCAT slave found, for example), a process that failed to start, an abnormal exit
[measured]The kinematics applied to the robot at launch: geometry: measured record applied (measured <date>) or geometry: model nominal (<model>). rejected: means the measured values failed validation and the launch stopped (Stops and recovery)
  • Drag with the mouse to copy the selected lines to the clipboard of the screen you are looking at (Copying log lines).
  • While scrolled up, new lines do not pull the view down. Enter jumps back to the latest line.
  • l cycles the log detail through info → debug → warn → err. It is saved and applies from the next launch.

Copying log lines​

Over SSH, the selection is sent to your laptop's terminal (OSC 52). Whether it arrives depends on the terminal.

TerminalReceives the copy
Windows Terminal · VS Code · WezTerm · kittyYes
iTerm2Once clipboard access is allowed
GNOME TerminalNo. Connect with ssh -X instead
tmux 3.3 or later, on the device or the laptopOnly with set -g set-clipboard on in that tmux's ~/.tmux.conf

After a copy the TUI says how it went: Copied to clipboard when a clipboard tool (xclip or similar) took it, Sent to the terminal clipboard (needs a terminal with OSC 52) when it was only sent to the terminal.

Gripper and F/T chips​

A robot with a gripper set shows a GRIP <model> chip above the log. A robot with an F/T sensor set shows an F/T <model> chip on its own line below. The gripper chip adds the position (pos=…mm) and force (eff=…) after the state.

ChipShowsMeaning
GRIP○ idleIdle, nothing held
GRIP● gripHolding an object
GRIP⋯ busyMoving
GRIP✗ ERRORGripper error
GRIP· waiting for /gripper_statusNo state received yet
GRIP✗ not answeringThe gripper does not answer. Check the cable and tool power. The chip recovers by itself once the gripper answers again
F/T● ok |F|=… |T|=… load=…%Normal: force and torque magnitude, and load against the rating
F/Tyellow ▲ <sentence> · red ✗ <sentence>Warning · error, with the sensor's own status sentence
F/T· no signalNo signal yet

Reading F/T values is covered in F/T sensor.

Robot Control for a robot with a gripper and an F/T sensor. Above the log is the chip GRIP rg6 ✗ not answering, and below it F/T aft200_d80 ● ok |F|=4.8N |T|=0.13Nm load=12%.

RViz and PlotJuggler​

v opens or closes MoveIt RViz; it is available only when the stack was launched with Motion planning. p opens or closes PlotJuggler and does not appear in the key bar. Without a monitor on the device, no window opens. Stopping the stack closes both.

All keys​

The key bar shows only the keys that fit the moment. On a narrow window, keys at the end drop off first; they still work. With the Korean input method on, the key in the same position works too. Keys are case sensitive: r is the brake and R (Shift+r) is recovery.

KeyKoreanWhat it doesIn the key bar
sㄴLaunch · stop the stackAlways (start / stop)
rㄱRelease brake into Trajectory · brakeAfter launch
fㄹBrake ↔ FreedriveAfter launch
RㄲRecoverRed, only when recovery is needed
a · dㅁ · ㅇAdd · delete poseInside JOINT MOVE
[ · ]sameShow or hide the left column · SYSTEMAlways
lㅣLog detailAfter launch
vㅍRVizLaunched with Motion planning
pㅔPlotJugglerNot shown
← · →—Focus the robot list · the logNot shown
,—SettingsBefore launch
qㅂQuit. A second q forces it (Quitting)Always