Skip to content

Controllers and configuration

The Controllers tab appears when Physical Access Control is enabled for the selected site. It shows the controller name, integration type, health, IP address, host address, post, and available actions.

Review controller health

Open the row menu and select Health to view the matched central-health record. The action is disabled when no health target is associated with the controller. A successful health report verifies reporting connectivity; it does not prove that every reader, input, output, schedule, or credential is correctly configured.

Edit controller settings

With configuration authority, select Controller. The form groups:

  • site post, name, integration type, controller type, and external ID;
  • MAC address, serial number, IP address, port, username, password, and host address;
  • online status and health-alert recipients;
  • integration-specific DSX values; and
  • notes.

Changing the integration type or network identity can make the controller unreachable. Verify the installed controller, addressing plan, credentials, and post before saving. A saved controller record changes TEKControl configuration; it does not by itself prove the new values were applied to the physical panel.

Changing an Azure controller between supported two-door and four-door types resets its existing hardware configuration and applies the matching default after a separate confirmation. Keri controller records expose a confirmed Reboot Controller action when the site has the required Keri device configuration. Deleting a controller permanently removes its TEKControl record; first confirm its reader and configuration dependencies and follow the approved decommissioning process.

Use Azure hardware configuration

For Azure controllers, select Hardware. The configuration workspace contains six related sections:

  1. Serial Ports — port mode, speed, timing, and communication settings.
  2. Peripherals — downstream device identifiers, addresses, and types.
  3. Inputs — positions, thresholds, masking schedules, secure timing, and configured state.
  4. Outputs — positions, pulse behavior, schedules, and configured state.
  5. Access Points — operating modes, strike timing, door contacts, request-to-exit inputs, and relays.
  6. Readers — peripheral and access-point relationships, position, schedules, signal and reader modes, strike behavior, and facility-entry or exit flags.

Create dependencies in that order when commissioning new hardware. Before deleting an item, remove or update records that reference it. Saving these records changes the planned hardware topology; use the configuration controls only after matching every position and identifier to the wiring schedule.

The workspace also provides Default Configuration and Erase Configuration. Both can replace substantial configuration and require confirmation. Export or otherwise retain the approved current values before using either action.

Run controller utilities

Utilities is available for Azure and Vertex controllers.

Azure utilities

Azure utilities can restart the controller, request a named firmware file, check connectivity, and open output, access-point, or reader command dialogs. A connectivity check updates the stored online status and last-seen time. Enter only a firmware file that has been approved and made available to the controller service.

Vertex utilities

Vertex utilities can pull interface information and restart the controller. When card-format files are available, the format push writes format and card-set configuration, sets controller time, and requests a restart.

Administrator-level users also see manual file push, database changeover, task restarts, and the configured-host-address action. These are recovery and commissioning tools, not routine troubleshooting shortcuts. Confirm the destination path, file content, active database, and maintenance window before proceeding.

Danger

Restarts, firmware changes, file pushes, database changeover, task restarts, default configuration, and erase operations can interrupt access processing. Use an approved change window and maintain a safe alternate-entry plan.

Review the push queue

Select Push Queue to inspect configuration work for the selected controller. Filter by site, controller, or status, then select rows to Enable, Disable, or Remove them. These actions change pending delivery behavior, not just the grid display, and each bulk action asks for confirmation.

Use Refresh to verify the resulting status. Before removing a failed or disabled item, determine whether the underlying configuration is still required; removing the queue item does not undo a change that the controller already accepted.