Keri Systems Doors.NET Manual - Manual (Page 261)

Doors.NET Reference Manual
- 261 -
Requirements
l
Doors.NET software must at least be version 3.5.1.15 or greater
l
The number of Aperio readers must be enabled on the license
l
The number of Aperio readers per controller must be enabled
l
The locks must already be paired to the hubs prior to setting up in Doors.NET
Limitations
l
25M range between lock and hub (AH-30)/ 5M for the AH-15 (the stated range is
subject to the hub being installed within ideal environmental conditions)
l
Maximum of 16 Aperio locks per NXT MSC controller
l
When the Aperio hub is being used the communication protocol of the bus is
changed. As a result you cannot use NXT peripheral hardware such as a 4x4 mod-
ule on the same bus.
l
Only Mifare or iClass credentials (depending upon lock type) are supported at this
time
Supported Aperio Devices
The Aperio ribbon bar displays the supported wireless locking devices and the AH30
hub.
Communication Hubs
Doors.NET supports both the AH-15 and the AH-30 hubs. The AH-15 hub pairs directly
with a single Aperio wireless lock. The AH-30 hub is capable of supporting up to 8
Aperio locks. Multiple hubs can be connected to a single NXT reader port, covering a
maximum of 16 locks per controller.
l
When using a 1-8 hub, add the AH-30 hub first. Then use the ASSA Aperio Pro-
gramming Application (APA) tool to add the locks to the hub.
l
When using a 1-1 hub, add the lock to the bus. The AH-15 hub is added auto-
matically by the Doors.NET software.
Installing the Hub
Connecting the hub to the NXT Mercury Powered controller using the RS-485 interface
is the default method. It is the same wiring for the AH-15 and the AH-30.