Skip to content

Roadmap & status ​

MotionCore is at v0.2 (development). The full design is in the specification (draft v0.2).

Phases ​

PhaseScopeStatus
0 — Architecture contractsState machine, units, motion ownership, plugin manifests, protocol messagesDone
1 — Virtual MCU + Rust hostProtocol crate, framed transport, simulated MCU, handshake, clock sync, queue, fault telemetryDone
2 — First physical axisSTM32 firmware: step/dir, enable, limit switch, watchdog, safe faults; validated with instrumentsFirmware done; hardware validation pending
3 — Plugin SDK and device graphPlugin lifecycle, capability resolution, example plugins, config validationDone for builtin plugins; WASM execution pending
4 — Motion engineJoint-space trajectories, trusted validation, homing, stop behaviour, virtual/physical paritySingle-axis done; coordinated multi-axis pending
5 — Go API + React dashboardStatus, jog/homing, plugins, telemetry, 3D viewDone (ratavyr, sindrava)
6 — Firmware builderBoard selection, reproducible compile, flash, verify, logsDone
7 — Multi-axis / AR4-MK5Real controller electronics, pinout, gearing; one joint → synchronised multi-jointRP2040 six-channel firmware done; not started on the robot

v0.1 acceptance criteria ​

#A user can…Status
1Install and start the Rust engine independently; optionally connect the Go API and React UI✅
2Load a versioned robot/actuator plugin✅ builtin
3Configure one axis through the web UI⚠️ UI shows config read-only; edit TOML
4Connect a virtual MCU and issue validated jog/home/stop commands✅
5Select a supported STM32 board, compile and flash firmware✅ compile; flashing unverified on hardware
6Connect real hardware and confirm firmware capabilities⏳ pending hardware
7Move a single axis safely with endstop/watchdog support⏳ pending hardware
8Inspect position, queue state, communication health and faults✅
9Disconnect the MCU or crash a plugin and observe defined fault behaviour✅ in simulation

Known limitations ​

  • One MCU per robot; telemetry has one MCU block.
  • One axis moves per command; motion::plan_synchronized exists but is not wired up.
  • Measured position is the MCU step counter; no encoder feedback.
  • Serial transport, flashing and both boards' firmware are untested on hardware.
  • External WASM plugins are validated but not executed.
  • No configuration-editing or validation API; the Robot Composer is read-only.
  • Firmware verification is CLI-only.
  • Firmware job progress is polled; the event stream does not carry job updates.
  • Gateway roles are per token: no user accounts, and tokens can only be rotated by restarting.
  • The 3D viewer cannot draw an articulated chain; the engine does not expose link geometry.

Later ​

  • Additional MCU families (ESP32-S3, Teensy 4.1) after toolchain and HAL validation
  • Multi-MCU synchronisation
  • Editable visual Robot Composer
  • Encoder and GPIO firmware modules; servo PWM
  • WASM plugin execution (Wasmtime), web UI extensions
  • Collision-aware planning, advanced calibration
  • Homing with back-off and slow second touch
  • DFU flashing for STM32
  • Separate MotionCore ROS and MotionCore AI Lab projects, integrating through the stable APIs

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