Skip to main content

Introduction

ArmorLink is a modular framework for connected props, wearables and ESP32 projects.

It was created to simplify the development of distributed systems consisting of one or more ESP32-based modules.

ArmorLink provides a common architecture for communication, configuration management, telemetry, remote debugging and mobile app integration while allowing developers to focus on their actual application logic.

Building a distributed ESP32 project often requires solving the same problems repeatedly:

  • Device communication
  • Module management
  • Configuration storage
  • Remote control
  • Telemetry
  • Debugging
  • Mobile app integration

ArmorLink provides a unified solution for these challenges and allows developers to focus on building features instead of infrastructure.

Core Concepts​

ArmorLink is built around a small number of concepts:

  • Gateway
  • Modules
  • Actions
  • Configuration
  • Telemetry
  • Remote Debugging
  • Mobile App

Understanding these concepts is the key to understanding ArmorLink.

Architecture Overview​

Every ArmorLink network has exactly one Gateway.

For small projects, the Gateway may be the only module in the system.

For larger projects, the Gateway acts as the central coordinator that connects and manages all other modules.

              Mobile App
                  ?
                (BLE)
                  ?
                  ?
             Gateway
          (Coordinator)
            /   |   \
           /    |    \
          ?     ?     ?
      Helmet  Arm   Back

The mobile application is optional.

ArmorLink systems continue to function without the mobile application.

ArmorLink does not replace your application code.

Buttons, sensors, LEDs, servos, audio systems and effects remain part of your own firmware.

ArmorLink provides the infrastructure that allows modules to communicate and be managed consistently.

For example:

  • A button press may trigger local LED effects
  • The same button press may send a command to another module
  • A receiving module may execute an Action in response to that command

ArmorLink handles communication and routing.

Your firmware defines the behavior.

Next Steps​

Continue with the following topics:

  1. Gateway
  2. Modules
  3. Actions
  4. Configuration
  5. Telemetry
  6. Pairing
  7. Mobile App