ArduMY (retired)
Historical note about the runtime-configurable Arduino protocol
ArduMY (retired)
Status: retired in 2026.
ArduMY was OctoMY™'s runtime-configurable Arduino protocol. It was renamed to Fluxo for symmetry with the static-configuration path Fixo, then removed entirely once Fixo's embedded LLVM toolchain made its compile-and-flash workflow fast enough to be the only path.
This page exists only to redirect older bookmarks and to record what happened. There is no live ArduMY firmware to flash, no ArduMY library to install, and no controller-selection step in the Agent.
If you arrived here looking for hardware setup instructions, jump to:
- Configure Fixo Controller — current step-by-step setup guide
- Fixo Controller Reference — current technical reference
- Why Fixo — why a single static-config path replaced the runtime-config path
What survived
A handful of pieces from the old ArduMY/Fluxo stack moved into the new world rather than being deleted:
| Old (ArduMY/Fluxo) | Where it lives now |
|---|---|
| Wire protocol (frame format, command codes) | libnumex/ — the unified value/command protocol that Fixo firmware also speaks |
| Board database (pin capabilities, flash sizes) | libboard/ |
| STK500v1/v2/AVR109 flashing | libfirmware/ — used by Fixo to flash the compiled ELF |
| Actuator type names (servo, motor, stepper, relay) | libfixo/ — re-exposed as Fixo actuator types |
So if you have an old Plan that references "ArduMY", the actuator semantics are unchanged; you just need to rebuild a Fixo preset to get the controlling firmware.
What was retired
| Removed in 2026 | Reason |
|---|---|
| Runtime-configurable ArduMY firmware sketch | Replaced by Fixo's purpose-built firmware |
| Multi-controller selector in the Agent UI | There's only one controller now |
ArduMYController / FluxoController C++ classes |
Replaced by FixoController |
| Servotor32 binding | Same reason |
IController abstraction |
No longer needed for a single implementation |
See the Why Fixo explanation for the design rationale.