AXON Master E
An Ethernet access controller with four local relay contacts, reader interfaces and two CAN connections for compatible expansion. Select the firmware, readers, output interfaces and power arrangement for the building.
One board for a small site
AXON ICM-E is an Ethernet controller with four local relay contacts, one RS-485 reader port and one Wiegand input. The contacts provide control signals for doors, gates or compatible equipment. The number of complete doors is planned separately, including each reader, lock supply, exit interface and required connections.
The access rules are stored locally, while the network supports the configured administration and communication functions. When more command contacts are needed, compatible nodes can extend the installation over CAN. The local output count, number of readers and complete access points are separate design decisions.
ICM-E suits offices, clinics and commercial buildings with an available Ethernet connection. It has no fitted cellular modem. For cellular connectivity, compare the appropriate ICM-GE or Master Premium configuration against the project requirements.
This page describes AXON ICM-E and this model’s interfaces and capacities. The current modular family uses Master Premium or Master Lite, with compatible Node8 and Reader EV3 devices. It supports up to 240 subordinate devices and up to 1,000,000 cards per master. A modular master can be installed inside or outside the cabin; the output counts and capacities of different models are not interchangeable. Read how the AXON system works.
What the board does for the site
Four relays on the controller
Four relay channels, CH1 to CH4, are wired straight to the board's terminal blocks. A door strike, a garage gate, a barrier and an alarm channel can all be driven from the controller that made the decision, with no bus device in between and nothing to address.
Readers connect directly
An RS-485 port carries the encrypted AXON reader protocol for a URX-Secure, and a Wiegand port takes any third-party 26-bit reader on D0/D1. Both terminals supply 12 V to the reader, so a door needs one four-core cable and no separate power run.
The decision stays on the board
The master stores the configured permissions locally for access decisions. Card capacity, synchronization and behavior during a network outage are confirmed for the firmware installed on this Ethernet variant.
Two CAN buses when the site grows
The two CAN interfaces provide connections for compatible expansion nodes. Plan the number of nodes, addressing, power and outputs for the selected firmware and installation. Additional contacts can serve more signals without treating each relay as a complete door controller.
Per-node encrypted CAN link
Access events and commands between the master and compatible nodes are encrypted and authenticated, with checks against invalid or repeated messages. The installed versions and provisioning must match the intended protected connection.
One wired uplink, used sparingly
Ethernet connects to AXON management over MQTT/TLS with DHCP addressing. It carries database synchronisation, events and remote updates; the access decision stays on the board. This variant has no cellular modem, SIM slot or antenna.
A door on the board itself
Card presented
A resident taps a DESFire EV3 card on a URX-Secure on the RS-485 port, or a legacy card on the Wiegand port.
Credential arrives
The reader hands the authenticated credential to the controller over the reader port — no bus hop, no node in between.
Local lookup
The master finds the record in its on-board database and checks the permissions and the validity dates.
Relay pulses
On a grant it pulses the matching channel of CH1 to CH4 and records the event for the server.
Readers and doors first, bus second
Readers and 4 relays
RS-485 and Wiegand provide connections for compatible readers. Four local relay contacts can serve suitable control inputs or rated loads. Check the reader supply, connected equipment and electrical limits before selecting the wiring.
RS-485 A/B · Wiegand D0/D1 · CH1–CH4Two CAN connections for expansion
Two CAN interfaces organize compatible node groups. Route and power each segment according to the installation plan. Confirm addressing, supported node count and bus behavior with the selected controller firmware.
Two CAN interfaces · configuration-specific capacityEthernet only
Ethernet carries MQTT over TLS, with DHCP or a reserved address. Use a dedicated switch port or managed VLAN on the building network. This variant has no cellular connection.
Ethernet · MQTT/TLS · RJ-45The numbers, from the datasheet
Values describe the v1.4 board and shared AXON master platform. Confirm the electrical requirements and compatible configuration for the intended installation.
| Role | Ethernet master with local contacts and compatible expansion |
|---|---|
| Board | AX-MAIN-02, hardware v1.4 |
| Card database | Local database; capacity confirmed for the installed firmware |
| Access decision | Local, offline; no network request for access |
| Permission model | Permissions per node and output, with validity dates |
| Real-time clock | On-board RTC with coin-cell backup |
| Relay outputs | 4 channels (CH1–CH4), relays, dry contacts |
|---|---|
| Encrypted reader port | RS-485 (A / B / GND) with 12 V reader supply |
| Legacy reader port | Wiegand (D0 / D1 / GND) with 12 V reader supply |
| Card platform | MIFARE DESFire EV3 via URX-Secure; Wiegand 26-bit for retrofit |
| Ports | 2× Classic CAN 2.0B, 11-bit IDs |
|---|---|
| Bit rate | Confirm with the compatible firmware and node configuration |
| Addressing | Compatible node count confirmed per firmware and installation |
| Segment power | Separately switched per port |
| Termination | 120 Ω at the two physical ends of each segment |
| Ethernet | Ethernet 10/100, RJ-45 |
|---|---|
| Cellular | Not fitted — this is the wired variant |
| Cloud protocol | MQTT over TLS, port 8883 |
| Cloud role | Database sync, events, OTA — never the access decision |
| Firmware update | Remote updates with integrity verification |
| Node link | Encrypted and authenticated access messages |
|---|---|
| Key model | Individual node identity and provisioning |
| Anti-replay | Checks against repeated or invalid access messages |
| Reader link | Encrypted AXON protocol on RS-485; Wiegand is cleartext by nature |
| Input | 12 V or 24 V DC |
|---|---|
| Indicators | Status LEDs: CAN 1, CAN 2, Ethernet, error, general status |
| Controls | Bus-power button, reset button, service button |
Terminals & connectors
First CAN segment to AXON Nodes. Leave unused on a site that only needs the on-board doors.
Second, independent segment — a separate riser, wing or entrance group.
Encrypted AXON reader port with reader supply on the same block; one four-core cable per door.
Third-party 26-bit reader input with reader supply, for retrofits that keep existing readers.
Four dry-contact channels for strikes, gates, barriers or signal lines.
Uplink to the AXON cloud over MQTT/TLS. DHCP by default.
12 V or 24 V DC. Size the supply for the controller plus every reader and lock it feeds.
ICM-E or ICM-GE?
| Aspect | AXON ICM-E | AXON ICM-GE |
|---|---|---|
| Uplink | Ethernet only — needs a switch port on site | Ethernet plus LTE over an Axon Network soft SIM |
| First access points | Four relays and two reader ports on the board | Reached through an AXON Node on the CAN bus |
| Smallest useful system | One controller with Ethernet and four local relay contacts | One board plus one Node per door or landing |
| Growth path | Same two CAN ports — add Nodes when needed | Two CAN interfaces; node capacity confirmed for the selected configuration |
| Running cost | No SIM, no data plan | Connectivity included with the Axon Network SIM |
Where AXON ICM-E fits
Typical configurations we size for integrators. Every scenario below is a planning example, not a customer reference.
Plan contacts and readers together
In a clinic, the four contacts can be assigned to entrance, staff-door and other equipment commands. The installer separately plans reader connections, lock power and free exit. Where additional reader interfaces or outputs are needed, compatible expansion nodes complete the arrangement.
Keeping the readers already on the wall
A building has a Wiegand reader it wants to retain. ICM-E can connect that reader to its Wiegand input and use a relay contact for the door command, matched to the lock interface and supply. Additional readers need separate compatible interfaces.
Local contacts now, expansion later
A small building starts with the entrance and garage on the board. When the upper floors are fitted out, AXON Nodes go onto CAN port 1 on a twisted pair and the same controller, the same database and the same cards cover them.
Where a SIM makes no sense
A site with structured cabling and a managed switch has no use for a cellular modem, an antenna or a data plan. The ICM-E drops the lot and puts a dedicated VLAN port between the controller and the AXON cloud.
Pricing and configuration
Considering AXON ICM-E for your project? Compare economical and Premium configurations, then adjust the budget for elevators, access-controlled landings, doors, garages and credentials.
- One-elevator system · inside or outside
- 100 €+
- One-elevator system · inside and outside
- 200 €+
- Cards / tokens · each, wholesale
- 3 €+
Indicative starting prices for system configurations. Your project quote specifies the selected boards, equipment, installation and services.
AXON ICM-E FAQ
What exactly is different from the AXON Master (ICM-GE)?
Can I still add floor nodes later?
Can I mix an encrypted AXON reader and an old Wiegand reader?
What happens if the network drops?
Which one should I buy?
Is it available now?
Plan the outputs and expansion together
Tell us the entrances, doors and readers. We will say whether the ICM-E covers it on its own, or whether the ICM-GE and per-floor nodes are the better fit.



