Running a workflow on real hardware
Run a workflow on the robot from a deployed box: the execution world, the checks before the arms move, and how Pause and Stop behave.
Real-hardware runs happen on a deployed box, the Zeon machine wired to your robot. You use the same Workflow Editor as in the cloud; the execution world dropdown next to the status badge decides whether the real arms move.
The robot moves. Clear the workspace of people and obstacles before you run, and keep the robot's emergency stop within reach. Pause and Stop in the app are software commands sent over the network; they do not replace an emergency stop.
Simulation or Real Hardware
On a deployed box the dropdown offers Simulation and Real Hardware, and the Workflow Editor and the Skills Editor both start on Real Hardware. Check the dropdown every time you open the screen. The choice is made per run, and the dropdown is locked during a run.
In the cloud there is no real hardware; the dropdown is locked to Simulation.
Before you run
The app does not check that the bench matches the world, or that each arm carries the tool the software expects. Check both yourself:
- The scene matches the world. Every object the workflow uses must be where the world says it is. Compare the bench with the world in the World Builder.
- The endpoints match the tools. Hardware Setup in the header menu shows the endpoint each arm is fitted with (
live: …). Change it between runs, not during one: applying restarts the backend. See Hardware Setup.
The Hardware indicator in the header shows whether the arms, grippers, cameras and pipettes the setup expects are connected: green when all are, amber when one is not, grey when the execution service does not answer. It is not a safety check: it does not say where the arms are, whether the scene matches the world, or whether a camera delivers images right now.
Running
- Open the app on the box and the project.
- Click Execute Workflow on Home.
- Pick the workflow and the world, and Load the world.
- Set the execution world to Real Hardware.
- Fill in the inputs, or confirm in the canvas.
- Click Run, name the run if you want, and click Start.
Before the arms move, Run makes two checks. If either fails, the run does not start and a message says what to fix:
| Check | On failure |
|---|---|
| Each wrist camera delivers a fresh image. | "… wrist camera not streaming. Check the camera is plugged in / powered, then press Run again." |
| The pipette is homed, which also reconnects it if its link dropped. On a rig without a pipette this check passes. | "Pipette not connected. Check that the pipette is powered on, power-cycle it, then press Run again." |
The run then reloads the world and starts.
Pause and Stop
- Pause stops the arms at once, mid-move, and holds the run until you click Resume (or a resume choice a skill offers).
- Stop stops the arms at once and ends the run.
Pause and Stop do not move the arms to a rest position. The arms stay where they stopped, which can mean an arm holding labware over an instrument. Plan the recovery before you press Stop. In operator mode, Park runs the project's park skill, if it has one.
After a Stop, the inputs stay on screen so you can fix something on the bench and run again.
If a skill fails on real hardware and its node has no on_failure edge, the run does not end and shows no error: it stays at that step, shown as running, and Resume does not continue it. Stop ends it.
Continuing an interrupted run
Resume run in the top bar lists runs of the workflow that did not complete. Picking one opens a five-step dialog that walks you through returning the pipette held in the gripper to its stand before the run continues.
The sliders in the third step of that dialog open and close the real grippers as you move them. Hold the pipette firmly before you touch a slider, keep your other hand clear of the jaws, and move in small steps.
The resumed run starts the workflow again from its first step, in the same run record and with the same inputs. Skills that record their progress skip work already done; other skills repeat. See Resume run.
One run at a time
The box runs one workflow or skill run at a time. A run started while another is in force is refused with "Another run is in progress: … Stop it or wait for it to end."
Updated 9 days ago