Running a workflow in the cloud sim

Run a workflow against the simulated robot at zeonsystems.app: what you need, the steps, and what a run does and does not change.

In the cloud every run is a simulation: the workflow drives a simulated robot in your world, and you watch it in the 3D view. Use it to check a workflow before it runs on a real robot.

What you need

The starter project already has both: the workflows Plate Transfer (plate_transfer) and Plate Through Shaker (plate_through_shaker), and the world shaker_deck. Its project.json names Plate Transfer and shaker_deck as active, so the run screen selects them for you.

Running it

  1. Open https://zeonsystems.app. The app opens your last project; switch with the project dropdown in the header if needed.
  2. Click Execute Workflow on Home. The Workflow Editor opens.
  3. Pick the workflow under Workflow and the world under World, then click Load if the world shown is not the one loaded ("Not loaded: click Load to run").
  4. Fill in the Inputs tab, or the canvas if the workflow has one, and confirm in the canvas.
  5. Click Run, adjust the run name if you want, and click Start.

From the CLI (1.5.5 or newer), zeon app <workflow> --run prints a link that opens step 3 directly, and zeon app <workflow> opens the canvas. The link also signs the browser in, so you do not need to sign in first; it is personal and works once, within 5 minutes (see Login links from the CLI). See The Workflow Editor.

zeon run <workflow> runs it from the terminal instead, Fast at 8x by default (--speed 1|2|4|8; --motion full for the robot's own control loops in real time). See Instance commands.

During the run

  • The World View shows the simulated arms moving.
  • The graph highlights the current step; the strip under it lists finished steps with their durations.
  • The Log tab streams the run log. See The run log.
  • If a skill asks a question, a dialog waits for your answer. zeon answer ID CHOICE answers it from the terminal.
  • Pause, Resume and Stop work as on a real robot: Pause holds the arms where they are, Stop ends the run. zeon stop ID stops a run from the terminal.

In the cloud, a step that fails ends the run: the badge reads FAILED and the strip under the graph names the step and the error. Fix the cause, push the fix with zeon sync, click Refresh in the header, and run again.

What a run changes

  • Each run reloads the world before its first step, so every run starts from the saved world. The reload does not move the arms: after a run that stopped half-way with an arm holding or touching something, click Reset (or run zeon reset-arms) before the next run.
  • A run never changes the saved world. Objects a skill moves are moved for that run only.
  • Your input values stay on screen after the run, ready for the next one.

Only one run is in force at a time. Starting another while one runs is refused with "Another run is in progress: … Stop it or wait for it to end."

Cloud only

The execution world is locked to Simulation; its tooltip reads "Cloud runs simulation only". In place of the pipette button, the bar has Reset, which puts both simulated arms back at their start position, opens the grippers and lets go of a held object (zeon reset-arms does the same from the terminal). Data Export, Secrets and the Workflows history screen exist on a deployed box only; earlier runs of a workflow that did not complete are still listed under Resume run.

When the workflow behaves as it should, run it on the robot: Running a workflow on real hardware.


Did this page help you?