AXON Technical Documentation

Engineering deep-dives written from real firmware and field deployments, not from marketing copy. Each guide documents one AXON product end-to-end — pinouts, bus configuration, encryption, failure modes, installation requirements, and what is shipping today versus what is on the roadmap.

Why this library exists

Most access control vendors publish datasheets that read like sales sheets — long lists of features, no engineering detail, and a contact form when you want to know how something actually works on the wire. That is not useful when you are sizing a CAN backbone for a twenty-floor riser, deciding whether to terminate a LoRa link with a directional antenna, or wondering whether a relay module's output stage will survive an inductive kickback from an elevator brake coil.

This documentation library exists because we built every board in the AXON system ourselves, in Kosovo, and we know what the firmware does — line by line — because we wrote it. So the answers we give in these guides come from the source, not from a marketing team summarising a product brief. When an article says "the CAN controller pauses for thirty seconds after five consecutive errors and then re-initialises", that statement is grounded in the code path that handles it. When an article says "the relay output is driven from the local card-authorisation path rather than from a CAN command issued by the Master", that is what the firmware does today — even though it is not what the long-term architecture is supposed to look like.

We document the gap between current implementation and design intent openly, because integrators planning rollouts deserve to know what is shipping and what is roadmap. There is no honest way to land a hardware deployment with a vendor that pretends the gap does not exist.

What you will find here

The twelve articles below cover the full AXON product line. Six modules are shipping today with stable firmware and field deployments in Prishtinë and elsewhere in Kosovo. Six are in development with prototypes on the bench, firmware in active integration, and documentation already written so integrators can plan ahead. Every article follows the same structure: an answer-summary box at the top for the impatient reader, then sections covering what the module does, required components, end-to-end operation, bus configuration, pinout, communication architecture, protections, installation, troubleshooting, comparisons to alternatives, roadmap, and an FAQ block.

For deeply technical readers — embedded engineers, building automation integrators, certified security installers — start with the floor node article (AXON Node) because it is the most thoroughly documented and explains the AES-128 CTR encrypted CAN bus that ties most of the system together. From there, the cabin controller article (CCU-32) explains how floor relays are driven in an elevator integration. The reader article (URX-Secure) explains how DESFire EV2 anti-cloning works in practice. The communication module articles (ICM-GE, ICM-LR) cover Ethernet, GSM, and LoRa uplinks for sites without local fibre.

Browse by category

The twelve articles group naturally into five families. Use the category labels below to jump to the section that matches what you are looking for, or scroll through the full grid.

Topic guides and concept articles

Beyond the per-product deep-dives, the library contains topic-level articles that explain the concepts these products embody — protocol choices, anti-cloning strategy, and reference architectures for common building types. Read these first if you are evaluating AXON against alternatives, or if you want to understand the design decisions behind the product line before drilling into specific modules.