Readers and live control

The Readers tab appears when Physical Access Control is enabled for the selected site. It shows the reader name, resolved controller, integration type, remote-open state, hardware position, and available actions.

Verify a reader before changing it

Match the reader name, controller, type, and position to the approved door schedule and the physical installation. A blank controller means TEKControl could not resolve the reader-to-controller relationship; correct that configuration before issuing commands.

Select Configure when you have configuration authority. Azure readers open inside the controller's hardware workspace. Other supported readers use the reader form, which can include interface, name, integration type, serial or Bluetooth identifier, position, access time, hold-open schedule, external ID, remote-open permission, and facility-entry or exit flags.

Changing position, interface, controller relationships, or external identifiers can route credentials and commands to the wrong door. Save only after validating the installed wiring and integration identifiers.

Send a live reader command

Select Command, or use Reader Command from a linked AllBox. The command is available only to a Field Technician when the selected site has Physical Access Control and the reader resolves to a supported controller.

Azure reader access control

1. Confirm the displayed controller and reader.
2. Review the available strike list derived from the reader's access-point configuration.
3. Select the intended strike or strikes.
4. Choose Use Long Strike Time only when the operational need calls for the configured long duration.
5. Select Send and verify the physical result.

If no strikes appear, review the Azure peripheral, access-point, reader, and strike relationships in hardware configuration.

Pulse another supported reader

TEKControl displays a Pulse access point confirmation before sending the command. Reconfirm the site, AllBox or reader name, and affected door, then select Pulse. Keri requires a site Keri device configuration; other supported controllers use the configured controller service.

Other Azure live controls

Controller actions and Azure utilities can expose:

• Access Point Control — select an access point, operating mode, strike-time type, custom timing when applicable, and either one strike or all strikes.
• Output / Relay Control — select a configured output and command mode, with a pulse duration when required.
• Reader Access Control — select a reader and one or more mapped strikes.

These commands act on live hardware. Selection labels come from the saved Azure hardware topology, so a mislabeled or outdated topology can target the wrong physical circuit.

Danger

Never use a live command until someone has verified that the door, gate, or relay can move safely. Maintain communication with onsite personnel, keep people clear of moving equipment, and verify that the access point returns to its expected state.

Command attempts are recorded in the controller audit with the user, controller, command, target, outcome, and available details. A success response means the service accepted or reported success for the command; always verify the physical result.