The main app
The web app for a project: opening a project, the screens, the header menu, and what differs between the cloud and a deployed box.
The main app is the browser interface to one project. You run workflows, try single skills, build worlds, and annotate objects there. It runs in two places:
- The cloud, at
https://zeonsystems.app. Every run is a simulation. - A deployed box, the Zeon machine wired to your robot. The same app can also drive the real arms.
You edit the project files themselves with the CLI and your editor. See The development loop.
Opening a project
Sign in as described in Signing in. If you open a link into the app while signed out, sign-in returns you to that link.
The address / opens a project for you: the one you last opened in this browser, otherwise your most recently updated project. If you have no project yet, one is created. Every screen of a project lives under /p/<project-id>/.
To switch project, use the project dropdown in the header. The app stays on the same screen and shows a loading screen while the other project is prepared.
Screens you may see before the project opens
| Screen | Meaning | What to do |
|---|---|---|
| All robots are busy | Every robot slot is taken. The text reads "You are number N in line." | Wait. The page asks again on its own: after 5, 10 and 20 seconds, then every 30 seconds. Retry asks at once. |
| Could not load | The first load failed for another reason. The text says what failed. | Retry. |
| Cannot open this project | The project could not be opened: it does not belong to the signed-in account, it does not exist, or the server failed. The screen names the project id, the account you are signed in as, and the error. | Check that you are signed in with the right account. Retry tries again; All projects goes back to /. |
| Waiting for the backend… | The services behind the app are starting or restarting. | Wait. After one minute a Continue anyway button appears. |
The screens
| Screen | How to get there | Page |
|---|---|---|
| Home | The house button in the header | Below |
| Workflow Editor (the run screen) | Execute Workflow on Home | The Workflow Editor |
| World Builder | Build World on Home, or the sidebar | The World Builder |
| Skills Editor | Practice Skill on Home, or the sidebar | The Skills Editor |
| Object Database | Annotate Object on Home, or the sidebar | The Object Database |
| Workflows | Past Executions on Home, or the sidebar (deployed box only) | Below |
Home is a grid of tiles: Execute Workflow, Practice Skill, Build World, Annotate Object, and, on a deployed box, Past Executions.
The sidebar is hidden by default; the menu button at the far left of the header shows it. It lists Home, World Builder, Skills Editor and Object Database, plus Workflows on a deployed box.
Workflows (deployed box only) has two tabs. Saved Workflows lists the project's workflows. Past Executions lists earlier runs with their status, date and world.
The header
From left to right: the sidebar button, the Home button, the project dropdown, a refresh button, the Hardware indicator, your email address, and the menu (the vertical dots).
- Refresh re-reads the project's skills, workflows and worlds. Its tooltip reads "Refresh project data (re-fetches skills, workflows, worlds from sync)". Use it after you push changes with the CLI.
- Hardware shows a coloured dot: green when every expected device is connected, amber when one is not, grey when the execution service does not answer. Click it for the detail per device, the name of the setup the backend runs, and a Reconnect pipette button when a pipette is down. It is not a safety check. See Running a workflow on real hardware.
The menu holds:
| Item | What it does | Where |
|---|---|---|
| Restart backend | Restarts the services behind the app, after a confirmation. A run in progress is interrupted. The app reloads the project when the backend is back. | Cloud and deployed box |
| Hardware Setup | The rig, and the gripper endpoint on each arm. See Hardware Setup. | Cloud and deployed box |
| Pipettes | Which pipettes the rig connects at startup. See Hardware Setup. | Cloud and deployed box |
| Data Export | Where exported run data is uploaded. See Data Export. | Deployed box only |
| Secrets | Named credentials for skills. See Secrets. | Deployed box only |
| Operator mode | Switches this browser to the simplified operator view. See Operator mode. | Cloud and deployed box |
| Log out | Signs you out. | Cloud and deployed box |
Cloud and deployed box
| Cloud | Deployed box | |
|---|---|---|
| Execution world on the run screen and in the Skills Editor | Simulation only. The dropdown is locked; its tooltip reads "Cloud runs simulation only". | Simulation or Real Hardware. Both screens start on Real Hardware. |
| Button next to Run | Reset: puts both simulated arms back at their start position (zeon reset-arms from the terminal) | Reconnect pipette |
| Workflows screen and Past Executions tile | Hidden | Shown |
| Data Export and Secrets | Hidden | Shown |
| Rig setup in Hardware Setup | Switchable among the rigs available to your organization | Fixed to the box's configured setup |
A workflow run that starts while you are on another screen, for example from another browser tab, opens the Workflow Editor on that run.
Updated 1 day ago