ArmorLink lets you build wireless ESP32 props without rebuilding firmware for every small adjustment. Add simple module-to-module communication, tune servo positions, timings, GPIO assignments and settings from the browser or app, then control the finished build in one place.
Start with finished hardware, adapt a complete reference project, or use ArmorLink underneath firmware that is entirely your own.
“I want my prop to work.”
Use official ArmorLink Nodes, connect them through the app and follow a complete build guide from wiring to calibration.
“I can wire and solder — just give me a proven starting point.”
Recreate an official reference build or adapt its documented source code to your own pinout, servos and components.
“Firmware updates should be for features, not servo angles.”
Build your own firmware, expose the settings that should stay adjustable and stop recompiling just to tune hardware.
Move from a finished Node to your own wiring and later to fully custom firmware without replacing the ecosystem around it.
ArmorLink gives every module the same language for Actions, configuration, telemetry and presence, whether you are using one ESP32 or a full prop with multiple wireless parts.
Helmets, arms, backs, props and sensors as independent modules.
Trigger Actions between modules without writing routing logic again.
Use the Companion App when you want a UI. Run prop-to-prop commands when you do not.
Hardware, firmware and app integration for real-world builds.
Each official reference project is designed to be reproduced, understood and adapted — not hidden behind a compiled binary.
ArmorLinkModule helmet(
"ArmorLink Helmet",
ArmorLinkModuleType::Helmet
);
void toggleFaceplate()
{
ArmorLink.info("Toggle faceplate");
}
void setup()
{
ArmorLinkOptions options;
options.enableBle = true;
options.enableEspNow = true;
helmet.actions()
.add("toggleFaceplate")
.label("Toggle Faceplate")
.command("Facemask", "toggle")
.onExecute([] {
toggleFaceplate();
});
ArmorLink.begin(helmet, options);
}Connect an ArmorLink node in the browser, read what the firmware supports and tune the prop without opening an IDE or recompiling for every small hardware adjustment.
Expose servo positions, timings, GPIO assignments and module settings without hardcoding every value forever.
Adjust pins, open and closed positions and pulse ranges for mechanisms like faceplates.
Reuse compatible module, board and servo profiles for repeatable builds and hardware variants.
Use the setup tool while building and the Companion App when the prop is assembled.
ArmorLink does not force every project into the same architecture. Start with one device, add modules when the build needs them and keep diagnostics available in the field.
Run one ESP32 as a Gateway-enabled module and control it directly from the ArmorLink Companion App. ESP-NOW is not required.
Single Module Gateway →Use one Gateway and multiple paired modules. Send Commands between modules or broadcast Commands to all matching modules.
Gateway Button Panel →Use on-demand Telemetry, Remote Logging and module Presence detection to debug assembled systems without USB access.
Remote Logging →Define a module, expose Actions and keep adjustable hardware values in configuration instead of rebuilding firmware for every tweak.
ArmorLinkModule helmet(
"ArmorLink Helmet",
ArmorLinkModuleType::Helmet
);
void setup()
{
ArmorLinkOptions options;
options.enableGateway = true;
options.enableBle = true;
ArmorLink.begin(helmet, options);
}void toggleFaceplate()
{
ArmorLink.info("Toggle faceplate");
}
module.actions()
.add("toggleFaceplate")
.label("Toggle Faceplate")
.command("Facemask", "toggle")
.stylePrimary()
.onExecute([] {
toggleFaceplate();
});config.addServoConfig("faceplateLeft", &servoLeft)
.section("Servos")
.gpio(4)
.openPosition(160)
.closedPosition(10);
config.addBool("eyeFlicker", &eyeFlicker)
.section("LEDs");Official boards are the shortest route to a working prop. The same concepts remain available as open reference projects for self-built hardware.
Faceplate servos, eye outputs and guided calibration for animated helmets.
A dedicated audio module for effects, triggers and prop-integrated sound.
A compact Multi Purpose Node for small mechanisms, lights and sensors.
Expandable Nodes for larger mechanisms and more complex wearable systems.
High-channel-count control for larger servo-driven assemblies.
The app is not required for every ArmorLink build. When used, it provides one interface for pairing, Actions, settings, telemetry and remote logs.
See connected modules, status and available controls.
Control Actions and inspect module-specific configuration.
Discover and pair modules through the ArmorLink Gateway.
Read live values and remote logs without opening the prop.
Framework concepts, API documentation, examples and technical guides continue in the dedicated Docusaurus documentation.