Floor Access Node

AXON Node

Per-floor RS-485 to CAN bridge that never decides alone
AXON NodeReady for use

Per-floor bridge between the landing reader and the AXON Master: it takes the reader's authenticated card event over RS-485, forwards it on the encrypted CAN backbone, and pulses two relays only when the master says so.

CAN 2.0B 250 kbps
Encrypted CAN connection
2 relay outputs
RS-485 reader bus, 115200
AXON Node — 3D board render
250kbps
Classic CAN 2.0B backbone
CANnodes
Capacity confirmed per configuration
2relays
Master-commanded outputs
< 10ms
Measured tap-to-verdict
800ms
Fail-closed deny timeout
Overview

The floor node that never decides alone

AXON Node is the per-floor endpoint of the AXON architecture. It sits at an elevator landing or building entrance, close to the reader. It forwards authenticated reader events from RS-485 to the master over CAN, then drives its two outputs when the master grants access. The installer sets the bus address with the on-board DIP switches.

The master decides access. The card database, floor permissions and time windows stay on the master. The node forwards the reader event and waits for a valid response before commanding the assigned outputs. If the decision does not arrive within the configured window, the request is denied.

Access traffic between each node and the master is encrypted and authenticated, with checks against invalid or replayed messages. Each node has its own identity in the system. Protection depends on the installed firmware, correct key provisioning and secure mounting; the documented version does not yet provide hardware-backed key storage.

This page describes AXON Node 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.

Key capabilities

What the board does for the site

RS-485 to CAN bridge

The node connects the landing reader over RS-485 and the building master over CAN. The same compatible AXON reader can therefore serve a cabin or landing installation.

Individual node identity

Each node is identified separately so its access events, outputs and communication status can be associated with the correct point in the building. Record the address when installing or replacing a board.

Protected reader and master links

Both the reader connection and the master connection protect access messages with encryption and authentication. Repeated or invalid messages are checked before an output can be commanded.

Two master-commanded relays

The two outputs respond to the master’s authorised command. They can be assigned to suitable door-release or call-control inputs, with the pulse duration set for the receiving equipment. A denial does not activate an output.

DIP-switch addressing

The DIP switches set the node address and its application type: floor, door, garage or ramp. This gives the technician a visible local setting to check when commissioning or replacing a unit.

Communication recovery and monitoring

A watchdog helps recover from a stalled program, while communication monitoring reports whether the node and reader are available. Connection faults can be investigated at the affected point without changing the permission policy for the building.

How it works

One landing tap, reader to master and back

Reader authenticates card

The landing reader runs mutual authentication with the DESFire EV3 card and sends the card event (flags, UID) to the node over the secured RS-485 link at 115200 baud.

Node re-wraps for CAN

The node verifies the reader event and forwards it over the protected CAN connection to the master.

Master decides

The master checks the card and its permission for that access point in the local database, then returns the decision.

Node executes the verdict

The node returns the result to the reader for its indicators and activates only the authorised outputs for the configured time.

If the master does not return a valid decision within the configured window, the request is denied. Communication monitoring helps the technician identify a disconnected reader or node.
Communication Architecture

Two buses, two secure sessions, one verdict path

Upstream · backbone

CAN 2.0B, 250 kbps

Classic CAN at 250 kbps connects the node to the building master. Use a linear backbone with short stubs and 120 Ω termination at the two physical ends only. The selected installation plan determines the address allocation on each segment.

Classic CAN · 250 kbps · 120 Ω at ends
Downstream · reader

RS-485, 115200 8N1

The half-duplex RS-485 connection carries card events from a compatible AXON reader and returns the access result for its indicators. It uses the same protected reader connection as the cabin master.

RS-485 · authenticated reader connection
Access protection

Authenticated communication

The master and node verify their communication before exchanging access commands. Key protection and provisioning are checked against the installed version during commissioning; hardware-backed key storage is not active in the documented node version.

Encryption · authentication · anti-replay
Technical specifications

The numbers, from the datasheet

Values are taken from the node firmware and the AXON system specification (June 2026). Bench-measured figures are marked as such; unconfirmed hardware limits are left out.

CANnodes
Capacity by configuration
AES-128
Encrypted access communication
< 10ms
Measured tap-to-verdict
System01
RoleRS-485 to CAN bridge for a local access point
AddressingOn-board DIP switches
ApplicationsFloor / door / garage / ramp
DecisionPermission decided by the master
Connectivity02
CAN busClassic CAN 2.0B, 250 kbps
Nodes per backboneAddress allocation and capacity depend on the master, compatible firmware and installation
Termination120 Ω at both physical ends only
Reader connectionRS-485, 115200 bps, half-duplex
Legacy reader inputWiegand-26 D0/D1, retained for compatible configurations
Outputs & status03
Outputs2 relay outputs
Output controlMaster command with configured pulse duration
Missing decisionRequest denied when no valid master response arrives
MonitoringNode and reader connection status
Security04
Access messagesEncrypted and authenticated
Anti-replayChecks against repeated or invalid commands
Key protectionHardware-backed storage is not active in the documented version
Resilience05
WatchdogAutomatic recovery from a stalled program
CommunicationBus recovery and reader connection monitoring
Master responseRequest expires as deny if no valid decision arrives
Power & mechanical06
Supply input12–24 V DC
MountingIndoor IP30 enclosure, DIN-rail; IP65 in damp spaces
CAN cablingShielded twisted pair, stubs ≤ 30 cm, no star wiring

Connections and installation

CAN H / L / GND

Building backbone. Terminate only at the two physical ends.

RS-485 A / B

Connection to the compatible landing reader, using twisted-pair cable.

Two outputs

Assigned to the receiving control inputs during installation.

Wiegand D0 / D1

Retained input for compatible legacy-reader configurations.

DIP addressing

Set and document the address and application type for each node.

Read the full technical guide Request the datasheet PDF Confirm the ratings and interface requirements for your installation.
Compared

How it compares to off-the-shelf floor controllers

AspectAXON NodeOff-the-shelf floor controllers
Reader-to-controller linkAuthenticated, encrypted RS-485 access messagesWiegand carries credential data without encryption on the reader cable
Backbone to the decision-makerA shared CAN connection to the master, with addressing and capacity matched to the installationAn Ethernet/PoE drop and controller per floor, or OSDP that ties you to OSDP-only readers
Compromise blast radiusOne node — its session is dropped and re-authenticated; other nodes keep their own keysA single shared bus key, or no bus encryption at all
Deployment scenarios

Where AXON Node fits

Typical configurations we size for integrators. Every scenario below is a planning example, not a customer reference.

Residential · 20 floors

One node per landing on a single riser

A 20-floor residential tower with one elevator puts a node beside each landing reader. All nodes share one CAN backbone through the riser, terminated at the basement master end and at the machine room. The master holds the floor-to-credential table; nodes capture taps, forward them and pulse the call relay on grant. Roughly 80 m of bus, well inside margin.

Office · 12 floors, multi-tenant

Landing nodes and door nodes on the same bus

A 12-floor office with several tenants per floor uses nodes at each landing and further nodes on internal doors. The DIP application settings mark landing nodes and door nodes so the master applies the right policy to each. One backbone carries both; per-node keys and hardware filtering keep them logically separate without a second cable run.

Hotel · staff-only floors

Stricter policy without different hardware

A hotel reserves two floors for staff areas and places nodes at those landings. Guest credentials are simply absent from the authorised list for those floors, and stricter time windows apply. Node behaviour is identical everywhere; the difference lives entirely in the master's centrally managed permissions, changed without a visit to the floor.

Hospital · controlled wings

Visiting hours as a single configuration push

A hospital guards wards with different visiting policies. Time-windowed access is applied per credential class — medical staff, administration, cleaning, contractors, family. Because the master is authoritative and the node fails closed, changing visiting hours is one configuration change at the master; nothing changes on the per-floor hardware and no door opens on a silent master.

Project budget

Pricing and configuration

Considering AXON Node 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.

Questions integrators ask

AXON Node FAQ

How is each AXON Node addressed on the CAN bus?
The on-board DIP switches set the node address and application type. Each address must be unique on its segment and recorded in the installation documentation. Confirm the available address range for the installed configuration.
Are the messages on the CAN bus encrypted?
Access messages on the documented CAN connection are encrypted and authenticated, with checks against replay. The installer should confirm that the selected master, node version and configuration use the same protected connection.
Does the node make access decisions on its own?
No. The node forwards the verified reader event and applies the master’s decision. A missing or invalid response is not permission to activate an output. The installed firmware configuration must match this master-controlled operation.
Why 250 kbps and classic CAN?
Classic CAN at 250 kbps suits a shared backbone through the building. Bus length, cable quality, termination and the selected node configuration are considered together when planning the route. This node connection does not use CAN-FD.
What is the RS-485 port used for?
It connects the landing reader to the node at 115200 bps, half-duplex, using the protected AXON reader connection. Reader and node compatibility is confirmed during installation.
What should be checked when securing a node?
Use the correct firmware and provisioning process, protect the enclosure from unauthorised access and document replacements. The documented version does not yet provide hardware-backed key storage, so physical installation remains part of the protection plan.
Size the backbone for your riser

Ready to specify AXON Node?

Tell us the floor count, where the master will sit and which landings need a door relay as well as a call relay. We size the CAN backbone, termination and node addressing for your building. Availability on request.