Safety¶
uMe is a full-size humanoid. Treat every live session as physical-safety-critical.
For IT, technicians and integration partners
Technical reference for IT departments, URG technicians and trained partners. It is not written as operating instructions for end users.
Built-in safeguards¶
- STOP (software stop). The
estopcommand (the app's red STOP button) forcesDAMPand damps all motors; it does not wait for a pending mode change. Known limitation (Gateway 2.6 and later, not yet checked on a device): while an action is running (gesture, dance, get up, also as a step in a skill), STOP takes effect only after that action has ended. If the robot does not go to DAMP, press the emergency stop on the robot at once. STOP then takes effect as the last command. If the robot does not confirm STOP within 2 s, the app reports it (estop_failed): press the emergency stop on the robot. During an action, do not wait for this report. STOP is not a safety function: keep the emergency stop on the robot within reach at all times. - Guarded mode changes. Entering
PREPuses a slide-to-confirm control, so the robot never extends its body by accident. - Gated locomotion. Joysticks and
moveare only active inWALK; a damped or unprepared robot cannot be driven. - WALK after PREP only. The app disables
WALKuntil the robot has been prepared. - Clear status. Warnings from the robot and mode hints are shown prominently and take priority in the UI.
Mock mode for development¶
The Gateway can be started in mock mode (--mock): every command is validated and logged and
status is streamed, but no motion is executed. Use it for app development, scripts and CI.
The installed service runs in real mode
On a commissioned robot the autostart service runs with --real — motors respond as soon as
the service is up. Never assume a robot is "only mocking": check with
systemctl --user status ume-gateway.service and keep the emergency stop on the robot within reach.
First live run¶
- Only with a responsible person at the robot, emergency stop on the robot in reach.
- Start from
DAMP, go toPREP, place the robot on the ground, thenWALK. - Keep the app's STOP button visible and ready.
- Expect that STOP (
estop) puts the robot into DAMP and requires re-preparing it via PREP.
Network safety¶
The Gateway has no authentication yet — network isolation is the security boundary. Keep
port 8765 on the LAN only and never expose it to the internet. On the robot, change default
credentials and prefer an SSH key (see Gateway Deployment).