ANVILFIELD Try FieldOS

Field glossary · component

Controller

A controller makes operating decisions from inputs, stored logic, permissions, and system status, then commands outputs. Its failure boundary depends on what it can do locally. In access control, loss of a host connection can leave door decisions operating from local data; loss of controller power is a different event. In elevator work, the controller governs a much broader machine and safety interface.

The brain of the elevator: dispatching and the safety logic. The mod swaps obsolete relay logic for a microprocessor controller

Used across 2 Anvilfield field guides, most in Electrical.
Updated

Count doors separately from readers

HID Mercury’s LP1502 data sheet specifies native support for four readers and two openings, expandable to 64 readers and openings. Four reader connections therefore do not establish four independently controlled native doors. Entry and exit readers can belong to the same opening.

HID Mercury lists 240,000 cardholders and a 50,000-transaction buffer for the LP1502. Credential capacity and event capacity are different resources: a panel can retain its authorized users while its uncollected event history grows toward the buffer limit. Include both in an access-control submittal rather than using one large capacity number to represent the whole system.

Host independence is not power independence

HID Mercury describes the LP1502 as capable of operating independently of the host. HID Mercury’s February 2026 LP1502 installation manual calls for annual replacement of the memory-and-clock backup battery. That coin cell preserves static RAM and the real-time clock during loss of input power; the controller and locks need their own standby supply.

A network interruption and a mains-power interruption consequently need different acceptance checks. Verify the configured local access decisions during loss of host communication, and separately verify controller, reader, and lock operation under the installed standby-power arrangement. Record what happens to events awaiting upload and to schedules that depend on correct time.

HID Mercury rates LP1502 primary input at 12 to 24 VDC, ±10 percent, with 500 mA maximum consumption excluding reader and USB ports. A power budget using only that 500 mA figure omits explicitly excluded loads. Add the actual peripheral and lock requirements through the approved power-distribution arrangement.

The same LP1502 manual assigns the reader ports a combined 600 mA allowance added to primary current. At 24 V, the 500 mA controller allowance plus 600 mA for those ports totals 1.1 A, or 26.4 W, before USB and lock loads. Counting four logical readers as four independent board power ports would apply the reader-capacity number to the wrong resource.

An elevator controller is not a floor-permission interface

An access panel can exchange floor permissions with an elevator system without becoming the elevator’s motion controller. Keep that interface boundary explicit in the access-control scope and the elevator modernization scope. Identify which system owns authorization, movement, status reporting, and the specified failure response.

ASME lists A17.1-2025 as the current Safety Code for Elevators and Escalators edition. Replacing an elevator controller belongs to that equipment’s alteration and safety framework; installing a credential interface does not by itself establish an equivalent modernization scope.

Distinctions

Reader
A reader acquires credential information. The controller evaluates the configured access rules and drives the appropriate outputs; reader count alone does not state controlled-opening capacity.

Frequently asked questions

Will doors always unlock when the controller loses power?

The result depends on the locking hardware, power arrangement, and required egress and fire interfaces. Document the specified response for each opening rather than inferring it from the controller’s network behavior.

Sources checked

Also defined as

  • The device on the secure side that makes the grant-or-deny decision against schedules and a permission list and drives the lock

Where this shows up

Next step: Watch access-control project signals

Back to the full field glossary