Open-source hardware and software for linear motion machines
For OSSM-style machines and anything else that moves along a rail: a PCB, its firmware, a protocol and an app, all open source.
Pre-release. Protocol spec v1.0-draft.
Where to start
-
Use it
Get the app and play your first script.
-
Build on it
The protocol, the docs and the plugin API.
-
See how it works
Diagrams, the planner in your browser and the PCB.
System overview
The firmware runs a hub that holds the machine's state. The desktop app, browser tabs, scripts and plugins connect to the hub as clients and stay in sync with it.
- Phosphoror any app
Phosphor builds its pages from what the machine declares. Scripts, plugins and the page the machine serves connect the same way. Phosphor
- Valencethe protocol
WebSocket over Wi-Fi, BLE for setup. The machine describes itself; apps send requests. Valence
- ESP32-C6radio
Moves bytes over SDIO and runs Espressif's stock firmware, so the P4 is the only chip you flash. Chips
- HubNucleus on the ESP32-P4
Holds the machine's state, clamps every request to the machine's limits and reports back what it actually did. Nucleus
- Kinetic²planner
Turns timed knots into a 128 ms strip of positions on a 1 ms grid, so a short planner stall doesn't reach the motor. Kinetic
- LP corequadrature out
Sends A/B quadrature from a 40 MHz crystal and parks itself if its 4 ms timeout runs out. Motion
- Servo drivecloses the loop
Follows the quadrature and closes the loop on the motor. Alarms come back to the P4, RS485 carries reads. Drive interface
- Motor and railwhere it ends up
The firmware homes it and holds every move inside the rail window; the PCB's E-stop cuts motor power in hardware. Hardware
Measurements
- Peak-to-peak spread of the LP core's quadrature edges at a prime rate, Rigol DHO4204 at 8 ns per sample. The spread is the 125 ns poll loop and does not accumulate.
- 128ns
- Quadrature transitions measured on a scope while the HP cores wrote to flash with the cache disabled (about 1.0 s of every 5 s): LP late count 0, illegal transitions 0.
- 2,156
- Difference between the native, wasm and ESP32-P4 motion plans, built with -ffp-contract=off.
- 0ULP
Sources: Nucleus: motion control · Nucleus: architecture · Kinetic: determinism
Repositories
Valence
The protocol: spec, registry, reference library, clients, tools, documentation.
MIT · spec text CC BY 4.0Nucleus
Firmware for the OSSM Flagship PCB: an ESP32-P4 with an ESP32-C6 for Wi-Fi, built on ESP-IDF. The P4's low-power (LP) core generates the quadrature output.
Apache-2.0Phosphor
The reference client, for Windows, macOS and Linux (including a Flatpak), with plugins, themes and Neutrino, a built-in emulator. Android is in progress.
Apache-2.0
Kinetic
The motion planner: jerk-limited trajectories from timed knots. Header-only C++, deterministic across targets.
Apache-2.0Hardware
The OSSM Flagship PCB and everything physical around it, in KiCad.
CERN-OHL-S-2.0
Isotope
Accessory firmware for the ESP-NOW network around Nucleus. WIP, design stage.
no license yetButtplugIO
A fork of buttplugio/buttplug carrying the Valence hardware manager, on branch
BSD-3-Clausevalence.
Status
- Firmware
Homes the rail, plays scripts, and connects to the client over Wi-Fi.
- Phosphor
Builds for Windows, macOS and Linux from one codebase. Pre-release builds.
- Protocol
Pre-release. It changes through RFCs, and the registry assigns every wire number.
The docs cover building clients and machines; Phosphor's plugin contract covers building control surfaces.
How it's built
AtlanticTM designs the system and signs off every change.
Coding agents write most of the code, held to each repo's rules: a written doctrine, a registry that assigns every wire number, lint that fails the build, tests on every change, and a bench gate that requires firmware to move a real motor before a change is closed.
The Advanced pattern comes from fray-d's OSSM-Lite and keeps its CERN-OHL-S-2.0 license. The stroke patterns come from theelims' StrokeEngine. Type is Archivo and Martian Mono, both under the SIL Open Font License.