Skip to content

Emergency Stop ​

WARNING

Always keep the emergency stop button accessible during operation. In any situation where the robot poses a risk to people or property, press the emergency stop button immediately.

E-STOP in the app ​

E-STOP confirmation

The red E-STOP button sits at the right of the top bar on the control home. On a very small screen, less than 720 px wide, it shows only its emergency icon (on a humanoid the RL stop label stays). On the other screens it sits in the same place at the right of the header. It works while a robot is connected or is reconnecting after a dropped link — for 8 seconds after the drop — and is dimmed otherwise. Pressing it opens the confirmation Emergency stop?:

The robot immediately stops all motion and cuts power. Reinitialization is required to resume control.

Press Stop to send the emergency stop, or Cancel to close the dialog. There is no path that fires E-STOP without this confirmation.

  • The app sends the emergency stop on a dedicated channel, ahead of anything already queued, and repeats it on the reliable command channel.
  • You do not need to own the robot first: the robot accepts E-STOP from any connected device, bypassing the ownership check. It does not take ownership — the current owner stays the same.
  • If neither channel is open when you press Stop — for example right after the link dropped — the app shows E-Stop send failed — the channel is closed. Use the physical emergency stop at once. Use the physical button. The app still keeps the stop and sends it if the link comes back within 8 seconds.
  • If the robot does not acknowledge the command, the app logs E-Stop send failed — no response. Use the physical E-Stop. Do not wait — use the physical button.

Physical emergency stop button ​

Emergency stop button on the rear of the robot
[ Emergency stop push button — located on the rear of the robot ]

When the physical emergency stop button is pressed, or the app's E-STOP is confirmed:

  • All joints switch to High Damping mode.
  • The robot resists external motion but does not accept torque or position commands.
  • The robot may lose its posture and settle to the ground under gravity.

High Damping mode protects both the user and the robot. The robot will not execute any motion commands until the emergency stop is cleared and the robot is re-initialized.

Recovery ​

  1. Ensure safety — confirm that all people and animals are at least 2 m from the robot.
  2. Release the button — if the physical button was pressed, rotate it clockwise to unlock it.
  3. Return to initial pose — if the robot has fallen or shifted, place it in the initial pose on a flat surface. Do not force the joints while the robot is in High Damping mode.
  4. Re-initialize — run the automatic start sequence or the Stand motion from the control home and confirm the robot state in the top bar before resuming operation.

If the robot still cannot get up, use the Position control group in the Select command grid — Manual Recovery, Lock Joints, Position Sit and Position Stand — only on flat ground with the robot on the floor. See Motion commands.

Spectating ​

Only one device controls the robot at a time, and a device connects as a spectator — it does not take control on its own, even when no other device is driving. The one exception is the device that was driving when its connection dropped (the app or the robot software restarted, the WiFi dropped, or the app stayed in the background long enough for the robot to close the connection): when it connects again and no device holds control, it takes control back without asking. If another device holds control by then, it stays a spectator. After this device sees another device driving, or after you press Disconnect on the hub, it no longer takes control back on its own. A robot without a serial number, such as the simulator, is remembered only until the app closes. Right after it takes control back, the robot does not follow a stick you are already holding until you let that stick return to the center; while you push such a stick, Control taken back — center the sticks to drive shows. Buttons work as usual. About a second after connecting, or after another app or controller takes ownership, this device shows spectating: the video and the 3D view keep running, but every control below the top bar is locked. The top bar stays usable — E-STOP, the logo menu, the view dropdown and the status popover. On the control home the Spectating button sits just below it at the center, next to Another device is driving · tap to take control, or No one is driving · tap to take control when no device holds control. On the hub and the other screens a small Spectating chip appears on the right of the top bar, left of the battery.

On the hub, in Settings, in the log and on the Add robot and Access code screens nothing is covered — you can still add another robot or enter an access code while spectating. On the hub the Dashboard tile is locked, Maintenance shows only Robot Check with only its remote check section (so you can still disconnect remote check — see Remote check), and the auto-start card is hidden; in Settings the robot tabs are locked while the app tabs stay usable. The Add robot and Access code screens show no spectating mark.

While spectating, the view dropdown offers 3D and Driver's view only. The driving device picks the camera, so Driver's view shows the same camera it is watching. When the driving device is on 3D, Driver's view switches to 3D as well, and goes back to that camera when the driver does. A spectating device never turns the robot's camera on or changes it. You hear the robot's audio only while the driving device has Listen to robot audio on.

Up to four devices can spectate a robot at once (MAX_SPECTATORS under [WebRTC] in the robot's Streamer.ini, 4 when absent, 0 for no limit; read when Streamer starts). When all slots are taken, a spectator gets no video until one frees up: the view stays on 3D and the Spectating button on the control home reads Too many viewers, video waiting · tap to take control. Video comes back on its own when a slot frees up, and taking control works regardless. A spectator connected remotely (WAN) gets no video, only the 3D view and status readouts.

Tap Spectating to open Take control?. Its top line shows the current state (Another device is driving, No one is driving and so on):

  • Take control — asks the robot to hand ownership to this device. The device that was driving switches to spectating.
  • ▶ Auto Start — after the confirmation Run Auto Start? → Auto Start, takes control and runs the automatic start sequence.
  • Keep spectating — closes the menu.

On the control home you can also check and take ownership from the Overall system status popover (tap the status chip in the top bar): the Ownership row shows Held when this device is the owner and Take ▸ when it is not.

Overall system status popover with the Ownership row

This user manual is intended for RBQ users.