AD Series Wired Lock Setup
Connect AD300 wired locks with your Verkada access controller
Verkada access controllers require wired inputs into their cartridges to register events and operate locks. This does not, however, prevent wireless locks from integrating with the AC41/AC42/AC12. 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:
Schlage Utility Software (SUS) only compatible with android devices.
SUS cable.
AD300 lock with the AD300 RS485 Communication Module attached.

Required items vary, depending on the installation. For assistance, please contact your Allegion ESE.
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.
Set up the AD300 lock with Verkada ACU
In most cases, a locksmith or contractor will be following these instructions.
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.

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.
Configure the AD300 lock
You must give all AD300 locks an address.
Couple the lock and SUS app:
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.
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.

If reclassifying lock:
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.
Wire the AD300 to an ACU
See Wiring Best Practices for Third-Party Wireless Locks KB for more information.
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.
+ > VIN
- > GND
A > TDA-
B > RDB+

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.
For AC12 integrations, wire the Communication Module to the RS-485 inputs on Reader 1.
+ > VIN
- > GND
A > TDA-
B > RDB+
AC42 Door 1

AC12 Reader 1:

Wire more than 1 AD300 to an ACU
ACUs cannot support daisy chaining power for multiple AD300 locks but do require data to be daisy chained in a linear bus topology.
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.
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.

Add access control unit and locks to Command
Ensure that the ACU is in Schlage device mode.
Ensure that a site, building, and floor are assigned.

Add an AD300 door
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.
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.

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.
Need more help? Contact Verkada Support.
Last updated
Was this helpful?





