The Verkada access controller physically connects to door components to manage access. Access controllers work with your building’s existing door hardware and readers.
Before you begin
Using events to AUX output requires that a Door Position Indicator (DPI)/contact sensor be installed on each door.
Using Door Forced Open (DFO) events requires a Request-to-Exit (REX) device to be installed or a badge-in-out policy to be in place.
Set up an AUX output
AUX output utilizes the dry relay on the AUX output of all models of Verkada access controllers, including the AX11. A single output can be configured for multiple doors and on different controllers. Event AUX output currently supports only Door Held Open (DHO) and DFO events.
In Verkada Command, go to All Products > Access.
Select an access control panel to set up. This panel should be on that does not have AUX outputs in use.
At the top right, click Settings.
Click Add.
On Add Entity, you should see the Aux Output option. This functionality is independent of the Emergency Lockdown function, which is still configured from the Lockdown Output option.
On Add AUX Output > General, fill out the Output Name and select the Port that you want to trigger the event on. You can use any output available on the device. When complete, click Next.
You will also see the Controller Name, Site, Building, and Floor where the event is being created. Note: All doors must be within the same site to work across each other.On Add AUX Output > Scenario:
Select the event type: Door Held Open or Door Forced Opened.
Select which doors to trigger this event scenario. You can select multiple doors within a site to trigger the event. You can also use multiple doors across different events.
Select the deactivation requirements. You can apply these requirements to only the door that triggers the event or to any door in the selected list of doors that can trigger the event.
Click Create.
Deactivate an active scenario
You can resolve and deactivate output events in these ways:
Deactivate from Command—Requires that the event be acknowledged from a logged-in Command session by an Access Site Manager before it ends. Recommended only for high security environments.
Timer—Indicates the end of a predetermined duration when the event will end. This is best for DFO events where the responders to the door may not have access to Command or for DHO events that do not always require resolution.
Door Opened—Indicates a valid badge door entry that triggered the event or any of the doors in a scenario the event will be resolved.
Door Closed—Indicates the door that triggered the event being closed, where the event will be resolved. We do not recommend this for DFO.
Note: You always have the option to acknowledge and deactivate any single event from Command, regardless of the default deactivation scenario.
Wire a door
You can wire an event to AUX output relatively simply by connecting your powered accessory device in series with the NO/COM/NC port of the AUX output relay, where:
On the access controller products, they are the AUX cassette or terminal block.
For the AX11, they are any of the output gates.
Note: These are dry relays that do not provide power themselves.
Requirement. The AUX output relays are rated to handle a passthrough signal of 24VDC at 2A current. If a VAC connection, a higher DC voltage connection, or a higher current-rated device is used, then an external APC is required for your accessory.
Power the AUX relay
Recommendation. By default, the AUX output does not provide power. We recommend to use a compatible power supply with your accessory, whether it's a buzzer or light wired into the relay. You are then able to power it up to 12VDC+ VDC at 250mA with the AUX power connection.
Alternatively, if you need a higher current demand on the device, and you have a spare door port that is not in use, you can share the power output from there for 12 or 24 VDC.
Set the power output to the desired 12V or 24V with the unit off.
Connect the door port COM to the negative side of your accessory.
Take the NC output from that door port and connect it to the COM port on the AUX relay.
Connect the positive (+) wire of the accessory to the desired NO/NC it is expecting; for most cases, this is NO.
The expected result is a powered AUX relay.
Note: You cannot apply a door to the port giving the power source.
Understand multiple active scenarios
In Verkada Command, under Access Events:
When a given scenario is active, you can see an event type for Aux Output Activated. This event type is made at the start of a given scenario. Once all active triggers are resolved, the Aux Output Deactivated event type is created.
Notice the Activation tag over each event that is currently holding a scenario active:
The event that kicks off an output scenario is seen prior to the trigger tile.
In this case a second trigger condition was met on 2 other doors, making 3 total alerts active; however, there are no additional trigger tiles because the original one was not yet resolved.
At the top right, click Active to see all active triggers for the event to AUX output.
(Optional) Clear the event and end the AUX output, regardless of the trigger dismissal conditions. This can be very useful for a loud alarm that you want to disable while you investigate the issue.
Troubleshoot DFO events
DFO events are triggered when the doors DPI sensor is detected as closed, yet the door is opened without a user badging in nor passing through a REX detection device from the secured side. There are some cases that a DFO can occur by accident:
Using the physical key to open the door without badging in
The timer for the REX device expiring before a user opens the door
A user tailgating into a door that has closed enough to engage the DPI sensor but not enough to re-engage the lock.
Recommendation. For cases where an unusual amount of DFO events are occurring, we recommend to review that your installation allows for proper exit and if the issue persists, please contact Verkada Support.
Related resources
Visit the Verkada Training Center for bite-sized video tutorials on how to accomplish role-based tasks in Command
Need more help? Contact Verkada Support