Skip to content

Introduction ​

MotionCore lets you configure, build firmware for, connect, monitor and control robotic axes without rewriting the motion-control stack for every robot. You describe the robot in a TOML file; MotionCore plans the motion on the host, streams timestamped segments to a microcontroller, and the microcontroller produces the step pulses.

It runs independently of ROS. The first physical reference robot is the Annin Robotics AR4-MK5, but nothing in the architecture depends on that model.

The three repositories ​

MotionCore is split into three independently versioned repositories. Only the first is required.

RepositoryLanguageRoleRequired?Docs
motioncoreRustEngine (the state authority), MCU firmware, simulator, plugins, firmware builder, motioncore CLI, engine API contractyesthis site
ratavyrGoREST/WebSocket gateway: authentication, roles, audit log, firmware job orchestrationoptionalratavyr.bzy-logics.com
sindravaTypeScript (Vite + React + Three.js)Browser operator UIoptionalsindrava.bzy-logics.com
text
sindrava ──REST/WS──▶ ratavyr ──gRPC (engine-api v1)──▶ motioncore engine ──COBS+CRC frames──▶ MCU firmware
                                                              ▲                                (board or simulator)
                                motioncore CLI ──gRPC─────────┘

The rule that holds everything together: the engine is the only owner of robot state. The gateway and the UI relay commands and display telemetry; they never plan motion, invent state, or talk to hardware directly. The MCU, in turn, independently enforces its own safety limits even if the host misbehaves.

What works today ​

AreaStatus
Engine, motion planning, safety state machineImplemented, tested end-to-end in simulation
Virtual MCU (in-process and over TCP)Implemented, runs the real firmware runtime
motioncore CLIImplemented
Firmware builder (configure / build / flash / verify)Implemented
STM32F411 "Black Pill" firmware (1 axis)Compiles, host-tested, not validated on hardware
RP2040 Pico firmware (6 axes, PIO)Compiles, host-tested, not validated on hardware
Builtin pluginsImplemented
External WASM pluginsManifests validated; execution not yet implemented
ratavyr gateway (REST, WebSocket, roles, audit)Implemented
sindrava UIImplemented; Robot Composer is read-only
Coordinated multi-axis motionNot yet — one axis is commanded at a time
Multiple MCUs per robotNot yet — one MCU per robot

See Roadmap & status for the full list.

Where to go next ​

Safety

MotionCore is not a certified safety system. A software emergency stop complements a hardware E-stop circuit; it can never replace one. Any physical setup must have an independent E-stop that removes driver power.

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