Hardware
Actuators, sensors, and controllers
Hardware reference
Technical specifications for OctoMY™ hardware integration.
Did You Know?
OctoMY™'s hardware abstraction is designed for hobbyists - you don't need to write code to add new actuators. The actuator configuration system uses a declarative approach where you describe what hardware you have (servo on pin 9, DC motor on pins 5-6), not how to control it. OctoMY™ handles the low-level details.
Reference
Hardware basics
| Topic | Description |
|---|---|
| Actuators | Motors, servos, and output devices |
| Sensors | Input devices and data sources |
| Lobes | Real-time control logic |
| Stanzas | Agent behavior modes |
| Controller interface | How the controller layer works today |
| Fixo controller | The current static-firmware controller |
Fixo subsystems
| Topic | Description |
|---|---|
| Fixo data model | FixoPreset, FixoStanza, FixoActuator/Sensor/Lobe types, FixoPort |
fixo.json schema |
File format for every Fixo resource |
| Books and FixoLibrary | Storage, discovery, and CRUD |
| Fixo Studio | Manager activities and editors |
| Stanza Templates | Reusable stanza patterns and auto-connect |
| FixoRuntime | State machine and lifecycle |
| Preset Templates | Parameterised presets and the wizard |
| Fixo Wizard | Page-by-page reference for the controller-setup wizard |
History
| Topic | Description |
|---|---|
| ArduMY (retired) | Pointer to the retired runtime-config protocol |
Overview
OctoMY™ supports a wide range of hardware through:
- Flexible actuator configuration via
FixoActuatorTyperecords - Multiple sensor types
- Pluggable control logic (Lobes) with per-stanza placement (board / native / both)
- A single controller path — Fixo — that compiles your preset into purpose-built firmware via embedded LLVM/Clang. The earlier runtime-configurable Fluxo/ArduMY path was retired in 2026; see Why Fixo.