Operator mode
A simplified view of the app for the person running the robot, typically on a tablet next to it: pick a workflow, Start, Pause, Stop, Park.
Operator mode reduces the app to what the person at the robot needs: a list of workflows and a run screen with large buttons. It is meant for a tablet or screen next to the robot. Nothing about the project changes; it is a different view of the same app.
Operator mode is a convenience, not an access control: anyone can leave it with ?ui=full.
Turning it on and off
The mode is remembered per browser, across reloads and sign-ins.
- On: add
?ui=operatorto any app address, or choose Operator mode in the header menu. - Off: add
?ui=fullto any address. Zeon administrators and organization admins also see Leave operator mode in the menu.
What the operator sees
The header holds Home, the project name, the Hardware indicator, the account, and a menu with Restart backend, Leave operator mode (Zeon administrators and organization admins only) and Log out. There is no sidebar. Any screen other than Home and the run screen redirects to Home.
Home is titled Choose a workflow. It lists the project's workflows as large buttons, the project's active workflow first, marked Usual workflow. Below are the other projects, to switch to.
The run screen shows:
- The workflow name, Real robot or Simulation, and the world. Workflows goes back to the list (not during a run).
- A status panel in plain words: Ready, Waiting for you, Starting, Running, Paused, Done, Stopped or Failed, with the next step to take.
- Large buttons: Start (or Start again), Pause, Resume, Stop, and Unfinished runs, which offers the same resume as Resume run. Start asks for confirmation and an optional run name first.
- If the world is not loaded, "The world is not loaded." and Load world. When the project names no active world and has several, a world list comes first.
- Show steps opens the workflow graph, read-only.
- Two tabs: Setup (the inputs form or the canvas) and Run log.
Prompts from a skill appear as on the full run screen; the status panel then reads "Waiting for you".
Park
Park moves the arm to its rest pose. It appears only when exactly one skill in the project carries the tag park in its metadata.yaml; that skill is what Park runs. Park asks for confirmation, is refused while a run is in force, and can be stopped while it moves.
# skills/park_arms/metadata.yaml (excerpt)
tags:
- parkSee Skills metadata.yaml.
Updated 9 days ago