Safety behaviour
DANGER
The on-screen E-STOP is a software stop. It travels browser → ratavyr → engine → MCU, and any of those can fail. Every machine must have an independent hardware E-stop circuit that removes driver power.
E-STOP
- In the header on every screen, and never disabled — not even while disconnected or signed in as a viewer.
- After a click it shows "Accepted, waiting for engine confirmation…".
- It reports confirmed only once engine telemetry says
emergency_stopped. A successful HTTP response only means the engine accepted the command. - If the request fails, or no confirmation arrives within 2 s, it tells the operator to use the hardware emergency stop.
- It is labelled as a software stop.
Confirmations
| Action | Why it asks |
|---|---|
| Enable | Energises the drives |
| Home | Moves the axis toward its endstop |
| Reset fault | Clears a latched fault (motion does not resume, axes must be re-homed) |
| Flash | Requires ticking "drives are powered off" |
In every dialog, Cancel has the focus, so pressing Enter or Escape never confirms by accident.
Connection status
The header always shows how fresh the data is:
| Status | Meaning |
|---|---|
live | WebSocket connected, telemetry fresh |
reconnecting | API WebSocket down; retrying with exponential backoff (0.5 s → 10 s, ±20 % jitter) |
disconnected | API or engine unreachable, with the engine's reason — e.g. an incompatible API version |
stale | No telemetry for 1.5 s |
faulted | The robot has a latched fault |
Motion controls are disabled unless the data is live and fresh. You can't command a robot you can't currently see.
Never synthesised
Every value on screen comes from engine telemetry or configuration. The UI does not predict positions, assume a command succeeded, or fill gaps when data stops. Robot states and faults are explained in MotionCore: robot states and faults.
Tested
The E-stop flow, confirmations and permission handling are covered by jsdom UI tests (npm test). See Testing.