Access Launchpad > Application > Monitor/Command > Devices > HID Aero

HID Aero Output

Location: Main Menu > Monitor/Command > Devices > Select Controller or Subcontroller > Add Device > Output

Overview

HID Aero Outputs are used to control external devices within the access control system. These outputs act as relays or signals that can be triggered by system events, user actions, schedules, or alarms.

Outputs are commonly used for door strikes, alarms, indicators, and auxiliary system controls, making them a key component in extending system functionality beyond basic access control.

Key Features

•Supports relay-based control of external devices

•Configurable online and offline behavior

•Can be triggered by:

oAccess events

oScheduled Commands

oThreat Levels

oManual commands

•Available on:

ox1100 controllers

ox100 and x300 subcontrollers

•Supports timed (pulse) or steady-state activation

Creating or Editing an Aero Output

1.Navigate to Devices

2.Select the appropriate controller or subcontroller (x1100/x100/x300)

3.Click the Add Device tab

4.Select Output

5.Click Create

This opens the Output configuration page.

Configuration Fields

General

•Description

oA descriptive name for the output (e.g., Front Door Strike, Alarm Siren, Gate Control Relay)

Settings Tab

•Output Number

oThe physical output terminal the device is wired to

•Online Mode

oDefines the default state when the system is communicating normally

•Offline Mode

oDefines the state when communication is lost

•Pulse Command Time (seconds)

oDuration the output remains active when triggered by a pulse command

Output Behavior

Outputs can operate in different ways depending on how they are triggered:

•Momentary (Pulse)

oActivates for a defined time, then returns to normal

oCommon for door strikes

•Latched (On/Off)

oRemains in the commanded state until changed

oCommon for lighting or alarm systems

Details Tab (Read-Only)

Used for troubleshooting and support.

•Aero Controller

oParent x1100 controller

•Hardware Server

oConnected Drawbridge server

•Aero Controller UID

oInternal system identifier

•Subcontroller UID

oPanel identifier (if applicable)

•SIO Number

oManufacturer reference

•Revision

oHardware revision level

•Firmware Version

oInstalled firmware version

•Serial Number

oUnique hardware identifier

History Tab

•Displays a full audit trail of:

oConfiguration changes

oOutput state changes

oSystem-triggered events

Common Use Cases

•Door strike control

•Alarm sirens or strobes

•Gate or barrier operation

•Elevator relay control

•Lighting or automation triggers

Best Practices

•Use clear and descriptive names for outputs.

•Verify correct wiring to output terminals.

•Set appropriate Pulse Command Time for the application.

•Define safe Offline Mode behavior (e.g., fail-safe vs fail-secure).

•Test outputs after configuration to confirm expected behavior.