ENGAGE NDE/LE Mercury SIO Communication
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.
| EP-2500 Channel (Port 2 or 3) | ENGAGE Gateway (configured for 2-wire RS485) |
| TR+ | TX- |
| TR- | RX+ |
| GND | GND |
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 an EP-1501 PLUS 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
- Install and configure the EP controller to communicate with Access It!® Universal.NET
- Navigate to the Hardware menu
- Select SCP’s
- Edit the EP controller
- Set Port speed to 9600 for appropriate port
The EP Channel that the ENGAGE Gateway wired to. - Set Protocol to Schlage PIM for appropriate port
The EP Channel that the ENGAGE Gateway wired to. - Click Save
The EP board will reset. - From the left hand tree, expand SCP’s
- Expand the EP controller
- Select SIOs
- From the right hand pane, edit the SIO that has the address of the ENGAGE Gateway
- Name the ENGAGE Gateway
- Set Model to Schlage ENGAGE Gateway
- Check Device Installed
- Set Channel accordingly
The EP Channel that the ENGAGE Gateway wired to. - Select the Options tab
- 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
- Navigate to the Hardware menu
- Select SIOs
- From the right hand pane, edit the SIO that has the address of the ENGAGE Gateway
- Select the Event tab
- Locate the Tamper Alarm event
- Change the message to be 'BLE Tamper Alarm'
- Click Save
- Locate the Tamper Normal event
- Change the message to be 'BLE Tamper Normal'
- 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