Doors.NET provides support for several Assa Abloy wireless locks featuring Aperio technology and both wireless and wired IP Locks. These locks can be used with or without hard-wired Keri controller-managed doors on the same system, providing you with the utmost in deployment flexibility. The Aperio locks are only supported with the NXT-MSC (Mercury Powered 2 or 4 door controllers).

Aperio is the smart technology that enables mechanical locks to be wirelessly linked to an existing access control system. The heart of Aperio is a short-distance, wireless communication protocol, designed to link with an online electronic access system with an Aperio enabled mechanical lock.

Each lock requires a hub for its wireless link, the hub connects into a bus of an Mercury-Powered NXT controller. Each controller can manage up to 16 Aperio hubs/locks.

This section provides information regarding the setup process in Doors.NET, adding the relevant lock or hub type, and addressing information for the hub.

Installers and integrators who wish to use the Aperio range of products with Doors.NET MUST be certified by ASSA Abloy. Keri Systems DOES NOT supply or support the software application which is required to configure the wireless locks. Keri Systems recommends that you contact your local ASSA Abloy supplier for further details about product training and support.

2.0 System Requirements

• Doors.NET software must at least be version 3.5.1.15 or greater
• The number of Aperio readers must be enabled on the license
• The number of Aperio readers per controller must be enabled
• The locks must already be paired to the hubs prior to setting up in Doors.NET

3.0 System Capacities

• 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)
• Maximum of 16 Aperio locks per NXT MSC controller
• 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 module on the same bus.

• You cannot use MS or Wiegand readers on the same bus as an Aperio hub/reader. A RIM will not come online if an Aperio device is on the same bus. Aperio uses a different communications protocol and there can only be one RS-485 protocol in use on the bus at any one time.

• Only Mifare or HID iClass credentials (depending upon lock type) are supported at this time

4.0 Supported Aperio Devices

The Aperio ribbon bar displays the supported wireless locking devices and the AH30 hub.

5.0 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.

• When using a 1-8 hub, add the AH-30 hub first. Then use the ASSA Aperio Programming Application (APA) tool to add the locks to the hub.
• When using a 1-1 hub, add the lock to the bus. The AH-15 hub is added automatically by the Doors.NET software.

6.0 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.

There is an 8-pin terminal block on the reverse of the hub for making the wiring connections to the controller.

6.1 RS-485 Wiring to NXT Mercury Powered Controller

6.2 Wiegand Wiring to NXT Mercury Powered Controller 

When connecting to the controller via Wiegand you must have a Reader Interface Module (RIM) plugged into the controller’s reader port and it needs to be configured for Wiegand (Refer to the RIM Installation guide for setup instructions. The hub is wired into the 8-pin terminal block connected to the RIM.

6.3 Dip Switch Setting:

• Switch 10 - Antenna set to INT not EXT

6.4 Set Comm Address

• In Doors.NET > Hardware Settings click on the bus with the hub
• Note the comm number shown in the grid
• Set the comm dip switches on the hub to match the comm number in the grid (refer to the dip switch table at the bottom of the page)
• The comm address set on the hub must match the address shown in the software or else the hub will not come online.

7.0 Adding to the NXT Mercury Powered Controller

Highlight the controller’s bus in the hardware tree and select from the Aperio ribbon the device(s) you wish to add.

NOTE: If the Aperio icons are not available, please refer to License Manager permissions to ensure that your system is enabled for Aperio.

Addressing the Hub

The address of the hub is determined by Doors.NET. Refer to the Comm Address field in the hub properties to determine the device address for the hub.

This addressing follows a specific pattern depending upon the types of hubs being installed. Refer to the table below appropriate to your installation.

NOTE: Once the hub has been added to an NXT-MSC controller you MUST perform a RAM reset. The controller will re-configure the RS-485 protocol for Aperio devices. Only other Aperio devices can be used on that bus; no other peripheral type will be accepted.

Setting the Address on the Hub

There are 30 available address numbers for the hubs, set via the DIP switch on each hub. For example, Switch 1 in the UP position and all others DOWN will set the unit to address 1. All 30 address switch positions are shown in the figure below.