Overview

This document outlines how to program and integrate an Allegion NDE series lock or Allegion LE series lock to Access It!® Universal.NET.

Access It! Universal.NET Licensing
The following licensing option must be enabled within the Access It! Universal.NET dongle and is a per integrated reader count license.

• Integrated Reader Count - 1/x

Required Components

The following components are required to complete the integration.

• Access It!® Universal.NET min s/w v5.2
• One of the following EP/LP controllers
  • EP-1501 PLUS min f/w 1.211
  • EP-1502 min f/w 1.250 (Access It! Universal.NET 6.4 or Greater)
  • EP-2500 min f/w 1.211
  • EP-4502 min f/w 1.250 (Access It! Universal.NET 6.4 or Greater)
  • LP-1501 min f/w 1.269 (Access It! Universal.NET 6.4 or Greater)
  • LP-1502 min f/w 1.269 (Access It! Universal.NET 6.4 or Greater)
  • LP-2500 min f/w 1.269 (Access It! Universal.NET 6.4 or Greater)
  • LP-4502 min f/w 1.269 (Access It! Universal.NET 6.4 or Greater)
• ENGAGE Gateway min f/w 1.38.08
• NDE or LE Series lockset

Hardware / Wiring References

Up to 16 ENGAGE Gateways can be installed to a single EP controller. An individual ENGAGE Gateway can have a maximum of 10 NDE/LE Locks. For performance reasons, it is strongly recommended that no more than 8 Gateways be connected to a single RS-485 communication port. The total number of readers cannot exceed 64 per SCP. When used with a EP-1501PLUS, the maximum number of NDE/LE locks cannot exceed 16.

Configuring The ENGAGE Gateway

The ENGAGE gateway and NDE lock must be commissioned using the Allegion phone application. The following settings must be applied

• Each ENGAGE Gateway must be configured for RSI Mode
• Each ENGAGE Gateway must have a unique RS-485 address
  When using any SCP other than EP/LP-2500 set the ENGAGE Gateway starting at address 1.
• Each ENGAGE Gateway must have a unique range of sequential low and high door addresses
• Each ENGAGE gateway must have at least one NDE/LE lock paired to it
• To preserve battery, the NDE/LE lock should have the internal WiFi disabled

Access It! Universal.NET

1. Install and configure the EP controller to communicate with Access It!® Universal.NET
2. Navigate to the Hardware menu
3. Select SCP’s
4. Edit the EP controller
5. Set Port speed to 9600 for appropriate port
   The EP Channel that the ENGAGE Gateway wired to.
6. Set Protocol to Schlage PIM for appropriate port
   The EP Channel that the ENGAGE Gateway wired to.
7. Click Save
   The EP board will reset.
8. From the left hand tree, expand SCP’s
9. Expand the EP controller
10. Select SIOs
11. From the right hand pane, edit the SIO that has the address of the ENGAGE Gateway
12. Name the ENGAGE Gateway
13. Set Model to Schlage ENGAGE Gateway
14. Check Device Installed
15. Set Channel accordingly
    The EP Channel that the ENGAGE Gateway wired to.
16. Select the Options tab
17. Set Number of Readers accordingly

Tamper Alarm

When a phone connects to the ENGAGE Gateway via bluetooth, the SIO will report a generic Tamper Alarm. It is recommended to change the default reporting to better indicate a BLE Tamper. To change this event, the following steps can be taken

1. Navigate to the Hardware menu
2. Select SIOs
3. From the right hand pane, edit the SIO that has the address of the ENGAGE Gateway
4. Select the Event tab
5. Locate the Tamper Alarm event
6. Change the message to be 'BLE Tamper Alarm'
7. Click Save
8. Locate the Tamper Normal event
9. Change the message to be 'BLE Tamper Normal'
10. Click Save

More Information

• When REX is held, it is possible the lockset will report a door open/close event regardless if the door is actually used
• After a magnetic tamper event, the door will always report a open state until re-calibrated
• Low battery report will only report one time
• Door unlock times will always use what is programmed in Access It! Universal.NET regardless of how mobile app is configured