AD-400 Lock Setup Guide

AD-400 Lock Setup Guide

1.0 Introduction

This section explains how to setup and use the Allegion AD-400 wireless locks with the NXT Mercury Powered (MSC) controllers. These locks have extensive functionality and operating modes and are combined units consisting of the electric lock, credential reader, Request-to-Exit and Request-to-Enter sensors, door position switch and tamper guard.

Note: Effective from Doors.NET v5.2.0 you can mix and match ENGAGE Gateways, PIM-400s and AD-300s on the same bus. You can add up to 8 x ENGAGE Gateways, 8 x PIM-400s or 32 AD-300s (to each controller bus). Adding one of these supported devices will reduce the number of other devices that can be added. For example, if 4 x ENGAGE gateways are added you will then be limited to adding 4 x PIM-400s or 28 AD-300s.

AD-400 Schematic

Maximum Number of AD-400 Locks Per PIM-400 and Per Controller

  1. The maximum number of AD-400 locks per PIM-400 is 16.
  2. The maximum number of AD-400 locks you can add to an NXT-MSC 2D controller is 64.
  3. The maximum number of AD-400 locks you can add to an NXT-MSC 4D controller is 64.

Note: Effective from Doors.NET v5.2.0, when using NXT-MSC controllers you will need to delete the Keri NXT reader which is added to the bus by default and then configure the protocol to support the Schlage RSI protocol before adding the PIM-400.


2.0 Hardware Requirements

2.1 Keri NXT Hardware Requirements

NXT-MSC Controllers

  • Requires NXT-MSC (Mercury Powered) controllers (Mercury (SCP), standard NXT or PXL controllers do not support Allegion wireless locks).
  • The NXT-MSC controllers must be using the latest firmware (1.294) at the time of writing.


2.2 Allegion Hardware Requirements




SUS App and Cable
            PIM 400/485 KRI Module   AD-400 Lockset        SUS For Android App and USB cable



3.0 Software/Licensing Requirements

Access the License Manager to verify you have the correct license settings: Start menu >> All Programs >> Doors.NET >> License Manager.

  • Current Doors.NET Software (Version 5.2.0 at the time of writing)
  • Mercury Powered controller licensing
  • Mercury gateway installed and configured
  • Allegion enabled

The following screen shots are the required settings within the License Manager

3.1 License Capacities

  • Number of Gateways - 1 or more
  • Readers - Allegion - 1 or more
  • Readers - Allegion per controller - 1 or more


Allegion - Image 1



3.2 Hardware Capacities

Supported Hardware

Allegion - True
Keri Systems - NXT (MSC) - True


Allegion - Image 2


3.2 User Interface

Distribution Interface - False

Allegion - Image 3


Note: Before getting started on setting up the AD-400 lock, verify the following:

  • Ensure the AD-400 batteries have adequate voltage and are installed properly.
  • The PIM 400-485 KRI and AD-400 lock(s) have to be reset to factory defaults, (this will also remove any construction credentials).


The reset procedure is explained at the end of this document.


4.0 Configure the AD-400 With the Schlage™ Utility Software and Android App

The Schlage Utility Software (SUS) is an application that runs on supported Android devices. It is used to configure, edit and program all supported devices.

You can use the app to; edit the AD-300 lock properties, update the lockset's firmware, couple the HHD to the device, set the date/time and run diagnostics.

This section assumes that you have already:


  • Downloaded and installed the SUS Android app.


4.1 Logging into the App for the First Time

  1. Once the application is downloaded, you must change default password.
  2. Select User Type: Manager or Operator.
  3. Enter Default Password: 123456.
  4. You will be prompted to enter a new password and confirm the new password.

    >> New password must not be a default password, subset or super set of default password.

  5. You must log in again with User Type: Manager or Operator and new password.


4.2 Couple the Mobile device to the AD-400

This section explains how to connect and couple the mobile device to the AD-400 locks:


Note: The mobile device must have file transfer via USB enabled to function properly.

  1. Start the Schlage Utility Software for Android (SUS-A).
  2. Connect the SUS-A Cable to the mobile device. A pop-up will appear, “Allow Schlage Utility Software to access SUS A-CABLE?” Click OK to continue.
  3. Connect the SUS-A Cable into the lock’s USB port located at the bottom of the exterior housing.

    SUS USB Connection

  4. Press the Schlage button twice to begin communication.
  5. The lock will be displayed on the screen.
  6. On the mobile device, select Device Options.
  7. Remove the top inside lock cover.

  8. Press and hold the Inside Push button. Then press and release the tamper switch three times.

  9. Release the Inside Push button. On the lock, the Inside Push button LED will illuminate.

  10. On the mobile device, select Couple mobile device to Device.

  11. When Coupling is successful, a message will be displayed on the screen.


Note: The mobile device will use a default Coupling Password (123456) when coupling with a device. The Coupling Password should be changed to provide increased security for your locks.



5.0 Couple the PIM400 With the Schlage™ Utility Software and Android App

AD-Series devices can be coupled, or authenticated, with the mobile device. This provides enhanced security by ensuring that the device will only communicate with mobile device(s) to which it has been coupled. Once the device has been coupled, the coupling password is passed to the device from the mobile device during programming.


Note: Mobile devices with the same coupling password can program the same devices. Once the mobile device and the device are coupled, the coupling password is disabled in the PIM400 and any mobile device with the correct coupling password will automatically couple with the PIM400.


  1. Remove the PIM400 cover.
  2. Connect the mobile device to the PIM400 or PIB300 using the SUS-A cable. The PIM400 or PIB300 will be displayed on the mobile device screen.

  3. On the mobile device, select Device Options.
  4. On the PIM400, press and hold the LINK 1 button. Then press the LINK 2 button three times.

    PIM400 Diagram

  5. On the mobile device, select Couple mobile device to Device.
  6. When Coupling is successful, a message will be displayed on the mobile device screen.


  1. Connect the mobile device to the PIM400.
  2. Select Device Options.

  3. Select PIM Properties for the connected device.
  4. Select the Link tab.

  5. Select the door number from the drop-down box >> See the system administrator for the proper door number selection.
  6. The PIM400 will stay in link mode for up to 30 minutes.

  7. Put the lock (door) into link mode >> See the user guide that came with the lock for more information.
  8. The PIM400 will automatically exit link mode once linking is complete.


7.0 Put PIM400 Into Diagnostic Mode

  1. Connect the mobile device to the PIM400 and select Device Options.
  2. Select Demo mode and then select the door number from the drop-down box.
    • Card Data box: shows card data from credential when card presented to reader.
    • Unlock on Read: if enabled allows the door to be unlocked upon the reading of a card: the OEM has the ability to disable this feature (grayed out).


8.0 Update the PIM400 Firmware

For further information about updating the firmware on the AD-400 locks, or the PIM400, refer to page 11 of the SUS for Android User Guide.



PDF Icon The full Allegion SUS for Android User Guide can be viewed here:


9.0 Programming the PIM 400-RS485 Address

The RS485 Channel must be selected to the corresponding bus used on the NXT-MSC controller for proper operation .

  1. In the Android SUS app, select Device Options >> PIM properties >> Edit.
  2. Select the correct RS-485 address. The address number is determined by how many modules will be added to each of the controller buses.

    For example, if you are using a 4-door controller:
    → Bus 1 = The first PIM module on bus 1 is address 0, second is address 1, and so on...
    → Bus 2 = The first PIM module on bus 2 is address 0, second is address 1, and so on...
    → Bus 3 = The first PIM module on bus 3 is address 0, second is address 1, and so on...
    → Bus 4 = The first PIM module on bus 4 is address 0, second is address 1, and so on...

  3. Disconnect the HHD.
  4. Remove the USB cable from the PIM400/485 KRI and turn off the HHD.


Other lock and PIM settings may be configured by selecting Door Properties or PIM Properties from within the app. Other editable items include: Heart Beat and Comm Loss Mode - for these item settings consult the SUS for Android User Guide.



10.0 Connecting the NXT-MSC 2D/4D Controller to the PIM 400-485

Wiring the PIM 400/485 to an NXT-MSC Controller


NXT-MSC RS-485 port                                                                   PIM 400-485
PINLabelWire ColorPIN485 Connector Label
112VDC-- No Connection -- -- No Connection --
3IO +Green4TA -
4IO -White2TB +
  • Jumpers must be in place on J19 and J20

  • The PIM 400-485 wires directly to the NXT-MSC's 485 bus (4 conductor port). Take note which buss/es) are being used so these can be configured properly. (DO NOT POWER FROM NXT CONTROLLER, PIM MUST HAVE ITS OWN POWER SUPPLY)
  • Each NXT-MSC controller can handle up to 16 (max) AD-400 locksets per controller.
  • Additional PIM 400/485s installed on an NXT-MSC controller will not increase the 16 AD-400 MAX lock limit per controller.

  • More than 16 AD400 locks will require additional NXT-MSC controllers.



11.0 Configuring Doors.NET for the AD-400 and PIM 400-485

This section assumes the NXT (MSC) 2-door or 4-door controller is online, configured and ready to add the AD-400/PIM 400-485 to the database.


Note: Effective from Doors.NET v5.2.0, when using NXT-MSC controllers you will need to delete the Keri NXT reader which is added to the bus by default and then configure the protocol to support the Schlage RSI protocol before adding the PIM-400.

(Refer to the NXT (MSC) controller Quick Start Guide for further details about setting up and configuring this controller type with Doors.NET).

  1. Log in to Doors.NET and go to Setup >> Hardware Setup >> All
  2. On the hardware tree you will see the gateway node and the NXT (MSC) controller(s)
  3. Expand the controller and select the bus which the PIM400-485 is connected to.

    Add PIM400 icon

  4. Select the reader which is added to the bus, by default.
  5. Click on the Hardware Browser tab at the top of the screen and click the Remove icon.

    Reader Remove

  6. The default reader (NXT-3R) will be removed from the bus.
  7. With the bus still selected, locate the Protocol (Serial) setting in the bus properties.
  8. Change the protocol (Serial) setting from Keri Systems to Schlage RSI.

    Bus protocol Schlage

  9. Save the bus settings.
  10. You will be prompted to reset the controller - so go ahead with the reset.
  11. From the hardware ribbon, with the bus selected, click the Add PIM-400 icon.

    Add PIM400 Icon

  12. Click the ACCEPT button and a PIM-400 will be added to the hardware tree.
  13. Select the newly added PIM-400.
  14. From the hardware select ribbon bar, click on the ADD AD-400 icon.

    Add AD-400 Icon

  15. The AD-400 lock will also be added to the hardware tree.


AD400 on hardware tree


Linking the AD-400 to the PIM 400 using Doors.NET

The next step is to link the AD-400 lock to the PIM 400-485. The only prerequisite is that the lock must have been factory reset and the PIM400 has already been configured with the correct address.


To link the lock perform the following:

  1. Add the PIM 400 to the correct bus.

  2. Highlight the PIM 400 then add the AD-400 lock.
  3. Right-click the AD-400 lock and select Mode >> Link.


Software Linking



Setup and Configuring Credential Types

  1. Before setting up users or adding credentials to users, “Credential Types” must be configured to allow proper card and/or PIN operation.
  2. The Credential Types feature must be enabled on your license key within the Options section.
  3. While logged into the Doors.NET software, click Setup >> Credential Types.

    Credential Types

  4. From the Access Control tab, click Add Active Format.
  5. In the properties pane locate Format and select Standard 26-bit.
  6. For PIN operation leave the FC field set to 0. and leave the Offset field set to 0. (This format will allow the keypad to work in 26-bit mode with a FC of 0).
  7. For CARD operation set the FC field to the Facility Code programmed in the card(s) to be enrolled.
  8. Leave the offset field set to 0, click save.
  9. If using cards the above process will need to be completed for each facility code in use.



Enrolling a Card or a PIN

  1. From Home >> Cardholders, add a new cardholder and save.
  2. When adding a card or PIN to a cardholder ensure the 'Calculate Internal Number' option is unchecked.
  3. Enter the Imprint number (number printed on the card) or the PIN into the Cardnumber field.
  4. Leave the issue code at the default value of zero.
  5. Click the Add Card button then save.
  6. Assign the card record an access group from the Access Rights tab.
  7. This card will automatically be sent to the controller(s) and should work within a few seconds.


System Capacities

  1. Secure 900 MHz wireless communication, AES-128 encrypted
  2. Real time access control and monitoring
  3. Patent pending wireless lockdown/unlock feature via PIM400 in 10 seconds or less (preserves up to 2 year battery life)
  4. Powered by four (4) standard AA batteries, optional 8 AA battery pack available
  5. Weather resistant, exterior operating temperature: -31° to 151°F (-35° to 66°C)
  6. Additional wireless products also available
    - Wireless Portable Reader (WPR400) for muster stations, buses, etc.
    - Wireless Reader Interface (WRI400) eliminates running wires to remote doors, parking gates and elevator applications
  7. ANSI/BHMA A156.25, ANSI/BHMA Grade 1, UL294 and UL10C certified
  8. NXT-2D can support up to 2 PIM400-485
  9. NXT 4D can support up to 4 PIM400-485
  10. Each PIM400-485 can support up to 16 AD-400 wireless devices, not to exceed 16 wireless devices per NXT (MSC) controller.
  11. Wireless range up to 200’ in typical building construction, up to 1000' line of sight.



Supported Card Formats

Proximity cards (125kHz)

  • AWID®

  • GE/CASI®
  • HID®

  • Schlage®
  • XceedID®


Smart cards (13.65 MHz)

  • aptiQ™ MIFARE Classic

  • aptiQ™ MIFARE DESFire™ EV1
  • PIV and PIV-I compatible


Smart cards (13.65 MHz) - Reads card serial number only):


  • DESFire®




Resetting the AD-400/PIM 400-485

AD-400 Reset Procedure (to Factory Defaults)

(This will clear all the information programmed in the lock).

  1. Remove the top inside cover
  2. Press and hold the Schlage™ button until two (2) beeps sound (10 seconds) then release
  3. Press and release the Inside Push Button (IPB) three (3) times within 10 seconds... the button will beep and blink red with each press
  4. The Schlage™ button and IPB will both light green for one second and a one-second beep will be heard. This indicates that the lock has been reset... If IPB is not pressed 3 times within 10 seconds, two beeps with two red blinks indicating a timeout and procedure must be repeated.
  5. Replace the top inside cover.


PIM 400-485 KRI Reset Procedure (to factory defaults)

(This will clear all the information programmed in the device)

  1. Remove the main cover of the PIM400/485
  2. Press and hold both link buttons for over 3 seconds until the LEDs start to flash red several times. When complete the LEDs will flash green momentarily and unit will be reset... Identified as LINK1 and LINK2 inside the PIM400

  3. Replace the main cover

    • Related Articles

    • AD-300 Lock Setup Guide

      1.0 Introduction Allegion Schlage AD-300 networked, hardwired locks can be integrated seamlessly with the Doors.NET software when used with the NXT-MSC (Mercury-Powered controllers). You can connect and communicate with up to 32 AD-300s via the ...
    • AD Locks and Local Linkage Setup Guide

      1.0 Introduction The Allegion AD Series locks can be integrated with the Local Linkage feature to provide enhanced functionality and monitoring. Note: Both the AD-300 and AD-400 locks can be used with Local Linkage. 2.0 Ensure Advanced Local Linkage ...
    • Allegion - AD Series Lock Functions

      There are several lock modes that are supported by the AD Series locks. You can set one of the supported modes by performing the following: Highlight the AD lock in the hardware tree. Locate the Modes section and view the Extended Feature drop-down ...
    • Allegion NDE and LE Lock Integration - Full Reference Guide

      1.0 Introduction Keri can integrate with the Allegion LE and NDE wireless locks using Schlage Control™ technology. Installation and lock configuration is extremely simple and easy using the Allegion ENGAGE app and the setup in the Doors.NET software ...
    • Allegion NDE and LE Lock Integration - Quick Start Guide

      1.0 Introduction This quick start guide walks you through the process of setting up the Doors.NET integration between the Allegion Gateway and the Allegion NDE and LE locks. It assumes you have an existing Allegion ENGAGE 'Third-Party' account type ...