For Mercury controller integration, Allegion Schlage AD, LE, and NDE Series locks require a Mercury EP or LP (or Honeywell) controller. For this integration, EP and LP controllers are viewed as interface modules, and the AD, LE, and NDE Series locks are viewed as non-intelligent 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
The supported controller models are:
|AD-300||Allegion Schlage AD-300 hardwired electronic lock with an RS-485 interface. Must be connected to an EP or LP controller (see datasheet).||
|AD-400||Allegion Schlage AD-400 wireless electronic lock. Requires the PIM400 wireless communication module to connect to the EP or LP controller (see datasheet).||
|PIM400-485||Allegion Schlage PIM400-485 is an RS-485 communication module, capable of connecting up to 16 AD-400 wireless locks to an EP or LP controller (see datasheet and wiring diagram).||
|PIM400-1501||Allegion Schlage PIM400-1501 is a PIM-485 module pre-wired to a Mercury EP1501 or LP1501 controller (see 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 EP or LP 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 EP or LP controller.||
|LE||Allegion Schlage LE wireless electronic lock. Requires an ENGAGE gateway to connect to an EP or LP controller. The lock connects to the gateway over Bluetooth, then the gateway connects to the EP or LP controller directly by an RS-485 interface.||
|NDE||Allegion Schlage NDE wireless electronic cylindrical lock. Requires an ENGAGE gateway to connect to an EP or LP controller. The lock connects to the gateway over Bluetooth, then the gateway connects to the EP or LP 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 an EP or LP controller (see datasheet). Up to 8 ENGAGE Gateways can be connected per RS485 data line.||
1 You can mix and match the locks within limits. For example, a single EP2500 or 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.
RS-485 wiring instructions
- TDA- to TR+
- TDB+ to TR-
- 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/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/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 are not supported:
- Request to enter
- Stalled motor
- Interior push button
- Deadbolt switch position
- Latch bolt
- Inputs on AD-300 and AD-400 locks are not configurable. This feature is not 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 is not precise.