Paxton
UK's Leading Access Control — Net2 and Paxton10 with KNX Building Integration
Paxton Access (Brighton, UK, founded 1985) is the UK's largest access control manufacturer with over 15 million tokens installed worldwide and a dominant market share in UK commercial buildings, education, and healthcare. The Net2 Pro server-based system controls up to 500 doors from a central PC, while the newer Paxton10 uses PoE IP-connected controllers for cable-free installation. KNX integration is achieved via ACU auxiliary relay outputs wired to KNX binary input modules — door events trigger lighting, HVAC, and energy automation.
Role in our panels
How we use Paxton
Net2 architecture: Net2 Pro server software (Windows, SQL Server database) communicates with Net2 Plus ACUs (Access Control Units) via RS-485 daisy chain (up to 500 ACUs, 115200 baud, max 1200m cable). Each ACU controls 1 door: 2 RFID reader inputs (Wiegand D0/D1), 1 door lock relay output (electric strike or magnetic lock, 12/24V DC), 2 auxiliary relay outputs, 2 supervised inputs (REX button, door monitor). RFID readers: 125kHz EM4100 proximity (standard) or 13.56MHz Mifare DESFire EV2 (encrypted, high security). Anti-passback: Net2 supports time-based anti-passback to prevent card sharing. Cardholder database: SQL Server, photos, access levels, time zones, holiday calendars. KNX integration via ACU auxiliary relays: each Net2 Plus ACU auxiliary relay output (NO/COM, 2A 30V DC rated) connects to a KNX binary input module. Net2 Pro configures relay activation on access events: Access Granted → auxiliary relay 1 closes for 5 seconds. Door Forced → relay latches. ETS6 programs binary input: relay closure → DPT 1.001 telegram → lighting GA, HVAC GA, energy metering flag. Emergency unlock: KNX binary output relay → ACU REX input — on fire alarm, KNX relay activates REX input, ACU unlocks door (supplementary to hardware fire interlock). Paxton10 IP platform: Paxton10 replaces RS-485 with PoE IP controllers (single Cat6 cable per ACU from PoE switch — no separate PSU). Paxton10 app (Android tablet, web browser) for configuration. REST API (JSON/HTTP) available for advanced integration — access events as webhooks to Home Assistant, KNX IoT gateway, or custom scripts. Paxton10 still has auxiliary relay output for hardware KNX integration. For new-build projects: Paxton10 recommended. For retrofit where RS-485 infrastructure exists: Net2 Pro upgrade. Market position: Paxton Net2 holds approximately 40% of the UK commercial access control market. Common in schools (6–200 doors), NHS trusts (200+ doors), corporate offices. Paxton partner ecosystem includes 3,000+ UK installers. Integration with BMS (Trend, Delta, Honeywell EBI) via Modbus adapter or BACnet/IP. KNX integration is installer-driven (KNX contractor wires ACU relay to KNX binary input) — no official Paxton KNX protocol, purely hardware.
Hardware integration via ACU auxiliary relay outputs wired to KNX binary input modules — door granted/denied/forced events trigger KNX lighting and HVAC automation. Emergency unlock via KNX relay to ACU REX input.
Used in these project types
Paxton products
Key components we install
Paxton Net2 Plus ACU (door controller)
RS-485 door controller for 1 door, 2 readers, lock relay, 2 aux relays for KNX integration
Net2 Pro server software (50 doors)
Windows access control server, SQL database, cardholders/time zones/reports, up to 500 doors
Paxton Net2 RFID proximity reader
125kHz EM4100 IP55 wall reader, Wiegand D0/D1 output, LED/buzzer feedback
Paxton10 PoE IP controller
PoE-powered single-door controller, REST API, web config, aux relay for KNX binary input
Paxton Mifare DESFire EV2 reader
13.56MHz encrypted smart card reader for high-security areas, Wiegand or OSDP output
Paxton FAQ
Does Paxton Net2 have a native KNX protocol?
No — Paxton Net2 does not support KNX at the software level. Integration is hardware-based: ACU auxiliary relay outputs (dry contact) wired to KNX binary input modules. For software integration, use the Paxton Net2 .NET API (Net2.OpenProtocol.dll) to subscribe to access events and send commands to KNX via a KNXnet/IP gateway using a third-party integration platform.
What cable is used for Net2 RS-485 daisy chain?
Paxton recommends 2-core shielded cable (0.5mm² minimum, typically CQR TP2/100 security cable) for RS-485. Maximum 1200m total chain length. Terminate with 120Ω resistor across A and B at the furthest ACU from the server. Do not use star topology — always daisy chain.
Can Paxton10 and Net2 coexist in the same building?
No — Paxton10 and Net2 are separate platforms with different server software and databases. For a building upgrade, replace Net2 ACUs with Paxton10 controllers progressively, migrating cardholder data via Paxton migration tools. Both systems cannot share cardholder databases in real time.
Need a panel with Paxton components?
We select, procure, assemble and certify. Free initial consultation.
Request consultation →