> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/low-level-interface-elevator-cars.md).

# Low Level Interface Elevator Cars

The Controller provides low level elevator access control using readers and input/output interfaces.

Readers may be installed in elevator cars to provide restricted access to floors with or without a [PIN](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#pin-personal-identification-number). Floors may be "unlocked", (i.e. the elevator floor select button enabled) on a time schedule.

Where entry to specific floors requires a PIN, the corresponding floor select buttons in the Elevator Car will not be enabled unless the Cardholder correctly enters their PIN. Access to other floors, that do not require PIN entry is allowed.

**Note:** See [Configuring Local Overrides at Card Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/status-and-overrides/configuring-local-overrides-at-card-readers.md) for further detail regarding card readers in elevators.

The flexible design of the Controller allows the Controller to be configured for almost any elevator control situation. The configuration is limited only by the following:

* Up to 75 levels per Controller
* Up to 4 elevator shafts per Controller 6000 or 7000

Typically, elevator control requires one card reader for each elevator car and one output for each floor select button in each elevator car. If destination reporting is required, then one input is required for each floor select button in each elevator car. If you are configuring elevator cars that are controlled via a high level interface refer to [High Level Interface Elevator Cars](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/high-level-interface-elevator-cars.md).

### In This Section

* [Configuring Elevator Cars](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/low-level-interface-elevator-cars/configuring-elevator-cars.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/low-level-interface-elevator-cars.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
