How to Set Up the DK22 Demo Kit

Introduction

The DK22 is a plug-and-play, portable demo kit that lets you quickly experience the power of Verkada’s cloud-based physical security platform.

The DK22 includes an access control deployment consisting of:

• Maglock door

• AC12 single door controller

• AD34 reader

• Push-button REX device

• AUX input

• AUX output LED

To showcase the powerful integration between Verkada products, the DK22 also includes a CM42 camera so you can see how seamlessly our access control and video security systems work together.

Lastly, we know finding an open network port for a demo can sometimes be a challenge, so the DK22 includes a GC31 cellular gateway to provide connectivity and PoE power to the other devices.

Unboxing

Start by removing the DK22 from its shipping container and placing it to the side for when you return the unit.

First, screw in the antennas so the cellular gateway can start to operate. 

Then, plug the DK22 into wall power.

Adding Devices to Command

If this is your first time creating a Command org, you can create one from any computer or mobile device, but we recommend a desktop or laptop for the easiest experience.

Navigate to command.verkada.com and follow the instructions. If you need help, click here for additional instructions.

You can also go through this process in an existing Command org.

In the product picker on the top left, click “Add Devices.”

On the back of the DK22, you’ll see a sticker with three serial numbers. You’ll need to enter all three serial numbers. Then click “Add 3 Devices.”

Setting Up Devices in Command

Click on the camera, and then click “set up” on the right. You can rename the device if you want. Then click “site”. You can add this device to an existing site if you have one, or follow the steps to create a new site. 

Now repeat those steps with the AC12, including choosing a building and floor.

Confirming Devices are Online

In the next few minutes, you should see that the LED on each of the devices has turned solid blue. This means they are online and communicating through the cellular gateway. You may need to power cycle the device if it doesn’t come up right away.

Once you see the blue LEDs, you can start configuring the access control system.

Configuring Access Control

Navigate to the Access Control tile, click Controllers, and click on the AC12 you just added. A door has automatically been created. Click the door, and then settings in the upper right. Pair the CM42 camera to this door as the exterior context camera.

Scroll down to the Hardware section, and make sure that the following settings are turned on: 

• DPI

• Monitor DHO (set threshold to 10 seconds)

• REX1

• REX1 Unlocks Door

Feel free to spend some time on this page exploring the other door configuration settings - in particular things like remote unlock, bluetooth unlock, and mobile NFC.

Your door is now set up. Give it a try by pressing the remote unlock button, or pressing the REX button on the DK22 itself. You’ll see the unlock event populate in Command.

Users and Access Permissions

Now let’s talk about giving the right users access to this door. Here’s how we think about access at Verkada:

• Each user has one or more credential types, like a card, fob, or mobile credential

• Users are assigned into one or more Access Groups, for example “HQ Employees”

• Each Access Group is then assigned to one or more Access Levels. Access Levels are what we use to determine who can access which doors at what times. In this case, the Access Level “HQ Working Hours” might be Monday through Friday from 8am to 6pm

Let’s set this up for the AC12. On the left side of the page, click Access Users and Groups. 

For testing purposes, create two new users, and call them User 1 and User 2. For each user, scan one of the included Verkada cards to create a credential for them. Make sure to keep track of which card is tied to which user - we’ll use this for testing later.

Next, click Groups across the top, and create a new one. We’ll name the group DK22 Testing. Add your own user profile and User 1 to this group - do not add User 2.

Navigate back to the Access homepage, and click Access Levels across the top, then create a new level. Name the access level whatever you want, add the DK22 Testing group you just created, select the site with the AC12 in it, and add the door that was automatically created earlier. For now, keep the schedule as Access Granted 24/7, and click Save.

Testing the System

Now you can test a fully functional access control system all from the DK22. 

Starting with the User 1 badge, try badging into the door - it should unlock. In Command, you can click on that door to see the access event populate and see the associated camera footage.

Close the door and now try to badge in using User 2’s credential. The door will stay locked and you’ll see the access denied event populate in Command. This is because we did not add User 2 to the Access Group associated with this door.

Feel free to spend some time on this Door Details page to familiarize yourself with the events and analytics.

Congratulations on completing the basic system test! 

Optional: Lockdowns

Verkada access controllers can perform lockdown events in case of an emergency. During a lockdown event, all selected doors and/or buildings are locked, and access to those doors is restricted to authorized user groups only.

From the Access homepage, click controllers, select the AC12, and click Add on the top right. Select AUX input and name it “panic button”. Make sure it’s showing the connection type as NO. 

Select “panic button” as the input type, and then “add scenario”. Give your scenario a name, then select the site that your AC12 is in and the door that we created. Add your access group as being able to both activate and deactivate a lockdown.

Once you’ve finished, push the panic button on the DK22 and see what happens to the door and in Command.

Don’t forget to release the lockdown from Command when you’re done.

Optional: AUX Outputs

Finally, let’s test the AUX output to light up when the door is held open. 

We already set the monitored door held open threshold to 10 seconds during setup.

Click Add Entity at the top of the Controller page again, and this time select AUX output. We’ll name this “DHO light”, and make sure Port 1 is selected. Choose Door Held Open as the event type and add the door we’ve been working with.

Now, unlock the door on the DK22 using the keycard or web unlock, and hold it open - you’ll see the light go on after 10 seconds. 

In a real life scenario, this output could be something like a siren or strobe light.

Conclusion

The DK22 supports Verkada’s full access control functionality, so feel free to play around with additional settings, schedules, and features in Command. Note that if you want to test the camera’s advanced analytics, those settings need to be enabled at the org level.

If you need any more help, feel free to reach out to our 24/7 support team by clicking the Help icon in Command.