# AD Series Wired Lock Setup

Verkada [access controllers](https://docs.verkada.com/docs/access-control-overview.pdf) require wired inputs into their cartridges to register events and operate locks. This does not, however, prevent wireless locks from integrating with the [AC41](https://docs.verkada.com/docs/door-controller-ac41-datasheet.pdf)/[AC42](https://docs.verkada.com/docs/door-controller-ac42-datasheet.pdf)/[AC12](https://docs.verkada.com/docs/ac12-one-door-controller-datasheet.pdf). This article focuses on how to use the Schlage AD300 wired lock with Verkada Access Controllers.

### Before you begin

### You will need the following hardware:

* [AC41](https://docs.verkada.com/docs/door-controller-ac41-datasheet.pdf)/[AC42](https://docs.verkada.com/docs/door-controller-ac42-datasheet.pdf)/[AC12](https://docs.verkada.com/docs/ac12-one-door-controller-datasheet.pdf) -Referred to as ACU.

  **Note:** The AC62 does not support Wireless locks.
* Schlage Utility Software (SUS) only compatible with android devices.
* SUS cable.
* AD300 lock with the AD300 RS485 Communication Module attached.\
  ​

  ![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-585d4bc9e57f66a309e6006a3dc5d6935e4fa74b%2Fe2b94e3399a44b792f1dfdcc0d70f63fb891c881.png?alt=media)

{% hint style="warning" %}
Required items vary, depending on the installation. For assistance, please contact your Allegion ESE.
{% endhint %}

### What you need to know

* While in **Schlage** mode, the ACU cannot control traditional wired doors/Verkada Readers in the same installation.
* AD300 is an AD400 with a different chip board and classification that allows for RS-485 connection direct from lock to panel, this requires reclassifying the lock in the SUS application.
  * Outside of how they are connected to the ACU, AD300s and AD400s have the same features when used with the Verkada system
* The AC41/AC42 can support up to 16 AD300s but can only power up to 4 wired AD300s at a time.
* Allegion recommends supplying power to each AD300 at installation point with an external 12/24 VDC power supply via an electric hinge, however power can be drawn from individual door ports on the AC41/AC42.

***

### Program and Wire the Door

Verkada’s ACU supports the combination of wireless locks via the PIM400-485 Hub and wired AD300 locks, and in total supports up to 16 locks.

In the AD300 series configuration, no bridge is used, and the locks wire directly to the ACU. It should be programmed before you add any Schlage doors in [Verkada Command](https://app.gitbook.com/s/NRq5qDDjsYNxwNzF1bcB/get-started-with-verkada-command).

***

### Set up the AD300 lock with Verkada ACU

{% hint style="warning" %}
In most cases, a locksmith or contractor will be following these instructions.
{% endhint %}

To begin, the AD300 requires more holes to be bored into the door for it to function because of the built-in DPI sensor. For hardware installation instructions, read [Schlage AD Cylindrical Series Installation Instructions](https://us.allegion.com/content/dam/allegion-us-2/web-documents-2/InstallInstructions/Schlage_AD-Series_for_Cylindrical_Installation_Instructions_102104.pdf).

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-d0aa545b3fabee1b98a2acb415cac13471f29463%2F2a6e76493cd69604f273eec39184e50d0d70c945.png?alt=media)

{% hint style="warning" %}
The cables are fragile and should be handled carefully, you may see degraded lock performance if any cables are pinched.

If the lid is not screwed on properly this could result in the tamper switch being triggered and cause the lock to output errors.
{% endhint %}

***

### Configure the AD300 lock

{% hint style="danger" %}
You **must** give all AD300 locks an address.
{% endhint %}

{% stepper %}
{% step %}

#### Wire lock to a power source or ensure battery is connected and battery cover is secured.

{% endstep %}

{% step %}

#### Connect the SUS-A Cable’s Type C cable to the Android phone and the USB cable to the lock bottom.

{% endstep %}

{% step %}

#### Launch the **Schlage Utility Software - SUS** app.

{% endstep %}

{% step %}

#### If this is the first time you log in to the **SUS** app, you need to set the password:

* User type: Manager
* Password: 123456
  {% endstep %}

{% step %}

#### Reset the password.

{% endstep %}

{% step %}

#### Login to Sus app:

If you log in to the **SUS** app and the SUS-A cable is not connected, the "CABLE NOT CONNECTED" message displays.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-3d0b4e86e5af001e622bbebd816a5465c6a8cf43%2F060b51c357e637ae880372fd7a764ef87eb8baf5.png?alt=media" alt="" width="397"></div>
{% endstep %}
{% endstepper %}

Couple the lock and SUS app:

{% stepper %}
{% step %}

#### Press the Schlage button at the top of the lock to wake it up for connectivity. Press and hold the **#** key on ADs that have a keypad.

{% endstep %}

{% step %}

#### Couple the device: Click **Couple \[PHONE\_NAME] to Device**. This fails if the device is **not in coupling mode.**

a. To put the lock in coupling mode, hold internal release (REX or # key) button of lock and press the small silver tamper switch 3 times, release internal REX button and immediately select couple device on phone app.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Coupling may take a few tries. If a device is already coupled to a different SUS phone, you will need to factory reset the lock twice in order to couple it for this installation.
{% endhint %}

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-89e4fc0a168cbc6dc96af237af6c3ae8e42a5a42%2F5164c43394418c69986425bca6487e3ec5387a4a.png?alt=media)

#### If reclassifying lock:

{% stepper %}
{% step %}

#### Once coupled select Change Lock Class from phone app.

{% endstep %}

{% step %}

#### Select firmware file from the file list for this lock.

{% endstep %}

{% step %}

#### Select lock model to reclassify as AD300.

{% endstep %}

{% step %}

#### Follow screen pop-ups to confirm and let it start to update.

{% endstep %}
{% endstepper %}

If failing to reclassify contact Allegion Support for further assistance.

***

### Configure lock Address in SUS app

While SUS-A Cable is connected to phone and lock.

{% stepper %}
{% step %}

#### If not coupled, will need to couple again, follow steps above to re-couple.

{% endstep %}

{% step %}

#### Go to Device configuration.

{% endstep %}

{% step %}

#### Configure an RS-485 address. Note down the address number, you will need it for Command Door setup.

{% endstep %}
{% endstepper %}

***

### Wire the AD300 to an ACU

{% hint style="warning" %}
See [Wiring Best Practices for Third-Party Wireless Locks KB](https://help.verkada.com/access-control/hardware-installation/wireless-locks/wiring-best-practices-for-third-party-wireless-locks) for more information.
{% endhint %}

#### Wire the AD300 to the AC41

The AD300 connects to the AC41 over a single pair RS-485. This means that you need to use 2 wires for data and 2 wires for power. It is recommended to ground the bare metal wire from the shielded wiring at the ACU’s negative battery terminal.

For AC41 integrations, wire the Communication Module to the RS-485 inputs on the **AUX** cassette.

{% hint style="warning" %}
\+ > VIN

\- > GND

A > TDA-

B > RDB+
{% endhint %}

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-2da2b545051da9c9466c9ae114616cfd9272ae45%2F686fd233f6b7aba3f424aa94304a435acd88c45f.png?alt=media)

#### Wire the AD300 to the AC12/AC42

The AD300 connects to the Ac12/AC42 over a single pair RS-485. This means that you need to use 2 wires for data and 2 wires for power. It is recommended to ground the bare metal wire from the shielded wiring at the ACU’s negative battery terminal on AC42 and the Drain Wire input next to Reader 1 on AC12.

* For AC42 integrations, wire the Communication Module to the RS-485 inputs on **Door 1**.

&#x20;

* For AC12 integrations, wire the Communication Module to the RS-485 inputs on **Reader 1**.

{% hint style="warning" %}
\+ > VIN

\- > GND

A > TDA-

B > RDB+
{% endhint %}

AC42 Door 1

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-2742ae7f88e901f8655c86d06ef5a829f80a49b6%2F02b30a2529afd34d2ea4abffeda17867004afefa.png?alt=media)

AC12 Reader 1:

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-4f1d047006dfe905253a1ed25b10e00f2bede278%2F4098fe7f5cdba321e9eb9713dc186d645111ba2b.png?alt=media)

#### **Wire more than 1 AD300 to an ACU**

{% hint style="danger" %}
ACUs cannot support daisy chaining **power for multiple AD300 locks but do require data** to be daisy chained in a linear bus topology.
{% endhint %}

* An AC41/AC42 can power up to 4 AD300 locks.
* An AC41/AC42 can draw power from other door ports or an external power supply for each additional Lock.
* The AC12 requires an external power supply for each additional lock.
* Allegion recommends powering with 12/24 VDC [external power supply at door installation via an electric hinge](https://us.allegion.com/content/dam/allegion-us-2/web-documents-2/WiringDiagram/Schlage_AD-300_AD-400_Schneider_ACX5720_40_RS485_Wiring_Diagram_109148.pdf).
* Data Wires (A\&B) must all be daisy chained to **AUX/Door 1 RS-485** inputs in a linear bus topology.
  * A star topology is not recommended and will likely lead to degraded performance.

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-860c7a04fa0ccb083038c9287c5c15c44507409f%2Fae9dccbfcf9512e04ff9bc6831dce2ae14893a87.png?alt=media)

***

### Add access control unit and locks to Command

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products** > **Devices**.

{% endstep %}

{% step %}

#### Click **Add Device**.

{% endstep %}

{% step %}

#### Type your ACU serial number and click **Add 1 Device**.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-f0d6b712f087a6319e00646bf90bbaaaef8d5d53%2Fd843207ab20e7b129b65b0e1d22e6ba60b4b69a2.png?alt=media" alt="" width="309"></div>
{% endstep %}

{% step %}

#### From the unassigned devices list, click the new access controller and click **Set Up**.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-39948dcbc00ee1530f3ee5fa45c05ef04b4855a2%2F3868b10c42a695a3972e0ef32e3b8bddcf9f3913.png?alt=media" alt="" width="124"></div>
{% endstep %}

{% step %}

#### On **Setup**:

{% endstep %}
{% endstepper %}

* Ensure that the ACU is in **Schlage** device mode.
* Ensure that a site, building, and floor are assigned.

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-8d330c10c11c87191ab9b4c0ba6d43599072a41b%2Fde423eea0015e2405880a38791ef431aa5ce096f.png?alt=media)

***

### Add an AD300 door

{% stepper %}
{% step %}

#### In Command, go to **All Products** > **Access Home** > **Controllers**.

{% endstep %}

{% step %}

#### Select the ACU wired to the Lock > in the top right select the **+ Add** to add a new door.

{% endstep %}

{% step %}

#### When prompted, select **Add Door** > **Lock Type: Wired-AD-300** and fill in the corresponding AD300 address. You should be able to see the paired door addresses in the SUS app. Once this information is entered, it is associated with the door.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-c2f0e2924fcfa2dd88ab97d84d88003723ac0961%2Fd7bf734f1fe31003b1e09f5a174f2d5214b9ca25.png?alt=media" alt="" width="381"></div>
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
AD300s have door position indicator (DPI) and request to exit (REX) built into the device. In the door installer **Settings** page, you can see that both DPI and REX are on, by default. If your DPI requires additional door hardware that is not installed, disable DPI.
{% endhint %}

You should see your newly added AD300 door listed in Command under the Access Controller page. This can take some time to sync. After 5-10 minutes if a Command page refresh does not show the lock as connected, test a keycard or keycode entry to generate connectivity.

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-abb1edd69b31a66081ddabd9c3d08ae22769ff39%2F1e8ba5477767d605bb0808cd0915c6695ea78bcb.png?alt=media)

***

## Troubleshooting guidelines

* Verify that your access controller unit (ACU) is in **Schlage Mode**. If you forgot to set it to **Schlage Mode**, you need to decommission it and re-add it.
* Verify that the AD300s have been successfully commissioned in SUS application.
* Ensure that the addresses for each AD300 were successfully configured and are matching between SUS application and Command.
* In the SUS app verify the lock does not need firmware update and check diagnostics tool to check for any logs that may indicate issues with the lock.

{% hint style="success" %}
**Need more help?** Contact [Verkada Support](https://www.verkada.com/contact/).
{% endhint %}
