Skip to content

Robot states ​

The engine's safety supervisor tracks exactly one robot state. Every client sees it as the state field of telemetry.

StateMeaningDrives
disconnectedNo MCU linkoff
initializingLink up; handshake, clock sync and axis configuration in progressoff
disabledMCU ready, drives not energisedoff
readyDrives energised, idle; motion commands acceptedon
homingA homing move is runningon
runningA jog or move is runningon
faultedA fault is latchedoff
emergency_stoppedA software E-stop is latchedoff

Transitions ​

The normal path:

text
disconnected ──connect──▶ initializing ──initialized──▶ disabled ──enable──▶ ready ⇄ homing
                                                            ▲                  │ ⇄ running
                                                            └─────disable──────┘

Exceptions:

text
any connected state ──fault / link lost──▶ faulted ───────────reset_fault──▶ disabled (link up)
any state ───────────estop──────────────▶ emergency_stopped ─reset_fault──▶ disconnected (link down)
FromEventTo
anyestopemergency_stopped
emergency_stoppedreset_faultdisabled if linked, else disconnected
emergency_stoppedfault, link lost, disable, motion completeemergency_stopped (unchanged)
disconnectedconnectinitializing
initializinginitializeddisabled
initializinglink lostdisconnected
initializingfaultfaulted
other connected statesfault or link lostfaulted
faultedreset_faultdisabled if linked, else disconnected
disabledenableready
ready, homing, runningdisabledisabled
readyhomehoming → ready when done
readyjog / moverunning → ready when done

The rules, from the transition table in crates/safety:

  • E-stop always wins. estop is accepted in every state and moves to emergency_stopped. While E-stopped, faults, link loss and disable requests do not change the state.
  • Faults and link loss move any connected state to faulted. The first fault is kept; later ones do not overwrite it. During initializing, link loss returns to disconnected instead.
  • Reset never resumes motion. reset_fault from faulted or emergency_stopped lands in disabled if the MCU is still connected, otherwise disconnected. Drives stay off and every axis must be re-homed.
  • One motion at a time. home, jog and move are only accepted in ready. A new motion command while running or homing is rejected with invalid_state.
  • Disable from ready, homing or running performs a controlled stop if moving, then de-energises the drives.
  • Nothing except connect is accepted while disconnected.

A rejected command returns invalid_state (gRPC FAILED_PRECONDITION, HTTP 409).

Stop vs. E-stop vs. disable ​

CommandMotionDrivesLatches?Who may send it (gateway)
stopDiscards queued segments, decelerates at stop_decelerationstay onnoviewer and up
disableControlled stop if movingturned offnooperator and up
estopHalts step generation immediatelyturned off immediatelyyes — emergency_stoppedviewer and up

stop and estop are open to every authenticated role and are never rate-limited: anyone who can see the robot may stop it.

Confirming a command ​

A successful response means the engine accepted the command, not that it finished. Watch telemetry for the outcome. For estop in particular, a client should only show the stop as confirmed once telemetry reports "state": "emergency_stopped". The sindrava UI does exactly this, and tells the operator to use the hardware E-stop if no confirmation arrives within 2 s.

Apache-2.0 OR MIT. Not a certified safety system — always use an independent hardware E-stop.