Integration of Allegion Schlage AD, LE, and NDE Series locks through Mercury require a Mercury EP, LP, MP, or Honeywell controller. For this integration, Mercury controllers are viewed as interface modules, and the AD, LE, and NDE Series locks are viewed as non-intelligent devices.
Synergis™ Softwire
11.5.3 supports the following hardware devices:
| Model | Description | Minimum compatible versions |
|---|---|---|
| IP controllers | A Mercury or Honeywell controller must act as an interface
module between the Synergis™ unit and the AD, LE, and NDE Series locks. The
supported controller models are:
See also Supported Mercury firmware versions in Synergis Softwire 11.5.3. |
|
| AD-300 | Allegion Schlage AD-300 hardwired electronic lock with an RS-485 interface. Must be connected to an EP, LP, or MP controller. See the AD-300 datasheet. |
|
| AD-400 | Allegion Schlage AD-400 wireless electronic lock. Requires the PIM400 wireless communication module to connect to the Mercury controller. See the AD-400 datasheet. |
|
| PIM400-485 | Allegion Schlage PIM400-485 is an RS-485 communication module, capable of connecting up to 16 AD-400 wireless locks to a Mercury controller. See the PIM400-485 datasheet and wiring diagram. Up to 8 PIM400-485 modules can be connected per RS-485 data line. |
|
| PIM400-1501 | Allegion Schlage PIM400-1501 is a PIM-485 module pre-wired to a Mercury EP1501, LP1501, or MP1501 controller. See the PIM400-1501 datasheet and wiring diagram. |
|
| WPR400 | Allegion Schlage WPR400 is a Wireless Portable Reader that uses the same credential reader modules offered with an AD Series electronic lock. WPR400 is represented as an AD-400 lock in Security Center. Requires the PIM400-485 to connect to the Mercury controller. |
|
| WRI400 | Allegion Schlage WRI400 is a Wireless Reader Interface that is represented as an AD-400 lock in Security Center. WRI400 provides wireless connectivity to one reader2, door strike, door monitor, request-to-exit, and reader tamper. Requires the PIM400-485 to connect to the Mercury controller. |
|
| LE (legacy and model B)3 | Allegion Schlage LE wireless electronic lock. Requires an ENGAGE Gateway to connect to a Mercury controller. The lock connects to the gateway over Bluetooth, then the gateway connects to the Mercury controller directly by an RS-485 interface. |
|
| NDE (legacy and model B)3 | Allegion Schlage NDE wireless electronic cylindrical lock. Requires an ENGAGE Gateway to connect to a Mercury controller. The lock connects to the gateway over Bluetooth, then the gateway connects to the Mercury controller directly by an RS-485 interface. |
|
| ENGAGE Gateway | Allegion Schlage ENGAGE Gateway includes support for RS-485 communication module, capable of connecting up to 10 NDE or LE wireless locks to a Mercury controller. See the ENGAGE Gateway datasheet. Up to 8 ENGAGE Gateways can be connected per RS-485 data line. |
|
1 You can mix and match the locks within limits. For example, a single LP2500 can control eight AD-300 locks, 20 AD-400 locks and six NDE Series locks.
2 Even though the WRI400 physically supports two readers, only one reader is supported because of a software limitation that makes the other reader port and I/O unusable.
3 Model B LE and NDE locks require Mercury LP 1.30.0 firmware or later.
RS-485 wiring instructions
When wiring an AD-300, a PIM400, or an ENGAGE Gateway module to an RS-485 bus on an EP, LP,
or MP controller, wire the connectors as follows:
- TDA- to TR+
- TDB+ to TR-
Limitations
The Allegion Schlage AD, LE, and NDE Series lock integration has the following limitations:
- Allegion Schlage devices and Mercury MR panels cannot be mixed on the same RS-485 bus.
- All Allegion Schlage devices connected to the same RS-485 bus must each have a different address.
- Door numbers cannot overlap between different locks on the same RS-485 bus, even if they are controlled by different PIM400 modules and AD-300 locks. For example, if you have a PIM400 with doors/locks 0 - 10, your next PIM400 must start with door or lock number 11 or nothing will work or come online.
- An AD-300 lock has a door number that is the same as its RS-485 address, and cannot overlap with any doors in the range used by a PIM400 on the same bus. For example, if you have a PIM400 at address 0 with doors or locks 0 - 10, you must assign your AD-300 an address between 11 and 31.
- All wireless locks (AD-400 locks under a PIM400; NDE and LE Locks under an ENGAGE Gateway) must have consecutive door numbers.
- Not all AD-300 and AD-400 messages and features are supported. The following lock
features aren’t supported:
- Request to enter
- Stalled motor
- Interior push button
- Deadbolt switch position
- Latch bolt
- Inputs on AD-300 and AD-400 locks aren’t configurable. This feature isn’t supported by the hardware.
- Manual unlock and relock commands can take more time than expected to be executed. This is because these commands rely on a Wake on Radio (WoR) message for which the timing isn’t precise.