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

HID Aero Input

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

Overview

HID Aero Inputs are used to monitor the status of external devices and conditions within the access control system. These inputs receive signals from connected hardware and generate events in Drawbridge based on state changes.

Inputs are commonly used for door contacts, request-to-exit (REX) devices, alarm signals, and general-purpose monitoring, providing critical system awareness and triggering automated responses.

Key Features

•Supports supervised and unsupervised inputs

•Capable of detecting conditions such as:

oOpen circuit

oShort

oGround fault

oForeign voltage

•Supports analog-to-digital conversion (on supervised inputs)

•Can trigger:

oEvents

oAlarms

oScheduled or automated actions

•Available on:

ox1100 controllers

ox100, x200, and x300 subcontrollers

Creating or Editing an Aero Input

1.Navigate to Devices

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

3.Click the Add Device tab

4.Select Input

5.Click Create

This opens the Input configuration page.

Configuration Fields

General

•Description

oA descriptive name for the input (e.g., Front Door Contact, Motion Sensor, Fire Alarm Input)

Settings Tab

•Input Number

oThe physical input terminal the device is wired to

•Line Supervision

oDefines whether the input is:

▪Supervised (recommended)

▪Unsupervised

•Debounce

oTime (in milliseconds) the input must remain stable before registering a state change

•Hold Time

oTime (in seconds) the input must remain active before generating an event

Input Behavior

Inputs generate events based on state changes. Common behaviors include:

•Normally Open (NO)

oCircuit is open in normal state; closes when activated

•Normally Closed (NC)

oCircuit is closed in normal state; opens when activated

These behaviors are typically defined in associated configurations (such as Reader input settings or alarm definitions).

Details Tab (Read-Only)

Used for troubleshooting and support.

•Aero Controller

oParent x1100 controller

•Hardware Server

oConnected Drawbridge server

•Aero Subcontroller

oPanel the input is wired to (if applicable)

•SIO Number

oManufacturer reference value

•Aero Controller UID

oInternal system identifier

•Subcontroller UID

oPanel identifier

•Input UID

oUnique identifier for the input

•Monitor Point Number

oManufacturer-specific reference

History Tab

•Displays a full audit trail of:

oConfiguration changes

oState changes

oSystem-triggered events

Common Use Cases

•Door position monitoring (open/closed)

•Request-to-Exit (REX) devices

•Motion detectors

•Alarm system integration

•Tamper switches

•Environmental sensors

Best Practices

•Use supervised inputs whenever possible for better fault detection.

•Clearly label inputs based on location and function.

•Match NO/NC configuration with the physical device wiring.

•Set appropriate debounce and hold times to prevent false alarms.

•Test all inputs after configuration to verify proper event generation.