Swap a Module
Change a module to give your build a new capability — how it works in practice.
Because Attaky modules use defined connection channels and combination rules, you can change what your Attaky does by swapping a module — fit a different Expand for a new capability, add a Control module for input, or move a compatible module to another build. The same Core carries on running it all.
Swap carefully, and never force a module
The back board-to-board (BTB) connector has a limited mating-cycle rating and is the most fragile connector in a build, so change modules only when you need to. Always work with the device powered off, and ease modules on and off gently and squarely — if a module resists, don't push or pull harder; back off, realign, and try again. Forcing a module is the quickest way to damage a connector, especially the BTB.
How modules attach
Modules join through the Attaky connector standard: an Expand mates with the Core's back connector, bottom Control modules link by flat-flex cable, and a Power module uses the route listed on its datasheet. Some Power modules support a back connector, some a 7-pin cable, and only modules with an explicit rear passthrough can sit between a Core and an Expand. The full picture is on Frame & Connections, and the exact connectors are on the Connectors page.
Swapping in practice
Power off. Switch off the Core's POWER first, then the Power module, if your build has one. Then unplug USB-C. Don't swap modules on a live build.
Remove the Frame. Take the Frame off so you can disconnect the module, then ease the module off its connector — pull it straight off, gently, and don't force it.
Attach the new module. Line it up with the connector and push it straight on until it's fully seated. If it resists, don't force it — back off, realign, and try again.
Refit the Frame.
Flash the matching firmware first. If the swap changed what your build can do, flash the firmware made for the new module before you use it — firmware built for different hardware can damage a module or the Core. Connect USB-C to flash; the Core runs on USB, so you don't need the Power module on for this. See Flash Your First Firmware.
Power on. Turn the Power module on first, if your build has one, then the Core, to run on battery.
A couple of rules
Any combination follows the same modular rules — the Compatibility Matrix is the full reference:
- One Expand at a time. The Expand modules share the Core's signal lines, so a build runs exactly one.
- A keyboard and a gamepad can be used together. The two Control modules chain on the FPC bus and each keeps its own address, so you can run both.
Changing the Expand usually means changing firmware too — the capability lives on the module, and the firmware is what drives it. Reflash from the Firmware section after a swap.